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#6323 — FS#10224 — rbx-s1-6k

Attached to Project— Network
Incident
Whole Network
CLOSED
100%
The router has rebooted.
Date:  Tuesday, 18 February 2014, 16:31PM
Reason for closing:  Done
Comment by OVH - Wednesday, 12 February 2014, 20:05PM

Last reload reason: bus error at PC 0x40E61ECC, address 0x202104D


Comment by OVH - Wednesday, 12 February 2014, 20:06PM

The router has just crashed again:

No warm reboot Storage
*** System received a Software forced crash ***
signal= 0x17, code= 0x24, context= 0x443a8944
PC = 0x417bf050, Cause = 0x5020, Status Reg = 0x34018002


Comment by OVH - Wednesday, 12 February 2014, 20:06PM

We are replacing the sup card of the router.


Comment by OVH - Wednesday, 12 February 2014, 20:07PM

We will prepare the chassis to replace the sup.


Comment by OVH - Wednesday, 12 February 2014, 20:40PM

The 2nd chassis has crashed as well.

Feb 12 20:03:48 CET: %HSRP-4-BADAUTH2: Bad authentication from 37.59.224.28
Feb 12 20:03:48 CET: %HSRP-5-STATECHANGE: Vlan2747 Grp 0 state Standby -> Active
Feb 12 20:03:49 CET: %HSRP-5-STATECHANGE: Vlan2747 Grp 1 state Standby -> Active
Queued messages:
Feb 12 20:03:56 CET: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.

Feb 12 20:03:56 CET: %HSRP-5-STATECHANGE: Vlan2747 Grp 0 state Active -> Disabled
*** System received a Bus Error exception ***
signal= 0xa, code= 0x10, context= 0x46ae0a84
PC = 0x42af803c, SP = 0x44d43cb0, RA = 0x416c15a0
Cause Reg = 0x00003c20, Status Reg = 0x34008002
rommon 1 >
Feb 12 20:04:10 CET: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.

Feb 12 20:04:10 CET: %OIR-SP-6-CONSOLE: Changing console ownership to switch processor



No warm reboot Storage
*** System received an unknown failure ***
signal= 0x0, code= 0x0, context= 0x443acd64
PC = 0x417bf050, Cause = 0x1020, Status Reg = 0x34008102

System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory

Autoboot executing command: "boot disk0:s72033-advipservicesk9-mz.122-33.SXI11.bin"
Loading image, please wait ...


Comment by OVH - Thursday, 13 February 2014, 09:29AM

The 2 chassis are back to normal. There's no further major impact, however, config syncing issues may affect some customers. We are checking the configs now.

According to our information, it was the commands passed by a robot that seem to have caused the crash. These robots were immediately disabled after the router router crashed. We are working with the manufacturer to determine the exact cause of these crashes.