The platform supports resource monitoring using Simple Network Management Protocol (SNMP) Traps. You can:

  • Create an SNMP Trap for each client.
  • Define the resources from which to receive traps.
  • Receive traps from devices.

SNMP trap processing

An SNMP trap indicates a specific condition defined in the Management Information Base (MIB) expressed as variable bindings that include a trap message. The platform processes traps and transforms them into alerts.

OID usage

the SNMP Object Identifier (OID) is an address that identifies devices for tracking device status. The SNMP OID has a form such as: 1.3.6.1.6.3.1.1.5.5.

You can include or exclude OIDs when creating an SNMP Trap monitor.

Use cases

Do not want to receive specific SNMP traps

If you do not want to receive SNMP traps from specific OIDs, create an SNMP trap monitor that excludes the OIDs you do not want to receive the trap from.

Want to receive all SNMP traps

If you want to receive SNMP traps from all resources, create an SNMP trap monitor and select the Receive traps from all devices option.

Want to receive specific SNMP traps

If you want to receive SNMP traps only from specific resources, select the Receive traps from specified devices only option and choose the devices that you want to receive the SNMP traps from.

Want to discard specific SNMP traps

If you want to discard SNMP traps from specific IP addresses, create an SNMP trap monitor and select the Discard traps from specific IP addresses option.

Create an SNMP trap monitor

You can add to the list of SNMP-enabled device traps to monitor:

  1. Go to Setup > Monitoring > SNMP Traps Configuration. This displays a list of any existing SNMP trap monitors, which you can edit, or continue to create a new monitor.

  2. To add a trap monitor and filter, click the + icon.

  3. In Client Name, choose the client.

  4. Enter a unique, descriptive Monitor Name.

  5. Include or exclude specific OIDs you want to monitor by selecting Exclude OID or Include OID and entering the OID.

  6. Click + to continue adding OIDs to be included or excluded.

  7. In the Devices section, choose the option for selectively receiving or discarding traps:

    OptionDescriptionAction
    Receive traps from all devicesTraps are received from all devices.N/A
    Receive traps from specified devices onlyTraps are received from selected devices.From the list of Available Devices, select the device and click the right-chevron (>>) to add the device to the Selected Devices category.
    Receive traps from specified device groups onlyTraps are received from selected device groups.From the list of Available Device Groups, select the device group (or) groups and click the right-chevron (>>) to add the device groups to the Selected Devices groups category.
    Discard traps from specific IP addressesTraps are discarded from devices selected by IP address.For traps that you want to discard, enter a comma-separated list of device IP addresses in the List of devices edit box.
  8. Click Save to apply your changes and display the list of available SNMP trap monitors:

Documentation Information Model

Click on the SNMP trap monitor name to change monitoring settings.

To remove an SNMP trap monitor, select the monitor name and click the delete icon.

To export the SNMP trap monitors list as a CSV or PDF file, click Export and select the format.

Configure SNMP v3 Traps

When you configure a gateway as an SNMP Trap receiver, the device-generated traps are sent to the gateway and processed according to the configuration defined when you created the SNMP trap monitor. For SNMPv2 traps, the gateway can interpret the Trap OIDs because the message is not encrypted. For SNMPv3 traps, the OIDs are encrypted and the gateway needs to know the encryption credentials to decode the traps.

Default SNMPv3 credentials

By default gateway understands and processes traps if the device sends traps using the SNMPv3 credentials shown in the following table. You can configure these credentials in the device.

UserTypeAuthorization ProtocolAuthorization PasswordPrivacy ProtocolPrivacy Password
vistarashatrapuserAuthPrivSHAVist@raAuth@123AES128Vist@raPriv@456
vistaratrapuserAuthPrivMD5Vist@raAuth@123AES128Vist@raPriv@456
vistarauserAuthNoPrivMD5vistara@123nullnull
vistaraAuthPrivMD5VstrMd5AuthAES128VstrAesAuth
vistarashaAuthPrivSHAVstrSHAAuthAES128VstrAESPriv

Add custom SNMPv3 credentials

If you do not want to use the default credentials, you need to define gateway credentials using Base64 encoding.

Format custom credentials

Define custom SNMPv3 credentials using the format:

{securityname}###{authProto}###{authPassPhrase}###{privProto}###{privPassphrase}

Example: user6###MD5###abcdef@123###DES###ghijkl@456

If any of the authProto, authPassPhrase, privProto, or privPassphrase fields are empty or not required use NONE for the field value. For example:

1) All authorization and privilege fields are defined (SNMPv3 AuthPriv):

    snmpusername###MD5###snmpuserauthstring###DES###snmpprivstring

2) All authorization fields are defined and privilege fields are not defined (SNMPv3 AuthNoPriv):

    snmpusername###MD5###snmpuserauthstring###NONE###NONE

3) Authorization and privilege fields are not defined (SNMPv3 NoAuthNoPriv):

    snmpusername###NONE###NONE###NONE###NONE

As another example, a device with the following SNMPv3 credentials:

Username: user6
Auth:  MD5
Authorization password: abcdef@123
Privacy: DES
Privacy password : ghijkl@456

has the following custom credential format:

    user6###MD5###abcdef@123###DES###ghijkl@456

Encode credentials

After formatting the credentials, convert the formatted credentials to Base64 encoding using a tool of your choice. The user6###MD5###abcdef@123###DES###ghijkl@456 formatted credentials are encoded as dXNlcjYjIyNNRDUjIyNhYmNkZWZAMTIzIyMjREVTIyMjZ2hpamtsQDQ1Ng==.

Configure the gateway with the credentials

You can specify multiple SNMPv3 credentials in the same gateway configuration file, each on a new line.

  1. Log in to the gateway using the ruser account.

  2. Open the /opt/gateway/vprobe/conf/snmp_trap_v3_credentials.cfg file in edit mode.

  3. Copy the Base64-encoded credentials and save the file.

  4. Restart the vprobe service:

        service vprobe restart
        

The gateway is ready to process SNMPv3 traps using the configured credentials.