Thanks David and Dale for the insights. SP Rommon was pretty far back, and upgrading it solved an issue I was having. However, after reading the caveats listed for the MSFC2A, I don't think I am going to mess with the RP - until I really need to.
Thanks again, -graham On 6/14/09 7:07 PM, "David Prall" <[email protected]> wrote: > The key issue with the boot image is being able to access the flash device > where the real image exists. A number of devices, ie Majority, no longer > need this but in the past upgrading to an ATA Flash card / disk0:, from > linear flash / slot0: meant that you needed a boot image that could support > the flash. The 7500 is an absolute for having the two in sync. > > 6500 MSFC3 ROMMON > http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/rommon/OL_4497.htm > l > > David > > -- > http://dcp.dcptech.com > > >> -----Original Message----- >> From: [email protected] [mailto:cisco-nsp- >> [email protected]] On Behalf Of Dale Shaw >> Sent: Sunday, June 14, 2009 7:54 PM >> To: Graham Wooden >> Cc: [email protected] >> Subject: Re: [c-nsp] 6500/SUP32 - RP ROMMON upgrade? >> >> Hi, >> >> <semi-hijack> >> >> On Mon, Jun 15, 2009 at 8:52 AM, Graham Wooden<[email protected]> >> wrote: >>> >>> I just updated the SP¹s ROMMON on a Sup32 to the latest, >>> c6ksup32-rm2.srec.122-18r.SX9. However, can this same file be >> applied to >>> update the RP's ROMMON as well? While logged into CCO I have only >> came >>> across docs that referred to the SP upgrade. I guess no biggie if the >> SP and >>> RP have difference ROMMON versions, I was just curious. >> >> I'm curious about how many people out there manage ROMMON/bootflash >> images in the same way the 'main' image is managed. >> >> In one customer network, there are tens of 7200s running 12.4T code >> with 12.3-based boot code. The same network has 20+ 6500s >> (sup32/sup720) running various 12.2(18)SXF images and I doubt anyone's >> ever given a second thought to 'auxiliary' code like ROMMON or any >> other flashable components. >> >> So, is stuff like ROMMON a set-and-forget or >> never-even-thought-about-it thing for you, or do you actively track >> image availability and factor upgrades in to your broader platform >> management activities? Is it considered good practice, for example, to >> match 7200 series boot flash revs with the main image, or does this >> fall into the "if it ain't broke, .." category? >> >> cheers, >> Dale >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
