Porked 403. How to "clear CMOS?"

[jonnyGURU]

I've got a 403 here that crashed during an upgrade. Now it's just flashing lights and rebooting every 2 seconds.

I've pulled the battery for no less than TWO WEEKS and it still does this.

I've shorted out the pins that the battery plugs into and it still blinks and taunts me.

I can't see it via MAC address and I can't get to it via COM port.

There's nothing PHYSICALLY wrong with the module. There's GOT TO BE a way to clear the EEPROM on these things. Shorting a certain pair of pins, etc.

Anyone? PLEASE!!!! The unit's out of warranty! I BEG OF YOU!!!

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[IPGuru]

check FAQ940-4500
If you cannot get into the Monitor Loader using the com port then you are screwed.

an upgrade failure should not be terminal so good luck

 

[jonnyGURU]

I can't get into any kind of IP Configuration, TFTP, etc. because the system is rebooting every 2 seconds.

I don't think that's the right FAQ. I'm not configuring a point to point ISDN connection.

Thanks!


Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[NuggiFirst]

IPGuru meant faq940-5354 (he wrote it and should know better )

I'm quite sure that you can catch it this way! I have done the same mistake quite a few times, so...

 

[big70]

Did you have a fixed ip-adress and is it in the range of you config.
If the 403 is 10.0.5.100 dont use 192.168.42.2 but one in the same range.
You can look in a old config what is the ip-adress.

Good luck Peter

 

[jonnyGURU]

Thanks, but again... You can not hit the 403 via IP address or MAC address because it is in an endless cycle of rebooting. Even if I could ping it, I'd lose the ping after two seconds because the system reboots itself.


Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[jonnyGURU]

Unfortunately, the FAQ doesn't address this either. It's assuming I can actually talk to the control unit.

I was hoping someone knew of a pair of pins or traces I could jumper to default the EEPROM. I know Avaya has the hindsight of a retarted jackal at times, but I refuse to believe that they built this thing with no failsafe.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[NuggiFirst]

Read the FAQ again!

You should connect via serial to the DTE-port.
About 0,5 seconds after power-on, you break the boot-cycle by hitting Esc. Then the unit should be steady-red, and you can reset it with AT-commands.

I have screwed up in just the same way many times, and have allways been able to recover the unit with this procedure.

You can do absolutely nothing on the LAN-interface in this situation, the unit has no firmware in this state, and will not boot at all.

 

[jonnyGURU]

That didn't work.

Nothing in Hyperterminal. Can't break the reboot cycle with the ESC key.



Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[Leemondcomm]

Make sure IPOFFICE is powered down.
Ensure Computer running manager program is set to a static IP address.
- Connect DTE lead. And open hyperterminal connection.
- Power up and press ESC key on the pc until PremiSYS Loader etc etc comes up.
- Check connection is their by typing AT - Enter.
- The response OK should be returned.
- Type in AT-X and press enter.
Response Multi-Sector erase
ok will be returned.

Start or restart Manager application. (Can help here by building default in manager)
So remove LAN, Setup system ready to recieve file. Add a new Bootp entry as 192.168.42.1 - add MAC also - Add file name IP403.bin - Ensure working directory is set - Reconnect LAN - reboot.

A message similar to the following will appear.
Recieved BOOTP Response ;C0.A8 etc etc.

Once message INSTALLISATION COMPLETE STARTING TA is recieved IP Office is operational again.

Just on this note if upgrading SW make sure you are using the 1.99/2.99 step upgrades before moving to the appropriate level.

Taken from my notes hope this helps and makes sense

 

[jonnyGURU]

quote:

- Connect DTE lead. And open hyperterminal connection.
- Power up and press ESC key on the pc until PremiSYS Loader etc etc comes up.

Result:

Nada.


Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[Leemondcomm]

<<Fire suit on>>

Is this lead definatly a worker.

<<Fire suit off>>

 

[jonnyGURU]

For the record: This happened when I took the switch from 2.1(27) to 2.99 before a 3.0 upgrade.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[jonnyGURU]

Yeah. Same one I always use. But it doesn't hurt to try another.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[joehump]

Are you using the right 9 to 25 pin cable. Make sure its not a null modem cable. Set to 38400 8 none 1. Terminial type vt100. If all else fails Fed Ex delivers overnight.

 

[jonnyGURU]

Yeah. It's not a null modem cable. Like I said.. Same one I always use. In fact, it was in the back of the car because I was using it to get into the SMDR port of a Partner... which is why I don't have another one to try right now. I had a bad 355A adapter and swapped out the serial cable as a troubleshooting step when I couldn't talk to the Partner.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[big70]

i had the simular problem years ago with a Argent office.
I send it to avaya and got it back working.



Greets Peter

 

[IPGuru]

Appologies for the wrong FAQ.

Current Diagnosis, System fried, return to Avaya

 

[bason]

i got exactly the same on my upgrade to 2.1(31) after trying the 2.99 upgrade first.
At no point via hyper can i get to monitor loader and it cycles as you say every minute or so.
It has gone to the bin, no sorry to AVAYA.

 

[cobragb]

Why would you go to 2.99 before 2.1.(31)?

I'm confused??