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!

How To Re-Boot a Redundant SX2000 Light system.

Status
Not open for further replies.

tundranugget

Technical User
Sep 4, 2003
98
US
We have been told to re-boot our SX2000 redundant system. We can blunder through it, but we are hoping someone can give us a correct Step-by-Step procedure that would avoid potential blundering mistakes.
 
Chapter 5 of the Technicians Handbook available from Mitel Online details the Power Down Procedure for the SX-2000R
 
Thanks. I was lucky enough to dig up a copy of the handbook. I am also registering to Mitel Online. Thanks again.
 
A "Redundant" SX2000 Light should be set to perform an Activity Switch nightly and if not then why not? Aside from a component failure there is no valid reason I can think of for not performing a nightly activity switch (or at minimum, weekly, but nightly still preferred).

An Activity Switch effectively "reboots" the system but is not (and should not be) service affecting. If switching activity between redundant controllers and I/O systems causes a resulting service impairment, then something is seriously wrong and in urgent need of attention.

The above notwithstanding, an activity switch is not the same as performing a data save/data restore and jumping the system across a partition. This latter method is how you recover from a database error, aka database corruption and IS SERVICE AFFECTING meaning an approximate 15 minute total system outage will occur. I could talk you through it, but your best approach would be to have a current copy of the tech handbook (one which matches your current level of software) and perform the steps outlined therein.
 
OK. A data save was done and the system was powered down according to Ch. 5 of the Tech's handbook. HOWEVER, this did not rectify the original problem and the reason why the 're-boot' was ordered. What started all this is that several users have their message lights flashing on their 4025 Supersets, even though there are no messages waiting (neither new or saved messages). All manner of things have been tried to stop the message lights flashing and nothing works. The re-boot was a last-ditch, desperate measure. My suspicion is that the root cause of the 'phantom' message flashing was the execution of some "MOVE / SWAP" commands while messages were waiting. Also, several of the affected numbers have had more than one "MOVE / SWAP" performed on them while the light was flashing. Although I was warned not to do this, unfortunately there are several people performing maintenance on the system with full access. The question is: How do we stop the lights from flashing?
 
Caught your reply on another post. 4025's and a nupoint.

with 4025's you should be able to enable the COS option to allow a user to clear the message thru the softkeys. You may need message waiting inquire enabled and also Multiline Set Voice Mail Callback Message Erasure Allowed.

with the handset in the cradle you can then press the message key, read the message and erase the message.

Failing that, you might want to try setting the SUPERSET Callback Message Cancel Timer in the system options assignment to a low value overnight like 2 hours. this "might' cancel all message indicators and then you can refresh with the nupoint. (it might not cancel any messages that were set before the change though, but it's worth a try)

to refresh with the nupoint, S ystem / O ther / L amp
Input range of stations, message waiting type 2 (existing) and type leave blank for All enabled types for the vm.

If the customer is causing these issues by moving sets that have message indicators, start billing them to fix it. That will get their attention.

Locate feature Extension xxxx will identify features that are active before a move, no excuses.
 
No excuse I agree, but you won't work with the moron I do. The problem is, he's one of us yet in spite of having this Mov/Swap issue being explained to him multiple times he finds it expedient (to him) to race through large moves (groups of 30~100) and go off blissfully into the sunset at quitting time, turning his cell phone off as he walks out the door. He understands, but he doesn't care.

A Move/Swap around our shop is a 3-step process; check the MWI lamp, if on, turn it off. Do the swap and reenable the MWI lamp. "Bozo" doesn't have time for this. I'll block out the whole afternoon for a 50-person move, do the swaps in software, physically move the instruments (cooties intact) and redress (as needed) the cables under the workstation. Bozo will do the whole move in 90 minutes. Instead of moving the customer's instrument he just swaps the desi's on the sets. When complaints come in the following day about MWI lamps Bozo's only comment is, "Oh well" and then laughs. I'd have fired him years ago, but he doesn't report to me. Mgmt likes him because he's fast, never mind that he's a bull in a china shop. Obviously speed counts more than accuracy.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top