nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Serial Number and System ID change

paultodd99

I'm building the second node as per the install instructions but am getting a system id mismatch error after setting the env variables SYS_SERIAL_NUM and bootarg.nvram.sysid. Any suggestions? This is the 8.2.1RC1 version of the simulator in cluster-ontap mode.

Thanks

Find more posts tagged with

ONTAP Simulator

Accepted answers

shatfield

Here's an example:

vSim was originally built with sn:4034389062, I'll change it to 4079432753. (Need to stick to serial numbers with published license key sets)

From the VLOADER>

Set the new serial number in both places:

setenv bootarg.nvram.sysid 4079432753

setenv SYS_SERIAL_NUM 4079432-75-3

If I boot now, I'll see:

WARNING: System id mismatch. This usually occurs when replacing CF or NVRAM cards!

Override system id? {y|n} [n]

pick y

Now you'll get a system panic:

PANIC: Can't find device with WWN 0x1649431296. Remove '/sim/dev/,disks/,reservations' and restart

Don't panic, lets do that:

reboot again, this time Ctrl-C to bring up the boot menu

When the boot menu appears, type:

systemshell

now we're in the systemshell, aka the BSD shell

Enter the command:

rm /sim/dev/,disks/,reservations

poof, no more reservations. But we still need to reassign disk ownership to our new vsim sysid. So exit the systemshell:

exit

and now you're back at the boot menu, so its option 5 - Maintenance mode

when you eventually get to the *> prompt, type:

disk assign all

halt

Then reboot the sim, and it should be up and running on the new sysid. All you have left is to apply the corresponding license keys for the serial number.

All comments

shatfield

Did you start with a fresh copy of the sim? Try replacing the cf vmdk and var vmdk with clean copies from the tgz.

I wish they would ship it with autoboot turned off.

paultodd99

I didn't see a cf vmdk, but I did replace the DataONTAP-var.vmdk and DataONTAP-sim.vmdk files with original ones from the tgz package. I had also found and edited a file called env within the cfcard\env directory of the virtual machine folder. Replacing just the -var.vmdk didn't work, but after editing the env file with the updated serial info I used in the instructions and replacing the -sim.vmdk file, I got past the error that prevented the simulator from booting. I don't know if editing the env file directly had anything to do with this, but this file still contained the original SYS_SERIAL_NUM and bootarg.nvram.sysid.

Thanks for your suggestions.

shatfield

Glad you got it working. The env file is a remnant of the build process, and not actually used by the simulator. A copy of it lives on the boot device, DataONTAP.vmdk - historically a compactflash card, and represents the initial boot environment for the simulator. If you are going to make changes, such as modifying the serial, switching modes or adjusting the simdisk inventory, its best to catch the very first boot. During the first boot, the nvram is discarded, /var is populated, and /sim is populated with simdisks. If you miss the first window and have problems its easier to start over with clean files than it is to reset and re-arm those initialization processes.

viana

Hi, Sean.

So how can I edit a Serial Number if my second node is getting it's serial duplicated (same serial as 1st node?)

I've tried paultodd99 proccess but of course that didn't work based on what you explained.

Thanks,

Patricia