Notes: From what I have read in the newsgroups, there are two vintages of the 675. The older one with the power transformer at the wall end may have the older chipset that can't be upgraded past CBOS 2.0.1. If you attempt to upgrade this unit, the upgrade may fail. My advice would be to have a copy of the 2.0.1 image handy just in case.

Word is that there might be a compatibility issue with CBOS 2.2 and certain ISP's. It seems to work fine with qwest dsl but if you are using another ISP, it would be a good idea to have a copy of 2.1.0 around just in case.

If your upgrade fails, you can normally use the MONITOR mode procedure below to recover. Once again, it would be advisable to have a copy of the previous CBOS image handy.

The NAT entry syntax has changed again in CBOS 2.4.1. See NAT Routing for some examples.

Qwest Now supports the upgrade and supplies the 2.4.6 image for the 675 and 678.

Note: DO NOT TRY TO UPGRADE A 678 WITH THE IMAGE FILE FOR A 675! Reports are that this could be catastophic. Also, be sure you flash your 678 with the proper 678 file. There are seperate files for CAP and DMT provisioning.

Disclaimer: I assume no responsibility for your use of thse procedures. Be aware that if something goes wrong with your upgrade, you could end up with a very valuable paperweight.

You'll need a serial connection to the 675 and Hyperterminal or some other program that supports Xmodem. It is also possible to upgrade the 675 using TFTP.

You'll need the image file (e.g. nsrouter.c675.2.4.6.bin) which has been obtained for the 675 and 678:

Prepare the 675 to receive the code file.

    enable
    set download code enable

    -- Download complete --
         Transferred 0009e600 bytes
    rebooting... 
    Hello! 
    C67x self-update code: Release 2.0.1 
    NOTE: 

    Do not power off the Cisco 675 until update is finished!
    Decompressing router ... 
    Erasing FLASH ...
    Programming ... 
    Decompressing monitor ... 
    Programming ... 
    Finished.  Rebooting...
    Hello!

(can also be used to recover from a bad upgrade attempt)

Put the 675 into monitor mode.

    reboot

When the alarm light is comes on hit Ctrl/C

You should now see the => prompt.

    df 10008000

Start the Xmodem transfer. The unit will display Downloading....When it is completed you'll get a message indicating the number of bytes written (e.g. 00fe8001). Make a note of this number.

Issue the following erase sector commands to the 675

    es 0
    es 1
    es 2
    es 3
    es 4

Take the program from the download area to the flash area where <size> is the size reported as written by the df command

    pb 10008000 fee00000 <size>

    m0
    rb

    enable
    set tftp enable

Using a TFTP client, upload the image file via put command. The destination file should be nsrouter.hr

    Initiate the transfer

If you are on an NT or UNIX machine, from a shell window type

  tftp -i 10.0.0.1 put nsrouter.c675.2.4.6.bin nsrouter.hr

    Note: The file name must be dot "." delimited, 
          not dash "-" or underbar "_" delimited.

If you are on an Win9x machine, you will need to initiate a binary transfer using a TFTP client. Win9x doesn't come with one. I've used PumpKIN TFTP and it seems to work fine. Also tftp.exe that comes with NT works on Win9x. Mac users can try the shareware tftp client from MacTechnologies.

Once the transfer is complete, use telnet or Hyperterminal to check for errors on the 675

  show errors
 
    You should see something like
    
      Image downloaded successfully
    
    If errors exist, attempt to upload the file again

Do NOT use the write command to save changes at this point! Reboot the 675 to come up on the new CBOS.