Help! Can't log in to G3si 2

[SBL110]

This is an interesting one ... have a dual-cabinet G3si with redundant processors running software rev 12. Today for some reason I was unable to log in via ASA, couldn't dial in via modem, BCMS couldn't connect and was unable to FTP using VAL Manager. I borrowed a SAT terminal and tried connecting to the "TERM" port, but couldn't get any kind of response that way.

The switch appears to be working properly. We have mostly 8410D phones about (80) and a few (6) IP phones. No complaints from users. The local Intuity which is connected via LAN also seems to be communicating with the switch, and I've verified that all LAN connections (CLAN, MEDPRO) are connecting to the Cisco 4507 -- can also ping the CLAN, other than that, it's not allowing me to log in. Last time I logged in was Wed 11/22/06 and everything seemed normal. Any suggestions other than crashing the system? Thanks.

Scott

 

[orypecos]

U could try and have Avaya connect remotely, but that probably won't work either except if it your trouble is that it doesn't recognize your password. Is your system on a UPS and did it go down? Many times if the system goes down partially due to bad power, it will corrupt the software in RAM memory, but the back up memory will be fine. So if U reboot it will come up fine. But if U are fearfull, it might be a good idea to have a maintenance person come out with a crash kit in case it doesn't come back up.

Da-vi'do Juan-is'imo
P.S. For the best response to a question, read FAQ222-2244. Also give the type & version of your voice mail & pbx & preview your post to make sure it is complete & understandable. Please answer all questions so that I may have the info to assist you. Leaving a post on how you fixed the problem will also be appreciated.

 

[kwing112000]

I have a system i think it is R11 2 cabinet si and this happens all the time. The only way back in is to reboot. It gets a admin console alarm and you can not connect anyway to it. Avaya looked at it a long time ago and could not figure it out.

 

[SBL110]

Thanks for your replies both orypecos and kwing112000. I think my best bet right now is to turn off the active cabinet and hope that it fails over. This might free up a port to allow me to log in. I can then bring the downed cabinet back up and do a system reset 4 to clear everything.

If anyone is interested in the results, I will post what happened.

Scott

 

[orypecos]

. Leaving a post on how you fixed the problem will also be appreciated.

 

[SBL110]

Ok, the problem is resolved. This may not have been the proper sequence, but fortunately it worked:

1. Crashed the active carrier by tripping the circuit breaker on the back. This forced the system to fail over to the "B" carrier. At this time I was able to get a login prompt from the SAT terminal that I set up last week.

2. Powered carrier "A" back up and let it settle. As you might guess, several phones went down with carrier "A." I was able to bring them back by doing a busy/release on the station. The BCMS system was also able to log in, however, I was unable to dial the Audix server. I would get a ring but no answer.

Showing a major alarm on carrier "A" on the CPU card. Did a DISP ALA but the screen didn't show anything.

3. I issued a SYSTEM RESET 4 and crossed my fingers. After the system settled down, I was able to access all phones, Audix and BCMS. Nice way to start Monday huh?

A happy ending, but the burning question is why did it happen in the first place? Before the controlled crash and subsequent system reset, I wasn't able to connect through GEDI, a local SAT terminal or dial up. Not sure that Avaya would have had better advise than orypecos. Just glad it worked out. Thank you again for your replies.

Scott

 

[mikeydidit]

Orypecos is and has been a very valued member here for a long time. This is not the first(or last time) he has spent his time helping someone like you.

Have a star on Mikey for helping someone in need orypecos.

"You don't stop playing because you get old. You get old because you stopped playing."

 

[SBL110]

There was an old post (thread 690-1148735) that referenced a patch for a problem that is almost identical to this one.
Anyone know about this? My BP says that he can't find this through his searches.

The problem is returning intermittently but fortunately I'm able to dial in and reset the SAT service via IP-SERVICES. Strange stuff here.

Scott

 

[mikeydidit]

http://support.avaya.com/elmodocs2/qppcn/1406Bu.pdf

This may be what you are looking for.

"You don't stop playing because you get old. You get old because you stopped playing."