[c-nsp] 6509 only boots to bootflash
Brian
bms314 at gmail.com
Mon Mar 5 17:50:33 EST 2007
I am stuck trying to figure out why my standby sup720 ignores the boot
system commands and only tries to boot from bootflash.
Here are my boot variables:
SW008#sh bootvar
BOOT variable = disk0:s72033-ipservicesk9_wan-mz.122-18.SXF7.bin,12;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby is up
Standby has 458720K/65536K bytes of memory.
Standby BOOT variable = disk0:s72033-ipservicesk9_wan-mz.122-18.SXF7.bin,12;
Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
And the contents of disk0:
SW008#sh disk0:
-#- --length-- -----date/time------ path
1 81764868 Feb 26 2007 16:19:08 s72033-ipservicesk9_wan-
mz.122-18.SXF7.bin
429932544 bytes available (81772544 bytes used)
When I reload the peer sup engine, I see the following:
SW008#redundancy reload peer
Reload peer [confirm]
Preparing to reload peer
SW008#
Mar 5 10:10:19 Central: %OIR-SP-3-PWRCYCLE: Card in module 6, is being
power-cycled (RF request)
Mar 5 10:10:20 Central: %SNMP-5-MODULETRAP: Module 6 [Down] Trap
SW008#
Mar 5 10:10:19 Central: %PFREDUN-SP-6-ACTIVE: Standby processor removed or
reloadeäCat6k-Sup720/SP processor with 524288 Kbytes of main memory
Autoboot executing command: "boot bootflash:"
boot: cannot determine first file name on device "bootflash:"
System Bootstrap, Version 8.4(2) Release
Copyright (c) 1994-2005 by cisco Systems, Inc.
rommon 1 >
>From rommon, I can change the confreg to '2' so it boots off the system
image, then it boots fine. But the next reload has the same results where
it boots from bootflash. I can also issue a 'boot
disk0:s72033-ipservicesk9_wan-mz.122-18.SXF7.bin' and it loads fine, so I
know my image is good.
I must be missing something simple...can anyone see my mistake?
TIA,
Brian
More information about the cisco-nsp
mailing list