OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#12301 — VAC2
Incident
Report for Network & Infrastructure
Resolved
There's an issue with vac2-0-a9:
RP/0/RSP0/CPU0:vac2-0-a9#sh ip bgp sum
Fri Jan 2 14:14:07.528 CEST
PID 1082794310: _dl_abort. libtermcap.dll:dllmgr: Failed to allocate data segment for dll libtermcap.dll [Not enough memory]
PID 1082794311: _dl_abort. libbgp_client_util.dll:dllmgr: Failed to allocate data segment for dll libbgp_client_util.dll [Not enough memory]
PID 1082790213: _dl_abort. libttyctl.dll:dllmgr: Failed to allocate data segment for dll libttyctl.dll [Not enough memory]
Update(s):
Date: 2015-01-02 15:20:16 UTC
The configuration is synchronised.
UP.
Date: 2015-01-02 15:17:39 UTC
vac2-0-a9 is UP.
We're resynchronising the configuration to get it back into operation.
We're also looking at the logs to understand what caused the issue.
there were no issues with vac1-0-a9 and vac3-0a-9. It's an ASR9001:
vac1-0-a9 en 4.3.1 no issues
vac2-0-a9 en 5.1.3 issue
vac3-0-a9 en 5.1.3 no issues
It's down to some lovely bugs which have got the year off to a great start!
Date: 2015-01-02 13:09:53 UTC
We're going to reboot it.
Impossible in software.
We will reboot the hardware.
Reboot underway.
Date: 2015-01-02 09:22:38 UTC
The rest of the follow-up will be detailed in this task: https://status.ovh.net/?do=details&id=8387
RP/0/RSP0/CPU0:vac2-0-a9#sh ip bgp sum
Fri Jan 2 14:14:07.528 CEST
PID 1082794310: _dl_abort. libtermcap.dll:dllmgr: Failed to allocate data segment for dll libtermcap.dll [Not enough memory]
PID 1082794311: _dl_abort. libbgp_client_util.dll:dllmgr: Failed to allocate data segment for dll libbgp_client_util.dll [Not enough memory]
PID 1082790213: _dl_abort. libttyctl.dll:dllmgr: Failed to allocate data segment for dll libttyctl.dll [Not enough memory]
Update(s):
Date: 2015-01-02 15:20:16 UTC
The configuration is synchronised.
UP.
Date: 2015-01-02 15:17:39 UTC
vac2-0-a9 is UP.
We're resynchronising the configuration to get it back into operation.
We're also looking at the logs to understand what caused the issue.
there were no issues with vac1-0-a9 and vac3-0a-9. It's an ASR9001:
vac1-0-a9 en 4.3.1 no issues
vac2-0-a9 en 5.1.3 issue
vac3-0-a9 en 5.1.3 no issues
It's down to some lovely bugs which have got the year off to a great start!
Date: 2015-01-02 13:09:53 UTC
We're going to reboot it.
Impossible in software.
We will reboot the hardware.
Reboot underway.
Date: 2015-01-02 09:22:38 UTC
The rest of the follow-up will be detailed in this task: https://status.ovh.net/?do=details&id=8387