Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: ttrumble111 on January 06, 2012, 01:53:46 PM

Title: Minor Alarm
Post by: ttrumble111 on January 06, 2012, 01:53:46 PM
I have been given the task to troubleshoot the following error message.

               |Total In|      Unavailable      | Alarm Threshold Percentages   
   Category    | System | Total |    %  | Alarm |  MINOR  |  MAJOR  | CRITICAL 
---------------+--------+-------+-------+-------+---------+---------+----------
Lines          |   185  |    16 |   8 % | Minor |   > 0 % |    20 % |   100 % |
---------------+--------+-------+-------+-------+---------+---------+----------


The equipment I have is a Mitel 3300 ICP MX. I have confirmed this with the shell command sysGetPlatformFamily.

We are using ESM Version 5.2.4.4

It does have a Hard Drive.

When I boot up everything loads successfully and then I get the alarm. We can call out, call internally, but no one, external, can call any DID numbers.

Any ideas?

- Tom
Title: Re: Minor Alarm
Post by: ralph on January 06, 2012, 02:04:26 PM
Enter the command 'Show fault all'

Am I assuming correctly if I say you have peripheral cabinet with DNI cards or ONS cards?

I suspect you have a 'phantom' card programmed but no card installed.

Ralph
Title: Re: Minor Alarm
Post by: ttrumble111 on January 09, 2012, 09:23:38 AM
Good morning Ralph,

Yes I have SX2000 Peripheral Cabinet with the following cards:

Four - DNI LINE (MC330AB)
Four - NA ONS CLASS LINE CARD (MC320FA)
One - PERIPHERAL SW CONT II ( MC312AB)
One - POWER CONVERTER (MP914 AA)

The following Modules are in the Mitel 3300:

One - Dual FIM
One - T1/E1

With the peripheral cabinet connecting to the 3300 by fiber.

All lights are green (either solid or flashing) on FIM Port 1, on the the Ethernet Port, T1/E1 Port 1, & the Adtran TSU 120.

Tom
Title: Re: Minor Alarm
Post by: ralph on January 09, 2012, 09:50:56 AM
Check your programming to see how many cards you have programmed and then compare to what cards are installed.

I'll bet dollars to doughnuts that you have 1 more ONS or DNIS card programmed than you actually have installed.

If that's correct the you can kill the alarm by using this command 'set thres lines 9 20 100'

Ralph
Title: Re: Minor Alarm
Post by: ttrumble111 on January 09, 2012, 12:14:44 PM
Just out of curiosity. Does the programming for the cards reside on the Hard Drive or on one of the cards within the 3300.

The reason I ask is: I replaced a 3300, identical to the one I am using now with a BCM450, so I thought that I would create a hotspare for the existing 3300.

I cloned the hard drive from the one that is in use, used the appShutdown shell command on the original, hit space 3 times pulled the power, and replaced the original with the clone.

I moved - from the original to the clone - the Fiber, T1, & 25 Pair TELCO Connector cable on back, powered up the clone, watched from the maintenance port, all seemed to load successfully and finally got the Minor Alarm I reported.

I could not resolve the problem so I shut down the clone, moved the cables back to the original, powered down the Peripheral Cabinet with the On/Off switch in the back, waited 30 seconds then powered the cabinet on, waited another 30 seconds and powered the original 3300 on with cables attached and did not receive the Minor Alarm.

Did powering down the cabinet fix the Minor Alarm or is there programming on the 3300 that needs to get modified? Also is there a proper sequence to power down and powering up the 3300 and Cabinet?

What are your thoughts?

Tom

Title: Re: Minor Alarm
Post by: ralph on January 09, 2012, 04:11:17 PM
Did I read that right?!!
You took a BCM 450 cabinet and put a 3300 drive in it along with all the modules that were in the 3300 and everything worked? (except for the minor alarm)

I must have misunderstood that.

Can you clarify?

Ralph
Title: Re: Minor Alarm
Post by: Mattmayn on January 10, 2012, 02:42:44 PM
Ralph, I think he is saying that a 3300 was forklifted and replaced with a BCM450 giving him spare parts. Not running MCD on the BCM.
Title: Re: Minor Alarm
Post by: ttrumble111 on January 11, 2012, 02:45:43 PM
Mattmayn is correct.

The agency did not want the Mitel 3300 System and phones anymore so they went with a complete overhaul. Now I have these spare parts for the the Agency that is still using the Mitel 3300.

- Tom
Title: Re: Minor Alarm
Post by: ralph on January 12, 2012, 06:11:35 AM
Wow.  Worse yet.  They replaced a 3300 with a BCM that will be EOL in 2 months.

Now I think I understand.  It's possible that one of your cards didn't load when the system booted.   I've had issues with DNI cards on occasion and just reseating the card resolved it.   A reboot of the system may have also resolved it.

