These ranges were true, but somewhere maybe since JunOS 18.4 (at least), they were dropped and the whole pool seems now to be allocated on a first asked first served basis, starting from label 16 (by example I have here on an MX in 19.4 a label 26 used as a service label [LSI Label] to a L3VPN VRF, and a label 28 is a transport LDP label used to forward traffic to another interface).
Looks like there's only one big «dynamic range» and a small «static range», by default, today.
> show mpls label usage
Label space Total Available Applications
LSI 999984 999961 (100.00%) BGP/LDP VPLS with no-tunnel-services, BGP L3VPN with vrf-table-label
Block 999984 999961 (100.00%) BGP/LDP VPLS with tunnel-services, BGP L2VPN
Dynamic 999984 999961 (100.00%) RSVP, LDP, PW, L3VPN, RSVP-P2MP, LDP-P2MP, MVPN, EVPN, BGP
Static 48576 48576 (100.00%) Static LSP, Static PW
Effective Ranges
Range name Shared with Start End
Dynamic 16 999999
Static 1000000 1048575
Configured Ranges
Range name Shared with Start End
Dynamic 16 999999
Static 1000000 1048575
------------------------------
Olivier Benghozi
------------------------------
Original Message:
Sent: 07-29-2021 10:45
From: Unknown User
Subject: MPLS Label Ranges
Hello,
I found this link:
https://community.juniper.net/answers/blogs/elevate-member/2020/10/22/what-are-the-label-switched-interface-lsi-label-value-assignments-for-different-services
Bellow the link content. I hope that's answer your question, or at least, part of it.
VPLS uses a dynamic virtual tunnel logical interface on a tunnel PIC to model traffic from a remote PE router site in a VPLS domain. All traffic coming from the remote site is treated as if it is coming over the virtual port that represents this remote site, for the purposes of Ethernet flooding, forwarding, and learning.
In this approach, an MPLS lookup based on the inner VPN label is done on a PE router in the CF chip or R-chip. The label is stripped and the Layer 2 Ethernet frame it contained is forwarded to a tunnel PIC. The tunnel PIC loops the packet back, then a lookup is performed based on Ethernet MAC addresses.
Drawbacks to this approach include creating a bottleneck at the tunnel PIC and requiring the PE router to perform two lookups.
By default, VPLS uses a tunnel PIC. If the no-tunnel-services statement is configured under a VPLS instance, it uses an LSI and does not require a tunnel PIC.
The current label numbering assignment is listed in the following table:
Services | Label Values |
Reserved | 0 - 15 |
LSI VPN | 16 - 2047 |
LSP VPLS | 2048 - 4095 |
Unassigned | 4096 - 10,000 |
Static LSP | 10,000-99,999 |
Global | 100000-799999 |
Block Allocation | 800000-899999 |
Per Intf | 900000-999999 |
For more information, click Layer 2 VPNs and VPLS Feature Guide.
#faq
#MPLS#vpls#vpn
Original Message:
Sent: 03-04-2021 01:41
From: Unknown User
Subject: MPLS Label Ranges
Hi everyone.
Is there any document that tells me the MPLS label ranges for various applications such as LSI, VPNs, etc.
The command below tells me the number of labels in each range... but since they don't add up to the complete number of available MPLS labels, they don't tell me the actual ranges.
jcluser@vMX-addr-0# run show mpls label usage
Label space Total Available Applications
LSI 69609 69609 (100.00%) BGP/LDP VPLS with no-tunnel-services, BGP L3VPN with vrf-table-label
Block 199936 199936 (100.00%) BGP/LDP VPLS with tunnel-services, BGP L2VPN
Dynamic 487936 487936 (100.00%) RSVP, LDP, PW, L3VPN, RSVP-P2MP, LDP-P2MP, MVPN, EVPN, BGP
Static 48576 48576 (100.00%) Static LSP, Static PW
Thanks,
Deepak
Juniper Business Use Only