Re: [j-nsp] RSVP hidden routes in inet.0

OK, Seems I understood it. Look like igp shortcut for keeping rsvp signaling going. That's why routes in inet.0 Thanks everyone for useful comments. On Mon, 11 Dec 2023, 21:57 Misak Khachatryan via juniper-nsp, mailto:juniper-nsp@puck.nether.net>> wrote: The most annoying

Re: [j-nsp] RSVP hidden routes in inet.0

The most annoying thing is that this is inet.0 table, not inet.3 Best regards, Misak Khachatryan, On Mon, Dec 11, 2023 at 7:30 PM Tom Beecher mailto:beec...@beecher.cc>> wrote: This is correct, they exist for the bypass LSPs. I wouldn't characterize it as a dirty hack though. RFC409

[j-nsp] RSVP hidden routes in inet.0

10.255.0.226 via ae1.7, label-switched-path Bypass->10.255.0.230->10.255.25.158 The /32 routes here are the IPs of adjacent routers. The only thing I found in inet is that Juniper does something similar with LDP over RSVP. It seems like some dirty hack on the control plane side, but I will be very grateful if someone can explain. Best regards, Misak Khachatryan ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] MX480 / RE-S-2000-4096

Hi, We do that with RE-S-1300 and DPCE 4x 10GE R sort of cards. No problems for a 4 or more years. And IPv6 full tables too. Best regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC- ALFA CJSC 1 Khaghaghutyan str., Abovyan, 2201 Armenia Tel: +374 60 46 99

Re: [j-nsp] BGP Peering Policies - Best Practices

Hi Niall, we have this knob in VRF and master instance, but IMHO having it in master is overkill. I should consider to remove it from master, as we have only mpls loopbacks routes there mostly. Best regards, Misak Khachatryan, On Sat, May 25, 2019 at 1:24 AM Niall Donaghy mailto:niall.dona

Re: [j-nsp] BGP Peering Policies - Best Practices

loss. Best regards, Misak Khachatryan On Wed, May 22, 2019 at 5:40 PM Niall Donaghy mailto:niall.dona...@geant.org>> wrote: Hi Adam, Yes I can show: - When we had the internet table in inet.0, with uRPF loose, we did not have any problem. - When we moved internet into its own VRF,

Re: [j-nsp] vRR/L3VPN/Unusable

inet.0; } } The only family that still needs resolution is route-target. Best regards, Misak Khachatryan, On Thu, Sep 13, 2018 at 4:08 PM adamv0...@netconsultings.com<mailto:adamv0...@netconsultings.com> mailto:adamv0...@netconsultings.com>> wrote: > From: Ivan Ivanov [mailto:

Re: [j-nsp] vRR/L3VPN/Unusable

OK, so this seems also perfectly OK in my vRR: resolution { rib bgp.l3vpn.0 { resolution-ribs inet.0; } rib bgp.rtarget.0 { resolution-ribs inet.0; } } Thanks Adam for help! Best regards, Misak Khachatryan, On Thu, Sep 13, 2018 at 1:28 PM Misak Khachatryan

Re: [j-nsp] vRR/L3VPN/Unusable

on his VRR Best regards, Misak Khachatryan, On Thu, Sep 13, 2018 at 1:41 AM adamv0...@netconsultings.com<mailto:adamv0...@netconsultings.com> mailto:adamv0...@netconsultings.com>> wrote: Hmm, these things are nasty you set them once and forget how they work :) Why to define the

Re: [j-nsp] vRR/L3VPN/Unusable

0/0> discard; } } rib inet6.3 { static { route ::/0 discard; } } resolution { rib bgp.l3vpn.0 { resolution-ribs [ inet.3 inet.0 ]; } } } Best regards, Misak Khachatryan, On Wed, Sep 12, 2018 at 3:51 PM Jason Lixfeld mailto:j

