[c-nsp] 6509 only boots to bootflash

[Brian]

That was indeed my problem.

SW008#remote command switch sh boot

BOOT variable = disk0:s72033-ipservicesk9_wan-mz.122-18.SXF7.bin,12;
CONFIG_FILE variable does not exist
BOOTLDR variable =
Configuration register is 0x2101

I "re"set the confreg to 0x2102 and saved the config and it now boots
correctly.

Thanks for all of the replies!!

Brian


On 3/5/07, David Prall <dcp at dcptech.com> wrote:
>
> Try "remote command switch sh boot" to confirm that the configuration
> register synchronized properly with the SP. I've run into this more then
> once. I'm not sure off the top of my head how to do this with the slave
> though.
>
> David
>
> --
> http://dcp.dcptech.com
>
>
> > -----Original Message-----
> > From: cisco-nsp-bounces at puck.nether.net
> > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Voll, Scott
> > Sent: Monday, March 05, 2007 7:22 PM
> > To: Brian; cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] 6509 only boots to bootflash
> >
> > Try Slavedisk0:
> >
> > -----Original Message-----
> > From: cisco-nsp-bounces at puck.nether.net
> > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Brian
> > Sent: Monday, March 05, 2007 2:51 PM
> > To: cisco-nsp at puck.nether.net
> > Subject: [c-nsp] 6509 only boots to bootflash
> >
> > 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
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
>
>