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#11792 — FS#15990 — vss-10ab-6k

Attached to Project— Network
Incident
Roubaix
In progress
90%
Both routers are unaccessible. We are investigating.
Comment by OVH - Monday, 04 January 2016, 19:40PM

We have detected a procedure problem on IPv6, we have temporarily cut it, and everything is back to normal in IPv4.

We are still investigating the cause of the problem, and we will progressively activate IPv6.


Comment by OVH - Monday, 04 January 2016, 19:46PM

the CPU is at 100% on the two routers because of IPv6 process.
We have no choice but to cut the IPv6 routing on both routers.

Routers are UP. With IPv4 only.

We will put all the IPv6 configuration on the router A
then we will gradually look into potential problems.


Comment by OVH - Monday, 04 January 2016, 19:47PM

75% of IPs are UP again. We are lokking to restart the 25% of IPs
that remain DOWN.


Comment by OVH - Monday, 04 January 2016, 19:49PM

All IPs are up.

https://twitter.com/olesovhcom/status/684053754224705536


Comment by OVH - Monday, 04 January 2016, 19:53PM

We are reactivating the IPv6 except on one vlan
where we probably have a client who has
a big problem. We will look at it, as well as potential protection. In short, with this IPv6 we might take longer to know the origin of the problem.


Comment by OVH - Monday, 04 January 2016, 19:54PM

The IPv6 has been reactivated, except for one of the VLANs. The situation is stable, we are investigating on the last VLAN.


Comment by OVH - Monday, 04 January 2016, 19:56PM

The IPv6 has been reactivated on all of the VLANs. We will continue to investigare the problem with Cisco.