Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
Currently this network is using Nexus 5010.
We will change it and implement more performing switches, Nexus 5548.
Update(s):
Date: 2013-04-11 23:49:36 UTC The upgrade was completed but did not fix the problems on the ipmi vlan and the vracks' netboot .
Regarding IPMI, we established a workaround and we are operating normally.
Netboot problems for vrack customers persist for now. We will continue our investigations with Cisco engineers.
Date: 2013-04-11 23:45:57 UTC We will reboot the second switch in order to continue the update.
Traffic to the network 178.33.62 will be impacted for a few minutes.
Date: 2013-04-11 23:44:50 UTC We resumed the upgrade of the platform.
Date: 2013-04-11 23:44:09 UTC The quick upgrade went wrong, the situation is that a switch was upgraded and the other one was not. The FEX and primary switch are still using the old release.
If the quick upgrade fails again on the second switch, there is a risk of a longer downtime because the images of the new release should be downloaded by the switch on all FEX. We will therefore postpone the upgrade till later in the evening to minimize the impact on our customers.
We are planning to resume the intervention at 23:00.
Date: 2013-04-11 23:38:45 UTC The ISSU upgrade went wrong and traffic to the servers was impacted.
sw-n5-62.249# sh install all failure-reason
Install has failed. Return code 0x40930039 (aborting due to failed upgrade)
The infrastructure is now up but in a degraded status.