Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[M/MX/T-series] RSVP LSP setup and hold priority values

0

0

Article ID: KB24851 KB Last Updated: 26 Jun 2012Version: 1.0
Summary:
The MPLS LSP configuration will not be committed, when the highest set-up priority is defined, instead of the hold priority value. You cannot configure an LSP with a high setup and a low reservation priority value.
Symptoms:
Even when you try to configure the high set up priority, rather than the hold priority, for an RSVP signaled MPLS LSP, Junos CLI will not allow you to commit the configuration. It will  generate the Configuration Check-out failed error message, as shown below:
lab:R1# show protocols mpls
label-switched-path LSP-1 {
    from 1.1.1.1;
    to 4.4.4.4;
    bandwidth 10g;
    no-cspf;
    priority 2 5;
}
interface all;

[edit]
lab:R1# commit check
[edit logical-systems R1 protocols mpls]
'label-switched-path LSP-1'
invalid priority value at '5' not in range 0 to 2
error: configuration check-out failed
Cause:
  • As the default set up priority and Holding Priority values are 7 and 0 for an RSVP LSP, the RSVP signaling protocol will not allow you to manually lower the holding priority value to that of the setup priority value.

  • Either both the setup and holding priority values need to be the same or set-up priority should be less than the holding priority value.

Note: The priority is inversely proportional to numerical values.
Solution:
Configure the low set-up priority, rather than the holding priority value, for the LSP to form.
edit protocols mpls label-switched-path LSP-1]
lab:R1# show
from 1.1.1.1;
to 4.4.4.4;
bandwidth 10g;
no-cspf;
priority 5 4;

[edit protocols mpls label-switched-path LSP-1]
lab:R1# commit check
configuration check succeeds
Alternatively, you can configure the set-up and holding priority to the same value, as shown below, for the LSP to form:
[edit protocols mpls label-switched-path LSP-1]
lab:R1# show
from 1.1.1.1;
to 4.4.4.4;
bandwidth 10g;
no-cspf;
priority 5 5;

[edit protocols mpls label-switched-path LSP-1]
lab:R1# commit
commit complete

[edit protocols mpls label-switched-path LSP-1]
lab:R1# top

[edit]
lab:R1# run show mpls lsp
Ingress LSP: 1 sessions
To          From         State      Rt    P        ActivePath       LSPname
4.4.4.4     1.1.1.1       Up         0    *                          LSP-1
Total 1 displayed, Up 1, Down 0

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search