IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install the remote monitoring servers > Linux or UNIX: Installing a remote monitoring server

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Configure the remote monitoring server

To configure the remote monitoring server.

  1. Run...

    ...where tems_name is the name of your monitoring server (for example, remote_itmdev17).

  2. Type remote to indicate that this is a remote monitoring server.

  3. Enter the type of protocol to use for communication with the monitoring server.

    You have seven choices: ip, ip.pipe, ip.spipe, ip6, ip6.pipe, ip6.spipe, or sna. Press Enter to use the default communications protocol (ip.pipe).

  4. Press Enter to accept the default IPv4 or IPv6 (or both) host name(s) for the monitoring server. Depending on the protocols specified, this should be the host name for your computer for IPv4 or IPv6 (or both). If it is not, type the correct host name and then press Enter.

  5. To set up a backup protocol, enter that protocol and press Enter. If you do not want to use backup protocol, press Enter without specifying a protocol.

  6. Depending on the type of protocol you specified, provide the following information when prompted:

    Protocol Value Definition
    ip and ip6 ip and ip6 port number Port number for the monitoring server. The default is 1918.
    sna Net Name SNA network identifier for your location.
    LU Name LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software.
    Log Mode Name of the LU6.2 LOGMODE. The default value is "CANCTDCS."
    ip.pipe and ip6.pipe ip.pipe and ip6.pipe port number Port number for the monitoring server. The default is 1918.
    ip.spipe and ip6.spipe ip.spipe and ip6.spipe port number Port number for the monitoring server. The default is 3660.

  7. Press Enter to not specify the name of the KDC_PARTITION.

    You can configure the partition file at a later time, as described in Firewalls.

  8. Press Enter when prompted for the path and name of the KDC_PARTITION.

  9. To use Configuration Auditing, press Enter. If you do not want to use this feature, type n and press Enter.

  10. Press Enter to accept the default setting for the Hot Standby feature (none).

    For best results, wait until after you have fully deployed your environment to configure the Hot Standby feature for your monitoring server. See the IBM Tivoli Monitoring High Availability Guide for Distributed Systems for information about configuring Hot Standby.

  11. Press Enter to accept the default value for the Optional Primary Network Name (none).

  12. Press Enter for the default Security: Validate User setting (NO).

    This option is valid only for a hub monitoring server.

  13. For Tivoli Event Integration, type 2 and press Enter.

    This option is valid only for a hub monitoring server.

  14. At the prompt asking if you want to disable Workflow Policy/Tivoli Emitter Agent event forwarding, press Enter to accept the default (2=NO).

    This option is valid only for a hub monitoring server.

  15. To disable TEMS Security Compatibility Mode, type 2 and press Enter. Otherwise, press Enter to accept the default value (1=YES).

    Leaving TEMS Security Compatibility Mode enabled performs the following functions:

    1. It allows for backwards compatibility with previous versions of IBM Tivoli Monitoring components shipped before V6.3 when securing command execution (Situation Take Action, Execute Command, Take Action, Workflow Policy Take Action). Accept the default if you have a previous version of a portal server, hub monitoring server, or OMEGAMON product connecting to this Tivoli Enterprise Monitoring Server or if the system clocks are not synchronized across the systems with monitoring servers, the portal server, and monitoring agents.

    2. It permits commands to still execute even if cryptographic facilities are not available. This gives you time to ensure that, for example, your z/OS Tivoli Enterprise Monitoring Server has the Integrated Cryptographic Services Facility (ICSF) available.

    If you disable this option and you have a mixture of pre-V6.3 and V6.3 server components, if clocks are not synchronized, or if you don't have cryptographic services available, then command executions might fail.

  16. At the prompt asking if you want to configure the SOAP hubs, press Enter to save the default settings and exit the installer.

    This option is valid only for a hub monitoring server.


Results

The monitoring server is now configured.

A configuration file is generated in the install_dir/config directory with the format ms.config.


Parent topic:

Linux or UNIX: Installing a remote monitoring server