The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document illustrates a Multiprotocol Label Switching (MPLS) network with ATM. Since VC-merge is not used, there is one VC allocated per route as determined by the prefix in the routing table.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
Cisco IOS® Software Release 12.0 or later is for MPLS on Guilder and Damme.
This setup uses one ATM switch that is used as the label switch router (LSR). In this example, it is a Catalyst 8540MSR. It can also be a LS1010. Cisco recommends software version WA4.8d or later on the LS1010. Any software on the 8540MSR is sufficient.
Cisco Express Forwarding (CEF) needs to be enabled on the routers that run MPLS/Tag switching. In this example, Guilder and Damme are Cisco 3600s. If a 7500 is used, ip cef distributed must be enabled.
Note: Although not a requirement, this document uses VPI 2, 3, or 4 for all Tag VCs in this example.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
In this section, you are presented with the information to configure the features described in this document.
Note: To find additional information on the commands used in this document, use the Command Lookup Tool (registered customers only) .
This document uses this network setup:
Note: Loopback interfaces have been set on all routers/LSRs. They are not shown in the network diagram for the sake of simplicity.
This document uses these configurations:
! interface Loopback0 ip address 100.100.0.1 255.255.0.0 no ip directed-broadcast ! interface Ethernet0/1 ip address 188.8.131.52 255.255.0.0 no ip directed-broadcast ! router ospf 1 network 100.100.0.0 0.0.255.255 area 184.108.40.206 network 220.127.116.11 0.0.255.255 area 18.104.22.168 !
! ip cef ! interface Loopback0 ip address 22.214.171.124 255.255.0.0 no ip directed-broadcast ! interface Ethernet0/1 ip address 126.96.36.199 255.255.0.0 no ip directed-broadcast ! interface ATM1/0 no ip address no ip directed-broadcast no atm ilmi-keepalive ! interface ATM1/0.1 tag-switching ip address 188.8.131.52 255.255.0.0 no ip directed-broadcast tag-switching atm vpi 2-4 tag-switching ip ! router ospf 1 network 184.108.40.206 0.0.255.255 area 0.0.0.0 network 220.127.116.11 0.0.255.255 area 18.104.22.168 network 22.214.171.124 0.0.255.255 area 0.0.0.0 !
! interface Loopback0 ip address 126.96.36.199 255.255.0.0 no ip directed-broadcast ! interface ATM3/0/0 ip address 188.8.131.52 255.255.0.0 no ip directed-broadcast no ip route-cache cef no atm ilmi-keepalive tag-switching atm vpi 2-4 tag-switching ip ! interface ATM3/0/3 ip address 184.108.40.206 255.255.0.0 no ip directed-broadcast no ip route-cache cef no atm ilmi-keepalive tag-switching atm vpi 2-4 tag-switching ip ! router ospf 1 network 220.127.116.11 0.0.255.255 area 0.0.0.0 network 18.104.22.168 0.0.255.255 area 0.0.0.0 network 22.214.171.124 0.0.255.255 area 0.0.0.0 !
! ip cef ! interface Loopback0 ip address 126.96.36.199 255.255.0.0 no ip directed-broadcast ! interface FastEthernet0/0 ip address 188.8.131.52 255.255.0.0 no ip directed-broadcast duplex auto speed 10 tag-switching ip ! interface ATM1/0 no ip address no ip directed-broadcast no atm ilmi-keepalive pvc 0/16 ilmi ! pvc 0/5 qsaal ! ! interface ATM1/0.2 tag-switching ip address 184.108.40.206 255.255.0.0 no ip directed-broadcast tag-switching atm vpi 2-4 tag-switching ip ! router ospf 1 network 220.127.116.11 0.0.255.255 area 0.0.0.0 network 18.104.22.168 0.0.255.255 area 22.214.171.124 network 126.96.36.199 0.0.255.255 area 0.0.0.0 !
! interface Loopback0 ip address 188.8.131.52 255.255.0.0 no ip directed-broadcast ! interface Ethernet0/0 ip address 184.108.40.206 255.255.0.0 no ip directed-broadcast ! router ospf 1 network 220.127.116.11 0.0.255.255 area 18.104.22.168 network 22.214.171.124 0.0.255.255 area 126.96.36.199 !
This section provides information you can use to confirm your configuration is working properly.
Certain show commands are supported by the Output Interpreter Tool (registered customers only) , which allows you to view an analysis of show command output.
show tag-switching forwarding-table—Shows the Tag Forwarding Information Base (TFIB).
show tag-switching atm-tdp bindings—Shows dynamic ATM tagging information.
show tag-switching int atm [int number] detail—Shows detailed per-interface tag switching information.
This output shows that the routing table is complete on Guilder:
Guilder#show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route Gateway of last resort is not set 188.8.131.52/16 is subnetted, 1 subnets C 184.108.40.206 is directly connected, Loopback0 220.127.116.11/32 is subnetted, 1 subnets O 18.104.22.168 [110/2] via 22.214.171.124, 23:14:31, ATM1/0.1 126.96.36.199/32 is subnetted, 1 subnets O 100.100.0.1 [110/11] via 188.8.131.52, 23:45:47, Ethernet0/1 184.108.40.206/32 is subnetted, 1 subnets O IA 220.127.116.11 [110/13] via 18.104.22.168, 23:13:01, ATM1/0.1 O 22.214.171.124/16 [110/2] via 126.96.36.199, 23:14:31, ATM1/0.1 C 188.8.131.52/16 is directly connected, ATM1/0.1 184.108.40.206/16 is subnetted, 1 subnets O IA 220.127.116.11 [110/12] via 18.104.22.168, 23:13:08, ATM1/0.1 22.214.171.124/16 is subnetted, 1 subnets C 126.96.36.199 is directly connected, Ethernet0/1 188.8.131.52/32 is subnetted, 1 subnets O 184.108.40.206 [110/3] via 220.127.116.11, 23:14:32, ATM1/0.1
Check the prefix to label/VC mapping with the show tag-switching forwarding-table command.
Guilder#show tag-switching forwarding-table Local Outgoing Prefix Bytes tag Outgoing Next Hop tag tag or VC or Tunnel Id switched interface 26 Untagged 100.100.0.1/32 570 Et0/1 18.104.22.168 27 2/33 22.214.171.124/32 0 AT1/0.1 point2point 28 2/34 126.96.36.199/16 0 AT1/0.1 point2point 29 2/35 188.8.131.52/32 0 AT1/0.1 point2point 30 2/37 184.108.40.206/16 0 AT1/0.1 point2point 31 2/38 220.127.116.11/32 0 AT1/0.1 point2point
On Capri (the ATM LSR), you can check the TVC to route binding with the show tag atm-tdp bindings command. One TVC is used for each routing table entry.
Capri#show tag atm-tdp bindings Destination: 18.104.22.168/16 Tailend Switch ATM3/0/0 2/34 Active -> Terminating Active Tailend Switch ATM3/0/3 2/34 Active -> Terminating Active Destination: 22.214.171.124/16 Tailend Switch ATM3/0/0 2/35 Active -> Terminating Active Destination: 126.96.36.199/32 Transit ATM3/0/3 2/33 Active -> ATM3/0/0 2/36 Active Destination: 188.8.131.52/32 Transit ATM3/0/3 2/35 Active -> ATM3/0/0 2/37 Active Destination: 184.108.40.206/16 Transit ATM3/0/3 2/36 Active -> ATM3/0/0 2/38 Active Destination: 220.127.116.11/16 Tailend Switch ATM3/0/3 2/37 Active -> Terminating Active Destination: 18.104.22.168/32 Transit ATM3/0/0 2/53 Active -> ATM3/0/3 2/33 Active Destination: 100.100.0.1/32 Transit ATM3/0/0 2/54 Active -> ATM3/0/3 2/34 Active Destination: 22.214.171.124/16 Transit ATM3/0/0 2/55 Active -> ATM3/0/3 2/35 Active
There is currently no specific troubleshooting information available for this configuration.