Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Maintenance Port Locked On Mitel SX2000 Light

Status
Not open for further replies.

IPS123

IS-IT--Management
May 3, 2004
13
How can I unlock the maintenance Port On the active Plane of a Mitel SX2000 Light?
 
What do you mean by "locked out"? Can you log in at all, or can you just not access CDE? If the latter, check and see if there's any print jobs pending ("sho print all"), and kill any print jobs, that will lock out CDE access. If all else fails, you may need to perform an activity switch or reboot.
 
I can not log in on the active plane. I can logi on the inactive plane but cannot make changes.
 
what, if any, alarms are active on the inactive plane?
 
There are no alarms on the active plane.
 
Wait, i thought you couldn't log into the active plane?

If the inactive plane is free of alarms and has a good database, force an activity switch (you'll have to do this from the panel). There's a chance that even though the currently inactive plane shows no alarms that the mate link may be closed and therefore you could lose service for 5-10 minutes. Once the inactive plane takes over, it will reset the other controller and then you can try logging in to see what's wrong. If still no joy, you'll probably need to replace the Main Controller on that plane.
 
do a control q on the port that doesnt respond and then a control c to refresh th screen
 
FWIW, I have seen this same phenomenon starting somewhere about LW33 where inexplicably the SX2K's active plane Maint and/or CDE interface will occasionally lock up without warning or apparent cause. Once locked it is LOCKED and totally unresponsive to any keycode combination directed to any of its various interfaces in an attempt to unlock it.

The only known cause of a lockup I'm aware of is when there are 2 or more terminals concurrently logged into the same control plane through different interfaces, i.e., one logged in via a terminal server attached to one of the serial interfaces and another logged directly via telnetting to the IP address of the main controller. In this lone instance closing either one of the sessions will serve to release the other.

However, if you experience a lockup and the above described scenario is not the cause then the only 2 ways I've found to free it up are;

1) force an activity transfer (usually harmless but not recommended in general practice)
or
2) wait until the overnight scheduled activity xfr happens by itself.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top