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#905 — FS#4938 — var-1-6k

Attached to Project— Network
Incident
Whole Network
CLOSED
100%
The router at Warsaw, var-1-6k, is isolated from the network

2x10G amsterdam/Warsaw
2x10G frankfurt/Warsaw
and
1x10G prague/Warsaw
are down.

We are searching for the origin of the problem.
Date:  Monday, 13 December 2010, 01:04AM
Reason for closing:  Beta version
Comment by OVH - Saturday, 11 December 2010, 22:37PM

Dec 11 22:01:59 20g.var-1-6k.routers.ovh.net 62357: Dec 11 22:01:37 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/4, changed state to down
Dec 11 22:01:59 20g.var-1-6k.routers.ovh.net 62358: Dec 11 22:01:37 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/1, changed state to down
Dec 11 22:01:59 20g.var-1-6k.routers.ovh.net 62359: Dec 11 22:01:37 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
Dec 11 22:01:59 20g.var-1-6k.routers.ovh.net 62360: Dec 11 22:01:37 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/4, changed state to down
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62361: Dec 11 22:01:37 GMT: %EC-SP-5-UNBUNDLE: Interface Te1/4 left the port-channel Po4
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62362: Dec 11 22:01:37 GMT: %EC-SP-5-UNBUNDLE: Interface Te3/1 left the port-channel Po4
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62363: Dec 11 22:01:37 GMT: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/4, changed state to down
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62364: Dec 11 22:01:37 GMT: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/1, changed state to down
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62365: Dec 11 22:01:37 GMT: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62366: Dec 11 22:01:37 GMT: %LINK-3-UPDOWN: Interface Port-channel4, changed state to down
Dec 11 22:02:00 20g.var-1-6k.routers.ovh.net 62367: Dec 11 22:01:37 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/1, changed state to down
Neighbor Down: Interface down or detached
Dec 11 22:02:02 20g.var-1-6k.routers.ovh.net 62370: Dec 11 22:01:39 GMT: %LINK-SP-3-UPDOWN: Interface TenGigabitEthernet1/4, changed state to down
Dec 11 22:02:02 20g.var-1-6k.routers.ovh.net 62371: Dec 11 22:01:39 GMT: %LINK-SP-3-UPDOWN: Interface Port-channel4, changed state to down
Dec 11 22:02:02 20g.var-1-6k.routers.ovh.net 62372: Dec 11 22:01:39 GMT: %LINK-SP-3-UPDOWN: Interface TenGigabitEthernet3/1, changed state to down


Apparently amsterdam/warsaw was down down before the rescue via frankfurt.


Comment by OVH - Sunday, 12 December 2010, 06:54AM

There are some taskworks planned for tonight on the link Amsterdam/Warsaw, but not on Frankfurt/Warsaw:
http://status.ovh.co.uk/?do=details&id=870
http://status.ovh.co.uk/?do=details&id=871


Comment by OVH - Sunday, 12 December 2010, 07:06AM

The worktasks that had been planned(had been advanced and started earlier than announced)impacted not only 2x10G Amsterdam<>Warsaw but all our links to Warsaw.
We can not precise actually the occurate reasons that led to the simultaneous cut of 5x10G ( although via 3 different fiber courses,and largely independant: Prague / Amsterdam / Frankfurt).

It is planned to set back things to normal conditions about 02:00 CET.


Comment by OVH - Sunday, 12 December 2010, 07:11AM

The cut on Frankfurt <> Warsaw and Prague <> Warsaw is due to an independant incident and does not have any link with the maintenance planned for Amsterdam <> Warsaw .


Comment by OVH - Sunday, 12 December 2010, 07:14AM

We will secure Amsterdam<>Warsaw with another course.
Tired of having cuts on this destination.