Lucent Technologies 555-233-119 Resolving poor state of health

DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119 Issue 1
April 2000
Maintenance Objects
3-202ATM PNC-DUP (ATM PNC Duplication)
3
The Int er-PN I ndex cont ains 3 field s (XX.XX. XX). The Inter- PN Ind ex rep ort s faul ts
in connectivity between p ort networks.
■The meaning of each fault class field is given in Table 3-83.
■A zero entry indicates that there are no faults rep orted.
■Higher numbers indic ate increasing number of faults.
■All zeros indicates per fect state of health.
■Unless the PNCs are locked, the active PNC’s state of health shoul d
always be equal to or better than the standby’s, otherwise, the system
performs a spontaneous interc hange.
After a PNC-related alarm is cleared, the sys tem performs a partial refresh of the
standby PNC. The corresponding fault class field is not up dated to reflect the
improved state of health until the refresh is d one. The state of health indexes do
not agree with the current alarm status d uring this period.
Resolving poor state of health
When the SoHs for both PNCs are not all zeros (perfect health), use the following
steps to identify and rep air the problem.
1. Look for PNC component alarms (major or minor) for the PNC sid e whose
SOH is not all zero. The standby PNC should be repaired first.
2. Busy-out the standby PNC.
3. Follow the appropriate diag nostic and repair p rocedures 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 SOH is restored to all zeros.
5. Release the standby PNC.
Table 3-83. PNC State of Health Fault Classes
Fault Class Priority Description MOs
FC_EAL 1 Numb er of PN s with EALs d own EXP-PN
FC_PACL 2 Number of PNs with LINL, RINL, or EI-SNI
neighbor link faults EXP-PN
FC_HW 3 Number of PNs affected by hardware faults in a
link having an EI as an endpoint. (End points can
be determined with list atm-pnc.)
ATM-EI