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.

G700 Traps<br />

Configure the G700 to send SNMP traps<br />

Configuring the G700 Media Gateway to send SNMP traps to the primary server can be<br />

accomplished by two commands:<br />

G700 Traps<br />

● Layer 2 Switching Processor CLI command: set snmp community trap [community<br />

string]<br />

● Media Gateway Processor (MGP) CLI command: set snmp trap <br />

enable<br />

Configure an SNMP community string for traps<br />

SNMP requires community strings to be used for each SNMP "request". Only three community<br />

strings can be set on the G700 — one each for read requests, write requests, and traps. The<br />

command for traps is set snmp community trap [community string].<br />

To configure an SNMP community string for traps<br />

1. Open the Run dialog box.<br />

2. Enter telnet <br />

3. Log in as root.<br />

4. At the L2 Processor CLI prompt, enter set snmp community trap [community<br />

string]<br />

5. Enter exit<br />

Configure the destination for G700 SNMP traps<br />

Events occurring on the G700 cause SNMP traps to be generated. The G700 MGP can be<br />

configured to send SNMP traps to any network management system (NMS) in the network,<br />

including the primary server. The MGP CLI set snmp trap command is the way to configure<br />

the NMS network element that will receive those traps. The traps are sent in User Datagram<br />

Protocol (UDP) on the customer’s IP network.<br />

Communication Manager Release 5.0 Issue 4 January 2008 387

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

Saved successfully!

Ooh no, something went wrong!