12.07.2015 Views

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5BGPBFD for BGP4 debug comm<strong>and</strong>sTo debug Bidirectional Forwarding Detection (BFD) for BGP4, use the following debuggingcomm<strong>and</strong>s:• debug ip bgp [all-vrfs | vrf ] bfd• debug bfd application (Refer to this comm<strong>and</strong> on page 107.)• debug bfd itc (Refer to this comm<strong>and</strong> on page 111.)debug ip bgp bfdSyntax: debug ip bgp [all-vrfs | vrf ] bfd• all-vrfs - Displays information for all BGP BFD events.• vrf - Displays information for a specific VRF event.Comm<strong>and</strong> output resembles the following example.<strong>Brocade</strong># debug ip bgp bfdSep 9 18:37:07 BFD:ITC, Received BFD MHOP ITC Create Session Request from bgp(0)Sep 9 18:37:07 BFD: BFD MHOP ITC Create Session Response Sent to bgp(0)Sep 9 18:37:07 BGP: 6.1.1.2 Peer Received BFD MHOP Create Session Response ITC messageSep 9 18:37:07 BFD: BFD MHOP ITC Update Session Negotiated Parameters Request Sent to bgp(0)Sep 9 18:37:07 BGP: 6.1.1.2 Peer Received BFD MHOP BFD Session State Change Notify ITC messageSep 9 18:37:07 BGP: 6.1.1.2 Peer Received BFD session UP state notificationSep 9 18:37:07 BGP: 6.1.1.2 Peer BGP-BFD state changed to UPSep 9 18:37:07 BGP: 6.1.1.2 Peer Received BFD MHOP Update Session NegotSep 9 18:37:14 BFD:ITC, Received BFD MHOP ITC Route Change Indication from bgp(0)IPv6 ND debug comm<strong>and</strong>sThis section describes the IPv6 ND-related debug comm<strong>and</strong>s.debug ipv6 ndSyntax: [no] debug ipv6 ndThis comm<strong>and</strong> enables debugging for all neighbors. To enable debugging for a specific neighbor,enter the debug ipv6 nd comm<strong>and</strong> followed by the debug ipv6 address comm<strong>and</strong>.Comm<strong>and</strong> output resembles the following example.<strong>Brocade</strong># debug ipv6 ndIPv6 Generic:IPv6: nd debugging is onDebug message destination: ConsoleDec 10 15:04:10 ICMPv6-ND: Received NS for fe80::21b:edff:fe19:692 on 4/3 (4/3)from fe80::21b:edff:fe17:6632Dec 10 15:04:10 ICMPv6-ND: New neighbor entry fe80::21b:edff:fe17:6632 on port4/3, Link-Addr 001b.ed17.6632Dec 10 15:04:10 ICMPv6-ND: INCOMP->STALE: fe80::21b:edff:fe17:6632 on 4/3Dec 10 15:04:10 ICMPv6-ND: Sending NA for fe80::21b:edff:fe17:6632 on 4/3Dec 10 15:04:10 ICMPv6-ND: STALE->DELAY: fe80::21b:edff:fe17:6632 on 4/3 (ResolveNbr)Dec 10 15:04:10 ICMPv6-ND: adding neighbor to request listfe80::21b:edff:fe17:6632124 <strong>Brocade</strong> <strong>MLX</strong> <strong>Series</strong> <strong>and</strong> <strong>Brocade</strong> <strong>NetIron</strong> <strong>XMR</strong> <strong>Diagnostic</strong> <strong>Guide</strong>53-1002426-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!