Chapter 6. Connectivity troubleshooting
Review the connectivity troubleshooting topics for problems you might experience
with logging in, passwords, and communication among IBM Tivoli Monitoring
components.
When the Tivoli Enterprise Portal detects a connection error, it can repair the error
and your client session can resume unaffected. Use the connectivity topics to
diagnose and recover from connectivity problems.
If you are running the Tivoli Enterprise Monitoring Server on z/OS, see
“Troubleshooting z/OS-based installations” on page 96 for information about
configuration problems affect connectivity.
Cannot log on to the portal server
If you are unable to successfully log on to the portal server to start your Tivoli
Enterprise Portal work session, review the symptoms and corrective actions to
remedy the problem.
The following table provides resolutions for problems logging in to the Tivoli
Enterprise Portal Server.
Table 12. Cannot log in to the Tivoli Enterprise Portal Server
Problem Corrective action and solution
User authorization failed
-OR-
KFWITM215E: Unable to process
logon request
v Ensure the user ID and password are correct.
v Verify that the monitoring server has started.
v Define the user in the portal server.
v Configure the TEPS or TEPS2 data sources.
v If security validation is active on the hub monitoring server, make sure
the user ID is defined to the security system.
For more information on security validation see the IBM Tivoli Monitoring
Installation and Setup Guide (http://publib.boulder.ibm.com/infocenter/
tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623FP1_install.htm) or
IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:
Common Planning and Configuration Guide.
KFWITM010I: Tivoli Enterprise
Portal Server not ready.
-OR-
KFWITM402E: Communication with the
Tivoli Enterprise Server could not
be established.
v Wait for the portal server to establish connection.
To determine whether or not the portal server is ready for portal client
logon, search the portal server trace log for this text string: Waiting for
requests. If that string is not found, the portal server has not completed
initialization. Portal server initialization can take as long as 20 minutes.
To view the trace log, open Manage Tivoli Monitoring Services, right-click
the portal server, and select Advanced > View trace log
v Recycle the portal server.
For more information see “The portal server does not start or stops
responding” on page 15.
© Copyright IBM Corp. 2005, 2012 115
To Next Page
Loading...
Need help?
General
