Labels iin MPLS TE environment

I am trying to simulate a MPLS TE FRR with GNS3 and everything seems to work fine. However every time i simulate a failover, the labels seems to change
Is it something expected or a problem with the simualtion engine
When FRR is not active
R1-PE1#traceroute vrf abc 200.200.200.1
*Jan 28 20:32:21.735: %SYS-5-CONFIG_I: Configured from console by console
Type escape sequence to abort.
Tracing the route to 200.200.200.1
1 20.20.20.2 [MPLS: Labels 209/405/607 Exp 0] 560 msec 308 msec 360 msec
2 10.10.10.2 [MPLS: Labels 310/405/607 Exp 0] 268 msec 540 msec 204 msec
3 10.10.10.6 [MPLS: Labels 405/607 Exp 0] 312 msec 312 msec 392 msec
4 200.200.200.1 484 msec * 236 msec
R1-PE1#
When FRR is active
R1-PE1#traceroute vrf abc 200.200.200.1
Type escape sequence to abort.
Tracing the route to 200.200.200.1
1 20.20.20.2 [MPLS: Labels 209/405/607 Exp 0] 420 msec 1124 msec 712 msec
2 30.30.30.2 [MPLS: Labels 510/405/607 Exp 0] 516 msec 480 msec 408 msec
3 30.30.30.10 [MPLS: Labels 405/607 Exp 0] 328 msec 328 msec 220 msec
4 200.200.200.1 648 msec * 500 msec
R1-PE1#
When i bring up my interface again
R1-PE1#traceroute vrf abc 200.200.200.1
Type escape sequence to abort.
Tracing the route to 200.200.200.1
1 20.20.20.2 [MPLS: Labels 209/405/607 Exp 0] 372 msec 324 msec 248 msec
2 10.10.10.2 [MPLS: Labels 312/405/607 Exp 0] 256 msec 772 msec 736 msec .... i see lable 312 instead of 310 ??
3 10.10.10.6 [MPLS: Labels 405/607 Exp 0] 420 msec 328 msec 344 msec
4 200.200.200.1 312 msec * 264 msec
R1-PE1#
i have attached the configs
Ambi

Ambi,
Have you tried the protection setting for LDP/TDP?
This is possible with "mpls ldp session protection" command. I do not know if we have this command to TDP.
Sds,

Similar Messages

Is auto-bw recommended in MPLS TE environment?

Hi Sir,
Is automatic bandwidth adjustment recommended in MPLS TE environment? The configuration of a primary TE tunnel is as follows:
interface Tunnel1
load-interval 30
tunnel mpls traffic-eng auto-bw
Thank you.
B.Rgds,
Lim TS

It depends on your requirement. And how important is the primary path BW for you.
As the traffic already using the backup path as primary may be depleted of BW.
Since these are all knobs or features, there is nothing like only this or that is recommended. you will need to study and baseine your BW requirements and then go ahead with unlimited, auto or fixed.
HTH-Cheers,
Swaroop

MPLS load balancing

Hello,
Graph of the network is in the attachment. I have problem that loadbalanicing among two GigabitEtehernet links in OSPF (between PE4 and P1 router on the picture)doesn't work. Black link goes to 1G/s and begins to drop packets and red one stays empty. Amount of traffic is 1,4Gbps. 700Mb/s from EoMPLS vlan 11 plus 700Mb/s from EoMPLS vlan 12.
Regarding two EoMPLS tunnels, PE4 should balance traffic in CEF and it should look the inner label from MPLS packet.
All routers are Cisco7600
Here is output from PE4
PE4#sh mpls forwarding-table 192.168.0.5 32 detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
395 134 192.168.0.5/32 1573173346488 Gi1/0/0 10.10.1.189
MAC/Encaps=14/18, MRU=9216, Label Stack{134}
001563F33EC0001C0F5C92C08847 00086000
No output feature configured
Per-destination load-sharing, slots: 0 2 4 6 8 10 12 14
134 192.168.0.5/32 130361493 Gi2/0/0 10.10.1.197
MAC/Encaps=14/18, MRU=9216, Label Stack{134}
001563F33EC0001C0F5C92C08847 00086000
No output feature configured
Per-destination load-sharing, slots: 1 3 5 7 9 11 13 15
PE4#sh mpls forwarding-table 192.168.0.105 32 detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
120 49 192.168.0.105/32 0 Gi1/0/0 10.10.1.189
MAC/Encaps=14/18, MRU=9216, Label Stack{49}
001563F33EC0001C0F5C92C08847 00031000
No output feature configured
Per-destination load-sharing, slots: 0 2 4 6 8 10 12 14
49 192.168.0.105/32 217252 Gi2/0/0 10.10.1.197
MAC/Encaps=14/18, MRU=9216, Label Stack{49}
001563F33EC0001C0F5C92C08847 00031000
No output feature configured
Per-destination load-sharing, slots: 1 3 5 7 9 11 13 15
If anyone have idea what could be the problem please give me a hint.

