A remote monitoring server can be configured to report
to a high-availability or a static hub monitoring server. Although
most sites prefer to have z/OS® agents
report to a hub monitoring server on z/OS,
they can also report to a remote monitoring server that reports to
a hub on a distributed system.
About this task
The configuration shown in Figure 1 depicts a remote monitoring
server reporting to a static hub monitoring server on another z/OS LPAR.Figure 1. Remote monitoring server on z/OS reporting
to a hub on a distributed system
By default, monitoring agents are configured to report to the
local monitoring server.
Procedure
Set the KDS_TEMS_COMM_PROTOCOLn parameters.
At least one of the communication protocols must be the same
as a protocol selected for the hub.
Set the KDS_TEMS_TCP_HOST parameter to the TCP/IP host
name (in dot-decimal format) of the z/OS system
where the remote monitoring server is installed.
Set the KDS_HUB_TCP_HOST parameter to the TCP/IP host name
(in dot-decimal format) of the system where the hub monitoring server
is installed.
Set the KDS_HUB_TCP_pipe_type_PORT_NUM to the value
of the port number of the hub for each protocol selected.
What to do next
There are many other KDS_* parameters that are required for
monitoring server configuration. You must either accept the defaults
for these parameters or customize them for your site. See Tivoli Enterprise Monitoring Server (KDS) parameters for more information on these
parameters. You may also want to enable the following optional features:
