Sei sulla pagina 1di 3

Design Scenario 1

ABC is MPLS service provider which provide its customers (corporates, banks, etc.) with L3VPN
service in order to maintain connectivity among their different entities

MSK bank is one of the most well-known banks which is rapidly growing and expanding to serve
its clients among large geographic area

MSK is currently utilizing MPLS L3VPN service provided by ABC and RIPv2 is the PE to CE routing
protocol in place

A new branch has been established in a rural area which could not be served by the current
service provider: ABC

MSK bank contacted XYZ service provider to check the coverage for their new branch and they
confirmed the service availability but they asked for some time as they were upgrading their
network

XYZ were in the process of deploying a new router to serve as ASBR as they received a lot of
requests from their customers asking for Inter-AS services as well as Internet services running
over their current utilized service: MPLS L3VPN

XYZ deployed the new ASBR and informed MSK bank about their readiness for providing the
service of concern waiting for logistics to take place with ABC service provider

ABC per policy placed by their network designer cannot use back to back VRF option as they
have a lot of customers and they faced scalability and performance issues earlier, as well,
security is a main concern and it is a top priority and no internal information to be leaked
outside their autonomous system, no static default routes to be used anywhere within the
autonomous system as well

The policy also states that for providing Internet access over L3VPN, global RIB is only used for
internal communication and customers VRFs to be placed only on the respective Provider Edge
routers

After agreement with ABC, XYZ discovered that their transmission team made a huge mistake by
assuming the availability of fiber interconnections to the new deployed ASBR and as per the
guidelines followed by the network engineers inside the XYZ service provider, no external
protocols to run on any internal provider edge router

The only available physical connection can be terminated on their PE as can be shown in the
below diagram:
AS 7

R7-
INET

R1- R4-
ASBR ASBR

R2-PE R5-PE
CR

ISP XYZ
ISP ABC (ISIS
R3-CE (OSPF Area R6-CE
Area 49.0001)
0)
AS 10
AS 20

Now, we have to counter for the mistake made by the transmission team as the contract has
been signed and to follow the rules placed by the network team at XYZ in order to serve this
new branch taking into consideration that this branch needs Internet access as well

Please help us filling in the below in order to achieve the service delivery per the design
considerations (core devices are the concern, CEs are out of scope)
VRF Definition
Route Target Filter
Global RIB Redistribution
VRF RIB Redistribution
IGP
IPv4 iBGP
VPNv4 iBGP AS 7
IPv4 eBGP VRF Definition
VPNv4 eBGP Route Target Filter
Next Hop Self R7- Global RIB Redistribution
Static Routes (#) VRF RIB Redistribution
0 1 2 INET IGP
Label Distribution (Intf) IPv4 iBGP
1
1 VPNv4 iBGP
IPv4 eBGP
VPNv4 eBGP
Next Hop Self
VRF Definition Static Routes (#)
Route Target Filter 0 1 2
Global RIB Redistribution
VRF RIB Redistribution Label Distribution (Intf)
IGP 1
IPv4 iBGP 3
VPNv4 iBGP
IPv4 eBGP R1- R4-
VPNv4 eBGP ASBR
Next Hop Self ASBR 1
Static Routes (#)
0 1 2 2
Label Distribution (Intf) 1
VRF Definition 1 2 3 VRF Definition
Route Target Filter Route Target Filter
Global RIB Redistribution
1 Global RIB Redistribution
VRF RIB Redistribution VRF RIB Redistribution
1 IGP
IGP R2-PE 2 R5-PE IPv4 iBGP
IPv4 iBGP
VPNv4 iBGP CR VPNv4 iBGP
IPv4 eBGP 2 3 IPv4 eBGP
VPNv4 eBGP VPNv4 eBGP
Next Hop Self Next Hop Self
Static Routes (#) Static Routes (#)
0 1 2 0 1 2
Label Distribution (Intf) ISP1 (ISIS Area ISP2 (OSPF Label Distribution (Intf)
1 2 R3-CE 49.0001) Area 0) R6-CE 1 2 3
AS 10 AS 20

Potrebbero piacerti anche