![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/2/07/207ea955-b0a5-4690-afdf-8b9461a5122e/207ea955-b0a5-4690-afdf-8b9461a5122e-bg394.png)
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-232ATM PNC-DUP (ATM PNC Duplication)
9
■ If a
reset system 1
(warm) takes place during a PNC interchange, the
reset is escalated to level 2 (cold2).
Fault isolation using Duplicated PNC
In some cases, PNC duplication can aid in the fault isolation procedure. PNC
interchanges can be used to help isolate the faulty hardware. Two examples
demonstrating this technique follow:
1. There is a fault that can occur in either the PPN ATM-EI or the PKT-INT
which cannot be readily attributed to one board or the other. If the packet
bus transceivers on either the PKT-INT or ATM-EI fail, 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 indicate which of
the two boards.
— If the interchange cures the problem, the ATM-EI was at fault.
— If the interchange does not cure the problem, the PKT-INT is
suspect, provided there are no PKT-BUS faults.
2. A similar relationship exists for the EPN Archangel (EAA - the active
ATM-EI) and certain TDM bus problems. If the EAA is unable to
communicate with a port board over the TDM bus, either 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. 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.
Error Log entries
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 Table 9-98
and
Table 9-99
can help to identify which areas of the Alarm Log to investigate to find
the source of the problem.