Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
We had an incident on this network. We are looking for the origin of the problem.
Update(s):
Date: 2012-04-08 12:03:24 UTC Routing is back to normal but we continue to monitor.
Date: 2012-04-08 12:02:49 UTC We reboot the second switch.
Date: 2012-04-08 00:29:20 UTC 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.
Date: 2012-04-07 22:24:58 UTC 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.
Date: 2012-04-07 22:15:17 UTC We have rebooted one of the 2 switches managing the network 178.33.224 et 225. The connectivity is cut for these 2 networks.