3. If subnodes are online, are workspaces showing correct titles?
v No: Verify that application support has been installed correctly and that
buildpresentation.bat ran correctly.
v Yes: Go to the next step.
4. If workspaces contains titles, is there a column heading?
v No: Verify that application support has been installed correctly and that
buildpresentation.bat ran correctly.
v Yes: Go to the next step.
5. If there is only a column heading with no data, turn on UNIT:KRA ALL in the
agent and verify that rows are being returned when the workspaces are
displayed.
Status of a monitoring agent is mismatched between the portal client
and tacmd command
You can encounter a problem that the status of a monitoring agent is mismatched
between the Tivoli Enterprise Portal client and tacmd command. For example, a
monitoring agent shows as online in the portal client and offline in the results of a
tacmd command.
Diagnosing that the status of a monitoring agent is
mismatched between the portal client and tacmd command
You can diagnose that the status of a monitoring agent is mismatched between the
Tivoli Enterprise Portal and tacmd command by setting a trace to determine
whether the problem is in the Tivoli Enterprise Portal Server or the Tivoli
Enterprise Monitoring Server.
About this task
To diagnose that the status of a monitoring agent is mismatched between the
portal client and tacmd command, perform the following steps:
Procedure
Preliminary diagnostics
1. Verify the state of the monitoring agent in Manage Tivoli Monitoring Services.
2. Compare the status of the node in the physical Navigator view with the status
reported in the Managed System Status workspace. If the status in the physical
Navigator view agrees with the status shown in the Managed System Status
workspace, then the problem is at the monitoring agent. See “Resolving
monitoring agent problems” on page 14.
3. To determine whether the problem is in the portal server or monitoring server,
set the following trace in the portal server: ERROR (UNIT:ctcmw IN ER)./
4. Then examine the portal server log for the following statement: Node Status
event received (managed system name).
v If the trace shows that the last node status record received for the managed
system matches the status shown in the portal client, then the problem is
located in the monitoring server. See
v If the trace shows that the last node status record received for the managed
system indicated the correct status, then the problem is located in the portal
server. Run the portal server trace, collect logs, and call IBMSoftware
Support.
Chapter 3. Common problem solving 13
To Next Page
Loading...
Need help?
General
