DeviceAutoDiscovery

The Oracle Communications Unified Assurance Core Device Auto Discovery application uses the defined inclusion and exclusion profiles to find and record new devices on the network. After a device has been discovered and added to the database, the device information is sent to rules for additional custom processing that may be needed. All initially discovered devices appear in the Devices UI with a Status of Verified.

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

Device Auto Discovery Setup

1. Add inclusion profiles or modify existing inclusion profiles:

   Configuration -> Device Discovery -> Inclusion Profiles

2. (Optional) Add inclusion profiles or modify existing inclusion profiles:

   Configuration -> Device Discovery -> Exclusion Profiles

3. 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 runs at 11:59 pm every Friday.

• By default batches are sized by dividing the total number of items to be discovered over the number of threads. As the number of items increases, it is best practice to limit this batch size to prevent certain denial of service limitations on your network.

• When batching multiple devices per thread (default), there is potential based on hardware for processing overhead to be included in the Latency metric because pings are requested asynchronously per batch. This overhead can be reduced by limiting the batch size using MaxBatchSize to reduce the number of devices pinged at once by the threads, but this will cause a longer poll cycle.

Rules

This application 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.

• Application Logging

Tokens

The application 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: ./DeviceAutoDiscovery [OPTIONS]

• Options:

   -c, --AppConfigID N   Application Config ID (Service, Job, or Request ID)
   -d, --Device S        Comma separated list of devices to manually discover
   -?, -h, --Help        Print usage and exit
  

• Threaded: Multithreaded