Snmp Versions; Snmpv1; Snmpv2C - Avaya G250 Administration

SNMP versions

There are currently three versions of SNMP:

SNMPv1

●

SNMPv2c

●
SNMPv3
●
The Avaya G350 Media Gateway supports all three of these versions. The implementation of
SNMPv3 on the G350 is backwards compatible. An agent that supports SNMPv3 will also
support SNMPv1 and SNMPv2c.
The Avaya G250 Media Gateway supports users for all three of these versions, but only
supports the SNMPv3 mechanism for sending traps. Thus, the set snmp trap command is not
supported in the G250, although the set snmp trap enable auth|frame-relay
command is supported.
SNMPv1
SNMPv1 uses community strings to limit access rights. Each SNMP device is assigned to a
read community and a write community. To communicate with a device, you must send an
SNMP packet with the relevant community name.
By default, if you communicate with a device using only the read community, you are assigned
the security name ReadCommN. This security name is mapped to the ReadCommG group by
default. This allows you to view the agent's MIB tree, but you cannot change any of the values
in the MIB tree.
If you communicate with a device using the write community, you are assigned the security
name WriteCommN. This security name is mapped to the WriteCommG group by default. This
allows you to view the agent's MIB tree and change any of the values in the MIB tree.
Note:
If you delete the ReadCommN or WriteCommN users, the ReadCommG or
Note:
WriteCommG groups, or the snmpv1WriteView or snmpv1View, you may not be
able to access the device using SNMPv1 or SNMPv2c.
In addition, traps are sent to designated trap receivers. Packets with trap information also
contain a trap community string.
SNMPv2c
SNMPv2c is very similar to SNMPv1. However, SNMPv2c adds support for the get-bulk action
and supports a different trap format.
SNMP versions
Issue 1.1 June 2005 205