Table Of Contents
debug mpls l2transport signaling
encapsulation (Any Transport over MPLS)
show mpls l2transport hw-capability
MPLS AToM — Commands
This document contains new and revised commands for the MPLS AToM. All other commands used with MPLS AToM are documented in the Cisco IOS Release 12.2 command reference publications.
The following sections are included in this document:
Documentation Specifics
This documentation set includes the following sections:
•
Start Here: MPLS AToM: Transport, Platform, and Release Specifics
•
•
•
Note
The other chapters provide overview, configuration, and command reference information for MPLS AToM features.
New and Revised Commands
•
•
•
•
•
•
•
connect (Frame Relay)
To define connections between Frame Relay permanent virtual circuits (PVCs), use the connect command in global configuration mode. To remove connections, use the no form of this command.
connect connection-name interface dlci {interface dlci | l2transport}
no connect connection-name interface dlci {interface dlci | l2transport}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.1(2)T
This command was introduced.
12.0(23)S
This command was updated with the l2transport keyword.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
When frame Relay switching is enabled, the connect command creates switched PVCs in Frame Relay networks.
Examples
The following example shows how to enable Frame Relay switching and define a connection called frompls1 with a DLCI 100 on serial interface 5/0.
PE1_router(config)# connect frompls1 Serial5/0 1000 l2transportRelated Commands
frame-relay switching
Enables PVC switching on a Frame Relay DCE or NNI.
mpls l2transport route
Enables routing of Frame Relay packets over a specified VC.
debug acircuit
To display errors and events that occur on the attachment circuits (the circuits between the provider edge (PE) and customer edge (CE) routers), use the debug acircuit command in privileged EXEC mode. To disable this debugging output, use the no form of this command.
debug acircuit {error | event}
no debug acircuit {error | event}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
An attachment circuit connects a PE router to a CE router. A router can have many attachment circuits. The attachment circuit manager controls all the attachment circuits from one central location. Therefore, when you enable the debug messages for the attachment circuit, you receive information about all the attachment circuits.
Examples
The following is sample output from the debug acircuit event command when you enable an interface:
Router# debug acircuit event*Jan 28 15:19:03.070: ACLIB: ac_cstate() Handling circuit UP for interface Se2/0*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: pthru_intf_handle_circuit_up() calling acmgr_circuit_up*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Connecting*Jan 28 15:19:03.070: ACMGR: Receive <Circuit Up> msg*Jan 28 15:19:03.070: Se2/0 ACMGR: circuit up event, SIP state chg down to connecting, action is service request*Jan 28 15:19:03.070: Se2/0 ACMGR: Sent a sip service request*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: AC updating switch context.*Jan 28 15:19:03.070: Se2/0 ACMGR: Rcv SIP msg: resp connect forwarded, hdl 9500001D, l2ss_hdl 700001E*Jan 28 15:19:03.070: Se2/0 ACMGR: service connected event, SIP state chg connecting to connected, action is respond forwarded*Jan 28 15:19:03.070: ACLIB: pthru_intf_response hdl is 9500001D, response is 1*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-ConnectedThe following is sample output from the debug acircuit event command when you disable an interface:
Router# debug acircuit event*Jan 28 15:25:57.014: ACLIB: SW AC interface INTF-DOWN for interface Se2/0*Jan 28 15:25:57.014: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Idle*Jan 28 15:25:57.014: ACLIB: SW AC interface INTF-DOWN for interface Se2/0*Jan 28 15:25:57.014: Se2/0 ACMGR: Receive <Circuit Down> msg*Jan 28 15:25:57.014: Se2/0 ACMGR: circuit down event, SIP state chg connected to end, action is service disconnect*Jan 28 15:25:57.014: Se2/0 ACMGR: Sent a sip service disconnect*Jan 28 15:25:57.014: ACLIB [11.0.1.1, 200]: AC deleting switch context.*Jan 28 15:25:59.014: %LINK-5-CHANGED: Interface Serial2/0, changed state to administratively down*Jan 28 15:25:59.014: ACLIB: ac_cstate() Handling circuit DOWN for interface Se2/0*Jan 28 15:26:00.014:%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to downdebug condition
To limit output for some debugging commands based on specified conditions, use the debug condition command in privileged EXEC mode. To removed the specified condition, use the no form of this command.
debug condition {username username | called dial-string | caller dial-string | vcid vc-id | ip ip-address}
no debug condition {condition-id | all}
Syntax Description
Command Modes
Privileged EXEC
Command History
Defaults
All debugging messages for enabled protocol-specific debug commands are generated.
Usage Guidelines
Use the debug condition command to restrict the debug output for some commands. If any debug condition commands are enabled, output is only generated for interfaces associated with the specified keyword. In addition, this command enables debugging output for conditional debugging events. Messages are displayed as different interfaces meet specific conditions.
If multiple debug condition commands are enabled, output is displayed if at least one condition matches. All the conditions do not need to match.
The no form of this command removes the debug condition specified by the condition identifier. The condition identifier is displayed after you use a debug condition command or in the output of the show debug condition command. If the last condition is removed, debugging output resumes for all interfaces. You will be asked for confirmation before removing the last condition or all conditions.
Not all debugging output is affected by the debug condition command. Some commands generate output whenever they are enabled, regardless of whether they meet any conditions. The commands that are affected by the debug condition commands are generally related to dial access functions, where a large amount of output is expected. Output from the following commands is controlled by the debug condition command:
•
•
•
•
•
Examples
Example 1
In the following example, the router displays debugging messages only for interfaces that use a username of fred. The condition identifier displayed after the command is entered identifies this particular condition.
Router# debug condition username fredCondition 1 setExample 2
The following example specifies that the router should display debugging messages only for VC 1000:
Router# debug condition vcid 1000Condition 1 set01:12:32: 1000 Debug: Condition 1, vcid 1000 triggered, count 101:12:32: 1000 Debug: Condition 1, vcid 1000 triggered, count 1Other debugging commands are enabled, but they will only display debugging for VC 1000.
Router# debug mpls l2transport vc eventAToM vc event debugging is onRouter# debug mpls l2transport vc fsmAToM vc fsm debugging is onThe following commands shut down the interface where VC 1000 is established.
Router(config)# interface s3/1/0Router(config-if)# shutThe debugging output shows the change to the interface where VC 1000 is established.
01:15:59: AToM MGR [13.13.13.13, 1000]: Event local down, state changed from established to remote ready01:15:59: AToM MGR [13.13.13.13, 1000]: Local end down, vc is down01:15:59: AToM SMGR [13.13.13.13, 1000]: Processing imposition update, vc_handle 6227BCF0, update_action 0, remote_vc_label 1801:15:59: AToM SMGR [13.13.13.13, 1000]: Imposition Disabled01:15:59: AToM SMGR [13.13.13.13, 1000]: Processing disposition update, vc_handle 6227BCF0, update_action 0, local_vc_label 75501:16:01:%LINK-5-CHANGED: Interface Serial3/1/0, changed state to administratively down01:16:02:%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1/0, changed state to downRelated Commands
debug condition interface
Limits output for some debugging commands based on the interfaces.
debug frame-relay events
To display debugging information about Frame Relay Address Resolution Protocol (ARP) replies on networks that support a multicast channel and use dynamic addressing, use the debug frame-relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug frame-relay events
no debug frame-relay events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful for identifying the cause of end-to-end connection problems during the installation of a Frame Relay network or node.
Note
Examples
The following is sample output from the debug frame-relay events command:
Router# debug frame-relay eventsSerial2(i): reply rcvd 172.16.170.26 126Serial2(i): reply rcvd 172.16.170.28 128Serial2(i): reply rcvd 172.16.170.34 134Serial2(i): reply rcvd 172.16.170.38 144Serial2(i): reply rcvd 172.16.170.41 228Serial2(i): reply rcvd 172.16.170.65 325As the output shows, the debug frame-relay events command returns one specific message type. The first line, for example, indicates that IP address 172.16.170.26 sent a Frame Relay ARP reply; this packet was received as input on serial interface 2. The last field (126) is the data-link connection identifier (DLCI) to use when communicating with the responding router.
For Frame Relay over MPLS, the following is sample output for the debug frame-relay events command. The command output shows the status of the VCs.
Router# debug frame-relay eventsFrame Relay events debugging is onThis example shows the messages that are displayed when you shut the core-facing interface on a PE router:
04:40:38:%SYS-5-CONFIG_I: Configured from console by consolenf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface hssi2/0Router(config-if)# shut04:40:43:%OSPF-5-ADJCHG: Process 10, Nbr 12.12.12.12 on Hssi2/0 from FULL to DOWN, Neighbor Down: Interface down or detached04:40:43: FRoMPLS [12.12.12.12, 100]: PW pvc_status set INACTIVE04:40:43: FRoMPLS [12.12.12.12, 100]: Setting pw segment DOWN04:40:43: FRoMPLS [12.12.12.12, 100]: Setting connection DOWN04:40:43: FRoMPLS [12.12.12.12, 101]: PW pvc_status set INACTIVE04:40:43: FRoMPLS [12.12.12.12, 101]: Setting pw segment DOWN04:40:43: FRoMPLS [12.12.12.12, 101]: Setting connection DOWN04:40:45:%LINK-5-CHANGED: Interface Hssi2/0, changed state to administratively down04:40:46:%LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi2/0, changed state to downThis example shows the messages that are displayed when you enable the core-facing interface on a PE router:
Router(config-if)# no shut04:40:56:%LINK-3-UPDOWN: Interface Hssi2/0, changed state to up04:40:57:%LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi2/0, changed state to up04:41:06:%OSPF-5-ADJCHG: Process 10, Nbr 12.12.12.12 on Hssi2/0 from LOADING to FULL, Loading Done04:41:19: FRoMPLS [12.12.12.12, 100]: PW pvc_status set ACTIVE04:41:19: FRoMPLS [12.12.12.12, 100]: Setting pw segment UP04:41:19: FRoMPLS [12.12.12.12, 101]: PW pvc_status set ACTIVE04:41:19: FRoMPLS [12.12.12.12, 101]: Setting pw segment UPThis example shows the messages that are displayed when you shut the edge-facing interface on a PE router:
Router(config)# interface pos4/0Router(config-if)# shut04:42:50: FRoMPLS [12.12.12.12, 100]: acmgr_circuit_down04:42:50: FRoMPLS [12.12.12.12, 100]: Setting connection DOWN04:42:50: FRoMPLS [12.12.12.12, 100]: PW pvc_status set INACTIVE04:42:52:%LINK-5-CHANGED: Interface POS4/0, changed state to administratively down04:42:53:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS4/0, changed state to downThis example shows the messages that are displayed when you enable the edge-facing interface on a PE router:
Router(config)# interface pos4/0Router(config-if)# no shut04:43:20:%LINK-3-UPDOWN: Interface POS4/0, changed state to upc72-33-2(config-if)#04:43:20: FRoMPLS [12.12.12.12, 100]: Local up, sending acmgr_circuit_up04:43:20: FRoMPLS [12.12.12.12, 100]: PW nni_pvc_status set ACTIVE04:43:20: FRoMPLS [12.12.12.12, 100]: PW pvc_status set ACTIVE04:43:20: FRoMPLS [12.12.12.12, 100]: Setting pw segment UPdebug mpls l2transport ipc
To display the interprocessor communication (IPC) messages exchanged between distributed platforms, such as the Cisco 12000 series router and the Cisco 7500 series routers, use the debug mpls l2transport ipc command in privileged EXEC mode. To disable this debugging output, use the no form of this command.
debug mpls l2transport ipc
no debug mpls l2transport ipc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
You can issue this command either from the line card or the route processor to log AToM updates to or from line cards. This command applies only to platforms that support distributed mode.
Examples
The following is sample output from the debug mpls l2transport ipc command:
Router# debug mpls l2transport ipcAToM ipc debugging is on*May 27 23:56:04.699 UTC: AToM SMGR: Repopulating line card 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1101]: Sending Imposition update to slot 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1101]: Imposition being done on ingress interface*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1101]: Sending disposition update to slot 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1101]: Distributing disposition info to all linecards*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 701]: Sending Imposition update to slot 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 701]: Imposition being done on ingress interface*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 701]: Sending disposition update to slot 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 701]: Distributing disposition info to all linecards*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1201]: Sending Imposition update to slot 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1201]: Imposition being done on ingress interface*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1201]: Sending disposition update to slot 255*May 27 23:56:04.699 UTC: AToM SMGR [17.17.17.17, 1201]: Distributing disposition info to all linecardsdebug mpls l2transport packet
To display information about the status of Any Transport over MPLS (ATOM) switched packets, use the debug mpls l2transport packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls l2transport packet {data |error}
no debug mpls l2transport packet {data | error}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
Use this command sparingly, because the command output can be overwhelming.
For platforms that support distributed switching, the command displays output only for packets switched by the central route processor module. Packets switched autonomously by the linecards are not displayed. For example, packets switched by Versatile Interface Processors (VIPs) on the Cisco 7500 router are not displayed.
Examples
The following is sample output from the debug mpls l2transport packet commands for a PPP over MPLS configuration:
Router# debug mpls l2transport packet dataAToM packet data debugging is onRouter# debug mpls l2transport packet errorAToM packet errors debugging is onRouter# show debugAToM:AToM packet data debugging is onAToM packet errors debugging is on*Mar 24 23:29:30.495: ATOM-PPP Switching: check features failed.*Mar 24 23:29:30.495: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:30.495: 0F 00 88 47 00 01 10 FF 00 01 51 02 00 00 00 00*Mar 24 23:29:30.495: 00 FD C0 01 01 01 C0 4B 41 73 F4 00 01 00 02 CC*Mar 24 23:29:30.495: 66 51 88 B4 CE 73 39 00 00 40 00 88 03 02 00 70*Mar 24 23:29:30.495: 23 30 00 04 3C 61 83 C0 00 06 00 06 94 CC A7 23*Mar 24 23:29:30.495: 49 84 D8 33 17 8C F2 60 00 11 9E 80 00 50 08 08*Mar 24 23:29:30.495: 86 69 39 98 CD E2 02 49 B8 E9 9D 0D C6 53 A1 DC*Mar 24 23:29:30.495: DE 72 35 88 09 E7 0C 60 61 3A 1A 4D C6 71 01 4C*Mar 24 23:29:30.495: F2 73 CC 06 DC 38 6F 33 66 83 09 C8 CA 20 05 12*Mar 24 23:29:30.495: 49 E5 31 00 A0 E8 6D 14 88 06 E3 21 80 C3 31 E4*Mar 24 23:29:30.495: 28 21 E4 21 69 28 A6 2D 26 8A 45 82 02 B6 FC 39*Mar 24 23:29:30.499: D8 60 A3 62 B1 60 A5 80*Mar 24 23:29:31.835: ATOM-L2 Switching Disposition Packet data:*Mar 24 23:29:31.835: FF 03 00 FD C0 04 8A 57 FF FF FF FF FF FF FF FF*Mar 24 23:29:31.835: FF FF FB 14 B0 00*Mar 24 23:29:49.423: ATOM-L2 Switching Disposition Packet data:*Mar 24 23:29:49.423: FF 03 C0 21 01 11 00 0F 03 05 C2 23 05 05 06 5F*Mar 24 23:29:49.423: 23 35 D4*Mar 24 23:29:49.435: ATOM-PPP Switching: check features failed.*Mar 24 23:29:49.435: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:49.435: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 15 00 00*Mar 24 23:29:49.435: C0 21 01 2F 00 0F 03 05 C2 23 05 05 06 5F CC 5F*Mar 24 23:29:49.435: E5*Mar 24 23:29:49.435: ATOM-PPP Switching: check features failed.*Mar 24 23:29:49.435: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:49.435: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 15 00 00*Mar 24 23:29:49.435: C0 21 02 11 00 0F 03 05 C2 23 05 05 06 5F 23 35*Mar 24 23:29:49.435: D4*Mar 24 23:29:49.443: ATOM-L2 Switching Disposition Packet data:*Mar 24 23:29:49.443: FF 03 C0 21 02 2F 00 0F 03 05 C2 23 05 05 06 5F*Mar 24 23:29:49.443: CC 5F E5*Mar 24 23:29:49.447: ATOM-L2 Switching Disposition Packet data:*Mar 24 23:29:49.447: FF 03 C2 23 01 D0 00 1C 10 45 59 13 1A 92 FD 93*Mar 24 23:29:49.447: 01 A2 CF B6 FB 3A 04 46 93 63 65 32 2D 67 73 72*Mar 24 23:29:49.451: ATOM-PPP Switching: check features failed.*Mar 24 23:29:49.451: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:49.451: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 22 00 00*Mar 24 23:29:49.451: C2 23 01 F5 00 1C 10 F1 98 35 3F 79 F2 1A 15 10*Mar 24 23:29:49.451: B4 C0 73 D7 B1 9F 2A 63 65 31 2D 67 73 72*Mar 24 23:29:49.455: ATOM-PPP Switching: check features failed.*Mar 24 23:29:49.455: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:49.455: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 22 00 00*Mar 24 23:29:49.455: C2 23 02 D0 00 1C 10 56 4A 32 5B 99 55 D5 CF 44*Mar 24 23:29:49.455: FC D3 D9 3F CC 8C A8 63 65 31 2D 67 73 72*Mar 24 23:29:49.463: ATOM-L2 Switching Disposition Packet data:*Mar 24 23:29:49.463: FF 03 C2 23 02 F5 00 1C 10 45 84 E4 E5 DD C0 5F*Mar 24 23:29:49.463: FD 2F 37 63 9A 3D 03 7B B9 63 65 32 2D 67 73 72*Mar 24 23:29:49.463: ATOM-L2 Switching Disposition Packet data:*Mar 24 23:29:49.463: FF 03 C2 23 03 D0 00 04*Mar 24 23:29:49.471: ATOM-PPP Switching: check features failed.*Mar 24 23:29:49.471: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:49.471: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 0A 00 00*Mar 24 23:29:49.471: C2 23 03 F5 00 04*Mar 24 23:29:49.471: ATOM-PPP Switching: check features failed.*Mar 24 23:29:49.471: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits are 0*Mar 24 23:29:49.471: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 10 00 00*Mar 24 23:29:49.471: 80 21 01 0B 00 0A 03 06 78 01 01 78*Mar 24 23:29:49.475: ATOM-PPP Switching: check features failed.debug mpls l2transport signaling
To display information about the Any Transport over MPLS (AToM) signaling protocol, use the debug mpls l2transport signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls l2transport signaling {event | message}
no debug mpls l2transport signaling {event | message}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Examples
The following is sample output from the debug mpls l2transport signaling command:
Router# debug mpls l2transport signaling eventAToM LDP event debugging is onRouter# debug mpls l2transport signaling messageAToM LDP message debugging is onRouter# show debuggingAToM:AToM LDP event debugging is onAToM LDP message debugging is on*Mar 24 23:10:55.611: AToM LDP [9.9.9.9]: Allocate LDP instance*Mar 24 23:10:55.611: AToM LDP [9.9.9.9]: Opening session, 1 clients*Mar 24 23:10:56.063: %SYS-5-CONFIG_I: Configured from console by console*Mar 24 23:10:56.583: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0, changed state to up*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Session is up*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Peer address change, add 1.1.1.100*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Peer address change, add 46.1.1.6*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Peer address change, add 9.9.9.9*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Peer address change, add 57.1.1.6*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Sending label mapping msgvc type 7, cbit 1, vc id 50, group id 6, vc label 21, status 0, mtu 1500*Mar 24 23:11:00.539: AToM LDP [9.9.9.9]: Received label mapping msg, id 113vc type 7, cbit 1, vc id 50, group id 6, vc label 21, status 0, mtu 1500debug mpls l2transport vc
To display information about the status of the AToM VCs, use the debug mpls l2transport vc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls l2transport vc {event | fsm}
no debug mpls l2transport vc {event | fsm}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
You can issue this command from the line card or route processor.
Examples
The following is sample output from the debug mpls l2transport vc commands:
Router# debug mpls l2transport vc eventAToM vc event debugging is onRouter# debug mpls l2transport vc fsmAToM vc fsm debugging is onRouter# show debuggingAToM:AToM vc event debugging is onAToM vc fsm debugging is on*Mar 24 23:17:24.371: AToM MGR [9.9.9.9, 50]: Event provision, state changed from idle to provisioned*Mar 24 23:17:24.371: AToM MGR [9.9.9.9, 50]: Provision vc*Mar 24 23:17:24.371: AToM SMGR [9.9.9.9, 50]: Requesting VC create, vc_handle 61A09930*Mar 24 23:17:24.371: AToM MGR [9.9.9.9, 50]: Event local up, state changed from provisioned to local standby*Mar 24 23:17:24.371: AToM MGR [9.9.9.9, 50]: Update local vc label binding*Mar 24 23:17:24.371: AToM SMGR [9.9.9.9, 50]: sucessfully processed create request*Mar 24 23:17:24.875: %SYS-5-CONFIG_I: Configured from console by console*Mar 24 23:17:25.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0, changed state to up*Mar 24 23:17:28.567: AToM MGR [9.9.9.9, 50]: Event ldp up, state changed from local standby to local ready*Mar 24 23:17:28.567: AToM MGR [9.9.9.9, 50]: Advertise local vc label binding*Mar 24 23:17:28.567: AToM MGR [9.9.9.9, 50]: Event remote up, state changed from local ready to establishing*Mar 24 23:17:28.567: AToM MGR [9.9.9.9, 50]: Remote end up*Mar 24 23:17:28.567: AToM MGR [9.9.9.9, 50]: Event remote validated, state changed from establishing to established*Mar 24 23:17:28.567: AToM MGR [9.9.9.9, 50]: Validate vc, activating data plane*Mar 24 23:17:28.567: AToM SMGR [9.9.9.9, 50]: Processing imposition update, vc_handle 61A09930, update_action 3, remote_vc_label 21*Mar 24 23:17:28.567: AToM SMGR [9.9.9.9, 50]: Imposition Programmed, Output Interface: PO5/0*Mar 24 23:17:28.567: AToM SMGR [9.9.9.9, 50]: Processing disposition update, vc_handle 61A09930, update_action 3, local_vc_label 22*Mar 24 23:17:28.571: AToM SMGR: Processing TFIB event for 9.9.9.9*Mar 24 23:17:28.571: AToM SMGR [9.9.9.9, 50]: Imposition Programmed, Output Interface: PO5/0encapsulation (Any Transport over MPLS)
To configure the ATM adaptation layer (AAL) for an Any Transport over MPLS (AToM) ATM permanent virtual circuit (PVC), use the encapsulation command in AToM-VC configuration mode. To remove an encapsulation from an AToM PVC, use the no form of this command.
encapsulation layer-type
no encapsulation layer-type
Syntax Description
layer-type
The adaptation layer type. Possible values are:
aal5—ATM adaptation layer 5
aal0—ATM adaptation layer 0
Defaults
The default encapsulation is AAL5.
Command Modes
AToM VC configuration
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
The pvc command and the encapsulation command work together. How you use the commands for AToM is slightly different than for all other applications. The following table shows the differences in how the commands are used:
The following list highlights the differences:
•
•
•
When you use the aal5 keyword, incoming cells (except OAM cells) on that PVC are treated as AAL5 encapsulated packets. The router reassembles the packet from the incoming cells. The router does not check the contents of the packet, so it does not need to know the encapsulation type (such as aal5snap, aal5mux, and so on). After imposing the MPLS label stack, the router sends the reassembled packet over the MPLS core network.
When you use the aal0 keyword, the router strips the header error control (HEC) byte from the cell header and adds the MPLS label stack. The router sends the cell over the MPLS core network.
Examples
The following example shows how to configure a PVC to transport AAL5 packets for AToM:
pvc 1/100 l2transportencapsulation aal0Related Commands
pvc
Creates or assigns a name to an ATM PVC.
Configures AAL encapsulation type for an ATM PVC.
mpls l2transport route
To enable routing of Any Transport over MPLS (AToM) packets over a specified virtual circuit (VC), use the mpls l2transport route command in the appropriate command mode. To delete the VC, use the no form of this command on both routers.
mpls l2transport route destination vc-id
no mpls l2transport route destination vc-id
Syntax Description
destination
Specifies the Label Distribution Protocol (LDP) IP address of the remote provider edge (PE) router.
vc-id
Assigns a VC ID to the virtual circuit between two PE routers.
Defaults
No default behavior or values.
Command Modes
Depending on the AToM transport type you are configuring, you use the mpls l2transport route command in one of the following command modes:
ATM AAL5 and Cell Relay
ATM VC configuration mode
Ethernet VLAN
Subinterface configuration mode
Frame Relay
Connect submode
HDLC and PPP
Interface configuration mode
Command History
Usage Guidelines
An MPLS VC runs across an MPLS cloud to connect interfaces on two provider edge (PE) routers.
Use this command on each PE router to route packets across the MPLS cloud to the interface of the other PE router. Specify the LDP IP address of the other PE router for the destination parameter. Do not specify the IP address of the router from which you are issuing the command.
You can choose any number for the VC ID. However, the VC ID must be unique per pair of routers. Therefore, in large networks, it may be necessary to track the VC ID assignments to ensure that a VC ID does not get assigned twice.
Examples
The following examples show some implementations of the command. Two routers are named PE1 and PE2, which establish a VC to transport packets. PE1 has IP address 172.16.0.1, and PE2 has IP address 192.168.0.1. The VC ID is 50.
ATM AAL5 over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface atm5/0.100
PE1_Router(config-if)# pvc 1/200
PE1_Router(config-atm-vc)# encapsulation aal5
PE1_Router(config-atm-vc)# mpls l2transport route 192.168.0.1 50
At PE2, you issue the following commands:
PE2_Router(config)# interface atm5/0.100
PE2_Router(config-if)# pvc 1/200
PE2_Router(config-atm-vc)# encapsulation aal5
PE2_router(config-atm-vc)# mpls l2transport route 172.16.0.1 50ATM Cell Relay over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface atm5/0.100
PE1_Router(config-if)# pvc 1/200 l2transport
PE1_Router(config-atm-vc)# encapsulation aal0
PE1_Router(config-atm-vc)# mpls l2transport route 192.168.0.1 50
At PE2, you issue the following commands:
PE2_Router(config)# interface atm5/0.100
PE2_Router(config-if)# pvc 1/200 l2transport
PE2_Router(config-atm-vc)# encapsulation aal0
PE2_router(config-atm-vc)# mpls l2transport route 172.16.0.1 50Ethernet over MPLS Example
At PE1, you issue the following commands:
PE1_router(config)# interface GigabitEthernet1/0.2PE1_Router(config-subif)# encapsulation dot1Q 200PE1_Router(config-subif)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_router(config)# interface GigabitEthernet2/0.1PE2_Router(config-subif)# encapsulation dot1Q 200PE2_Router(config-subif)# mpls l2transport route 172.16.0.1 50Frame Relay over MPLS Example
At PE1, you issue the following commands:
PE1_router(config)# connect frompls1 Serial5/0 1000 l2transportPE1_router(config-fr-pw-switching)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_router(config)# connect frompls2 Serial2/0 102 l2transportPE2_router(config-fr-pw-switching)# mpls l2transport route 172.16.0.1 50HDLC over MPLS Example
At PE1, you issue the following commands:
PE1_router(config)# interface Serial3/0PE1_router(config-if)# encapsulation hdlcPE1_router(config-if)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_router(config)# interface Serial1/0PE2_router(config-if)# encapsulation hdlcPE2_router(config-if)# mpls l2transport route 172.16.0.1 50PPP over MPLS Example
At PE1, you issue the following commands:
PE1_router(config)# interface Serial3/0PE1_router(config-if)# encapsulation pppPE1_router(config-if)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_router(config)# interface Serial1/0PE2_router(config-if)# encapsulation pppPE2_router(config-if)# mpls l2transport route 172.16.0.1 50oam-ac emulation-enable
To enable Operation, Administration, and Maintenance (OAM) cell emulation on ATM adaptation layer 5 (AAL5) over Multiprotocol Label Switching (MPLS), use the oam-ac emulation-enable command in the ATM VC configuration mode on both provider edge (PE) routers. To disable OAM cell emulation, use the no form of this command on both routers.
oam-ac emulation-enable [ais-rate]
no oam-ac emulation-enable [ais-rate]
Syntax Description
Defaults
By default OAM cell emulation is disabled. If you enable OAM cell emulation without specifying an AIS rate, the default is to send one AIS cell every second..
Command Modes
ATM VC configuration mode
Command History
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
This command is only applicable to AAL5 over MPLS and is not supported with ATM Cell Relay over MPLS.
This command is only available when you specify the pvc vpi/vci l2transport command.
Examples
The following example shows how to enable OAM cell emulation on an ATM PVC.
Router# interface ATM 1/0/0Router(config-if)# pvc 1/200 l2transport
Router(config-atm-vc)# oam-ac emulation-enableThe following example sets the rate at which an AIS cell is sent to every 30 seconds:
Router (config-atm-vc)# oam-ac emulation-enable 30Related Commands
pvc
To create or assign a name to an ATM permanent virtual circuit (PVC), to specify the encapsulation type on an ATM PVC, and to enter interface-ATM-VC configuration mode, use the pvc command in interface or subinterface configuration mode. To remove an ATM PVC, use the no form of this command.
pvc [name] vpi/vci [ces | ilmi | qsaal | smds | l2transport]
no pvc [name] vpi/vci [ces | ilmi | qsaal | smds | l2transport]
Syntax Description
Defaults
No PVC is defined. When a PVC is defined, the global default of the encapsulation command applies (aal-encap = aal5snap).
Command Modes
Interface or subinterface configuration
Command History
