13.07.2015 Views

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SNMP versionsSNMPv1SNMPv1 uses community strings to limit access rights. Each SNMP device is assigned to aread community and a write community. To communicate with a device, you must send anSNMP packet with <strong>the</strong> relevant community name.By default, if you communicate with a device using only <strong>the</strong> read community, you are assigned<strong>the</strong> security name ReadCommN. This security name is mapped to <strong>the</strong> ReadCommG group bydefault. This allows you to view <strong>the</strong> agent’s MIB tree, but you cannot change any <strong>of</strong> <strong>the</strong> valuesin <strong>the</strong> MIB tree.If you communicate with a device using <strong>the</strong> write community, you are assigned <strong>the</strong> securityname WriteCommN. This security name is mapped to <strong>the</strong> WriteCommG group by default. Thisallows you to view <strong>the</strong> agent’s MIB tree and change any <strong>of</strong> <strong>the</strong> values in <strong>the</strong> MIB tree.Note:Note: If you delete <strong>the</strong> ReadCommN or WriteCommN users, <strong>the</strong> ReadCommG orWriteCommG groups, or <strong>the</strong> snmpv1WriteView or snmpv1View, you may not beable to access <strong>the</strong> device using SNMPv1 or SNMPv2c.In addition, traps are sent to designated trap receivers. Packets with trap information alsocontain a trap community string.SNMPv2cSNMPv2c is very similar to SNMPv1. However, SNMPv2c adds support for <strong>the</strong> get-bulk actionand supports a different trap format.SNMPv3SNMPv3 enables <strong>the</strong> following features over SNMPv1 or v2c:●●●●●User au<strong>the</strong>ntication with a user name and password.Communication encryption between <strong>the</strong> Network Management Station (NMS) and <strong>the</strong>SNMP agent at <strong>the</strong> application level.Access control definition for specific MIB items available on <strong>the</strong> SNMP agent.Notification <strong>of</strong> specified network events directed toward specified users.Definition <strong>of</strong> roles using access control, each with unique access permissions andau<strong>the</strong>ntication and encryption requirements.The basic components in SNMPv3 access control are users, groups, and views. In addition,SNMPv3 uses an SNMP engine ID to identify SNMP identity. An SNMP engine ID is assigned toeach MAC address <strong>of</strong> each device in <strong>the</strong> network. Each SNMP engine ID should be unique in<strong>the</strong> network.Issue 3 January 2005 121

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

Saved successfully!

Ooh no, something went wrong!