|
|
|
The active Cisco VSG does not see the standby Cisco VSG. |
Roles are not configured properly:
|
Do the following: 1. Verify the role of each Cisco VSG by entering the show system redundancy status command. 2. Update an incorrect role by entering the system redundancy role command. 3. Save the configuration by entering the copy run start command. |
Network connectivity problems are occurring between the Cisco VSG and the upstream and virtual switches. The problem could be in the control or management VLAN. |
Restore connectivity as follows: 1. From the vSphere client, shut down the Cisco VSG, which should be in standby mode. 2. From the vSphere client, bring up the standby Cisco VSG after network connectivity is restored. |
The active Cisco VSG does not complete synchronization with the standby Cisco VSG. |
A version mismatch between Cisco VSGs might be occurring. |
Do the following: 1. Verify the software version on both Cisco VSGs by entering the show version command. 2. Reinstall the secondary Cisco VSG with the same version used in the primary. |
Fatal errors occur during the gsync process. Check the gsyncctrl log by entering the show system internal log sysmgr gsyncctrl command and look for fatal errors. |
Reload the standby Cisco VSG by entering the reload module standby_module_number command. See the “Reloading a Module” section. |
The standby Cisco VSG reboots periodically. |
The Cisco VSG has connectivity only through the management interface. When a Cisco VSG is able to communicate through the management interface, but not through the control interface, the active Cisco VSG resets the standby to prevent the two Cisco VSGs from being in HA mode and out of sync. |
Check control VLAN connectivity between the primary and secondary Cisco VSG by entering the show system internal redundancy info command. In the output, degraded_mode flag = true. If there is no connectivity, restore it through the control interface. |
Both Cisco VSGs are in active mode. |
The following network connectivity problems might be occurring:
- Check for control and management VLAN connectivity between the Cisco VSG at the upstream and virtual switches.
- When the Cisco VSG cannot communicate through any of these two interfaces, they both try to become active.
|
If network problems exist, do the following: 1. From the vSphere client, shut down the Cisco VSG, which should be in standby mode. 2. From the vSphere client, bring up the standby Cisco VSG after network connectivity is restored. |
Active and standby Cisco VSGs are not synchronized. |
Incompatible versions The boot variables for active and standby Cisco VSGs are set to different image names, or if image names are the same, the files are not the correct files. When active and standby Cisco VSGs are running different versions that are not HA compatible, they are unable to synchronize. |
Update the software version or the boot variables as follows: 1. From each Cisco VSG (active and standby), verify the software version by entering the show version command. 2. Reload the standby Cisco VSG with the version that is running the active Cisco VSG by doing one of the following: – Correct the boot variable names. – Replace the incorrect software files. See the “Reloading a Module” section. |
Broadcast traffic problem The broadcast traffic from the standby to the active Cisco VSG might prevent the Cisco VSGs from synchronizing. The standby Cisco VSG tries to contact the active Cisco VSG periodically, but if broadcast traffic problems persist for over a minute when the standby is booting up, the system cannot synchronize. |
Fix the traffic problem and reload the standby Cisco VSG as follows. 1. From the standby Cisco VSG, verify the broadcast traffic problem by entering the show system internal log sysmgr verctrl command. The following message appears: standby_verctrl: no response from the active System Manager 2. Fix network connectivity. 3. Reload the standby Cisco VSG by using the reload module standby_module_number command. See the “Reloading a Module” section. |
False standby removal The active Cisco VSG falsely detects a disconnect with the standby. The standby is removed and reinserted and synchronization does not occur. |
Verify redundancy states and reload the standby Cisco VSG as follows: 1. Verify active Cisco VSG redundancy by using the show system internal redundancy status command. The output is as follows:
2. Verify the standby Cisco VSG redundancy by using the show system internal redundancy status command. The output is as follows:
3. Reload the standby Cisco VSG by using the reload module standby_module_number command. See the “Reloading a Module” section. |
The Cisco VSG HA pair reboots continuously in headless mode (VSMs are down). |
The nonsystem VLAN Cisco VSG ports are down after they reconnect post reboot of the Cisco VSG because the VSM is not present to bring them up. |
Check if the service and HA VLANs are configured as system VLANs. If they are not system VLANs and the Cisco VSG pair reboots for any reason, they do not come back up until the VSM comes up. |