Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
We will update this Nexus pair on March 3rd as of 11pm.
The update is expected to be disruptive for the Nexux pair, because the pair is only constituted by fex2348, on which we have to upgrade the PHY (firmware managing interfaces) fex2348 implying a fex reload (2-3min of down).
If we need to reload all fex, it is better on disruptive ISSU, which is in charge of preloading the new image in the fex, and reloading them one by one.
Date: 2016-03-04 03:46:15 UTC We reloaded the fex to update PHY
bg2-20b-n56#
sbg2-20b-n56# reload fex 101
WARNING: This command will reboot FEX 101
Do you want to continue? (y/n) [n] y
sbg2-20b-n56#
sbg2-20b-n56#
sbg2-20b-n56#
sbg2-20b-n56#
sbg2-20b-n56#
sbg2-20b-n56#
sbg2-20b-n56#
sbg2-20b-n56# reload fex 102
WARNING: This command will reboot FEX 102
Do you want to continue? (y/n) [n] y
sbg2-20b-n56#
Date: 2016-03-04 03:45:48 UTC reload of A is in progress
sbg2-20a-n56# wr
[########################################] 100%d
Copy complete, now saving to disk (please wait)...
sbg2-20a-n56# reload
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y
[ 6873.695570] Shutdown Ports..
[ 6873.729872] writing reset reason 9,
[ 6873.774594] Resetting board
...............................................................................
....................................Image verification OK
Booting kernel
INIT: devmemfd:0x7fab4dd8
Date: 2016-03-04 03:45:15 UTC 20A finalized their ISSU without problems, but B crashed later with no apparent reason.
Traffic was still forwarded by 20A until some point, we started losing IPs,it came back then we had a total blow up.
We have updgraded 20B... fex are attached above it.