Metro - Core Inter As

Download PNETLab Platform
PNETLAB Store
PNETLab.com
METRO – CORE INTER AS

(MOBILE BACKHAUL – UNIFIED MPLS FULL NETWORK)
1. Lab Topology:
2. Requirement And Background Theory

2.1 Requirement :
You are asked to use : Making CE-A1 and CE-A2 reachable
2.2 Background Theory:
• IP address and OSPF is preconfigured on all routers

• We need to enable MPLS on routers, except interlink between MTC and ASBR (MTC acts
as role of ASBR in Metro)
• Then configure BGP for VPNv4 and IPv4 LU. CSG and AGG02-1 is VPNv4 neighbor;
AGG02-1 and MTC is both VPNv4 and IPv4 LU neighbor; MTC and RR is VPNv4 neighbor.
• VPNv4 prefix from CSG is advertised to AGG02-1 then to MTC with next-hop is the
Loopback address on AGG02-1. MTC then advertises this prefix to RR with Nexthop
Unchanged to keep the next-hop pointing to AGG02-1. Finally, RR will advertise the
prefix to PE01.
• The same for prefixes from PE01. RR will send VPNv4 from PE to MTC with Nexthop
Unchanged to keep the next-hop pointing to PE1
• CSG receives VPNv4 prefixes from PE01 with next-hop is the PE01's Loopback address.
• PE01 receives VPNv4 prefixes from CSG with next-hop is the AGG02-1's loopback
address.
• In order to make the next-hop reachable, these IPv4 loopback addresses have to be
advertised by BGP from one AS to another AS.
1
PNETLAB Store
PNETLab.com
• We need to create an end-to-end LSP spanning across the boundary between ASes. BGP
ipv4 + Label (RFC 3107) needs to be used between ASBR and MTC. ASBR and MTC
advertise BGP IPv4 towards their iBGP neighbor, needed to set next-hop-self on them.
3. Configuration and Verification
IP loopback on Router as following:

3.1 CSG01: 10.2.3.1
3.2 AGG02-1: 10.2.1.1
3.3 AGG-03: 10.2.1.3
3.4 MTC: 10.2.0.1
3.5 ASBR: 10.0.2.1
3.6 RR: 192.168.2.1
3.7 PE-01: 10.0.1.1
3.1. CSG
1. Enable MPLS
mpls ip
mpls ldp router-id l0
inter e0/0
mpls ip
2. Configure VRF
ip vrf SIGNALING
rd 1:1
route-target both 65101:1
route-target import 65001:1 !!!!!route target from PE1!!!!!
2
PNETLAB Store
PNETLab.com
exit
inter e0/2
ip vrf forwarding SIGNALING
3. BGP
router bgp 65101
bgp router-id 10.2.3.1
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor AGG peer-group
neighbor AGG remote-as 65101
neighbor AGG update-source Loopback0
neighbor 10.2.1.1 peer-group AGG
address-family ipv4
neighbor 10.2.1.1 activate
exit-address-family
address-family vpnv4
neighbor AGG send-community extended
neighbor 10.2.1.1 activate
exit-address-family
address-family ipv4 vrf SIGNALING

3
PNETLAB Store
PNETLab.com
redistribute connected
exit-address-family
3.2. AGG
1. Enable MPLS
mpls ldp
router-id 10.2.1.1
interface GigabitEthernet0/0/0/0
2. BGP
router bgp 65101
bgp cluster-id 3.3.3.3
ibgp policy out enforce-modifications
address-family ipv4 unicast
network 10.2.1.1/32
allocate-label all
address-family vpnv4 unicast
neighbor-group MTC
remote-as 65101
update-source Loopback0
4
PNETLAB Store
PNETLab.com
address-family ipv4 labeled-unicast
next-hop-self
next-hop-self
neighbor-group CSG
remote-as 65101
route-reflector-client
next-hop-self
neighbor 10.2.0.1
use neighbor-group MTC
neighbor 10.2.3.1
use neighbor-group CSG
3.3. MTC
1. MPLS
mpls ldp
5
PNETLAB Store
PNETLab.com
router-id 10.2.0.1
2. BGP
router bgp 65101
network 10.2.0.1/32
allocate-label all
neighbor-group AGG
remote-as 65101
next-hop-self
neighbor-group ASBR
6
PNETLAB Store
PNETLab.com
remote-as 65001
send-community-ebgp
route-policy DEFAULT in
route-policy DEFAULT out
next-hop-self
!!!!DEFAULT policy is preconfigured to pass all routes. In IOS XR with eBGP neighbor, if there is
no route-policy configured, the router will not accept incoming routes nor sends out routes to
the neighbor.!!!!!
neighbor-group RR_CORE
remote-as 65001
ebgp-multihop 20
next-hop-unchanged
neighbor 10.2.1.1
use neighbor-group AGG
neighbor 172.16.12.2
use neighbor-group ASBR

