Trapd

The Oracle Communications Unified Assurance Event Trap Aggregator is a generic SNMP trap message listener that receives messages from devices, parses the results with customizable rules and creates de-duplicated events within Unified Assurance.

A default installation includes a set of rules files for processing a variety of traps from numerous different vendors. The following documentation has information regarding supported devices and other useful information:

• Device Support Overview

• Foundation Rules

Contact Oracle Support if there are devices that are sending traps not processed by the default foundation rules.

You can run this application as a service using the Services UI.

Trap Aggregator Setup

1. Review the logic in the rules files referenced in the configuration to see the processing that will be done when traps are received:

   • LoadRules will be run during application startup to load data that might be needed during processing.

   • IncludeRules will be read during application startup to load additional files that might be called during processing.

   • BaseRules will be run for each trap that is received.

   Update the logic as needed.

2. Enable the default Service, unless you need a specific configuration option.

   See Services in Unified Assurance User's Guide for information about the Services UI.

3. Configure devices to send SNMP trap messages to the server where the Event Trap Aggregator has been started.

SNMPv3 Setup

You must create an SNMP access profile with the same credentials configured on the sending devices if the security level is authNoPriv or authPriv. You can set up multiple SNMP access profiles to match different credential sets.

1. Go to the SNMP Access UI:

   From the Configuration menu, select Device Discovery, then select SNMP Access. See SNMP Access for information about this UI.

2. For each profile needed:

   • Security Level is always required

   • Username is always required

   • Authentication Protocol and Authentication Password are required if Security Level set to authNoPriv or authPriv

   • Privacy Protocol and Privacy Password are required if Security Level set to authPriv

Default Service

The following table shows the settings for the default service. Actual values are in bold, descriptions of values are in plaintext.

See Services in Unified Assurance User's Guide for general information about the settings for services.

See Using Application Primary/Backup Failover for more information about the different failover types.

Default Configuration

The following table shows the default configurations for the application. Actual values are in bold, descriptions of values are in plaintext.

Best Practices

The following list shows the best practices for working with this application:

• Depending on the server specifications and loads, you may need to increase the number of threads that the aggregator uses. However, too many threads can have negative effects.

• By default, devices send SNMP trap Messages on UDP port 162. If messages are not reaching the Unified Assurance system, check firewall settings in the network.

• SNMPv1 and SNMPv2 traps with any community string, and SNMPv3 traps with any username and security level of noAuthNoPriv are automatically accepted.

• SNMPv3 traps require an SNMP access profile to exist with matching credentials if the security level is authNoPriv or authPriv. You may see the following errors in the log if something is misconfigured:

  • Missing profile with matching username: Error finding username in local configuration datastore [unknownSecurityName]: ...

  • Mismatch with authentication protocol and/or password: Error authenticating message [authenticationFailure]: ...

  • Mismatch with privacy protocol and/or password: Error decrypting PDU [decryptionError]: ...

  See SNMP Access in Unified Assurance User's Guide for information about the UI for adding SNMP access profiles and Creating SNMP Access Profiles for an example.

• If you have multiple SNMPv3 profiles with the same username (not typical), you must provide specific engine IDs to distinguish unique credentials.

• Using different SNMPv3 profiles for polling and trap collection require a non-engine ID profile to have a higher priority (lower order number).

• Reloading the configuration from the Services UI will update SNMP access profiles.

Rules

This aggregator uses the Unified Assurance standard rules architecture in Perl syntax. For information about creating rules, see the following in Unified Assurance Developer's Guide:

• Core for information about core rules functions.

• Events for information about Event rules functions.

• Application Logging

For examples of enabling the Trap Aggregator, and explanation of how rules are applied, see Events Examples.

Tokens

The aggregator exposes the following tokens for rules processing.

$CustomHash->{SubObject} = &share({});

Administration Details

The following list shows the technical details you will need for advanced administration of the application:

• Package: coreCollection-app

• Package: ./Trapd [OPTIONS]

• Options:

   -c, --AppConfigID N   Application Config ID (Service, Job, or Request ID)
   -?, -h, --Help        Print usage and exit
  

• Threaded: Multithreaded