Remember one thing. In MPLS, everything is end-to-end*. I.e. once the traffic enters MPLS cloud, it cannot be rerouted using the usual IP tricks (summarization, IP routing, etc).
If you wish to divert MPLS traffic, you need to do it at the head-end (ingress LSR). For that, you will indeed need to configure MPLS TE with the explicit-path. [*] There is one specific exception to this rule and that, again, goes back to MPLS TE. You can have protected TE tunnels where one of the intermediate nodes can reroute the LSP in question, but only if primary path fails. Again, in order to do this, new LSP needs to be built (label is added) and original label is preserved on the packet. This is called MPLS FastReroute. -- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert Mailto: [email protected] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Community: http://www.ipexpert.com/communities On Wed, Jan 13, 2010 at 08:59, Taqdir Singh <[email protected]> wrote: > Hi All, > > I have read that in case of classifying MPLS packets, we can only match the > exp bits of top label. > > So that means , there is no way to classify packets on "P" routers based on > the source IP address of an MPLS packet ? > > I was trying to build one scenario. Please have a look on attached diagram. > > Basically I want to match my source address 172.16.10.1 and 182.16.10.1 > when they come to "P" router. > > What I want is whenever I do a ping from CE1 with source address of > 172.16.10.1 to 192.16.10.1 the P router should divert the traffic to PE2. > > and > > when I do a ping from CE1 with source address of 182.16.10.1 to 192.16.10.1 > the P router should divert the traffic to PE3. > > is this possible in MPLS or specific in this scenario and how ? _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