Hi,
Can you just clarify me which command I use on PE4 in order to see which outgoing interface uses EoMPLS VLAN11. For EoMPLS VLAN 12 I use show mpls l2transport vc 12, but I can't use this command for vlan12 because it originates on PE3. On PE4 EoMPLS vlan11 should be MPLS packet. So do I use show mpls forwarding-table 192.168.0.5 detail (or maybe show ip cef exact-route).
In the output below you can see both outgoing interfaces Gi1/0/0(black link) and Gi2/0/0(red). I can't see which one it uses.
PE4#sh mpls forwarding-table 192.168.0.5 32 detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
395 134 192.168.0.5/32 1573173346488 Gi1/0/0 10.10.1.189
MAC/Encaps=14/18, MRU=9216, Label Stack{134}
001563F33EC0001C0F5C92C08847 00086000
No output feature configured
Per-destination load-sharing, slots: 0 2 4 6 8 10 12 14
134 192.168.0.5/32 130361493 Gi2/0/0 10.10.1.197
MAC/Encaps=14/18, MRU=9216, Label Stack{134}
001563F33EC0001C0F5C92C08847 00086000
No output feature configured
Per-destination load-sharing, slots: 1 3 5 7 9 11 13 15
and for CEF otputs are:
PE4#sh ip cef exact-route 192.168.0.1 192.168.0.5
192.168.0.1 -> 192.168.0.5 => label 134 TAG adj out of GigabitEthernet1/0/0, addr 10.10.1.189
But since PE4 is Cisco7600 this command should be relevant and its output shows that Gi2/0/0 as ougoing interface(red link)
PE4#sh mls cef exact-route 192.168.0.1 192.168.0.5
Interface: Gi2/0/0, Next Hop: 10.10.1.197, Vlan: 1023, Destination Mac: 0015.63f3.3ec0

MPLS/VPN network load balancing in the core

Hi,
I've an issue about cef based load-balancing in the MPLS core in MPLS/VPN environment. If you consider flow-based load balancing, the path (out interface) will be chosen based on source-destination IP address. What about in MPLS/VPN environment? The hash will be based on PE router src-dst loopback addresses, or vrf packet src-dst in P and PE router? The topology would be:
CE---PE===P===PE---CE
I'm interested in load balancing efficiency if I duplicate the link between P and PE routers.
Thank you for your help!
Gabor

Hi,
On the PE router you could set different types and 2 levels of load-balancing.
For instance, in case of a DUAL-homed site, subnet A prefix for VPN A could be advertised in the VPN by PE1 or PE2.
PE1 receives this prefix via eBGP session from CE1 and keep this route as best due to external state.
PE2 receives this prefix via eBGP session from CE2 and keep this route as best due to external state.
                             eBGP
                     PE1 ---------CE1
PE3----------P1                          Subnet A
                     PE2----------CE2 /
                            eBGP
Therefore from PE3 point of view, 2 routes are available assuming that IGP metric for PE3/PE1 is equal to PE3/PE2.
The a 1rst level of load-sharing can be achieve thanks to the maximum-paths ibgp number command.
2 MP-BGP routes are received on PE3:
PE3->PE1->CE1->subnet A
PE3->PE2->CE2->subnet A
To use both routes you must set the number at 2 at least : maximum-paths ibgp 2
But gess what, in the real world an MPLS backbone hardly garantee an equal IGP cost between 2 Egress PE for a given prefix.
So it is often necessary to ignore the IGP metric by adding the "unequal-cost" keyword: maximum-paths unequal-cost ibgp 2
By default the load-balancing is called "per-session": source and destination addresses are considered to choose the path and the outgoing interface avoiding reordering the packets on the target site. Overwise it is possible to use "per-packet" load-balancing.
Then a 2nd load-sharing level can occur.
For instance:
         __P1__PE1__CE1
