PNC-DUP (PNC Duplication)
Issue 1 May 2002
8-1291
555-233-143
In multinode CSS configurations FC_DS1 is considered less critical that FC_
SNINL since DS1C constraints affect only one PN and indicate restricted
bandwidth. However FC_SNINL can indicate problems for all PNs on the far end
switch node (the one downlink from the PN) If the DS1C problem is critical (for
example, loss of all bandwidth to the affected PN) a constraint with a higher order
fault class will be reported to PNC DUP.
Resolving Poor State of Health
When the SOHs for both PNCs are not all zeros (perfect health), use the following
steps to identify and repair the problem.
1. Look for PNC component alarms (major or minor) for the PNC side whose
SOH is not all zero. The standby PNC should be repaired first.
2. Busy-out the standby PNC.
3. Follow the appropriate diagnostic and repair procedures for the alarmed
PNC components just as with a unduplicated 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 form 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.
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...