Chapter 12. IBM Change and Configuration Management Database integration 437
Deploy Of prague.itsc.austin.ibm.com was SUCCESSFUL !
KUICCN001I Initializing required services...
KUICCN039I Attempting to connect to host prague.itsc.austin.ibm.com ...
KUICCN050I Distributing file 51 of 51 (112.8 MB / 113 MB)...
KUICCN002I Beginning the installation and configuration process...
KUICCN065I The node creation operation was a success.
###############################
################# Results #################
Successful Deployment: 3
UnSuccessful Deployment: 0
--------- SuccessfulAgents ---------
oslo.itsc.austin.ibm.com
paris.itsc.austin.ibm.com
prague.itsc.austin.ibm.com
--------- FailedAgents ---------
################# ******* #################
######################
Exiting Tool
Mon Jul 16 12:47:36 CDT 2007
######################
Users can rerun the tool with the -c option again with the same input file,
because this file is updated by the executing scripts so that successfully
deployed systems are removed from the missing agents report. You may also
want to rerun the script with the -d option again so that the known environment
and reports are fully up-to-date regarding managed system status.
12.2.7 Using the TADDM reporting feature to assess coverage
As an alternative to the scripted scenario described here, you can use the built-in
reporting feature of TADDM to display the monitoring coverage as a generated
report displaying clearly which systems currently are monitored and which are
not.
TADDM Version 5.1 introduced the Monitoring Coverage Report tool designed
specifically for IBM Tivoli Monitoring users to aid the process of assessing
monitoring coverage.
438 IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments
The process for using this tool is similar to the process described previously.
However, instead of running the scripts described in 12.2.5, “Query the TADDM
database” on page 431, this time we ran the TADDM reporting tool to generate
our output.
Follow these steps to use the TADDM reporting tool to generate output:
1. Run through instructions given in 12.2.2, “Using TADDM to discover all
systems on the network” on page 425 through 12.2.4, “Upload generated
XML file to TADDM” on page 430, if you have not already done so.
2. Using a Web browser, connect to the TADDM host machine and launch the
Domain Manager.
3. After logging in, select Monitoring Coverage Report under the Reports tab
in the left-side navigation pane as shown in Figure 12-5. (Note that the report
may take several minutes to create, depending on the size of your
environment.)
Figure 12-5 TADDM Domain Manager
Chapter 12. IBM Change and Configuration Management Database integration 439
The generated report contains the following sections:
򐂰 Table of contents
These are a series of links that will take you to the monitoring coverage
summary of the environment and to each Management Software System
section created for this environment report. There will be a separate section
for each portal server from which data has be acquired.
򐂰 Management Software System (MSS) reports
An MSS is created for each portal server instance you have uploaded data to
TADDM about, that is, each portal server that has had the KfwTmsDla script
run against it. Each MSS provides details about every managed system
known to that monitoring server and monitoring agents available on each
machine, as well as the version number and affinity strings for those agents.
The following information is given for every MSS:
Product Name IBM Tivoli Monitoring Services
Product Version The version of IBM Tivoli Monitoring
MSS Name The name by which TADDM uniquely identifies this
MSS
GUID A generated globally unique ID of the MSS
Access Info A URL pointing to where the user interfaces residing
on the portal server can be accessed
In each MSS in the Monitoring Coverage Report, TADDM will display a list of
the IBM Tivoli Monitoring agents deployed in the environment. The following
information is provided:
Product Code The two-letter IBM Tivoli Monitoring product code
for the agent (for example, NT for Windows, LZ for
Linux)
Managed System Name The IBM Tivoli Monitoring Managed System name
for the agent
Affinity The affinity string code corresponding to the
product code.
Software Version The version of the agent bundle installed.
Source Token A URL to launch the browser-based portal console
to the workspace for the agent
򐂰 Coverage summary section
This is an easy-to-read view of databases and operating systems which are
known to TADDM. Alongside each system is a color-coded indicator of the
monitoring status.

Get IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.