How to find the actual boot image on cisco catalyst 6503 E

Published on by dellpe

Question:
I would like to verify what is the actual boot image running on my catalyst 6503 E SUP 2T.

My IOS is s2t54-adventerprisek9-mz.spa.151-2.sy.bin and my Rommon is ok with the version 12.2(50r)sys3.

I tried many command without any success. Here’s the commands that i have been tried:

- show bootvar
-show version
- show module
- show run
- show boot

I try to see the boot image that is use by my 6503 E and not only one that is configure under boot command.

I have configure my 6503 e like this: boot bootstrap bootdisk:/s2t54-boot-mz.SPA.151-2.SY.bin.

Answer:

Ah, well if the sup2T is like the 720s, the actual booting is done by the images on the SP and/or RP. They, in turn, boot the IOS (according to boot strings, if so configured and enabled).

For multiple IOS images, including a reduced IOS image, you would need to look at the boot strings. Then check, for any image not actively running, check whether there’s really an image where the boot string says it should be.

Again, not very familiar with the sup2T, but on a 720 you can specify just a device as part of the boot string, and the boot process will look for any valid image (I believe restricted to the root of the device) and boot it.

In other words, except for the running image, you need to analyze how the device is configured to boot using the boot strings (i.e. config-reg), whether boot strings have been defined, and whether there are valid images on your different flashes, and whether they all agree.

Even without explicit boot strings, a (720) can be configured to default boot using first valid IOS image found on its default boot device.

You asked about the “running image”, again show version tells you that, but for how that image was actually selected during the boot process depends on all the above. Again, what image might be selected to boot into, depends on all the above.

As some of the boot devices can be changed on the fly, an accurate analysis of what should boot isn’t a guarantee of what will be actually be booted at time of boot.

Personally, I like (on 720s):
boot system disk1:
boot system disk0:
boot system bootdisk:

Which allows me to change IOS by changing CFs in disk1 and disk0, and without touching config.

However, others prefer explicit device:IOSFileName.

Published on Cisco 6500

To be informed of the latest articles, subscribe:
Comment on this post
O
Nice website full of quite interesting and informative posts, so must keep on good working!
Reply
O
Good Idea
Reply
O
Thank's
Reply
C
Thank's to Share
Reply
O
Thank's to Share
Reply