Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerFlex Appliance with PowerFlex 3.x Administration Guide

PDF

Configure SNMP trap forwarding

To configure SNMP trap forwarding, specify the access credentials for the SNMP version you are using and then add the remote server as a trap destination.

About this task

PowerFlex Manager supports different SNMP versions, depending on the communication path and function. The following table summarizes the functions and supported SNMP versions:
Function SNMP version
PowerFlex Manager receives traps from all devices, including iDRAC v2
PowerFlex Manager receives traps from iDRAC devices only v3
PowerFlex Manager forwards traps to the network management system v2, v3
NOTE:SNMPv1 is supported wherever SNMPv2 is supported.

PowerFlex Manager can receive an SNMPv2 trap and forward it as an SNMPv3 trap.

SNMP trap forwarding configuration supports multiple forwarding destinations. If you provide more than one destination, all traps coming from all devices are forwarded to all configured destinations in the appropriate format.

PowerFlex Manager stores up to 5 GB of SNMP alerts. Once this threshold is exceeded, PowerFlex Manager automatically purges the oldest data to free up space.

For SNMPv2 traps to be sent from a device to PowerFlex Manager, you must provide PowerFlex Manager with the community strings on which the devices are sending the traps. If during resource discovery you selected to have PowerFlex Manager automatically configure iDRAC nodes to send alerts to PowerFlex Manager, you must enter the community string used in that credential here.

For a network management system to receive SNMPv2 traps from PowerFlex Manager, you must provide the community strings to the network management system. This configuration happens outside of PowerFlex Manager.

For a network management system to receive SNMPv3 traps from PowerFlex Manager, you must provide the PowerFlex Manager engine ID, user details, and security level to the network management system. This configuration happens outside of PowerFlex Manager.

Prerequisites

PowerFlex Manager and the network management system use access credentials with different security levels to establish two-way communication. Review the access credentials that you need for each supported version of SNMP. Determine the security level for each access credential and whether the credential supports encryption.

To configure SNMP communication, you need the access credentials and trap targets for SNMP, as shown in the following table:
If adding... You must know...
SNMPv2 Community strings by which traps are received and forwarded
SNMPv3 User and security settings

Steps

  1. Log in to PowerFlex Manager.
  2. On the menu bar, click Settings, and click Virtual Appliance Management.
  3. On the Virtual Appliance Management page, in the SNMP Trap Configuration section, click Edit.
  4. To configure trap forwarding as SNMPv2, click Add community string. In the Community String box, provide the community string by which PowerFlex Manager receives traps from devices and by which it forwards traps to destinations.

    You can add more than one community string. For example, add more than one if the community string by which PowerFlex Manager receives traps differs from the community string by which it forwards traps to a remote destination.

    NOTE:An SNMPv2 community string that is configured in the credentials during discovery of the iDRAC or through management is also displayed here. You can create a new community string or use the existing one.
  5. To configure trap forwarding as SNMPv3, click Add User. Enter the Username, which identifies the ID where traps are forwarded on the network management system. The username must be at most 16 characters. Select a Security Level:
    Security Level Details Description authPassword privPassword
    Minimal noAuthNoPriv No authentication and no encryption Not required Not required
    Moderate authNoPriv Messages are authenticated but not encrypted

    (MD5 at least 8 characters)

    Required Not required
    Maximum authPriv Messages are authenticated and encrypted

    (MD5 and DES both at least 8 characters)

    Required Required

    Note the current engine ID (automatically populated), username, and security details. Provide this information to the remote network management system so it can receive traps from PowerFlex Manager.

    You can add more than one user.

  6. In the Trap Forwarding section, click Add Trap Destination to add the forwarding details.
    1. In the Target Address (IP) box, enter the IP address of the network management system to which PowerFlex Manager forwards SNMP traps.
    2. Provide the Port for the network management system destination. The SNMP Trap Port is 162.
    3. Select the SNMP Version for which you are providing destination details.
    4. In the Community String/User box, enter either the community string or username, depending on whether you are configuring an SNMPv2 or SNMPv3 destination. For SNMPv2, if there is more than one community string, select the appropriate community string for the particular trap destination. For SNMPv3, if there is more than one user-defined, select the appropriate user for the particular trap destination.
  7. Click Save.

    The Virtual Appliance Management page displays the configured details as shown below:

    Trap Forwarding  <destination-ip>(SNMP v2 community string or SNMP v3 user)

    NOTE:To configure nodes with PowerFlex Manager SNMP changes, go to Settings > Virtual Appliance Management, and click Configure nodes for alert connector.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\