Demand test descriptions and error codes - Avaya Support

ATM PNC-DUP (ATM PNC Duplication)
After a PNC-related alarm is cleared, the system performs a partial refresh of the standby PNC.
The corresponding fault class field is not updated to reflect the improved state of health until the
refresh is done. The state-of-health indexes do not agree with the current alarm status during
this period.
Table 43: PNC State-of-Health Fault Classes
Fault
Class
Priority Description MOs
FC_EAL 1 Number of PNs with EALs down EXP-PN
FC_PACL 2 Number of PNs with LINL, RINL, or EI-SNI neighbor link
faults
FC_BFD 3 Number of PNs with BFDL (Bearer Fault Detection Link)
faults
FC_HW 4 Number of PNs affected by hardware faults in a link having
an EI as an endpoint. Enter list atm pnc to see endpoint
designations.
Resolving Poor State of Health
When both PNCs do not have an all-zero SOH (perfect health), use the following steps to
identify and repair the problem.
1. Look for PNC component alarms (major or minor) for the PNC side without an all-zero
SOH. The standby PNC should be repaired first.
2. Busy-out the standby PNC.
3. Follow the appropriate diagnostic and repair procedures for the alarmed PNC components
just as with a simplex PNC. Both the alarm and error logs should be examined to isolate
the fault.
4. Verify that the related PNC’s SOH is restored to all zeros.
5. Release the standby PNC.
Refresh and Unrefresh of the Standby PNC
EXP-PN
SYS-LINK
ATM-EI
In a fully-functional PNC with healthy standby and active sides, the standby PNC has a
complete set of call connections corresponding to those in the active PNC. If, however, the
standby PNC’s state of health degrades, a selective unrefresh of those connections that utilize
the faulted component(s) is performed. If the standby PNC’s health improves, a selective
refresh of connections on the affected route is performed so that call setup is consistent
between the active PNC and the healthy parts of the standby PNC.
Issue 5 May 2009 163