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.

OSPF 5debug ip ospf log-empty-lsaSyntax: [no] debug ip ospf log-empty-lsaThis comm<strong>and</strong> logs instances when empty or truncated LSA update messages are sent or received.Comm<strong>and</strong> output resembles the following example.<strong>Brocade</strong># debug ip ospf log-empty-lsaOSPF: empty-LSA logging debugging is onSYSLOG: Dec 10 23:56:45 R3 OSPF: nbr state changed, rid 13.13.13.13, nbr addr187.1.1.2, nbr rid 15.15.15.15, state downSYSLOG: Dec 10 23:56:45 R3 OSPF: interface state changed, rid 13.13.13.13,intf addr 187.1.1.1, state designated routerSYSLOG: Dec 10 23:56:45 R3 OSPF: nbr state changed, rid 13.13.13.13, nbr addr187.101.1.2, nbr rid 15.15.15.15, state downSYSLOG: Dec 10 23:56:45 R3 OSPF: interface state changed, rid 13.13.13.13,intf addr 187.101.1.1, state designated routerSYSLOG: Dec 10 23:56:47 R3 OSPF: interface state changed, rid 13.13.13.13,intf addr 187.1.1.1, state backup designated routerSYSLOG: Dec 10 23:56:47 R3 OSPF: nbr state changed, rid 13.13.13.13, nbr addr187.1.1.2, nbr rid 15.15.15.15, state fullSYSLOG: Dec 10 23:56:47 R3 OSPF: intf rcvd bad pkt: Cannot associate neighbor,rid 13.13.13.13, intf addr 187.101.1.1, pkt size 120, checksum 41856, pkt src addr187.101.1.2, pkt type link state updateSYSLOG: Dec 10 23:56:48 R3 OSPF: intf rcvd bad pkt: Cannot associate neighbor,rid 13.13.13.13, intf addr 187.101.1.1, pkt size 60, checksum 48577, pkt src addr187.101.1.2, pkt type link state updateSYSLOG: Dec 10 23:56:52 R3 OSPF: intf rcvd bad pkt: Cannot associate neighbor,rid 13.13.13.13, intf addr 187.101.1.1, pkt size 88, checksum 50589, pkt src addr187.101.1.2, pkt type link state updatedebug ip ospf lsa-generationSyntax: [no] debug ip ospf lsa-generationThis comm<strong>and</strong> generates information about LSAs in output similar to the following example.<strong>Brocade</strong># debug ip ospf lsa-generationJan 15 16:35:25 OSPF: install a new lsa, type 3, ls_id 0.0.0.0, age 0, seq80000003 area-id 10Jan 15 16:35:25 OSPF: NSR : Sync node add, type 3, ls_id 0.0.0.0, age 0, seq80000003Jan 15 16:35:25 OSPF: originate router LSA, area 0Jan 15 16:35:25 OSPF: install a new lsa, type 1, ls_id 2.2.2.2, age 0, seq80000004 area-id 0Jan 15 16:35:25 OSPF: NSR : Sync node add, type 1, ls_id 2.2.2.2, age 0, seq80000004Jan 15 16:35:25 OSPF:NSR Sync ACK received for LSAJan 15 16:35:25 OSPF:ls_header.id 0.0.0.0 type 3 ToBesyncedState 2Jan 15 16:35:25 OSPF:NSR Sync ACK received for LSAJan 15 16:35:25 OSPF:ls_header.id 2.2.2.2 type 1 ToBesyncedState 2Jan 15 16:35:25 OSPF: install a new lsa, type 3, ls_id 37.0.0.0, age 0, seq80000001 area-id 1Jan 15 16:35:25 OSPF: NSR : Sync node add, type 3, ls_id 37.0.0.0, age 0, seq80000001Jan 15 16:35:25 OSPF:NSR Sync ACK received for LSAJan 15 16:35:25 OSPF:ls_header.id 37.0.0.0 type 3 ToBesyncedState 2Jan 15 16:35:28 OSPF: redistribute into ospf26.0.0.0 with ffffff00 forwardingaddress 0.0.0.0Jan 15 16:35:28 OSPF: originate external lsa26.0.0.0 with ffffff00Jan 15 16:35:28 OSPF: install a new lsa, type 5, ls_id26.0.0.0, age 0, seq80000001 area-id 0<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> 14953-1002426-02

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

Saved successfully!

Ooh no, something went wrong!