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.

● There has been a spontaneous PNC interchange.<br />

● The st<strong>and</strong>by PNC has been released from busy-out.<br />

PNC-DUP (PNC Duplication)<br />

● A system reset of level 2 or higher has taken place.<br />

The Refreshed field may show y when the st<strong>and</strong>by is partially unrefreshed. An interchange into<br />

an incompletely refreshed st<strong>and</strong>by results in dropped calls. This can happen when a more<br />

severe fault occurs on the active PNC, or when set pnc interchange is used with the<br />

override option.<br />

PNC Interchanges<br />

PNC spontaneous interchanges occur when PNC duplication software determines that the SOH<br />

of the st<strong>and</strong>by PNC is better than that of the active PNC. PNC-DUP executes a spontaneous<br />

interchange only when a message from a PNC component MO sends a message indicating that<br />

either a fault has occurred on the active PNC, or a fault has been resolved on the st<strong>and</strong>by PNC<br />

such that the state of health of the active PNC is now lower than that of the st<strong>and</strong>by.<br />

This message will usually indicate the type <strong>and</strong> location of the failed connectivity component. A<br />

corresponding major or minor alarm is logged by the reporting MO, stimulating an alarm report.<br />

In the less common situation when the resolution of a fault on the st<strong>and</strong>by renders it more<br />

healthy than a simultaneously faulted active PNC, the message will indicate the type <strong>and</strong><br />

location of the improved component.<br />

Once the interchange completes, the failed component will be on the st<strong>and</strong>by PNC. A dem<strong>and</strong><br />

interchange can be requested in the presence or absence of st<strong>and</strong>by PNC faults. The following<br />

sequence of actions can be observed during a fault-free interchange:<br />

1. The Expansion Interfaces currently acting as archangels in the PNs are deactivated as<br />

indicated by the amber LEDs going from flashing to on solid.<br />

2. The EIs in IPSI port networks are interchanged as indicated by the new st<strong>and</strong>by EI amber<br />

LED off <strong>and</strong> the new active EI amber LED on solid.<br />

3. One by one the EIs in non IPSI port networks are interchanged as indicated by new<br />

st<strong>and</strong>by EI amber LED turning off <strong>and</strong> the new active EI amber LED flashing (2 seconds<br />

on, 200 milliseconds off). At this point the interchange is functionally complete.<br />

4. The SNIs amber LEDs are updated. so that the SNIs on the active SN have amber LEDs<br />

on, while the st<strong>and</strong>by SN’s SNIs amber LEDs turn off.<br />

Certain conditions may interfere with the normal execution of the interchange:<br />

1. In a faulted spontaneous interchange it is possible the PN directly affected by the fault will<br />

be the last to interchange.<br />

2. A user directly affected by the single fault instigating a PNC interchange can experience a<br />

momentary outage of voice path connectivity during the switch.<br />

Issue 5 May 2009 763

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

Saved successfully!

Ooh no, something went wrong!