cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4288
Views
0
Helpful
1
Replies
Jan Beginner
Beginner

6500 VSS issu update bootloop

I am trying to update a 6500 vss with a couple of linecards (no service modules) from 12.2.33.SXI4a to 12.2.33.SXI5 with issu. I loaded the images to both chassis sup-bootdisks.

After issu loadversion, the slave reloads with the newer software, but enters a bootloop:

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 bootdisk:s72033-ipbasek9-mz.122-33.SXI5.bin"
Loading image, please wait ...


Initializing ATA monitor library...

Self extracting the image... [OK]
Self decompressing the image : ###########################################################################################################[..]

System detected Virtual Switch configuration...
Interface TenGigabitEthernet 1/6/4 is member of PortChannel 1
Interface TenGigabitEthernet 1/6/5 is member of PortChannel 1
Initializing as Virtual Switch STANDBY processor

*Dec 21 07:46:02.055: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
*Dec 21 07:45:19.987: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch
*Dec 21 07:45:26.011: %VSL_BRINGUP-6-MODULE_UP: VSL module in slot 6 switch 1 brought up
*Dec 21 07:46:00.475: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
*Dec 21 07:46:00.475: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  6/5 
*Dec 21 07:46:00.547: %VSLP-5-VSL_UP:  Ready for control traffic
*Dec 21 07:46:02.055: %OIR-SW1_SPSTBY-6-CONSOLE: Changing console ownership to route processor


System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2009 by cisco Systems, Inc.
Cat6k-Sup720/RP platform with 1048576 Kbytes of main memory

Download Start
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Download Completed! Booting the image.
Self decompressing the image : [..]### [OK]

Restricted Rights Legend

[..]


cisco WS-C6506-E (R7000) processor (revision 1.2) with 983008K/65536K bytes of memory.
Processor board ID SAL144601FY
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
1 Virtual Ethernet interface
150 Gigabit Ethernet interfaces
12 Ten Gigabit Ethernet interfaces
2045K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
% Hostname "XYZ " is not a legal LAT node name, Using "CISCO_000000"
WARNING: Interface GigabitEthernet1/3/46 placed in restricted config mode. All extraneous configs removed!
WARNING: Interface GigabitEthernet2/3/46 placed in restricted config mode. All extraneous configs removed!
*Dec 21 07:48:04.991: RP: Currently running ROMMON from S (Gold) region
*Dec 21 07:48:06.043: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan. The Bridge IDs of all active STP instances have been updated, which might change the spanning tree topology
*Dec 21 07:48:46.859: %SYS-6-CLOCKUPDATE: System clock has been updated from 07:48:46 UTC Tue Dec 21 2010 to 07:48:46 UTC Tue Dec 21 2010, configured from console by console.
*Dec 21 07:49:02.831: %SYS-5-RESTART: System restarted --
Cisc
XYZ-sdby>o IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-M), Version 12.2(33)SXI5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 16-Jul-10 19:51 by prod_rel_team¢j
*Dec 21 07:49:15.418: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
***
*** --- SHUTDOWN NOW ---
***

*Dec 21 07:49:14.301: %SATVS_IBC-SW1_SPSTBY-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:0x5/0x5, SSAP/DSAP:0x2/0x1, OP/SEQ:0x1E/0x21, SIG/INFO:0x1/0x501, eSA:0000.0600.0000)

*Dec 21 07:49:15.414: %SYS-SW1_SPSTBY-5-RELOAD: Reload requested by Delayed Reload. Reload Reason: Reason unspecified.
*Dec 21 07:49:15.418: %OIR-SW1_SPSTBY-6-CONSOLE: Changing console ownership to switch processor


On the acive Unit i see a
[..]

