Avaya CMC1, Maintenance Procedures

Page: 48 / 426

Maintenance strategy
G700 server-controlled maintenance
48 Maintenance Procedures
December 2003
a Media Server. Another goal is to create “smarter” Media Modules which, when combined with
enhancements of the G700’s maintenance software, allow all Media Module testing to occur on the G700
platform. Test results are sent to system management.
Capacity constraints and feature limitations
Although Media Modules and other G700 components have functionality similar to DEFINITY server
components, there are some differences. For example, the DCP MM supports 8 ports, while the TN2224
supports 24 ports. In addition, the hardware associated with some of the components differs significantly
from the DEFINITY server version.
These differences, as well as the fact that the G700 has control over the TDM bus, the tone/clock
generator, and the tone detectors means that a Media Server does not have any knowledge of those
components. In addition, any facet of port maintenance that deals with packet bus maintenance or system
synchronization will not be provided by the G700.
See Table 24, Media module tests, on page 49 for a complete list of the allowable and invalid tests for the
G700 Media Modules. As shown in this table, the board and port tests are based on existing tests that run
on the equivalent DEFINITY server port boards and the associated ports. Some tests abort with abort
code 1412 to indicate that these tests cannot be run on a Media Module Maintenance Object by
maintenance software on Avaya Media Servers.
NOTE:
No alarms are generated for failures detected by tests that are specified to abort for Media
Modules.