266
Protocol: BGP4+ Process ID: 0
SubProtID: 0x1 Age: 00h01m07s
Cost: 50 Preference: 255
Tag: 0 State: Active Adv
OrigTblID: 0x1 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NBRID: 0x25000001 LastAs: 0
AttrID: 0x1 Neighbor: 3000::1
Flags: 0x10060 OrigNextHop: 3000::1
Label: NULL RealNextHop: FE80::20C:29FF:FE4A:3873
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface101
BkTunnel ID: Invalid BkInterface: N/A
The output shows that Switch C communicates with network 1200::0/64 through the path Switch
C<—>Switch B<—>Switch A. Then the path Switch C<—>Switch B<—>Switch A fails.
# Enable debugging on Switch C.
<SwitchC> debugging bgp event
<SwitchC> terminal monitor
<SwitchC> terminal logging level 7
%Mar 14 15:00:24:256 2012 SwitchC BFD/6/FSM: -VDC=1; Sess[3002::2/3001::1, LD/RD:
513/513, Interface:N/A, SessType:Ctrl, LinkType:INET], Sta: UP->DOWN, Diag: 1
*Mar 14 15:00:24:257 2012 SwitchC BGP/7/DEBUG: -VDC=1;
BGP.: 3001::1 Receive ManualStop event in ESTABLISHED state.
*Mar 14 15:00:24:257 2012 SwitchC BGP/7/DEBUG: -VDC=1;
BGP.: 3001::1 Send NOTIFICATION
Err/SubErr: 6/0 (Cease/ErrSubCode Unspecified)
Error data NULL.
*Mar 14 15:00:24:258 2012 SwitchC BGP/7/DEBUG: -VDC=1;
BGP.: 3001::1 State is changed from ESTABLISHED to IDLE.
The output shows that Switch C can quickly detect the link failure and notify BGP to change the relevant
IBGP session state.
# Display route 1200::0/64 on Switch C.
<SwitchC> display ipv6 routing-table 1200::0 64 verbose
Summary Count : 1
Destination: 1200::/64
Protocol: BGP4+ Process ID: 0
SubProtID: 0x1 Age: 00h00m57s
Cost: 100 Preference: 255
Tag: 0 State: Active Adv
OrigTblID: 0x1 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NBRID: 0x25000000 LastAs: 0
AttrID: 0x0 Neighbor: 2000::1
To Next Page
Loading...
