PollerDiscoveryAgent

The Oracle Communications Unified Assurance Metric Poller Discovery Agent application uses the configured Polling Policies to create metrics that will be polled from a device and associate thresholds. This is accomplished by using instance information already gathered by other applications and put into the Unified Assurance database.

Below are some examples of processing that can be done so the base metric entries are created for the respective application, but other processing can also be done as well:

• Ping Polling metrics can be created.

• Interface Inbound and Outbound Bandwidth, Errors and Discards metrics can be created depending on the Device Type and Instance Name.

• Response Time metrics can be created depending on the Device Type and Instance Name.

You can run this application as a scheduled job using the Jobs UI.

Poller Discovery Agent Setup

1. Devices must exist in the Device Catalog for this application to be able to function. Devices can be created in several different ways:

   1. Using the Core Device Auto Discovery application.

   2. Using the Manual Discovery UI:

      Configuration -> Device Discovery -> Manual Discovery

   3. Manually entering all values using the Devices UI:

      Configuration -> Device Catalog -> Devices

2. (Optional) The bandwidth metric creation functionality requires that instances have been discovered using the Metric SNMP Network Interface Discovery Agent job (which uses the Metric SNMP Network Interface Discovery Agent application), or via another method.

3. (Optional) The response time metric creation functionality requires that instances have been discovered using the Metric NMAP TCP Port Discovery job (which uses the Metric Pipe Instance Discovery application), or via another method.

4. Using the Polling Policies UI, create the entries that will be used when the application is run, and make changes as needed in the environment:

   Configuration -> Metrics -> Polling Policies

   When configuring policies, there are several defaults that have been configured for ease of use.

   • If setting up Ping Polling, the following can be used:

     • Match

       • Instance

         • Match => LIKE

         • Name => Device

     • Assign

       • Method => NA

       • Poller Template => Default Ping

       • Threshold Group => Default Ping

   • If setting up Network Interface Polling, the following can be used:

     • Match

       • Instance

         • Match => LIKE

         • Name => eth

     • Assign

       • Method => SNMP

       • Poller Template => Default Network Interface

       • Threshold Group => Default Network Interface

   • If setting up Response Time Polling, the following can be used:

     • Match

       • Instance

         • Match => LIKE

         • Name => tcp

     • Assign

       • Method => Transaction

       • Poller Template => Default Response Time

       • Threshold Group => Default Response Time

5. Enable the default Job, unless a specific configuration option is needed.

   Configuration -> Broker Control -> Jobs

Default Scheduled Job

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

See Jobs in Unified Assurance User's Guide for general information about the settings for jobs.

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 default job configuration is to run every Sunday at 12:59:00am.

Administration Details

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

• Package: coreCollection-app

• Package: ./PollerDiscoveryAgent [OPTIONS]

• Options:

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

• Threaded - Multihreaded