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: [email protected] <[email protected]> 
Sent: Tuesday, September 1, 2020 5:34 PM
To: Kody Vicknair <[email protected]>; 'Roger Wiklund' 
<[email protected]>; 'Colton Conor' <[email protected]>
Cc: 'Juniper List' <[email protected]>
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.1X54--------17.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: forwarding        State: Active

-Aaron


_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to