Re: [j-nsp] Upgrading from RE-S-2000-4096-S/SCB-MX960-S to RE-S-1800X4-32G-S/SCBE2-MX-S

, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC- ALFA CJSC 1 Khaghaghutyan str., Abovyan, 2201 Armenia Tel: +374 60 46 99 70 (9670), Mob.: +374 55 19 98 40 URL:www.rtarmenia.am On Tue, Jan 16, 2018 at 5:52 PM, craig washington <craigwashingto...@hotmail.com>

Re: [j-nsp] Meltdown and Spectre

Hi, although i think this is theoretical only discussion, but If JavaScript on a browser can do it, I think at least python script will do it. And it's not a problem to run it. Best regards, Misak Khachatryan On Mon, Jan 8, 2018 at 3:15 PM, Ola Thoresen <o...@nytt.no> wrote: > O

Re: [j-nsp] Junos 15.1 and DPC

Oh, thanks, didn't know that! I think for us it's safe to downgrade to 14.2 then, as the single reason to have 15.1 is version consistency between our routers. Best regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC- ALFA CJSC 1 Khaghaghutyan str., Abovyan

Re: [j-nsp] Junos 15.1 and DPC

Hi, we run 15.1R4-S8 on MX-480 with RE-S-1300 and a few DPCE 4x 10GE R and DPCE 20x 1GE + 2x 10GE R for a while, no problem. We use it as pure internet border router with bunch of peers and upstreams. Best regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC

Re: [j-nsp] Juniper BGP signaled VPLS interoperability, site-id issue

regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC- ALFA CJSC 1 Khaghaghutyan str., Abovyan, 2201 Armenia Tel: +374 60 46 99 70 (9670), Mob.: +374 55 19 98 40 URL:www.rtarmenia.am On Thu, Nov 10, 2016 at 6:03 PM, Misak Khachatryan <m.khachatr...@gnc

Re: [j-nsp] Juniper BGP signaled VPLS interoperability, site-id issue

Hello, Yes, site range set to 100, but I'm planning to remove it, as default is 64K. Best regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC- ALFA CJSC 1 Khaghaghutyan str., Abovyan, 2201 Armenia Tel: +374 60 46 99 70 (9670), Mob.: +374 55 19 98 40 URL

Re: [j-nsp] Juniper BGP signaled VPLS interoperability, site-id issue

Small correction: After more thorough examination site 5 seems not working, instead site 17. So it seems site ID's 1-15 not working, like first label block. Best regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC- ALFA CJSC 1 Khaghaghutyan str., Abovyan

[j-nsp] Juniper BGP signaled VPLS interoperability, site-id issue

9, range: 16, offset: 112 Localpref: 100 Router ID: 10.255.255.41 Mikrotik uses base 16, while Juniper - 8. But changing label-block-size on Juniper config doesn't help. So, is there something I'm missing? Any help appreciated. Best regards, Misak

Re: [j-nsp] JTAC Recommended Junos Software Versions Old?

We have it in our network, installed about 3-4 months ago. We use them as PE in our MPLS network, every function we use seems OK. Best regards, Misak Khachatryan, Network Administration and Monitoring Manager, GNC-Alfa CJSC. - Original Message - From: Sascha Luck [ml] li...@c4inet.net

Re: [j-nsp] MX extended DHCP server static address binding

Khachatryan, Network Administration and Monitoring Manager, GNC-Alfa CJSC. - Original Message - From: Ben Dale bd...@comlinx.com.au To: Misak Khachatryan m.khachatr...@gnc.am Cc: juniper-nsp juniper-nsp@puck.nether.net Sent: Friday, January 16, 2015 2:52:09 AM Subject: Re: [j-nsp] MX

[j-nsp] MX extended DHCP server static address binding

Pool2 to host. Juniper MX480, JunOS 14.2R1.9 I know that i can send IP address by RADIUS attribute, but unfortunately our billing server don't have this feature implemented yet. -- Best regards, Misak Khachatryan. ___ juniper-nsp mailing list juniper

