Routing

 View Only

  • 1.  BGP-LS topology id set to 0 after JUNOS 25.x

    Posted 26 days ago

    Hello Experts,

    On JUNOS 24.2R1 and earlier, the following config works perfectly fine:

    set protocols mpls traffic-engineering database import identifier 101

    This results in topology id set to 101 in BGP-LS routes, for instance:

    admin@P1> show route table lsdist.0

lsdist.0: 22 destinations, 22 routes (22 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

NODE { AS:65002 BGP-LS ID:101 ISO:0001.0001.0001.00 ISIS-L2:101 }/1216              
                   *[IS-IS/18] 00:04:09
                       Fictitious

    See "ISIS-L2:101".

    But on JUNOS 25.2 and 25.4, this command does not work (even though it's accepted), and topology id is always set to 0.

    admin@R1> show route table lsdist.0 

lsdist.0: 92 destinations, 92 routes (92 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

NODE { AS:65002 BGP-LS ID:101 ISO:0001.0001.0001.00 ISIS-L2:0 }/1216              
                   *[IS-IS/18] 18:33:42
                       Fictitious

    Note that BGP-LS ID still works (in both cases set to 101, with command "set protocols mpls traffic-engineering database import bgp-ls-identifier 101") but that one has a different purpose and is not very compatible across vendors, so let's focus on the topology id.

    Right now it's not possible to run BGP-LS on JUNOS in a multi-domain setup, even though before 25.2 this worked fine.

    Is this a known bug?



    ------------------------------
    DMYTRO SHYPOVALOV
    ------------------------------


  • 2.  RE: BGP-LS topology id set to 0 after JUNOS 25.x

    Posted 25 days ago

    I got a response from someone from Juniper:

    1) This is related to multi-instance ISIS. I reconfigured ISIS as ISIS-instance, and applied the command "set protocols isis-instance 101 link-state-instance-id 101". Now BGP-LS routes are advertised with topology-id 101

    2) The global identifier not working is actually a bug and it will be fixed in future JUNOS releases 



    ------------------------------
    DMYTRO SHYPOVALOV
    ------------------------------

    Original Message