2013-02-07 08:17 AM
I have installed ontap 8.1.2 simulator using VM Workstation 9 on WinServer 2008 R2. I was
2.pdf. Everything went fine until I powered on the simulator's VM.
After that it keeps rebooting with a critical message that 32MB is used for NVRAM.
Switching from normal to maintenance boot worked, and I was able to use ONTAP API. Yet when I
do any "aggr" or "vol" commands, it reports that there are no disks attached.
The VM Workstation reports that there are 4 hard disks installed as shown in the picture below.
I noticed that several older simulator installation instructions
installation-simple-steps-and-frequently-asked-questions, for example) are mentioning an
additinal step of adding DataONTAP-cf.vmdk virtual disk. I don't see this file in my download
of 8.1.2 simulator.
I will appreciate any ideas for moving forward.
Solved! SEE THE SOLUTION
2013-02-10 08:32 PM
welcome to communities,
I suspect the ontap vm is rebooting because its not seeing disks.
I would recommend to boot the VM . Press Ctrl+C to invoke boot menu and Press option 4
after this. you would get cluster setup prompt
hope this helps.
2013-02-10 08:42 PM
And for further steps i would recommend following
section Data ONTAP 7-Mode and Cluster-Mode setup
2013-02-11 08:52 AM
Yes, rebooting with option 4, allowed me to move on. If you have access to Simulate_ONTAP_8.1.2.pdf, it would be great to add this step there.
I still can't ping the simulator, probably because of network adapter setup problems on the VM hosting it. It would be helpful to have more detailed instructions for the adaptor setup in the Simulate_ONTAP_8.1.2.pdf too. For example, why DHCP is needed for using the bridged configuration.
2013-02-12 02:01 AM
glad to help.
>I still can't ping the simulator, probably because of network adapter setup problems on the VM hosting it.
i hope you are following the same steps as mentioned in the pdf. Is it still not working?
2013-02-13 10:18 AM
It looks like I needed to restart the virtual machine for the network adapter changes to take effect. Also, it looks like no DHCP server didn't prevent me using the bridged mode.