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.
The MPLS VPN Inter-AS with ASBRs Exchanging IPv4 Routes and MPLS Labels feature allows a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) to span service providers and autonomous systems. This module explains how to configure an MPLS VPN Inter-AS network so that the Autonomous System Boundary Routers (ASBRs) exchange IPv4 routes with MPLS labels of the provider edge (PE) routers. Route reflectors (RRs) exchange VPN-IPv4 routes by using multihop, multiprotocol, external Border Gateway Protocol (eBGP).
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
The network must be properly configured for MPLS VPN operation before you configure MPLS VPN Inter-AS with ASBRs Exchanging IPv4 Routes and MPLS Labels.
The table below lists the Cisco 12000 series line card support in Cisco IOS S releases.
Table 1 | Cisco 12000 Series Line Card Support in Cisco IOS S Releases |
Type |
Line Cards |
Cisco IOS Release Supported |
---|---|---|
ATM |
4-Port OC-3 ATM 1-Port OC-12 ATM 4-Port OC-12 ATM 8-Port OC-3 ATM |
12.0(22)S 12.0(23)S 12.0(27)S |
Channelized interface |
2-Port CHOC-3 6-Port Ch T3 (DS1) 1-Port CHOC-12 (DS3) 1-Port CHOC-12 (OC-3) 4-Port CHOC-12 ISE 1-Port CHOC-48 ISE |
12.0(22)S 12.0(23)S 12.0(27)S |
Electrical interface |
6-Port DS3 12-Port DS3 6-Port E3 12-Port E3 |
12.0(22)S 12.0(23)S 12.0(27)S |
Ethernet |
3-Port GbE |
12.0(23)S 12.0(27)S |
Packet over SONET (POS) |
4-Port OC-3 POS 8-Port OC-3 POS 16-Port OC-3 POS 1-Port OC-12 POS 4-Port OC-12 POS 1-Port OC-48 POS 4-Port OC-3 POS ISE 8-Port OC-3 POS ISE 16-Port OC-3 POS ISE 4-Port OC-12 POS ISE 1-Port OC-48 POS ISE |
12.0(22)S 12.0(23)S 12.0(27)S |
An autonomous system is a single network or group of networks that is controlled by a common system administration group and that uses a single, clearly defined routing protocol.
As VPNs grow, their requirements expand. In some cases, VPNs need to reside on different autonomous systems in different geographic areas. Also, some VPNs need to extend across multiple service providers (overlapping VPNs). Regardless of the complexity and location of the VPNs, the connection between autonomous systems must be seamless to the customer.
An MPLS VPN Inter-AS provides the following benefits:
This feature can configure a MPLS VPN Inter-AS network so that the ASBRs exchange IPv4 routes with MPLS labels of the PE routers. RRs exchange VPN-IPv4 routes by using multihop, multiprotocol, External Border Gateway Protocol (eBGP). This method of configuring the Inter-AS system is often called MPLS VPN Inter-AS--IPv4 BGP Label Distribution.
An Inter-AS system can be configured so that the ASBRs exchange the IPv4 routes and MPLS labels has the following benefits:
A VPN service provider network to exchange IPv4 routes with MPLS labels can be configured. The VPN service provider network can be configured as follows:
Alternatively, the route reflector can reflect the IPv4 routes and MPLS labels learned from the ASBR to the PE routers in the VPN. This is accomplished by the ASBR exchanging IPv4 routes and MPLS labels with the route reflector. The route reflector also reflects the VPN-IPv4 routes to the PE routers in the VPN. For example, in VPN1 of the figure below, RR1 reflects to PE1 the VPN-IPv4 routes it learned and IPv4 routes and MPLS labels learned from ASBR1. Using the route reflectors to store the VPN-IPv4 routes and forward them through the PE routers and ASBRs allows for a scalable configuration.
BGP routing information includes the following items:
MPLS labels are included in the update messages that a router sends. Routers exchange the following types of BGP messages:
When BGP (eBGP and iBGP) distributes a route, it can also distribute an MPLS label that is mapped to that route. The MPLS label mapping information for the route is carried in the BGP update message that contains the information about the route. If the next hop is not changed, the label is preserved.
When you issue the neighbor send-label command on both BPG routers, the routers advertise to each other that they can then send MPLS labels with the routes. If the routers successfully negotiate their ability to send MPLS labels, the routers add MPLS labels to all outgoing BGP updates.
To configure MPLS VPN Inter-AS with ASBRs exchanging IPv4 routes and MPLS labels, perform the tasks in the following sections:
The figure below shows the following sample configuration:
Perform this task to configure the ASBRs to exchange IPv4 routes and MPLS labels. This configuration procedure uses ASBR1 as an example.
Perform this task to enable the route reflectors to exchange VPN-IPv4 routes by using multihop, multiprotocol eBGP.
This procedure also specifies that the next hop information and the VPN label are to be preserved across the autonomous systems. This procedure uses RR1 as an example of the route reflector.
Perform this task to enable the RR to reflect the IPv4 routes and labels learned by the ASBR to the PE routers in the autonomous system.
This is accomplished by making the ASBR and PE router route reflector clients of the RR. This procedure also explains how to enable the RR to reflect the VPN-IPv4 routes.
If you use ASBRs to distribute the IPv4 labels and route reflectors to distribute the VPN-IPv4 routes, use the following procedures to help verify the configuration:
The figure below shows the configuration that is referred to in the next several sections.
Perform this task to verify the route reflector configuration.
Perform this task to verify that router CE1 has NLRI for router CE2.
Perform this task to verify that router PE1 has NLRI for router CE2.
Perform this task to ensure that PE2 can access CE2.
Perform this task to verify that the ASBRs exchange IPv4 routes with MPLS labels or IPv4 routes without labels as prescribed by a route map.
Configuration examples for Inter-AS using BGP to distribute routes and MPLS labels over an MPLS VPN service provider included in this section are as follows:
The figure below shows two MPLS VPN service providers. The service provider distributes the VPN-IPv4 routes between the route reflectors. The MPLS VPN service providers distribute the IPv4 routes with MPLS labels between the ASBRs.
The configuration example shows the following two techniques you can use to distribute the VPN-IPv4 routes and the IPv4 routes with MPLS labels of the remote RRs and PEs to the local RRs and PEs:
The configuration example for RR1 specifies the following:
ip subnet-zero ip cef ! interface Loopback0 ip address aa.aa.aa.aa 255.255.255.255 ! interface Ethernet0/3 ip address dd.0.0.2 255.0.0.0 ! router ospf 10 log-adjacency-changes auto-cost reference-bandwidth 1000 network aa.aa.aa.aa 0.0.0.0 area 100 network dd.0.0.0 0.255.255.255 area 100 ! router bgp 100 bgp cluster-id 1 bgp log-neighbor-changes timers bgp 10 30 neighbor ee.ee.ee.ee remote-as 100 neighbor ee.ee.ee.ee update-source Loopback0 neighbor ww.ww.ww.ww remote-as 100 neighbor ww.ww.ww.ww update-source Loopback0 neighbor bb.bb.bb.bb remote-as 200 neighbor bb.bb.bb.bb ebgp-multihop 255 neighbor bb.bb.bb.bb update-source Loopback0 no auto-summary ! address-family ipv4 neighbor ee.ee.ee.ee activate neighbor ee.ee.ee.ee route-reflector-client !IPv4+labels session to PE1 neighbor ee.ee.ee.ee send-label neighbor ww.ww.ww.ww activate neighbor ww.ww.ww.ww route-reflector-client !IPv4+labels session to ASBR1 neighbor ww.ww.ww.ww send-label no neighbor bb.bb.bb.bb activate no auto-summary no synchronization exit-address-family ! address-family vpnv4 neighbor ee.ee.ee.ee activate neighbor ee.ee.ee.ee route-reflector-client !VPNv4 session with PE1 neighbor ee.ee.ee.ee send-community extended neighbor bb.bb.bb.bb activate neighbor bb.bb.bb.bb next-hop-unchanged !MH-VPNv4 session with RR2 neighbor bb.bb.bb.bb send-community extended !with next hop unchanged exit-address-family ! ip default-gateway 3.3.0.1 no ip classless ! snmp-server engineID local 00000009020000D0584B25C0 snmp-server community public RO snmp-server community write RW no snmp-server ifindex persist snmp-server packetsize 2048 ! end
ASBR1 exchanges IPv4 routes and MPLS labels with ASBR2.
In this example, ASBR1 uses route maps to filter routes:
ip subnet-zero mpls label protocol ldp ! interface Loopback0 ip address ww.ww.ww.ww 255.255.255.255 ! interface Ethernet0/2 ip address hh.0.0.2 255.0.0.0 ! interface Ethernet0/3 ip address dd.0.0.1 255.0.0.0 mpls label protocol ldp mpls ip ! router ospf 10 log-adjacency-changes auto-cost reference-bandwidth 1000 redistribute connected subnets passive-interface Ethernet0/2 network ww.ww.ww.ww 0.0.0.0 area 100 network dd.0.0.0 0.255.255.255 area 100 router bgp 100 bgp log-neighbor-changes timers bgp 10 30 neighbor aa.aa.aa.aa remote-as 100 neighbor aa.aa.aa.aa update-source Loopback0 neighbor hh.0.0.1 remote-as 200 no auto-summary ! ! address-family ipv4 ! Redistributing IGP into BGP redistribute ospf 10 ! so that PE1 & RR1 loopbacks neighbor aa.aa.aa.aa activate ! get into the BGP table neighbor aa.aa.aa.aa send-label neighbor hh.0.0.1 activate neighbor hh.0.0.1 advertisement-interval 5 neighbor hh.0.0.1 send-label neighbor hh.0.0.1 route-map IN in ! accepting routes in route map IN. neighbor hh.0.0.1 route-map OUT out ! distributing routes in route map OUT. neighbor kk.0.0.1 activate neighbor kk.0.0.1 advertisement-interval 5 neighbor kk.0.0.1 send-label neighbor kk.0.0.1 route-map IN in ! accepting routes in route map IN. neighbor kk.0.0.1 route-map OUT out ! distributing routes in route map OUT. no auto-summary no synchronization exit-address-family ! ip default-gateway 3.3.0.1 ip classless ! access-list 1 permit ee.ee.ee.ee log !Setting up the access lists access-list 2 permit ff.ff.ff.ff log access-list 3 permit aa.aa.aa.aa log access-list 4 permit bb.bb.bb.bb log route-map IN permit 10 !Setting up the route maps match ip address 2 match mpls-label ! route-map IN permit 11 match ip address 4 ! route-map OUT permit 12 match ip address 3 ! route-map OUT permit 13 match ip address 1 set mpls-label ! end
RR2 exchanges VPN-IPv4 routes with RR1 through multihop, multiprotocol eBGP. This configuration also specifies that the next-hop information and the VPN label are preserved across the autonomous systems:
ip subnet-zero ip cef ! interface Loopback0 ip address bb.bb.bb.bb 255.255.255.255 ! interface Serial1/1 ip address ii.0.0.2 255.0.0.0 ! router ospf 20 log-adjacency-changes network bb.bb.bb.bb 0.0.0.0 area 200 network ii.0.0.0 0.255.255.255 area 200 ! router bgp 200 bgp cluster-id 1 bgp log-neighbor-changes timers bgp 10 30 neighbor aa.aa.aa.aa remote-as 100 neighbor aa.aa.aa.aa ebgp-multihop 255 neighbor aa.aa.aa.aa update-source Loopback0 neighbor ff.ff.ff.ff remote-as 200 neighbor ff.ff.ff.ff update-source Loopback0 no auto-summary ! address-family vpnv4 neighbor aa.aa.aa.aa activate neighbor aa.aa.aa.aa next-hop-unchanged !Multihop VPNv4 session with RR1 neighbor aa.aa.aa.aa send-community extended !with next-hop-unchanged neighbor ff.ff.ff.ff activate neighbor ff.ff.ff.ff route-reflector-client !VPNv4 session with PE2 neighbor ff.ff.ff.ff send-community extended exit-address-family ! ip default-gateway 3.3.0.1 no ip classless ! end
ASBR2 exchanges IPv4 routes and MPLS labels with ASBR1. However, in contrast to ASBR1, ASBR2 does not use the RR to reflect IPv4 routes and MPLS labels to PE2. ASBR2 redistributes the IPv4 routes and MPLS labels learned from ASBR1 into IGP. PE2 can now reach these prefixes.
ip subnet-zero ip cef ! mpls label protocol ldp ! interface Loopback0 ip address xx.xx.xx.xx 255.255.255.255 ! interface Ethernet1/0 ip address hh.0.0.1 255.0.0.0 ! interface Ethernet1/2 ip address jj.0.0.1 255.0.0.0 mpls label protocol ldp mpls ip ! router ospf 20 log-adjacency-changes auto-cost reference-bandwidth 1000 redistribute connected subnets redistribute bgp 200 subnets ! Redistributing the routes learned from passive-interface Ethernet1/0 ! ASBR1(eBGP+labels session) into IGP network xx.xx.xx.xx 0.0.0.0 area 200 ! so that PE2 will learn them network jj..0.0 0.255.255.255 area 200 ! router bgp 200 bgp log-neighbor-changes timers bgp 10 30 neighbor bb.bb.bb.bb remote-as 200 neighbor bb.bb.bb.bb update-source Loopback0 neighbor hh.0.0.2 remote-as 100 no auto-summary ! address-family ipv4 redistribute ospf 20 ! Redistributing IGP into BGP neighbor hh.0.0.2 activate ! so that PE2 & RR2 loopbacks neighbor hh.0.0.2 advertisement-interval 5 ! will get into the BGP-4 table. neighbor hh.0.0.2 route-map IN in neighbor hh.0.0.2 route-map OUT out neighbor hh.0.0.2 send-label neighbor kk.0.0.2 activate neighbor kk.0.0.2 advertisement-interval 5 neighbor kk.0.0.2 route-map IN in neighbor kk.0.0.2 route-map OUT out neighbor kk.0.0.2 send-label no auto-summary no synchronization exit-address-family ! address-family vpnv4 neighbor bb.bb.bb.bb activate neighbor bb.bb.bb.bb send-community extended exit-address-family ! ip default-gateway 3.3.0.1 ip classless ! access-list 1 permit ff.ff.ff.ff log !Setting up the access lists access-list 2 permit ee.ee.ee.ee log access-list 3 permit bb.bb.bb.bb log access-list 4 permit aa.aa.aa.aa log route-map IN permit 11 !Setting up the route maps match ip address 2 match mpls-label ! route-map IN permit 12 match ip address 4 ! route-map OUT permit 10 match ip address 1 set mpls-label ! route-map OUT permit 13 match ip address 3 end
Configuration examples for Inter-AS using BGP to distribute routes and MPLS labels over a non MPLS VPN service provider included in this section are as follows:
The figure below shows two MPLS VPN service providers that are connected through a non MPLS VPN service provider. The autonomous system in the middle of the network is configured as a backbone autonomous system that uses LDP or Tag Distribution Protocol (TDP) to distribute MPLS labels. Traffic engineering tunnels can also be used instead of TDP or LDP to build the LSP across the non MPLS VPN service provider.
The configuration example for RR1 specifies the following:
ip subnet-zero ip cef ! interface Loopback0 ip address aa.aa.aa.aa 255.255.255.255 ! interface Serial1/2 ip address dd.0.0.2 255.0.0.0 clockrate 124061 ! router ospf 10 log-adjacency-changes auto-cost reference-bandwidth 1000 network aa.aa.aa.aa 0.0.0.0 area 100 network dd.0.0.0 0.255.255.255 area 100 ! router bgp 100 bgp cluster-id 1 bgp log-neighbor-changes timers bgp 10 30 neighbor ee.ee.ee.ee remote-as 100 neighbor ee.ee.ee.ee update-source Loopback0 neighbor ww.ww.ww.ww remote-as 100 neighbor ww.ww.ww.ww update-source Loopback0 neighbor bb.bb.bb.bb remote-as 200 neighbor bb.bb.bb.bb ebgp-multihop 255 neighbor bb.bb.bb.bb update-source Loopback0 no auto-summary ! address-family ipv4 neighbor ee.ee.ee.ee activate neighbor ee.ee.ee.ee route-reflector-client !IPv4+labels session to PE1 neighbor ee.ee.ee.ee send-label neighbor ww.ww.ww.ww activate neighbor ww.ww.ww.ww route-reflector-client !IPv4+labels session to ASBR1 neighbor ww.ww.ww.ww send-label no neighbor bb.bb.bb.bb activate no auto-summary no synchronization exit-address-family ! address-family vpnv4 neighbor ee.ee.ee.ee activate neighbor ee.ee.ee.ee route-reflector-client !VPNv4 session with PE1 neighbor ee.ee.ee.ee send-community extended neighbor bb.bb.bb.bb activate neighbor bb.bb.bb.bb next-hop-unchanged !MH-VPNv4 session with RR2 neighbor bb.bb.bb.bb send-community extended with next-hop-unchanged exit-address-family ! ip default-gateway 3.3.0.1 no ip classless ! snmp-server engineID local 00000009020000D0584B25C0 snmp-server community public RO snmp-server community write RW no snmp-server ifindex persist snmp-server packetsize 2048 ! end
ASBR1 exchanges IPv4 routes and MPLS labels with ASBR2.
In this example, ASBR1 uses route maps to filter routes:
ip subnet-zero ip cef distributed mpls label protocol ldp ! interface Loopback0 ip address ww.ww.ww.ww 255.255.255.255 ! interface Serial3/0/0 ip address kk.0.0.2 255.0.0.0 ip route-cache distributed ! interface Ethernet0/3 ip address dd.0.0.1 255.0.0.0 mpls label protocol ldp mpls ip ! router ospf 10 log-adjacency-changes auto-cost reference-bandwidth 1000 redistribute connected subnets passive-interface Serial3/0/0 network ww.ww.ww.ww 0.0.0.0 area 100 network dd.0.0.0 0.255.255.255 area 100 router bgp 100 bgp log-neighbor-changes timers bgp 10 30 neighbor aa.aa.aa.aa remote-as 100 neighbor aa.aa.aa.aa update-source Loopback0 neighbor kk.0.0.1 remote-as 200 no auto-summary ! address-family ipv4 redistribute ospf 10 ! Redistributing IGP into BGP neighbor aa.aa.aa.aa activate ! so that PE1 & RR1 loopbacks neighbor aa.aa.aa.aa send-label ! get into BGP table neighbor kk.0.0.1 activate neighbor kk.0.0.1 advertisement-interval 5 neighbor kk.0.0.1 send-label neighbor kk.0.0.1 route-map IN in ! Accepting routes specified in route map IN neighbor kk.0.0.1 route-map OUT out ! Distributing routes specified in route map OUT no auto-summary no synchronization exit-address-family ! ip default-gateway 3.3.0.1 ip classless ! access-list 1 permit ee.ee.ee.ee log access-list 2 permit ff.ff.ff.ff log access-list 3 permit aa.aa.aa.aa log access-list 4 permit bb.bb.bb.bb log ! route-map IN permit 10 match ip address 2 match mpls-label ! route-map IN permit 11 match ip address 4 ! route-map OUT permit 12 match ip address 3 ! route-map OUT permit 13 match ip address 1 set mpls-label ! end
RR2 exchanges VPN-IPv4 routes with RR1 using multihop, multiprotocol eBGP. This configuration also specifies that the next-hop information and the VPN label are preserved across the autonomous systems:
ip subnet-zero ip cef ! interface Loopback0 ip address bb.bb.bb.bb 255.255.255.255 ! interface Serial1/1 ip address ii.0.0.2 255.0.0.0 ! router ospf 20 log-adjacency-changes network bb.bb.bb.bb 0.0.0.0 area 200 network ii.0.0.0 0.255.255.255 area 200 ! router bgp 200 bgp cluster-id 1 bgp log-neighbor-changes timers bgp 10 30 neighbor aa.aa.aa.aa remote-as 100 neighbor aa.aa.aa.aa ebgp-multihop 255 neighbor aa.aa.aa.aa update-source Loopback0 neighbor ff.ff.ff.ff remote-as 200 neighbor ff.ff.ff.ff update-source Loopback0 no auto-summary ! address-family vpnv4 neighbor aa.aa.aa.aa activate neighbor aa.aa.aa.aa next-hop-unchanged !MH vpnv4 session with RR1 neighbor aa.aa.aa.aa send-community extended !with next-hop-unchanged neighbor ff.ff.ff.ff activate neighbor ff.ff.ff.ff route-reflector-client !vpnv4 session with PE2 neighbor ff.ff.ff.ff send-community extended exit-address-family ! ip default-gateway 3.3.0.1 no ip classless ! end
ASBR2 exchanges IPv4 routes and MPLS labels with ASBR1. However, in contrast to ASBR1, ASBR2 does not use the RR to reflect IPv4 routes and MPLS labels to PE2. ASBR2 redistributes the IPv4 routes and MPLS labels learned from ASBR1 into IGP. PE2 can now reach these prefixes.
ip subnet-zero ip cef ! mpls label protocol ldp ! interface Loopback0 ip address xx.xx.xx.xx 255.255.255.255 ! interface Ethernet0/1 ip address qq.0.0.2 255.0.0.0 ! interface Ethernet1/2 ip address jj.0.0.1 255.0.0.0 mpls label protocol ldp mpls ip ! router ospf 20 log-adjacency-changes auto-cost reference-bandwidth 1000 redistribute connected subnets redistribute bgp 200 subnets !redistributing the routes learned from passive-interface Ethernet0/1 !ASBR2 (eBGP+labels session) into IGP network xx.xx.xx.xx 0.0.0.0 area 200 !so that PE2 will learn them network jj.0.0.0 0.255.255.255 area 200 ! router bgp 200 bgp log-neighbor-changes timers bgp 10 30 neighbor bb.bb.bb.bb remote-as 200 neighbor bb.bb.bb.bb update-source Loopback0 neighbor qq.0.0.1 remote-as 100 no auto-summary ! address-family ipv4 ! Redistributing IGP into BGP redistribute ospf 20 ! so that PE2 & RR2 loopbacks neighbor qq.0.0.1 activate ! will get into the BGP-4 table neighbor qq.0.0.1 advertisement-interval 5 neighbor qq.0.0.1 route-map IN in neighbor qq.0.0.1 route-map OUT out neighbor qq.0.0.1 send-label no auto-summary no synchronization exit-address-family ! address-family vpnv4 neighbor bb.bb.bb.bb activate neighbor bb.bb.bb.bb send-community extended exit-address-family ! ip default-gateway 3.3.0.1 ip classless ! access-list 1 permit ff.ff.ff.ff log access-list 2 permit ee.ee.ee.ee log access-list 3 permit bb.bb.bb.bb log access-list 4 permit aa.aa.aa.aa log ! route-map IN permit 11 match ip address 2 match mpls-label ! route-map IN permit 12 match ip address 4 ! route-map OUT permit 10 match ip address 1 set mpls-label ! route-map OUT permit 13 match ip address 3 ! end
ASBR3 belongs to a non MPLS VPN service provider. ASBR3 exchanges IPv4 routes and MPLS labels with ASBR1. ASBR3 also passes the routes learned from ASBR1 to ASBR4 through RR3.
Note |
Do not redistribute eBGP routes learned into iBGP if you are using iBGP to distribute the routes and labels. This is not a supported configuration. |
ip subnet-zero ip cef ! interface Loopback0 ip address yy.yy.yy.yy 255.255.255.255 interface Hssi4/0 ip address mm.0.0.0.1 255.0.0.0 mpls ip hssi internal-clock ! interface Serial5/0 ip address kk.0.0.1 255.0.0.0 load-interval 30 clockrate 124061 ! router ospf 30 log-adjacency-changes auto-cost reference-bandwidth 1000 redistribute connected subnets network yy.yy.yy.yy 0.0.0.0 area 300 network mm.0.0.0 0.255.255.255 area 300 ! router bgp 300 bgp log-neighbor-changes timers bgp 10 30 neighbor cc.cc.cc.cc remote-as 300 neighbor cc.cc.cc.cc update-source Loopback0 neighbor kk.0.0.2 remote-as 100 no auto-summary ! address-family ipv4 neighbor cc.cc.cc.cc activate ! iBGP+labels session with RR3 neighbor cc.cc.cc.cc send-label neighbor kk.0.0.2 activate ! eBGP+labels session with ASBR1 neighbor kk.0.0.2 advertisement-interval 5 neighbor kk.0.0.2 send-label neighbor kk.0.0.2 route-map IN in neighbor kk.0.0.2 route-map OUT out no auto-summary no synchronization exit-address-family ! ip classless ! access-list 1 permit ee.ee.ee.ee log access-list 2 permit ff.ff.ff.ff log access-list 3 permit aa.aa.aa.aa log access-list 4 permit bb.bb.bb.bb log ! route-map IN permit 10 match ip address 1 match mpls-label ! route-map IN permit 11 match ip address 3 ! route-map OUT permit 12 match ip address 2 set mpls-label ! route-map OUT permit 13 match ip address 4 ! ip default-gateway 3.3.0.1 ip classless ! end
RR3 is a non MPLS VPN RR that reflects IPv4 routes with MPLS labels to ASBR3 and ASBR4.
ip subnet-zero mpls label protocol ldp mpls traffic-eng auto-bw timers no mpls ip ! interface Loopback0 ip address cc.cc.cc.cc 255.255.255.255 ! interface POS0/2 ip address pp.0.0.1 255.0.0.0 crc 16 clock source internal ! router ospf 30 log-adjacency-changes network cc.cc.cc.cc 0.0.0.0 area 300 network pp.0.0.0 0.255.255.255 area 300 ! router bgp 300 bgp log-neighbor-changes neighbor zz.zz.zz.zz remote-as 300 neighbor zz.zz.zz.zz update-source Loopback0 neighbor yy.yy.yy.yy remote-as 300 neighbor yy.yy.yy.yy update-source Loopback0 no auto-summary ! address-family ipv4 neighbor zz.zz.zz.zz activate neighbor zz.zz.zz.zz route-reflector-client neighbor zz.zz.zz.zz send-label ! iBGP+labels session with ASBR3 neighbor yy.yy.yy.yy activate neighbor yy.yy.yy.yy route-reflector-client neighbor yy.yy.yy.yy send-label ! iBGP+labels session with ASBR4 no auto-summary no synchronization exit-address-family ! ip default-gateway 3.3.0.1 ip classless ! end
ASBR4 belongs to a non MPLS VPN service provider. ASBR4 and ASBR3 exchange IPv4 routes and MPLS labels by means of RR3.
Note |
Do not redistribute eBGP routes learned into iBGP if you are using iBGP to distribute the routes and labels. This is not a supported configuration. |
ip subnet-zero ip cef distributed ! interface Loopback0 ip address zz.zz.zz.zz 255.255.255.255 ! interface Ethernet0/2 ip address qq.0.0.1 255.0.0.0 ! interface POS1/1/0 ip address pp.0.0.2 255.0.0.0 ip route-cache distributed ! interface Hssi2/1/1 ip address mm.0.0.2 255.0.0.0 ip route-cache distributed mpls label protocol ldp mpls ip hssi internal-clock ! router ospf 30 log-adjacency-changes auto-cost reference-bandwidth 1000 redistribute connected subnets passive-interface Ethernet0/2 network zz.zz.zz.zz 0.0.0.0 area 300 network pp.0.0.0 0.255.255.255 area 300 network mm.0.0.0 0.255.255.255 area 300 ! router bgp 300 bgp log-neighbor-changes timers bgp 10 30 neighbor cc.cc.cc.cc remote-as 300 neighbor cc.cc.cc.cc update-source Loopback0 neighbor qq.0.0.2 remote-as 200 no auto-summary ! address-family ipv4 neighbor cc.cc.cc.cc activate neighbor cc.cc.cc.cc send-label neighbor qq.0.0.2 activate neighbor qq.0.0.2 advertisement-interval 5 neighbor qq.0.0.2 send-label neighbor qq.0.0.2 route-map IN in neighbor qq.0.0.2 route-map OUT out no auto-summary no synchronization exit-address-family ! ip classless ! access-list 1 permit ff.ff.ff.ff log access-list 2 permit ee.ee.ee.ee log access-list 3 permit bb.bb.bb.bb log access-list 4 permit aa.aa.aa.aa log ! route-map IN permit 10 match ip address 1 match mpls-label ! route-map IN permit 11 match ip address 3 ! route-map OUT permit 12 match ip address 2 set mpls-label ! route-map OUT permit 13 match ip address 4 ! ip default-gateway 3.3.0.1 ip classless ! end
Related Topic |
Document Title |
---|---|
MPLS |
Standard |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIB |
MIBs Link |
---|---|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFC |
Title |
---|---|
RFC 1700 |
Assigned Numbers |
RFC 1966 |
BGP Route Reflection: An Alternative to Full Mesh IBGP |
RFC 2842 |
Capabilities Advertisement with BGP-4 |
RFC 2858 |
Multiprotocol Extensions for BGP-4 |
RFC 3107 |
Carrying Label Information in BGP-4 |
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 2 | Feature Information for MPLS VPN Inter-AS with ASBRs Exchanging IPv4 Routes and MPLS Labels |
Feature Name |
Releases |
Feature Configuration Information |
---|---|---|
MPLS VPN Inter-AS with ASBRs Exchanging IPv4 Routes and MPLS Labels |
12.0(21)ST 12.0(22)S 12.0(23)S 12.2(13)T 12.0(24)S 12.2(14)S 12.0(27)S 12.0(29)S |
This module explains how to configure an MPLS VPN Inter-AS network so that the ASBRs exchange IPv4 routes with MPLS labels of the provider edge (PE) routers. Route reflectors (RRs) exchange VPN-IPv4 routes by using multihop, multiprotocol, external Border Gateway Protocol (eBGP). This feature uses no new or modified commands. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.