Hey there I followed your how-to but ran into one of those irritating snags. I had to resort to plan B and update the cbos via serial as something went off in the tftp transfer. Anyway you might want to add a cleaned up version of this to your How-to: When|if your cisco comes back up and you get a happy little => Prompt you need to do the following steps with a working serial connection (Minicom or god forbid Hyperterminal) 1) Erase what's there (I actually did the upgrade without erasing any of my previous settings. I assume this will come back and bite me in the rump in a few days) => es 0 => es 1 => es 2 => es 3 => es 4 => es 5 2) Upload the CBOS to the cisco => df 10008000 (It will begin the upload of the cbos. Send it via your terminal program with the xmodem protocol, takes about 10 minutes) After the transfer make node the bytes transferred. You'r looking for a Hex number. 3) Reprogram the flash => pb 10008000 fee00000 (Hex number from above) 4) reboot => rb You might have to reenter your connection settings or what not but things should go well. I'm not sure what my tftp problem was, I oddly enough used the same .bin image in tftp as I did with the serial connection. Hope that helps anyone else who might get stuck On Thursday 02 August 2001 16:16, you wrote: > Here you are.. I guess I should just make a webpage for this... there is > also new info on how to do this via serial link, but I didn't write that > part, so it's not in this message. > > On Thu, 2 Aug 2001 11:19:57 -0500 > > "Ben Lutgens" <blutgens at sistina.com> wrote: > > On Thu, Aug 02, 2001 at 11:02:42AM -0500, Bill Layer wrote: > > >Dude, if you follow my instructions - that upgrade takes you an > > >honest-to-god five minutes, including downloading the code. Anyway, > > when > > > >you move, will you not be taking the 675 with you? > > > > It appears I need to do that too. Bill what's the URL to the > > aforementioned "instructions" and do you know the pinouts for the cable. > > (Note: I have telnet disabled on my 675 - you could just as easily do the > 'serial console' steps over telnet, were you to have that enabled.) > > The easy & fast way to upgrade the CBOS (the latest version I found was > 2.4.1, so I used it) is via tftp. The drill goes like this: (IMPORTANT > NOTE: I assume that the 675 is ip 10.0.0.1, and the client used to send > the upgrade is 10.0.0.2. Adjust as required for your network.) > > Log into CBOS over the serial cable, enter enable mode. > > #set tftp enabled > #set tftp remote 10.0.0.2 (this may be optional, but I set it the address > of my desktop. This forces the 675 tftp to only accept tftp connects from > a single host (security)). > > Now, from the client machine 10.0.0.2, and assuming you have downloaded > CBOS 2.4.1 as filename 'nsrouter.c675.2.4.1.bin': > > $mv nsrouter.c675.2.4.1.bin nsrouter.c675.2.4.1.bin.hr > $tftp 10.0.0.1 69 > tftp>mode binary > tftp>put nsrouter.c675.2.4.1.bin.hr > tftp>quit > > Back to the CBOS serial console on more time: > > #set tftp disabled > #reboot > > The modem should reboot, check a bunch of checksums, *then* it flashes the > EEPROM, reboots again and wakes up with the new version. You shouldn't > have to touch any of your NVRAM settings, but if they are ugly, log into > the serial console, enter enable mode and do: > > #set nvram erase > #write > #reboot > > Then you may configure the unit as if factory-fresh; ppp passwords and > all... > > > -.bill.layer.- > > -.those who are talking don't know, and those who know aren't talking.- > > -.frogtown.- -.minnesota.- -.u.s.a.- > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list -- ----------------------------- |\/|ike at GetBent.net