MPLS MP-IBGP configuration

Hi,
I have configured following senario
PE1-s1/0--------P1---P2------s1/0-PE2
10.10.10.1 10.10.30.2
PE1 -s1/0-10.10.10.1
PE2 -s1/0-10.10.30.2
I have configured the IBGP between PE1 and PE2 with physical interface IP address.
I can see the BGP session is UP between PE1 and PE2.
I have configured (activate) MP-IBGP between PE1 and PE2.
And i received the following message on the PE1 router.
%BGP-4-vpnv4NH_IF:next-hop 10.10.10.1 may not be reachable from neighbour 10.10.30.2 - not a loopback.
Can anyone please explain me what is this mean?

Explanation A VPNv4 route is being sent to the IBGP neighbor indicated in the messages. The next hop is one of the directly connected physical interfaces. It is possible that the label for the address of the next hop is being removed in the MPLS cloud one hop too soon. Because the provider (P) routers do not store VPN information, they do not know where to forward packets that carry the BGP label. If the address is not available at the correct hop, it could break connectivity between VPN sites.
regards
shivlu jain

Similar Messages

MPLs and ATM configuration

Please i need some information about configuring MPLS and ATM and the addcon command
thanks

Please look at the following documents and let me know if they address the questions you have.
Integrating MPLS with IP and ATM :
http://www.cisco.com/en/US/partner/products/sw/ps2346/ps99/products_configuration_guide_chapter09186a00800ee108.html
Configuring MPLS with the BPX Switch and the 6400/7200/7500 Routers:
http://www.cisco.com/en/US/partner/products/sw/ps2346/ps99/products_configuration_guide_chapter09186a00800ee112.html
Designing MPLS for ATM:
http://www.cisco.com/en/US/partner/products/sw/ps2346/ps99/products_configuration_guide_chapter09186a00800ee110.html
Let me know if this helps,

MPLS TE Tunnels configuration

Hello.
I have the following doubt. What happens if I configure one TE tunnel in both ends. I have read that is enough configure only one side.
Thanks

The LSP starts on PE on which Tunnel was built and ends on some ther PE, and its unidirectional. To have bidirectional you need to make two Tunnels on each end.
HTH,
Gaurav Prakash

InterAS MPLS Option C (BGP IPv4 + Labels) IOS XR with eBGP multihop session

Hello,
Right now we have InterAS MPLS Option C configured between 2 autonomous systems.
Now we need to add more bandwith and would like to add another interface between the two routers establishing a multihop session using loopbacks to load share traffic.
I know that IOS-XR does not automatically learn directly connected host routes so for the XR router to assign labels you'll need to configure a static host route to ensure MPLS forwarding to the neighboring AS.
This works with directly connected neighbors but when I try to enable the multihop session, the XR does not assign labels even configuring the staic host route.
Does anybody has a configuration like that working?
Thanks!!
Jose.

Hello Jose
There are basically two options in Option C L3VPN setup. I will discuss the first option for Multihop.
Following are the key points that distinguish the InterAS Option C from previous options.
1) External Multihop BGP address families are invoked between two different autonomous systems; however, these eBGP sessions are invoked between the route reflectors in each AS and not on the ASBR. The route reflector in each AS thus passes labeled ipv4 unicast VPN routes to the other AS. Note:- The route reflector in this case will have PE clients in the vpnv4 address family within that Autonomous System.
2) ASBRs facilitate the creation of InterAS LSP by providing labeled /32s for PE and Route Reflector loopback.
3) This option enhances scalability because ASBRs do not handle VPNv4 routes in fact this option gets rid of the extra L3VPN LFIB that is created as a result of option B . The LFIB size is minimal as we control the redistribution to the only 2 needed loopback addresses (remote ASBR and remote RR)
Sample config of the RR:
router bgp 102
address-family ipv4 unicast
address-family vpnv4 unicast
neighbor-group ibgp
remote-as 102
update-source Loopback0
address-family ipv4 unicast
   route-reflector-client
address-family vpnv4 unicast
   route-reflector-client
