Demand test descriptions and error codes - Avaya Support

PNC-DUP (PNC Duplication)
Most repairs involve fixing a single fault on the standby PNC.
1. Use set pnc lock or busyout pnc to prevent an interchange into the PNC being
repaired.
If a faulty component exists on the currently active PNC, the standby PNC is more
severely faulted. Normally the standby PNC is repaired first because it is the most severely
impaired.
2. To repair the active PNC, use reset pnc interchange override-and-lock to
request an interchange and ensure that no subsequent interchange occurs during the
repair of the standby PNC.
The demand interchange may not be necessary if the following conditions drive a
spontaneous interchange:
● The anti-thrashing period from the last interchange has expired.
● The global refresh from releasing the standby PNC has completed.
The standby PNC SOH is better than the active.
3. At this point, the faulty component is on the standby PNC, and the PNCs are locked in their
current active/standby state. Busy-out the PNC.
4. Use fault isolation and component testing procedures for the individual PNC components.
Replacement of components will not disrupt operation of the active PNC.
5. Once the failed component is replaced, test the standby PNC component from the terminal
to ensure the replacement is functioning properly.
6. When the problem is resolved as indicated by a state of health with all zeros, (status
pnc), unlock and release the pnc.
No further PNC interchange is required because you can test the standby PNC as thoroughly as
the active.
Interactions: Server Resets and PNC Interchanges
● A system reset of level 1 (warm), 2 (cold2) or 4 (reboot) does not change which PNC is
active. If a PNC interchange was in progress when the reset took place, the PNC
interchange still goes to completion.
● If a system reset level 1 (warm) takes place during a PNC interchange, the reset is
escalated to level 2 (cold2).
Issue 5 May 2009 765