Avaya Media Gateway G350, Maintenance Manual

Page: 301 / 332

G350 traps
G350 traps and resolutions
Maintenance of the Avaya G350 Media Gateway 301
June 2004
cmgTrapTypes 106 cmgRegistrationFault Major The Media Gateway cannot register with any
controllers in its controller list.
1 Verify that the controller list is correct.
From the CLI, use the command show
mgc list. The IP address should match
the Media Server CLAN or the Media
Server IP addresses.
2 If needed, correct this in the CLI’s
'configure' mode. Clear the mgc list with
the clear mgc list command. Then use a
set mgc list with the correct IP addresses.
3 If the IP address in the mgc list matches
the Media Server CLAN or the Media
Server IP addresses, there may be a
network problem.
4 Verify that the primary controller is up.
cmgTrapTypes 108 cmgH248LinkDown Minor An H.248 link between the Media Gateway and its
controller is down.
1 Check the S8300, S8500, or S8700. If
down, bring up.
2 If not, check the G350 administration.
Since the following command causes a
brief service outage, it should only be
executed at the customer’s
convenience.
3 If the administration is correct, reboot the
G350.
4 If the problem persists, check network
connectivity. Use ping or traceroute to
the S8300/S8500/S8700 to check
connectivity.
5 If the problem persists, speak to an Avaya
technical professional.
cmgTrapTypes 109 cmgH248LinkUp An H.248 link between the Media Gateway and its
controller that was down has come back up.
Table 159: G350 Traps and Resolutions 8 of 12
Enterprise
Trap
ID
Name
Msg
Facility
Severity Description / Resolution
8 of 12