 Feedback
|
Table Of Contents
Any Transport over MPLS: Tunnel Selection
Prerequisites for Any Transport over MPLS: Tunnel Selection
Restrictions for Any Transport over MPLS: Tunnel Selection
Information About Any Transport over MPLS: Tunnel Selection
How to Configure Any Transport over MPLS: Tunnel Selection
Configuring Any Transport over MPLS: Tunnel Selection
Configuration Examples for Any Transport over MPLS: Tunnel Selection
Configuring Tunnel Selection: Example
Verifying the Configuration: Example
Troubleshooting Tunnel Selection: Example
Feature Information for Any Transport over MPLS: Tunnel Selection
Any Transport over MPLS: Tunnel Selection
First Published: April 14, 2003Last Updated: February 19, 2007The Any Transport over MPLS: Tunnel Selection feature allows you to specify the path that Any Transport over MPLS (AToM) traffic uses. You can specify either a Multiprotocol Label Switching (MPLS) traffic engineering tunnel or a destination IP address and Domain Name System (DNS) name. If the specified path is unreachable, you can specify that the virtual circuits (VCs) should use the default path, which is the path that MPLS Label Distribution Protocol (LDP) uses for signaling. The option of having a backup LDP path is enabled by default; you must explicitly disable it.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Any Transport over MPLS: Tunnel Selection" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Any Transport over MPLS: Tunnel Selection
•
•
•
•
•
Prerequisites for Any Transport over MPLS: Tunnel Selection
For the Cisco 7600 series router, see the following documents for prerequisites:
•
•
Restrictions for Any Transport over MPLS: Tunnel Selection
This feature is supported only on the Cisco 7600 series router in Cisco IOS Release 12.2(33)SRA and later releases.. For the Cisco 7600 series router, see the following documents for restrictions:
•
•
Information About Any Transport over MPLS: Tunnel Selection
This feature allows you to specify the path that Any Transport over MPLS (AToM) traffic uses. You can specify either a Multiprotocol Label Switching (MPLS) Traffic Engineering tunnel or a destination IP address and Domain Name System (DNS) name. If the specified path is unreachable, you can specify that the virtual circuits (VCs) should use the default path, which is the path that MPLS Label Distribution Protocol (LDP) used for signaling. This option is enabled by default; you must explicitly disable it.
How to Configure Any Transport over MPLS: Tunnel Selection
•
•
•
Configuring Any Transport over MPLS: Tunnel Selection
You configure tunnel selection when you set up a pseudowire class. You enable tunnel selection with the preferred-path command. Then you apply the pseudowire class to an interface that has been configured to transport AToM packets.
The following guidelines provide more information about configuring tunnel selection:
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Configuration Examples for Any Transport over MPLS: Tunnel Selection
This section contains the following configuration example:
•
•
•
Configuring Tunnel Selection: Example
The following example sets up two preferred paths for PE1. One preferred path specifies an MPLS traffic engineering tunnel. The other preferred path specifies an IP address of a loopback address on PE2. There is a static route configured on PE1 that uses a TE tunnel to reach the IP address on PE2.
Router PE1
mpls label protocol ldpmpls traffic-eng tunnelstag-switching tdp router-id Loopback0pseudowire-class pw1encapsulation mplspreferred-path interface Tunnel1 disable-fallback!pseudowire-class pw2encapsulation mplspreferred-path peer 10.18.18.18!interface Loopback0ip address 10.2.2.2 255.255.255.255no ip directed-broadcastno ip mroute-cache!interface Tunnel1ip unnumbered Loopback0no ip directed-broadcasttunnel destination 10.16.16.16tunnel mode mpls traffic-engtunnel mpls traffic-eng priority 7 7tunnel mpls traffic-eng bandwidth 1500tunnel mpls traffic-eng path-option 1 explicit name path-tu1!interface Tunnel2ip unnumbered Loopback0no ip directed-broadcasttunnel destination 10.16.16.16tunnel mode mpls traffic-engtunnel mpls traffic-eng priority 7 7tunnel mpls traffic-eng bandwidth 1500tunnel mpls traffic-eng path-option 1 dynamic!interface gigabitethernet0/0/0no ip addressno ip directed-broadcastno negotiation auto!interface gigabitethernet0/0/0.1encapsulation dot1Q 222no ip directed-broadcastxconnect 10.16.16.16 101 pw-class pw1!interface ATM1/0/0no ip addressno ip directed-broadcastno atm enable-ilmi-trapno atm ilmi-keepalivepvc 0/50 l2transportencapsulation aal5xconnect 10.16.16.16 150 pw-class pw2!interface gigabitEthernet2/0/1ip address 10.0.0.1 255.255.255.0no ip directed-broadcasttag-switching ipmpls traffic-eng tunnelsip rsvp bandwidth 15000 15000!router ospf 1log-adjacency-changesnetwork 10.0.0.0 0.0.0.255 area 0network 10.2.2.2 0.0.0.0 area 0mpls traffic-eng router-id Loopback0mpls traffic-eng area 0!ip route 10.18.18.18 255.255.255.255 Tunnel2!ip explicit-path name path-tu1 enablenext-address 10.0.0.1index 3 next-address 10.0.0.1PE2
mpls label protocol ldpmpls traffic-eng tunnelsmpls ldp router-id Loopback0interface Loopback0ip address 10.16.16.16 255.255.255.255no ip directed-broadcastno ip mroute-cache!interface Loopback2ip address 10.18.18.18 255.255.255.255no ip directed-broadcast!interface gigabitEthernet3/1ip address 10.0.0.2 255.255.255.0no ip directed-broadcastmpls traffic-eng tunnelsmpls ipno cdp enableip rsvp bandwidth 15000 15000!interface gigabitEthernet3/3no ip addressno ip directed-broadcastno cdp enable!interface gigabitEthernet3/3.1encapsulation dot1Q 222no ip directed-broadcastno cdp enablempls l2transport route 10.2.2.2 101!interface ATM5/0no ip addressno ip directed-broadcastno atm enable-ilmi-trapno atm ilmi-keepalivepvc 0/50 l2transportencapsulation aal5xconnect 10.2.2.2 150 encapsulation mpls!router ospf 1log-adjacency-changesnetwork 10.0.0.0 0.0.0.255 area 0network 10.16.16.16 0.0.0.0 area 0mpls traffic-eng router-id Loopback0mpls traffic-eng area 0Verifying the Configuration: Example
In the following example, the show mpls l2transport vc command shows the following information (in bold) about the VCs:
•
•
Router# show mpls l2transport vc detailLocal interface: Gi0/0/0.1 up, line protocol up, Eth VLAN 222 upDestination address: 10.16.16.16, VC ID: 101, VC status: upPreferred path: Tunnel1, activeDefault path: disabledTunnel label: 3, next hop point2pointOutput interface: Tu1, imposed label stack {17 16}Create time: 00:27:31, last status change time: 00:27:31Signaling protocol: LDP, peer 10.16.16.16:0 upMPLS VC labels: local 25, remote 16Group ID: local 0, remote 6MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 10, send 10byte totals: receive 1260, send 1300packet drops: receive 0, send 0Local interface: AT1/0/0 up, line protocol up, ATM AAL5 0/50 upDestination address: 10.16.16.16, VC ID: 150, VC status: upPreferred path: 10.18.18.18, activeDefault path: readyTunnel label: 3, next hop point2pointOutput interface: Tu2, imposed label stack {18 24}Create time: 00:15:08, last status change time: 00:07:37Signaling protocol: LDP, peer 10.16.16.16:0 upMPLS VC labels: local 26, remote 24Group ID: local 2, remote 0MTU: local 4470, remote 4470Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 0, send 0byte totals: receive 0, send 0packet drops: receive 0, send 0Troubleshooting Tunnel Selection: Example
You can use the debug mpls l2transport vc event command to troubleshoot tunnel selection. For example, if the tunnel interface that is used for the preferred path is shut down, the default path is enabled. The debug mpls l2transport vc event command provides the following output:
AToM SMGR [10.2.2.2, 101]: Processing imposition update, vc_handle 62091860, update_action 3, remote_vc_label 16AToM SMGR [10.2.2.2, 101]: selected route no parent rewrite: tunnel not upAToM SMGR [10.2.2.2, 101]: Imposition Programmed, Output Interface: Et3/2Additional References
The following sections provide references related to the Any Transport over MPLS: Tunnel Selection feature.
Related Documents
Any Transport over MPLS for the Cisco 7600 series routers
Cisco 7600 Series Cisco IOS Software Configuration Guide, Release 12.2SX
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents modified commands only.
debug mpls l2transport vc
To display information about the status of the Any Transport over MPLS (AToM) virtual circuits (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
Usage Guidelines
You can issue this command from the line card or the 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 [10.9.9.9, 50]: Event provision, state changed from idle to provisioned*Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Provision vc*Mar 24 23:17:24.371: AToM SMGR [10.9.9.9, 50]: Requesting VC create, vc_handle 61A09930*Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Event local up, state changed from provisioned to local standby*Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Update local vc label binding*Mar 24 23:17:24.371: AToM SMGR [10.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 [10.9.9.9, 50]: Event ldp up, state changed from local standby to local ready*Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Advertise local vc label binding*Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Event remote up, state changed from local ready to establishing*Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Remote end up*Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Event remote validated, state changed from establishing to established*Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Validate vc, activating data plane*Mar 24 23:17:28.567: AToM SMGR [10.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 [10.9.9.9, 50]: Imposition Programmed, Output Interface: PO5/0*Mar 24 23:17:28.567: AToM SMGR [10.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 [10.9.9.9, 50]: Imposition Programmed, Output Interface: PO5/0preferred-path
To specify the path that traffic uses (a Multiprotocol Label Switching (MPLS) Traffic engineering (TE) tunnel or destination IP address and Domain Name Server (DNS) name), use the preferred-path command in pseudowire configuration mode. To disable tunnel selection, use the no form of this command.
preferred-path {interface tunnel tunnel-number | peer {ip-address | host-name}} [disable-fallback]
no preferred-path {interface tunnel tunnel-number | peer {ip-address | host-name}} [disable-fallback]
Syntax Description
Defaults
Tunnel selection is not enabled.
Command Modes
Pseudowire configuration
Command History
Usage Guidelines
The following guidelines provide more information about using this command:
•
•
•
•
•
•
•
Examples
The following example creates a pseudowire class and specifies tunnel 1 as the preferred path:
Router(config)# pseudowire-class pw1Router(config-pw)# encapsulation mplsRouter(config-pw)# preferred-path interface tunnel 1 disable-fallbackRelated Commands
show mpls l2transport vc
Displays information about AToM VCs that have been enabled to route Layer 2 packets on a router.
Feature Information for Any Transport over MPLS: Tunnel Selection
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Note
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0612R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006, 2007 Cisco Systems, Inc. All rights reserved.