7
PNETLAB Store
PNETLab.com
use neighbor-group RR_CORE
3. Static route
!!!!!!For IOS-XR over Inter-As link there is a different logic as compared to that of IOS. It is
required to configure a static /32 route to ASBR1's interface, so that mpls label is bound for a
/32 prefix. If this is not done then control plane will come up but the traffic will not be
forwarded.!!!!
!!!
router static
172.16.12.2/32 GigabitEthernet0/0/0/0
commit
!!verification mpls binding for static route
3.4. ASBR
1. enable MPLS
mpls ldp
router-id 10.0.2.1
address-family ipv4
8
PNETLAB Store
PNETLab.com
2. BGP
router bgp 65001
allocate-label all
neighbor-group MTC
remote-as 65101
next-hop-self
neighbor-group RR
remote-as 65001
next-hop-self
9
PNETLAB Store
PNETLab.com
use neighbor-group RR
3. Static route
!!!!!!For IOS-XR over Inter-As link there is a different logic as compared to that of IOS. It is
required to configure a static /32 route to ASBR1's interface, so that mpls label is bound for a
/32 prefix. If this is not done then control plane will come up but the traffic will not be
forwarded.!!!!
!!
router static
172.16.12.1/32 GigabitEthernet0/0/0/2
Commit
!!Verification for MPLS binding for static route
3.5. RR
Because eBGP neighbor relationship between RR and MTC is established by using their
loopback. So RR and MTC have to reach their partner loopback each other. Otherwise, there
will be no neighbor. There are several way to make them reachable:
- Advertised loopback addresses into BGP, then at MTC and ASBR, redistribute these IPv4 into
OSPF so that intermediate routers like P1 will know how to forward the prefix.
10
PNETLAB Store
PNETLab.com
- Advertise loopback into BGP and enable MPLS on RR interface towards P router.
Then, connectivity from RR to MTC can be reached by MPLS.
1. Enable MPLS
mpls ldp
router-id 192.168.2.1
address-family ipv4
2. BGP
router bgp 65001
network 192.168.2.1/32
allocate-label all
neighbor-group MTC
remote-as 65101
ebgp-multihop 20
11
PNETLAB Store
PNETLab.com
next-hop-unchanged
neighbor-group ASBR
remote-as 65001
neighbor-group PE-CORE
remote-as 65001
neighbor 10.0.1.1
use neighbor-group PE-CORE

12
PNETLAB Store
PNETLab.com
neighbor 10.0.2.1
use neighbor-group ASBR
neighbor 10.2.0.1
3.6. PE
1. enable MPLS
mpls ldp
router-id 10.0.1.1
address-family ipv4
2. VRF
vrf SIGNALING
import route-target
65001:1
65101:1
export route-target
65001:1
!
13
PNETLAB Store
PNETLab.com
exit
vrf SIGNALING
ipv4 address 172.16.100.1 255.255.255.252
commit
3. BGP
router bgp 65001
network 10.0.1.1/32
allocate-label all
neighbor-group RR
remote-as 65001
use neighbor-group RR
14
PNETLAB Store
PNETLab.com
vrf SIGNALING
rd 10.0.1.1:1
redistribute connected
4. verification
3.8 AGG2-01:
3.9 MTC
15
PNETLAB Store
PNETLab.com
3.10 RR
3.11 PE-01
16
PNETLAB Store
PNETLab.com
3.12 CSG
CSG2-01#show bgp vpnv4 uni VRF SIGNALING labels
Network Next Hop In label/Out label
Route Distinguisher: 10.2.3.1:1 (SIGNALING)
10.0.1.1/32 10.2.1.1 nolabel/24006 → Go to PE1’s loopback, Nexthop is AGG2-1 and VPN Label is 2006
CSG2-01#show mpls forwarding-table 10.2.1.1
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
27 Pop Label 10.2.1.1/32 0 Et0/0 172.16.0.1 → Go to Nexthop 10.2.1.1 by interface e0/0

without label.
!!!!AGG!!!!
17

Metro - Core Inter As

Uploaded by

Copyright:

Available Formats

Metro - Core Inter As

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Metro - Core Inter As

Uploaded by

Copyright:

Available Formats

Download PNETLab Platform

METRO – CORE INTER AS

2. Requirement And Background Theory

• IP address and OSPF is preconfigured on all routers

3. Configuration and Verification

IP loopback on Router as following:

mpls ldp router-id l0

route-target both 65101:1

route-target import 65001:1 !!!!!route target from PE1!!!!!

ip vrf forwarding SIGNALING

router bgp 65101

bgp router-id 10.2.3.1

no bgp default ipv4-unicast

neighbor AGG peer-group

neighbor AGG remote-as 65101

neighbor AGG update-source Loopback0

neighbor 10.2.1.1 peer-group AGG

neighbor 10.2.1.1 activate

neighbor AGG send-community extended

neighbor 10.2.1.1 activate

address-family ipv4 vrf SIGNALING

router bgp 65101

bgp router-id 10.2.1.1

bgp cluster-id 3.3.3.3

ibgp policy out enforce-modifications

address-family ipv4 unicast

address-family vpnv4 unicast

address-family ipv4 labeled-unicast

address-family vpnv4 unicast

address-family vpnv4 unicast

use neighbor-group MTC

use neighbor-group CSG

router bgp 65101

bgp router-id 10.2.0.1

bgp cluster-id 2.2.2.2

address-family ipv4 unicast

address-family vpnv4 unicast

address-family ipv4 labeled-unicast

address-family vpnv4 unicast

address-family ipv4 labeled-unicast

route-policy DEFAULT out

address-family vpnv4 unicast

route-policy DEFAULT out

use neighbor-group AGG

use neighbor-group ASBR

use neighbor-group RR_CORE

!!verification mpls binding for static route

router bgp 65001

bgp router-id 10.0.2.1

address-family ipv4 unicast

address-family ipv4 labeled-unicast

route-policy DEFAULT out

address-family ipv4 labeled-unicast

use neighbor-group MTC

!!Verification for MPLS binding for static route

router bgp 65001

bgp router-id 192.168.2.1

bgp cluster-id 1.1.1.1

address-family ipv4 unicast

address-family vpnv4 unicast