neighbor 192.168.253.3
remote-as 101
ebgp-multihop 255
description eBGP-RR-PEER-AS101
update-source Loopback0
address-family vpnv4 unicast
   route-policy allow-all in
   route-policy allow-all out
   next-hop-unchanged
neighbor 192.168.254.1
use neighbor-group ibgp
neighbor 192.168.254.3
use neighbor-group ibgp
neighbor 192.168.254.4
use neighbor-group ibgp
On the PE router, the config will look something like this:
router bgp 102
address-family ipv4 unicast
redistribute ospf 1 metric 3333 route-policy interAS-optionc-out
allocate-label route-policy interAS-optionc-out
neighbor 65.10.20.1
remote-as 101
address-family ipv4 labeled-unicast
   route-policy interAS-optionc-in in
   route-policy interAS-optionc-out out
neighbor 192.168.254.2
remote-as 102
update-source Loopback0
address-family ipv4 unicast
router static
address-family ipv4 unicast
65.10.20.1/32 TenGigE0/0/0/1
192.0.2.0/24 Null0 tag 10
route-policy interAS-optionc-in
if destination in remote-RR-PE then
    pass
else
    drop
endif
end-policy
route-policy interAS-optionc-out
if destination in local-RR-PE then
    pass
else
    drop
endif
end-policy
prefix-set local-RR-PE
192.168.254.2/32,
192.168.253.6/32,
192.168.253.5/32
end-set
prefix-set remote-RR-PE
192.168.253.2/32,
192.168.253.3/32,
192.168.253.3/32
end-set
Just for your clarification, 192.168.253.0/24 is the Remote AS networks and 192.168.254.0/24 is the local AS networks.
Hope this clarifies your doubts.
Cheers ... !!!
Vinit

Managing Route-Map based MPLS VPN

1) How to derive the VPN information of the MPLS VPN configured using route-maps? As I understand, stitching route-maps information to derive VPN is complex as it is difficult to derive & correlate the filters tied to each of the route-maps that are tied to a VRF :(
2) Is there any MIB to get from the MIB
a) Route-maps tied to each VRF
b) What is the filter associated with each route-map?
c) Definition of each of the above filter
It would have been nice if the route-maps' name had global-significance within AS, so that we could have treated route-maps, pretty much like the route-tragets. Alas, I doubt it is :(
It should be noted here that if the MPLS VPN is configured using route targets, the VPN information derivation is fairly straight forward throught MplsVpn MIB.
So, the question is what is the simplest way to derive the MPLS VPN info given that they are configured using route-maps in BGP for labelled-route-distribution & for the pkt association with the VRFs.
Thanks,
Suresh R

Each CE in a customer VPN is also added to the management VPN by selecting the Join the management VPN option in the service request user interface.
The function of the management route map is to allow only the routes to the specific CE into the management VPN. The Cisco IOS supports only one export route map and one import route map per VRF.
http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/products_user_guide_chapter09186a0080353ac3.html

Venturing into MPLS Network

Hi all, it is just my curiousity that ended up with a small discussion like this. Here's about it...
My company has a main client which have tonnes of remote sites connecting to both their HQ and Disaster Recovery Centre. Some of the remote sites still running on frame-relay, while other is purely leased-line. There's a few question I wish I can clear up as follows:
i. When the client have frame-relay device, what we do is create a tunnel and route all the frame-relay traffic over. Is there any advantage if we change it over to MPLS?
ii. Even if comparing to leased-line services, what kind of advantages I can expect if our cliet migrate over to leased-line?
iii. If one customer is running purely on frame-relay connectivity, any difficulties will arise when they want to switch over to MPLS network?
I still never has any hands on experience on the MPLS, that's why need to gather some info in the first place, I'm currently have a glance through those MPLS guides and configuration examples, but I knew that perhaps in real-life network, things may differs, in the meanwhile I'm studying through it, hope to gather some precious opinions. Regards

