Avaya G250 Administration page 62

Accessing the Avaya G250/G350 Media Gateway
2. If required, define additional notification recipients using the snmp server group, snmp
server host, and snmp server user commands, and activating the security
notification filter. For example:
//define an SNMP group:
G350-001(super)# snmp-server group MSS_group v3 noauth read iso write iso
notify iso
Done!
//create a new snmp user belonging to the SNMP group:
G350-001(super)# snmp-server user MSS MSS_group v3
Done!
//identify an SNMP trap recipient, activating the security notification
filter:
G350-001(super)# snmp-server host 5.5.5.2 traps v3 noauth MSS security
Done!
//view the SNMP configuration
G350-001(super)# show snmp
Authentication trap disabled
Community-Access Community-String
---------------- ----------------
read-only *****
read-write *****
SNMPv3 Notifications Status
-----------------------------
Traps: Enabled
Informs: Enabled Retries: 3 Timeout: 3 seconds
SNMP-Rec-Address Model Level Notification Trap/Inform User name
---------------- ----- ------- --------------- ----------- -------------------
5.5.5.2 v3 noauth all trap MSS
UDP port: 162
3. Use the set mss-notification rate command to modify the MSS reporting rate, if
necessary. The default is 300 seconds. The G250/G350 counts events for each Denial of
Service (DoS) class for the duration of the interval. At the end of each interval, if the count
of each class of DoS events surpasses a defined threshold, the G250/G350 generates an
MSS notification, reporting on the event type, event parameters, and the number of
occurrences.
4. Ensure that INADS reporting is configured on the active MGC. For information about
configuring INADS reporting in Avaya Communication Manager, see Avaya
Communication Manager documentation.
62 Administration for the Avaya G250 and Avaya G350 Media Gateways