Avaya 03-300430 Manual De Usuario

Descargar
Página de 2574
G700 Media Gateway Traps
304 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
 
G700 Alarm Format
G700 Media Gateways (serving either as standalone port networks, or as port networks within 
an IP or a Multi-Connect system) report alarms to the primary server (either an S8300 or S8700 
Media Server) using SNMP traps. Like the primary server’s own alarms, alarms from a G700 
Media Gateway:
Reside in the primary server’s alarm log
Can be viewed using the SAT command display alarms
Can be viewed using the Web Interface Display Alarms option
However, the format of these displayed alarms is slightly different. Using the G700 MO’s 
Event ID #1 (the first entry in 
on page 305) as an example, a displayed G700 alarm has the following format:
n CMG 1 WRN 07/17/2002:13:45 121.1.1.2:cmgMultipleFanFault
Within the previous alarm-display string, the value:
“n” is a sequential alarm ID.
“CMG” identifies a G700 Media Gateway as the MO.
“1” is the event’s ID (1st column of 
This table also contains each alarm’s corresponding SNMP trap # in the 2nd column of 
on page 305. However, 
many of the MIB-defined traps have been excluded, either because:
A specific trap (such as, Trap #3) is the SNMP mechanism to clear an alarm logged by 
another specific trap (in this case, Trap #2).
The specific event indicated by a trap is not severe enough to justify an entry in the 
primary server’s alarm log.
A trap is defined, but not implemented.
A trap # is reserved for future use.
“WRN” is the event’s severity (3rd column of 
“07/17/2002:13:45“is the event’s date and time stamp.
“121.1.1.2“is the IP address for Telnet access to the alarmed G700 Media Gateway 
Processor (MGP).
“cmgMultipleFanFault” is an alarm description (4th column of