| reply to javed akbar
Sorry I just saw this message, I've been out for a few days sick.
I've had plenty of practice with this, as I've got a few
people that were helping me upgrade the IOS on a
bunch of switches, but they'd get all excited and forget
to verify that they actually put the new IOS on teh switch
before they powered off the switch.
(oh yeah, I even found a bizarre Lord Of the Rings version of an IOS file on 2 of my c3750's, but still
puzzles me, but have not had the time to play with it
to see what it does)
Needless to say, after waiting 3+ hours for the
IOS file to transfer over the console cable at 9600 baud,
I decided to make things much easier.
** TFTP transfers are not possible if the switch IOS image file is missing or corrupt **
You had the right procedure, but
here's how I do it;
(this is a 3750, but works on 3550, 3560, etc)
(also, you've covered steps, but just to reiterate this is from a document that I created for the NOC to support the 3750 switches)
I use hyper term, as I know it has the 1k xmodem
transfer, where my standard term program (crt),
does not.
*note* you might need to issue the 'load_helper' command.
1) Connect to console via Hyperterm
- 9600 baud
- 8 data bits
- no parity bits
- 1 stop bit
- no DTR/DSR flow control
- no RTS/CTS flow control
- no XON/XOFF
2) Initialize the flash subsystem with 'flash_init' command
switch:flash_init<enter>
3) View the contents of flash memroy to determin if IOS image is missing or if one is persent, if it's corrupt.
switch:dir flash:<enter>
4) Change console port speed from 9600 bps to 115200 bps.
(notice the case of the 'BAUD' variable, it is case sensitive)
switch:set BAUD 115200<enter>
*note* you will be disconnected from console session
5) Change/open new terminal session with new baud rate;
- 115200 baud
- 8 data bits
- no parity bits
- 1 stop bit
- no DTR/DSR flow control
- no RTS/CTS flow control
- no XON/XOFF
6) Issue the 'copy xmodem: flash:' command to start the transfer.
switch:copy xmodem: flash:c3560-ipservices-mz.122-46.SE.bin<enter>
you will see the following;
Begin the Xmodem or Xmodem-1K transfer now...
CCCCCCCCCC
quickly do step #7 before the transfer times out.
7) From the terminal package select;
'send file' with 'xmodem' or '1k-xmodem' protocol.
8) After the transfer is complete, verify the IOS image file is in the flash with the 'dir flash:' command.
9) If you're going to use the .bin file you just loaded as the main IOS and NOT use the .tar file, change
the boot parameters to reflect the new IOS image
with the 'set BOOT flash:' command.
*notice* the case of the 'BOOT' variable.
switch:set BOOT flash:c3560-ipservices-mz.122-46.SE.bin<enter>
10) change the console speed from 115200 bps back to the standard 9600 bps.
(notice the case of the 'BAUD' variable, it is case sensitive)
switch:set BAUD 9600<enter>
11) Change/open new terminal session with new baud rate;
- 9600 baud
- 8 data bits
- no parity bits
- 1 stop bit
- no DTR/DSR flow control
- no RTS/CTS flow control
- no XON/XOFF
12) Issue the 'boot' command to boot the switch off of the new IOS image using the
'boot flash:' command.
boot flash:c3560-ipservices-mz.122-46.SE.bin<enter>
Unless there's something drastically wrong with your switch,
you should be back in business. There have been times when I've had to
reformat the flash before adding the new IOS image file.
Usually once the switch is back up, I usually blow away
the IOS image .bin file, and proceed to upgrade the switch with the .tar file.
It's a long story, but it makes it easier for the NOC to handle software updates.
I've had to revive more switches than I'd care to have done this way, but after doing it enough times, I can say I've streamlined the process.
Hope this helps out. |