Hello,
Regarding answer iii: What you have to use inside the MPLS cloud is MBGP to route the customer prefixes. In your LAN however you will have an IGP like EIGRP. This means you need mutual redistribution between MBGP and your IGP. So a routing loop can occur once you have at least two pathes. An Example:
N1-CE1 - PE1 - PE2 - CE2
with: CE1 - PE1 using RIP, CE2 - PE2 using RIP, PE1 - PE2 using MBGP and a FR PVC between CE1 - CE2 using RIP
This would be the case when you migrate from FR to MPLS VPN and do not shut down FR the very moment you activate the MPLS links.
What can happen in this scenario is: CE1 is announcing Network N1 through RIP to CE2 directly over the FR PVC and also to PE1. PE1 will redistribute N1 into MBGP, send the prefix to PE2, which will redistribute N1 into RIP and send the update to CE2.
Now depending on implementation and metrics this will result in all traffic flowing over FR or MPLS (when adjusting metrics). No major problem yet.
The problem might occur once CE1 looses network N1. It will send an update directly to CE2 and to PE1 and a race condition exists. CE2 will still have one valid path to N1 learned from PE2 and announce this one to CE1, which will announce it to PE1 and then PE2, CE2, CE1 again and so on.
This is an intermittend or even persistent routing loop, depending on what you have done with hop count during redistribution.
By designing your overall routing solution carefully you can avoid this scenario.
Hope this helps! Please rate all posts.
Regards, Martin

EBGP and IBGP and update-source loopback use

Cisco curriculum CCNP1 V3.0 "9.3.3 EBGP and IBGP configuration example" says:
(((Because EBGP sessions are typically point-to-point, there is no need to use update-source loopback command with EBGP))).
Is this acceptable ? because we know we can use update-source loopback with EBGP,,,Don't we ?

