ITM Agent Insights: Agent systems missing from COGNOS based TCR Operational Reports
DougDoering 120000E6GG Visits (4993)
In the TCR interface, under "Work With Reports" section, the "Resource Section" will contain the list of systems that the selected report is able to be run against under the "Servers" section. If this list is blank, or missing a desired system, this indicates that there is no entry for this system in the ManagedSystem table or the ManagedSystem table is absent in the Tivoli Data Warehouse (TDW) database.
COGNOS based TCR reports run SQL queries against the contents of the TDW database, and rely on entries in the ManagedSystem table which is populated by running TCR for OS Agent Report script / procedure against historical data that has been gathered previously from individual IBM Tivoli Monitoring Agent systems and summarized by the Summarization and Pruning Agent (SY), or by configuring the SY agent to create / maintain the dimension resource tables:
Creating and maintaining the dimension tables
The first step should be to verify the overall monitoring environment:
2) OS platform, hostname, and ITM components installed on the HUB TEMS (and Remote TEMS if using them).
3) What interface is used for the TEP? Is it the browser TEP client? Or the desktop TEP client?
4) OS platform, hostname, and ITM components installed on the system where the Warehouse Proxy Agent (WPA) is installed / running (HD component)
5) OS platform, hostname, and ITM components installed on the system where the Summarization and Pruning Agent (SPA) is installed / running (SY component)
6) OS platform, hostname, ITM components installed on the system where the Tivoli Data Warehouse (TDW) is installed.
7) OS platform, hostname, and ITM components installed on the agent system(s) missing from the list of servers a report can be run against.
If some agent systems are displayed, while others are missing, provide the output from "pdcollect" utility on both a working endpoint and a failing endpoint for comparison.
After verifying the ITM environment, verify the contents of the TDW database to determine if the ManagedSystem table exists, and if it is populated with data using SQL select statements.
select * from MANAGEDSYSTEM
The entries in the MANAGEDSYSTEM table are inserted when running the POPULATE_OSAGENTS stored procedure / script, which relies on historical data for platform specifiic attribute groups for Unix / Linux / Windows OS
If there are no values in the MANAGEDSYSTEM table of the TDW database, check the contents of the UNIX_IP_Address_D , Linux_IP_Address_D, and NT_C
If there are no <attribute_group>_D tables, review the Summarization options to confirm that historical data summarization is configured for Daily summarization.
This can be seen in the TEP in the Historical Configuration GUI. Example showing that Daily summarization has NOT been configured for Unix_IP_Address attribute group:
If there are no entries in the <attribute_group>_D tables but the tables exist, check the base tables that the summarized data would be created from to confirm if there are detailed entries for the UNIX_IP_Address, Linux_IP_Address, and NT_C
The historical collection configuration is needed to confirm where the Short Term Historical (STH) files for historical data are written (TEMS or TEMA), and to confirm that the historical collection is distributed to the endpoint that is not listed in TCR reports "Servers" list or is missing from the MANAGEDSYSTEM table in TDW.
On the agent endpoint, review the .LG0 file for the confirm the agent is connecting to the TEMS:
KRAREG000 Connecting to <TEMS name>
And that the agent shows the UADVISOR situation for the historical collection is distributed / started:
KRAIRA000 Starting Enterprise situation UADVISOR_* <> for <Attribute Group>. No action is required.
The monitoring agent receives the details for where to find the Warehouse Proxy Agent (HD) from the TEMS it connects to.
The agent endpoint must be able to communicate with the HD component over the network in order for STH data to be able to be exported to the TDW database.
If the historical collection is storing the STH file on the TEMA, the pdcollect from the agent endpoint will provide a dir.info file that can be used to confirm the size and last modification date for the STH files.
To review whether there is a problem with the warehousing of the data from the STH binary file into the TDW database.
The default is to warehouse data every 24 hours, but if there are communication problems or other issues in the environment where the short term historical data being stored on the TEMA is not able to be exported to the TDW, the STH binary files for the attribute groups will continue to grow.
General ways to identify whether historical data is being exported:
One thing to note is that the issue may start off as a temporary "network" communication issue that is resolved, but because of the size of the STH file, then switches to a different issue related to free-space on the system which prevents the warehousing of the data even once the network issue is resolved.
During the export process, there must be free space equal to 3 times the size of the STH file.
The general flow:
The WPA registers with the HUB TEMS when it starts.
The agent connects to the TEMS it is configured to when it starts, and gets the location information from the TEMS for the location of where the WPA is running.
The agent performs historical data collections and historical samples are written to the STH files.
The agent exports data to the TDW through the HD based on warehousing interval and historical samples are inserted into the raw details historical tables for the attribute group.
The SY summarizes historical data from the raw details tables and creates / populates the "Daily" summary table / views.
The POPULATE_OSAGENTS procedure / script is run to query the _DV tables and create entries in the MANAGEDSYSTEM table.
Selecting a report in TCR lists the endpoint as a possible system to run the report against.
There are numerous possible causes for problems exporting historical data to the TDW database.
- Corruption / missing khdexp.cfg or STH files
- Attribute collection issues preventing data collectino for historical samples
Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM
Subscribe and follow us for all the latest information directly on your social feeds: