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...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

802.1ag CFM for VPLS debug comm<strong>and</strong>s 3• The setting for POS keepalive messages must be the same on both ends of the link. Keepalivemessages are enabled by default for POS interfaces.• The Data-Link Connection Identifier (DLCI) is the circuit ID for the link <strong>and</strong> can be a number inthe range from 1 through 1023. The circuit ID must be the same on both ends of the link.• POS modules use their own field-programmable gate arrays (FPGAs).• B<strong>and</strong>width – You can change a 2488 Mbps port to run at 622 Mbps if needed.• SPE scrambling is enabled by default. Both ends of a link must use the same scramblingalgorithm.• Cyclic Redundancy Check (CRC) – You can specify the length of the CRC field in each packetsent by the POS interface. The default length is 32 bits. You can change the length to 16 bits.• POS overhead flags – You can change the following values in the POS frame header:- c2 – Payload content type. The default is 0x16, which specifies PPP with scramblingenabled.- j1 – Path trace byte. Default is 0x0.- j0 – Section trace byte. Default is 0x1.Common diagnostic scenariosIssues with POS modules are usually hardware-related. The following problems may occur:• Memory defects are in the module hardware.• The module is not sending bridge protocol data units (BPDUs).• Free queue depth levels are rising <strong>and</strong> falling.• Modules in a particular chassis slot are showing similar errors. In this case, the chassis slotconnector may be faulty. Contact <strong>Brocade</strong> Technical Support if you suspect a faulty chassisslot.802.1ag CFM for VPLS debug comm<strong>and</strong>sThe debug comm<strong>and</strong>s for troubleshooting 802.1ag Connectivity Fault Management (CFM) forVirtual Private LAN Service (VPLS) are described in this section.debug cfmSyntax: [no] debug cfm This comm<strong>and</strong> enables 802.1ag debugging. The variable is a value from 0 through 7.Setting the level to 7 enables debugging of all CFM packets.Comm<strong>and</strong> output resembles the following example.<strong>Brocade</strong># debug cfm 1CFM: debug level is 1Dec 10 17:36:35 CFM: receive packet :rx_l2_bpdu 12Dec 10 17:36:35 CFM: receive packet :rx_l2_bpdu 12Dec 10 17:36:36 CFM: receive packet :rx_l2_bpdu 12Dec 10 17:36:36 CFM: receive packet :rx_l2_bpdu 17Dec 10 17:36:36 CFM: receive packet :rx_l2_bpdu 12Dec 10 17:36:36 CFM: receive packet :rx_l2_bpdu 12Dec 10 17:36:36 CFM: receive packet :rx_l2_bpdu 12<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> 6953-1002426-02

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

Saved successfully!

Ooh no, something went wrong!