It is becasue of the nature of where EBGP is used as opposed to IBGP.
IBGP is generally ran within your AS, along with an IGP such as OSPF, ISIS or EIGRP. Your routers generally have multiple interfaces and multiple paths to each IBGP neighbor. Therefore the use of a loopback interface as a source is the best option (it doesn't goe down etc).
With EBGP you normally only have a single path to a Neighbor and you don't run other routing protocols to that neighbor. They are generally directly connected by a physical link. If the physical link goes down you generally want the EBGP peering to break as well so it is normal to use the physical interface IP address as the source for the neighbor relationship.
Does that explain it any better?
Andy

Configuring LSP

Hi All,
I need to know the set of commands which are needed to create new LSP in Cisco Router.
I tried searching other docs available on Cisco Support forums, and came across the below set of commands, please help me know if these are correct and sufficient .
Also please guide me to know commands needed to create Explicit Path LSP.
switch# configure terminal
switch(config)#
switch(config)# feature mpls traffic-engineering
switch# configure terminal
switch(config)#
switch(config)# feature isis
switch(config)# router isis 200
switch(config-router)#
switch(config-router)# mpls traffic-eng level-1
switch(config-router)# mpls traffic-eng router-id loopback0
switch# configure terminal
switch(config)#
switch(config)# feature ospf
switch(config)# router ospf 200
switch(config-router)#
switch(config-router)# mpls traffic-eng area 1
switch(config-router)# mpls traffic-eng router-id loopback0
switch# configure terminal
switch(config)#
switch(config)# interface ethernet 2/1
switch(config-if)#
switch(config-if)# mpls traffic-eng tunnels
switch(config-if)# mpls traffic-eng bandwidth 1000
switch(config-if)# no shut
switch# configure terminal
switch(config)#
switch(config)# interface tunnel-te 1
switch(config-if-te)#
switch(config-if-te)# ip unnumbered loopback 0
switch(config-if-te)# destination 10.3.3.3
switch(config-if-te)# path-option 10 explicit name Link5
switch(config-if-te)# no shutdown
switch# configure terminal
switch(config)#
switch(config)# mpls traffic-eng configuration
switch(config-te)#
switch(config-te)# explicit-path name Link5
switch(config-te-expl-path)# index 10 next-address 10.3.3.3

Hello Ayush,
To form the LSP using MPLS Traffic Engineering, folowing is the checklist:
++ CEF should be enabled on all the routers
config t
ip cef
++ Loopback should be configured on the routers (which will also be used as router-id)
++ End to end loopback reachability should be fine via ISIS or ospf
++ "mpls traffic-eng tunnel" should be configured globally
++ "mpls traffic-eng tunnel" and "ip rsvp bandwidth" should be configured under all the core interfaces. By default rsvp reserves 75% bandwidth
++ mpls traffic-engineering should be configured under the ospf or isis process (as seen in the output of your question)
switch(config)# router ospf 200
switch(config-router)#
switch(config-router)# mpls traffic-eng area x
switch(config-router)# mpls traffic-eng router-id loopback0
++ Configure the explicit path on 2 end points
Suppose you have 3 routers:
A---------B---------C
so the config on A will be:
ip explicit-path name ABC
next-address
next-address
next-address
Similarly, configure the explicit path on C in reverse direction.
++ Finally, configure the tunnel on 2 end points.
config t
int tunnel x
ip unnumbered loop0
tunnel mode mpls traffic-eng
tunnel destination x.x.x.x >> This is the loopback IP of remote end
tunnel mpls traffic-eng path-option 1 explicit name abc
After this, it is upto you if you want to send the traffic on this tunnel via this options:
1. static
2. PBR
3. Autoroute Announce
4. Forwarding Adjacency
5. Load Sharing
6. Automatic Bandwidth Adjustment
Seems like the command line you used above is for Nexus (NX-OS). I have explained it for IOS.
Hope This Helps!!
Regards,
Imran

MPLS TE: Fastreroute issue/question IOS XR

I have MPLS TE tunnels configured to protect long distance links between routers in the core of the network. I have primary tunnel UP and also the backup tunnel UP, the problem is that when I try to see if fastreroute is ready it seems that is not there. I have to mention that I haven't configured the autoroute announce command on the primary tunnel (haven't done the traffic migration yet).
The configuration is the following:
interface tunnel-te1
ipv4 unnumbered Loopback0
signalled-bandwidth 5000000
destination x.x.x.x
fast-reroute
path-option 1 explicit name primary
interface tunnel-te2
ipv4 unnumbered Loopback0
backup-bw 4000000
destination x.x.x.x
path-option 1 explicit name backup
mpls traffic-eng
interface TenGigE0/1/0/0
backup-path tunnel-te 2
interface TenGigE0/2/0/0
Every thing else is already configured (rsvp, osfp-mpls-te)
The output of the show commands are:
RP/0/9/CPU0:router#show mpls traffic-eng fast-reroute database summary
Status Count
Active 0
Ready 0
Partial 0
RP/0/9/CPU0:router#show mpls traffic-eng tunnels backup
tunnel-te2
Admin: up, Oper: up
Src: y.y.y.y, Dest: x.x.x.x, Instance: 222
Fast Reroute Backup Provided:
Protected LSPs: 0
Backup BW: any-class; limit: 4000000 kbps, Inuse: 0 kbps
Protected i/fs: TenGigE0/1/0/0
Is there anything I should be worried about? is this a normal behaviour knowing that the autoroute command is not configured yet?
Many thanks for your help.

As you can see in the "show mpls traffic-eng tunnels" output it says that fastreroute is enabled, but I can not see it in the fastreroute database.
RP/0/9/CPU0:P-MTY01#sh mpls traffic-eng tunnels 1
Name: tunnel-te1 Destination: x.x.x.x
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit primary (Basis for Setup, path weight 10000)
G-PID: 0x0800 (derived from egress interface properties)
Config Parameters:
Bandwidth: 5000000 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Policy class: not set
Loadshare: 0 equal loadshares
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 5000000
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Fast Reroute: Enabled, Protection Desired: Any
History:
Tunnel has been up for: 00:49:17
Current LSP:
Uptime: 00:49:17
Prior LSP:
ID: path option 1 [435]
Removal Trigger: path verification failed
Path info (OSPF 1000 area 0):
Hop0: y.y.y.y
Hop1: z.z.z.z
Do you think this is an issue I should be worried about?

Can I send bridge traffic over MPLS backbone?

