Boot variable for VSS modular IOS

Unanswered Question
Dec 29th, 2009

Dear friends,

I have a VSS switch booting from modular IOS image as you will from the system image filename in sh ver:

sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-VM), Version 12.2(33)SXI2a, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Tue 01-Sep-09 17:52 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)

t3a.sidradc.core uptime is 8 weeks, 3 hours, 19 minutes
Uptime for this control processor is 8 weeks, 3 hours, 17 minutes
Time since t3a.sidradc.core switched to active is 8 weeks, 3 hours, 17 minutes
System returned to ROM by  power cycle at 14:12:58 DST Wed Oct 28 2009 (SP by power-on)
System restarted at 13:00:00 DST Tue Nov 3 2009
System image file is "sup-bootdisk:/sys/s72033/base/s72033-ipbasek9-vm"
Last reload reason: Reload Command

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.

t3a.sidradc.core#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-VM), Version 12.2(33)SXI2a, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Tue 01-Sep-09 17:52 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)

t3a.sidradc.core uptime is 8 weeks, 3 hours, 21 minutes
Uptime for this control processor is 8 weeks, 3 hours, 20 minutes
Time since t3a.sidradc.core switched to active is 8 weeks, 3 hours, 20 minutes
System returned to ROM by  power cycle at 14:12:58 DST Wed Oct 28 2009 (SP by power-on)
System restarted at 13:00:00 DST Tue Nov 3 2009
System image file is "sup-bootdisk:/sys/s72033/base/s72033-ipbasek9-vm"
Last reload reason: Reload Command

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
[email protected].

cisco WS-C6509-E (R7000) processor (revision 1.5) with 1040384K/8192K bytes of memory.
Processor board ID SMC1336002G
SR71000 CPU at 600Mhz, Implementation 1284, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
3 Virtual Ethernet interfaces
174 Gigabit Ethernet interfaces
20 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

System is currently running from installed software.
For further information use "show install running".

However, my boot system configuration is as follows:

boot-start-marker
boot system sup-bootdisk:/sys/s72033/base/s72033-ipbasek9-vm
boot system sup-bootdisk:/s72033-ipbasek9-vz.122-33.SXI2a.bin
boot system flash sup-bootdisk:s72033-ipbase-vz.122-33.SXI2a.bin
boot-end-marker

However, i am just wondering if i need this. I am thinking of removing the last two boot system commands viz,

no boot system sup-bootdisk:/s72033-ipbasek9-vz.122-33.SXI2a.bin
no boot system flash sup-bootdisk:s72033-ipbase-vz.122-33.SXI2a.bin

I hope this will be ok. Can anyone confirm this please?

Thanks a lot

Gautam

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Reza Sharifi Tue, 12/29/2009 - 07:05

Hi Gautam,

You can delete the once you do not need, but I would at least keep one just in case the first IOS crashes, then you can just change the boot variable and boot from the second one until you figure out what ver to upgrade to. This is specially important, because there are so many buggy SXI versions out there.

HTH

Reza

vvasisth Tue, 12/29/2009 - 08:14

if i am not wrong you are deleting the IOS image from which your switch has booted. Just remove the

remaining 2 not the one switch has booted from.

regards,

Varun

gautamzone Tue, 12/29/2009 - 11:58

Thanks a lot Reza.

Varun: My system image file is sup-bootdisk:/sys/s72033/base/s72033-ipbasek9-vm.

So i guess the .bin files in the boot variable can be safely removed?

Thanks a lot

Gautam

Actions

This Discussion