09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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-DUP (PNC Duplication)<br />

3. At this point, the faulty component is on the standby PNC, and the PNCs are locked in their<br />

current active/standby state. Busy-out the PNC.<br />

4. Use fault isolation and component testing procedures for the individual PNC components.<br />

Replacement of components will not disrupt operation of the active PNC.<br />

5. Once the failed component is replaced, test the standby PNC component from the terminal<br />

to ensure the replacement is functioning properly.<br />

6. When the problem is resolved as indicated by a state of health with all zeros, (status<br />

pnc), unlock and release the pnc.<br />

No further PNC interchange is required because you can test the standby PNC as thoroughly as<br />

the active.<br />

Interactions: <strong>Server</strong> Resets and PNC Interchanges<br />

● A system reset of level 1 (warm), 2 (cold2) or 4 (reboot) does not change which PNC is<br />

active. If a PNC interchange was in progress when the reset took place, the PNC<br />

interchange still goes to completion.<br />

● If a system reset level 1 (warm) takes place during a PNC interchange, the reset is<br />

escalated to level 2 (cold2).<br />

Fault Isolation Using Duplicated PNC<br />

PNC duplication, can, in some cases aid in the isolation of faults. PNC interchanges can be<br />

used to help indict the faulty hardware. Following are two examples demonstrating this<br />

technique.<br />

● There is a fault which can occur in either an IPSI port network’s EI or the PKT-INT which<br />

cannot be readily attributed to one board or the other. If the packet bus transceivers on the<br />

PKT-INT or EI fail, it will be apparent that the two boards cannot communicate, but it will<br />

not be clear which board is at fault. In this case, a planned interchange of the PNC can be<br />

used to indict one of the two boards. If the interchange cures the problem, the EI was at<br />

fault. If the interchange does not cure the problem, the PKT-INT is suspect, provided there<br />

are no PKT-BUS faults.<br />

● A similar relationship exists for the PN Archangel (active EI) and certain TDM bus<br />

problems. If the EAA cannot communicate with a port board over the TDM bus, then the<br />

EAA has a fault, the port board has a fault, or there is a problem with the TDM bus itself.<br />

- If TDM bus maintenance tests find no problems with the bus, then it is either the port<br />

board or the EAA. It may be simpler to replace the port board than to request a PNC<br />

interchange.<br />

Communication Manager Release 5.0 Issue 4 January 2008 1127

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

Saved successfully!

Ooh no, something went wrong!