Snmp Protocol Versions; Recommended Configuration Procedure - HP 830 Series Configuration Manual

Poe+ unified wired-wlan switch switching engine web-based
Hide thumbs Also See for HP 830 Series:
Table of Contents

Advertisement

Set—The NMS modifies the value of an object node in an agent MIB.
Notifications—Includes traps and informs. SNMP agent sends traps or informs to report events to
the NMS. The difference between these two types of notification is that informs require
acknowledgement but traps do not. The device supports only traps.

SNMP protocol versions

HP devices support SNMPv1, SNMPv2c, and SNMPv3. An NMS and an SNMP agent must use the same
SNMP version to communicate with each other.
SNMPv1—Uses community names for authentication. To access an SNMP agent, an NMS must use
the same community name as the one that is set on the SNMP agent. If the community name used
by the NMS is different from that set on the agent, the NMS cannot establish an SNMP session to
access the agent or receive traps from the agent.
SNMPv2c—Uses community names for authentication. SNMPv2c is compatible with SNMPv1 but
supports more operation modes, data types, and error codes.
SNMPv3—Uses a user-based security model (USM) to secure SNMP communication. You can
configure authentication and privacy mechanisms to authenticate and encrypt SNMP packets for
integrity, authenticity, and confidentiality.

Recommended configuration procedure

SNMPv3 differs from SNMPv1 and SNMPv2c in many ways. Their configuration procedures are
described in separate sections.
Table 31 Configuring SNMPv1 or SNMPv2c
Step
1.
Enabling SNMP agent
2.
Configuring an SNMP view
3.
Configuring an SNMP community
4.
Configuring SNMP trap function
5.
Displaying SNMP packet statistics
Remarks
Required.
The SNMP agent function is disabled by default.
IMPORTANT:
If SNMP agent is disabled, all SNMP agent-related configurations are
removed.
Optional.
After creating SNMP views, you can specify an SNMP view for an
SNMP community to limit the MIB objects that can be accessed by the
SNMP community.
Required.
Optional.
Allows you to configure that the agent can send SNMP traps to the
NMS, and configure information about the target host (usually the
NMS) of the SNMP traps.
The SNMP agent sends traps to inform the NMS of important events,
such as a reboot.
By default, an agent is allowed to send SNMP traps to the NMS.
Optional.
99

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents