OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#11589 — gra-3a-a9
Incident
Report for Network & Infrastructure
Resolved
The router is inaccessible, there is no impact on traffic.
The add/edit for IP FO or virtual mac are impacted.
Update(s):
Date: 2014-09-17 02:48:22 UTC
The traffic we reset on gra-3a-a9.
We din't notice any CRC!
--
The Network Team (Always there to protect OVH network).
Date: 2014-09-17 02:44:03 UTC
The card has been replaced.
We will resume traffic on gra-3a-a9.
Date: 2014-09-16 12:06:39 UTC
The update is now complete.
Following this update, there is an error with a 24*10G card:
LC/0/0/CPU0:Sep 16 11:25:20.760 : prm_server_ty[300]: %PLATFORM-NP-0-INIT_ERR : Device BST memory test failure 0x80001760 on NP channel 5 external search memory, memory ID 0
LC/0/0/CPU0:Sep 16 13:30:03.874 CEST: prm_server_ty[300]: %PLATFORM-NP-0-INIT_ERR : Device BST memory test failure 0x80001760 on NP channel 5 external search memory, memory ID 0
LC/0/0/CPU0:Sep 16 13:43:36.711 CEST: prm_server_ty[300]: %PLATFORM-NP-0-INIT_ERR : Device BST memory test failure 0x80001760 on NP channel 5 external search memory, memory ID 0
We will organise for the card to be replaced.
Date: 2014-09-16 12:05:37 UTC
The rooter is isolated. We are updating it.
Date: 2014-09-16 12:05:12 UTC
To implement redundancy between the 2 RSPs, we will update RSP1 to 5.1.3.
During the update, the traffic will be rooted via gra-3b-a9.
Date: 2014-09-16 05:54:52 UTC
We have reloaded the first RSP, but it blocks on mgmt interface configuration (for no clear reason).
Details
--------
Current active rmf state: 4 (I_READY)
Reason for standby not ready
162 0/RSP0/CPU0 cfgmgr-rp Management interface configuration not yet applied
Not ready set Mon Sep 15 20:57:28 2014: 10 minutes ago
Current active rmf state for NSR: Ready
All standby not-ready NSR bits clear - standby should be NSR-ready
There fore, we can not commit configurations.
We unclipped the chassis card to allow the robot to work.
We will investigate with Cisco.
The problem of bonded session and the problem of mgmt interface configuration does not seem related.
Date: 2014-09-16 05:51:19 UTC
The limit of connections on the router has been reached, many session were \"Stuck\"
We made a switchover on the 2nd RSP.
We have access to the router.
The add/edit for IP FO or virtual mac are impacted.
Update(s):
Date: 2014-09-17 02:48:22 UTC
The traffic we reset on gra-3a-a9.
We din't notice any CRC!
--
The Network Team (Always there to protect OVH network).
Date: 2014-09-17 02:44:03 UTC
The card has been replaced.
We will resume traffic on gra-3a-a9.
Date: 2014-09-16 12:06:39 UTC
The update is now complete.
Following this update, there is an error with a 24*10G card:
LC/0/0/CPU0:Sep 16 11:25:20.760 : prm_server_ty[300]: %PLATFORM-NP-0-INIT_ERR : Device BST memory test failure 0x80001760 on NP channel 5 external search memory, memory ID 0
LC/0/0/CPU0:Sep 16 13:30:03.874 CEST: prm_server_ty[300]: %PLATFORM-NP-0-INIT_ERR : Device BST memory test failure 0x80001760 on NP channel 5 external search memory, memory ID 0
LC/0/0/CPU0:Sep 16 13:43:36.711 CEST: prm_server_ty[300]: %PLATFORM-NP-0-INIT_ERR : Device BST memory test failure 0x80001760 on NP channel 5 external search memory, memory ID 0
We will organise for the card to be replaced.
Date: 2014-09-16 12:05:37 UTC
The rooter is isolated. We are updating it.
Date: 2014-09-16 12:05:12 UTC
To implement redundancy between the 2 RSPs, we will update RSP1 to 5.1.3.
During the update, the traffic will be rooted via gra-3b-a9.
Date: 2014-09-16 05:54:52 UTC
We have reloaded the first RSP, but it blocks on mgmt interface configuration (for no clear reason).
Details
--------
Current active rmf state: 4 (I_READY)
Reason for standby not ready
162 0/RSP0/CPU0 cfgmgr-rp Management interface configuration not yet applied
Not ready set Mon Sep 15 20:57:28 2014: 10 minutes ago
Current active rmf state for NSR: Ready
All standby not-ready NSR bits clear - standby should be NSR-ready
There fore, we can not commit configurations.
We unclipped the chassis card to allow the robot to work.
We will investigate with Cisco.
The problem of bonded session and the problem of mgmt interface configuration does not seem related.
Date: 2014-09-16 05:51:19 UTC
The limit of connections on the router has been reached, many session were \"Stuck\"
We made a switchover on the 2nd RSP.
We have access to the router.