H3C Technologies H3C SR8800 - Manual (Page 113)

101
Task Command Remarks
Display the modules that can send
traps and their trap status (enable
or disable).
display snmp-agent trap-list [ | { begin |
exclude | include } regular-expression ]
Available in any view
Display SNMPv3 user information.
display snmp-agent usm-user [ engineid
engineid | username user-name | group
group-name ] * [ | { begin | exclude |
include } regular-expression ]
Available in any view
Display SNMPv1 or SNMPv2c
community information.
display snmp-agent community [ read |
write ] [ | { begin | exclude | include }
regular-expression ]
Available in any view
Display MIB view information.
display snmp-agent mib-view [ exclude |
include | viewname view-name ] [ | { begin |
exclude | include } regular-expression ]
Available in any view
SNMP configuration examples
SNMPv1/SNMPv2c configuration example
Network requirements
As shown in Figure 37 , the NMS (1.1.1.2/24) uses SNMPv1 or SNMPv2c to manage the SNMP agent
(1.1.1.1/24), and the agent automatically sends traps to report events to the NMS.
Figure 37 Network diagram
Configuration procedure
1. Configure the SNMP agent:
# Configure the IP address of the agent as 1.1.1.1/24 and make sure that the agent and the NMS
can reach each other. (Details not shown)
# Specify SNMPv1 and SNMPv2c, and create a read-only community public and a read and write
community private.
system-view
[Sysname] snmp-agent sys-info version v1 v2c
[Sysname] snmp-agent community read public
[Sysname] snmp-agent community write private
# Configure contact and physical location information for the switch.
[Sysname] snmp-agent sys-info contact Mr.Wang-Tel:3306
[Sysname] snmp-agent sys-info location telephone-closet,3rd-floor
# Enable SNMP traps, set the NMS at IP address 1.1.1.2/24 as an SNMP trap destination, and
use public as the community name. (To make sure that the NMS can receive traps, specify the same
SNMP version in the snmp-agent target-host command as that on the NMS.)