[c-nsp] 6509-e IOS update

Peter Kranz pkranz at unwiredltd.com
Fri Feb 19 13:23:17 EST 2010


FYI Based on the dates on your flash, are you thinking of moving to this
image:

1     60284964 Feb 19 2010 15:42:58
s3223-advipservicesk9_wan-mz.122-33.SXH6.bin

I would think you should be on this image instead:

S3223-advipservicesk9_wan-mz.122-33.SXI3.bin

I believe most have skipped the SXH train, but could be wrong..

Peter Kranz
Founder/CEO - Unwired Ltd
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 510-207-0000
pkranz at unwiredltd.com

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Leslie Meade
Sent: Friday, February 19, 2010 9:27 AM
To: Antonio Soares; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 6509-e IOS update

Many thanks..


-----Original Message-----
From: Antonio Soares [mailto:amsoares at netcabo.pt]
Sent: Friday, February 19, 2010 9:04 AM
To: Leslie Meade; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] 6509-e IOS update

The config-register defines how the boot process will occur. Usually we have
the default values of 0x2102 or 0x102 meaning that the router/switch will
take a look to the config and there usually we have a "boot system flash
device:filename" command. So in your case i would do something like:

no boot system flash device:old_ios
boot system flash device:new_ios
boot system flash device:old_ios

Then confirm that everything looks fine with the "show bootvar" command.

You don't need to touch the bootflash. You are running in native mode (not
the old hybrid catos+ios mode) so you don't need the
MSFC2 file for nothing.


Regards,
 
Antonio Soares, CCIE #18473 (R&S/SP)
amsoares at netcabo.pt

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Leslie Meade
Sent: sexta-feira, 19 de Fevereiro de 2010 16:10
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] 6509-e IOS update

I have a question about these devices, I am a voice man not a R&S man so my
kungfu is not strong in this..

I am wanting to update the IOS on this and I am not quite sure on something

Is the booting of this device controlled by the Sup-bootdisk ? I.e. if I
change the code in the configs to boot the new ios and reload it should work
?

The question is this what is bootflash: used for? Should I also update is as
well ?


DTCCAT-CORE01#sh bootflash:
-#- ED ----type---- --crc--- -seek-- nlen -length-
---------date/time--------- name
1   .. image        3CA5FC8A 1098158   38 16875736 May 5 2007 21:26:10
+00:00 c6msfc2a-ipbase_wan-mz.122-18.SXF8.bin

 
DTCCAT-CORE01#sh sup-bootdisk:
-#- --length-- -----date/time------ path
1     60284964 Feb 19 2010 15:42:58
s3223-advipservicesk9_wan-mz.122-33.SXH6.bin
2     58262020 Aug 23 2008 18:58:58
s3223-advipservicesk9_wan-mz.122-33.SXH3.bin
3     26843548 Aug 23 2008 19:05:40 sea_log.dat



Cheers

Leslie

_______________________________________________
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/



More information about the cisco-nsp mailing list