Snmpv3 Configuration Example - HP 6125XLG Configuration Manual

[Agent] snmp-agent community write private
# Configure contact and physical location information for the agent.
[Agent] snmp-agent sys-info contact Mr.Wang-Tel:3306
[Agent] snmp-agent sys-info location telephone-closet,3rd-floor
# Enable SNMP notifications, set the NMS at 1.1.1.2 as an SNMP trap destination, and use
public as the community name. (To make sure the NMS can receive traps, specify the same SNMP
version in the snmp-agent target-host command as is configured on the NMS.)
[Agent] snmp-agent trap enable
[Agent] snmp-agent target-host trap address udp-domain 1.1.1.2 params securityname
public v1
2. Configure the SNMP NMS:
Specify SNMPv1.
Create the read-only community public, and create the read and write community private.
Configure timeout time and maximum number of retries as needed.
For more information about configuring the NMS, see the NMS manual.
NOTE:
The SNMP settings on the agent and the NMS must match.
3. Verify the configuration:
# Try to get the MTU value of NULL0 interface from the agent. The attempt succeeds.
Send request to 1.1.1.1/161 ...
Protocol version: SNMPv1
Operation: Get
Request binding:
1: 1.3.6.1.2.1.2.2.1.4.135471
Response binding:
1: Oid=ifMtu.135471 Syntax=INT Value=1500
Get finished
# Use a wrong community name to get the value of a MIB node on the agent. You can see an
authentication failure trap on the NMS.
1.1.1.1/2934 V1 Trap = authenticationFailure
SNMP Version = V1
Community = public
Command = Trap
Enterprise = 1.3.6.1.4.1.43.1.16.4.3.50
GenericID = 4
SpecificID = 0
Time Stamp = 8:35:25.68

SNMPv3 configuration example

Network requirements
As shown in
of the agent (1.1.1.1/24). The agent automatically sends notifications to report events to the NMS. The
default UDP port 162 is used for SNMP notifications.
Figure 25, the NMS (1.1.1.2/24) uses SNMPv3 to monitor and manage the interface status
78