Snmpv3 configuration example, Network requirements, Configuration procedure – H3C Technologies H3C SecPath F1000-E User Manual
Page 161
11
[Sysname] snmp-agent sys-info contact Mr.Wang-Tel:3306
[Sysname] snmp-agent sys-info location telephone-closet,3rd-floor
# Enable the sending of traps to the NMS with an IP address of 1.1.1.2/24, using public as the
community name.
[Sysname] snmp-agent trap enable
[Sysname] snmp-agent target-host trap address udp-domain 1.1.1.2 params securityname
public v1
Ensure that the SNMP version specified in the snmp-agent target-host command is the same as that
on the NMS; otherwise, the NMS cannot receive any trap.
Step2
Configuring the SNMP NMS
With SNMPv1/v2c, the user needs to specify the read only community, the read and write community,
the timeout time, and number of retries. The user can inquire and configure the device through the NMS.
NOTE:
The configurations on the agent and the NMS must match.
Step3
Verify the configuration
•
After the above configuration, an SNMP connection is established between the NMS and the agent.
The NMS can get and configure the values of some parameters on the agent through MIB nodes.
•
Execute the shutdown or undo shutdown command to an idle interface on the agent, and the
NMS receives the corresponding trap.
SNMPv3 Configuration Example
Network requirements
•
As shown in
, the NMS connects to the agent through an Ethernet.
•
The IP address of the NMS is 1.1.1.2/24.
•
The IP address of the agent is 1.1.1.1/24.
•
The NMS monitors and manages the interface status of the agent using SNMPv3. The agent reports
errors or faults to the NMS. The inbound port for traps on the NMS is 5000.
Figure 5 Network diagram for SNMPv3
Configuration procedure
Step1
Configuring the 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. (The configuration procedure is omitted here)
# Configure the access right: the user can read and write the objects under the interface node with the
OID of 1.3.6.1.2.1.2, and cannot access other MIB objects. Set the user name to managev3user,