Table of Contents
Advertisement
Implementing SNMP
Configuring SNMP Trap Notifications
This task explains how to configure the router to send SNMP trap notifications.
You can omit
Note
Configuring SNMPv3, on page 69
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
Command or Action
Step 1
configure
Step 2
snmp-server group name {v1 | v2c | v3 {auth | noauth
| priv}} [read view] [write view] [notify view]
[access-list-name]
Example:
RP/0/RP0/CPU0:router(config)# snmp-server group
group_name v3 noauth read view_name1 write
view_name2
Step 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]
Example:
RP/0/RP0/CPU0:router(config)# snmp-server user
noauthuser group_name v3
Step 3, on page 70
if you have already completed the steps documented under the
task.
System Management Configuration Guide for the Cisco NCS 6000 Series Router, Release 5.0.x
Configuring SNMP Trap Notifications
Purpose
Configures a new SNMP group or a table that maps SNMP
users to SNMP views.
Configures a new user to an SNMP group.
Only one remote host can be assigned to the same
Note
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.
71
Advertisement
Table of Contents
