Avaya G700 Maintenance Manual page 47

3 G700 Traps and Alarms:
Table 5. G700 Alarms (SNMP Traps) to the Primary Media Server
Event Trap
ID #
20 96 WRN
21 98 MAJ
22 100 MAJ
23 102 MAJ
Maintenance for S8300/S8700 and G700
555-234-101 — Issue 2 — October 2002
Alarm Description / Recommendation
Level
cmgProcessRestart — a software module on the Media Gateway
Processor failed. The Media Gateway Processor will attempt to restart
the failing module. A successful restart of the module will clear this trap
1. Check the Media Gateway Processor and insure that it has the
latest version of firmware installed. If it does not, install the latest
version of firmware and continue to monitor.
2. If this trap occurs infrequently and is automatically cleared, the trap
may be due to an unusual transient condition.Monitor future traps.
3. If the trap occurs frequently and is automatically cleared, it may
indicate an issue with a particular software module. Reset the
Media Gateway at a time convenient with the customer. Escalate
and have Tier 3 personnel capture the trap information and the
event logs for analysis.
4. If the trap occurs and does not clear, the Media Gateway may be
functionally impaired. Reset the Media Gateway at a time
convenient with the customer and consistent with the impairment.
Escalate and have Tier 3 personnel capture the trap information
and the event logs for analysis..
cmgIccMissingFault — An internal communications controller,
expected in Slot 1, is missing.
1. Check for presence of S8300.
2. If present, check the G700 administration.
3. If the administration is correct, suspect the S8300.
cmgIccAutoReset — The Media Gateway automatically reset the
internal communications controller.
1. If the problem persists, escalate.
cmgPrimaryControllerFault — The Media Gateway cannot contact the
first controller in its controller list.
1. Verify that the controller list is correct. From the MGP CLI, issue the
command show mgc list. The IP address should match the S8700
Media Server CLAN or the S8300 Media Server IP addresses.
2. If needed, correct this in 'configure' mode on the MGP's CLI by
clearing the mgc list first with the clear mgc list command, and
then issuing a set mgc list with the correct IP addresses.
3. If so, verify that the primary controller is up.
4. If so, shut down every LSP.
G700 Traps
Continued on next page
47