VMX 200 remote alarm??

[kma66]

This is the first time I've done this, so we'll see if it works....

Our receptionist has started receiving calls that play a voice mail system message "check modem, alarm 15400...error message 33". She said that it just started on 9/18.

I listed the hardware errors (see below), but I don't know what they mean and can't locate any documentation on this historical monument. Our vendor no longer supports this system so I don't have much to go by.

*** ALARM HAS BEEN GIVEN ***

TYPE SLOT CHNL PRIO DATE TIME #BAD DATA1 DATA2 DATA3 DATA4
33 01 00 3 09/19 11:16 3 00000000 00000005 00000000 00000000
24 01 01 2 08/28 10:17 2 00000009 00000002 00000000 00000003
24 01 00 2 09/18 10:52 8 00000010 00000001 00000000 00000000
24 01 00 2 09/18 10:52 6 00000010 00000002 00000000 00000000
24 01 00 2 09/18 12:25 5 00000010 00000003 00000000 00000000
24 01 00 2 09/18 12:25 3 00000010 00000004 00000000 00000000
24 01 00 2 09/18 12:25 1 00000010 00000005 00000000 00000000
24 01 01 2 09/18 12:25 2 00000009 00000001 00000000 00000003
24 01 16 2 09/18 12:28 2 00000007 00000002 00000001 0000002A
24 01 16 2 09/18 12:29 2 00000007 00000002 00000001 00000019
24 01 16 2 09/18 12:29 2 00000007 00000002 00000001 00000090
24 01 16 2 09/18 12:29 2 00000007 00000002 00000000 000000E1
42 00 00 1 09/19 11:16 3 00000016 00000000 00000000 00000000

Can anyone shed some light on how I can get the calls to stop? We were having some Nortel PBX issues that have been resolved, so I'm hoping that all is OK. We are currently getting quotes on a new VM system, so I just pray that our current system lives until we send it to the pearly e-waste gates.

Any help would be appreciated...

 

[doktor]

Hardware error type 24 is data link related.
If the expected data packet was not received within the tolerated time window, you will see type 24 for each port.

The type 24 alarm with DATA1 to DATA4 can be explained in this way:

DATA1 = 00000007 -> Fault when lighting a message waiting lamp on port 1 and port 2.

DATA1 = 00000009 -> If the expected data packet was not received within the tolerated time window, you will see type 24 for each port. This is seen for port 1 and port 2.


TYPE 42 deals with MENU - Single Digit menues.

TYPE 33 deals with Line Card Hardware Error.
Error logged by selftest when start LSP reply was
received with either an error status or an unexpected OK status (e.g., Slot is empty or already reported
down)

DATA-1:
00 = START LSP REPLY RECEIVED WITH EITHER AN ERROR
STATUS OR AN UNEXPECTED OK STATUS.

DATA-2:REPORTED STATUS
00 = LSP SUCCESSFULLY STARTED

DATA-3 = CURRENT SLOT STATE
00 = EMPTY (UNCONFIGURED)

--------------

Try to do a C H, and check later with L H


///doktor

 

[doktor]

Check the board in SLOT=1 (Most left in the VMX/OCTEL-200).
It is the board that makes the trouble..

Also check and post (here) the boards list:

1. logon
2. Go to update by pressing U and enter.
3. write l slot at the .-prompt.
4. post the result here.
5. type e for exit, and you are back at the @-prompt
6. Do a L H (at the @-prompt)and post the resutlt here.
Thanks.


///doktor

 

[kma66]

Hi Doktor,

Thank you so much for responding...

1. I did l h first. Nothing new from post. I then did c h.

2. Here's the l slot:

SLOT CARD TYPE PORT EXTENSION# COS MODE OUTCALL TEST SYS
---- ---------- ---- ---------- --- ---- ------- ---- ---
1 PICNT 1 7555 127 AX NO NO 1
2 7202 127 AX NO NO 2
3 7203 127 AX NO NO 3
4 7204 127 AX NO NO 4
5 7205 127 AX NO NO 5
6 7206 127 AX NO NO 6
7 7207 127 AX NO NO 7
8 7208 127 AX NO NO 8
9 7214 127 AX NO NO 9
10 7215 127 AX YES NO 10
11 7216 127 AX YES NO 11
12 7217 127 AX YES NO 12
13 7114 127 AX YES NO 13
14 7115 127 AX YES NO 14
15 7116 127 AX YES NO 15
16 7117 127 AX NO NO 16

