Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
We are starting an update campaign on some dedicated network switches.
Update(s):
Date: 2013-10-23 01:38:38 UTC The switches of the networks 176.31.224 and 225 are now downgraded and are back to normal. We will work with Cisco to determine the source of the issue.
On 226/227 we have rebooted one of the switches of the pair then the second as one or several fex are still missing the call. we are now again in a stable status for these networks with redundancy. All fex are being known again on each of both chassis.
Here's the final list of the updated networks tonight. There was no major impact on the traffic out of 4 networks on which we have encountered difficulties detailed above.
rollback for these 2 following networks:
176.31.224.0/24
176.31.225.0/24
Date: 2013-10-23 01:01:17 UTC We are having difficulties on the following networks:
176.31.224 à 227/24
On the 2x2 switches connecting these networks, the update didn't go well.
On 224/225:
The fex on which the servers are connected are going offline within few minutes. We have decided to downgrade to the previous version.
On 226/227:
2 fex (around 96 servers) are only running on one switch of the pair rather than 2. the traffic shouldn't be impacted. We are carrying on the troubleshooting to recover the redundancy.