Can someone let me know if bridging can be done across a MPLS backbone? If yes, please provide a brief config sample or let me know where I can find documentation. Thanks

You can provide Ethernet over MPLS. The configuration can depend on platform - here is a configuration guide for the 7600 series:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5013/products_feature_guide09186a0080088187.html
EoMPLS is also on 12000 and 10720:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/12s10k.htm
For 7200, 7500, and 12000 series, you can do port mode EoMPLS:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom25s.htm

Out of band Clocking between MWR-2941

Good morning I'm having problems configuring out
of band clocking between two MWR-2941
I have configured one MWR-2941 to
Remote
recovered-clock slave
interface Virtual-Cem 0/24
cem 0
xconnect 10.10.10.2 7600 encapsulation mpls
network-clock select 1 PACKET-TIMING
network-clock-select hold-timeout 900
the Master Router is getting it clock signal from an E1/T1 interface
MASTER
controller E1 0/0
clock source internal
cem-group 0 unframed
description Clocking-Signal
controller E1 0/13
clock source line
cem-group 0 unframed
interface CEM0/0
description Clocking-Signal
no ip address
cem 0
xconnect 172.16.20.26 7600 encapsulation mpls
interface CEM0/13
no ip address
cem 0
xconnect 172.16.20.26 11591 encapsulation mpls
with this configuration i can't get any clocking at the remote site. I have configured this between a Cisco 7609 and the MWR-2941 without problem, but in the Cisco 7609 I can create another virtual-cem interface. But I can't find a way to create a virtual-cem in the MWR-2941 that should be working as the clock master.
Any help will be greatly appreciated.
Thank you very mucy.

Thank you for your attention ,
I did not see such out put of my sho mac add command ,
I sent a image of my current topology , it may be useful , please find it.
I used router instead of cisco layer 3 switches (SVI for user access vlan is configured on router as sub interfaces) , and On my NAC Server I created a vlan mapping rule that map unauthenticated vlan to one of my access vlan ,
I have a problem with my Managed subnet !! I have to put my Managed Subnet as default gateway for my client because if I put the router SVI cisco nac agent client does not pop up at all !!!
I read different documents about that and all of them said that your client default gateway must be SVI , but it does not work,
best regard

Not all Prefixes in VRF Tables are Reachable?

Hello,
During my studies with an MPLS VPN [MP-BGP] lab I found something unexpected. I wonder if I am mistaken in my comprehension or if this normal:
Not all prefixes in a VRF Table are pingable/reachable ?
Seems that in the standard routing tables, if a prefix is there, then it is pingable/reachable.
I've attached a sketch to help illustrate the lab I have set up and what I found.
Below is output from ABR2 in the lab showing inability to ping 154.0.0.154, even though it is in the VRF IT table. After "mpls ip" is configured on the "*" interface of Core2 the LDP Adjacency between Core2 and ABR2 comes up and ABR2 can ping everything in the VRF IT table, including 154.0.0.154
Just seems like this is a "Gotcha" for one just coming into the world of MPLS VPN. Just because a Prefix is in the VRF Table does not mean it is reachable?
Thanks for any input.

Hello Greg,
Behavior which you have experienced is completly normal in MPLS environment. There is big difference between forwarding IP packets and MPLS frames.
If you disable "mpls ip" on some interface along your LSP, LSP is broken and traffic is lost. MPLS VPN packets have two labels:
- IGP label - according this label, packet is forwarded from ingress PE to egress PE
- VPN label - based on this label, egress PE can put packet to particular VRF
VPN label is known only to ingress and egress PE, if LSP is broken, IGP label is stripped off in the middle of the LSP and packet is forwarded based on VPN label. But as I said, intermediate routers do not know what to do with this packet, because label is unknow to them so packet is discarded.
I hope this cleared some things for you.
To further studies I would recommend this book:
http://www.ciscopress.com/store/mpls-fundamentals-9781587051975
Best Regards
Please rate all helpful posts and close solved questions

QoS-drops

