netapp sim upgrade

By Ron Havenaar/Dirk Oogjen

This is how it works with a new simulator:

1. Download the NetApp CDOT 8.2.1 simulator from
2. Unzip it to a directory of choice.
3. From that directory, import the DataONTAP.vmx file in VMware.
That can be a recent version of VMware workstation, Fusion or ESX, whatever you have.
4. The name of the imported vsim is now: vsim_netapp-cm. For this first node, you might first want to rename it to something like vsim_netapp-cm1.
5. The default setting for memory usage in the vm is 1.6 Gbyte. However, that is not enough for the upgrade.
You need to set this to at least 4 Gbyte. Later, when done with the upgrade, you can turn that back to 1.6 Gbyte. I tried, but less than 4 Gbyte won’t work…
6. Power On the simulator, but make sure you interrupt the boot process immediately!
You need the VLOADER> prompt.
In case you booted it before (when it is not a new machine), or you accidently booted the machine through from scratch, you cannot continue with it.
You MUST start with a new machine, and you MUST have the VLOADER> prompt at first boot if you want to change the serial numbers.
You CANNOT change the serial numbers on a machine that has been booted through before. (well… there is always a way.. but that takes much longer than starting from scratch again)
Just start over again if in doubt.
7. Two things need to happen now:
a. The serial numbers have to be set.
Each simulator in the set must have its own serial numbers. (more on this later)
b. You need to choose what kind of disks you want with this node.
These are the procedures for this: (next steps)
1. First the serial number:
Take for example the Serial Number 4082368507.
VLOADER> setenv SYS_SERIAL_NUM 4082368507
VLOADER> setenv bootarg.nvram.sysid 4082368507
2. Then choose the disk set to use for this node.
AGGR0 must be at least 10Gbyte for the upgrade, so be aware if you use small disks you have to add a lot of disks to AGGR0.

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
Type 23: 1 Gbyte FC
Type 30: 2 Gbyte FC
Type 31: 4 Gbyte FC
Type 35: 500 Mbyte SSD (simulated of course, for flashpool)
Type 36: 9 Gbyte SAS

Choose any combination of disks, but the maximum number of disks a simulator would allow is 56, no matter what size or type.
9. Then Boot the simulator.
10. Wait until you see the menu announcement.
Press Ctrl-C for the menu. Do NOT press enter after ctrl-C, ONLY ctrl-c !
If you press ctrl-c too quick, you get the VLOADER> instead.
If so, type: boot and wait for the menu announcement.
11. From the menu, choose option 4.
Confirm twice that you indeed would like to wipe all disks.
The system reboots.
12. Wait for the zeroing process to finish. That could take a while… Follow the dots… 😉
13. When done, follow the setup procedure and build your first Clustered Data Ontap node.
14. The cluster base license key in a cdot vsim is:
Further licenses can be easily added later using putty, since with putty you can cut and paste (on the VMware console in many cases you cannot), so you can skip the other licenses for now.
15. Turn off auto support:
Cluster::> autosupport modify -support disable -node *
16. Assign all disks:
Cluster::> disk assign -all true -node
17. Now add enough disks to Aggr0 to allow for enough space for the upgrade.
It has to be at least 10 Gbyte.
a. Cluster::> Storage aggregate show
b. Cluster::> Storage aggregate add-disks <# disks>
example: Cluster::> stor aggr add-disks aggr0 2
c. Cluster::> Storage aggregate show
d. Keep adding disks until you reach at least 10 Gbyte for Aggr0.
1. Log in with Putty and add all licenses for this node.
2. Check if the cluster is healthy:
Cluster::> cluster show
It should show the word ‘healthy’
3. Configure NTP time:
a. This is how to check it:
Cluster::> system services ntp server show
Cluster::> system date show (or: cluster date show)
b. This is an example how to set it:
Cluster::> timezone Europe/Amsterdam
Cluster::> system services ntp server create -server -node
Cluster::> cluster date show
1. This is how you can determine which image (OnTap version) is used on the simulator:
Cluster::> system node image show
2. Now it is time to make a VM Snapshot of the simulator, before you do the actual update.
A snapshot would allow you to revert to this state, start again with the update process, or update to a different version. Wait for the VM snapshot to finish before you continue.
3. If you don’t have it yet, download the Clustered Data Ontap image from the website. You need an account there to do so.
You can use the FAS6290 image, e.g. 822_q_image.tgz of 83_q_image.tgz (or whatever you need)
And yes, the simulator can be updated with this image! Neat huh!
4. We are going to use HTTP File Server (or HFS) to do the upgrade.
If you don’t have it yet, this is a free and very easy to use program, excellent for this job.
You can download it from
5. Add the .tgz image to HFS. Drag and drop will do. Do NOT unzip the image.
6. Make sure HFS is using the right local IP address.
If you have VMware on your local machine or any other program using a different IP range, HFS might use the wrong IP address. In HFS, go to the menu, under IP Address and check if the IP address is correct.
7. In the first line in HFS you see the URL you need to use. Write down this information.
8. Now we are going to do the upgrade:
Cluster::> system node image update -node * -package -replace-package true
Example: Cluster::> system node image update -node * -package -replace-package true

9. Since we only have one node, you cannot check if this is working fine.
If you decided to set up two or more nodes to start with, this is what you can do to check the progress on a different node:
Cluster::>> system node image show-update-progress -node *
You have to keep doing this until the system says: exited. Exit status Success
Otherwise, wait about half an hour. It takes quite a while! Be patient….!!!
10. When done, check if everything went okay:
Cluster::> system node image show
You should see the new version as image 2, but as you can see, that is not the default yet.

11. If it is indeed image2, choose to set this image as default:
Cluster::> system node image modify -node -image image2 -isdefault true
12. Check if that is okay now:
Cluster::> system node image show
Under ‘Is default’ is should say ‘true’
13. Reboot the node
Cluster::> reboot -node *
14. Just let it reboot completely. Do not interrupt. Wait for the login prompt.
The system would probably tell you the update process is not ready yet. No problem.
Just wait a few minutes. That will be done automatically.
15. If you want to check if it is still busy with the upgrade:
Cluster::> set -privilege advanced
Cluster::> system node upgrade-revert show
If you see the message: upgrade successful, it is ready.
16. You can check to see if everything has been upgraded correctly with:
Cluster::> system node image show
Cluster::> version
17. In VMware, you can set the memory usage back to 1.6 Gbyte now.
18. Now add the second node and follow the same procedure.
19. Alternatively, you could have set up two or more nodes with 8.2.1. first and do the upgrade afterwards, whatever you like better.

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:
1. Go to the systemshell
2. sudo chmod –r 777 /cfcard

Furthermore, if you want to run the simulator on a Vmware ESX-i box you need to change something there too:
1. Allow remote access with SSH and use putty to log in on your ESX-i server:
2. Edit the file /etc/rc.local.d/
3. Add the following text as last line:
vmkload_mod multiextent
4. Reboot the ESX box.

This entry was posted in Uncategorized. Bookmark the permalink.

Comments are closed.