Snmpv1 And Snmpv2C Traps; Snmp Trap Receivers - HP Aruba JL253A Management And Configuration Manual

If you want to use SNMPv3 notifications (including traps), you must also configure an SNMPv3 management
station. Follow the required configuration procedure in Configuring SNMPv3 notifications (CLI) on page
199.
2. To reconfigure any of the SNMP notifications that are enabled by default to be sent to a management station
(trap receiver), see Enabling Link-Change Traps (CLI) on page 204.
3. (Optional) See the following sections to configure optional SNMP notification features and verify the current
configuration:
• Configuring the source IP address for SNMP notifications (CLI) on page 205
• Viewing SNMP notification configuration (CLI) on page 207

SNMPv1 and SNMPv2c Traps

The switches support the following functionality from earlier SNMP versions (SNMPv1 and SNMPv2c):
• Trap receivers: A trap receiver is a management station to which the switch sends SNMP traps and
(optionally) event log messages sent from the switch. From the CLI you can configure up to ten SNMP trap
receivers to receive SNMP traps from the switch.
• Default Traps: A switch automatically sends default traps to trap receivers using the configured community
name. You have to configure and supply the community name to use in the trap-receiver config, there is no
default. Use the snmp-server host <IP_ADDRESS> community "<COMMUNITY_NAME>" command to
configure a community name and the snmp-server host <IP_ADDRESS> community
"<COMMUNITY_NAME>" trap-level [all | critical | not-info | debug | none] command
to set the level of traps to send to the community.
• Thresholds: A switch automatically sends all messages created when a system threshold is reached to the
network management station that configured the threshold, regardless of the trap receiver configuration.

SNMP trap receivers

Use the snmp-server host command to configure a trap receiver that can receive SNMPv1 and SNMPv2c
traps, and (optionally) Event Log messages. When you configure a trap receiver, you specify its community
membership, management station IP address, and (optionally) the type of Event Log messages to be sent.
If you specify a community name that does not exist—that is, has not yet been configured on the switch—the
switch still accepts the trap receiver assignment. However, no traps are sent to that trap receiver until the
community to which it belongs has been configured on the switch.
NOTE:
To replace one community name with another for the same IP address, you must first enter the
no snmp-server host <community-name> {< ipv4-address | ipv6-address >}
command to delete the unwanted community name. Otherwise, if you add a new community name
with an IP address that is already used with a different community name, two valid community name
entries are created for the same management station.
If you do not specify the event level ([none|all|not-info|critical|debug]), the switch does
not send Event Log messages as traps. However, "well-known" traps and threshold traps (if
configured) are still sent.
Chapter 7 Configuring for Network Management Applications 195