Configuring Netcool Configuration Manager

After installing Netcool Configuration Manager, you must perform the standard configuration tasks that are required to set up the product, and then configure the product to support the integration. At a minimum, you must set up a Worker Server resource, create an authentication set, change the server pool sizes, set up realms, import or build policies, and grant permissions to modify compliance policies.

You will require the IP address and port of the probe host computer in order to configure communication between Netcool Configuration Manager and the probe, so have these details at hand.

Before you begin

CAUTION:
When configuring Netcool Configuration Manager trap properties, ensure you guard against flooding Network Manager and Tivoli Netcool/OMNIbus with events.

To plan for the event volume that will be sent to your Tivoli Netcool/OMNIbus ObjectServer, be aware that one policy issued against one device generates one event. Therefore it is possible to generate a large number of events in a relatively short period of time if you are operating against a large number of devices.

If you have a large environment, consider filtering to just those events that are of most importance to you. Consult the Tivoli Netcool/OMNIbus documentation for further information.

About this task

Compliance policies and processes
At a minimum you must import or build network compliance policies, and grant permissions to modify policies, and to create, modify, schedule and execute processes.
Additionally, you must configure the product to support the integration by setting up a process and adding the relevant policies that are required for achieving operational, security, and regulatory compliance in the network. Ensure that this process is enabled for automatic validations so that the policies are run against a device when it changes, and an event is generated to indicate whether the device is in compliance.
Device configuration
You must also set up a Worker Server resource, create an authentication set, and change the server pool sizes.
Additionally, you must configure SNMP trap settings, and enable event generation for the different event types. To do so, set the following properties in the Systems Manager's System Properties window.
Table 1. Netcool Configuration Manager system properties
Property Description
Instance Identifier Specify a unique name for this particular instance of Netcool Configuration Manager.
Network Resource Event Registration Set this value to True to enable network resource events to be generated and written to the database. The default is True.
Resource Event Registration Set this value to True to enable resource events to be generated and written to the database. The default is True.
Work Event Registration Set this value to True to enable work events to be generated and written to the database. The default is True.
Compliance Policy Event Registration Set this value to True to enable compliance policy events to be generated and written to the database. The default is True.
SNMP Trap Recipients Use this property to configure Netcool Configuration Manager to forward events that are generated from SNMP traps to the SNMP Probe. (This property setting also enables the traps to be raised.)

Set the value of this property by using the following format:

IP_address:port

where IP_address is the IP address of the computer on which the SNMP Probe is installed, and port is the port on which the probe is listening.

You can use a comma-separated list to specify multiple probe hosts to which all events should be forwarded, as follows:

IP_address1:port1,IP_address2:port2,...

Important: You must set the SNMP trap recipients before performing device synchronization, otherwise the right-click functionality in Network Manager and Tivoli Netcool/OMNIbus will be restricted.
SNMP Trap Flood Prevention Specify the minimum time in milliseconds (ms) the system will wait after sending a trap before sending another.
SNMP Trap Retries Specify the maximum number of times that the system attempts to resend unacknowledged traps.
SNMP Trap Timeout Specify the maximum time in milliseconds that the system waits for a trap acknowledgement before resending.

You perform a number of Netcool Configuration Manager configuration tasks after the TIP portal has been installed, and the tarball applied. See the related links for more information.