Link Search Menu Expand Document

SNMP Template

EdgeConnect appliances support Management Information Base (MIB-II) as described in RFC 1213 for cold start traps, warm start traps, and EdgeConnect private MIBs. Appliances issue an SNMP trap during reset when loading a new image, recovering from a crash, or rebooting.

An appliance sends a trap every time an alarm is raised or cleared. Traps contain additional information about alarms, including severity, sequence number, a text-based description of the alarm, and the time the alarm was created. For more information, you can download a .zip archive containing supported MIBs here.

Use this page to configure the appliance’s SNMP agent and trap receivers.

  1. Select the Enable SNMP check box to activate configuration options for SNMP v1/v2, SNMP v3, and Trap Receivers details.

  2. If you select the Enable SNMP Traps check box, the SNMP agent on the appliance sends traps to configured receivers.

  3. Use the Default Trap Community field to specify the string the trap receiver uses to accept traps being sent to it. The default value is public. You can modify this value.

SNMP v1/v2

Configure the following fields for SNMP v1 and v2c.

FieldDescription
Enable SNMPAllows the SNMP agent on the appliance to send traps to configured receivers.
Read-Only CommunityThe SNMP application needs to present this text string (secret) to poll the appliance’s SNMP agent. The default value is public. You can modify this value.

SNMP v3

For additional security, configure SNMP v3 if you want to authenticate without using clear text. To add an SNMP v3 user, click Add above the SNMP v3 table and configure the following properties:

FieldDescription
EnabledSelect this check box to enable the selected user. Clear this check box to disable the user and maintain the configuration.
UsernameEnter the username to identify the SNMP v3 user.
Authentication TypeSelect the authentication type to use for SNMP requests from the user.

NOTE: Authentication type is required and SHA-1 is the only supported algorithm.
Authentication PasswordEnter a password that the SNMP agent can use to authenticate requests sent by the user.

NOTE: The password must be at least 20 characters long.
Privacy TypeSelect the encryption type to use for encrypting requests from the SNMP user.

NOTE: Encryption is required, and AES-128 is the only supported algorithm.
Privacy PasswordEnter a password (key) to use for encrypting requests sent by the user.

NOTE: The password must be at least 20 characters long.

NOTE: To delete an SNMP v3 user, click the X to the right of the entry in the table.

Trap Receivers

To configure a trap receiver, click Add above the Trap Receivers table and configure the following properties:

NOTE: You can configure up to three trap receivers per appliance.

FieldDescription
HostIP address of the host where traps should be sent.
VersionSelect the SNMP version of the trap receiver.
Community/UsernameFor v1 and v2c, enter the community string the receiver should use to accept traps. If left blank, the default community string (public) is used. If a different community string is configured on the trap receiver, enter it here.

For v3, specify the SNMP v3 user that is sending traps to the receiver.
EnabledSelect this check box to enable the receiver. Clear this check box to disable the receiver and maintain the configuration.

NOTE: To delete a receiver, click the X to the right of the entry in the table.


Back to top

© Copyright 2022 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.