[j-nsp] How to pick JUNOS Version

[aaron1 at gvtc.com]

Thanks KV, also, if you just wanted to clear that high cpu thing, you can do this...

show system processes extensive | except 0.0

* get the process ID of the fxpc hogging process...in this case it's 1820

me at acx5048> show system processes extensive | except 0.0
last pid:  7231;  load averages:  0.89,  0.93,  0.91  up 516+22:09:03    23:07:23
144 processes: 5 running, 118 sleeping, 21 waiting

Mem: 625M Active, 296M Inact, 471M Wired, 425M Cache, 69M Buf, 32M Free
Swap:

  PID USERNAME  THR PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND
 1820 root        2 -51  -51  1185M   501M select    ??? 96.97% fxpc

* NOTE, when you hit enter on the KILL command, cursor may continue to blink, and you might think it didn't take your input, but it did... pings will start to die

start shell user root 
(enter root pwd)

kill -9 1820

-Aaron


-----Original Message-----
From: Kody Vicknair <kvicknair at reservetele.com> 
Sent: Wednesday, September 2, 2020 2:08 AM
To: aaron1 at gvtc.com; 'Roger Wiklund' <roger.wiklund at gmail.com>; 'Colton Conor' <colton.conor at gmail.com>
Cc: 'Juniper List' <juniper-nsp at puck.nether.net>
Subject: RE: [j-nsp] How to pick JUNOS Version

Aaron,

1. yes, I've seen this kb, but when I had someone I trust look at the diff, + the nature of the changes they were suggesting, I just wasn't comfortable making those changes. I personally avoided this at all cost. In my case, installs took about ~7 minutes per acx in a maintenance window and a majority of the routers are local, so it wasn't a big deal.

2. Not that I'm aware. I was including the caveat because for some reason during initial config we used vme.0 interfaces instead of em0.0 and I ran into issues with it not working properly in a lab setting and vme.0 was the gotcha for me.

By the way, I was seeing the same PR1419761 issues you are seeing, those have been resolved since upgrading.

-kv


-----Original Message-----
From: aaron1 at gvtc.com <aaron1 at gvtc.com> 
Sent: Wednesday, September 2, 2020 1:22 AM
To: Kody Vicknair <kvicknair at reservetele.com>; 'Roger Wiklund' <roger.wiklund at gmail.com>; 'Colton Conor' <colton.conor at gmail.com>
Cc: 'Juniper List' <juniper-nsp at puck.nether.net>
Subject: RE: [j-nsp] How to pick JUNOS Version

*External Email: Use Caution*

1 - https://link.edgepilot.com/s/6890e15f/hA34W4NyWUumQulQkNIdtw?u=https://kb.juniper.net/InfoCenter/index?page=content%26id=KB33988
(pretty sure that avoids the usb craziness, if memory serves me right, I think Juniper created that KB from my lab 5048 test back in March 2019. Now I'm wondering if I tried to go to like 15.x.D61 or something prior to trying to go to 17.3 if that would've helped)

2 - Virtual Chassis on an ACX5048?  Can you do that?

-Aaron

-----Original Message-----
From: Kody Vicknair <kvicknair at reservetele.com>
Sent: Tuesday, September 1, 2020 7:52 PM
To: aaron1 at gvtc.com; 'Roger Wiklund' <roger.wiklund at gmail.com>; 'Colton Conor' <colton.conor at gmail.com>
Cc: 'Juniper List' <juniper-nsp at puck.nether.net>
Subject: 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: aaron1 at gvtc.com <aaron1 at gvtc.com>
Sent: Tuesday, September 1, 2020 5:34 PM
To: Kody Vicknair <kvicknair at reservetele.com>; 'Roger Wiklund'
<roger.wiklund at gmail.com>; 'Colton Conor' <colton.conor at gmail.com>
Cc: 'Juniper List' <juniper-nsp at puck.nether.net>
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 at acx5048> show system information | grep Junos
Family: junos
Junos: 17.4R2-S11

name at acx5048> show route instance mgmt_junos detail
mgmt_junos:
  Router ID: 0.0.0.0
  Type: forwarding        State: Active

-Aaron





Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.