Mitel 3300 - ICM Comms Card Critical Alert

[brunoit]

Hi

We have just put in our 2nd Mitel 3300 (CX) in to a regional office. The system has been linked to our head office (which has an MXe) using clustering and the networking is working fine, we can sync with Ops Manager, call from office to office and network hot desking is working perfectly (as is the synchronised phone book)

The problem is, the regional 3300 CX has a critical alarm (in fact, it says there are two occurrences of the alarm) related to "ICM Comms Card".

We had assumed this was related to the networking but as it is all working, we are a little confused as to why we still have this alarm.

The system was onriginally set up off site and was linked to another CX for testing, however all traces of this other system have been removed (we have checked every form from within the web interface on several occasions)


Any ideas would be much appreciated.

 

[Mitel100]

This alarm could mean two things.

1. A fault with your E2T card.
2. A problem with your IP trunking

Because there is two occurances of this fault, then more than likely it is your IP Trunking that has an issue.

 

[brunoit]

Hi
Thanks for the response. I have looked through this area and the only thing that stands out is that there is an extra entry under ICP/PBX Assignments for a system "4"...all information is blank within this entry, but I dont seem to be able to delete it...could this be the problem?

 

[Mitel100]

It could be, if you are unable to delete it, it may be referenced elsewhere, within your IP/Xnet forms.

 

[brunoit]

Hi
I have checked out both IPX/MET forms on the london system (with no alarms) and the Manchester system (with alarm) and they are identical except that London shows trunk group number 3 as the Manchester system under Trunk Group Assignment and Manchester shows trunk group number 1 as London, which are both correct. Am not sure where else to look.

thanks again

 

[Lundah]

The maintenance command "state xnet all" will tell you which remote PBX is generating the alarm. If it's a bogus entry, you'll have to look through the IP trunking forms and remove any programming referencing the bogus entry.

 

[brunoit]

Hi
Thanks for the response...I ran the maintenance command and there doesn't seem to be any problem there..the result I have is below:

Signalling | Link | Dest | XNET | State | Owner | ID |Status
Dvc Location | Handle |Switch| Trunk Id | | | |
-------------------------------------------------------------------------------
1 1 11 254 | 42 | 1 | |Established | | |
-------------------------------------------------------------------------------

THe only link shown is established. Could this be a bug? Its the latest software version for the 3300 CX.

thanks