PE3           \/                   Subnet A
        \ __P2__PE2__CE2
There is still 2 MP-BGP paths :
PE3->P1->PE1->CE1->subnet A
PE3->P1->PE2->CE2->subnet A
But this time for 2 MP-BGP paths 4 IGP path are available:
PE3->P1->PE1->CE1->subnet A
PE3->P1->PE2->CE2->subnet A
PE3->P2->PE1->CE1->subnet A
PE3->P2->PE2->CE2->subnet A
For a load-balancing to be active between those 4 paths, they must exist in the routing table thanks to the "maximum-path 4 "command in the IGP (ex OSPF) process.
Therefore if those 4 paths are equal-cost IGP paths then a 2nd level load-balancing is achieved. the default behabior is the same source destination mechanism to selected the "per-session" path as mentionned before.
On an LSP each LSR could use this feature.
BR

Wred based on MPLS exp bits on 12000

I want to use WRED with MQC on 12000 but there is no mpls/exp-bits statment on the "random-detect" command.
I found this note at cisco documentation:
Note: The legacy CLI also uses the precedence syntax for Multiprotocol Label Switching (MPLS) traffic. The router treats the MPLS bits as though they are IP Type of Service (ToS) bits and puts the appropriate packets into the correct queues. This is not at all true for MQC.
so, is there a way to use WRED with MPLS EXP-bits on MQC?

Hi,
As fas as I know the solution is as follows:
1. Use MQC on the inbound interface of your P/PE LSR to match your desired traffic and set discard-class
2. Use MQC on the outbound interface of your P/PE
LSR to set desired WRED policy based on discard-class you marked in previous step. You also need to mark WRED as "discard-class-based"
Here is an example:
Inbound:
class-map class1
match XXXXX
class-map class2
match YYYYY
policy-map in-policy
class class1
set discard-class 0
class class2
set discard-class 1
Outbound:
policy-map out-policy
class class-default
random-detect discard-class-based
random-detect discard-class 0 10 20 5
random-detect discard-class 1 20 30 5
Hope that helped.
David

IOS support for MPLS QoS as stated in RFC 3270 L-LSP

Hi,
does anybody know something about the degree of implementation of RFC 3270 (Multi-Protocol Label Switching (MPLS) Support of Differentiated Services), particularly on the classification based on Labels (L-LSP)?
From what is detailed on the CCO it seems that only Exp-bits based LSP are supported (configuring all links along the path for the proper data plane behaviour based on the Exp-bits values): E-LSP
Thanx in advance
Francesco

I guess, in PPP and LAN environments, E-LSP is the preferred method and in the ATM only L-LSP is possible. Maybe cisco chose to implement only the E-LSP for the LAN and PPP environments, i am not sure though.
Anyone knows this for sure?
Check out http://www.cisco.com/warp/public/732/Tech/mpls/docs/mpls_qos_jayk.ppt for more details on MPLS-QoS

Carrying CLNS inside MPLS VRF

Is there a way to carry CLNS traffic inside MPLS VRF?

To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it floods Multiprotocol Label Switching (MPLS) traffic engineering (TE) link information into the indicated IS-IS level, use the mpls traffic-eng command in router configuration mode

MPLS / VRF

Hello,
how is it possible that VRF can be routed from one site to another site by the core routers?
It is clear that the VRF must be configured and each interface is to be assigned.
In addition, the IGP / redistribution between PE-CE and MP-BGP is to be configured.
I found the following configurations in the documentation to configure the PE-Routers in the Core:
(Configuring MP-BGP):
PE 1:
router bgp 1
x.x.x.x neighbor remote-as 1
x.x.x.x neighbor update-source loopback0
address-family vpnv4
neighbor x.x.x.x activate
x.x.x.x neighbor send-community Both
exit-address family
PE 2:
router bgp 1
x.x.x.x neighbor remote-as 1
x.x.x.x neighbor update-source loopback0
address-family vpnv4
neighbor x.x.x.x activate
x.x.x.x neighbor send-community Both
exit-address family
What additional commands are required that a router from one location can ping a router to another location in the same VRF successful?
Thanks for your help!

