Location of remote monitoring servers
It is a good idea to place a remote monitoring server on every z/OS® system where you are installing monitoring agents. In fact, two monitoring agents (OMEGAMON AI for z/OS and OMEGAMON AI for Storage) require that you configure them in the same address space as a hub or remote monitoring server.
For advice about placing remote monitoring servers on distributed systems, see the IBM Tivoli Monitoring: Installation and Setup Guide.
Tips:
- A remote monitoring server can report to a high-availability hub on the same LPAR.
- If the hub is not a high-availability hub, it cannot be on the same LPAR as any of the remote monitoring servers that report to it and that are configured to use any TCP/IP protocol.
- If more than one remote monitoring server is configured in a z/OS image and if a TCP/IP protocol is being used for communication, the hub to which each remote monitoring server reports must have a unique port number. Otherwise, connectivity problems are likely.
- If more than one hub is configured in a z/OS image, each hub must have a unique port number for any nonsecure TCP/IP protocols being used and a unique port number for any secure TCP/IP protocols being used.
For information about port number allocation, see Port number assignments.
- If a remote monitoring server is to communicate with any monitoring agents that require SNA, the remote monitoring server must be configured for SNA communications. Examples of such monitoring agents include OMEGAMON AI for z/OS and OMEGAMON for Messaging (for the 3270 interface component). See the product-specific configuration guides for further information about SNA requirements.