#no mpls ip propagate-ttl cmd question-?

Hi:
When this cmd. is enabled both on PE1 and PE2 across a MPLS core, why does the trace output show the egress PE2 router in the output?
I have CE1->PE1->P->PE2->CE2.
I am tracing to the lo0 of CE2 10.1.8.8
PE1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
PE1(config)#no mpls ip propagate-ttl
PE1(config)#end
PE2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
PE2(config)#no mpls ip propagate-ttl
PE2(config)#end
CE1#tr ip 10.1.8.8
Type escape sequence to abort.
Tracing the route to 10.1.8.8
1 10.1.17.1 28 msec 28 msec 28 msec
2 10.1.58.5 168 msec 180 msec 168 msec
3 10.1.58.8 112 msec * 112 msec
CE1#
As you can see, 10.1.58.5 is the PE2 intf. to CE2. I was hoping to see only 2 hops.
Now the doc for this cmd does say that it sometimes shows the egress provider router.
Is this based on IOS or router model?
Or just another bug ;->
Thx.

Thanks Harold!!
I was going by the example shown in the pdf for MPLS Technology Essentials where they only showed 2 hops, the 1st PE and then CE2 and thus....(they did state that sometimes the egress PE would also show up)....

Similar Messages

  • CalcMgrCmdLineLauncher.cmd question

    Hi all,
    I am trying to automate to run a business rule with the CalcMgrCmdLineLauncher utility.  Thanks to John's blog entry (More to life than this...: ODI Series – Launching Calculation Manager rules) I was able to create a batch script, however I am getting this error message when I run the batch.
    Loaded Version of Essbase RTC: 0xb1221
    Launch Vars: {SCENARIO=Forecast, VERSION=Working, ENTITY=1_BOALT, YEAR=FY14}
    FATAL - Failed to execute getRTPs().Unable to find Rule AggEntity.xml deployed i
    n plan type CalPlan in the repository.
    FATAL - Failed to execute getRule().Unable to find Rule AggEntity.xml deployed i
    n plan type CalPlan in the repository.
    I wonder if this is due to the RTPs are being hidden.  There are 4 variables (RTPs) in this business rule and they are all hidden with the below values:
    - CurrentYear: &current year of view
    - Version: &current stage
    - Scenario: &current scenario
    - Organization: &MyOrg
    I also thought maybe my RTP file was wrong so I changed it, but got a similar error message:
    Loaded Version of Essbase RTC: 0xb1221
    Launch Vars: {SCENARIO=&current scenario, VERSION=&current stage, ENTITY=&MyOrg,
    YEAR=&current year of view}
    FATAL - Failed to execute getRTPs().Unable to find Rule AggEntity.xml deployed i
    n plan type CalPlan in the repository.
    FATAL - Failed to execute getRule().Unable to find Rule AggEntity.xml deployed i
    n plan type CalPlan in the repository.
    null
    I don't know why it says unable to find Rule AggEntity.xml.  It is in the repository.  It is one of the most commonly used BRs in the system.
    Does anybody know what I am doing wrong here?
    Thanks,
    Mehmet

    I guess you don't need the "xml" extension in the business rule.  The script worked without it..

  • How to hide trace route layer 3 hop?

    My set up is MPLS router--- Internet edge-------ISP
    I am advertising public ip prefix from MPLS to internet edge and then to ISP
    when i trace route from internet to the public prefix i advertised, i am seeing the MPLS private IP which is expected.
    Basically i wanted to hide this from the trace route results i.e, when the user tries to trace route to the public ip from the internet he should  NOT see the private ip at all. "no icmp unreahcable" might give a * result in the trace route last hop but i wanted hide it .. is it possible?

    Hi,
    Traceroutes takes into account the TTL value, be it MPLS packet or IP packet.
    on the edge of the IP & MPLS network , TTL field get copied from one to another & the traceroute works properly. But "no mpls ip propagate-ttl" can diable this automatic copying the TTL value field. Hence, your traceroute will drop on edge/boundary, this generally done by ISP to hide their ip address from the traceroute path.
    mpls ip propagate-ttl
    To control the generation of the time-to-live (TTL) field in the Multiprotocol Label Switching (MPLS) header when labels are first added to an IP packet, use the mpls ip propagate-ttl command in global configuration mode. To use a fixed TTL value (255) for the first label of the IP packet, use the no form of this command.
    mpls ip propagate-ttl
    no mpls ip propagate-ttl [forwarded | local]
    The Traceroute Command in MPLS
    http://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/26585-mpls-traceroute.html
    - Ashok
    Please rate the post or mark as correct answer as it will help others looking for similar information

  • During tracert, PE (7603) sends out normal IP packets with TTL=0 ?

    Hi All,
    Below is my network diagram:
    Clients---PE1(10720)---P----PE2(7603 w/Sup720)--Cat6513---FW----Internet
    After hiding MPLS core by issuing "no tag-switching ip propagate-ttl forwarded", I tracert from Clients, I see 2 lines of ICMP ttl-exceeded message replied from Cat6513, as follows:
    1 <1ms <1ms <1ms 202.78.230.1
    2 <1ms <1ms <1ms 202.78.225.30
    3 <1ms <1ms <1ms 202.78.225.30
    4 <1ms <1ms <1ms 202.78.225.46
    Using sniffer, I realise that PE2(7603) sends TTL of 0 to the Cat6513 which makes Cat6513 send the 1st reply. Then, PE2(7603) sends TTL of 1 to the Cat6513 which makes Cat6513 send the 2nd reply.
    Any idea, pls help.

    Duc,
    I was assuming a non MPLS VPN network when I stated that you should see both the ingress and egress PE in the output of the traceroute. In an MPLS VPN scenario, it is correct that you will not see the egress PE if the VPN label it not an aggregate label.
    In any case I found the DDTS that is causing you to to see the CE twice in the output of the traceroute. It is CSCef16357. As explained in the release notes it is a HW issue that can't be fixed by software. For more information, please refer to the release notes:
    http://www.cisco.com/cgibin/Support/Bugtool/onebug.pl?bugid=CSCef16357&Submit=Search
    Hope this helps,

  • IS O&G - is it possible to use MPL without activating the ECC- DIMP?

    Hi
    We are an Oil and Gas industry and activated IS oil and gas in ECC6.0, our requirement is to use functionality such as Master Parts list which is there in ECC-DIMP under configuration control, as some companies within same group where MPL is required .
    The question is it possible to use MPL without activating the ECC- DIMP
    Request you to please help us to understand.
    Regards

    Hi Venkat,
    If a report is created over a DSO, it pulls data from the active table of a DSO. So as suggested in all the posts above it is not possiable to report on the DSO without activating it.
    Activation of DSO only allows to generate SID's to link transaction data and master data, SID's could also be generated at the time of reporting (When the report fetches data from BI server, but for the SID generation data is needed in active table). Also activation checks the correctness of data etc.
    Could you please let know why you want to report on the unactive request, is it having some problem with activation?
    Regards,
    Pankaj

  • 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 TE Bandwidth

    Dear community members,
    I am CCNP R&S and i have some trouble in understanding mpls TE tunnel. My question is if the bandwith is reserved over the tunnel will that bandwidth be usable for other data over that link or not ? e.g. if the reserved bandwidth on the link is configured to be 10Mbps and currently the data for which the tunnel is reserved is only 5Mbps. where will be that remaining 5Mbps ?
    Thank you 
    Best Regards
    Abdul Basit

    Hello abdulbasitkhan,
    The RSVP Bandwidth Reservation is done in control plane only ( not actual bandwidth reservation) so any traffic can utilize the underlying interfaces and compete with the TE tunnel traffic normally.
    For your example:
    My question is lets bandwidth is available and the requested bandwidth for the tunnel is 10Mbps but the data that initiated the tunnel is much less than 10Mbps, so here again will the remaining bandwidth can't be reused by other data over the link as RSVP reserved it ?
    Yes, the other data can normally use the remaining Mbps and competes with the TE tunnel data
    I hope that i answered your question

  • Convert HDLC T-1 to sub-if to configure multi-vrf CE

    We are converting a small ISP to MPLS and have a quick question-
    We have several sites connected using a basic HDLC T-1 from what is going to be the CE to the PE (all isr's running 12.4)
    Over this one link we will have MPLS (with the PE's side being in a vrf), and we would like to continue bringing in internet from the PE's global routing table that we are doing now.
    I know you can simply use frame relay with sub-interfaces to do this... only we cant provision frame-relay service to these CE's...
    Any ideas how we could segment these HDLC's into 2 sub-interfaces (one with private addressing for the MPLS wan) and one with public ip addressing for the internet circuit.
    I've been thinking about gre 2 tunnels between the PE/CE just to make this work, with one TUNNEL being in the PE's VRF for the customer, the other remaining in the global routing table.
    Oh, and I know you can just route the internet into the VRF on the PE, but that is not desirable here.
    Thanks,
    Joe

    I would say you need to use VRF-lite in order to do this efficiently.
    All other solutions will require tunnelling which is not efficient.
    One possibility is to have a single site that has the routes to the Internet i.e. a central DC site. This would mean that a default route would take all internet bound traffic to the DC whereby it will be routed to an 'Internet' circuit. This is a common method and usually involves a MPLS L2Transport circuit into the DC site which terminates between an Internet router and a CE/Fw. This will require a L2 protocol that can deliver discreet L2 paths i.e. FR or Ethernet VLANs. The advantage is reduced tunnelling but introduces suboptimal/hairpin routing.
    An alternative is L2TPv3 from each CE to an Internet CE

  • EXP propagation

    Hi,
    Can anyone shed some light on the issue of EXP field propagation as labels are removed or added?
    Specifically....
    1. I understand that at ingress of MPLS cloud you would use class-based policy to apply the initial EXP value based on some class-map matching by applying service-policy in either inbound direction in case you want to do on the inbound interface or in the outbound direction if you want to do on the outbound interface (probably frequently used in MPLS DS-TE), however my question is how will this field travel along the LSP?
    2. Do you have to make sure that you apply proper EXP value at any point in LSP when label is being stripped off or applied or is it automatically copies between the labels?
    3. Also, at egree, do you usually match on EXP value to apply proper QoS, like LLC. For example,
    class-map exp5
    match mpls experimental topmost 5
    policy-map premium
    class exp5
    priority 512
    interface fastethernet0/0
    service-policy output premium
    4. Cisco documentation speaks of three modes: Uniform, Pipe and Semi-pipe. Are these simply concept of implementations or are they really configuration parameters?
    Your help would be appreciated.
    Thanks,
    David

    Hi,
    1) the default for a PE is to copy IP precedence to MPLS exp bits in all imposed labels. With a policer you can choose to set exp to different values.
    2) the popped label exp bits are not copied to next label automatically. Assuming however that you set all exp bits to the same value during imposition this should not impose a problem.
    3) This would not work as the output traffic is (presumably) IP. so the trick is:
    class-map exp1
    match mpls exp topmost 1
    policy-map exp-mapping
    class exp1
    set qos-group 1
    class-map qos-group
    match os-group 1
    policy-map customer
    class qos-group
    bandwidth 128
    interface FastEthernet0/1
    description from core
    service-policy input exp-mapping
    interface Serial1/0
    description to CE
    service-policy output customer
    4) The qos models are concepts. Uniform mode means you can (and will) rewrite DSCP as the settings throughout IP/MPLS are using a uniform classification scheme. Pipe and short pipe model let you transport DSCP unchanged through an MPLS domain by setting exp bits ONLY and not rewriting DSCP in any place. This is used in case the customer has different settings than the SP and does not want them to be modified.
    Hope this helps
    Martin

  • VPLS works with the PVLAN

    Dears ,
    here is my  topology
    4507(Edge)--layer2-->(Core)6509-->ASA 5500-->ASR1002        ---MPLS CLOUD --->
    In the 6509 and 4507 i am working with PVLANs , i would like to extend the layer2 (PVLANs) to the MPLS cloud using VPLS my questions are :-
    1-I am using Sup 2T in 6500 is there any problem coz i read that
    ( With a Supervisor Engine 2T, Layer 2 protocol tunneling is not supported with VPLS (CSCue45974). )
    2-is there any problem extending PVLAN on the VPLS cloud .
    3- is there any issue i have to take care regarding Firewall or ASR1002

    Post Author: amr_foci
    CA Forum: Xcelsius and Live Office
    if you are asking about the supported excel functions in Xcelsius, you can check this link http://www.xcelsius.com/help/xcelsiusHelpXLV4/source/functionsAlpha.htm
    and also that link may helps you
    http://www.xcelsius.com/help/xcelsiusHelpXLV4/source/ug_FAQPro.htm
    good luck

  • URGENT: QoS Design on Data Center MPLS - MediaNet Question...

    Hello,
    I am posting this in hopes I can get some guidance from anyone who has done this in the field.  We have a large enterprise customer with 21 sites all around the world, they have Verizon MPLS and are experiencing QoS related issues on their WAN regarding Video/Voice.  We have proposed remediating their network acccording to the Enterprise QoS SRND 3.3 and the new MediaNet SRND to account for Video and TP QoS (     
    http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html )
    Here is the problem/question that was proposed in our presales meeting and I honestly don't know where to look for an answer... I am not asking for anyone to design a solution for me, just merely point me in the right direction:
    The Data Center has a ~40MB MPLS Connection ( full mesh ) into the cloud ( Verizon )
    Site A has a 8MB connection
    Site B has a 4MB connection
    I know on the Service policy and the interfaces at SiteA and SiteB I can assign "Bandwidth xxxx" and use ~95% of the bandwidth to do queuing and shaping/policing ect.  I am not concerned with SiteA and SiteB, that I think I can handle...
    Question was posed from the customer, "How can we ensure at the DataCenter level the 40MB MPLS is "chopped" up so that only 8MB of the total speed goes to SiteA ALONG with an attached QoS policy designed for that specific site, as well as ensure only 4MB goes to SiteB with an attached QoS policy.
    So I am looking for a way to allocate bandwith per site on the DC 40MB connection going into the cloud ( so that SiteB cannot use more than 4MB ) and attach a MediaNet specific QoS Service policy to that site.  The customer does not have seperate MPLS circuits for each site, they all come into the DC on 40MB shared ethernet connection ( no VC, or dedicated circuits to other sites ). 
    Any thoughts on if this is possible? 
    Thanks!
    Alex

    This is an example I have seen and I hope that is useful to you.
    Site A
    Subnet: 172.16.1.0/24
    Site B
    Subnet:172.16.2.0/24
    HeadOffice:
    ip access-list extended Site_A
    permit ip any 172.16.1.0 0.0.0.255
    ip access-list extended Site_B
    permit ip any 172.16.2.0 0.0.0.255
    class-map match-any Site_A
    match access-group name Site_A
    class-map match-any Site_B
    match access-group name Site_B
    policy-map To_Spokes
    class Site_A
    shape average 8000000
    service-policy Sub_Policy(Optional)
    class Site_B
      shape average 4000000
      service-policy Sub_Policy(Optional)
    class class-default
      shape average 28000000
      service-policy Sub_Policy(Optional)
    Interface G0/0
    Description To MPLS cloud
    bandwidth 40000000
    service-policy output To_Spokes
    interface G0/1
      Description To HeadOffice
    bandwidth 40000000
    service-policy output To_Spokes
    It would be greatly appreciated if someone can correct this or improve it as I am still learning.
    Please see the netflow graph from one of our routers using a similar policy as above.

  • MPLS question

    Hi all. We are in the midst of rolling out Mpls to 5 of our remote sites. 3 sites will have a cir of 10 mbps, 1 100mbps, and another 250 mbps. I am planning on running ospf in each site. My question is, will a 2821 router at each site be sufficient. Voice and data will be in use, so traffic shaping/qos will need to take place on these routers. Will this work. Thanks for your help.

    Ah, you didn't mention you were using Metro Ethernet connections. 3750 will easily handle 100 or 250 Mbps.
    As for tips for QoS, insure your voice is sent first. All data could be placed in a normal class or you could split it, with the 3 remaining classes, into critical, normal and scavenger if using non ES ports. Doubtful you need to do much more if using one of the ES ports, although it would be nice if you could do FQ in class default like you can on WAN routers but don't believe you can.
    QoS document: http://www.cisco.com/application/pdf/en/us/guest/netsol/ns432/c649/ccmigration_09186a008049b062.pdf
    Latest 3750 QoS config guide section: http://www.cisco.com/en/US/products/hw/switches/ps5532/products_configuration_guide_chapter09186a0080878de4.html

  • Questions stemming from the unidirectional nature of MPLS LSP

    After reading the following excerpt, I have some questions that I hope someone could clear up for me.
    "An MPLS connection (LSP) is unidirectional—allowing data to flow in only one direction between two endpoints. Establishing two-way communications between endpoints requires a pair of LSPs to be established. Because 2 LSPs are required for connectivity, data flowing in the forward direction may use a different path from data flowing in the reverse direction."
    Suppose I have a Network Management Station at each of the two geographically dispersed Data Centers, carrying out identical SNMP/ICMP-based monitoring against the same remote router at a third Data Center that's connected to the first two DCs via MPLS sold by the same ISP. There've been occasions when only one NMS (at say DC_A) reported the router at the third DC "down" (unreachable). Upon seeing the alert, the network operators sitting in DC_B pinged the remote router at DC_C successfully, therefore concluding the NMS was "crying wolf". I had thought it meant there's a problem with the particular MPLS circuit over there. But given the above paragraph about MPLS' unidirectionality, and the fact multiple interruptions in either forward or reverse direction could cause the NMS software to eventually conclude that the remote router has become unreachable, was my original conclusion wrong? What correct conclusions could be drawn from the aforementioned scenario of a single NMS reporting an outage at the other end of the MPLS? Furthermore, is it possible that actual business application traffic flowing through the same DC_A <=> DC_C MPLS could be unimpacted while my NMS there was alerting, due to the former taking a "different path"?

    Hello Yjdabear,
    your understanding is correct in line of principle one LSP can be broken and the NMS of site A complains of connectivity failure.
    testing on path site A to site C can provide a different result then test from site B to site C
    To be noted that there are some tests that could be run on routers to check the health state of LSPs
    see
    http://cco.cisco.com/en/US/docs/ios/12_4t/12_4t11/ht_lspng.html#wp1054520
    so there are ways to understand if LSPs between site A and site C and between site B and site C are operational
    Hope to help
    Giuseppe

  • TTL Question? SMTP?

    OK, here's question #2 for the mighty IronPort Nation. The nation is doing great so far.
    I am trying to determine why an e-mail failed. The delivery failure is:
    5.4.7 - Delivery expired (message too old) '[Errno 61] Connection refused'
    The e-mail was sent while the recipient e-mail system was down. What I'm trying to determine is why didn't it queue up either on the sending e-mail system or on IronPort. I don't really understand the path when IronPort is involved. Anyway, my research has led me to believe the problem was caused by a TTL parameter that was too small. Do all e-mail systems use TTL? The sending e-mail system admin. says they don't have/use TTL.
    Any thoughts on the topic?
    Thanks,
    Newbie IronPort/Messaging Admin.

    How old was the message when it expired? There is no explicit TTL mechanism in SMTP, each server retries for however long it is configured. RFC 2821 recommends a minimum retry time of "at least 4-5 days" (interesting that it is so nonspecific).
    Regarding "understand[ing] the path when IronPort is involved," that's going to be very installation-specific. Your mail system may be configured to route its outbound mail via your IronPort, or it may be configured to route its own outbound mail. The fact that you got an error from the IronPort implies the former. In this case, mail will stay on the appliance for the duration of its retry time. The default is 72 hours, but can be changed via a bounce profile.

  • Some MPLS questions, agian

    I . when I read the "Label Distribution topic" I getting in trouble with this problem:
    - What are the differents between PE and P routers? (in Label distribution mechanism).
    - When distrubute Label, which Table dose PE (or P) base on ?
    And I feel not sure to anwser those questions :
    QUESTION NO: 1
    How does a PE-router operating in the default frame mode distribute labels?
    A. The PE-router distributes a label for every destination in its FIB.
    B. The PE-router only distributes labels for destinations inside the MPLS domain.
    C. The PE-router only distributes labels for destinations outside the MPLS domain.
    D. The PE-router does not distribute labels. Label distribution is only done by the core
    LSR.
    ==> can you explain for me: what is called "default frame-mode"? in the default frame-mode is "PHP" is enabled by default ?
    QUESTION NO: 2
    How could you check for potential MTU size issues on the path taken by a PE-to-PE
    LSP?
    A. Because MPLS packets are label switched, MTU problems can only be detected by the
    user applications.
    B. Use the ping vrf command with packet size set to the largest MTU along the path
    and DF bit set from the local PE-router to ping the remote PE-router.
    C. Use the ping vrf command with packet size set to the smallest MTU along the path
    and DF bit set from the local PE-router to ping the remote PE-router.
    D. Because MPLS packets are label switched, packets are automatically fragmented and
    reassembled by the PE-routers.
    Therefore, there are no potential MTU issues.
    ==> I choose B in this question, is it correct ?
    Thanks.

    MPLS can work on two modes Frame mode and Cell mode.
    Routers by default support frame mode.ATM switches and routers with ATM interface support cell mode.
    PHP means Penultimate Hop.PHP is a term use to refer to node which is one HOP before the destination.e.g
    R1-R2-R3-R4,your destination is on R4 in that case R3 is acting as PHP.It pops the label and sends it out as IP packet.
    The PE router assigns the labels to all its destination learned through IGP.However BGP routes gets the label through their next hop e.g If you learn 120K BGP routes through single next hop.All the BGP routes will be having one label.
    There is a feature called BGP with labels which overcomes this limitation.
    -Waris

Maybe you are looking for