09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Media Gateway Traps<br />

The command syntax is:<br />

set SNMP trap {enable|disable}<br />

[{all|power|temp|app|module|config|voice|operations}]<br />

where is the IP address of the NMS trap receiver that will be receiving the<br />

traps from the G700, and<br />

[{all|power|temp|app|module|config|voice|operations}] indicates the groups<br />

whose traps will be sent to the specified receiver. If no keywords follow the IP address entry,<br />

then all traps will be enabled for the specified receiver.<br />

If "enable" or "disable" is used without a trap designation keyword, then all traps is<br />

assumed. Up to ten trap receivers can be configured.<br />

To configure the destination for media gateway SNMP traps<br />

1. From the L2 Processor CLI, enter session mgp<br />

2. At the mg-xxx-n(super-user) prompt, enter configure<br />

3. At the mg-xxx-n(configure) prompt, enter set snmp trap enable<br />

4. Enter exit<br />

Media Gateway Traps and Resolutions<br />

Although alarms can be viewed from the primary server, they are normally resolved from within<br />

the media gateway. The media gateway generates the following traps. Follow the error<br />

388 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!