9.0 simulator release

[jtownsen]

With the release of 9.0RC1 I'm curious when we could be on the lookout for a 9.0 sim being published?

[locke]

Will 9.1 work on the 9.0 simulator?

Thanks,

Anne

[SeanHatfield]

Yes, if you perform an ONTAP upgrade insde the simulator, either through the option 7 boot menu or the normal update procedure.  The boot menu option is faster in the simulator.

[bob_lansley]

Is that using the standard 91_q_image.tgz image or is there a stripped down one more suited to the simulator?

[SeanHatfield]

Generally speaking the q_image will work.  It has since edge was introduced in 8.1.1.  Prior to that the vidconsole drivers were missing from the kernel and the vmservices components were not included in the root image.    There is a v_image vairant specific to the virtual platforms that doesn't have all the firmware, etc, for the physical platforms included.  If you are entitled on one of the virtual platforms you can download it from there (edge, select, or cloud).

On 9.1RC2 and newer you have to change the console variable in the loader if you use the vidconsole (which is the default)

setenv console vidconsole,comconsole

Otherwise it will not boot after the upgrade.

[Neil_Anderson]

Thanks Sean!

[ohaensel]

Thanks Sean, that was it!

Best regards

Oliver

[bob_lansley]

Thanks Sean

I now have 9.1 running on my simulator. The pointer regarding upgrading via option 7 from the boot menu was also very useful (much quicker and lighter on disk space)

Cheers,

Bob

[bob_lansley]

If adding a second node does SYS_SERIAL_NUM just have to change from XXXXXXX-XX-1 to XXXXXXX-XX-2 to be different from node 1 or does it have to be the one used in the setup/install PDF (which appears to have been blended from a previous ONTAP 8 version)

[SeanHatfield]

The serial numbers (SYS_SERIAL_NUM) need to match one of the license key sets in the license text files on the download page.  Licenses are keyed to the serial number so pick from one of the ones on the list.

The sysid (bootarg.nvram.sysid) just needs to be unique, in particular the last two digits need to be unique.  By convention people set them to match the serial number, but they don't acutally have to.  What you want to avoid is cloning a vsim VM thats been through a power cycle, because the simulated disk serial numbers (which are in part derived from the sysid) will not be unique, and that leads to some really strange behaviour with the disk related commands if more than one instance ends up in the same cluster.