Re: [j-nsp] Thanks for all the fish

Shall we start taking bets on what stays, and what goes? Here’s my List: Stays: PE/Edge Routing (MX/Trio) - Stays and continues development. Reasons stated already in this thread. It’s the Swiss army knife to solve $things-you-didn’t-even-know-you-needed-to-do for some future corner case, and

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory - Resolved

Indeed. Apologies to all --- I too got an update from JNPR on the "show route" vs "show routing" CLI conflict a few weeks ago in early September -- but forgot to share it here. CASE; 2023-0719-733950 Synopsis: "show route" and "show routing" operational mode CLI conflict - JunOS 21+ Root

Re: [j-nsp] Q. Is anyone deploying TCP Authentication Option (TCP-AO) on their BGP peering Sessions?

FWIW -- We've asked for that feature now in any RFP/RFQs we send to the usual gang of $vendors. Thats our method to get adoption, else they get a black-mark/non-comply in the [BGP section] when it comes time to score the responses. - CK. > On 27 Sep 2023, at 10:49, Barry Greene via

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Hi Jeff I'll open it with my SE here in Australia (Mark Barrett). Will advise once complete. - CK. > On Jul 19, 2023, at 01:24, Jeff Haas via juniper-nsp > wrote: > > > Juniper Business Use Only > On 7/12/23, 12:11 PM, "Jeff Haas" > wrote: >> On 7/12/23, 11:46

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

+1 Mark! As any good problem begs for a solution, my suggestions to JNPR are as follows, as alternative places for this command: "show route transport-class ..." (or really, is it even a routing thing? might be better w/the segment-routing or spring commands)i.e.: "show segment-routing ..."

Re: [j-nsp] JunOS RPKI/ROA database in non-default routing instance, but require an eBGP import policy in inet.0 (default:default LI:RI) to reference it.

ken going the other way, so I've > had to enumerate all of the routing-instances that I want to be sure have a > copy of the validation DB to get them to work correctly. Maybe the other way > will work in your case. > > David > >> On Jun 4, 2023, at 7:52 PM, Chris Kawchuk vi

[j-nsp] JunOS RPKI/ROA database in non-default routing instance, but require an eBGP import policy in inet.0 (default:default LI:RI) to reference it.

Hi All Been scratching my head today. As per Juniper's documentation, you can indeed setup RPKI/ROA validation session inside a routing-instance. You can also have it query against that instance on an import policy for that VRF specifically, and if there's no session, it will revert to the