User guide

Chapter 11. Troubleshooting Alcatel-Lucent 5620 SAM

LogToFile Technology Pack

Troubleshooting tips for issues related to Alcatel-Lucent 5620 SAM LogToFile

Technology Pack and its related components.

Specifying parameter values

Several of the tips to tell you to make sure that the correct values were specified

for parameters in the deployed topology.

You specify the values for these parameters depending on the Tivoli Netcool

Performance Manager platform.

Tivoli Netcool Performance Manager 1.3.2

These parameters are supplied in the pack XSD file. You used the Topology Editor

to specify a value for these parameters as part of adding a UBA Bulk Collector and

associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more

information, see Adding a UBA Bulk Collector in the IBM Tivoli Netcool Performance

Manager: Installation Guide.

Inventory issues

If you do not see the expected inventory in your Tivoli Netcool Performance

Manager instance, use this information. Complete the steps in each subsection, to

verify that you have configured your instance correctly.

Metric data collection issues

If you do not see the expected metrics in your Tivoli Netcool Performance

Manager instance, use this information. Complete the steps in each subsection, to

verify that you have configured your instance correctly.

The following sections provide an overview of metric data, and describe

troubleshooting tips for issues related to the metric data collection:

Overview of metric data

The SAM server supports the following types of metric data:

Polled

Polled metric data is collected by the SAM server from the routers using

SNMP. To collect this data, MIBs must be enabled on the SAM server, and

polling periods must be set. For more information about the MIBs that are

needed, see “Enable the MIBs for the SAM statistics classes” on page 59.

Exception to the Rule: The exception is the HwEnvironmentTemperature files.

These files are in effect inventory files in which the temperature properties

are read in as metrics. For a variety of reasons related to this data not

being real metrics, the temperature data is only available for a subelement

under the following conditions:

v The CPU utilization metric for that subelement is available.