OVHcloud Network Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#8418 — vss-3b-6k
Scheduled Maintenance Report for Network & Infrastructure
Completed
We will move the router vss-3b-6k to a new routing room.

We will take this migration to switch the router to the version SXI11.

We will also double the capacity between vss-3-6k and Vlan switch.

The migration is scheduled for Thursday, April 11 at 7:00am.

Update(s):

Date: 2013-04-11 11:49:11 UTC
We are going to configure networks of this router by using GLBP instead of HSRP to balance the load between vss-3 and vss-3b.

Date: 2013-04-11 11:48:16 UTC
We have migrated all vlan switches connected to vss-3b-6k.

Date: 2013-04-11 11:47:33 UTC
We have changed the supervisor. The router has correctly rebooted.

Date: 2013-04-11 06:46:24 UTC
%Software-forced reload

Early Notification of crash condition..

00:56:12 GMT Tue Apr 14 2009: Breakpoint exception, CPU signal 23, PC = 0x42B05
154



--------------------------------------------------------------------
Possible software fault. Upon reccurence, please collect
crashinfo, \"show tech\" and contact Cisco Technical Support.
--------------------------------------------------------------------


-Traceback= 42B05154 42B02C94 42761E60 42761E8C 425716EC 425F1948 425F19A4 40ABA
E54 40ABBD24 40ABBC44 40ABCA18 426DC510 426CDF74 426CE190 42AF7804
$0 : 00000000, AT : 44F00000, v0 : 444A0000, v1 : 00000000
a0 : 4815DDA4, a1 : 0000F100, a2 : 00000000, a3 : 00000000
t4 : 42AF7FE0, t5 : 5000DAB0, t6 : 00000000, t7 : 00007089
s0 : 00000000, s1 : 44D50000, s2 : 5044B708, s3 : 0000001F
s4 : 5044B708, s5 : 48548BD0, s6 : 00000000, s7 : 08FED9C8
t8 : 08028FEC, t9 : 00000000, k0 : 00000000, k1 : 00000000
gp : 44EFCE48, sp : 5000DBB0, s8 : 00000000, ra : 42B02C94
MDLO : 00000000, MDHI : 00000000, BadVaddr : 00000000
Cause 00000824 (Code 0x9): Breakpoint exception
Writing crashinfo to bootflash:crashinfo_20090414-005612-GMT
=== Flushing messages (00:56:12 GMT Tue Apr 14 2009) ===
Buffered messages: (last 4096 bytes only)
Apr 14 00:55:33 GMT: %LINK-3-UPDOWN: Interface Vlan553, changed state to down
Apr 14 00:55:33 GMT: %LINK-3-UPDOWN: Interface Vlan556, changed state to down
Apr 14 00:55:37 GMT: %SYS-5-RESTART: System restarted --
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 12
Technical Support: http://www.cisco.com/techsupport
Compiled Fri 15-Feb-13 17:18 by prod_rel_team
Change Detected. Current system replication mode is Ingress
Apr 14 00:55:37 GMT: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 213.186.33.13
port 514 started - CLI initiated
Apr 14 00:55:37 GMT: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 213.186.33.41
port 514 started - CLI initiated
port 514 started - CLI initiated
Apr 14 00:55:37 GMT: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 188.165.9.217
Apr 14 00:55:40 GMT: %SNMP-5-COLDSTART: SNMP agent on host vss-3b-6k is undergoi
ng a cold start
Apr 14 00:55:42 GMT: %FM_EARL7-4-MLS_IPV6_FORCED_COMPRESS_MODE: Use IPv6 mask va
lues of 88 or lower in forced compress mode for consistent processing of incompr
*Apr 11 05:04:48.751: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 t
*Apr 13 23:53:01.339: SP: SP: Currently running ROMMON from S (Gold) region
olean (address 0). -Process= \"\", ipl= 1, pid= 3
87C
type vlan. The Bridge IDs of all active STP instances have been updated, which m
*Apr 13 23:55:36.107: %OIR-SP-6-INSPS: Power supply inserted in slot 1
*Apr 13 23:55:36.203: %OIR-SP-6-INSPS: Power supply inserted in slot 2
*Apr 13 23:55:36.203: %C6KPWR-SP-4-PSREDUNDANTBOTHSUPPLY: in power-redundancy mo
*Apr 13 23:55:36.307: %SYS-SP-5-RESTART: System restarted --
.2(33)SXI11, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Compiled Fri 15-Feb-13 17:36 by prod_rel_team
*Apr 13 23:55:42 UTC: %FABRIC-SP-5-CLEAR_BLOCK: Clear block option is off for th
*Apr 13 23:55:42 UTC: %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Modul
Apr 14 00:55:44 GMT: %DIAG-SP-6-RUN_MINIMUM: Module 5: Running Minimal Diagnosti
cs...
Apr 14 00:56:11 GMT: %DIAG-SP-3-MAJOR: Module 5: Online Diagnostics detected a M
ajor Error. Please use 'show diagnostic result ' to see test results.
Apr 14 00:56:11 GMT: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestFibDevices
failed
Apr 14 00:56:11 GMT: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestIPv4FibSho
rtcut failed
Apr 14 00:56:11 GMT: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestL3Capture2
failed
Apr 14 00:56:11 GMT: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestIPv6FibSho
rtcut failed
Apr 14 00:56:11 GMT: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestMPLSFibSho
rtcut failed
Apr 14 00:56:11 GMT: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestNATFibShor
tcut failed
Queued messages:
Apr 14 00:56:12 GMT: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console de
bugging output.

00:04:47: %HA_EM-6-LOG: Mandatory.go_bootup.tcl: GOLD EEM TCL policy for boot u
p diagnostic
Apr 14 00:56:12 GMT: %CPU_MONITOR-3-PEER_EXCEPTION: CPU_MONITOR peer has failed
due to exception , reset by [5/0]
*** System received a Software forced crash ***
signal= 0x17, code= 0x24, context= 0x46ae53e4
PC = 0x42af803c, SP = 0x44d48648, RA = 0x416c15a0
Cause Reg = 0x00003820, Status Reg = 0x34008002
rommon 1 >

Date: 2013-04-11 06:45:35 UTC
We started.
Posted Apr 11, 2013 - 02:13 UTC