XMI000 28 : Msg from shelf 0: XPEC error #0001

[Extinguish]

I frequently receive error: "XMI000 28 : Msg from shelf 0: XPEC error #0001" on my Meridian-81c. Can anyone provide any assistance as to a possible solution? Thanks.

 

[johnpoole]

the trouble is from loop 28, is that a working loop? of so is it an ipe? if so, replace the network and/or controller cards.. if not let us know the loop type so we can help.

XMI0000 aaaa
Message ""aaaa"" received from a Network Card (NT8D04). The possible
messages are: 1. PLL UNLOCK EVENT. The Network card lost synch with the
system clock. 2. MSG FROM SHELF x: XPEC ERROR 0001. This error is
usually self correcting. If may indicate a double timeslot problem or
invalid call teardown. 3. TN READ UNBLOCKED: CNT=x. A number of SSD
messages
were sent to the PS card but not acknowledged. In order to prevent the
locking of the message path, the Network card assumed the message was
received. 4. Any of the following three messages: XNET POLLING FAILURE
ON PORT x RSIG LINK LOST ON PORT #x - REINITIALIZED R71 DISASTER;
CANNOT ALIGN TRANSCEIVERS. These messages indicate that the Controller
is not responding to the Network card polling messages.
Action: 1. a. Ignore if message occur when clocks are switched.
b. If it occurs periodically, switch the clocks.
c. If it occurs often, replace Network card or clocks. Random XMI000
messages may be generated if excessive Electrostatic Discharges (ESD)
are allowed to enter the system. These messages may be safely ignored.
Refer to General Maintenance Information (553-3001-500) for ESD
avoidance practices.
2. a If message occurs rarely, ignore it.
b. If it occurs often, replace the Controller.
3.  a. If message occurs rarely, ignore it.
b. If it occurs often, replace the PS or Network card.
4.  a. Check cabling between Controller and Network.
b. Replace the Controller.
c. Replace the Network. In X11 Release 15 and 16, ""FRw APx SQy TPz""
is output before the text, where ""w"" is the loop number. This data is
not output in X11 Release 17 and later. Messages without text indicate
that the Network or Controller card have requested software download.
Severity:  Critical

post from err xmi000... switch looked it up without the loop 28 trailer..

john poole
bellsouth business
columbia,sc

 

[Extinguish]

Thank you for your assistance - I'll mostly be replacing the controller card. Thanks again.

 

[Extinguish]

It appears that this "XMI000 Error" is occuring on several super loops. Such as "XMI000 68, XMI000 84, XMI000 28,XMI000 36. We do utilize IPE. I don't believe it to be the controller if it's happening throughout the switch. For each "XMI ERROR", they are all the same format i.e. "XMI000 ## : Msg from shelf 0: XPEC error #0001". Also, all the mentioned loops are funtioning with out error. Could there be something else going on? Got any ideas? Thank you.

 

[johnpoole]

because you are using ipe shelves it could be related to traffic. does this happen on heavy voice and/or data traffic?

john poole
bellsouth business
columbia,sc

 

[janaya]

Take a look at this.


Title:
Getting XMI000 messages.

Facts:
PBX
Meridian
Meridian 1
Option 81C
CPP
FNF
release 25.40

Symptoms:
Getting XMI000 messages.
Error: XMI000
XMI000
XMI000s throughout day following upgrade to 25.40.
XMI000s point to variety of loops.


Changes:
Upgrade to 25.40.


Fix:

Install patch 03943.
Note : The patch is designated as 03943, there is no preceding MPLR.

 

[Extinguish]

This would be related to voice traffic... Thx

 

[janaya]

are you also getting AUD messages along with the XMI messages?

John

 

[Extinguish]

Janaya - yes, "AUD000" - "AUD017" - "AUD019" - "DTC001" - and occasionally TFS402 & TFS501 errors.
My switch is running:
VERSION 3011
RELEASE 24
ISSUE 25 + MDCS03 NA00

-Thanks

 

[yyrkroon]

I had the same problem with one of our 81C CP4 25.40B system.

I replace every single controller, network card, persig card and I would still have the same problem, sometime more often then other.

Finally, opened a case with Nortel and they found that our 81 wasn't balanced. The TimeSlot to TNs ratio was to low, they recommended that we provision more SL and segment it all out to give a more even TimeSlot to TNs ratio. Once we did that, no more XMI, haven't seen an XMI in a couple of years now...with the exception of the normal one when you pull the cards.

Just my .02, might be worth checking into

 

[janaya]

Here you go. Looks like a tedious fix but nothing too critical.



Solution ID: NORT108918 Product Family: Enterprise Voice Create Date: 11/01/2002

Title:
Mail agent causing XMI000 and AUD017, AUD018, AUD019, and TFS501

Facts:
PBX

Meridian 1 - Core

CallPilot mini

Octel

Centigram

MIK

MCK

Guest mailboxes

PBX is interfaced to voice mail through a M2616 port with MIK and MCK keys programmed.

NARS


Symptoms:
Mail agent causing XMI000 and AUD017, AUD018, AUD019, and TFS501

AUD019 decode shows Mail agent TN

XMI000

XMI000 4 : Msg from shelf 1: XPEC error #0001

AUD017

AUD018

AUD019

TFS501


Cause:
Mail is attempting to set message waiting to an invalid DN beginning with AC1 or AC2.


Fix:

Remove the message waiting DN from the mailbox or guest mailbox when the DN is not a valid DN in the M1 network, or the DN routes to a NI2 interface.