Hi.. I have configured service policy on tunnel interface but i am seeing packets are being drop in default class even if bandwidth is not full utilized.
I have been running 20MB mpls circuit and configured GRE tunnel b/w two locations over mpls circuits. I have assigned 15mb to FTP traffic.
pls tell me why there is drops even if link bandwidth is almost available.
class-map match-any ftp
match ip dscp af21
policy-map police
class ftp
    bandwidth 15000
policy-map shape
class class-default
    shape average 20000000
service-policy police
interface Tunnel1
service-policy output shape
Router#sh policy-map interface t1
Tunnel1
Service-policy output: shape
    Class-map: class-default (match-any)
      2056697 packets, 1360260464 bytes
      5 minute offered rate 566000 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/424/0
      (pkts output/bytes output) 2075327/1394463992
      shape (average) cir 20000000, bc 80000, be 80000
      target shape rate 20000000
      Service-policy : police
        Class-map: ftp (match-any)
          0 packets, 0 bytes
          5 minute offered rate 0 bps, drop rate 0 bps
          Match: ip dscp af21 (18)
            0 packets, 0 bytes
            5 minute rate 0 bps
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth 15000 kbps
        Class-map: class-default (match-any)
          2056697 packets, 1360260464 bytes
          5 minute offered rate 566000 bps, drop rate 0 bps
          Match: any
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/424/0
          (pkts output/bytes output) 1952029/1304014921

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
As Vasilii has described, you can compute the additional delay you might impose by increasing queue's limit (NB: keep in mind, though, queue depth is in packets, so if the same number of packets were smaller in size, maximum latency would be reduced).
If you want to allow a single TCP flow to be able to use all the bandwidth, you'll need to insure your queue can handle about half the BDP.
Doing so, again, risks increasing the possible maximum latency. However, using QoS, you can sometimes get the best of both. Low latency for light weight flows and maximum transfer rate for bandwidth hogs.

2602 lightweight AP losing config on reboot

Anyone encountered an issue with the 2602E access points losing config everytime they lose power?
I have a 5508 WLC running 7.4.121.0 code and two 2602E Flexconnect access points that everytime they lose power they default their configuration. The APs are located at a remote site connected via MPLS and are configured for FlexConnect with local switching. The 2602Es will re-associate with the WLC since the DHCP option 43 points them to it, they just show up with the default config.
I have three 2602E models at the site but only two of them are doing this, the third comes back up and associates and has retained its configuration. I also have several 1142 models at the site and they behave normally.

There are no secondary controllers, just the primary. These two access points lose all configuration, name, ap group, flexconnect group,flexconnect setting, everything. Its like they are new out of the box and associating for the first time. I have a third 2602E located att the same site and have tested it via power reset and reboots and it retains all config. Both the AP that retains its info and the two that dont are all running the same code/boot version/etc. I cant see any difference in their configuration.

Merging of lsps

hi,
what do you mean by merging of lsps..?
In what all scenarios do we use this..?
How do we do this..?
Thanks in advance,
Thomas.

Hello Thomas,
the term "VC merge" is used in cell based MPLS. There ATM cell headers (VPI/VCI) are used as labels. Basically LVCs are setup through f.e. LDP. The main issue VC merge does address is the comparably low number of VCs supported per interface in ATM routers and switches. Assume 100 routers attached to an ATM network - this could mean roughly 10000 LVCs.
VC merge means, that an ATM switch has several incoming VCs (VPI/VCI) mapped to one outgoing label (VPI/VCI). Thus on the outgoing interface towards one router R1 only one VC is created and not 99 (a separate one per other router).
In cell-based MPLS you can configure this through the command "mpls atm vc-merge".
The detailed description can be found at: "MPLS over ATM: VC Merge"
http://www.cisco.com/en/US/tech/tk436/tk798/technologies_configuration_example09186a00801c2d73.shtml
In frame-based MPLS the downstream router distributes a single label per destination network. So all upstream neighbors will use the same label. This could also be called "merging of LSPs". As this is the default, there is no specific configuration required.
Hope this helps! Please rate all posts.
Regards, Martin

MPLS MP-IBGP configuration

Similar Messages

Maybe you are looking for