09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PNC-DUP (PNC Duplication)<br />

The Inter-PN Index contains six fields (XX.XX.XX.XX.XX.XX), and the Inter-SN Index has two<br />

(XX.XX). The Inter-PN Index reports faults in connectivity between port networks and<br />

supersedes the Inter-SN Index, which reports faults in connectivity between switch nodes. (The<br />

Inter-SN Index is only meaningful for systems with a center stage switch having two switch<br />

nodes, each of which is duplicated).<br />

The meaning of each fault class field is given in Table 307: PNC State-of-Health Fault Classes.<br />

A zero entry indicates that there are no such faults reported. Higher numbers indicate<br />

increasing number of faults. All zeros indicates perfect state of health. Unless the PNCs are<br />

locked, the active PNC’s state of health should always be equal to or better than the standby’s.<br />

(Otherwise, the system would perform a spontaneous interchange.)<br />

After a PNC-related alarm is cleared, the system performs a partial refresh of the standby PNC.<br />

The corresponding fault class field is not updated to reflect the improved state of health until the<br />

refresh is done. The state of health indexes will not agree with the current alarm status during<br />

this period.<br />

Table 307: PNC State-of-Health Fault Classes<br />

Fault Class Priority Description MOs<br />

FC_EAL 1 Number of PNs with EALs down EXP-PN<br />

FC_INL 2 Number of PNs with LINL, RINL, or<br />

EI-SNI neighbor link faults<br />

3 Number of PNs with BFDL (Bearer Fault<br />

Detection Link) faults<br />

FC_HW 4 Number of PNs affected by hardware<br />

faults in a link having an EI as an<br />

endpoint (Endpoints can be determined<br />

with list fiber-link.)<br />

FC_BFD 1<br />

FC_PER 5 Number of PNs affected by SNI peer link<br />

faults for SNIs connected to EIs<br />

FC_DS1 6 Number of PNs affected by DS1C facility<br />

faults<br />

FC_SNIL 7 Number of inter-switch-node fibers<br />

affected by peer or neighbor link faults<br />

FC_SNIHW 8 Number of interswitch-node fibers<br />

affected by hardware faults<br />

EXP-PN,<br />

SN-CONF<br />

SYS-LINK<br />

EXP-INTF,<br />

SN-CONF,<br />

FIBER-LK,<br />

SNI-BD,<br />

DS1C-BD<br />

SNI-PEER<br />

DS1FAC<br />

SNI-PEER<br />

SN-CONF,<br />

SNI-BD,<br />

FIBER-LK<br />

1. BFDLs only exist in Port networks that have an IPSI. Port networks that do not have an IPSI will<br />

have the EI as Archangel and no BFDL faults.<br />

In multi-node CSS configurations FC_DS1 is considered less critical that FC_SNINL since<br />

DS1C constraints affect only one PN and indicate restricted bandwidth. However FC_SNINL<br />

Communication Manager Release 5.0 Issue 4 January 2008 1123

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!