You can omit Step 3, on page 366 if you have already completed the steps documented under the
Configuring SNMPv3, on page 365 task.
Note
SUMMARY STEPS
1.
configure
2.
snmp-server group name {v1 | v2c | v3 {auth | noauth | priv}} [read view] [write view] [notify view]
[access-list-name]
3.
snmp-server user username groupname {v1 | v2c | v3 [auth {md5 | sha} {clear | encrypted}
auth-password [priv des56 {clear | encrypted} priv-password]]} [access-list-name]
4.
snmp-server host address [traps] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port
port] [notification-type]
5.
snmp-server traps [notification-type]
6.
commit
7.
(Optional) show snmp host
DETAILED STEPS
PurposeCommand or Action
configure
Step 1
Configures a new SNMP group or a table that maps SNMP
users to SNMP views.
snmp-server group name {v1 | v2c | v3 {auth | noauth
| priv}} [read view] [write view] [notify view]
[access-list-name]
Step 2
Example:
RP/0/RSP0/CPU0:router(config)# snmp-server group
group_name v3 noauth read view_name1 write
view_name2
Configures a new user to an SNMP group.
snmp-server user username groupname
{v1 | v2c | v3 [auth {md5 | sha} {clear | encrypted}
Step 3
Only one remote host can be assigned to the same
username for SNMP version 3. If you configure the
same username with different remote hosts, only the
last username and remote host combination will be
accepted and will be seen in the show running
configuration. In the case of multiple SNMP
managers, multiple unique usernames are required.
Note
auth-password [priv des56 {clear | encrypted}
priv-password]]} [access-list-name]
Example:
RP/0/RSP0/CPU0:router(config)# snmp-server user
noauthuser group_name v3
Cisco ASR 9000 Series Aggregation Services Router System Management Configuration Guide, Release 5.1.x
367
Implementing SNMP
Configuring SNMP Trap Notifications