Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

tunnel-status

Syntax

Hierarchy Level

Description

Use the RSVP or LDP tunnel status.

If the ingress PE tunnel is disabled or if the tunnel from the ingress PE to egress PE is not Up due to some reason, the egress PE can't allocate egress labels. If tunnel-status is enabled, then that ingress PE without a valid tunnel will not be considered for upstream multicast hop (UMH) selection.

Similarly, mLDP tunnel status can be retrieved from TAI by checking the allocated egress labels and based on this status, the UMH selection can be retriggered to add or remove the PE router from the UMH list.

Note: If the egress PE’s message isn't able to reach the ingress PE, the egress PE can still have an egress label and show the tunnel status as Up. The end-to-end tunnel can still be down, and the system can’t detect this state even with the configuration statement tunnel-status.
Note: S‑PMSI-only scenarios without an I-PMSI tunnel can’t be detected because source reachability is via I-PMSI only, therefore an I-PMSI tunnel configuration is required for tunnel-status configuration.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement for mLDP introduced in Junos OS Release 26.2R1.

Related Documentation