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.

MMI-SYNC (MMI Synchronization)<br />

MO Name<br />

in Log<br />

Alarm<br />

Level<br />

Initial Comm<strong>and</strong> to Run Full Name of MO<br />

MMI-SYNC MIN <strong>test</strong> board location long Multimedia Interface circuit pack<br />

Note:<br />

Note: Refer to Chapter 4: General troubleshooting in Maintenance Procedures for<br />

<strong>Avaya</strong> Aura Communication Manager, Media Gateways <strong>and</strong> Servers<br />

(03-300432) for MMCH troubleshooting information.<br />

Each Port Network (PN) must have a TN787D or later MMI circuit pack assigned as the<br />

Multimedia Interface (MMI) master synchronization source for that PN. If one or more MMI<br />

circuit pack is administered in a PN, one MMI circuit pack is designated as the master<br />

synchronization source for every MMI circuit pack within that PN.<br />

The MMI circuit pack generates a synchronization signal <strong>and</strong> puts that signal on the TDM bus.<br />

Other MMI packs or any other circuit pack within a PN can listen to this signal <strong>and</strong> “synchronize<br />

up” to it. The first MMI circuit pack inserted in a PN is normally designated as the master. As<br />

subsequent MMI packs are inserted, they are instructed to listen <strong>and</strong> synchronize to the<br />

time-slot of the master MMI. In the unlikely case of an MMI losing this reference, an uplink<br />

message is sent from the MMI circuit pack that lost the signal to maintenance, which also clears<br />

the “event” counter on this MMI with a downlink message. This forces the MMI circuit pack to<br />

return the current state of the synchronization signal. If the signal is still lost, then the recovery<br />

algorithm is entered. Note that during this time, the MMI circuit pack synchronizes to its internal<br />

clock, <strong>and</strong> there should be no service disruption. A loss of synchronization is usually the result<br />

of a circuit pack failure. The maintenance strategy is to switch the master source away from the<br />

bad pack to another healthy MMI circuit pack within the PN.<br />

A synchronization switch takes place if half or more of the MMI circuit packs in a PN report a<br />

loss of synchronization. For example, a PN with two MMIs reporting a loss of sync source<br />

switches immediately, three <strong>and</strong> four MMIs switch if two report the loss, <strong>and</strong> so forth. A healthy<br />

MMI circuit pack becomes the master synchronization source providing the signal on a new<br />

timeslot. The other MMI circuit packs within the PN are instructed to listen to this new signal,<br />

<strong>and</strong> the old master stops providing the signal <strong>and</strong> now listens to the new master MMI. If an MMI<br />

is physically removed from the system, then the remaining MMIs report the loss of<br />

synchronization. The first MMI with no alarms present becomes the new master of that PN.<br />

Once a synchronization switch has occurred, another switch is not allowed for 15 minutes to<br />

avoid hyperactive switching. If every MMI has an alarm, then no switch is made.<br />

If the MMI circuit pack that provides synchronization is craft busied out, it will not affect the PN<br />

synchronization. The signal is still provided by the busied-out pack. There is no effect on<br />

synchronization if the technician enters a release of the busied-out MMI. Synchronization is not<br />

affected by a warm start of the system (reset system 1). For every other restart (reboot through<br />

cold 2), MMI synchronization recovers during board insertion.<br />

664 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!