Did your clone drive work?   We've done this before so I can't see why it wouldn't.

Ralph
Title: Re: Minor Alarm
Post by: ttrumble111 on January 18, 2012, 12:23:01 PM
I was connected to the maintenance port when I powered on the spare 3300 with the cloned HD and all of the informational messages showed "loaded successfully".

After everything loaded I logged in to the ESM and could navigate without any hiccups except for the "Minor Alarm".

Is there a proper sequence and amount of time to wait (once one device is powered up) to power on the other?

- Tom

Title: Re: Minor Alarm
Post by: ralph on January 18, 2012, 01:10:28 PM
20 to 30 minutes should be more than enough to be sure all the cards are loaded.

Can you do a "Sho Fault Alarm" command?   That should show you what's broke.
It would appear to me that 1 card is either not installed or not loaded.
It's not uncommon to have a card programmed but not installed.

You can turn off the alarm by entering "set th line 9 20 100"

Ralph
Title: Re: Minor Alarm
Post by: ttrumble111 on January 19, 2012, 01:31:09 PM
Thank you Ralph.

But I am still looking for the "Proper Sequence" for Shutdown & Startup. For Example:

ShutDown
1. Enter appShutdown from Shell and then <SPACE><SPACE><SPACE> to stop auto-boot AFTER countdown starts then power off the 3300
2. Power Down Peripheral Cabinet with the Rocker Switch on back

StartUp
1. Power Up "Peripheral Cabinet" with Rocker Switch on back
2. Wait 20 or 30 Minutes
3. Power on 3300
4. Wait 15 or 20 Minutes and log into ESM

What are your thoughts?

- Tom
Title: Re: Minor Alarm
Post by: ralph on January 19, 2012, 02:33:58 PM
You have the shut down correct, but it really doesn't matter when you power off the pers.

For the start up, there's no need to wait for the pers to come up.
You can turn them all on at the same time.

I usually put a ping -t agains the 3300 just to know when things start responding.
Watch the Shell and one of the last things to come on line is the voice mail.   
Once you see that then you should be able to log in.
It doesn't hurt to try and log in earlier.  It just won't let you until it's ready.

Ralph
Title: Re: Minor Alarm
Post by: ttrumble111 on February 03, 2012, 01:53:34 PM
Good afternoon Ralph,

I don't want to be a kiss a$$... but you are good. I finally got around to doing a better physical inventory of what is installed in the Peripheral cabinet and what is programed and your January 6 post was spot on:

"I suspect you have a 'phantom' card programmed but no card installed."

After running "SH FA Alarms" on the original system this is what it displayed:

Lines                                                                           
----------------------------------------------------------                     
|                |                              | Total  |                     
| Cab Shelf Slot |      Card Description        | Faults |                     
----------------------------------------------------------                     
|  6    1    12  | MC320Cx On Premises Line     |   16   |                     
----------------------------------------------------------                 
     

As I looked up at the Peripheral Cabinet I saw no card in slot 12. The light bulb just got screwed in a little bit tighter.

Now I have 2 questions arising from this discovery.

1. I did what you suggested and ran "set th line 12 20 100" but I would like to remove the MC320Cx from the programming. How do I  that?

2. Can you explain to me how Mitel determines Cabinet, Shelf, & Slot? For example this is from my system:

Cabinet   Shelf   Slot   P/N                DESCRIPTION
1             3         32     ViperAA IP     Controller
2             1          6         
3             1          6         
4             1          6      MCASUAA       ASU
5             1          6         
6             1         16     MC312AB       Peripheral SW Cont II
1             1         10     MCSTHA         ICP Comms
1             1         11     MC266AA       Communications Processor
7             1          2      MC270A         Universal T1

6             1          1      MC330AB       DNI Card
6             1          2      MC330AB       DNI Card
6             1          3      MC330AB       DNI Card
6             1          4      MC330AB       DNI Card
6             1          5      MC330AB       DNI Card
6             1          6      MC320CX       OPN Card
6             1          7      MC320CX       OPN Card
6             1          8      MC320CX       OPN Card
6             1          9      MC320CX       OPN Card
6             1         10         
6             1         11         
6             1         12     MC320CX   'Phantom' CARD
6             1         13         
6             1         14     MP914 AA   Power Converter
6             1         15     MP914 AA   Power Converter 
6             1         16     MC312AB    Peripheral SW Cont II
6             1         16A         
6             1         17         


- Tom
Title: Re: Minor Alarm
Post by: ralph on February 03, 2012, 07:53:18 PM

Quote
6   1     1      MC330AB       DNI Card

using part of your example, The 1st digit is the cabinet, the second digit is the shelf in that cabinet (almost always 1) and the 3rd digit is the card.  For that card you'd have 16 total circuits.   So the plid of the 6th circ on that card would be 6-1-1-6.

