Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
We currently have a network incident affecting traffic outgoing from SBG.
We are working with our partner to solve this issue asap.
Thank you for your patience.
Update(s):
Date: 2017-03-28 20:15:51 UTC Update of sbg-d2-a75 is now completed and it has been re-added as active element on our network.
Thank you for your patience and comprehension.
Date: 2017-03-28 19:27:29 UTC sbg-d1-a75 is now up to date and handle traffic correctly.
We are proceeding with sbg-d2-a75 isolation and update.
Date: 2017-03-28 18:45:11 UTC We have started the update on sbg-d1-a75.
Date: 2017-03-28 18:10:17 UTC The bug fix is present in a version released by Arista. We will upgrade our equipment to this version one by one.
Thank you for your comprehension.
Date: 2017-03-28 17:37:16 UTC We are still with Arista to find a solution to this issue.
Date: 2017-03-28 16:37:06 UTC We have the Arista engineer with us. We are looking for a non-disruptive way of fixing this issue.
Thank you for your patience.
Date: 2017-03-28 15:15:34 UTC We are still working with our partner Arista to apply the hotfix.
Date: 2017-03-28 14:45:15 UTC We have identified the issue.
When a sbg datacenter server wants to reach an OVH IP, the exit router of sbg (sbg-d1/d2-a75) shall know the route.
However a bug affecting this equipment prevent him to learn new routes.
So by default, it uses the route going to the equipment sbg-g2-nc5.
This router, sbg-g2-nc5, know only the external routes and send all internal traffic back to sbg-d1/d2-a75). This is where the loop appears.
We are working with our partner Arista to apply a hotfix.