How to migrate on to MPLS network....

hi,
we are a telecom service provider and want to shift our network backbone/core on to MPLS .
would appreciate if someone could help me in the same or any doc to go through for migration steps.
right now the network is on IP.do we have to cofigure it first for frame relay or ATM ???
Thanks in advance

There is no such migration document available, till my awareness is. Although Vivek Alwayns book is a good place to start understanding the nitty grities.
No you dont need to migrate your network to ATM or FR as its already on IP.
Here is a high level summary of the migration steps to be followed:
1) Migrate the Core for Label Switching.
2) Enable all service including Internet, Central Hosted Service Like Mail, Telephony etc onto a dual connected scenario. That is each service will have two links one for VRF and other into Global Table.
3) Start migrating customers one at a time,
when you put them in VRF they acces all the services as is through VRF and who are left over they access through global table.
This requires each VPN/Customer to be migrated at a time. Hope this method suits you, as its very subjective.
Also you can read through these previous post,
1)MPLS: Redistribute from VRF to Global
2)best internet access method over MPLS?
All this would you a fair idea of all hte high level tasks involved. Then you have to start working out everything into miute details, considering all the services you want to deploy.
HTH-Cheers,
Swaroop

Similar Messages

  • How traffic is directed in MPLS network? Via ldp LSPs or via RSVP LSPs

    My question is basicly to understand how traffic is treated.
    Lets assume our topology is :
    A-----------------------------B------------------------------------C--------------------------------------------D
    1-) if we just enable MPLS under all interfaces, LDP labels are exchanged with each peer. At that moment   RIB, LIB, FIB and LFIB are created on all routers. So LDP LSPs are created dynamicly. but  If i ping "loopback D"  from router A, there will be IP routing or LABEL switching.  will routing make routing by looking IP address at each hop or labels will be swapped at each hop ?
    2-) If we enable MPLS traffic engineering capability and create a tunnel interface between router A and router D, vice versa. At that moment, Router A will have :
    -simple IGP reachability to Router D,
    -Dynamic LDP LSP  and
    -RSVP tunnel.
    what about now, Which one of the paths above  my traffic will follow ? do I have to direct my traffic to tunnel interface signaled via RSVP. Is there any precedence for choosing the path that traffic will be addressed ?

    for second secenario, i have found that I have to write
    "tunnel mpls traffic-eng autoroute announce " other wise traffic will always follow LDP signaled paths. In order to get all traffic inside "tunnel" we should execute that command.  once you write that command you see that ;
    Before executing command;
    R1#sh ip route
    O       3.3.3.3 [110/129] via 3.3.3.3, 00:07:08, serial0/0
    R1#show mpls forwarding-table
    18     18          3.3.3.3/32        0          Se0/0      point2point
    After executing command;
    R1#sh ip route
    O       3.3.3.3 [110/129] via 3.3.3.3, 00:07:08, Tunnel0
    R1#show mpls forwarding-table
    18     Pop tag [T] 3.3.3.3/32        0          Tu0        point2point 
    Hope you see my point, router doesnt decide to use RSVP signaled LSP itself, we shoud trig router to use RSVP signalled LSP.

  • How to priortize video & voice traffic over mpls network

    Dear all,
    I have taken a 512k link from mpls network containing juniper as core routers, while i am using completely cisco in my network, my query is can i priortize my voice and video traffic over this mpls network i am also using rtp header compression.
    plz give me sample config if it is possible.
    thanks

    hi
    if i m not wrong there will be different kinda service offering in general being provided by the SPs.
    it falls under 2 main major categories one is managed and the other is unmanaged.
    in managed services your SP will honour the marking being done by the customers and the same is being carried throughout(in SP backbone) till reaching the remote destination.
    in unmanaged services whatever markings you do at ur end will be remarked or ignored by SP according to the policies followed by them.
    you can enquire about this with your SP and you can have the QOS policies configured accordingly.
    regds

  • How to Move Local Users to Network Domain Users

    Before you follow these instructions...... I'm a rank amateur so I'd check to see if the smart kids have corrected my errors or improved on the method in the replies below
    The reason for the post is I have good and established local user accounts on all the computers and moving them to domain controlled accounts is the one topic I could not find a script to follow that worked for my low level of knowledge of OS X.
    Let me first explain my setup and needs. I'm replacing a Windows Home Server (WHS) with the Mac Mini Server. My goal was to have the Mac Mini as the server holding all our photos, data, etc. and running a user account to run the family iTunes account to feed the Apple TV and be the backup / sync point for a family sized set of iPod Touches, iPads and iPhones. I want to be able to log into each mac and have the same information setting, links, etc........ basically walk around the house, find any mac shaped device not used by someone else, log in and carry on where I was before -  with the MacBook Air having a portable account so it can come travelling with us.
    The key hardware is...
    Mac Mini Server running Snow Leopard 10.6.8
    Apple TV
    2 x iMac Running Lion 10.7.1 [upgraded from 10.6.8]
    MacBook Air running Lion 10.7.1 [upgraded from 10.6.8]
    Normal stuff like wifi, hubs and a router doing the DHCP (and for me reserving IP addresses based on the 'MAC Address' to save me having to manually configure all the IP addresses)
    Key Resources I used as I learnt how to do this; to level set you all, I'm a relative newcomer to OS X having had a Windows life with Linux for fun, so i'm not a mac or IT specialist but like to play around.
    Apple's podcast series 'Apple Quick Tour of Leopard Server'  - this is great, it informed me and kept me motivated through all the bah moments, all 33 episodes and it's in the iTunes store as a podcast.
    The book 'Mac OS X Snow Leopard Server For Dummies' - I bought this about half way through the whole process and wish i'd bought it earlier, my reccomendation would be get the Kindle version so you can search it for advice.
    The excellent information on DNS from Hoffman Labs http://labs.hoffmanlabs.com/node/1436
    The video 'Setting up a primary DNS zone.....' from Lynda.com on youtube  http://www.youtube.com/watch?v=OOEgQY9oFK4
    The Series of PDF document on Snow Leopard Server from Apple http://support.apple.com/manuals#mac%20os%20x%20server%20v10.6
    And finally this excellent post from Joe Ferrante which was the core of what I used http://joeferrante.net/how-to-migrate-local-user-account-to-network-user-account -with-networked-home-folder-on-snow-leopard-server/
    Right off we go....
    Setting up the Server [this took me 6 goes to get it right as I learnt a little each time].
    So i'm not going to go through this step by step because it in the 'dummies' book and the videos from Apple above and those will be better than anything I write but here's my details/advice.
    I split the primary disc into 2 partitions using disk utility so I could reformat the operating system without moving my data.
    100GB for the OS X system
    400GB for user data
    Install OS X from the DVD, press the buttons based on your desires but stop at the bit about naming you computer titled Network Names
    READ UP ON DNS  - this one of the reason I had so many goes as it was the 1st time i've set up a server like this using DNS and guessing didn't get me there.
    If you don't have one buy a domain name for your network it make it much easier in the long run & is $10 well spent
    The name needs to be [the computer name].[your domain name].[com or net or org, etc]
    So if you want you computer to be called fred and you bought or have the domain location.com enter fred.location.com in the primary DNS name box
    This shoud automatically put fred in the computer name box.
    Follow along with the set up guide to finish
    After you have finished the set up test the DNS with NSLOOKUP in a terminal window
    nslookup fred.location.com    in my example and you should get the IP
    Add your servers IP address to the list of DNS servers in network preferences on the client mac.
    Bind [link] the client computers to the server in Accounts on the client computer - I used the 'dummies' book for this but there's lots of data on the web.
    Clean up the user profile on the client to reduce the size of the Home folder as much as possible or the data transfer is loooooooonnnnng - i also connect the iMac on a cable rather than wifi to speed it up.
    Read Joe's post http://joeferrante.net/how-to-migrate-local-user-account-to-network-user-account -with-networked-home-folder-on-snow-leopard-server/ and follow along.useful info I learnt somewhere - to get the paths to the folders correct in the terminal window go to the folder in Finder and then drag it to the terminal window and let go - this will put the correct link in the instruction.
    You now need to be on a terminal window on your server, with a finder window open and logged into the client as the user you are moving
    THE CLIENT COMPUTER NEEDS TO BE LOGGED OUT or logged in as a different user than the one you're trying to move.
    so when you're at the right point - type sudo cp -R then hit the space bar, drag the existing user folder onto the finder window, add the /* and hit space then find the users folder on the server and drag that onto the terminal window to complete the instruction.
    Hit enter and wait a while assuming it starts ok - i used network traffic on the Activity Monitor utility to check if it was working.
    If you got this far and it all worked - login to the profle you moved on any computer linked to the server or the server but not the original client computer to see if it worked and all your setting and data are intact and then delete the profile off the original client if it was ok [archiving the home directory took ages for me].
    As you can probably guess most of this was good learning for me and it worked successfully for me in the end, moving all my history, saved password, etc, etc without any problems.
    Hope this helps other in the same situation & feel free to expand or correct this if I've missed anything.
    Ed

    Hi,
    I was unable to access the Joe Ferrante information (it appears to now requrie a password and was not able to determine how a username and password were assigned)  Would you happen to have a copy of the post that you refer to above?
    I am still at the early stages of this process but am hoping that the steps you refer to are going to get me where I want to be.  Your stated end goal is where I hope to get to.
    Thanks,
    Sean

  • Exchange 2013 Migration in a complicated network environment

    Hello everyone,
    I am conducting an Exchange migration from 2007 to 2013. The client have 4 geographical site and each of those site have an Exchange CAS server on it. The sites
    have also DCs on each of them. 
    There's two types of connection between sites one is MPLS that's 50MBPs and the other is p2p that's 2mbps. Client wants to have only 2 Exchange 2013 Server with
    all the roles collocated on them and DAG between them.
    I already have installed and configured DAG on the servers. One server is located in the Central data center and the other is located on a second geographical
    site that also have a disaster recovery data center.
    Client wants to configure the MAPI network on Exchange 2013 to use the P2P 2mbps connection and use the MPLS 50mbps connection for the replication NIC. 
    The problem is that both networks MPLS and P2P have the same IP subnet, same gateway e.g. (10.1.1.0/16) but a range of those IPs are configured on the router to
    use the MPLS connectivity.
    I have tried to add static route to the replication network to use the gateway but when trying to add a copy of a centralized database to the DAG. the DAG copies
    the connection over the P2P line. 
    Is it possible to configure this with the same subnet or do I need to have the mpls connection on a totally different network and subnet? 
    I would appreciate all your suggestions and I  am very sorry for my terrible explanation because I am my self confused about their network topology. 
    I will prepare a visio diagram of the network, IPs and everything to clear everything out.
    Mohammed JH

    I have solved the issue, it was very simple but due to lack of knowledge about networking it got complicated. the way I have configured the replication networks between both sites was that each replication NIC on each site should have a different subnet
    that configured on the MPLS network with the high speed and bandwidth. they must be different on each site. 
    For each replication NIC a persistent static route should be configured on Exchange server to tell the NIC where to direct traffic exactly. 
    After configuring the subnets on the replication NIC, I added the static routes and the replication started to work flawlessly. 
    This is the static route command that I run on the first machine on the first site, it tells the Replication NIC to direct traffic to the subnet network on the second site through the gateway 10.1.1.1 
    route -p add 10.5.1.0 MASK 255.255.0.0 10.1.1.1 
    On Exchange on the second site, I had to run the same command as well
    route -p add 10.1.1.0 MASK 255.255.0.0 10.5.1.1 
    thanks everyone for the help.
    Mohammed JH

  • Path Selection for Routes Across MPLS Network

    Customer hub site has two CE routers with two links connected to two seperate PE routers in the Carrier's MPLS network. At the customer's remote site one CE router on a single link is connected to PE router in MPLS network.
    How can I configure the CE routers at the hub site to advertised the same network across the MPLS network to the CE router at the remote site? Also, how can I configure the CE router at the remote site to select on of the router as the primary and the other as secondary? Can I use local-preference on the CE router at the remote site to selected on path over the other.
    I'm not sure if this makes any sense. Any help will be appreciated. Thanks

    Even with multiple RDs for VRFs belonging to the same VPN, you still need IBGP multipath, correct? Multiple RDs is just to get around the RR restriction.
    Also, you posted this message a while back:
    "If you have many VPN customers all using the same addresses (most likely rfc1918), the fact that they have different RDs and that the PE prepends the RD to the prefixes exchanged between PEs will make the same prefixes different in the MPLS VPN core
    cust1 advertises 192.168.1.0/24 with RD 1:1 therefore
    VPNv4 prefix is 1:1:192.168.1.0
    cust2 advertises 192.168.1.0/24 with RD 1:2 therefore
    VPNv4 prefix is 1:2:192.168.1.0"
    My test lab does not support the IBGP multipath command, and thus even with different RDs, it still only installs one best path.
    I understand that RD = make unique VPNv4 routes in SP space, and that RT = what to import into the VRF. However, I am having a hard time visualizing the scenario with mutiple RDs for the same VPN for load balancing purposes. I am trying to understand the logic behind it.
    Per your example, if both 1:1 and 1:2 are received by the remote PE, assuming IBGP multipath is enabled, why would the remote PE load balance between the two links? Why would it assume that the hub subnets are reachable via two different PEs, and that it's not two different, isolated VPNs altogether?
    Is it b/c you imported both 1:1 and 1:2 into a VRF at the remote PE?

  • Migrate switches from different networks to a single network

    Hello, I have a question on migrating C3750 switches between networks.
    Our current situation is that we have two networks.
    We control the cores on both networks but do not controll all the edge devices on both networks.
    We can not access the IOS and configuration on a number of switches because we don't have the login information for those.
    In the future if we are to take control of those edge devices how can we modify the IOS and configuration settings for multiple switches at one time?
    Within the core we can modify vlans, destroy and recreate to suit our purposes, so that's easy enough.
    We would rather not have to visit each and every switch and do this manually as there are over 40 switches and only 2 admins.
    Manually doing this requires using the password recovery option method to change the IOS.
    Once done we should be able to update the config via CISCOWorks on all the devices,
    Or we could do it the other way around and update the config and then update the IOS via CISCOWorks.
    Our wish is to attempt to do both via CISCOWorks or some other automated method.
    ej

    Hi,
    Can this be acheived by normal TMS configuration (without Extended Transport Control)? If yes how?
    Yes.
    Understand the following basic relationship behind transporting chagnes using TMS
    ....Repository Objects ->are assigned to-> Package ->are assigned to->Single Transport Layer ->is assigned to-> Single Transport Route -> Target System.
    The basic concept behind standard Transport Control is that every repository object in Source System (e.g Dev-System) is assigned (via a package) to a certain transport layer, it follows that a change request can only have one target system. So, you can transport change requests from multiple clients of Development System, which you can import into QUA system's clients upon release.
    With the standard Transport control program, it is not possible to create two transport routes with the same transport layer from one SAP System. Thus, The extended Transport Control program is used for transporting the changes based on Client specific Transport Routes by using the concept of Transport Group. Using this, one can transport changes to multiple systems, multiple clients using the same transport layer.
    Regards
    Bhavik G. Shroff

  • Running Large Backups over an MPLS Network

    We are opening up a second data center at my organization. The location is about 60 miles from our primary data center.
    At our primary data center we use an MPLS network for our WAN. We have ll remote locations on our WAN and we have a DS-3 that connects to our primary data center.
    At our new second data center we will connect it to the MPLS network.
    Do you think we should run our backups between the 2 data centers across the MPLS or do you think we should order a seperate private line or ethernet type service between the 2 data centers? All back ups from our primary data center will continually move across the network to our new secondary data center.
    Do you think MPLS is a good technology to run large back ups across? Is it reliable enough

    "Do you think MPLS is a good technology to run large back ups across?"
    Sure.
    "Is it reliable enough"
    Depends more on your MPLS provider than the technology itself.
    Two issues that may be more important to you vs. how "reliable" MPLS is, might be cost of bandwidth vs. other technologies or sharing the MPLS bandwidth with non-backup applications. The latter would depend much on what QoS that might be available to you to insure your backup traffic doesn't adversely impact non-backup traffic.

  • How to migrate vShield to another vCenter?

    I have a vCenter 5.1 infrastructure with 2 ESXi 5.1 hosts and vShield implemented with 2 Edges.
    I need to migrate this 2 ESXi hosts to a new vCenter 5.5.
    Migrate the hosts is not the problem, my question is: how I migrate vShield Manager, Edge, etc to the new vCenter (vShield Manager was already upgraded to version 5.5.x)?

    Hello,
    Best approach is to export your existing firewalls and rules from the first vShield Manager. Setup a new one within the new location. Import all the firewall rules into the new vShield Manager. You may have to fix up your networks on the firewalls however.
    Best regards,
    Edward L. Haletky
    VMware Communities User Moderator, VMware vExpert 2009-2015
    Author of the books 'VMWare ESX and ESXi in the Enterprise: Planning Deployment Virtualization Servers', Copyright 2011 Pearson Education. 'VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment', Copyright 2009 Pearson Education.
    Virtualization and Cloud Security Analyst: The Virtualization Practice, LLC -- vSphere Upgrade Saga -- Virtualization Security Round Table Podcast

  • Access local mpls network surf internet with pda(gprs/edge/3g connection)

    dear sir,
    we have the hp pda 6365 and wish to use this pda connect with gprs/edge/3g and hopefully can access the local mpls network and surf internet. Any idea how to perform this? please share. thank you very much.
    hereby is the link to the pda.
    http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp &lang=en&cc=us&contentType=SupportManual&docIndexId=179166&prodTypeId=215348&prodSeriesId=430120&lang=en&cc=us

    Hi,
    For this kind of case, normally, I anticipate the connection comes from internet cloud which refers to remote access.
    Since we have managed firewall services that associated with customer VRF, on windows based client, just configure/enable PPTP/IPSec on client - like most laptop or maybe perhaps pda...
    cheers..
    maher

  • Debugging and monitoring MPLS networks

    Hi ,
    I've had the following problem with a customer of ours and I'd like to know if there's any tools I can use in the future to better diagnose the problem if it may arise again.
    The customer is a bank with hundreds of brnach sites. All of them are connected to the corporate via a MPLS network managed by a local TELCO company .
    In the last ten days they have experienced long delays during logons of users in the branch sites . This delay has been initially thought due to new operating systems deployed on the clients ( XP ) . In fact there's a rollout of XP computers at all the branch sites .
    Trying to troubleshoot the problem we have started looking at all OS related known problems but found nothing important.
    Next I tried looking at the network connections with the few tools I have ( basically ping , traceroute and protocol analyzer ) but all seemed ok .
    Having no access to the telco routers I monitored the corporate's switch ports to which the two telco router are attched .
    Finally I found some packet discarded and could call the telco and having the routers checked.
    They found a problem , they didn't told us what it was , and suddendly most of the problems were gone.
    This was really tricky because a part from the slow logon we had no other mulfunctions . I found the problem thanks to a Microsoft tool to check group policy problem which point me to possible networks problem.
    The question , after this long post , is ; is there any tool, agent , software I can install or use to check MPLS network efficiency having no access to the TELCO routers ?
    Thanks in advance
    Stefano Colombo
    CCNA - CCSP
    MCSE NT/2k/2003 Messaging

    havent not told us what the actual problem was it is kinda difficult to suggest tools. However IF this was an MTU issue then you should have used ping with the DF bit set to see how big a packet you could get over the mpls network. Let us know what the issue was and hopefully we can be a bit more detailed in our responses.
    HTH

  • Full mesh VPN solution for on MPLS network with PE and CPEs

    Hi,
    We are trying to evaluate some best solution for Hub-Spoke mesh vpn solution in a MPLS network. The VPN hub router will be in PE router and all the VPN spoke will be in CPE.
    Can someone please let us know what will be the best vpn solution, we understands that there will be some technical limitations going with GETVPN but still we did counld find any documenation for possiblity of using DMVPN.
    How about the recent flexvpn, can fex-vpn work on this requirement, where can i get a design/configuration document.?
    thanks in advance.

    Hello,
    GetVPN is intended for (ANY-to-ANY) type of VPN communication, over an MPLS network with Hub and Spoke Topology, your best Option is to look for Cisco (DMVPN) implementation where this type of VPN is primarily designed for Hub & Spoke.
    Regards,
    Mohamed

  • Routing Protocol recommendation for MPLS Network

    I am in the process of building a 14 site MPLS network for voice and data traffic. The vendor installing the network has configured RIPv2 as the routing protocol. I am considering switching this over to EIGRP. Can anyone explain to me why this would be better or should I just stay with RIP.
    Thanks

    Hi Chip,
    Its not very clear whether you are implementing a MPLS network or implementing a Network over MPLS for an end user with 14 sites.
    1) If MPLS network then other IGP variants than OSPF and ISIS best avoided. Now if the choice is between ISIS and OSPF then my personal recommendation would be OSPF. And this decision is purely driven by Operational Considerations rather than any technical advantages. Since at the end of the day what matters is how easy it is to implement add delete or troubleshoot the network.
    2)If for End User then it would not be right to recommend EIGRP or RIP or OSPF without knowing the current size & topology of each of these 14 sites, as well as the desired expansion plans. But if these 14 sites are the only sites and are all standalone branch sites connecting over MPLS VPN then RIP,EIGRP or OSPF can be implemented as per your and customer comfort.
    HTH-Cheers,
    Swaroop

  • Routing to MPLS network

    Hi,
    We have several branch offices connected via a managed MPLS network. Each MPLS router in the branch office is connected to the local LAN switch, with its separate firewall and internet access router. How do we direct traffic from the local network (unmanaged) to the private IP addresses in the MPLS network (managed)? Can static routes be configured on the ASA5505 firewall to route traffic to MPLS router?
    ISP router>local router>ASA5505 firewall>LAN switch>MPLS router>MPLS cloud.

    Said
    Is the LAN switch layer 2 only or layer 3 capable. If you do not have access to the MPLS router you have 2 options
    1) Add a route on the ASA for the private MPLS networks pointing to the MPLS router. You will need to enable hairpinning on the ASA.
    Set the default-gateway of the clients on your LAN switch to be the ASA.
    2) If your switch is a Layer 3 switch then you can do this in a much cleaner way. Create the L3 vlan interface(s) for the client vlan(s) on the switch and then you can use statics on the L3 switch eg.
    ip route 0.0.0.0 0.0.0.0 "ASA inside interface"
    ip route "MPLS private net" "subnet mask" "MPLS router inside interface"
    Jon

  • Why CEF needed in MPLS Network??

    I have read the MPLS Fundamentals book by Luc De Ghein, So I understand from the from book that cef needs to enabled in edge routers to tag or untag labels (for Ip packets). I am eager to know why Mpls (Not a cisco proprietary) depends on a cisco proprietary CEF?? If I use Non-Cisco routers in the mpls edge how come the labels get tagged for ip packets??
    <<<<<<<<<Taken from Book>>>>>>>>>>>>>
    MPLS Fundamentals - Luc De Ghein
    Why Is CEF Needed in MPLS Networks?
    Concerning MPLS, CEF is special for a certain reason; otherwise, this book would not explicitly
    cover it. Labeled packets that enter the router are switched according to the label forwarding
    information base (LFIB) on the router. IP packets that enter the router are switched according to
    the CEF table on the router. Regardless of whether the packet is switched according to the LFIB
    or the CEF table, the outgoing packet can be a labeled packet or an IP packet
    <<<<<<<<>>>>>>>>>>

    Hello Bava,
    the key point is that LDP or RSVP TE are able to generate distribute labels for FECs but they do not create the FECs from stratch.
    FEC = Forwarding Equivalent Class
    a destination IP subnet is a typical FEC.
    cisco MPLS code takes advantage of the work done by CEF and uses as input data the FIB (Forwarding Information Base) mantained by CEF, to build the LFIB that is the table where for each FEC there is an association with a label taken from the local node label space.
    The work done by CEF is not so different from what is needed by MPLS: the biggest difference is that the CEF table is kept local and not exported to any other device. MPLS FEC/label bindings are advertised.
    In MPLS frame mode the labels are distributed in unsolicited downstream mode.
    Unsolicited means that the label/FEC association is buiilt based on the topology FIB instead  of waiting for some device to ask a label for the FEC.
    downstream means the labels are sent in the opposite direction of that used by traffic.
    Other attributes are:
    indipendent : means each LSR is free to create its own FEC/label association before receiving the label from the edge LSR that owns the prefix or from a device that is nerarest to the IP subnet (upstream)
    liberal retention: the device will keep note of labels advertised by neighbors even if they are currently not on the best path. This can be seen in the output of show mpls ldp binding and allows for faster recover in case of failure of the best path.
    The unsolicited and liberal retention in standard frame mode comes from the relatively big label space (roughly one milllion labels)
    This was not possible in MPLS cell mode where the label space was small. So MPLS cell mode used on demand downstream label binding and no retention.
    Also MPLS allows for label stacking = use of multiple levels of MPLS Label for services like L3 VPNs
    to be noted other implementations are different in some aspects and each vendor has its internal tecnique to build a table of FECs to be used as starting point for MPLS code.
    For example indipendent label/FEC mapping has its own drawbacks it may be better to wait for a label to be received from a device upstream = nearest to the IP prefix in order to ensure the path is end to end.
    Hope to help
    Giuseppe

Maybe you are looking for