Introduction

During normal operations, software or firmware may detect error conditions pertaining to specific Maintenance Objects (MOs) or other subsystems. The system automatically attempts either to fix or circumvent these problems. Errors are detected in two ways:

• Firmware on the component during ongoing operations
• A "periodic test" or a "scheduled test" started by software

The technician can run tests on demand that are generally more comprehensive (and potentially disruptive) than are the "scheduled tests".

When an error is detected, the maintenance software puts the error in the Error Log and increments the error counter for that error. When an error counter is "active" (greater than 0), there is a maintenance record for the MO. If a hardware component incurs too many errors, an alarm is raised.

Alarms on the S8300 Media Server with G700 Media Gateways can occur in several areas:

• Media Modules, Media Servers, the Media Gateway Processor, and the Layer 2 Switching Processor are all capable of detecting internal failures and generating traps and alarms.
• The G700 detects faults and alerts the Media Server; the Media Server then raises an alarm, and sends the alarm to an appropriate alarm management site.
• Communication Manager alarms reflect G700 health status.
• The Web Interface also displays platform alarms.

Alarms may be viewed using the following:

• Communication Manager Web Interface

Note: For non-Communication Manager alarms, use the Web Page header "Alarms and Notification" and "Diagnostics: View System Log". Choose the appropriate heading and, if necessary, call Avaya support.

• S8300 SAT CLI
• MGP CLI
• Layer 2 Switching Processor CLI