Manually Switching Nexus1000v Active VSM to Standby
Use this procedure to manually switch an active VSM to standby in a dual supervisor system.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You are logged in to the active VSM CLI in EXEC mode.
•You have completed the steps in the “Verifying that a System is Ready for a Switchover” section, and have found the system to be ready for a switchover.
•A switchover can only be performed when two VSMs are functioning in the switch.
•If the standby VSM is not in a stable state (ha-standby), then you cannot initiate a manual switchover. You will see the following error message:
Failed to switchover (standby not ready to takeover in vdc 1)
•Once you enter the system switchover command, you cannot start another switchover process on the same system until a stable standby VSM is available.
•If a switchover does not complete successfully within 28 seconds, the supervisors will reset.
•Any unsaved running configuration that was available at active VSM is still unsaved in the new active VSM. You can verify this unsaved running configuration using the show running-config diff command. Save that configuration, if needed, as you would do in the other VSM (by entering thecopy running-config startup-config command).
SUMMARY STEPS
1. system switchover
2. show running-config diff
3. copy running-config startup-config
EXAMPLES
This example shows how to switch an active VSM to the standby VSM and displays the output that appears on the standby VSM as it becomes the active VSM.
n1000v# system switchover
----------------------------
2009 Mar 31 04:21:56 n1000v %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_PRE_START:
This supervisor is becoming active (pre-start phase).
2009 Mar 31 04:21:56 n1000v %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_START:
This supervisor is becoming active.
2009 Mar 31 04:21:57 n1000v %$ VDC-1 %$ %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.
2009 Mar 31 04:22:03 n1000v %$ VDC-1 %$ %PLATFORM-2-MOD_REMOVE: Module 1 removed (Serial
number )
This example shows how to display the difference between the running and startup configurations:
n1000v# show running-config diff
*** Startup-config
— Running-config
***************
*** 1,38 ****
version 4.0(4)SV1(1)
role feature-group name new
role name testrole
username admin password 5 $1$S7HvKc5G$aguYqHl0dPttBJAhEPwsy1 role network-admin
telnet server enable
ip domain-lookup
source link