05-14-2013 11:19 PM - edited 03-07-2019 01:21 PM
Hi
I have a standalone 6506E chassis which has following configuration,
router-sp#show boot
BOOT variable = bootflash:s72033-ipservicesk9-mz.151-1.SY.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
----------------------------------------------------------------------------------------
router#sh run | inc boot
boot-start-marker
boot system flash sup-bootflash:s72033-ipservicesk9-mz.151-1.SY.bin
-------------------------------------------------------------------
router#show boot
BOOT variable = sup-bootflash:s72033-ipservicesk9-mz.151-1.SY.bin,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby not ready to show bootvar
router>Sh ver
System image file is "sup-bootdisk:s72033-advipservicesk9-mz.151-1.SY.bin"
Can someone please explain why and how it has booted from advipservicesk9-mz.151-1.SY.bin
regards
egan
05-14-2013 11:53 PM
Hi Egan,
Please provide me the output of:
show ver
show bootvar
show module
dir all
Regards
Inayath
05-15-2013 07:23 AM
Hi Inayath
Please find the output of
1> sh ver
router#Sh ver
router uptime is 5 days, 7 hours, 51 minutes
Uptime for this control processor is 5 days, 7 hours, 50 minutes
System returned to ROM by power cycle at 15:18:22 Fri May 10 2013 (SP by power on )
System restarted at 16:24:27 EST Fri May 10 2013
System image file is "sup-bootdisk:s72033-advipservicesk9-mz.151-1.SY.bin"
Last reload reason: Unknown reason
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
cisco WS-C6506-E (R7000) processor (revision 1.1) with 458720K/65536K bytes of memory.
Processor board ID SAL1104FAQD
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
1 Virtual Ethernet interface
26 Gigabit Ethernet interfaces
8 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
====================================================================================
router#sh bootvar
BOOT variable = sup-bootflash:s72033-ipservicesk9-mz.151-1.SY.bin,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby not ready to show bootvar
======================================
#sh module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL1137ZZAG
3 8 CEF720 8 port 10GE with DFC WS-X6708-10GE SAL1204DVJL
5 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL1130VUE3
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0019.30cf.0128 to 0019.30cf.013f 2.6 12.2(14r)S5 15.1(1)SY Ok
3 001f.6ca3.9940 to 001f.6ca3.9947 1.3 12.2(18r)S1 15.1(1)SY Ok
5 001a.2f3c.0d00 to 001a.2f3c.0d03 5.4 8.4(2) 15.1(1)SY Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Centralized Forwarding Card WS-F6700-CFC SAL113810XK 4.0 Ok
3 Distributed Forwarding Card WS-F6700-DFC3C SAL1204E7B4 1.0 Ok
5 Policy Feature Card 3 WS-F6K-PFC3B SAL1130VSP9 2.3 Ok
5 MSFC3 Daughterboard WS-SUP720 SAL1130VSX7 3.0 Ok
Mod Online Diag Status
---- -------------------
1 Pass
3 Pass
5 Pass
============================================================================================
1#dir all-filesystems
Directory of flexwan-fpd:/
0 dr--
No space information available
Directory of system:/
2 -r-- 0
4 dr-x 0
1 -rw- 12695
3 dr-x 0
No space information available
Directory of tmpsys:/
102 drw- 0
6 drw- 0
5 drw- 0
47 -rw- 0
49 -rw- 0
67 -rw- 0
69 -rw- 0
71 -rw- 0
73 -rw- 0
75 -rw- 0
77 -rw- 0
51 -rw- 0
53 -rw- 0
55 -rw- 0
57 -rw- 0
59 -rw- 0
61 -rw- 0
63 -rw- 0
65 -rw- 0
4 drw- 0
8 drw- 0
46 -rw- 0
48 -rw- 0
66 -rw- 0
68 -rw- 0
70 -rw- 0
72 -rw- 0
74 -rw- 0
76 -rw- 0
50 -rw- 0
52 -rw- 0
54 -rw- 0
56 -rw- 0
58 -rw- 0
60 -rw- 0
62 -rw- 0
64 -rw- 0
7 drw- 0
1 dr-x 0
9 drw- 0
No space information available
Directory of bootflash:/
1 -rw- 282422 Jun 27 2008 17:29:49 +10:00 crashinfo_20080627-072949
3 -rw- 186010 Feb 21 2011 14:26:40 +11:00 running-config(infoblox)
65536000 bytes total (59168376 bytes free)
Directory of disk0:/
1 -rw- 80230948 Oct 11 2011 08:49:40 +11:00 s72033-entservicesk9_wan-mz.122-18.SXF17b.bin
2 -rw- 10084 Jun 27 2008 02:07:20 +10:00 default-config
3 -rw- 114196 Jun 27 2008 17:40:56 +10:00 newstartup
4 -rw- 30597 Oct 6 2008 13:56:10 +11:00 config
5 -rw- 124546 Nov 17 2009 03:11:58 +11:00 old.cfg
6 -rw- 79922180 May 3 2011 15:42:34 +10:00 s72033-ipservicesk9_wan-mz.122-18.SXF11.bin
7 -rw- 17376 Oct 11 2011 10:02:32 +11:00 vlan1.dat
8 -rw- 5874316 Oct 18 2011 15:27:26 +11:00 c6slb-apc.4-2-14.bin
255979520 bytes total (89636864 bytes free)
Directory of disk1:/
No files in directory
1022590976 bytes total (1022590976 bytes free)
Directory of sup-bootdisk:/
1 -rw- 33554432 Apr 16 2008 07:14:38 +10:00 sea_log.dat
2 -rw- 33554432 Mar 18 2013 14:46:20 +11:00 sea_console.dat
3 -rw- 105429516 Mar 18 2013 14:40:12 +11:00 s72033-advipservicesk9-mz.151-1.SY.bin
4 -rw- 240732 Jun 27 2008 17:29:58 +10:00 crashinfo_20080627-072958
5 -rw- 113453380 May 3 2011 16:16:58 +10:00 s72033-ipservicesk9_wan-mz.122-33.SXI6.bin
6 -rw- 100666828 May 9 2013 16:21:44 +10:00 s72033-ipservicesk9-mz.151-1.SY.bin
7 drw- 0 Mar 18 2013 14:45:28 +11:00 call-home
8 -rw- 291824 May 7 2013 12:44:26 +10:00 crashinfo_SP_20130507-024427-UTC
512024576 bytes total (124805120 bytes free)
Directory of sup-microcode:/
0 dr--
1 -r-- 39194618
2 -r-- 12702954
3 -r-- 15803170
4 -r-- 14843654
5 -r-- 333584
6 -r-- 303510
7 -r-- 325656
8 -r-- 376704
9 -r-- 375086
10 -r-- 753230
11 -r-- 489038
12 -r-- 902190
13 -r-- 814590
14 -r-- 1300926
15 -r-- 65318
16 -r-- 60490
88644718 bytes total (0 bytes free)
Directory of const_nvram:/
1 -rw- 0
129004 bytes total (129004 bytes free)
Directory of nvram:/
1918 -rw- 12761
1919 ---- 1950
1920 -rw- 12761
1 ---- 0
2 ---- 146
3 -rw- 0
4 -rw- 13
1964024 bytes total (1945165 bytes free)
Directory of cfc#1-bootflash:/
No files in directory
15990784 bytes total (15990784 bytes free)
Directory of dfc#3-bootflash:/
1 -rw- 269530 Jun 1 2011 15:56:12 +10:00 crashinfo_20110601-055612
15990784 bytes total (15721124 bytes free)
05-15-2013 12:23 AM
your boot configuration is proper and it should boot from the specified IOS. But in this case i feel the specified image is currepted, so that it fetched the next available IOS from flash. If you could post the boot sequence logs, it would be easy to find. May be you can try IOS upgrade again.
--Pls rate if this is useful--
05-15-2013 07:09 AM
Where can i find the boot sequence log?
05-15-2013 07:33 AM
Hi,
If you run the command verify sup-bootflash:s72033-ipservicesk9-mz.151-1.SY.bin this will tell you whether the image you're trying to boot is corrupt.
Regards
05-15-2013 09:35 PM
image doesnt seem to be corrupt
see output of verify command
Embedded Hash MD5 : D3EC50B1FA3E66B3EC50BEB0E3F8B3AA
Computed Hash MD5 : D3EC50B1FA3E66B3EC50BEB0E3F8B3AA
CCO Hash MD5 : 0A0F345732FF3B034D571C1505EC9941
Embedded hash verification successful
So if the image is not corrupt why is it booting advipservices image.
And more importantly what is casuing it to boot that, when all the boot parametes point to ipservices image ??
05-16-2013 12:07 AM
Very interesting.
It looks to me like a bug. I havent got time to do the bug scrub on this, will find sometime to do the same later.
Regards
Inayath
05-16-2013 07:34 AM
Hello Egan,
Would mind changing the boot statement to:
boot system flash sup-bootdisk:s72033-ipservicesk9-mz.151-1.SY.bin
Instead of sup-bootflash,
Please let me know how that worked?
Regards,
Sony
05-16-2013 11:47 PM
Please capture the console logs while the switch booting up and paste the logs...
KVS
05-19-2013 10:25 PM
Cannot do this atm, the box is in the production and currently UP
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide