Avaya 03-300430 User Manual

Page of 2574
G700 Media Gateway Traps
324 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
 
37
(cont’d)
128
WRN
8. If manually resetting the VoIP module does not return it to 
service, and if a spare VoIP module of the same type is 
available, replace the failing VoIP module with the spare and 
see if the spare VoIP module goes into service. If so, follow 
procedures for dealing with the original, bad, VoIP module.
9. If the spare VoIP module fails to go into service, it is of course 
possible that the spare VoIP module is bad, as well. There may 
be a power issue, also. 
10. Try manually resetting the Media Gateway Processor at a time 
convenient to the customer and see if this restores service. If 
so, both the original and the spare VoIP modules can probably 
be considered okay, and the problem is probably with the 
Media Gateway Processor itself. Capture the trap information. 
If possible, capture the event logs, using the show 
event-log
 CLI command, for analysis. Escalate.
If none of this works, capture the trap information. If possible, 
capture the event logs, using the show event-log CLI
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server  (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
 20 of 20