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_red
icon_blue
icon_red
icon_orange
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#15174 — th2-1-a9

Attached to Project— Network
Incident
Whole Network
CLOSED
100%
We have some instability on this router.

We are investigating

Date:  Friday, 17 November 2017, 06:01AM
Reason for closing:  Done
Comment by OVH - Thursday, 16 November 2017, 02:39AM

It seems that the router is not responding.

We decided to reboot it and open a ticket to our vendor


Comment by OVH - Thursday, 16 November 2017, 03:00AM

We are isolating the router and we are going to open a ticket to Cisco


Comment by OVH - Thursday, 16 November 2017, 05:00AM

After an investigation with the Cisco TAC, we've found that one linecard has an issue. We are going to proceed with an RMA


Comment by OVH - Thursday, 16 November 2017, 07:38AM

We have isolated the router because we still have strange behavior


Comment by OVH - Friday, 17 November 2017, 01:15AM

Action plan
------------
We planned a maintenance on Nov 17th around 1AM Paris time to do the following actions:
1) reseat the linecard 0/1/CPU0 and see if both the interface and HDD errors are gone
2) if the problem is still present, re-insert another card in the chassis (as the issue was not hardware related)


Comment by OVH - Friday, 17 November 2017, 01:16AM

The first step failed
We insert another linecard in the chassis


Comment by OVH - Friday, 17 November 2017, 02:37AM

It seems ok for the moment with this linecard. We reactivated all the ports on the router.
We put back the router in production except the VOiP, the xDSL (routed via Gsw-1-a9) and FranceIX.


Comment by OVH - Friday, 17 November 2017, 05:06AM

After a few hours, the router seems stable.
we will keep monitoring it