MD110 Error Codes

[beirt]

Hi Folks,

i notice in many posts that people post with their issues and detail error-codes; 67, 31, etc and that there is in most cases a reply detailing what that error code is.

Where are you getting the info (docs) on the mappings between numerical error codes and the human-readable version?

Thanks

/B

 

[himdp]

Every release of MD110, MX-One TSW and MX-One TSE has had an associated library of documents. In the old days his was a large collection of binders.

For some time the document collection has been available in electronic form in various formats as technology and licencing dictated. I has been available as DocView, Dynatext, Alex and now, in my opinion the least useful, as a collection of pdfs known as CPI.

There is a section in the collection known as "Fault Locating" where every fault code is listed together with a flow chart defining how to handle the resolution with, when alll else fails, the ultimate step of "consult an expert"

You can obtain this collection from the Aastra Knowledge Base as a download.

I hope his helps.

 

[beirt]

Thanks. That explains the _where_ but doesn't help me locate the actual docs themselves. I assume soft-copy versions of these docs are not shared among the forum?

/B

 

[himdp]

You assume correctly as the documents are copyright.

Having said that, I believe they should be available to any legitimate user/maintainer of a system.

As I said before they are availale on the Knowledge Base web site if you have a log in, if not, request them from your service partner. Each library has a part number and can be ordered.

In the meantime, just post your alarms here and someone can look them up for you

 

[beirt]

Thanks for the offer. I'm building a monitoring view for the MD110 owner and am trying to parse the codes that are present in the SNMP Traps. I'd thought to find them in the MIBs but no luck.

The codes I would need to parse (for now) are;
25
31
268
270
271
303
309

Thanks

B

 

[beirt]

Just for anyone who has a similar need in future;

- The SNMP Traps sent fromt he MD110 actually containg an OctetString containing the human-readable version of the ErrorCode.

/B

 

[aastratech]

hope this helps for now !!



The codes I would need to parse (for now) are;

25
If the synchronization between the LIM and the GSM clock is faulty, (or between two LIMs in two LIM without group switch) SLIP will occur on the PCM line and the supervision program is informed.
ADD INFO 1: 0 = Slip between LIM and GSM clock has occurred in one LIM.
1 = Slip between LIM and GSM clock has occurred in several LIMs.


31
Incrementation alarm for alarm class 1
see fault locating directions for
If a specified number of system acknowledged alarms (set by means of command ALULS ) has arrived in alarm class 1, a new alarm is generated in alarm class 2. This is called incrementation alarm. The incrementation alarm is removed if the number of alarms in alarm class 1 becomes less than the specified number


268 Digital trunk Out of order
ADD INFO 1: Individual pointer to TRS data individual


270 Digital trunk, bit error in frame synchronization word
ADD INFO 1: Individual pointer to TRS data individual
l

271 Digital trunk, received alarm from remote end
ADD INFO 1: Individual pointer to TRS data individual
ADD INFO 2:
0 = Synchronization error in time slot 0
1 = Multiframe synchronization error in time slot 16
2 = Yellow alarm (CCITT)
3 = Remote multiframe alarm



303 Data link alarm
ADD INFO 1: Pointer to the interface
ADD INFO 2:
0 = G fault, Unsuccessful data link establishment
1 = H fault, No DL (Data Link) -RELEASE acknowledgement
2 = Maximum retransmit count exceeded
3 = J fault, Invalid received sequence number
4 = K fault, Frame reject response
5 = A fault, Not expected supervisory response
6 = B, C, D, E fault, Not expected UA (Unnumbered Acknowledgement or DM
(Disconnected Mode) response
7 = F fault, SABME (Set Asynchronous Balanced Mode Extended) from peer received
8 = Q fault, Blocking received
9 = R fault, DM (Disconnected Mode) response received
10 = I fault, No response on RR (Receiver Ready) or RNR (Receiver Not Ready)
11 = O fault, Received information field > N201 (260 Octets)
12 = L fault, Undefined control field
13 = N fault, Received frame with incorrect length
14 = M fault
15 = P fault, N2X4, Maximum number of retransmission of RNR frames exceeded
18 = TEI removal received
26 = TEI removal received





309 Data link alarm - bit error in bit stream (CRC-4)
The TLU-board has discovered a bit error in the incoming bit stream (CRC-4).
ADD INFO 1: Pointer to interface
ADD INFO 2: Bit error rate
0 = > 1 / errored seconds
1 = > 1 * 10EE -3 / severed errored seconds
2 = > 1 * 10EE -6 / degraded minutes


Tommy

 

[himdp]

25 SLIP on group junctor line
31 Incrementation alarm for alarm class 1
268 Digital trunk - out of order
270 Digital trunk - bit error in frame synchronization word
271 Digital trunk - received alarm from remote end
303 Data link alarm - faulty data link layer
309 Data link alarm - bit error in bit stream (CRC-4)

Is this OK?

 

[whosrdaddy]

aren't these codes available in the MIB?

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[beirt]

Thanks for the info folks. The info isn't in the MIB but it is in the traps sent so I can work around it for now.

 

[Damsube]

http://www.tek-tips.com/viewthread.cfm?qid=797751