10-22-2009 08:25 AM - edited 03-06-2019 08:15 AM
Hi, I have a 6509E platform with redundant supervisor cards. I noticed one was in ROMMON (not sure how it got there) and when I boot it back up it had an older IOS. I copied the new IOS that's on the active card. Do I just need to reload the (cold) module or do I need to reload both sup cards to get the equipment in a active/hot combo? Much thanks appreciated for any response. I could not find a link on Cisco right off hand describing the process.
10-22-2009 12:28 PM
Hello Robert,
if you have the same IOS image running on the two supervisors you are fine.
you should follow this link
you have to add few lines to master supervisor.
if your IOS allows it you should use SSO redundancy that is the best method.
Hope to help
Giuseppe
10-30-2009 09:39 AM
hy,
i have a problem with my SUP720 card, don't boot on the right IOS, there is an Autoboot executing command: "boot bootdisk:s72033-ipservice.122-18.SXF7.bin"
i want my card boot on this variable :s72033-ipservice.122-18.SXF13.bin
the too IOS are on the sup-bootdisk
but the probleme is when i power on my 6500, i have continously this error :
System Bootstrap, Version 8.4(2) Release
Copyright (c) 1994-2005 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 524288 Kbytes of main memory
Autoboot executing command: "boot bootdisk:s72033-ipservice.122-18.SXF7.bin"
Loading image, please wait ...
Initializing ATA monitor library...
Error : compressed image checksum is incorrect 0x0DDBFCBE
Expected a checksum of 0xCBFBA830
*** System received a Software forced crash ***
signal= 0x17, code= 0x5, context= 0x0
PC = 0x801000f4, Cause = 0x20, Status Reg = 0x30409003
is someone can help me ? i had never worked on a 6500
thanks
11-01-2009 05:51 AM
Hi.
First of all, you should open a new thread when you ask a new, unrelated question. That way it is easier for others to search for help later on.
Secondly, are you sure that your new (SXF17) image is complete? It sounds like you might have ahd some error during either download from cisco.com or when copying it to the bootdisk: device. Try repreating that process and see if it helps.
HTH, Ingolf
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