DEFINITY Enterprise Communications Server Release 8.2
Upgrades and Additions for R8r
555-233-115 Issue 1
April 2000
Troubleshooting an Upgrade
B-2New for Release 8
B
New for Release 8
■ATM PNC Duplication (ATM PNC-DUP)
■ATM Expansion Interface (ATM-EI)
■Mass Storage System
■Control LAN (C-LAN)
■Control LAN (C-LAN)
■System Links (SYS-LINK)

ATM PNC Duplication (ATM PNC-DUP)

The PNC-DUP maintenance object tracks the health of the ac tive and standby
PNCs, controls planned and sp ontaneous interchanges, and manages related
functions such as doub le call refresh and unrefresh, antithrashing , and so on.
The main responsibility of PNC-DUP is to recover the system to full service in the
event of a fault. In the event of multiple faults, PNC-DUP does its b est to
maximize service continuity.
In systems with the Critical Reliability option, the following components, whic h
together comprise the Port Network Conn ectivity (PNC), are duplicated :
■ATM-Expansion Interface (ATM-EI) circuit packs in the port networks (PNs)
■Fiber-optic cab les connecting the ab ove circuit pac ks to the ATM Switch
Interface Modules
■ATM Swi tc h
Although not part of the PNC, Tone-Clock circuit p acks are also duplic ated in
each PN. All systems have one Processor Port Network (PPN). ATM PNC systems
can have up to 43 EPNs.
PNC duplication architec ture utilizes an active/standb y duplication sc heme in
which one complete set of PNC co mponents supports c all processing, while the
duplicate PNC is held in reserv e. All calls on the active PNC are simultaneously
set up, or shadowed, on the stand by PNC in order for it to be cap able of instantly
assuming active status when nec essary, allowing for interchanges without
service disruption (in t he case of single faults).
PNC duplication does not introd uce any additional types of hardware or
hardware faults, and there are no tests associated with the PNC-DUP MO.
Instead, its error log entries contain useful information about the occurrenc e and
causes of interchanges in ord er to facilitate diagnosis of p roblems, which can
then be addressed by using the doc umentation for the individual maintenanc e
object involved.