Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
The following is an example for running a long test sequence twice on a port on a circuit pack:
test port UUCSSpp l r 2
● UU = the universal cabinet number (1 - 64)
● C = the carrier designation (A, B, C, D, or E)
● SS = the circuit pack slot number (01, 02,...)
● pp = the 2-digit port number (01, 02,...)
● l = long test sequence
● r = repeat
● 2 = the number of times the test sequence should be repeated.
The following is an example for testing a port on a media module. It runs the short test
sequence:
test port GGGVSpp r 3
● GGG = the media gateway number (1 - 250)
● V = the literal letter V, which designates a media gateway
● S = the media module number (1 - 9)
● pp = the 2-digit port number (01, 02,...)
● r = repeat
Alarm levels
● 3 = the number of times the test sequence should be repeated
During normal operations, software or firmware may detect error conditions concerning specific
Maintenance Objects (MOs). The system automatically attempts to fix or circumvent the
problem. The alarms are classified depending on their effect on system operation:
● Major alarms — Failures that cause critical degradation of service. These alarms require
immediate attention.
● Minor alarms — Failures that cause some degradation of service, but do not render a
crucial portion of the system inoperable. A minor alarm typically affects a few trunks or
stations or a single feature. Minor alarms require attention, but the consequences are not
immediate.
● Warning alarms — Failures that cause no significant degradation of service or failures in
equipment. These failures are not reported to INADS or the attendant console.
● On-Board problems originate in the circuitry on the alarmed Media Module or circuit pack.
416 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers