Demand test descriptions and error codes - Avaya Support

Fault Isolation Using Duplicated PNC
PNC duplication, can, in some cases aid in the isolation of faults. PNC interchanges can be
used to help indict the faulty hardware. Following are two examples demonstrating this
technique.
● There is a fault which can occur in either an IPSI port network’s EI or the PKT-INT which
cannot be readily attributed to one board or the other. If the packet bus transceivers on the
PKT-INT or EI fail, it will be apparent that the two boards cannot communicate, but it will
not be clear which board is at fault. In this case, a planned interchange of the PNC can be
used to indict one of the two boards. If the interchange cures the problem, the EI was at
fault. If the interchange does not cure the problem, the PKT-INT is suspect, provided there
are no PKT-BUS faults.
● A similar relationship exists for the PN Archangel (active EI) and certain TDM bus
problems. If the EAA cannot communicate with a port board over the TDM bus, then the
EAA has a fault, the port board has a fault, or there is a problem with the 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.
- 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.
Error Log Entries
When 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. There should be an alarm against the PNC
component that drove the interchange.
There are no PNC-DUP test sequences. Use status pnc to see information regarding the
status of the PNCs.
766 Maintenance Alarms for Communication Manager, Media Gateways and Servers