rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#2600 — FS#6561 — Network 178.33.225

Attached to Project— Network
Incident
Whole Network
CLOSED
100%
We had an incident on this network. We are looking for the origin of the problem.
Date:  Saturday, 05 May 2012, 02:55AM
Reason for closing:  Done
Comment by OVH - Sunday, 08 April 2012, 00:15AM

We have rebooted one of the 2 switches managing the network 178.33.224 et 225. The connectivity is cut for these 2 networks.


Comment by OVH - Sunday, 08 April 2012, 00:24AM

The traffic is back to normal on these 2 networks. The reboot of one of these switches, shouldn't have cut the traffic for a reason that we're ignoring at the moment, the 2nd switch is set in protection (vPC port cut). This was not expected. We are going to analyse what has happened with cisco.

A first explanation:
We do suspect that the vPC between both switches are found in an unstable condition since the beginning and this what explains the problems on the network 178.33.225 (loss of ping by intermittence). While rebooting the 1st switch, the vPC crashed and has cut all ports on the 2nd.


Comment by OVH - Sunday, 08 April 2012, 02:29AM

We have noticed some loss of ping. A reset of the mac table has fixed the problem for now but we did not isolate the cause of the problem. We are continuing the research.


Comment by OVH - Sunday, 08 April 2012, 14:02PM

We reboot the second switch.


Comment by OVH - Sunday, 08 April 2012, 14:03PM

Routing is back to normal but we continue to monitor.