
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1302PNC-DUP (PNC Duplication)
9
3. Follow the appropriate diagnostic and repair procedures for the alarmed
PNC components just as with a simplex PNC. Both the alarm and error
logs should be examined to isolate the fault.
4. Verify that the related PNC SOH is restored to all zeros.
5. Release the standby PNC for busy-out.
Refresh and Unrefresh of the Standby PNC
In a fully functional PNC with healthy standby and active sides, the standby PNC
has a complete set of call connections corresponding to those in the active PNC.
If, however, the state of health of the standby PNC degrades, a selective
unrefresh of those connections which utilize the faulted component(s) is
performed. If the health of the standby PNC improves, a selective refresh of
connections on the affected route is performed. so that call setup is consistent
between the active PNC and the healthy parts of the standby PNC.
The
Standby Refreshed?
field on the
status pnc
screen does
not
refer to the
selective type of refresh. It refers only to a global refresh which is performed
when:
■ The system is initialized and PNC duplication is enabled.
■ There has been a spontaneous PNC interchange.
■ The standby PNC has been released from busy-out.
■ A system reset of level 2 or higher has taken place.
The refreshed field may display
yes
when in fact the standby is partially
unrefreshed. An interchange into an incompletely refreshed standby will result in
dropped calls. This can happen when a more severe fault occurs on the active
PNC, or when
set pnc interchange
is used with the override option.
PNC Interchanges
PNC spontaneous interchanges occur when PNC duplication software
determines that the SOH of the standby PNC is better than that of the active PNC.
PNC-DUP executes a spontaneous interchange only when a message from a
PNC component maintenance object sends a message indicating that either a
fault has occurred on the active PNC, or a fault has been resolved on the standby
PNC such that the state of health of the active PNC is now lower than that of the
standby.
This message will usually indicate the type and location of the failed connectivity
component. A corresponding major or minor alarm is logged by the reporting
MO, stimulating an alarm report.