Avaya 03-300430 User Manual

TDM bus itself.  If TDM bus maintenance tests find no problems with the bus, then it is 
either the port board or the EAA.  It may be simpler to replace the port board than to request 
a PNC interchange.  However, if it is not clear which port board may be at fault or 
maintenance is being performed remotely, verify that the EAA is not at fault by executing a 
PNC interchange.  If the interchange solves the problem, then the EAA is faulty.  If the 
problem persists after the interchange, but TDM bus maintenance finds no problem, then 
the port board is faulty.

Whenever a PNC interchange takes place, an error is logged against PNC-DUP with a code 
that conveys information about the cause of the interchange and which PNC became active.  
There are no alarms associated with PNC-DUP errors, but there should be an alarm against the 
PNC component that caused the interchange.  There are no PNC-DUP test sequences, but 
status pnc provides information regarding the status of the PNCs.  The information in 

on page 597 can help to identify which areas of 

the Alarm Log to investigate to find the source of the problem.

1. The Aux Data indicates which PNC became active after the PNC interchange: “0” denotes PNC-A; “1” 

denotes PNC-B.

00000

Error in generating error code

None

1cxpp

Spontaneous Interchange in response to a constraint for A-PNC

Active PNC

2cxpp

Spontaneous Interchange in response to a constraint for B-PNC

Active PNC

51000

Spontaneous Interchange at expiration of SOH validation timer

Active PNC

52000

Spontaneous Interchange upon PNC UNLOCK

Active PNC

53000

Spontaneous Interchange at completion of Global Refresh

Active PNC

60801

PNC Demand Interchange

Active PNC

60800

PNC Demand Interchange with override

Active PNC