port-channel failover-groupgroup 1 port-channel 1 port-channel 2As shown in the following illustration, LAGs 1 and 2 are members of a failover group. LAG 1 fails and LAG2 is brought down after the failure. This effect is logged by Message 1, in which a console messagedeclares both LAGs down at the same time.Figure 47. Configuring Shared LAG State TrackingThe following are shared LAG state tracking console messages:• 2d1h45m: %RPM0-P:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Po 1• 2d1h45m: %RPM0-P:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Po 2To view the status of a failover group member, use the show interface port-channel command.R2#show interface port-channel 2Port-channel 2 is up, line protocol is down (Failover-group 1 is down)Hardware address is 00:01:e8:05:e8:4c, Current address is 00:01:e8:05:e8:4cInterface index is 1107755010Minimum number of links to bring Port-channel up is 1Port-channel is part of failover-group 1Internet address is not setMTU 1554 bytes, IP MTU 1500 bytesLineSpeed 1000 MbitMembers in this channel: Gi 1/17(U)ARP type: ARPA, ARP Timeout 04:00:00Last clearing of "show interface" counters 00:01:28Queueing strategy: fifoNOTE: The set of console messages shown above appear only if you configure shared LAG statetracking on that router (you can configure the feature on one or both sides of a link). For example,as previously shown, if you configured shared LAG state tracking on R2 only, no messages appearon R4 regarding the state of LAGs in a failover group.Important Points about Shared LAG State TrackingThe following is more information about shared LAG state tracking.• This feature is available for static and dynamic LAGs.Link Aggregation Control Protocol (LACP) 433