Hello,
From the above configuration it looks like that you have configured MP-BGP. This is important for VRF to VRF communication over MPLS enabled backbone (MPLS VPN) since MP-BGP propagates virtual routing and forwarding (VRF) reachability information to all members of a VPN community. MP-BGP peering must be configured on all PE devices within a VPN community.
Below are 2 links which clearly suggests what all things are required for VRF to VRF communication and reason for it.
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l3_vpns/configuration/15-mt/mp-l3-vpns-15-mt-book/mp-bgp-mpls-vpn.html
http://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/13733-mpls-vpn-basic.html
HTH,
Nikhil

MPLS IP-VPN compatibility

Hi, we've lots of members running on 2 Cisco 2611 with HA configured (HSRP, ISDN backup, etc). There is 2 scenarios here as follow:
i. 2 units of 2611 routers with each 2611 have a dedicated LL, one connected to HQ, the other connected to DR.
ii. 2 units of 2611 routers with only one have a dedicated LL, the other provide ISDN DDR when the LL on the other failed.
iii. 1 unit of 2611 routers with trunking to a 2950 switch, have a dedicated LL and ISDN DDR.
For the first scenario, when the members having 2 dedicated LL, normally it is from different telco providers. Now there's one single telco offering us the chance to upgrade to MPLS IP-VPN for an interesting rate. What I'm wondering is, can it work that way?
I have my 6509s with Sup720 at both HQ and DR, I have a good vendor all the while, if part of the members start to accept the MPLS-VPN, is there any integration problem? The HA configured will still work?
The thing that worried me most is the core layer part, since the member get the router through a router distribution from the core router in EIGRP, and the ISDN DDR will redistribute the static when the ISDN is active. How MPLS fit into my network?

Hello,
In principle everything can work. The dessign in question has one leased line (or ISDN) to the HQ and another path through a MPLS VPN. The issue you will have to deal with is to carefully design your dynamic routing. In case you have EIGRP, then an internal route will always be prefered over an external route. It is most likely to get external routes through the MPLS VPN - depending on implementation details.
Thus you might have the problem of proper primary/backup path selection and also with routing loops. The underlying reason for both is the redistribution in MP-BGP at the MPLS PE router.
You need to get more details on the implementation in the SP network to avoid any pitfalls. EIGRP supports backdoors in an MPLS VPN environment, but the question is, whether your telco does as well.
So it might work, but careful routing design is a must and involves you and the telco. HA is still possible, ISDN backup is possible as well. Depending on your specific implementation details you might need some route tagging and redistribution filters implemented by yourself or the telco to avoid the aforementioned problems.
Hope this helps! Please rate all posts.
Regards, Martin

MPLS over GRE tunnles

HI : Are there any MTU issues of running MPLS over GRE tunnels??
what will be the MTU size ?
thnak you

GRE has an overhead of 24 bytes, and can directly interfere with the MPLS overhead. The MTU associated with an MPLS packet is broken down like so:
Ethernet Payload - 1500
802.1q header - 18
AToM Header - 4 (Required for ATM and FR only)
AToM Label - 4
LDP Label - 4
TE Label - 4
MPLS Fast Reroute - 4
Total = 1538
Granted, you may not configure all of those features above into your MPLS network, this is a good baseline to use for the MPLS MTU. You need to configure the core network to accept an MTU of at least 1538 bytes, without GRE.
You need to ensure that your GRE tunnels can support an MTU greater than 1562 if you plan to implement additional MPLS features like TE and AToM.

What RFC for MPLS is supported?

Hi,
does anybody know what rfc's regarding mpls are supported by cisco (f.e. ASR9000 or Nexus 7000)?
TiA,
Stephan

Hi Stephan,
this is the list for ASR9k:
RFC 2547, BGP/MPLS VPNs
RFC 2702, Requirements for Traffic Engineering Over MPLS
RFC 2858, Multiprotocol Extensions for BGP-4
RFC 3031, Multiprotocol Label Switching Architecture
RFC 3032, MPLS Label Stack Encoding
RFC 3063, MPLS Loop Prevention Mechanism
RFC 3140, Per Hop Behavior Identification Codes
RFC 3270, Multi-Protocol Label Switching (MPLS) Support of Differentiated Services (E-LSPs only)
RFC 3443, Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks
RFC 3469, Framework for Multi-Protocol Label Switching (MPLS)-based Recovery
RFC 3564, Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
RFC 4124, Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
RFC 4127, Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.
RFC 3815, Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)
RFC 4448, Encapsulation Methods for Transport of Ethernet over MPLS Networks
RFC 5462, Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field.
HTH,
Ivan.