[j-nsp] VPLS Multihoming and CCC-Down interface flag

anyone explain this behavior? Any help highly appreciated. -- Best regards, Misak Khachatryan, ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Juniper MVPN and tunnel interfaces.

I had exactly that configuration in mind. Misak. Best regards, Misak Khachatryan, Network Administration and Monitoring Manager, GNC-Alfa CJSC. - Original Message - From: Mark Tinka mark.ti...@seacom.mu To: juniper-nsp@puck.nether.net Cc: Ivan Ivanov ivanov.i...@gmail.com, Misak

Re: [j-nsp] Juniper MVPN and tunnel interfaces.

? -bs -- Best regards, Misak Khachatryan, Network Administration and Monitoring Manager, GNC-Alfa CJSC. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Juniper MVPN and tunnel interfaces.

10.255.255.6, lsp-id 16860311 17 P2MP root-addr 10.255.255.6, lsp-id 16860520 17 P2MP root-addr 10.255.255.6, lsp-id 16860563 Output label database, 10.255.255.25:0--10.255.255.33:0 misak@MX80-HRAZDAN Best regards, Misak Khachatryan, Network Administration and Monitoring Manager, GNC

[j-nsp] VRRP aware IGMP/PIM

; } } interface all { mode sparse; version 2; } } mvpn { receiver-site; } } Junos version 12.3 -- Best regards, Misak Khachatryan, Network Administration and Monitoring Department Manager, GNC-Alfa CJSC

Re: [j-nsp] VRRP aware IGMP/PIM

