Configuring Snmp Access - Avaya G250 Administration

Configuring SNMP access

Use the following commands to configure SNMP access:
Note:
You need an Admin privilege level to use the SNMP commands.
Note:
Use the ip snmp enable command to enable SNMP access to the G250/G350. Use the
●
no form of this command to disable SNMP access to the G250/G350.
Use the snmp-server community command to enable SNMPv1 access to the G250/
●
G350. Use the no form of this command to disable SNMPv1 access to the G250/G350.
Use the snmp-server user command to create an SNMPv3 user. Use the no form of
●
this command to remove an SNMPv3 user.
Use the snmp-server group command to create an SNMPv3 group. Use the no form of
●
this command to remove an SNMPv3 group.
Use the snmp-server remote-user command to create an SNMPv3 remote user for
●
SNMP notifications. Use the no form of this command to remove an SNMPv3 remote user
for SNMP notifications.
Use the set snmp community command to create or modify an SNMPv1 community.
●
Use the snmp-server engineID command to configure the SNMPv3 engine ID. Use
●
the no form of this command to configure the engine ID to its default value. The SNMP
engine ID is set automatically by a calculation based on the MAC address of the host
device, but you can change the engine ID using this command. If the SNMP engine ID
changes, all users other than the default user are invalid and must be redefined.
Use the snmp-server view command to add or exclude OIDs from a view. Use the no
●
form of this command to delete an SNMPv3 view.
Use the show snmp view command to display a list of SNMPv3 views.
●
Use the show snmp userToGroup command to display a table of SNMPv3 users and the
●
groups to which they are mapped.
Use the show snmp engineID command to display the SNMPv3 engine ID.
●
Use the show snmp group command to display a list of SNMPv3 groups.
●
Use the show snmp user command to display a list of SNMPv3 users.
●
Use the show snmp command to display a list of SNMP notification receivers.
●
Configuring SNMP access
Issue 1.1 June 2005 211