2014-10-28 04:53 AM
We have a need to upgrade our production CMode cluster from 8.2.1 to 8.2.2P1 to address a bug. We'd like to test a critical application on the later version for functionality. Does anyone know whether there is a simulator download available for 8.2.2 (didn't see one on the download page), or if I'd be able to upgrade the 8.2.1 simulator to Ontap 8.2.2? I've searched around but it isn't clear whether an upgrade is doable.
2014-10-29 06:25 PM
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.
2014-11-11 01:34 AM
Upgrade the NetApp Clustered Data Ontap Simulator. This is how it is done.
In this procedure, I assume you start with new 8.2.1 simulators. If you want to upgrade existing 8.2.1. simulators you can, but some of the points down here would not apply then.
Please note that every simulator node in a cluster needs its own unique serial number. If you want to add more than one cluster and manage them with system manager, then too you need unique serial numbers for all of them.
This is how it works with a new simulator:
These are the procedures for this: (next steps)
Pick a simdisk inventory and enter the corresponding setenv commands at the VLOADER> prompt.
The default simdisk inventory is 28x1gb 15k:
setenv bootarg.vm.sim.vdevinit “23:14:0,23:14:1”
setenv bootarg.sim.vdevinit “23:14:0,23:14:1”
This inventory enables the simulation of multiple disk tiers and/or flash pools: (28x1gb 15k+14x2gb 7.2k+14x100mb SSD)
setenv bootarg.vm.sim.vdevinit “23:14:0,23:14:1,32:14:2,34:14:3”
setenv bootarg.sim.vdevinit “23:14:0,23:14:1,32:14:2,34:14:3”
This one makes the usable capacity of the DataONTAP-sim.vmdk even larger (54x4gb 15k)
setenv bootarg.vm.sim.vdevinit “31:14:0,31:14:1,31:14:2,31:14:3”
setenv bootarg.sim.vdevinit “31:14:0,31:14:1,31:14:2,31:14:3”
Using type 36 drives you can create the largest capacity.
Explanation of the above:
31:14:0 means: type 31 (4 Gbyte), 14 disks, shelf 0
You can use diofferent types (and disk sizes). Some examples are:
Choose any combination of disks, but the maximum number of disks a simulator would allow is 56, no matter what size or type.
Notes (not with detailed instructions):
The same procedure applies to 7-mode. The upgrade instructions are a bit different, but the procedure is the same. What we found out in 7-mode however, is, that we needed to set the /cfcard directory to read/write first, since it was read only. I did not have that issue with the cdot upgrade.
If you encounter that issue, this is what you need to do before the upgrade:
ESX usage note:
Furthermore, if you want to run the simulator on a Vmware ESX-i box you need to change something there too:
For any further questions: write to: firstname.lastname@example.org
Met vriendelijke groet / Kind regards,
2014-11-11 01:45 AM
What I forgot to mention in my post regarding upgrades of the simulator:
Upgrading the 8.2.1 Cdot simulator to version 8.3 unfortunately will not work.
The underlying BSD setup is different, and we cannot change that. The simulator crashes completely.
2014-11-11 08:06 AM
Option 7 is a little easier.
Start with a working simulator
Reboot to loader prompt
setenv bootarg.install.ramdisksize 512m
ctrl-C at the menu
pick option 7
Follow the prompts