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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 89: Duplex-Reliability Configuration<br />

St<strong>and</strong>ard Reliability<br />

TONE-BD (Tone-Clock Circuit Pack)<br />

Systems with the st<strong>and</strong>ard-reliability option (no duplication options) have one Tone-Clock circuit<br />

pack in each port network. For the first Port Network of a cabinet this is in the A carrier. Cabinets<br />

containing a second EPN will also have a Tone-Clock circuit pack in the E carrier. This<br />

Tone-Clock circuit pack generates clocks <strong>and</strong> provides system tones for every carrier of the port<br />

network it resides in.<br />

High Reliability<br />

IPSI<br />

PN 1<br />

EI<br />

Server A Server B<br />

Control Network A<br />

IPSI<br />

PN 2<br />

EI<br />

Bearer Network<br />

S8700-series Fiber-PNC: The high-reliability configuration shown in Figure 90: High-Reliability<br />

Configuration has a duplicated server, a duplicated control network, <strong>and</strong> duplicated IPSIs in the<br />

IPSI connected port networks. With this configuration, every IPSI connected PN must have<br />

duplicated IPSIs. The control network is duplicated so that a single fault in the control network,<br />

such as a bad Ethernet switch, won’t bring the whole system down. The non IPSI connected<br />

port networks have unduplicated Tone-Clock boards.<br />

An EPN’s Tone-Clock circuit pack configuration is the same as for the st<strong>and</strong>ard-reliability option.<br />

Each PN’s Tone-Clock circuit is active for both tones <strong>and</strong> clock signals for its port network.<br />

T/C<br />

PN 3<br />

EI<br />

Issue 5 May 2009 991

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

Saved successfully!

Ooh no, something went wrong!