Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
The 2 pairs Nexus 5548 which manage these 4 networks have been affected by Cisco bug CSCuo46284.
There is no impact on the forwarding, however, configuration robots are failing during certain operations.
We must initially reload each switch. There will be no impact, thanks to the VPC and fex on dual home.
Then we will update them on ISSU. we have 2 ISSU steps to take in order to arrive at 7.1.3.n1.4.
- Monday, May 30th 9am CEST (3am): reload the 4 switches
- Tuesday, May 31st 9am CEST (3am): ISSU on the switch of networks: 142.4.216.0/24 & 217.0/24
- Wednesday, June 1st 9am CEST (3am): ISSU on the switch of networks: 198.27.74.0/24 & 75.0/24
Update(s):
Date: 2016-05-30 14:15:59 UTC No configuration difficulties were detected, so the crash on ports security was strange.
We uploaded the crash core file for investigation.
We also set up the fex 1 by 1 and there was no crash.
The switches need to be updated, which will be done tomorrow afternoon.
Date: 2016-05-30 14:12:20 UTC Switch B of 198.27.74.0/24 & 75.0/24 crashed on eth_portsec
We stabilized it by cutting the po to the fex on switch B,
Date: 2016-05-30 14:08:44 UTC Switch B of 198.27.74.0/24 & 75.0/24 in progress
Switch A of 142.4.216.0/24 & 217.0/24 in progress
Switch B of 142.4.216.0/24 & 217.0/24 in progress
Switch A of 198.27.74.0/24 & 75.0/24 in progress
Date: 2016-05-30 14:07:45 UTC switch B of network 142.4.216.0/24 & 217.0/24 in progress
Switch A of network 198.27.74.0/24 & 75.0/24 in progress => we are fixing the mismatch speed
Switch B of network 198.27.74.0/24 & 75.0/24 STAND BY
switch A of network 142.4.216.0/24 & 217.0/24 DONE
Date: 2016-05-30 14:06:09 UTC Switch A of network 142.4.216.0/24 & 217.0/24 is UP, we are fixing the last mismatch speed.
Switch A of network 198.27.74.0/24 & 75.0/24 IN PROGRESS.
Date: 2016-05-30 14:05:23 UTC Starting reload switch A de 142.4.216.0/24 & 217.0/24