19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PNC State-of-Health Indexes<br />

PNC-DUP (PNC Duplication)<br />

The Inter-PN <strong>and</strong> Inter-SN Indexes form the state of health vector, which is used to track <strong>and</strong><br />

compare the states of health of both PNCs. The fields making up the indexes are two digit<br />

numbers separated by periods (.), with each field representing a different class of faults. The<br />

fault class fields are arranged in order of decreasing importance from left to right. In other<br />

words, each field in the index supersedes the following fields in determining which PNC is<br />

healthiest. A fault class drives an interchange only when all of the higher priority fault classes<br />

are equal. A zero entry indicates no faults in that class. Increasing numbers indicate<br />

increasingly higher numbers of faults present in that class.<br />

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

(XX.XX). The Inter-PN Index reports faults in connectivity between port networks <strong>and</strong><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 212: 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 st<strong>and</strong>by’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 st<strong>and</strong>by 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 212: 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 />

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 />

Issue 5 May 2009 761

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

Saved successfully!

Ooh no, something went wrong!