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

RSVP-TE LSP cannot be up between routing-instances on the same node.

1

0

Article ID: KB36357 KB Last Updated: 15 Apr 2021Version: 1.0
Summary:
This article discusses RSVP behavior between two virtual router instances on the same node.

From Junos OS 15.1, multi-instance have been supported for RSVP-TE. But, LSP cannot be established between two instances on the same node.  Since RSVP does not allow to have a peer on the same node, the situation is not supported.
Symptoms:
The following RSVP traceoptions log indicates PathErr being originated and tells that Path message is destined to local address.  This is because RSVP originates an error if the destination address is found in the local TE link database (which is instance agnostic). In addition to this destination check, RSVP also relies on the local TE link database to evaluate ERO objects in the incoming Path messages.



Test Topology

        +-----------------------------------+
        |                                   |
        |--------------+     +--------------|
        |  instance 1  |     |  instance 2  |
        |              |     |              |
        +-----------------------------------+
               |lt-0/0/0.0          |lt-0/0/0.1
               |                    |
               +--------------------+

              =========== X =========>
                    RSVP-TE LSP


instance 1, 2: virtual-router




MPLS/RSVP show command

lab@r1_re> show mpls lsp instance 1‚Äč
Nov 22 05:40:49
Ingress LSP: 1 sessions
To              From            State Rt P     ActivePath       LSPname
10.0.0.2        10.0.0.1        Dn     0       -                1      
Total 1 displayed, Up 0, Down 1

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

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

lab@r1_re> show mpls lsp instance 2
Nov 22 05:40:52
Ingress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

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

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

lab@r1_re> show mpls lsp instance 1 extensive
Nov 22 05:40:57
Ingress LSP: 1 sessions


10.0.0.2
  From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: 1
  ActivePath: (none)
  LSPtype: Static Configured, Penultimate hop popping
  LoadBalance: Random
  Follow destination IGP metric
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  LSP Self-ping Status : Not-Supported
  Primary                    State: Dn
    Priorities: 7 0
    SmartOptimizeTimer: 180
    Flap Count: 0
    MBB Count: 0
    2 Nov 22 05:40:27.498 RSVP System error, subcode 1: Bad sess dst addr[2 times, first Nov 22 05:40:27.498]
    1 Nov 22 05:40:27.497 Originate Call
  Created: Sun Nov 22 05:40:27 2020
Total 1 displayed, Up 0, Down 1

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

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



lab@r1_re> show rsvp session instance 1
Nov 22 05:41:13
Ingress RSVP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname
10.0.0.2        10.0.0.1        Dn       0  0  -       -        - 1      
Total 1 displayed, Up 0, Down 1

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

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

lab@r1_re> show rsvp session instance 2
Nov 22 05:41:15
Ingress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

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

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0


lab@r1_re> show rsvp session instance 1 extensive
Nov 22 05:41:21
Ingress RSVP: 1 sessions


10.0.0.2
  From: 10.0.0.1, LSPstate: Dn, ActiveRoute: 0
  LSPname: 1, LSPpath: Primary
  LSPtype: Static Configured
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: -
  Resv style: 0 -, Label in: -, Label out: -
  Time left:    -, Since: Sun Nov 22 05:40:27 2020
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 39928 protocol 0
  Enhanced FRR: Disabled, Reason: LSP Type, Refresh: 30 secs
  PATH rcvfrom: localclient
  Path MTU: received 0
  PATH sentto: [Local address configured as destination]
       outgoing message state: none, Message ID: 0, Epoch: 4771676
  Record route: <self> ...incomplete
Total 1 displayed, Up 0, Down 1

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

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0




instance 1 : traceoptions log

Nov 22 05:40:27.497516 [ <1> (I)  ] RSVP NSR: handle update to psb_repl_entry [PHOP Nbr: ifl-index 0, None] [Session ID 4, ID 513] [PSB created]
Nov 22 05:40:27.497559 [ <1> (I)  ] RSVP NSR: send path repl add for PSB [PHOP Nbr: ifl-index 0, None] [Session ID 4, ID 513]
Nov 22 05:40:27.497573 [ <1> (I)  ] RSVP psb_repl_entry [PHOP Nbr: ifl-index 0, None] [Session ID 4, ID 513]: state changed [Init to Ack desired]
Nov 22 05:40:27.497592 [ <1> (I)  ] RSVP psb_repl_entry [PHOP Nbr: ifl-index 0, None] [Session ID 4, ID 513]: state changed [Ack desired to Acked]
Nov 22 05:40:27.497601 task_timer_uset: timer 1-RSVP_RSVP short wait <Touched> set to interval 0 offset 0.001000 with jitter 0 at 5:40:27.498159
Nov 22 05:40:27.497621 [ <1> (I)  ] rsvp_metric_lookup for PSB : dest 10.0.0.0, metric 0/0, NH addr zero-len
Nov 22 05:40:27.497634 [ <1> (I)  ] rsvp_translate_metrics looked up new metric 0 for PSB 1
Nov 22 05:40:27.497643 task_job_create_background: create prio 7 job RSVP Metric Update for task 1-RSVP
Nov 22 05:40:27.497655 [ <1> (I)  ] start tracking 10.0.0.2/32 metric for PSB 0xbe01000 LSP  with current value 0
Nov 22 05:40:27.497730 [ <1> (I) 1 ] RSVP RESET ROUTE: LSP 1, LSP ID 1, SELF ID RSVP-4, PSB new metric 198083804, PSB old metric 198083804, PSB new weight 4097, PSB old weight 4097
Nov 22 05:40:27.498228 [ <1> (I) 1 ] Originate PathErr for LSP 1 as it is destined to local address 10.0.0.2
Nov 22 05:40:27.498237 [ <1> (I) 1 ] RSVP PathErr to client
Nov 22 05:40:27.498262 task_timer_uset: timer 1-RSVP_RSVP short wait <Touched Processing> set to interval 0 offset 0.001000 with jitter 0 at 5:40:27.499215
Nov 22 05:40:27.498288 [ <1> (I) 1 ] Originate PathErr for LSP 1 as it is destined to local address 10.0.0.2
Nov 22 05:40:27.498293 [ <1> (I) 1 ] RSVP PathErr to client
Nov 22 05:40:27.498340 background dispatch running job RSVP Metric Update for task 1-RSVP
Nov 22 05:40:27.498345 metric update job starting
Nov 22 05:40:27.498357 task_job_delete: delete background job RSVP Metric Update for task 1-RSVP
Nov 22 05:40:27.498361 metric update job finished, processed 1 prefixes, 0 had a metric change, 0 PSBs needed updating
Nov 22 05:40:27.498365 background dispatch completed job RSVP Metric Update for task 1-RSVP
Solution:
This behavior is by current design and part of the specification. 

Supporting an RSVP-TE LSP originating and terminating on different instances was not a goal for "Multi-instance for RSVP-TE" feature; so the situation of this KB is not a goal of the feature.
Virtual-instance is just different route databases, not different routers. Junos supports logical-systems; which allows you to create more than one router from a physical router. In this scenario, using logical-systems is recommended.
Modification History:
2021-04-15: initial publication

Related Links

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
Thank you for taking the time to give us your feedback.