Create a Policy

[This is the context-sensitive link for the Policies tab.]

Prerequisite: Make sure that the Node Group has been created to which you want to apply the Custom Polling Policy. See Define Node Groups for more information about creating Node Groups.

Tip You can also use nnmcustompollerconfig.ovpl to create a Custom Poller configuration. When using nnmcustompollerconfig.ovpl to create Custom Poller Policies, you must first create the Node Group to which you want to gather the additional information. Use nnmcustompollerconfig.ovpl to also enable, disable, configure, list, update, and delete Custom Poller configurations.

You can create one or more policies for a Custom Poller Collection. When configuring a Custom Poller Policy, you define which MIB variable or variables NNMi gathers from members of a specific Node Group.

If you configure more than one Policy per Collection, each Policy must be for a different Node Group.

The Management Mode setting for the node is used to determine whether NNMi collects Custom Poller information for the node regardless of the Management Mode for any associated interfaces. See Management Mode and Custom Poller for example scenarios.

Note These scenarios assume that the Custom Poller MIB Expression is configured to access MIBs from the Interface table.

Management Mode and Custom Poller
Node Management Mode Interface Management Mode Access Node MIBs Access Interface MIBs

Not Managed or Out of Service

Not Managed or Out of Service No No
Not Managed or Out of Service Managed No No
Managed Not Managed or Out of Service Yes Yes

To configure a Custom Poller Policy:

  1. Make your configuration choices (see table).
  2. Click   Save and Close to return to the Custom Poller Configuration form.

    To verify that Custom Poller is working as expected, see the report on the Custom Poller tab in HelpSystem Information.

Custom Poller Policy Attributes

Attribute Description
Name

The Name of the Policy configuration. Alpha-numeric and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted. No spaces are permitted.

Note The Policy name appears in any incidents generated as a result of the Collection. Specify a name that will help you to indicate the types of nodes that are polled with this policy.

Ordering

The order in which the Policy should be considered for nodes that appear in multiple Node Groups and therefore might have conflicting Policies. For example, Ordering is used in the following scenario:

  • Two Policies associated with the same Custom Poller Collection specify ifOperStatus as the MIB Expression.
  • One Policy uses the Routers Node Group and the second Policy uses the Switches Node Group.
  • Each Policy has a different Polling Interval.

In the example scenario above, if a device was in both the Routers Node Group and the Switches Node Group, NNMi would poll the device only one time according to the Policy with the lowest Ordering number.

Collection Click the Lookup icon and select Show Analysis or Open to display more information about the Custom Poller Collection.
Active State

Use the Active State setting to specify which Custom Poller Policies you want to enable or temporarily disable.

The Active State for the associated Custom Collect Policy. Possible values are described below:

Active - Indicates the Custom Poller Policy is in use.

At the time the Active State attribute is set to Active, NNMi applies the Custom Poller Policy to the nodes in the specified Node Group to determine which instances should be polled.

Inactive - Indicates the Custom Poller Policy is not in use. NNMi removes all Polled Instances associated with the Policy.

Suspended - Indicates someone on your team changed this Custom Poller Policy's Active State to Suspended, or the NNMi administrator disabled Custom Poller in the Global Control settings of Configuration workspace, Custom Poller Configuration form. NNMi suspends polling and retains the most recent State value from before the Policy was suspended.

Node Group The Node Group to which the Custom Poller Policy applies.
MIB Filter

The MIB Filter value to be used as the filter for determining the Polling Instances.

When using a MIB Filter, note the following:

  • The MIB Filter value must match the return type of your filter variable. For example, because hrDeviceDescr is of type String, to poll only those MIBs associated with each node that includes the description for a COM (communication) port, COM*  would be the MIB Filter for the example MIB Filter Variable hrDeviceDescr.
  • If your MIB Expression includes a MIB Variable that has multiple instances, you MUST specify a MIB Filter Variable and MIB Filter. For example, because a node can have multiple interfaces, MIB variables containing interface information have repeating instances and require you to use a MIB Filter to specify which interfaces you want NNMi to poll.
  • If your MIB Expression contains more than one MIB Variable with multiple instances, the MIB Filter must apply to each of these MIB Variables.
  • Valid types for MIB Filter Variables include the following:
    • INTEGER
    • UNSIGNED INTEGER
    • GAUGE
    • OCTET STRING
    • IpAddress (IPv4 only)

      Note The MIB Filter Variable must be a MIB variable that has multiple instances (Table Entry MIB) and that can be applied to all of the MIB variables used in the Custom Poller Collection.

Polling Interval The interval in which to perform the Custom Poll.