Costes totales

This chapter explains how to manage the Tivoli Netcool Performance Manager SNMP Inventory, and is made up of the following topics:

Overview

This chapter describes the monitoring actions that have to be performed regularly to keep Tivoli Netcool Performance Manager's SNMP Inventory process performing optimally.

If your SNMP Inventory is triggered every day, we recommend performing these monitoring actions at least once a week.

If your SNMP Inventory is triggered several times a day (for example, every six hours), we recommend performing these monitoring actions at least once a day.

Routine SNMP Inventory Management Tasks

The following sections discuss routine SNMP Inventory management tasks:

Finding Elements and Sub-elements About to Reach Their Retry Limit

When elements and sub-elements reach their retry limit, they are retired from the Inventory, which means that Tivoli Netcool Performance Manager stops collecting on them and removes them from some groups.

Note: The retry limit is set and managed in the

DataMart->Inventory Tool->Edit Profile->Synchronization Wizard.

The default is three retries and a resource that is older than seven days, as shown in the following figure. BOTH limits must be met in order for a sub-element to be retired.

Topic Page

Overview 33

Routine SNMP Inventory Management Tasks 33

To find elements and sub-elements about to reach their retry limit, do the following:

1. Log in as pvuser (or the user name that you specified during installation) on the system where DataMart is

installed.

2. Enter the following commands, noting that $PVMHOME is defined as /opt/datamart by default.

The commands look for elements and sub-elements approaching their retry counter, using greater than 2 (>2) for the retry count and 3 (the default) to specify the age of the resource.

— Elements

$PVMHOME/bin/resmgr/-noHead -export elt -colNames "dbIndex origin name profil state missing" -filterRule "%(elt.profil) not like '%bulk%' AND %(state)='on' AND

%(missing) >2"

The resmgr command returns output like the following:

200000004|_|inventory|_|skywalker.quallaby.com-1|_|lowell|_|on|_|8|_| 200000024|_|inventory|_|ducks.quallaby.com-1|_|lowell|_|on|_|4|_| 200001383|_|inventory|_|192.168.82.8-1|_|lowell|_|on|_|7|_|

— Sub-elements

$PVMHOME/bin/resmgr -noHead -export se -colNames "dbIndex origin name label

elt.profil invariant state missing" -filterRule "%(elt.profil) not like '%bulk%' AND %(state)='on' AND %(missing) >2"

The resmgr command returns output like the following:

200000029|_|inventory|_|bbpser170-1_processID<12074>|_|bbpser170-1_"bbpser170" "AMGR_visual" pid 12074 |_|unix|_|AMGR_visual|_|on|_|3|_|

Note: For more information on the resmgr command, see the Tivoli Netcool Performance Manager Command Line Interface Guide.

1. Fix the connectivity problem so that Tivoli Netcool Performance Manager can discover the element or sub- element about to be retired.

2. Check to see if there is a problem with the SNMP community name that is preventing Tivoli Netcool Performance Manager from taking to the resource.

3. Increase either the retry count or the resource age setting (or both) in the Synchronization Wizard.

Chapter 3: SNMP Inventory Management

Finding Elements and Sub-elements That Have Been Retired

As explained in Finding Elements and Sub-elements About to Reach Their Retry Limit on page 33, when an element or sub-element exceeds its Inventory Retry and Inventory Timeout limits, it is changed to the “off ” state and retired from the Inventory.

To detect elements and sub-elements that have been retired, do the following:

1. Log in as pvuser (or the user name that you specified during installation) on the system where DataMart is

installed.

2. Enter the following commands, noting that $PVMHOME is defined as /opt/datamart by default.

The commands look for elements and sub-elements that have been move to the “off ” state. — Elements

$PVMHOME/bin/resmgr -noHead -export elt -colNames "dbIndex origin name profil state missing" -filter "state(off)"

The resmgr command returns output like the following:

200028920|_|inventory|_|Delete_200028920_192.168.1.5-1|_|lowell|_|off|_|72|_|

— Sub-elements

$PVMHOME/bin/resmgr -noHead -export se -colNames "dbIndex origin name state missing" -filter "state(off)"

The resmgr command returns output like the following:

200000724|_|inventory|_|Delete_200000724_kafka.com-2_If<1>|_|off|_|7|_| 200000880|_|inventory|_|Delete_200000880_192.168.1.84-2_<NULL>|_|off|_|8|_| 200000916|_|inventory|_|Delete_200000916_192.168.1.84-2_If<1>|_|off|_|8|_| 200001205|_|inventory|_|Delete_200001205_192.168.1.84-2_If<2>|_|off|_|8|_|

Note: For more information on the resmgr command, see the Tivoli Netcool Performance Manager Command Line Interface Guide.

• Group them in a special group (for example, the retired group) and periodically check its content. • Delete them using the Resource Editor if you confirm that they have been permanently removed from the

network.

ACTION: If the elements or sub-elements are in the “off ” state, then they will be retired. If they are in the “on” state, but are approaching both their age limit and retry limit, they are about to be retired. The commands in this section search for elements and sub-elements that are in the “on” state, but will soon be retired.

To address this problem, do the following:

ACTION: Micromuse recommends the following Best Practices when dealing with retired elements and sub- elements:

Note: This does not remove their statistics from the database. It just marks them "deleted" in the database, so they will not overload the "retired" group, which will be kept at a manageable size.

Where to Go From Here

For information on troubleshooting tasks to perform after a new SNMP Inventory has been run, see Chapter 2, SNMP Inventory Troubleshooting on page 5.

Chapter 3: SNMP Inventory Management