Re: [j-nsp] How to pick JUNOS Version
1. I did a direct USB recovery format boot from 17.4r2-S11, and afterwards recovered configs from FTP. The reason for this was because 15.1x54D51 screws up your /tmp directory and you wont have enough free space no matter what you try. - at least, this was the case for my installs 2. One caveat of mgmt_junos routing-instance is you wont be able to utilize vme interfaces (so if you have a virtual chassis, it still won't work), to get around this I did the following: set system management-instance rename interfaces vme.0 to em0.0 set routing-instances mgmt_junos description "OOB Mgmt Instance" set routing-instances mgmt_junos routing-options static route 0.0.0.0/0 next-hop x.x.x.x set snmp interface em0.0 set snmp routing-instance-access set system ntp server x.x.x.x routing-instance mgmt_junos set system ntp server x.x.x.x routing-instance mgmt_junos and deleted the static route for management out of the default inet.0 table Goodluck! -KV -Original Message- From: aar...@gvtc.com Sent: Tuesday, September 1, 2020 5:34 PM To: Kody Vicknair ; 'Roger Wiklund' ; 'Colton Conor' Cc: 'Juniper List' Subject: RE: [j-nsp] How to pick JUNOS Version *External Email: Use Caution* Thanks Kody, 2 questions sir... I recently began moving towards that same version (17.4R2-S11) as I was hitting PR1419761 high cpu. 1 - did you upgrade straight from 15.1x54D51 to 17.4R2-S11 , or did you take an intermediate step? Asking since JTAC recently told me that this was too far of a jump and I should go through 17.1 on my way to 17.4 15.1X5417.1--17.4 2 - do you use that mgmt_junos route instance? I would've expected to see em0 or fxp0 in there or something like that, but I don't. name@acx5048> show system information | grep Junos Family: junos Junos: 17.4R2-S11 name@acx5048> show route instance mgmt_junos detail mgmt_junos: Router ID: 0.0.0.0 Type: forwardingState: Active -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX subscriber captive portal - redirect and rewrite simultaneously
I'll preface this by saying I don't have anything constructive to add... On Fri, 28 Aug 2020, Nathan Ward wrote: I’ve tried JTAC on this, twice. First on 16.1, and again now on 19.4. Both times JTAC have either not understood and stalled for months and refused to escalate to someone who does understand, or, more recently, claim that the docs are incorrect and are being fixed. Just got this exact response late last week, on the issue with BGP output queue priorities -- they figured out why it doesn't work, and will update the documentation to remove any promises that it should. Sigh. I hope this isn't a trend. -Rob ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] How to pick JUNOS Version
Thanks Kody, 2 questions sir... I recently began moving towards that same version (17.4R2-S11) as I was hitting PR1419761 high cpu. 1 - did you upgrade straight from 15.1x54D51 to 17.4R2-S11 , or did you take an intermediate step? Asking since JTAC recently told me that this was too far of a jump and I should go through 17.1 on my way to 17.4 15.1X5417.1--17.4 2 - do you use that mgmt_junos route instance? I would've expected to see em0 or fxp0 in there or something like that, but I don't. name@acx5048> show system information | grep Junos Family: junos Junos: 17.4R2-S11 name@acx5048> show route instance mgmt_junos detail mgmt_junos: Router ID: 0.0.0.0 Type: forwardingState: Active -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] How to pick JUNOS Version
Recently upgraded all my edges from 15.1x54D51 to 17.4R2-S11. The upgrade was forced by strange transit ARP packet digestion in vpls instances... Thoroughly tested in my lab prior to deployment. It is finally nice to gain a dedicated oob mgmt routing-instance How long have we been requesting this? -KV -Original Message- From: juniper-nsp On Behalf Of aar...@gvtc.com Sent: Tuesday, September 1, 2020 3:17 PM To: 'Roger Wiklund' ; 'Colton Conor' Cc: 'Juniper List' Subject: Re: [j-nsp] How to pick JUNOS Version *External Email: Use Caution* Amen to that. I recall a few years back, going with 15.1X54-D51.7 for the ACX5048 and having complete outage on irb's in L3VPN's with no dhcp relay (ip helper) capability. ...and being baffled as I recall that the D51 version was on the JTAC recommended list. (D61 fixed it) So yeah, I agree with Roger, do your testing and verification of your things you need to make work in your network environment prior to rolling it out if at all possible. -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] How to pick JUNOS Version
Amen to that. I recall a few years back, going with 15.1X54-D51.7 for the ACX5048 and having complete outage on irb's in L3VPN's with no dhcp relay (ip helper) capability. ...and being baffled as I recall that the D51 version was on the JTAC recommended list. (D61 fixed it) So yeah, I agree with Roger, do your testing and verification of your things you need to make work in your network environment prior to rolling it out if at all possible. -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