Message Waiting Link= 16
COS=

LSP table: PIC_NT
PRIMARY SYNC RECEIVER OF CLOCK

3. Here's the l h:

WED 09/23 10:27:52 2009 ELKGROVE ID:15400 S/N:211321 PBX:74
CLEARED: 09/23 10:18
TABLE IS EMPTY
@

 

[doktor]

Please try to make some calls to the system and see if the L H (alarm log) gets full.
Please post the result of the L H.

///doktor

 

[kma66]

I made several test calls and the log remained clear.

THU 09/24 15:07:51 2009 ELKGROVE ID:15400 S/N:211321 PBX:74
CLEARED: 09/23 10:18
TABLE IS EMPTY

 

[doktor]

So we solved this one! ;-))

///doktor

 

[kma66]

Hi Dok,

Thank you so much for being so helpful!!!

The same PBX cabinet went down again today... Nortel is checking into it, but here's what the l h looks like:

TYPE SLOT CHNL PRIO DATE TIME #BAD DATA1 DATA2 DATA3 DATA4
24 01 00 2 09/25 11:10 4 00000010 00000003 00000000 00000000
24 01 00 2 09/25 11:10 2 00000010 00000004 00000000 00000000
24 01 00 2 09/25 11:10 1 00000010 00000005 00000000 00000000
24 01 00 2 09/25 11:10 3 00000010 00000002 00000000 00000000
24 01 00 2 09/25 11:10 3 00000010 00000001 00000000 00000000
24 01 01 2 09/25 11:10 1 00000009 00000001 00000000 00000003
24 01 01 2 09/25 11:11 1 00000009 00000003 00000000 00000003
24 01 16 2 09/25 11:13 1 00000007 00000002 00000000 000000E1
24 01 16 2 09/25 11:13 1 00000007 00000002 00000001 0000002A
24 01 16 2 09/25 11:14 1 00000007 00000002 00000001 00000019
24 01 16 2 09/25 11:15 1 00000007 00000002 00000001 00000090
@

These errors generated approximately an hour after the cabinet originally went down. 7 of the 16 voice mail ports reside in that cabinet.

Is it 5pm yet??? This time next week I'll be packing my bags and leaving California for Hawaii... Oh, it can't come soon enough....

 

[doktor]

The errors shown in todays "l h" should not tear down a system!
Type 24 deals most with datapackets on the serial port or if you are using NIC boards like PIC_NT.
These boards carry both signalling and speech between the OCTEL and the Nortel PBX.
Syncronisation between the 2 systems can have gone bad.
Or the 2 boards (1 in the OCTEL and 1 in the Nortel PBX could be defective).
When we saw these errors, it often solved the problem if a good common grounding was made between the PBX and the OCTEL system. In some cases, a good thick ground cable was installed from one system to the other system.
Other cases were solve using shielded cable between the 2 systems.
Maybe you can use some of these ideas?
Let me know what the Nortel guys found out...


///doktor

 

[doktor]

& have a nice trip to Hawaii...

///doktor

 

[kma66]

Whew! What a relief! I'll get back to you on Monday....

Thanks again for sharing your knowledge....have a great weekend!

 

[kma66]

Hi Doktor,

It turns out that the power supply to the PBX cabinet kept failing and died for good yesterday. It was replaced and everything has worked fine since. The Octel is happy, the PBX is happy, so thankfully all of the users are happy!

Thank you so much for your expertise and for putting my mind at ease.

K

 

[doktor]

Thanks for the Update.
We expect OCTELs to last for many years to come.
(Some of mine has been running for 16+ years).

///doktor

 

[kma66]

I know what you mean.... The 2 that we have are pushing 20.... Long live the Octel! Take care!