TOPOLOGY for implementing MPLS:

We dont require Core p routers to run BGP .BGP will run

in the provider edge routers only because the top labels
is going to be swapped and top labels is just identifying
PE only.That is the benefits of the Layer 3 VPN that the
p- routers dont have to run BGP.P-router only need to
know all the routes inside the AS for the edges.
Lets route updates are coming from PE4 to the PE3 .PE3
wont send them to PE2 because PE4 is not neighbor to
PE2.So,we have to make PE3 as route reflector in this
case and PE2 being client.We will create another route
reflector PE2 with PE3 as client.
In MP-BGP ,we have to activate BGP for VPNv4.VPNv4 is
simply the customer clients vpn routes.
In the service provider network,top part is ipv4 and
bottom part is vpnv4 traffic.
We need to send community extended attribute by
default.We need it for the details like route targets,ospf
route types and if we want to inject the information
inside the vpn routes.Its better to give send community
both instead of send community extended because if
one PE is using standard and the other is using
extended then it will not send both of them.
In PE1,we have only bgp neighbor i.e PE2.we have to
enable bgp for ipv4 and vpnv4 routes.In PE2,we have 2
bgp neighbor.In PE2 and PE3,we have 2 bgp
neighbors.In
Verification commands:
Sh ip bgp neighbors.