OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#6740 — vss-7ab
Incident
Report for Network & Infrastructure
Resolved
We are dealing with it.
Update(s):
Date: 2012-05-17 02:10:07 UTC
May 16 07:49:28 vss-7a-6k 59778: May 16 05:49:03.406: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 12)
May 16 10:50:39 vss-7a-6k 59839: May 16 08:50:14.344: %SIBYTE-DFC9-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 25)
May 16 12:41:02 vss-7a-6k 59893: May 16 10:40:37.571: %SIBYTE-DFC6-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 6)
May 16 15:35:07 vss-7a-6k 59977: May 16 13:34:42.817: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 13)
May 16 16:15:40 vss-7a-6k 59989: May 16 14:15:15.547: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 14)
May 16 19:09:32 vss-7a-6k 60050: May 16 17:09:07.213: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 15)
Date: 2012-05-17 02:10:00 UTC
we've seen this morning on the vss-7a
May 16 08:50:14.344: %SIBYTE-DFC9-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 25)
May 16 10:40:37.571: %SIBYTE-DFC6-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 6)
May 16 13:34:42.817: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 13)
May 16 14:15:15.547: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 14)
Date: 2012-05-17 02:09:30 UTC
since the card was up, everything seem to be stable. so the problem seem to become hardware or software on the card #9.
We are keeping an eye on it, as no log could prove that it has less failure.
A chase in the darkness and without light.
Date: 2012-05-17 02:06:03 UTC
We reboot the card. As soon as everything is up
we will isolate the card 9 of the router b.
Date: 2012-05-17 02:05:14 UTC
We cut electrically the module 9 of vss-7a.
The traffic switches on the vss-7b
Date: 2012-05-17 02:04:22 UTC
In fact, making a long list of what is not.
we have an idea.
Date: 2012-05-17 02:02:36 UTC
And for now we don't find (it has been an hour since we've been searching why the system kept loosing packets).
Update(s):
Date: 2012-05-17 02:10:07 UTC
May 16 07:49:28 vss-7a-6k 59778: May 16 05:49:03.406: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 12)
May 16 10:50:39 vss-7a-6k 59839: May 16 08:50:14.344: %SIBYTE-DFC9-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 25)
May 16 12:41:02 vss-7a-6k 59893: May 16 10:40:37.571: %SIBYTE-DFC6-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 6)
May 16 15:35:07 vss-7a-6k 59977: May 16 13:34:42.817: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 13)
May 16 16:15:40 vss-7a-6k 59989: May 16 14:15:15.547: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 14)
May 16 19:09:32 vss-7a-6k 60050: May 16 17:09:07.213: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 15)
Date: 2012-05-17 02:10:00 UTC
we've seen this morning on the vss-7a
May 16 08:50:14.344: %SIBYTE-DFC9-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 25)
May 16 10:40:37.571: %SIBYTE-DFC6-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 6)
May 16 13:34:42.817: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 13)
May 16 14:15:15.547: %SIBYTE-DFC3-4-SB_EXCESS_COLL: Excessive collisions on mac 1 (count: 14)
Date: 2012-05-17 02:09:30 UTC
since the card was up, everything seem to be stable. so the problem seem to become hardware or software on the card #9.
We are keeping an eye on it, as no log could prove that it has less failure.
A chase in the darkness and without light.
Date: 2012-05-17 02:06:03 UTC
We reboot the card. As soon as everything is up
we will isolate the card 9 of the router b.
Date: 2012-05-17 02:05:14 UTC
We cut electrically the module 9 of vss-7a.
The traffic switches on the vss-7b
Date: 2012-05-17 02:04:22 UTC
In fact, making a long list of what is not.
we have an idea.
Date: 2012-05-17 02:02:36 UTC
And for now we don't find (it has been an hour since we've been searching why the system kept loosing packets).