[j-nsp] mx304 alarm seen after junos upgrade

[Aaron1]

Resolved… with the following…

FPC showed a difference between what was running and what is available… reminiscent of IOS-XR upgrades and subsequent fpd/fpga upgrades.


show system firmware

FPC 0            ZL30634 DPLL      9   6022.0.0              7006.0.0              OK

request system firmware upgrade fpc slot 0

request chassis fpc restart slot 0

Aaron

> On Feb 29, 2024, at 8:14 PM, Aaron Gould <aaron1 at gvtc.com> wrote:
> 
> Anyone ever seen this alarm on an MX304 following a Junos upgrade?
> 
> I went from ...
> 
> 22.2R3-S1.9 - initially had this
> 22.4R2-S2.6 - upgrade
> 23.2R1-S2.5 - final
> 
> now with23.2R1-S2.5, i have an issue with more than one, 100g interfaces being able to operate.  I have a 100g on et-0/0/4 and another one on et-0/0/12... BUT, they won't both function at the same time.  4 works, 12 doesn't... reboot mx304, 4 doesn't work, but 12 does. Very weird.
> 
> root at 304-1> show system alarms
> 6 alarms currently active
> Alarm time               Class  Description
> 2024-02-29 06:00:25 CST  Minor  200 ADVANCE Bandwidth (in gbps)s(315) require a license
> 2024-02-29 06:00:25 CST  Minor  OSPF protocol(282) usage requires a license
> 2024-02-29 06:00:25 CST  Minor  LDP Protocol(257) usage requires a license
> 2024-02-28 09:35:10 CST  Minor *FPC 0 firmware outdated*
> 2024-02-28 09:29:45 CST  Major  Host 0 fxp0 : Ethernet Link Down
> 2024-02-28 09:28:15 CST  Major  Management Ethernet Links Down
> 
> 
> root at 304-1> show chassis alarms
> 3 alarms currently active
> Alarm time               Class  Description
> 2024-02-28 09:35:10 CST  Minor *FPC 0 firmware outdated*
> 2024-02-28 09:29:45 CST  Major  Host 0 fxp0 : Ethernet Link Down
> 2024-02-28 09:28:15 CST  Major  Management Ethernet Links Down
> 
> 
> --
> -Aaron
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp