cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1481
Views
0
Helpful
11
Replies

problems with IOS in redundant sup720 into cat 6509e

when new sup 720 installed initally went to rommon, then did a boot from the console, came up as standby cold,

the standby is running (s72033_rp-IPSERVICESK9-VM), Version 12.2(18)SXF7

but I cannot find where that code is

doing a DIR ALL does not show it anywhere

copied the running code to the slavebootflash:

changed the boot statements in the config to boot from the bootflash, did a copy running start and the config went acorss to the standby 720 ok, did a redundancy reload peer command, to reload the standby 720, but still came up running the (s72033_rp-IPSERVICESK9-VM), Version 12.2(18)SXF7 code instead of the SXD5 code.

where is the s72033_rp-IPSERVICESK9-VM), Version 12.2(18)SXF7 code??

see enclosed output of

show redundancy and dir all commands

11 Replies 11

Is the active supervisor running this image 12.2(18)SXF7. Can you post the output of 'dir all' from the active SE?

the dir all is in the attachment with the orig post

the active SE is running 122-18.SXD5

You seem to have done everything the correct way.

Can you try resetting the module 'reset 6' to reload the standby SE rather than using the 'redundancy reload peer' command?

HTH

Sundar

I just noticed this in your first posting "went acorss to the standby 720 ok, did a redundancy reload peer command, to reload the standby 720,".

To reload the standby (slot 6) you would have the issue command 'redundancy reload peer' from the active SE (slot 5). You can either do that or do 'reset 6' from the active SE.

HTH

Sundar

ok so there is no difference between

the "Redundancy reload peer" and the "hw-module module 6 reset" commands

I am still puzzled where it gets the 122(18)SXF code from, I tell the machine to load from bootflash with the boot cmmand but still loads this SXF code from?

Where did you issue the 'redundancy reload peer' command from? Your original post indicates you did that from the standby SE. If that's true then you would have reset the active SE and not standby SE. Can you try either issuing the command 'redundancy' command from the active SE in slot5 or 'reset 6'.

HTH

Sundar

All I was saying that the config went across to the standby, I am using the active SE, console is not active on the standby. so I am always reloading the new Sup720 in slot 6

Can you post the console output of standby SE when it was reloading?

see below for part of console output

it says bootflash: is an invalid device!

System Bo otstrap, Version 8.4(2) Release

Copyright (c) 19 94-20 05 by cisco Systems, Inc.

Cat6k-Sup720/SP processor with 524288 Kbytes of main memory

Autoboot executing command: "boot bootflash:s72033-psv-mz.122-18.SXD5.bin"

Loading image, please wait ...

Invalid device specified

Booting from default device

Initializing ATA monitor library...

string is bootdisk:s72033-ipservicesk9-vz.122-18.SXF7.bin

Initializing ATA monitor library...

Self extracting the image... [OK]

Self decompressing the image : #################################### [OK]

running startup....

bootflash: bf_io_devctl: DEVCTL error 19

Restricted Rights Legend

Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph

(c) of the Commercial Computer Software - Restricted

Rights clause at FAR sec. 52.227-19 and subparagraph

(c) (1) (ii) of the Rights in Technical Data and Computer

Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.

170 West Tasman Drive

San Jose, California 95134-1706

Cisco Internetwork Operating System Software

IOS (tm) s72033_sp Software (s72033_sp-IPSERVICESK9-VM), Version 12.2(18)SXF7, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2006 by cisco Systems, Inc.

Compiled Thu 23-Nov-06 09:24 by kellythw

Image text-base: 0x01020150, data-base: 0x01021000

Hi,

I think you might have a problem in your boot config. Because the directory of the ios you want to use is in the sup-bootflash:/ instead of bootflash:

Directory of sup-bootflash:/

1 -rw- 45465300 Jul 6 2005 13:36:17 +10:00 s72033-psv-mz.122-18.SXD5.

pointing the boot coomand to 'sup-bootflash' made no difference, still goe to the default.

I have ordered some compact flash, hopefully installing these and pointing to boot from disk0 will cure the problem,

I am still mysterfied why I cannot see the default ATA when I do a dir all command

Review Cisco Networking products for a $25 gift card