OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#9706 — Dedicated network switches update - 2
Scheduled Maintenance
Report for Network & Infrastructure
Completed
Cisco has identified that the encountered issues during the last upgrade campaign ( http://status.ovh.net/?do=details&id=5647 ) is regarding a specific range of hardware.
We will resume the upgrade campaign for the Nexus 5000 which are not concerned by the encountered bug.
Meanwhile the Cisco BU wrks on an engineering image which fixes the BUG.
The first upgrade set is planned for Tuesday 19 November starting from 23h00 (FR time) and will cover the following networks:
176.31.232.0/24
176.31.233.0/24
176.31.234.0/24
176.31.235.0/24
176.31.236.0/24
176.31.237.0/24
176.31.238.0/24
176.31.239.0/24
178.33.228.0/24
178.33.229.0/24
178.33.230.0/24
178.33.231.0/24
188.165.12.0/24
188.165.13.0/24
188.165.14.0/24
188.165.15.0/24
178.33.241.0/24
178.33.242.0/24
178.33.60.0/24
178.33.61.0/24
178.33.62.0/24
178.33.63.0/24
37.59.16.0/24
37.59.17.0/24
37.59.18.0/24
37.59.19.0/24
Update(s):
Date: 2013-12-10 12:01:39 UTC
All UP type MAJs on the switches are finished. Due to a bug, we can't apply the MAJ on the P type switch at the moment. So we will update those switches with a future release where the bug will be fixed.
Date: 2013-12-04 08:44:01 UTC
The updates are finished.
Date: 2013-12-04 08:43:45 UTC
We have an issue with 1 of the 2 switches on networks 5.39.74.0 and 5.39.75.0
the ISSU upgrade went well but the QOS could not be reapplied.
On rebooting one swicth, the second switch froze causing the networks to go down for a few minutes.
Date: 2013-12-04 08:41:50 UTC
There's an anomaly on networks 37.59.32 and 33. The instant upgrade
went smoothly on 1 of the 2 switches, however 2 devices rebooted
on the other switch. There will be a few minutes impact on these
networks.
Date: 2013-12-03 22:14:40 UTC
We also have issues on another pair of the switch which impacted the networks 37.59.24 and 25. We will have an impact of 10min on these networks.
Date: 2013-12-03 22:13:12 UTC
We have an incident on the networks 5.135.138.0/24 5.135.139.0/24 , the traffic is impacted by the upgrade which is in progress on one of the switches. We restarted the secondary n5.
There will be about 10min of downtime on the servers of that network.
Date: 2013-12-03 22:08:33 UTC
We started the intervention.
Date: 2013-12-02 20:37:38 UTC
The next upgrade session session of the N5 switches is planned on Tuesday 03/12 at 11:00pm.
These networks will be concerned:
37.59.18.0/24
37.59.19.0/24
37.59.24.0/24
37.59.25.0/24
37.59.26.0/24
37.59.27./024
37.59.32.0/24
37.59.33.0/24
37.59.34.0/24
37.59.35.0/24
5.39.64.0/24
5.39.65.0/24
5.39.66.0/24
5.39.67.0/24
5.39.68.0/24
5.39.69.0/24
5.39.72.0/24
5.39.73.0/24
5.39.74.0/24
5.39.75.0/24
5.135.128.0/24
5.135.129.0/24
5.135.134.0/24
5.135.135.0/24
5.135.136.0/24
5.135.137.0/24
5.135.138.0/24
5.135.139.0/24
5.135.140.0/24
5.135.141.0/24
46.105.104.0/24
46.105.105.0/24
There are hotswap upgrades, so there will be no impact basically but the traffic will be \"at risk\".
Date: 2013-11-20 14:17:09 UTC
All the BHS dedicated server n5s are now up-to-date.
Date: 2013-11-20 12:59:15 UTC
One of the switches went down during the hotswapping process
The secind switch also crashed a few minutes later.
There was downtime of around 10mins on the servers on the network.
This is because the FEXs needed a coldswap.
Date: 2013-11-20 11:47:35 UTC
We have an incident on the 198.27.85.0/24 network, where the traffic has been affected by the upgrade in progress on one of the switches. We're working on it.
Date: 2013-11-20 11:17:18 UTC
We're instantly updating the BHS n5s.
The following networks will be affected:
198.27.85.0/24
142.4.218.0/24
142.4.219.0/24
Date: 2013-11-20 01:34:36 UTC
The upgrades have ended.
Only the following networks haven't been migrated tonight. They will be upgraded within a future window.
37.59.18.0/24
37.59.19.0/24
Date: 2013-11-20 01:32:23 UTC
We have had a crash on one of the switches while proceeding to perform a hotswap upgrade. We will manually accomplish the procedure but there will be a downtime for about 10min on the servers in this network.
Date: 2013-11-19 23:45:50 UTC
The upgrades are processing.
We are having an incident on the network 188.165.14 where the traffic is impacted by the upgrade which is processing on one of the switches. We are working on the issue.
Date: 2013-11-19 23:44:05 UTC
We are starting the updates (hotswap) the following networks:
176.31.232.0/24
176.31.233.0/24
176.31.234.0/24
176.31.235.0/24
176.31.236.0/24
176.31.237.0/24
176.31.238.0/24
176.31.239.0/24
178.33.228.0/24
178.33.229.0/24
178.33.230.0/24
178.33.231.0/24
188.165.12.0/24
188.165.13.0/24
188.165.14.0/24
188.165.15.0/24
178.33.241.0/24
178.33.242.0/24
178.33.60.0/24
178.33.61.0/24
178.33.62.0/24
178.33.63.0/24
37.59.16.0/24
37.59.17.0/24
37.59.18.0/24
37.59.19.0/24
Date: 2013-11-19 23:42:49 UTC
The nexus 5000 in BHS managing these networks are now updated.
Date: 2013-11-19 23:42:01 UTC
We are updating the n5 and BHS.
The following networks are concerned by the upgrade:
142.4.216.0/24
142.4.217.0/24
192.95.32.0/24
192.95.33.0/24
192.99.16.0/24
192.99.17.0/24
We will resume the upgrade campaign for the Nexus 5000 which are not concerned by the encountered bug.
Meanwhile the Cisco BU wrks on an engineering image which fixes the BUG.
The first upgrade set is planned for Tuesday 19 November starting from 23h00 (FR time) and will cover the following networks:
176.31.232.0/24
176.31.233.0/24
176.31.234.0/24
176.31.235.0/24
176.31.236.0/24
176.31.237.0/24
176.31.238.0/24
176.31.239.0/24
178.33.228.0/24
178.33.229.0/24
178.33.230.0/24
178.33.231.0/24
188.165.12.0/24
188.165.13.0/24
188.165.14.0/24
188.165.15.0/24
178.33.241.0/24
178.33.242.0/24
178.33.60.0/24
178.33.61.0/24
178.33.62.0/24
178.33.63.0/24
37.59.16.0/24
37.59.17.0/24
37.59.18.0/24
37.59.19.0/24
Update(s):
Date: 2013-12-10 12:01:39 UTC
All UP type MAJs on the switches are finished. Due to a bug, we can't apply the MAJ on the P type switch at the moment. So we will update those switches with a future release where the bug will be fixed.
Date: 2013-12-04 08:44:01 UTC
The updates are finished.
Date: 2013-12-04 08:43:45 UTC
We have an issue with 1 of the 2 switches on networks 5.39.74.0 and 5.39.75.0
the ISSU upgrade went well but the QOS could not be reapplied.
On rebooting one swicth, the second switch froze causing the networks to go down for a few minutes.
Date: 2013-12-04 08:41:50 UTC
There's an anomaly on networks 37.59.32 and 33. The instant upgrade
went smoothly on 1 of the 2 switches, however 2 devices rebooted
on the other switch. There will be a few minutes impact on these
networks.
Date: 2013-12-03 22:14:40 UTC
We also have issues on another pair of the switch which impacted the networks 37.59.24 and 25. We will have an impact of 10min on these networks.
Date: 2013-12-03 22:13:12 UTC
We have an incident on the networks 5.135.138.0/24 5.135.139.0/24 , the traffic is impacted by the upgrade which is in progress on one of the switches. We restarted the secondary n5.
There will be about 10min of downtime on the servers of that network.
Date: 2013-12-03 22:08:33 UTC
We started the intervention.
Date: 2013-12-02 20:37:38 UTC
The next upgrade session session of the N5 switches is planned on Tuesday 03/12 at 11:00pm.
These networks will be concerned:
37.59.18.0/24
37.59.19.0/24
37.59.24.0/24
37.59.25.0/24
37.59.26.0/24
37.59.27./024
37.59.32.0/24
37.59.33.0/24
37.59.34.0/24
37.59.35.0/24
5.39.64.0/24
5.39.65.0/24
5.39.66.0/24
5.39.67.0/24
5.39.68.0/24
5.39.69.0/24
5.39.72.0/24
5.39.73.0/24
5.39.74.0/24
5.39.75.0/24
5.135.128.0/24
5.135.129.0/24
5.135.134.0/24
5.135.135.0/24
5.135.136.0/24
5.135.137.0/24
5.135.138.0/24
5.135.139.0/24
5.135.140.0/24
5.135.141.0/24
46.105.104.0/24
46.105.105.0/24
There are hotswap upgrades, so there will be no impact basically but the traffic will be \"at risk\".
Date: 2013-11-20 14:17:09 UTC
All the BHS dedicated server n5s are now up-to-date.
Date: 2013-11-20 12:59:15 UTC
One of the switches went down during the hotswapping process
The secind switch also crashed a few minutes later.
There was downtime of around 10mins on the servers on the network.
This is because the FEXs needed a coldswap.
Date: 2013-11-20 11:47:35 UTC
We have an incident on the 198.27.85.0/24 network, where the traffic has been affected by the upgrade in progress on one of the switches. We're working on it.
Date: 2013-11-20 11:17:18 UTC
We're instantly updating the BHS n5s.
The following networks will be affected:
198.27.85.0/24
142.4.218.0/24
142.4.219.0/24
Date: 2013-11-20 01:34:36 UTC
The upgrades have ended.
Only the following networks haven't been migrated tonight. They will be upgraded within a future window.
37.59.18.0/24
37.59.19.0/24
Date: 2013-11-20 01:32:23 UTC
We have had a crash on one of the switches while proceeding to perform a hotswap upgrade. We will manually accomplish the procedure but there will be a downtime for about 10min on the servers in this network.
Date: 2013-11-19 23:45:50 UTC
The upgrades are processing.
We are having an incident on the network 188.165.14 where the traffic is impacted by the upgrade which is processing on one of the switches. We are working on the issue.
Date: 2013-11-19 23:44:05 UTC
We are starting the updates (hotswap) the following networks:
176.31.232.0/24
176.31.233.0/24
176.31.234.0/24
176.31.235.0/24
176.31.236.0/24
176.31.237.0/24
176.31.238.0/24
176.31.239.0/24
178.33.228.0/24
178.33.229.0/24
178.33.230.0/24
178.33.231.0/24
188.165.12.0/24
188.165.13.0/24
188.165.14.0/24
188.165.15.0/24
178.33.241.0/24
178.33.242.0/24
178.33.60.0/24
178.33.61.0/24
178.33.62.0/24
178.33.63.0/24
37.59.16.0/24
37.59.17.0/24
37.59.18.0/24
37.59.19.0/24
Date: 2013-11-19 23:42:49 UTC
The nexus 5000 in BHS managing these networks are now updated.
Date: 2013-11-19 23:42:01 UTC
We are updating the n5 and BHS.
The following networks are concerned by the upgrade:
142.4.216.0/24
142.4.217.0/24
192.95.32.0/24
192.95.33.0/24
192.99.16.0/24
192.99.17.0/24