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.

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

In addition the TN780 allows customization of up to six system tones in order to meet specific<br />

country needs. These changes are made using the change system-parameters<br />

country-options form.<br />

The TN2182 allows the same International changes as the TN780 but allows the customization<br />

of up to 24 system tones in order to meet specific country needs. These changes are made<br />

using the change tone-generation form.<br />

Manual Tone-Clock Interchange<br />

In an EPN with duplicated Tone-Clock or IPSI circuit packs, one circuit pack is always preferred<br />

over the other. For the first port network in a cabinet, this is the Tone-Clock or IPSI circuit pack<br />

in carrier A. If a second port network is configured in a cabinet, its preferred Tone-Clock or IPSI<br />

circuit pack is located in carrier E. The intention is that if the preferred Tone-Clock or IPSI circuit<br />

pack has been replaced or repaired, the system will make it active by interchanging to it as soon<br />

as possible.<br />

In a Port Network (PN) with more than one Tone-Clock circuit pack, the intention is to assure<br />

that the one considered most healthy is active at any given time. This is independent of the<br />

server duplication strategy, in the sense that the active Tone-Clock circuit pack need not change<br />

with an interchange of carriers. Rather, except for the effect of the manual intervention<br />

discussed earlier, Tone-Clock interchanges occur only as a result of changes in the health of<br />

Tone-Clock circuit packs, as perceived by maintenance software. When both Tone-Clock circuit<br />

packs are equally healthy, no preference is given to one over the other, regardless of which<br />

carrier is active.<br />

It is possible to manually control Tone-Clock interchanges in three ways.<br />

1. The st<strong>and</strong>by Tone-Clock circuit pack may be made unavailable for most purposes by using<br />

busyout tone-clock location. Such a Tone-Clock may not be selected with<br />

console comm<strong>and</strong>s, nor with normal maintenance software activities, until it has been<br />

made available again with restore tone-clock location.<br />

Note: busyout<br />

Note:<br />

tone-clock is not allowed for active Tone-Clock circuit packs.<br />

2. The processor lock switches may be used to force a particular SPE to be active. This<br />

method overrides all other Tone-Clock interchange controls. If there is a Tone-Clock circuit<br />

pack in the same carrier as the active SPE, it will become active, regardless of its health. If<br />

the Tone-Clock circuit pack in the selected SPE was in the busyout state (see item 1<br />

above), it will automatically be released <strong>and</strong> made active. While the lock switches are set<br />

for a particular carrier, no manual intervention or software <strong>error</strong> detection will cause an<br />

interchange of Tone-Clocks; the Tone-Clock circuit pack in the st<strong>and</strong>by SPE carrier can<br />

never become active. If there is no Tone-Clock circuit pack in the selected SPE at the time<br />

the switches are set, but one is later installed, the system will interchange to it regardless<br />

of its health. If the Tone-Clock circuit pack is removed from an SPE while the switches are<br />

set, no interchange will occur; the system will have no active tone-clock. When the lock<br />

switches are restored to the neutral position, a tone clock interchange will occur only if the<br />

st<strong>and</strong>by Tone-Clock circuit pack is healthier than the active one.<br />

Issue 5 May 2009 995

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

Saved successfully!

Ooh no, something went wrong!