Demand test descriptions and error codes - Avaya Support

Table 212: PNC State-of-Health Fault Classes
Fault Class Priority Description MOs
FC_SNIL 7 Number of inter-switch-node fibers
affected by peer or neighbor link faults
FC_SNIHW 8 Number of interswitch-node fibers
affected by hardware faults
In multi-node CSS configurations FC_DS1 is considered less critical that FC_SNINL since
DS1C constraints affect only one PN and indicate restricted bandwidth. However FC_SNINL
can indicate problems for all PNs on the far end switch node (the one downlink from the PN) If
the DS1C problem is critical (for example, loss of all bandwidth to the affected PN) 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, identify and repair the problem:
1. Look for PNC component alarms (major or minor) for the PNC side whose SOH is not all
zero. First repair the standby PNC.
2. Busy-out the standby PNC.
3. Follow the diagnostic and repair procedures for the alarmed PNC components just as with
a unduplicated PNC. Examine the alarm logs and error logs to isolate the fault.
4. Verify that the related PNC SOH is restored to all zeros.
5. Release the standby PNC for busy-out.
Refresh and Unrefresh of the Standby PNC
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 state
of health of the standby PNC degrades, a selective unrefresh of those connections which utilize
the faulted component(s) is performed. If the health of the standby PNC 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.
The Standby Refreshed field on the status pnc screen does not refer to the selective type of
refresh. It refers only to a global refresh that is performed when:
● The system is initialized and PNC duplication is enabled.
762 Maintenance Alarms for Communication Manager, Media Gateways and Servers
SNI-PEER
SN-CONF,
SNI-BD,
FIBER-LK
1. BFDLs only exist in Port networks that have an IPSI. Port networks that do not have an IPSI will
have the EI as Archangel and no BFDL faults.