IBM Tivoli

Set up an additional poller on the Network Manager server if one poller is not

sufficient to handle your network load.

To set up an additional poller for the monitoring system, you must add a record to

the NCMonitor Poller table, which adds the record to the Monitor Policy editor.

The ncp_poller process creates the record in the poller table and then exits.

The poller is automatically installed when you install Network Manager. Complete

the following steps to register a new instance of the poller and automatically start

the poller.

1. On the system where the poller will run, register the poller by entering the

following command.

ncp_poller -domain domain_name -register -name poller_name

2. Edit the CtrlServicesDOMAIN.cfg file.

a. Locate the entry for the ncp_poller process.

b. Copy the entry and change the -name parameter to match the name you

used to register the poller.

c. Save and close the file.

3. Restart the ncp_ctrl process with the specified domain. The ncp_ctrl process

restarts all running ncp_ processes, including the new poller

Now that the discovery has started, can monitor the progress of the discovery on

the Network Discovery Status page. Use the status in the Discovery Phase field to

determine how the discovery is running:

1. Until the first device is discovered, the discovery phase is Idle/Standby (0).

2. After the first device is discovered, the status changes to Discovering Network

(1). As further devices are discovered, the count in the Processed IP Addresses

field increases.

3. The discovery then runs through the following statuses:

a. Downloading ARP (2)

b. Downloading Connections (3)

c. Correlating Connectivity (-1)

4. After the discovery is completed, the status reverts back to Idle/Standby (0).

You can increase the storage limit for historical performance data. This enables

Performance reports to display a greater amount of historical data.

The storage limit for historical performance data is set by default to a conservative

value of 5 million database rows. You can increase this value; however, this can

lead to a degradation in the performance of the Performance reports.

To increase the storage limit for historical performance data:

1. Locate the following file:

v UNIX $NCHOME/etc/precision/NcPollerSchema.cfg

v Windows %NCHOME%etcprecisionNcPollerSchema.cfg

2. Find the section that contains the following lines:

-- =========================================================================

-- pruning

-- =========================================================================

create table config.pruning

(

MAXPOLLDATAROWS long64 not null

);

--

-- This defines the maximum number of rows allowed in ncpolldata.polldata.

-- Once the number of rows exceeds this limit the older data will be pruned

-- until close to the limit again.

--

-- Increasing this number will result in an increase in the data storage

-- size required for historical data and may also lead to a degradation

-- in the performance of reports using this data.

--

insert into config.pruning (MAXPOLLDATAROWS) values (5000000);

3. Change the value of MAXPOLLDATAROWS..

Please perform the below mentioned steps to disable port 3661 towards security vulnerability on windows servers –

1. Log into the windows server as itmuser

2. Go to Startà Programsà IBM Tivoli Monitoringà Manage Tivoli Monitoring Services, to open ITM Agent Mangement console

3. Verify which all agents are installed as presented in the below screen ie Universal Agent /Monitoring Agent for Windows OS

Note: In all the servers Monitoring Agent for Windows OS is present,universal agent is present in some severs only.

4. Go to the directory C:IBMITMTMAITM6

5. Locate the following two files in this directory-

i)KNTENV à For Windows OS Agent

ii) KUMENVà For Universal Agent ( This file will be present only if universal agent is installed on this server)

6. Open these files in wordpad and enter the below mentioned line at the end of file.

KDC_FAMILIES=https:0

7. Open Registry Editor and expand HKEY_LOCAL_MACHINEàSOFTWAREàCnadleàKNTàVer610àPrimaryàEnvironment

8. On the Right Hand Side window, Right click on KDC_FAMILIES and click on modify.

9. On the value data filed enter the following value.

https:0

Restart the agents running on the sever.

If a poller is not being used to monitor the network, you can remove the poller

from the monitoring system.

To remove a poller from the monitoring system, you must delete its record from

the NCMonitor Poller table, which removes the record from the Monitor Policy

editor. The ncp_poller process attempts to remove the relevant record from the

poller table and then exits.

Complete the following tasks to remove a poller from the monitoring system.

1. From the Network Manager server, issue the following command.

ncp_poller -deregister -domain [domain_name] -name [poller_name]

Note: When you issue this command, the record is deleted from the

NCMONITOR Poller table.

2. From the Monitor Policy Editor, edit each active policy to use a valid poller.