Something has changed in the fake nvram implementation.  full/partner/panic works, just not fake.    And it needs more ram than 8.2.x did.  Hoping we'll get an official vsim soon.  The upgrade is bumpy.     ... View more

I hit this last night on 8.2.1. The fix was simple enough, increase vm ram to 2gb. ... View more

If you use the 7mode serial numbers for nodes3&4, the keys from the 7mode sheet will activiate those features on the additional nodes.     ... View more

Option 7 is a little easier.   Start with a working simulator Reboot to loader prompt setenv bootarg.install.ramdisksize 512m boot ctrl-C at the menu pick option 7 Follow the prompts       ... View more

the registry is a file containing opions in key=value format  wild guess, that api call returns the value associated with a key. ... View more

Does it bootloop again after the option 4? (the first reboot is expected).   If so, something happened during init that prevented the simdisks from being created.  To confirm, Ctrl-C to the boot menu, then ls /sim/dev/,disks if the directory is empty, you need to rearm vdevinit at the loader:   Reboot, stopping at the LOADER> prompt, then enter the following: setenv bootarg.vm.sim.vdevinit "23:14:0,23:14:1" setenv bootarg.sim.vdevinit "23:14:0,23:14:1" boot   Then Ctr-C, option 4.  You should get a reboot, then a wall of dots, then the setup script.   ... View more

Cool.  There is the problem.   The first license you tried was for 4082368511, and the 2nd was for 4079432753.  You need the keys for 4233367593 and 4233367594.   Most of us would have to rebuild using node serials from the keys on the download page, but you appear to be internal so you've probably got better options.   If these nodes were built with an internal tool i'd imagine appropriate keys should be available to you.  If you built them by hand and just made up those node serials you'll have to drum up eval keys.   The keys really do have to match.  Can't say why they would work on your other sim pair.  They really shouldn't, and don't match the license type shown in your output.   Your hongboy sim pair has site licenses installed, but the keys on the download page are node-locked licenses. license show -instance on the hongboy sim would probably confirm that.  Just whatever you do, don't post a site license key in an open forum.           ... View more

  Run this command: system node show -fields node,systemid,serialnumber   have a look at the serial numbers in the output, and intall the licenses for those serial numbers.     ... View more

upgrade sorta works, but in all likelyhood will get killed by a watchdog timer before it completes because the upgrade process gets QOSd to the background and the VHA disk subsystem is so slow it can take over an hour to update a node.  If the node lives on an SSD you might get lucky, otherwise use the Ctr-C boot menu and run the upgrade from option 7.   That might also fail, but for a different reason.  sometimes the ramdisk is too small to unpack the update, but the error will display the bootarg you have to set to resize the ramdisk if required.       ... View more

It runs on 5.5.   The problem they will have is that one of the VMDKs is in 2gb sparse format, which is not supported on an out of the box 5.5 install. A few ways to fix that include -load the multiextent module from the esx cli -convert the vmdk to either thin or thick from the esx cli -use vmware converter to import the vm -convert it to an OVF and import the ovf   Those are approximately in ascending order of difficulty     ... View more

You have to build the VM, from scratch.  You'll need a windows server ISO.  Eval copies are usually available from microsoft but you'll have to seaarch microsoft.com.   ... View more

You can do it all nested on your laptop provided you have enough RAM and storage.    Active Directory is a big topic, but a minimalistic install should be enough to get you through CIFS setup Short version: 1. Install a windows server VM on the NAT network 2. Assign a static IP within the windows VM 3. Run DCPromo from the windows command line and follow the steps in the wizard.   Part of that will have you picking a domain name, make sure its something unique/private to your lab environment.  Or just reuse the name in the netapp courseware.   Then when setting up your cifs SVM, use the IP of the DC as the DNS server, the domain name used in DC promo, and the administrator credentials of the windows VM.   ... View more

Sure, you just build a windows server VM and configure it as a domain controller on your NAT network.  Without one, you will not be able to configure a CIFS svm.   ... View more

You need more than a domain name, you need an actual domain.  As in, Active Directoy domain controller.  Use whatever domain name belongs to your domain controller, and use its IP as the DNS server.     ... View more

Hard to say. Is it possible they have duplicate macs? At this point you might want to sign up for an eval of workstation so you have more control and visibility into the virtual networks. ... View more

Yes, Eugene posted the instructions they used to use in the courseware.  I posted an alternate method in the comments: http://community.netapp.com/t5/NetApp-University-Articles-and-Resources/Simulators-and-SSDs/ta-p/86888   ... View more

The license key is in the 8.0 simulator license key file.  But thats the easy part.  Setting up HA in the sims is pretty complicated, which is probably why its totally unsupported.     ... View more

You should be able to run 2 clusters on the same subnet, assuming you use different IPs for node/cluster mgmt, and a differeent cluster name.  During cluster join, be careful to join the correct cluster.   If you want to put the 2nd on a different subnet, its going to be challenging in player.  If the VMNET exists, your host pc will have an IP on that VM net and you can get the network/subnet/gateway addersses from that interface on the host pc.   ... View more

Might be on to something there.   The gateway on the nat network is almost always on .2   But even so, you should be able to putty in to the node interfaces.  If thats working, but the cluster management lif is not, we just have to fix the lif/routing groups.       ... View more

What address did you use for the default gateway? And can you ping it from inside the simulator? ... View more

You'll likely have problems booting since all the PCI devices now have slot assignments.   So after adding the bridge code, when you boot you'll get an error about not enough pci slots.  Find the device(s) referenced in the error and change their slot ID to -1 by editing the vmx file.  Then you will probably be able to boot.     ... View more

That looks fine, the cluster lifs on e0a/e0b are autoassigned in the 169 network.  If the join fails, on sibsequent attempts those ips have already been generated so you can just accept the previous values.   Changing the serial needs to be done during the first power on.  Adding nics should be done before the first power on, so it sounds like you've done everything correctly.   Whats the message you get when the join fails?   ... View more

Odds are no, so since you can't change the subnet of the NAT network in player, you have to figure out what subnet its actually configured for and adjust your IP settings accordingly during the cluster setup script.   The "NAT" network is really VMNET8, so check your host machines ipconfig /all for the ip range/netmask/gateway for VMnet8.  Use IPs in that range instead of whats called out in the simulator documentation, and you won't need the vm network editor.  Just assign nic0 and nic1 to "host-only" and the rest to "nat" and it should all fall into place.     ... View more