It was strange. It was a multi context installation. When trying to session into the fwsm from sup720 we got a password-prompt but our normal password didnt let us in. When connecting with console we got in with a default password (was it "cisco"? dont remember). I dont remember if the system context config was empty or screwed up, but after getting in from console I did write erase, reloaded the fwsm and successfully sessioned into the fwsm from sup720 without password (or was it "cisco"? Dont remember). Restored the system context from backup (Puuh!) and all virtual contexts got up automatically since the .cfg-files for them was solid. Did another upgrade and this time it worked.
What happened during upgrade was that I did copy tftp: flash:image, and it started showing !!!!!!!!:s. After that (and the tftp-server said that the entire file was transfered) I didnt get the text that the file was successfully transfered. After the exclamation marks: nothing. When talking to tac they said that "it can take a while. We dont know why, but you should wait for 30 minutes". My conclusion: We upgraded 2 fwsm. Both of them got stuck in the upgrade-process. We probably waited long enough before rebooting the first because it went up running the new version after removing/reinserting the fwsm-blade. The second we probably rebooted to early. After talking to tac we did attempt on second fwsm. We went for a burger and got back 40 min later. It was still "stuck", we rebooted it and it went up running 4.x. So, my advice is: When you upgrade FWSM and the tftp upload got stuck so you dont get the prompt back, wait AT LEAST 30 minutes before reseting the blade. What happend? Why couln´t I get in? No idea. It didnt respond to traffic, our password didnt work but we could get into it from console (it was running the old 3.x-version). Br Jimmy 2010/4/14 Bartlett Graham A <[email protected]> > Jimmy > > Did you have to do anything funky to with regards to connecting directly to > the FWSM, or did it just boot normally?? > > Thanks for the great info > > ------------------------------ > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jimmy Larsson > *Sent:* 14 April 2010 06:42 > *To:* OSL Security > *Subject:* Re: [OSL | CCIE_Security] Why is the cisco console cable flat? > > The correct answer is: If you try to upgrade a FWSM in a 6500-chassi and > the upgrade fails so you cannot access it you are toast because there is no > console port on the panel. However, if you open a Prio 1 TAC-case (which I > did), a friendly tac-engineer can tell you to connect to the > on-motherboard-mounted console-port and then reinsert the FWSM into the > chassi. There is about 3mm of space between the slots, which is enough to > have the console cable connected while powering up FWSM. ;) > > Now I know, but I wasnt home until 3am. ;) > > /J > > > 2010/4/13 Jimmy Larsson <[email protected]> > >> The other night I found out a reason for the standard light-blue >> console-cable to be flat. I solved a problem which hadnt been possible if >> the cable was thicker. >> >> Anyone take a guess? >> >> -- >> ------- >> Jimmy Larsson >> Ryavagen 173 >> s-26030 Vallakra >> Sweden >> http://blogg.kvistofta.nu >> ------- >> > > > > -- > ------- > Jimmy Larsson > Ryavagen 173 > s-26030 Vallakra > Sweden > http://blogg.kvistofta.nu > ------- > "This e-mail is intended for the recipient only. If you are not the > intended recipient you must not use, disclose, distribute, copy, print, > or rely upon this e-mail. If an addressing or transmission error has > misdirected this e-mail, please notify the author by replying to this > e-mail." > > "Recipients should note that all e-mail traffic on MOD systems is > subject to monitoring and auditing." > -- ------- Jimmy Larsson Ryavagen 173 s-26030 Vallakra Sweden http://blogg.kvistofta.nu -------
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
