Cannot reconnect to the Tivoli Enterprise Monitoring Server
This message is displayed after the monitoring server goes down and
attempts to reconnect. The Tivoli Enterprise Portal client attempts to log on
once again to the Tivoli Enterprise Portal Server session. After a successful
logon, the user authorities that were in effect when the original logon
occurred are compared with the current user authorities. If any permission
is different, you must restart the portal client to ensure that all components
are synchronized with your user permissions. Changes to user permissions
include changes such as Navigator view assignment differences since the
last logon.
If you want to apply new permissions for other users immediately, make
all necessary changes and recycle the monitoring server. When the
monitoring server recycle is complete, each user is reconnected and their
user ID validated. If there were changes to their profiles, users must restart
the portal client session.
Portal server cannot connect to the AIX monitoring server private interface
If the hub monitoring server is installed on an AIX server with a public
and a private interface, the portal server cannot connect to the hub. There
are two environment variables you can set to control which interfaces to
publish. For IPV4 use
KDEB_INTERFACELIST
, for IPV6 use
KDEB_INTERFACELIST_IPV6
. In either address family, you can set those
variables to set, restrict, or add to the interfaces in use.
Table 15. Control interface publishing
Interface control
Environment variable
To set specific interfaces
for consideration:
KDEB_INTERFACELIST=ip4addr-1 ... ip4addr-n
KDEB_INTERFACELIST_IPV6=ip6addr-1 ... ip6addr-n
To remove interfaces from
consideration:
KDEB_INTERFACELIST...=-ip4addr-1 ... -ip4addr-n
KDEB_INTERFACELIST_IPV6=-ip6addr-1 ... -ip6addr-n
To add interfaces for
consideration:
KDEB_INTERFA ip4addr-1 ... ip4addr-n
KDEB_INTERFACELIS ip6addr-1 ...ip6addr-n
where:
ip4addr
Specifies either a symbolic network name, or a raw form dotted decimal network address.
ip6addr
Specifies either a symbolic network name, or a raw form colon-separated hex digit network address.
Note:
The plus sign must stand alone.
Tivoli Enterprise Portal Server is not reconnecting
If the portal server does not reconnect to the hub, recycle the monitoring
server and restart the portal server.
DB2 errors when opening a Tivoli Enterprise Portal workspace
If you are able to log in but receive an error message that you cannot open a
workspace in the Tivoli Enterprise Portal, verify that the database agent and
manager are working correctly. The configuration settings might need updating.
122
IBM Tivoli Monitoring: Troubleshooting Guide
Summary of Contents for E027SLL-H - Tivoli Monitoring - PC
Page 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 2: ......
Page 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Page 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Page 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Page 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Page 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Page 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Page 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Page 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Page 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Page 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Page 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Page 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Page 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Page 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Page 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Page 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Page 309: ......
Page 310: ...Printed in USA GC32 9458 05...