- there is possibility both PE routers to believe they are DRs for the segment.(PE1 seeing P2'S hellos elects himself because of highest IP address and PE2 not seeing neighbor hellos elect himself as one and only pim router on segment) HTH, Krasi On 13 May 2014 15:09, Misak Khachatryan m.khachatr...@gnc.am

Re: [j-nsp] Procedure for upgrade routing engines.

with RE. I also saved and restored licenses. There is a chance that they will sync in process of config sync, but better to make sure. Thanks again to all who helped me with this. Misak Khachatryan wrote: Hello, Does anybody know the right procedure to upgrade routing engines on working router

Re: [j-nsp] MX480 RE-S-2000 IGMP flood

in detail. some things like my l2 policer were meant to solve invidualized needs there are probably examples in the wild albiet I can probably also dig one up. On 1/30/14, 10:03 PM, Misak Khachatryan wrote: Thanks Saku and Joel for detailed explanations, Do You know any good resource to start

Re: [j-nsp] MX480 RE-S-2000 IGMP flood

for each lo and routing instance unit or lo0.0 is catch all for everything? joel jaeggli wrote: On 1/30/14, 6:46 AM, Saku Ytti wrote: On (2014-01-30 14:35 +0400), Misak Khachatryan wrote: Thanks Abhi, i saw this document, but i need real life experience about hardening thresholds or implementing

[j-nsp] MX480 RE-S-2000 IGMP flood

mechanisms? Anybody nave recommendations for threshold tuning? I'm gonna to open ticket in JTAC of course, but here i can get faster answers. Thank You in advance. -- Best regards, Misak Khachatryan, Head of Network Administration and Monitoring Department, GNC-Alfa CJSC

Re: [j-nsp] MX480 RE-S-2000 IGMP flood

regards abhijeet.c On Thursday, January 30, 2014 2:57 PM, Misak Khachatryan m.khachatr...@gnc.am wrote: Hello, I met very ugly problem yesterday. Consider following scheme: Cisco ASR 1006 | Customer

Re: [j-nsp] MX-480 BGP Open message error with unknown subcode.

Nothing common. Mark Tinka wrote: On Monday, January 27, 2014 11:26:37 AM Misak Khachatryan wrote: This happes simultaneously to two customers, they saying that nothing changed. Customer with BIRD also tries other daemon - Quagga for example. Totally weird. Any commonality in how

Re: [j-nsp] MX-480 BGP Open message error with unknown subcode.

This happes simultaneously to two customers, they saying that nothing changed. Customer with BIRD also tries other daemon - Quagga for example. Totally weird. Mark Tinka wrote: On Sunday, January 26, 2014 06:54:07 PM Misak Khachatryan wrote: No, separate subnets. Th example above was from

Re: [j-nsp] MX-480 BGP Open message error with unknown subcode.

No, separate subnets. Th example above was from peering with Mikrotik. Sent from my iPad On 25 հնվ, 2014 թ., at 19:29, Mark Tinka mark.ti...@seacom.mu wrote: On Friday, January 24, 2014 03:37:33 PM Misak Khachatryan wrote: Yes, that's why it's weird. As additional info, the peers

Re: [j-nsp] MX-480 BGP Open message error with unknown subcode.

This issue resolved by adding multihop stanza to neighbor, which is pretty weird, as peers use directly connected interface IPs ... Misak Khachatryan wrote: Hello, I have strange problem on my MX-480. From some time router suddenly drops BGP peering with two customers and session doesn't come

Re: [j-nsp] MX-480 BGP Open message error with unknown subcode.

Peer2 Peer1---/30-Peer2 -Original Message- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Misak Khachatryan Sent: Friday, January 24, 2014 7:43 AM To: juniper-nsp@puck.nether.net juniper-nsp Subject: Re: [j-nsp] MX-480 BGP Open message

Re: [j-nsp] MX-480 BGP Open message error with unknown subcode.

-Original Message- From: Misak Khachatryan [mailto:m.khachatr...@gnc.am] Sent: Friday, January 24, 2014 8:59 AM To: Brent McIntosh; juniper-nsp@puck.nether.net juniper-nsp Subject: Re: [j-nsp] MX-480 BGP Open message error with unknown subcode. Here it is: neighbor xxx.xxx.98.74

[j-nsp] MX-480 BGP Open message error with unknown subcode.

::2_Connect flags Jan 22 12:47:37.568743 task_timer_uset: timer BGP_47623_49800.2a02:2a50:0:11::2_Connect Touched set to offset 2:28 at 12:50:05 Any clue? Thanks in advance. -- Best regards, Misak Khachatryan, Head of Network Administration and Monitoring Department, GNC-Alfa CJSC

[j-nsp] Juniper MX Virtual chassis

, or just some sort of MPLS ring. Our MX boxes used to be MPLS PE routers providing VPLS and VRF, and also acting as BRAS for our GPON customers. Thanks in advance. -- Best regards, Misak Khachatryan, Head of Network Administration and Monitoring Department, GNC-Alfa CJSC

[j-nsp] Procedure for upgrade routing engines.

? AS REs are very different I doubt it's possible, but better to ask. -- Best regards, Misak Khachatryan, Head of Network Administration and Monitoring Department, GNC-Alfa CJSC. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https

Re: [j-nsp] Procedure for upgrade routing engines.

some JNPR folks can chime in with actual technical facts and details? Best regards, Daniel -- Best regards, Misak Khachatryan, Head of Network Administration and Monitoring Department, GNC-Alfa CJSC. ___ juniper-nsp mailing list juniper-nsp

Re: [j-nsp] Procedure for upgrade routing engines.

I mean You have two identical REs with GRES/NSR enabled. Then if You replace one of REs with another type without disabling GRES/NSR in a minute or so shit hits the vents. Mark Tinka wrote: On Wednesday, January 08, 2014 03:19:57 PM Misak Khachatryan wrote: Maybe they assuming that GRS/NSR

Re: [j-nsp] Config archive subtleties

I would recommend NOC project, an open source OSS/BSS. It has many goodies, works with lot of hardware. http://www.nocproject.org I use it for bunch of Cisco's, Juniper's and D-Link switches for config archivation, as IP address management with integrated DNS support and lot of other stuff.