OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
gra-3ab-6k
Incident
Report for Network & Infrastructure
Resolved
Le routeur est down. nous investiguons.
The router is down, we're investigating.
Update(s):
Date: 2017-01-21 00:29:10 UTC
La mise à jour du router gra-3b-6k semble avoir stabilisé la situation, nous investiguons pour faire la maj du a car celui semble difficilement accessible dans son état.
The gra-3b-6k router update seems to have stabilized the situation. We are investigating to update the A Router, we are having difficulties reaching it in its current state.
Date: 2017-01-21 00:11:53 UTC
Le router gra-3b-6k est à jour. Nous passons à la mise à jour de gra-3a-6k.
Nous analysons une éventuelle corrélation avec un script de configuration par les robots du routeur.
The gra-3b-6k router is up-to-date. We're now updating the gra-3a-6k router.
We're analyzing an eventual correlation between a configuration script used by the robots on the router.
Date: 2017-01-20 23:48:15 UTC
Nous avons la confirmation d'un bug software par Cisco. Nous updatons à la dernière version.
We got the confirmation that there's a bug by Cisco. We are updating at the latest version.
Date: 2017-01-20 23:24:13 UTC
Nous sommes en cours d'investigation avec un ingénieur de chez Cisco pour comprendre les raisons des crash en boucle
Les routeurs tiennent quelques minutes après reload après crash avec une erreur du type :
Unexpected exception to CPU: vector 300
Cela nous fait penser à un problème hardware, mais il semble peut probable dans ce cas de figure (les 2 impactés en même temps).
Nous continuons d'investiguer avec le support P1 de chez cisco
------
We are still in contact with a Cisco Engeneer to understand the constant crashes.
The routers will only hold for a couple of minutes at a time, then reboot with errors like:
Unexpected exception to CPU: vector 300
That lead us to believe there's a hardware issue with the units, but it's unlikely since it's happening to both the unit at the same time.
We still investigating with the P1 Support from Cisco.
Date: 2017-01-20 23:05:02 UTC
Les réseaux IP suivants sont joignables actuellement mais ont été impactés:
The following networks are reachable, but were impacted:
5.196.95.0/24
5.196.94.0/24
5.196.89.0/24
5.196.88.0/24
5.196.75.0/24
5.196.74.0/24
5.196.73.0/24
5.196.72.0/24
5.196.71.0/24
5.196.70.0/24
5.196.69.0/24
5.196.68.0/24
5.196.67.0/24
5.196.66.0/24
5.196.65.0/24
37.187.99.0/24
37.187.98.0/24
37.187.97.0/24
37.187.96.0/24
37.187.95.0/24
37.187.94.0/24
37.187.93.0/24
37.187.92.0/24
37.187.91.0/24
37.187.90.0/24
37.187.9.0/24
37.187.89.0/24
37.187.88.0/24
37.187.8.0/24
37.187.79.0/24
37.187.78.0/24
37.187.77.0/24
37.187.76.0/24
37.187.75.0/24
37.187.74.0/24
37.187.73.0/24
37.187.72.0/24
37.187.7.0/24
37.187.6.0/24
37.187.5.0/24
37.187.4.0/24
37.187.31.0/24
37.187.30.0/24
37.187.3.0/24
37.187.29.0/24
37.187.28.0/24
37.187.27.0/24
37.187.26.0/24
37.187.25.0/24
37.187.24.0/24
37.187.23.0/24
37.187.22.0/24
37.187.21.0/24
37.187.20.0/24
37.187.2.0/24
37.187.19.0/24
37.187.18.0/24
37.187.17.0/24
37.187.16.0/24
37.187.15.0/24
37.187.14.0/24
37.187.13.0/24
37.187.129.0/24
37.187.128.0/24
37.187.127.0/24
37.187.126.0/24
37.187.125.0/24
37.187.124.0/24
37.187.123.0/24
37.187.122.0/24
37.187.121.0/24
37.187.120.0/24
37.187.12.0/24
37.187.119.0/24
37.187.118.0/24
37.187.117.0/24
37.187.116.0/24
37.187.115.0/24
37.187.114.0/24
37.187.113.0/24
37.187.112.0/24
37.187.111.0/24
37.187.110.0/24
37.187.11.0/24
37.187.109.0/24
37.187.108.0/24
37.187.107.0/24
37.187.106.0/24
37.187.105.0/24
37.187.104.0/24
37.187.103.0/24
37.187.102.0/24
37.187.101.0/24
37.187.100.0/24
37.187.10.0/24
37.187.1.0/24
37.187.0.0/24
178.32.32.0/24
151.80.47.0/24
151.80.46.0/24
151.80.45.0/24
151.80.44.0/24
151.80.43.0/24
151.80.42.0/24
151.80.41.0/24
151.80.40.0/24
151.80.38.0/24
151.80.37.0/24
Date: 2017-01-20 22:32:22 UTC
gra-3a-6k vien de rebooter, le couple est totalement down.
gra-3a-6k rebooted, both units are down.
Date: 2017-01-20 22:27:26 UTC
Le routeur B reboot en loop. Nous avons un crashfile. Nous ouvrons un case chez Cisco. Nous isolons le B pour prendre les traces.
The B Router reboots in loop. We have a crashfile. We opened a case with Cisco. We isolated the B router to capture traces.
Date: 2017-01-20 22:02:58 UTC
Nous avons le routeur b qui ne répond plus, nous investiguons
The B Router is unreachable, we're investigating.
Date: 2017-01-20 20:26:28 UTC
Le routeur a rebooté sans généré de logs. nous allons envoyer les infos technique à Cisco.
The router rebooted without generating logs. We're going to send the technicals informations to Cisco.
Date: 2017-01-20 20:24:43 UTC
Le routeur est revenu et maintenant stable.
The router is back online and stable.
The router is down, we're investigating.
Update(s):
Date: 2017-01-21 00:29:10 UTC
La mise à jour du router gra-3b-6k semble avoir stabilisé la situation, nous investiguons pour faire la maj du a car celui semble difficilement accessible dans son état.
The gra-3b-6k router update seems to have stabilized the situation. We are investigating to update the A Router, we are having difficulties reaching it in its current state.
Date: 2017-01-21 00:11:53 UTC
Le router gra-3b-6k est à jour. Nous passons à la mise à jour de gra-3a-6k.
Nous analysons une éventuelle corrélation avec un script de configuration par les robots du routeur.
The gra-3b-6k router is up-to-date. We're now updating the gra-3a-6k router.
We're analyzing an eventual correlation between a configuration script used by the robots on the router.
Date: 2017-01-20 23:48:15 UTC
Nous avons la confirmation d'un bug software par Cisco. Nous updatons à la dernière version.
We got the confirmation that there's a bug by Cisco. We are updating at the latest version.
Date: 2017-01-20 23:24:13 UTC
Nous sommes en cours d'investigation avec un ingénieur de chez Cisco pour comprendre les raisons des crash en boucle
Les routeurs tiennent quelques minutes après reload après crash avec une erreur du type :
Unexpected exception to CPU: vector 300
Cela nous fait penser à un problème hardware, mais il semble peut probable dans ce cas de figure (les 2 impactés en même temps).
Nous continuons d'investiguer avec le support P1 de chez cisco
------
We are still in contact with a Cisco Engeneer to understand the constant crashes.
The routers will only hold for a couple of minutes at a time, then reboot with errors like:
Unexpected exception to CPU: vector 300
That lead us to believe there's a hardware issue with the units, but it's unlikely since it's happening to both the unit at the same time.
We still investigating with the P1 Support from Cisco.
Date: 2017-01-20 23:05:02 UTC
Les réseaux IP suivants sont joignables actuellement mais ont été impactés:
The following networks are reachable, but were impacted:
5.196.95.0/24
5.196.94.0/24
5.196.89.0/24
5.196.88.0/24
5.196.75.0/24
5.196.74.0/24
5.196.73.0/24
5.196.72.0/24
5.196.71.0/24
5.196.70.0/24
5.196.69.0/24
5.196.68.0/24
5.196.67.0/24
5.196.66.0/24
5.196.65.0/24
37.187.99.0/24
37.187.98.0/24
37.187.97.0/24
37.187.96.0/24
37.187.95.0/24
37.187.94.0/24
37.187.93.0/24
37.187.92.0/24
37.187.91.0/24
37.187.90.0/24
37.187.9.0/24
37.187.89.0/24
37.187.88.0/24
37.187.8.0/24
37.187.79.0/24
37.187.78.0/24
37.187.77.0/24
37.187.76.0/24
37.187.75.0/24
37.187.74.0/24
37.187.73.0/24
37.187.72.0/24
37.187.7.0/24
37.187.6.0/24
37.187.5.0/24
37.187.4.0/24
37.187.31.0/24
37.187.30.0/24
37.187.3.0/24
37.187.29.0/24
37.187.28.0/24
37.187.27.0/24
37.187.26.0/24
37.187.25.0/24
37.187.24.0/24
37.187.23.0/24
37.187.22.0/24
37.187.21.0/24
37.187.20.0/24
37.187.2.0/24
37.187.19.0/24
37.187.18.0/24
37.187.17.0/24
37.187.16.0/24
37.187.15.0/24
37.187.14.0/24
37.187.13.0/24
37.187.129.0/24
37.187.128.0/24
37.187.127.0/24
37.187.126.0/24
37.187.125.0/24
37.187.124.0/24
37.187.123.0/24
37.187.122.0/24
37.187.121.0/24
37.187.120.0/24
37.187.12.0/24
37.187.119.0/24
37.187.118.0/24
37.187.117.0/24
37.187.116.0/24
37.187.115.0/24
37.187.114.0/24
37.187.113.0/24
37.187.112.0/24
37.187.111.0/24
37.187.110.0/24
37.187.11.0/24
37.187.109.0/24
37.187.108.0/24
37.187.107.0/24
37.187.106.0/24
37.187.105.0/24
37.187.104.0/24
37.187.103.0/24
37.187.102.0/24
37.187.101.0/24
37.187.100.0/24
37.187.10.0/24
37.187.1.0/24
37.187.0.0/24
178.32.32.0/24
151.80.47.0/24
151.80.46.0/24
151.80.45.0/24
151.80.44.0/24
151.80.43.0/24
151.80.42.0/24
151.80.41.0/24
151.80.40.0/24
151.80.38.0/24
151.80.37.0/24
Date: 2017-01-20 22:32:22 UTC
gra-3a-6k vien de rebooter, le couple est totalement down.
gra-3a-6k rebooted, both units are down.
Date: 2017-01-20 22:27:26 UTC
Le routeur B reboot en loop. Nous avons un crashfile. Nous ouvrons un case chez Cisco. Nous isolons le B pour prendre les traces.
The B Router reboots in loop. We have a crashfile. We opened a case with Cisco. We isolated the B router to capture traces.
Date: 2017-01-20 22:02:58 UTC
Nous avons le routeur b qui ne répond plus, nous investiguons
The B Router is unreachable, we're investigating.
Date: 2017-01-20 20:26:28 UTC
Le routeur a rebooté sans généré de logs. nous allons envoyer les infos technique à Cisco.
The router rebooted without generating logs. We're going to send the technicals informations to Cisco.
Date: 2017-01-20 20:24:43 UTC
Le routeur est revenu et maintenant stable.
The router is back online and stable.
This incident affected: Infrastructure || GRA (GRA1, GRA2, GRA3).