Re: [Users] same MPLS for multiple interfaces

No, labels are property of the source of the route. Source is free to choose any value. We restrict it to smaller value so that it is direct index lookup for performance. There are many cases but above is true in case of contrail. Regards -Harshad > On Jun 27, 2016, at 10:34 PM, kevin

Re: [Users] same MPLS for multiple interfaces

Thanks for the very good explanation... i have one more doubt here could you explain that *Since there is no central authority to allocate labels it scales well.* isn't controller which allocates labels On Mon, Jun 27, 2016 at 7:18 PM, Harshad Nakil wrote: > MPLS label is

Re: [Users] mpls label limit of 5120 and creating more than 5120 vms

wow awesome thanks that explains everything :) On Mon, Jun 27, 2016 at 1:56 PM, Robert Raszuk wrote: > Kevin, > > MPLS VPN label must be unique per each vm/lxc on a given compute node. The > forwarding based on that label is done *only* on a given compute node (SAFI > 128

Re: [Users] same MPLS for multiple interfaces

It is okay if 1. two ip(s) belong to same interface(port). or 2. two ip(s) are on different compute node. Are you seeing any forwarding issues? Until I know your specific case I cannot comment. Regards -Harshad > On Jun 27, 2016, at 10:43 AM, mad Engineer wrote: >

[Users] mpls label limit of 5120 and creating more than 5120 vms

Hello All, In a hypothetical scenario running 5120 vms from one tenant,spread across 50 compute running 100 vms each ,won't it exhaust MPLS labels and prevent creation of new vms? Can MPLS label be duplicated for another tenant so that it can also have 5120 vms Can you please help me understand