Filter
Top Products
Chapter 5. Troubleshooting techniques 145
From here on, the Endpoint problem determination process is explained in detail.
However, for more detailed information regarding Endpoint troubleshooting, refer
to the
Tivoli Management Framework Maintenance and Troubleshooting Guide
,
GC32-0807.
Is Endpoint alive?
The Endpoint must be alive in order to let the pcremote process send it the
necessary down calls. The following command could be used:
wep [Endpoint label] status
Is Gateway alive?
If the Endpoint is not alive, the problem could be issued by the Gateway
unavailability. The command that can be used to control the Gateway is:
wgateway [Gateway label]
Is the EP service started?
If an Endpoint is not alive and its Gateway is up, you have to control if the
Endpoint service is started locally on the machine.
If the service is not started, you have to start it. However, in the case of the
service fails to start, you could check the lcfd.log to analyze why the service
is failing to start.
If the Endpoint service is started and the Endpoint is still not alive, the
epmgrlog, located on the TMR Server, the gatelog, located on the Endpoint
Gateway and the lcfd.log, located on the local machine could you help to
isolate the problems.
Is Endpoint attached to a Gateway Proxy?
If either the RC Controller or the RC Target is connected to a Gateway Proxy,
you must be sure that your TFST environment is correctly configured and is
working. However, before starting this complex process, first you must be
sure that you have made the minimum control on the Endpoint, to verify that
the Endpoint itself is not causing the issue. Next, in order to help you follow
the necessary steps to determine if your TFST environment is working, we
have defined a specific process. Refer to “TFST problem determination
process” on page 147 for more information.
Is downcall working?
Even if the Endpoint is alive, it could be impossible for the Framework to issue
down calls on the Endpoint. You could check if the spawning of Framework
methods work properly by executing the following command:
wadminep [Endpoint label] view_version