Other AToM Troubleshooting Commands
This section contains other commands and more information that may be useful when troubleshooting AToM.
show mpls l2transport vc vcid detail
The show mpls l2transport vc vcid detail command displays detailed information about AToM VCs.
Example 7-102 shows the output from this command for VC ID 123.
Example 7-102. show mpls l2transport vc vcid detail Command Output
London_PE#show mpls l2transport vc 123 detail Local interface: Se4/0 up, line protocol up, FR DLCI 50 up Destination address: 172.16.1.4, VC ID: 123, VC status: up Tunnel label: 22, next hop 172.16.2.2 Output interface: Fa2/0, imposed label stack {22 26} Create time: 00:50:50, last status change time: 00:00:47 Signaling protocol: LDP, peer 172.16.1.4:0 up MPLS VC labels: local 29, remote 26 Group ID: local 5, remote 6 MTU: local 1500, remote 1500 Remote interface description: Sequencing: receive disabled, send disabled VC statistics: packet totals: receive 6, send 56 byte totals: receive 596, send 3168 packet drops: receive 0, send 0 London_PE# |
Highlighted line 1 shows that the local interface state is up and the line protocol is up. The local circuit (Frame Relay DLCI 50) is also in an up state.
The destination address (172.16.1.4, the peer PE router), together with the VC ID (123) and VC status (up), are shown in highlighted line 2.
In highlighted line 3, you can see the tunnel label (22), as well as the address of the next-hop LSR (172.16.1.2) in the path to the PE router.
Highlighted line 4 shows the outbound (core) interface for the tunnel LSP (fast Ethernet 2/0), together with the label stack imposed on tunneled Layer 2 PDUs. In this case, the label stack is 22, 26. Label 22 is the tunnel label, and 26 is the VC label.
The time when the circuit was created (00:50:50) and the time since the circuit state last changed (00:00:47) are shown in highlighted line 5.
In highlighted line 6, you can see the signaling protocol (LDP), together with the peer PE router LDP ID (172.16.1.4:0), and status (up). Highlighted line 7 shows local (29) and remote (26) VC labels for the circuit. Local (5) and remote (6) group IDs are shown in highlighted line 8.
Highlighted line 9 shows local and remote MTUs (both 1500). In highlighted line 10, you can see that send and receive sequencing for pseudowire packets is disabled. Finally, highlighted lines 11 to 13 show the number of receive and send packets, bytes, and packet drops.
show mpls l2transport hw-capability interface interface_name
This command displays the supported transport types and associated functionality on PE router interfaces.
Example 7-103 shows the output from the show mpls l2transport hw-capability interface interface_name command. Note that only a portion of the output is shown.
Example 7-103. show mpls l2transport hw-capability interface interface_name Command Output
London_PE#show mpls l2transport hw-capability interface atm 3/0
Interface ATM3/0
Transport type FR DLCI
Core functionality:
MPLS label disposition supported
Control word processing supported
Sequence number processing not supported
Edge functionality:
Not supported
Transport type ATM AAL5
Core functionality:
MPLS label disposition supported
Control word processing supported
Sequence number processing not supported
Edge functionality:
MPLS label imposition supported
Control word processing supported
Sequence number processing not supported
ATM AAL5 forwarding supported
F5 OAM cell forwarding supported
CLP bit setting supported
CLP bit detecting supported
EFCI bit setting supported
EFCI bit detecting supported
|
In Example 7-103, you can see the core and edge functionality supported for Frame Relay DLCI and ATM AAL5 transport types. Core functionality includes MPLS label disposition, control word processing, and sequencing. Edge functionality includes MPLS label imposition, control word processing, and sequence number processing.
In this example, you can also see that ATM AAL5 forwarding, F5 Operations, Administration, and Maintenance (OAM) cell forwarding, cell loss priority (CLP) bit setting and detecting, as well as Explicit Forward Congestion Indication (EFCI) bit setting and detecting are supported for ATM AAL5.
show mpls l2transport summary
The show mpls l2transport summary command can be used to display summary information about AToM virtual circuits.
Example 7-104 shows the output from this command.
Example 7-104. show mpls l2transport summary Command Output
show mpls l2transport summary Destination address: 172.16.1.4, total number of vc: 4 0 unknown, 3 up, 1 down, 0 admin down 3 active vc on MPLS interface Fa2/0 London_PE# |
Highlighted line 1 shows the destination address (172.16.1.4, the peer PE router) and the total number of VCs (4).
In highlighted line 2, you can see the number of VCs in an unknown state (0), the number in an up state (3), the number in a down state (1), and the number in an administratively down state (0).
Then in highlighted line 3, you can see that the number of VCs that are active (3) on core interfaces (here, interface fast Ethernet 2/0).
show mpls l2transport binding
The show mpls l2transport binding command displays VC label bindings, as shown in Example 7-105.
Example 7-105. Verifying VC Label Bindings
London_PE#show mpls l2transport binding Destination Address: 172.16.1.4, VC ID: 121 Local Label: 16 Cbit: 1, VC Type: Eth VLAN, GroupID: 2 MTU: 1500, Interface Desc: n/a Remote Label: 17 Cbit: 1, VC Type: Eth VLAN, GroupID: 1 MTU: 1500, Interface Desc: n/a Destination Address: 172.16.1.4, VC ID: 123 Local Label: 27 Cbit: 1, VC Type: FR DLCI, GroupID: 5 MTU: 1500, Interface Desc: n/a Remote Label: 26 Cbit: 1, VC Type: FR DLCI, GroupID: 6 MTU: 1500, Interface Desc: n/a Destination Address: 172.16.1.4, VC ID: 124 Local Label: 30 Cbit: 1, VC Type: HDLC, GroupID: 6 MTU: 1500, Interface Desc: n/a Remote Label: 25 Cbit: 1, VC Type: HDLC, GroupID: 8 MTU: 1500, Interface Desc: n/a London_PE# |
Highlighted line 1 shows the VC ID (123), as well as the associated destination PE router address (172.16.1.4).
The local VC label (27), together with the C (control word) bit setting (1), VC type (Frame Relay DLCI-to-DLCI connection), group ID (5), and MTU (1500) are shown in highlighted lines 1 to 4.
The corresponding remote VC label (26), as well as C bit setting (1), VC type (DLCI-to-DLCI connection), group ID (6), and MTU (1500) are shown in highlighted lines 5 to 7.
debug mpls l2transport signaling [event | fsm | message]
The debug mpls l2transport signaling command displays signaling protocol (LDP) information for AToM, as demonstrated in Example 7-106.
Example 7-106. debug mpls l2transport signaling message Command Output
London_PE#debug mpls l2transport signaling message AToM LDP message debugging is on London_PE# *Apr 19 19:01:54.183 UTC: AToM LDP [172.16.1.4]: Received label mapping msg, id 29 vc type 1, cbit 1, vc id 123, group id 6, vc label 24, status 0, mtu 1500 *Apr 19 19:01:55.183 UTC: AToM LDP [172.16.1.4]: Received label withdraw msg, id 30 vc type 1, cbit 1, vc id 123, group id 6, vc label 24, status 0, mtu 0 *Apr 19 19:02:05.187 UTC: AToM LDP [172.16.1.4]: Received label mapping msg, id 32 vc type 1, cbit 1, vc id 123, group id 6, vc label 25, status 0, mtu 1500 *Apr 19 19:02:06.415 UTC: AToM LDP [172.16.1.4]: Sending label mapping msg vc type 1, cbit 1, vc id 123, group id 5, vc label 25, status 0, mtu 1500 *Apr 19 19:02:07.415 UTC: AToM LDP [172.16.1.4]: Sending label withdraw msg vc type 1, cbit 1, vc id 123, group id 5, vc label 25, status 0, mtu 1500 *Apr 19 19:02:17.423 UTC: AToM LDP [172.16.1.4]: Sending label mapping msg vc type 1, cbit 1, vc id 123, group id 5, vc label 26, status 0, mtu 1500 London_PE# |
In highlighted line 1, you can see London_PE has received a label mapping message from peer PE router 172.16.1.4. Information contained in the message includes VC type (1), the C (control word) bit setting, the VC ID (123), the group ID (6), the VC label (24), the status (0), and the MTU (1500).
Highlighted line 2 shows that a label withdraw message has been received. London_PE sends a label mapping message to peer PE router 172.16.1.4 in highlighted line 3. London_PE sends a label withdraw message in highlighted line 4.
debug mpls l2transport packet {data | error}
The debug mpls l2transport packet {data | error} command displays information about packets switched over AToM pseudowires, as demonstrated in Example 7-107.
Example 7-107. debug mpls l2transport packet data Command Output
London_PE#debug mpls l2transport packet data AToM packet data debugging is on London_PE# *Apr 19 19:05:48.147 UTC: ATOM-FR DLCI imposition: in Se4/0, out Fa2/0, circuit id 50, size 32, EXP 0x0, seq 0, control word 0x220000 *Apr 19 19:05:48.147 UTC: 00 00 08 00 45 C0 00 1C 10 1D 00 00 01 02 BC DA *Apr 19 19:05:48.147 UTC: 0A 01 01 01 E0 00 01 27 16 00 08 D8 E0 00 01 27 *Apr 19 19:05:49.147 UTC: ATOM-FR DLCI imposition: in Se4/0, out Fa2/0, circuit id 50, size 32, EXP 0x0, seq 0, control word 0x220000 *Apr 19 19:05:49.147 UTC: 00 00 08 00 45 C0 00 1C 10 1E 00 00 01 02 BC D8 *Apr 19 19:05:49.147 UTC: 0A 01 01 01 E0 00 01 28 16 00 08 D7 E0 00 01 28 London_PE# |
Highlighted line 1 shows a Frame Relay PDU (without the header or FCS) being switched from interface serial 4/0 out over the AToM pseudowire out of core interface fast Ethernet 2/0. Other information shown includes the circuit ID (50), the Experimental (EXP) bits setting (0x0), the sequence number (0), and the control word (0x22000).
CAUTION
Exercise extra caution when using this command because it can produce copious output.
debug frame-relay events
The debug frame-relay events command displays information about the Frame Relay Address Resolution Protocol (ARP), as well as circuit status events.
Example 7-108 demonstrates sample output from this command.
Example 7-108. debug frame-relay events Command Output
London_PE#debug frame-relay events Frame Relay events debugging is on London_PE# *Apr 19 18:42:04.679 UTC: FRoMPLS [172.16.1.4, 123]: Local up, sending acmgr_circuit_up *Apr 19 18:42:04.679 UTC: FRoMPLS [172.16.1.4, 123]: PW pvc_status set ACTIVE *Apr 19 18:42:04.679 UTC: FRoMPLS [172.16.1.4, 123]: Setting pw segment UP *Apr 19 18:42:04.679 UTC: FRoMPLS [172.16.1.4, 123]: PW nni_pvc_status set ACTIVE *Apr 19 18:42:05.679 UTC: FRoMPLS [172.16.1.4, 123]: acmgr_circuit_down *Apr 19 18:42:05.679 UTC: FRoMPLS [172.16.1.4, 123]: PW pvc_status set INACTIVE *Apr 19 18:42:15.683 UTC: FRoMPLS [172.16.1.4, 123]: Local up, sending acmgr_circuit_up *Apr 19 18:42:15.683 UTC: FRoMPLS [172.16.1.4, 123]: PW nni_pvc_status set ACTIVE *Apr 19 18:42:15.683 UTC: FRoMPLS [172.16.1.4, 123]: PW pvc_status set ACTIVE *Apr 19 18:42:15.683 UTC: FRoMPLS [172.16.1.4, 123]: Setting pw segment UP *Apr 19 18:42:15.683 UTC: FRoMPLS [172.16.1.4, 123]: Setting connection UP London_PE# |
In highlighted line 1, the pseudowire PVC status changes to active. Then in highlighted line 2, the pseudowire NNI PVC status changes to active.
debug acircuit [error | event]
The debug acircuit [error | event] command displays attachment circuit error and event information such as provisioning events, circuit up/down events, and setup/configuration failures.
Example 7-109 demonstrates sample output from the debug acircuit event command.
Example 7-109. debug acircuit event Command Output
London_PE#debug acircuit event
Attachment Circuit events debugging is on
London_PE#
*Apr 19 19:14:03.031 UTC: ACMGR: Receive <Circuit Up> msg
*Apr 19 19:14:03.031 UTC: Se4/0 ACMGR: circuit up event, SIP state chg down to
connecting, action is service request
*Apr 19 19:14:03.031 UTC: Se4/0 ACMGR: Sent a sip service request
*Apr 19 19:14:03.035 UTC: Se4/0 ACMGR: Rcv SIP msg: resp connect forwarded, hdl
14000008, l2ss_hdl E5000009
*Apr 19 19:14:03.035 UTC: Se4/0 ACMGR: service connected event, SIP state chg
connecting to connected, action is respond forwarded
*Apr 19 19:14:03.035 UTC: Se4/0 ACMGR: Rcv SIP msg: resp remote up notification, hdl
14000008, l2ss_hdl E5000009
*Apr 19 19:14:03.035 UTC: Se4/0 ACMGR: remote up event, SIP connected state no chg,
action is ignore
*Apr 19 19:14:04.031 UTC: Se4/0 ACMGR: Receive <Circuit Down> msg
*Apr 19 19:14:04.031 UTC: Se4/0 ACMGR: circuit down event, SIP state chg connected to
end, action is service disconnect
*Apr 19 19:14:04.031 UTC: Se4/0 ACMGR: Sent a sip service disconnect
*Apr 19 19:14:14.039 UTC: ACMGR: Receive <Circuit Up> msg
*Apr 19 19:14:14.039 UTC: Se4/0 ACMGR: circuit up event, SIP state chg down to
connecting, action is service request
*Apr 19 19:14:14.039 UTC: Se4/0 ACMGR: Sent a sip service request
*Apr 19 19:14:14.039 UTC: Se4/0 ACMGR: Rcv SIP msg: resp connect forwarded, hdl
9100000A, l2ss_hdl A800000B
*Apr 19 19:14:14.039 UTC: Se4/0 ACMGR: service connected event, SIP state chg
connecting to connected, action is respond forwarded
*Apr 19 19:14:14.039 UTC: Se4/0 ACMGR: Rcv SIP msg: resp remote up notification, hdl
9100000A, l2ss_hdl A800000B
*Apr 19 19:14:14.039 UTC: Se4/0 ACMGR: remote up event, SIP connected state no chg,
action is ignore
London_PE#
|