SNMP versions
There are currently three versions of SNMP:
• SNMPv1
• SNMPv2c
• SNMPv3
The Branch Gateway supports all three versions. The implementation of SNMPv3 on the
Branch Gateway is backwards compatible. That is, an agent that supports SNMPv3 will also
support SNMPv1 and SNMPv2c.
Related topics:
on page 306
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 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.
SNMP
Administering Avaya G430 Branch Gateway
October 2013 305
Summary of Contents for G430
Page 1: ...Administering Avaya G430 Branch Gateway Release 6 3 03 603228 Issue 5 October 2013 ...
Page 12: ...12 Administering Avaya G430 Branch Gateway October 2013 ...
Page 246: ...VoIP QoS 246 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Page 556: ...IPSec VPN 556 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...