Hot answers tagged

9

The problem is the: [edit protocols rsvp] load-balance bandwidth If you look at the Juniper documentation for Unequal Cost Load Balancing RSVP LSPs, it states: For uneven load balancing using bandwidth to work, you must have at least two equal-cost LSPs toward the same egress router and at least one of the LSPs must have a bandwidth value configured at ...


9

FEC or 'Forwarding equivalence class' identifies identity for packet which will determine path it will take in the network. For pure IPv4 forwarding, with routing-table 10.0.0.0/24 -> 192.0.2.1 you can think that addresses 10.0.0.0 - 10.0.0.255 share that FEC, as they are treated same way, each of them are going to go to 192.0.2.1. In MPLS typically FEC is ...


9

Yes both LSR[12] could advertise given FEC, say 10.0.0.1/32 with label 10 to each other. Then if IGP says to LSR1 10.0.0.1/32 egress interface is towards LSR2, it'll impose (or swap to) label 10 and send towards LSR2. LSR2 then will find egress interface being something else than towards LSR1 and swap label to what ever that direction has advertised, might ...


6

is a unique label generated per Destination prefix in routing Table or is it per Next-hop in the routing table? ...i have seen customer scenarios approaching 1 million routes... But the MPLS doesn't have any common guidelines for label generation ? Is there not a common rule saying a unique label should be generated per Destination-prefix or per nexthop ? ...


3

The exact practical scenario when labels might run out is debatable. There are some house-keeping issues also which are not directly related to labels running out but contribute to that effect. Label managers today in major vendors (CSCO, JNPR at least) are programmed so that they need continuous block per label application. Of course this could be fixed, ...


3

Firstly, there looks to be something wrong with ae13 - if you have 16x 10G interfaces attached to it, you should have an RSVP interface bandwidth of 160Gbps, not 130Gbps as per your output? So is it a good practice to change RSVP bandwidth value of an interface? There is nothing inherently good or bad about manually overriding the speed of an interface ...


3

As far as I know, in L3VPNs which are implemented on top of MPLS-TE MPLS-TE and MPLS L3VPN are two independent features and L3VPN does not require the use of MPLS-TE. Some companies use MPLS-TE to achive specific routing or failover qualities for their L3VPNs, but MPLS-TE is only related to MPLS L3VPN by the fact that it uses MPLS labels. Are there some ...


1

From Junos MPLS and VPNs Student GUide Volume 1 of 3 revision 12.a Basic functional RSVP configuration requires: 1.Adding the mpls family to desired interfaces (not needed for lo0) 2.Linking interfaces with the routers MPLS process 3.Enabling RSVP on desired interfaces 4.Configure the label-switched-path under the protocols mpls hierarchy As your ...


1

RSVP reserves resources along a certain path in the network, but the destination could only be specified by a single address (unicast or multicast) so as far as I know you can neither reserve resources towards a CIDR block, nor send traffic to a different host in the same subnet as the one you initially reserved resources for and assume that the reservation ...


1

Cisco routers can be configured to support RSVP. RSVP would need to be configured on all the routers in a path from one endpoint to the other endpoint. This Cisco document may be useful to you: Configuring RSVP, or you can search the Internet for "Cisco RSVP". Once RSVP is properly configured on the routers, it is completely up to the applications and OSes ...


Only top voted, non community-wiki answers of a minimum length are eligible