Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
Le routeur de France Telecom annoncé à Hansenet les IP d'OVH sur Decix !?
Ce qui fait que les visiteurs de Hansenet avaient un routage très bizarre.
> Tracing route to epic-zone.com [91.121.31.116]
> over a maximum of 30 hops:
>
> 1 100 ms 32 ms 33 ms lo1.br11.ber.de.hansenet.net
> [213.191.64.20]
> 2 43 ms 32 ms 35 ms ae1-102.cr01.ber.de.hansenet.net
> [62.109.108.125
> ]
> 3 49 ms 51 ms 51 ms so-1-0-0-0.cr01.fra.de.hansenet.net
> [213.191.66.
> 21]
> 4 51 ms 61 ms 52 ms gi4-0-0.pr02.decix.de.hansenet.net
> [62.109.109.1
> 78]
> 5 315 ms 310 ms 313 ms bzrb403.equant.net [80.81.192.148]
> 6 320 ms 317 ms 326 ms
> so-7-2-0-0.fftcr2.Frankfurt.opentransit.net [193
> .251.248.209]
> 7 332 ms 335 ms 331 ms
> so-1-2-0-0.fftcr4.Frankfurt.opentransit.net [193
> .251.242.198]
> 8 356 ms 349 ms 347 ms xe-4-2-0.edge3.frankfurt1.level3.net
> [4.68.127.1
> 97]
> 9 * 327 ms * ae-31-51.ebr1.Frankfurt1.Level3.net
> [4.68.118.30
> ]
> 10 * 359 ms 359 ms ae-1-100.ebr2.Frankfurt1.Level3.net
> [4.69.132.12
> 6]
> 11 326 ms 326 ms 323 ms ae-2.ebr1.Dusseldorf1.Level3.net
> [4.69.132.137]
>
> 12 319 ms 326 ms 324 ms ae-1-100.ebr2.Dusseldorf1.Level3.net
> [4.69.132.1
> 30]
> 13 339 ms 331 ms 337 ms ae-2.ebr1.Amsterdam1.Level3.net
> [4.69.133.89]
> 14 327 ms 335 ms 343 ms ae-1-55.edge3.Amsterdam1.Level3.net
> [4.68.120.14
> 6]
> 15 361 ms 366 ms 433 ms 30g.level3.ams-1-6k.routers.ovh.net
> [213.251.130
> .69]
> 16 338 ms 330 ms * 40g.rbx-2-6k.routers.ovh.net
> [91.121.131.9]
> 17 320 ms 324 ms 318 ms rbx-15-m1.routers.ovh.net
> [213.251.191.168]
> 18 339 ms 375 ms 337 ms epic-zone.com [91.121.31.116]
>
> Trace complete.
Nous avons contacté Hansenet. Suite à ça, le probleme a été resolu sans
aucune explication. Nous avons vu un routeur se coupait sur Decix:
fra-1-6k#sh ip bgp sum | i 80.81.192.148
80.81.192.148 4 10282 13538 6204 0 0 0 08:01:52 Active
et un message sur la mailing list DECIX:
From: peering@orange-ftgroup.com To: tech@lists.de-cix.net Cc: peering@orange-ftgroup.com Subject: Orange Business Services (AS10282) outage in DECIX
X-Ovh-Remote: 80.81.196.3 (lists.de-cix.net)
X-Ovh-Local: 213.186.33.73 (mx3.ovh.net)
X-Spam-Check: DONE|H 0.5/N
We are currently experiencing problems with our connection to DECIX . We
have therefore temporarily shut down our peering sessions until the
problem is resolved.
Sorry for inconvenience
Best regards.
GIBN peering team
:::::::::::::::::::::::::::::::::::::::
GIBN 24x7 contact for fault management is at:
:::::::::::::::::::::::::::::::::::::::
*********************************
This message and any attachments (the \"message\") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************
[-- Attachment #2: message-footer.txt --]
[-- Type: text/plain, Encoding: 8bit, Size: 0,2K --]
On pense que ce routeur là a été à l'origine du probleme. Une
mauvaise configuration du routeur ou le routeur en lui-même qui
fait n'importe quoi.
Le probleme est resolu.
Update(s):
Date: 2008-11-08 22:29:47 UTC Le probleme semble d'être resolu.
Date: 2008-11-08 22:16:59 UTC Le probleme continue sur certaines IP de Hansenet.
En gros, le routeur d'equant fout le bordel malgré le fait
qu'ils ont coupé les sessions BGP. Nous avons telephoné à
Opentransit (en Inde) pour leur signaler le probleme. Sans
resultat.