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#245 — FS#4327 — Orange

Attached to Project— Network
Incident
Whole Network
CLOSED
100%
We notice difficulties of access from Orange. We are looking for the problem's cause.


Date:  Thursday, 01 July 2010, 13:20PM
Reason for closing:  Done
Comment by OVH - Wednesday, 30 June 2010, 17:32PM

OVH has 2 private peering of 2x10G with Orange. One on
Telehouse 1 and the other on Global Switch.

This morning we switched the configuration on
Global Switch to a port channel configuration
https://status.ovh.net/?do=details&id=245

Everything went well.

From 16:45, we notice a fell of 25% of the global ovh
traffic to Orange. 50% on the traffic
at Global Switch. There is no change from Telehouse 1
side.

We just cut the BGP session on Global Switch
everything is back.
It is reactivated. Still 50% of the traffic.
It is not a loss of packets. Is a
net interruption for some customers.
at Global Switch.

We conclude with a problem with Orange. We keep
the port down and contact them to see what is
going on.



Comment by OVH - Wednesday, 30 June 2010, 17:35PM

for the moment, the traffic passes through 2x10G
we have on Telehouse 1.


Comment by OVH - Wednesday, 30 June 2010, 17:43PM

An idea submitted to Orange: this morning we changed the
configuration from 2x 1x10G BGP with 2 BGP sessions to
2x10G connection with channels port, with a BGP session
May be at the time of the cleaning configuration works
the / 30, which allows us to make the BGP
was deleted at the same time as the / 30 which no longer serves.


Comment by OVH - Wednesday, 30 June 2010, 19:07PM

No idea about the origin of the problem.
We do not want to reactivate this link at 18h
to perform tests. We left thus the
traffic to pass only through Telehouse 1.

Tomorrow morning 7:00, we will reactivate the
port and check with Orange teams
Why the traffic doesn't pass correctly
on their network.

If you have been impacted to this problem, thank you
to post to oles@ovh.net , gui@ovh.net your IP with
Orange. This will allow us to make necessary
verifications, tomorrow on the good or bad
functioning to your connection.





Comment by OVH - Wednesday, 30 June 2010, 19:08PM

Thanks! and sorry ...


Comment by OVH - Wednesday, 30 June 2010, 23:10PM

Apparently the routing to 80.14.255.0/24 pose
problems from Orange side also. We have opened a
ticket at Orange. we wait.

In all cases tomorrow morning we will make tests
with teams, we've been in contact with them
today at the changeover.

Tough tough...



Comment by OVH - Thursday, 01 July 2010, 10:53AM

We reactivate the routing via the ports having problems in order to make a diagnosis.


Comment by OVH - Thursday, 01 July 2010, 10:58AM

You should have seen a cut off between 7h15 and 7h40 approximately.

The routing towards Orange must be back to normal
for the customers who were concerned.

If you still have problems towards OVH from
Orange, would you please point it out on noc@ovh.net. We
need to have your IP at Orange.


Comment by OVH - Thursday, 01 July 2010, 11:01AM

No feedback with the problems. We close the ticket.


Comment by OVH - Thursday, 01 July 2010, 11:25AM

It seems that the origin of the problem is from OVH.
We will make a test on /24 in order to find out
the problem.


Comment by OVH - Thursday, 01 July 2010, 11:49AM

During the maintenance
http://status.ovh.net/?do=details&id=187
We have migrated the ports from gsw-1 to gsw-2
and we forgot to re-announce the /30
on gsw-2

It continues to work because the routes
were announced in BGP.

After the migration of yesterday, it continues to work.
Only for certain networks which are
prefered in gsw-2. Therefore, the traffic
coming from rbx-1 goes on gsw-2
via th1-1 and were null routed by the announce
of 91.121.0.0/16 for all of the network.

th1-1-6k#sh ip route 91.121.131.50
Routing entry for 91.121.0.0/16
Known via "static", distance 200, metric 0 (connected)
Advertised by bgp 16276
Routing Descriptor Blocks:
* directly connected, via Null0
Route metric is 0, traffic share count is 1

gsw-2-6k#conf t
gsw-2-6k(config)#router ospf 16276
gsw-2-6k(config-router)#network 91.121.131.48 0.0.0.3 area 0

th1-1-6k#sh ip route 91.121.131.50
Routing entry for 91.121.131.48/30
Known via "ospf 16276", distance 110, metric 3, type intra area
Last update from 213.186.32.166 on Port-channel5, 00:00:01 ago
Routing Descriptor Blocks:
* 213.186.32.210, from 213.186.32.95, 00:00:01 ago, via Port-channel4
Route metric is 3, traffic share count is 1
213.186.32.166, from 213.186.32.95, 00:00:01 ago, via Port-channel5
Route metric is 3, traffic share count is 1



Sorry.


Comment by OVH - Thursday, 01 July 2010, 13:20PM

The error of beginners.