Don't remove a phantom card until you know what it's doing.  We'll program up those card for some special applications, usually something to do with voice mail.  Call each of the circuits and if you get a "out of service" on your display then it's ok to delete the circ.   Once you've removed all the circ's on the phone then you can go into the peripheral cabinets configuration and delete the card there.

Ralph
PS.  Thanks for the complement.
Title: Re: Minor Alarm
Post by: ttrumble111 on February 07, 2012, 03:18:11 PM
Ralph,

I get the plid 6-1-1-6 would be "Cabinet 6 - Shelf 1 - Slot 1 - Circuit 6", and I can physically see it, but what about the others "cabinets 1, 4, & 7" or "shelfs 3 & 1" or "Slots 32, 10, 11, 6, & 2" - whats that all about?

1             3         32     ViperAA IP     Controller
1             1         10     MCSTHA         ICP Comms
1             1         11     MC266AA       Communications Processor
4             1          6      MCASUAA       ASU
7             1          2      MC270A         Universal T1

I pieced together the information above from the log when I rebooted the 3300 last Friday. I am just trying to better understand the layout of the 3300 better so if something fails or is in an alarm state I can better troubleshoot it.

One other question. I know I can plug and unplug the Ethernet Port, FIM TX & RX, and the T1 connectors while its running without adversely affecting the 3300 - I think??? PLEASE tell me if I am wrong so that I don't fry the 3300, but what about the RJ21/Amphenol/50 Pin telco connector on the back? Can I unplug and plug the Amphenol connector while its running without hosing the 3300?

- Tom
Title: Re: Minor Alarm
Post by: v2win on February 07, 2012, 03:54:11 PM
Cabinet 1 is the 3300 itself the cards in cabinet 1 are virtual. Cabinet 4 is your embedded ASU and Cabinet 7 is your T1 module.

Yes you can unplug all the connections including the 50 pin amp cable without hurting anything. You will lose service on those but that is implied.
Title: Re: Minor Alarm
Post by: ttrumble111 on February 09, 2012, 03:54:06 PM
Thanks go to Ralph & v2win.

My backup Mitel system cutover went great Tuesday night @ 10PM.

Your answers to my questions have greatly assisted me on this project and I thank you.

Beers all around! ;D

- Tom
Title: Re: Minor Alarm
Post by: ttrumble111 on February 09, 2012, 04:15:17 PM
Oops I forgot to ask.

When Ralph suggested 'set thres lines 9 20 100' I did that but on a subsequent reboot it went back to "0 20 100". How do you save that threshold config to the firmware or configuration file so that on the next reboot I don't have to reset it again.

- Tom
Title: Re: Minor Alarm
Post by: ralph on February 09, 2012, 04:31:08 PM
That should have stayed.   That command is supposed to survive a reboot.

Not sure what's happening here.

Ralph
Title: Re: Minor Alarm
Post by: MitelMania on February 09, 2012, 09:10:43 PM
if you did a database restore the thresholds are lost..  I saw something about a backup and what not in the thread..  if you upgraded or did any kind of DB restore it will erase the alarm thresholds set by the set thresh commands..
-Christopher
Title: Re: Minor Alarm
Post by: ttrumble111 on February 13, 2012, 09:50:05 AM
Thank you Christopher,

During the March Reboot of my 3300 backup, that is currently in production, I will check the threshold and see if it goes back to the default.

- Tom
Title: Re: Minor Alarm
Post by: ttrumble111 on March 05, 2012, 10:21:50 AM
Before I reboot my "Backup" 3300, thanks to Ralph, Christopher, & v2win, from the Shell and check that the "thres lines 9 20 100" remained I would like to ask a couple of questions:


- Tom
Title: Re: Minor Alarm
Post by: ralph on March 05, 2012, 12:57:57 PM
I generally set up to reboot weekly so my command I use is "Program Reboot Sched Friday 2:15"

The following is right from the help files:


PROGRAMMED REBOOT
Qualifiers:
COURTESY ON

COURTESY OFF

DISPLAY

RESOURCE RECOVERY ON

RESOURCE RECOVERY OFF

RESOURCE RECOVERY <hh:mm:ss>

SCHEDULE ON

SCHEDULE OFF

SCHEDULE DAILY <hh:mm:ss>

SCHEDULE <day-of-week> <hh:mm:ss>

SCHEDULE MONTHLY <week # [1-4]> <day-of-week> <hh:mm:ss>

SCHEDULE INTERVAL <interval in weeks [1-52]> <MMM> <day-of-month> <hh:mm:ss>

•Note: The default values are:
PROGRAMMED REBOOT SCHEDULE IS OFF
PROGRAMMED REBOOT SCHEDULED: DAILY 02:15:00
PROGRAMMED REBOOT RESOURCE RECOVERY IS ON
PROGRAMMED REBOOT RESOURCE: RECOVERY 02:15:00
PROGRAMMED REBOOT COURTESY IS OFF