cat /proc/net/bonding/<bond id>
show cluster bond name <bond_name>
cphaprob show_bond <bond_name>
link
as no.show cluster state
cphaprob state
If any of the VSX Cluster Members has a State
other than Active, see the R80.30 ClusterXL Administration Guide - Chapter Monitoring and Troubleshooting Clusters.
On a VSX Cluster Member, reboot is needed after the following actions on a bond interface:
Note - Removing a slave interface does not require reboot.
For further information regarding bond status and failovers, view logs in the Logs & Monitor view. Any interface bond status change is logged and can be viewed in Logs & Monitor.
When using certain switches, connectivity delays may occur during some internal bond failovers. With the various features that are now included on some switches, it can take close to a minute for a switch to begin servicing a newly connected interface. The following are suggestions for reducing the startup time after link failure.
Note - PortFast is not applicable if the bond group on the switch is configured as Trunk. |
The PortFast feature should never be used on ports that connect to other switches or hubs. It is important that the Spanning Tree complete the initialization procedure in these situations. Otherwise, these connections may cause physical loops where packets are continuously forwarded (or even multiply) in such a way that network will ultimately fail.
The following are the commands necessary to enable PortFast on a Gigabit Ethernet 1/0/15 interface of a Cisco 3750 switch running IOS.
cisco-3750A#conf t
cisco-3750A(config)#interface gigabitethernet1/0/15
cisco-3750A(config-if)#spanning-tree portfast