Reference Guide

Layer 2 | 513
Figure 26-9. Debug FEFD packets display
During an RPM Failover
In the event that an RPM failover occurs, FEFD will become operationally down on all enabled ports for
approximately 8-10 seconds before automatically becoming operational again.
Figure 26-10. FEFD state change during an RPM failover
FTOS#debug fefd packets
FTOS#2w1d22h : FEFD packet sent via interface Gi 1/0
Sender state -- Bi-directional
Sender info -- Mgmt Mac(00:01:e8:14:89:25), Slot-Port(Gi 1/0)
Peer info -- Mgmt Mac (00:01:e8:14:89:25), Slot-Port(Gi 4/0)
Sender hold time -- 3 (second)
2w1d22h : FEFD packet received on interface Gi 4/0
Sender state -- Bi-directional
Sender info -- Mgmt Mac(00:01:e8:14:89:25), Slot-Port(Gi 1/0)
Peer info -- Mgmt Mac (00:01:e8:14:89:25), Slot-Port(Gi 4/0)
Sender hold time -- 3 (second)
02-05-2009 12:40:38 Local7.Debug 10.16.151.12 Feb 5 07:06:09: %RPM1-S:CP
%RAM-6-FAILOVER_REQ: RPM failover request from active peer: User request.
02-05-2009 12:40:38 Local7.Debug 10.16.151.12 Feb 5 07:06:19: %RPM1-P:CP
%IFMGR-5-OSTATE_UP: Changed interface state to up: Gi 0/45
02-05-2009 12:40:38 Local7.Debug 10.16.151.12 Feb 5 07:06:19: %RPM1-P:CP
%FEFD-5-FEFD-BIDIRECTION-LINK-DETECTED: Interface Gi 0/45 has bidirectional link with its peer