IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Configure IBM Tivoli Monitoring components

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Change the configuration of the Tivoli Enterprise Monitoring Server

You can change the basic configuration of the monitoring server through Manage Tivoli Enterprise Monitoring Services.

  1. In the Manage Tivoli Enterprise Monitoring Services window, right-click the monitoring server.

  2. Click Reconfigure (on Windows) or Configure (on UNIX).

  3. Identify the communications protocol for the monitoring server.

    You have seven choices: IP.UDP, IP6.UDP, IP.PIPE, IP6.PIPE, IP.SPIPE, IP6.SPIPE, or SNA. You can specify up to six methods for communication. If the method you identify as Protocol 1 fails, Protocol 2 is used as a backup. If Protocol 2 fails, Protocol 3 is used as a backup, and so on.

  4. Click OK.

  5. Complete the fields settings listed in Table 1 for the communications protocol for the monitoring server and click OK.


    Communications protocol settings

    Field Description
    IP.UDP and IP6.UDP settings
    Hostname or IP Address The host name or IP address for the hub monitoring server. Note that the Tivoli Enterprise Monitoring Server supports both IPV4 and IPV6 addressing formats.
    Port # or Port Pools The listening port for the hub monitoring server.
    IP.PIPE and IP6.PIPE settings
    Hostname or IP Address The host name or IP address for the hub monitoring server. Note that the Tivoli Enterprise Monitoring Server supports both IPV4 and IPV6 addressing formats.
    Port Number The listening port for the monitoring server. The default number is 1918.
    IP.SPIPE and IP6.SPIPE settings
    Hostname or IP Address The host name or IP address for the hub monitoring server. Note that the Tivoli Enterprise Monitoring Server supports both IPV4 and IPV6 addressing formats.
    Port number The listening port for the hub monitoring server. The default value is 3660.
    SNA Settings
    Network 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.
    LU 6.2 LOGMODE Name of the LU6.2 LOGMODE. The default value is "CANCTDCS."
    TP Name The transaction program name for the monitoring server.

  6. If the monitoring server was running when you began the configuration process, after the reconfiguration is complete, you are asked if you want it restarted.

    Figure 1. Restart Component window: Tivoli Enterprise Monitoring Server

    Reply Yes or No.


What to do next

On Linux and UNIX, you can also use the itmcmd config -S command to change the configuration of a monitoring server. When the CLI completes the reconfiguration, if the monitoring server was running when you began this process, you are asked if you want it restarted:

Reply 1 or 2, as appropriate.

If you choose the restart, the monitoring server is stopped and then started again. These actions are necessary to force the server to read your changed configuration (which is always read at server startup). On UNIX platforms the component should be restarted with the same user that it previously ran on. If the monitoring server was not running when reconfigured, no action is performed, and the server remains stopped.

  1. Use caution when starting, stopping, or restarting the Tivoli Enterprise Monitoring Server, as it is a key component.

  2. You cannot configure a hub monitoring server and a remote monitoring server on the same system because you cannot have two processes listen to the same IP port on the same system.

    • You can configure any number of remote monitoring servers on the same system as long as each reports to a different hub and uses a different port number.

    • You can configure any number of hub monitoring servers on the same system as long as each uses a different port number.

    • If a hub monitoring server and a remote monitoring server are configured on the same system, the remote monitoring server must report to a hub on another system using a port other than the one used by the hub running on the same system.

    • You cannot have two monitoring servers talking to each other over IP from the same system unless one of them is a high-availability hub monitoring server, because a high-availability hub is isolated to a private IP address. See the IBM Tivoli Monitoring High Availability Guide for Distributed Systems.


Parent topic:

Configure IBM Tivoli Monitoring components

+

Search Tips   |   Advanced Search