NETGEAR 7300S manual Migration of Configuration With a Firmware Upgrade, Code Mismatch

User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software

2.All units in the stack must run the same code version. Ports on stack units that don’t match the management unit code version don’t come up and the show switch command shows a “code mismatch” error. To resolve this situation the administrator may issue archive command. This command copies management unit’s software to the other units with mismatched code version. Before issuing this command, be sure the code running on the management unit is the desired code revision for all units in the stack. Once code is loaded to all members of the stack, the units must be reset in order for the new code to start running.

Migration of Configuration With a Firmware Upgrade

In some cases, a configuration may not be carried forward in a code update. For updates where this issue is to be expected, the following procedure should be followed:

1.Save the current configuration by uploading it from the stack, using the copy command from the CLI.

2.Load new code into the stack manager. Reboot the stack.

3.Upon reboot, go into the boot menu and erase the configuration (“restore to factory defaults”)

4.Continue with boot of operational code.

5.Once the stack is up, download the saved configuration back to the master. This configuration should then be automatically propagated to all members of the stack

Code Mismatch

If a unit is added to a stack and it does not have the same version of code as that of the master, the following should happen:

•“New” unit will boot up and become a “member” of the stack

•Ports on the added unit should remain in the “detached” state

•A message should appear on the CLI indicating a code mismatch with the newly added unit.

•To have the newly added unit to merge normally with the stack, code should be loaded to the newly added unit from the master using the copy command. The newly added member should then be reset, and should reboot normally and join the stack.

12-16 Managing Switch Stacks

202-10088-01, March 2005