DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1301PNC-DUP (PNC Duplication)
9
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 will
not agree with the current alarm status during this period.
Inter SN Index: FC_SNIL s11.s10 FC_SNIHW
In multinode CSS configurations FC_DS1 is considered less critical that FC_
SNINL since DS1C constraints affect only one EPN and indicate restricted
bandwidth. However FC_SNINL can indicate problems for all EPNs on the far
end switch node (the one downlink from the PPN) If the DS1C problem is critical
(for example, loss of all bandwidth to the affected EPN) a constraint with a higher
order fault class will be reported to PNC DUP.
Resolving Poor State of Health
When the SOHs for both PNCs are not all zeros (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 whose
SOH is not all zero. The standby PNC should be repaired first.
2. Busy-out the standby PNC.
Table 9-510. PNC State of Health Fault Classes
Fault
Class Priority Description MOs
FC_EAL 1 Number of PNs with EALs down EXP-PN
FC_INL 2 Number of PNs with LINL, RINL, or EI-SNI
neighbor link faults
EXP-PN SN-CONF
FC_HW 3 Number of PNs affected by hardware
faults in a link having an EI as an endpoint
(Endpoints can be determined with list
fiber-link.)
EXP-INTF SN-CONF
FIBER-LK SNI-BD
DS1C-BD
FC_PER 4 Number of PNs affected by SNI peer link
faults for SNIs connected to EIs
SNI-PEER
FC_DS1 5 Number of PNs affected by DS1C facility
faults
DS1FAC
FC_SNIL 6 Number of inter-switch-node fibers
affected by peer or neighbor link faults
SNI-PEER
FC_
SNIHW
7 Number of inter-switch-node fibers
affected by hardware faults
SN-CONF SNI-BD
FIBER-LK