*Dec 21 07:47:31.663: %PFREDUN-SW2_SP-6-ACTIVE: Standby initializing for SSO mode
*Dec 21 07:47:45.019: %PFINIT-SW2_SP-5-CONFIG_SYNC: Sync'ing the startup configuration to the standby Router.
*Dec 21 07:48:16.136: SW2_SP: Switch 1 Physical Slot 6 - Module Type LINE_CARD inserted
*Dec 21 07:48:33.863: %VSLP-SW2_SP-5-VSL_UP: Ready for data traffic
*Dec 21 07:48:34.671: SW2_SP: Card inserted in Switch_number = 1 ,
physical slot 6, interfaces are now online
*Dec 21 07:47:58.991: %SPANTREE-SW1_SPSTBY-5-EXTENDED_SYSID: Extended SysId enabled for type vlan. The Bridge IDs of all active STP instances have been updated, which might change the spanning tree topology
*Dec 21 07:47:58.999: SW1_SPSTBY: SP: Currently running ROMMON from S (Gold) region
*Dec 21 07:48:14.147: %OIR-SW1_SPSTBY-6-INSPS: Power supply inserted in slot 1
*Dec 21 07:48:14.151: %OIR-SW1_SPSTBY-6-INSPS: Power supply inserted in slot 2
*Dec 21 07:48:14.151: %C6KPWR-SW1_SPSTBY-4-PSOK: power supply 2 turned on.
*Dec 21 07:48:11.623: %FABRIC-SW1_SPSTBY-5-CLEAR_BLOCK: Clear block option is off for the fabric in slot 6.
*Dec 21 07:48:11.623: %FABRIC-SW1_SPSTBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 6 became active.
*Dec 21 07:48:12.267: %DIAG-SW1_SPSTBY-6-RUN_MINIMUM: Switch 1 Module 6: Running Minimal Diagnostics...
*Dec 21 07:48:12.287: %CONST_DIAG-SW1_SPSTBY-6-DIAG_PORT_SKIPPED: Module 6 port 4 is skipped in TestLoopback due to: the port is used as a VSL link.
*Dec 21 07:48:12.287: %CONST_DIAG-SW1_SPSTBY-6-DIAG_PORT_SKIPPED: Module 6 port 5 is skipped in TestLoopback due to: the port is used as a VSL link.
*Dec 21 07:48:19.623: %CONST_DIAG-SW1_SPSTBY-6-DIAG_PORT_SKIPPED: Module 6 port 4 is skipped in TestChannel due to: the port is used as a VSL link.
Cisco IOS Software, s72033_sp Software (s72033_sp-IPBASEK9-M), Version 12.2(33)SXI5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 16-Jul-10 20:18 by prod_rel_team
*Dec 21 07:49:02.363: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:01:29 to ensure console debugging output.
*Dec 21 07:49:03.551: %SYS-SW1_SPSTBY-6-BOOTTIME: Time taken to reboot after reload = 281 seconds
*Dec 21 07:49:12.499: %RF-SW2_SP-5-RF_RELOAD: Peer reload. Reason: RF Progression failure
*Dec 21 07:49:12.753: %SYS-SW1_SPSTBY-5-RELOAD: Reload requested - From Active Switch (Reload peer unit).
*Dec 21 07:49:14.259: %VSLP-SW2_SP-3-VSLP_LMP_FAIL_REASON: Te2/6/4: Disabled by Peer Reload Request
*Dec 21 07:49:14.259: %VSL-SW2_SP-5-VSL_CNTRL_LINK: New VSL Control Link Te2/6/5
*Dec 21 07:49:14.275: %VSLP-SW2_SP-3-VSLP_LMP_FAIL_REASON: Te2/6/5: Disabled by Peer Reload Request
*Dec 21 07:49:14.275: %VSLP-SW2_SP-2-VSL_DOWN: Last VSL interface Te2/6/5 went down


So what is
" %RF-SW2_SP-5-RF_RELOAD: Peer reload. Reason: RF Progression failure"

I managed to get a issu update with a stripped down startup-config, where most ports a shutdown and/or routed ports, but with my full config i can't.

Any hints?

So far my only solution is to NOT use issu with 6500 VSS as i was only able to get this thing back running by rebooting both chassis. In this case i will more likely do a "normal" softwareupdate with planned downtimes.

What are your experineces?

Everyone's tags (3)
1 REPLY 1
Highlighted
Cisco Employee

Re: 6500 VSS issu update bootloop

If the ISSU failed with the full config then the first thing that you need to look for is whether a any crashinfo files were generated.  Run the command "dir all" and look for a crashino file on both bootflash, sup-bootdisk, standby-bootflash and standby-Sup-bootdisk.

I would suggest opening a TAC case as I did a little extra research and found another posting where this same behavior was seen when performing an ISSU upgrade from SXI4a to SXI5 on a Sup32, non-VSS and is still under investigation.

Also, verify that the SXI4a and SXI5 images are both identical.  You post indicates that they are both IPBASE images.  Make sure they are both "K9" as your SXI5 image is a K9 image.

s72033-ipbase***k9***-mz.122-33.SXI5.bin

CreatePlease to create content
Content for Community-Ad