If you never want a router to be used as a transit path then just set the overload bit in the LSPDUs generated by it, so on R1 in this case.
That would be a hard "you cannot send traffic via me" signal to the two LSRs.
There are various other option available under the overload config depending on your needs (can have it act more like overload in OSPF where it just sets max metrics and there are also option to allow route leaking etc)
https://www.juniper.net/documentation/us/en/software/junos/is-is/topics/ref/statement/overload-edit-protocols-isis.html
------------------------------
STUART RIDSDALE
------------------------------
Original Message:
Sent: 11-28-2022 12:38
From: CHARLES MAYES
Subject: ISIS No Route-Through
Good morning everyone,
I have an ISIS Scenario that I need assistance with and I'm trying to get some expert opinions on this. I have a router connected to two Label Switch routers. All three are running ISIS. In the scenario, the two LSR's have a 300 Gbps link between them and each as a 100Gbps link to the lone router in this scenario. I'm trying to prevent the LSR's from using the 100Gbps links through the lone router as a backup to the 300Gbps link.
Currently I have each of the 100 Gbps links configured in a separate ISIS instance (in this example 5 & 6), but it seems that the logs are showing LSR database issues. I'm trying to see what my alternatives here would be. Any thoughts? Please let me know if you need any additional information.
I have attached a drawing of the topology in this scenario.
Thank you!
Chuck
------------------------------
CHARLES MAYES
------------------------------