Comment by OVH - Wednesday, 16 September 2015, 18:49PM
We have detected a malfunction in the internal routing protocol of IPv6 in RBX. Some routers use their neighbors as gateway so no configuration justifies this behavior.
A loop L3 has appeared after tonight's the intervention because both routers are used reciprocally as gateway, we corrected that.
A loss could be observed if multiple routers used the same neighbor.
We must pursue the investigation of this dysfunction to find out why the internal routing protocol reacts this way.
Comment by OVH - Wednesday, 16 September 2015, 18:50PM
All routers must now use rbx-g2-a9 as exit door outwards IPV6.
We are looking to optimize this by putting rbx-g1-a9 and rbx-g2-a9 as output door.
Comment by OVH - Wednesday, 16 September 2015, 18:50PM
Traffic is now load balanced between rbx-g1-a9 and rbx-g2-a9.
We expect customer feedback to confirm the resolution of the incident.
RSS for all categories
We have detected a malfunction in the internal routing protocol of IPv6 in RBX. Some routers use their neighbors as gateway so no configuration justifies this behavior.
A loop L3 has appeared after tonight's the intervention because both routers are used reciprocally as gateway, we corrected that.
A loss could be observed if multiple routers used the same neighbor.
We must pursue the investigation of this dysfunction to find out why the internal routing protocol reacts this way.
All routers must now use rbx-g2-a9 as exit door outwards IPV6.
We are looking to optimize this by putting rbx-g1-a9 and rbx-g2-a9 as output door.
Traffic is now load balanced between rbx-g1-a9 and rbx-g2-a9.
We expect customer feedback to confirm the resolution of the incident.