Ask The Expert: Understanding, Implementing, and Troubleshooting Cisco Prime Network

Ask questions and learn about Cisco Prime Network with Cisco experts Vignesh Rajendran Praveen and Jaminder Singh Bali.
Cisco Prime Network is and Cisco Prime Network provides cost-effective device operation, administration and network fault management for today’s complex and evolved programmable networks (EPNs). It is a single solution to support both the traditional physical network components, as well as compute infrastructure, and the virtual elements found in data centers. Automated configuration and change management combined with advanced troubleshooting and diagnostics greatly help service providers enable proactive service assurance. Additionally, the flexible and extensible architecture is designed to support the multivendor environment, helping to lower operational costs.
This event runs January 5 through January 16, 2015.
Vignesh Rajendran Praveen is a High Touch Engineer with the Focused Technical Services team supporting Cisco's major Service Provider customers in Routing, Switching, Multiprotocol Label Switching (MPLS) technologies and Cisco Prime Network related issues. Previously at Cisco he has worked as a Network Consulting Engineer for Enterprise Customers and as a Customer Support Engineer for Service Provider customers. He has been in the networking industry for ten years and holds CCIE certification (#34503) in the Routing and Switching as well as Service Provider tracks.
Jaminder Singh Bali is a Customer Support Engineer working in SP-NMS TAC team, supporting Cisco's major service provider customers in Cisco Prime Network, Performance and Prime Central related issues. His areas of expertise include Oracle, Linux and NMS applications. He has been in the industry for past six years.
Remember to use the rating system to let the experts know if you have received an adequate response.
The Experts might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation in Network Infrastructure community, sub-community, LAN, Switching and Routing discussion forum shortly after the event. This event lasts through January 16, 2015. Visit this forum often to view responses to your questions and the questions of other community members.

Hello Jerome,
A variety of Cisco devices are supported by the the Cisco Prime Network. I would encourage you to go through the below links on the user guide depending the version of Cisco Prime Network being used.
"Cisco Prime Network Supported Cisco Virtual Network Elements (VNEs)"
"Cisco Prime Network Supported Cisco VNEs - Addendum"
Below is the link for the user guide.
http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-network/products-user-guide-list.html
Hope this would help in providing you more clarity.
***********Plz do rate this post if you found it helpful*************************
Thanks & Regards,
Vignesh R P

Path Selection between 10 gig fiber and microwave

Hello everyone,
my network is running OSPF as an IGP, i have a 10 gig Ethernet fiber connected between two sites and a microwave link as a redundant connection.
since ospf metric is cost ( or bandwidth ), the 10 gig ethernet connection is always preferred. however, sometimes the 10 gig link is flapping or the bit error rate is bad, is there anyway to change the path selection to go through the microwave when the bit error rate in the 10 gig link is bad or the link flaps ?
basically can we make the path selection based on anything than the speed or cost ?

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Bandwidth can be a metric to OER/PfR. Much else can be used by OER/PfR.
The intent of this technology is sort of described by the names, Optimized Edge Routing (v1) and Performance Routing (v2).
Both can account for path bandwidth and/or analyze performance.
Understand typical dynamic routing protocols keep track of paths between source and destination and some have a way to "weight" paths (for example, OSPF link cost [which by RFC, hasn't nothing to do with bandwidth, but is often based on that]).
OER/PfR, for example, can run their own SLA tests.
Years ago, I set up OER in large dual MPLS/VPN environment. Our initial "problem", after activation, our WAN performance monitoring tools (and our users!) no longer "saw" any WAN performance issues. They were still happening, but OER "saw" them first, and worked around them before the monitoring tools saw them.

Oracle 9i on CentSO 5

Hi!
I tried to install Oracle 9i on a machine running CentOS 5. In order to complete the process I followed the instructions given at this address: http://ivan.kartik.sk/oracle/install_ora9_fedora.html. Everything worked fine until I run the Oracle universal installer. I mention that I used Java 6 from Sun all the time and modified the .bash_profile and oraparam.ini files to reflect that. I set up all that was needed and then clicked the ¨Install¨ button. In the window with the progress bar there were some labels: ¨Installing Java Runtime Environment 1.1.8.1.0¨, ¨Link pending¨ and ¨Copying jre¨. From this point nothing happened. I waited for ten minutes with zero processor activity then closed it. I also tried with selinux disabled and on a Debian 4 system and the whole scenario repeated.
Do you know what is causing this and could I fix it?
Thanks!

Hi,
There are two common causes for this issue:
1) Not using fully qualified hostname.If the output from the /bin/hostname command is not a fully qualified hostname, contact your Linux system administrator
2) Not having the environment variable LD_ASSUME_KERNEL set.set it using the syntax below:
export LD_ASSUME_KERNEL=2.4.19
Then,re-start OUI and start the installation.
Regards
Terry

