19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PNC-DUP (PNC Duplication)<br />

S8700-series Fiber-PNC only<br />

MO Name in Log Alarm Level Initial Comm<strong>and</strong> to Run Full Name of MO<br />

PNC-DUP NA status pnc PNC duplication<br />

In systems with the Critical Reliability option, the following components, which together<br />

comprise the Port Network Connectivity (PNC), are duplicated:<br />

● Expansion Interface (EI) TN570 circuit packs in the port networks (PNs)<br />

● Switch Node Interface (SNI) TN573 circuit packs in switch nodes<br />

● DS1 Converter (DS1C) TN574 circuit packs for remote PN connections<br />

● Fiber-optic cables (metallic in certain cases) connecting the above circuit packs<br />

● DS1 facilities between the DS1Cs<br />

● Switch Node Clock (SNC) TN572 circuit packs<br />

● IP Server Interface (IPSI) TN2312AP circuit packs<br />

Although not part of the PNC, Tone-Clock circuit packs are also duplicated in each PN. The<br />

PNC is available in two different configurations: direct connect, in which each port network is<br />

connected directly by fiber optic links to each other PN; <strong>and</strong> Center Stage Switch (CSS) which<br />

utilizes one or two switch nodes to interconnect the PNs. Direct connect systems can have up to<br />

two PNs. CSS systems with one switch node can have up to 15 PNs. CSS systems with three<br />

switch node can have up to 44 PNs. See Figure 61: Duplicated Direct Connect PNC<br />

Connectivity <strong>and</strong> Figure 62: Duplicated PNC with Center Stage Switch Connectivity.<br />

PNC duplication architecture utilizes an active/st<strong>and</strong>by duplication scheme, in which one<br />

complete set of PNC components supports call processing, while the duplicate PNC is held in<br />

reserve. All calls on the active PNC are simultaneously set up, or shadowed, on the st<strong>and</strong>by<br />

PNC in order for it to be capable of instantly assuming active status when necessary, allowing<br />

for interchanges without service disruption (in the case of single faults).<br />

The PNC-DUP MO tracks the health of the active <strong>and</strong> st<strong>and</strong>by PNCs, controls planned <strong>and</strong><br />

spontaneous interchanges, <strong>and</strong> manages related functions such as double call refresh <strong>and</strong><br />

unrefresh, anti-thrashing, <strong>and</strong> so on. The main responsibility of PNC-DUP is to recover the<br />

system to full service in the event of a fault. In the event of multiple faults PNC-DUP will do its<br />

best to maximize service continuity.<br />

PNC duplication does not introduce any additional types of hardware or hardware faults, <strong>and</strong><br />

there are no <strong>test</strong>s associated with the PNC-DUP MO. Instead, <strong>error</strong> log entries are used to log<br />

useful information about the occurrence <strong>and</strong> causes of interchanges. This is done in order to<br />

facilitate diagnosis of problems, which can then be addressed by using the documentation for<br />

the individual MO involved.<br />

754 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

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

Saved successfully!

Ooh no, something went wrong!