Users Guide
NOTE: For v1 / v2c trap conguration, if the community-string is not dened using the snmp-
server community command prior to using this command, the default form of the snmp-
server community
command automatically is congured with the community-name the same
as specied in the snmp-server host command.
Conguring Informs
To send an inform, use the following steps:
1. Congure a remote engine ID.
2. Congure a remote user.
3. Congure a group for this user with access rights.
4. Enable traps.
5. Congure a host to receive informs.
Related Commands
snmp-server enables— enables SNMP traps.
snmp-server user
Congure a new user to an SNMP group.
Syntax
snmp-server user name {group_name [access access-list-name | ipv6 access-
list-name | access-list-name ipv6 access-list-name]
To remove a user from the SNMP group, use the no snmp-server user name {group_name
[access access-list-name | ipv6 access-list-name | access-list-name ipv6
access-list-name] command.
Parameters
name Enter the name of the user (not to exceed 20 characters), on the host that
connects to the agent.
group_name Enter a text string (up to 20 characters long) as the name of the group. The
following groups are created for mapping to read/write community/security-names
(defaults):
• v1v2creadu — maps to a community with ro permissions.
• 1v2cwriteu — maps to a community rw permissions.
access access-list-
name
(Optional) Enter the standard IPv4 access list name (a string up to 16 characters
long).
ipv6 access-list-
name
(Optional) Enter the keyword ipv6 then the IPv6 access list name (a string up to
16 characters long).
access-list-name
ipv6 access-list-
name
(Optional) Enter both an IPv4 and IPv6 access list name.
Defaults As above.
Command Modes CONFIGURATION
Supported Modes Programmable-Mux (PMUX)
Simple Network Management Protocol (SNMP) and Syslog
355