Ask the Expert: Packet Capture Capabilities of Cisco Routers and Switches

With Rahul Rammanohar
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about packet capture capabilities of Cisco routers and switches.
In May 2013, we created a video that included packet capture capabilities across multiple Cisco routers and switches. For each product, we began with a discussion about the theory of the capabilities, followed by an explanation of the commands, and we concluded with a demo on real devices. In this Ask the Expert event, you’re encouraged to ask questions about the packet capture capabilities of these Cisco devices:
•       7600/6500: mini protocol analyzer (MPA), ELAM, and Netdr
•       ASR9k: network processor capture
•       7200/ISRs: embedded packet capture
•       Cisco Nexus 7K, 5K, and 3K: Ethanalyzer
•       Cisco Nexus 7K: ELAM
•       CRS: show captured packets
•       ASR1K: embedded packet capture
More Information
Blog URL: Packet Capture Capabilities of Cisco Routers and Switches
Watch the Video: https://supportforums.cisco.com/videos/6226
Hitesh Kumar is a customer support engineer in the High-Touch Technical Services team at Cisco specializing in routing protocols. He has been supporting major service providers and enterprise customers in routing, Multiprotocol Label Switching (MPLS), multicast, and Layer 2 VPN (L2VPN) issues on routing platforms for more than three years. He has more than six years of experience in the IT industry and holds a CCIE certification (number 38757) in service.
Rahul Rammanohar is a technical leader with the High-Touch Technical Support Team in India. He handles escalations in the area of routing protocols and large-scale architectures for devices running Cisco IOS, IOS-XR, and IOS-XE Software. He has been supporting major service providers and large enterprise customers for routing, MPLS, multicast, and L2VPN issues on all routing platforms. He has more than 13 years of experience and holds a CCIE certification (number 13015) in routing/switching and service provider.
Remember to use the rating system to let Hitesh and Rahul know if you have received an adequate response.
Because of the volume expected during this event, Hitesh and Rahul might not be able to answer each question. Remember that you can continue the conversation in the Service Provider, sub-community forum shortly after the event. This event lasts through November 1, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Erick
    Thanks for the topology. The trigger will be different for labelled packet as you would need to mention the values of labels too in the trigger.
     Below are two examples of one or two labels being used, it depends on where you are capturing the packet in mplsvpn scenario which will decide teh number of labels being imposed on the packet.
Trigger for one label. (if the router on which you are capturing the packet PHP is being performed)
VPN label - 5678
Source Address - 111.111.111.111
Destination Address - 123.123.123.123
show platform capture elam trigger dbus others if data = 0 0 0 0x88470162 0xE0000000 0 0 0x00006F6F 0x6F6F 7B7B 0x7B7B0000 [ 0 0 0 0xffffffff 0xf0000000 0 0 0x0000ffff 0xffffffff 0xffff0000 ]
Trigger for two labels. (for other core routers)
IGP label - 1234
VPN label - 5678
Source Address - 111.111.111.111
Destination Address - 123.123.123.123
show platform capture elam trigger dbus others if data = 0 0 0 0x8847004D 0x20000162 0xE0000000 0 0 0x00006F6F 0x6F6F7B7B 0x7B7B0000 [ 0 0 0 0xffffffff 0xf000ffff 0xf0000000 0 0 0x0000ffff 0xffffffff 0xffff0000 ]
    You can check the labels being used (by using show ip cef <> details) and covert their values to hex and change the trigger accordingly.
     I have changed the colors for better understanding. If you notice carefully in the trigger the values for ip address, labels have just been converted to their respective hex values which could be replaced.
     Please let me know if this helps.
Thanks & Regards
Hitesh & Rahul

Labels iin MPLS TE environment

Similar Messages

Maybe you are looking for