Is there any configuration document which explains about MPLS hub and spoke without any tunnel? The requirement is to avoid spoke to spoke communication directly and all traffic from spoke 1 to spoke 2 should be through the hub site, even though the spokes are connected to the same PE router. I tried lab it with VRF and route import/export, but the P router knows all the route and when it reaches the P router, it has the more specific route to spoke 2 and routes it. I wanted to avoid using a GRE/MGRE tunnel between PE to PE and carrying vrf in PE router (spoke 1, spoke 2) end to end.
Is there an option available to achieve this scenario?
Thanks for the update. If we are managing the P/PE router. The PE router will have the route target export and import in spoke and hub side, but the P will have all the specific routes from hub and all the spokes. Should we have route target configured at the P router(vrf)
As Ahmed says the P routers should not have the customer routes.
In an MPLS network the P routers only know how to get to other P routers and the PE routers but they have no knowledge of the networks outside of the MPLS network ie. the customer routes.
The PE routers know the routes that the P routers know so they can send traffic to each other and they also know the routes for the customer networks that are advertised from CE devices.
So when a customer packet comes in to the ingress PE router first lookups where to send the traffic to get to the destination network. The result of this lookup will be another PE. Then it has to find out how to get to the egress PE ie.which P router to send the traffic to. The P routers on the other hand do not care about the customer network, they simply label switch from one P router to another unitl it gets to the egress PE.
So if your P routers are seeing the customer routes it sounds like there is something wrong in the configuration.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...