minorron

We have a Definity G3s running version R011i.03.0t26.5
I am using ASA version: R1.13.5U2.2
I have been connecting from another location via ethernet to the G3s. After a few weeks I started getting the error message: Communications Error: No Ports Available
I was told that I need to do a logout when exiting the ASA software from Avaya tech support. Before this error I have been right clicking the connection status and selecting disconnect. I thought this was doing the logout.
Two questions:
Is this information correct? (when I checked the history it was showing that for each login there was a logout when I was doing the right click step.)
Is there a way to reset or free up the ports other than powering down the G3s?

Thanks

liquidvw

I get that error when I try to log in more than 5 via ASA. Do a stat log. That will show you who is logged in. Then have them log out. There is a command to force them out, but I forgot it, maybe someone else knows that command.

PBXtech.info

 

Blah

you can simply close the connection. Unless you have 5 or more people logged in simultaneously, this error shouldn't be happening. Also, on CM 2+, this issue of 5 or more goes away entirely. powering down the G3.. is like replacing your car's engine instead of changing the oil....

if you must, busy the CLAN card over which your ip-sat access occurs. Then release the CLAN board. This might sound bad, but to check what CLAN board you're using "displ ip-ser" and from there you can see which CLAN is being used.. also, make sure your CLAN is not also being used for other services before you busy out the entire board! and not to insult, don't busy out the CLAN unless you're in the system via modem , or at the actual SAT terminal. Otherwise, you'll kick yourself out of the system and have to dial in via modem..

but the CLAN should not be locking up.. closing the GEDI window= logoff. As does "disconnect"

Blah

I guess the short answer is "busy board _____"

then

"Release board ______"

and yes, status logins will show you who's logged in. Sometimes, people stayed logged in too long..

there's no way to force people off, nor limit their idle time /lock them out.

sdoherty

We recently upgraded a G3R 9.2 that use to have te same problem ... use the "status login" comamdn to get the "login id" numbers, then issue the "reset login-id X" command (replacing the X with the login-id. This will clear the logins.

minorron

Thanks for the help guys. I’m sorry to say I’ve dropped the engine twice already.
Next time I’ll do a status login and see who/what is tying up the logins.

PBXtech.info

 

Blah

when I tried a "reset login" with CM1>, it did nothing.. I had to busy the CLAN card. Maybe I have a problem.

liquidvw

Thats the command I was looking for reset login-id X. I have that in my CM2.X switches. That command works great to "kick" people out.

Blah

I just tested.. it does NOT work for 2.1.1... but does in a 2.1.0. at least for me. So much for the engine replacement vs changing the oil..