Filter
Top Products
146 IBM Tivoli Remote Control Across Firewalls
If you get the version of the Endpoint, this means the downcall is working.
Otherwise, you could face some local Endpoint security restrictions. To
isolate the problem, you could refer to the epmgrlog, located on the TMR
Server, the gatelog, located on the Endpoint Gateway, and the lcfd.log,
located on the local machine, which could provide you with much information
regarding the Endpoint communication.
Is the Managed Node alive?
If one of the Gateways is not alive, the Managed Node, which hosts the
Gateway, could be down itself. The command to check the availability of the
Managed Node is:
wping [Managed Node hostname]
If the Managed Node is up and the Gateway is not, you could check the
gatelog located on the Manage Node and try to restart the Gateway using the
wgateway command.
Is the Managed Node behind a firewall?
In a Standalone Remote Control Proxy environment, one Managed Node is
located behind a firewall, and communication problems could result from this
configuration.
Is the firewall configured?
If the Managed Node is behind a firewall, some ports are defined at the
Framework level to fix the Tivoli communications. Rules need to be created
on the firewall to allow this type of communication.
Is the DNS configured?
Tivoli is really dependent of the Domain Name Server (DNS) configuration. If
the normal and reserve hostname resolution are not working either from the
TMR Server to the Managed Node, or from the Managed Node to the TMR
server, the Framework will never be able to be establish communications
between its different components.
However, if the DNS is correctly configured and the Managed node is still not
alive, you could analyze the local Managed Node oservlog and/or reexec the
Managed Node.
Nevertheless, if the various problems could not be isolated even after you have
executed all actions and analyzed all of the logs mentioned above, it is advised
that you contact IBM customer support and provide them the following logs:
lcfd.log — located on the local machine
gatelog — located on the Endpoint Gateway
epmgrlog — located on the TMR Server
oservlog — located on the TMR Server and on the Endpoint Gateway