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

Configure or changing the monitoring server connection for agents

Use this procedure to configure or change the monitoring server connection to the agents.

  1. In the Manage Tivoli Enterprise Monitoring Services window, select the agent whose connection you want to configure. You can select multiple agents by holding down the Shift key or Control key and selecting agents.

  2. Click Actions → Reconfigure.

  3. Identify the communications protocol for communication with the monitoring server.

    You have seven choices: IP.UDP, IP.PIPE, IP.SPIPE, IP6.PIPE, IP6.SPIPE, IP6.UDP, or SNA. You can specify three methods for communication - this enables you to set up backup communication methods. If the method you've identified as Protocol 1 fails, Protocol 2 is used.

  4. Click OK.

  5. Complete the following fields 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 agent was running when you began the configuration process, after the reconfiguration is complete, you are asked if you want the agent restarted.

    Figure 1. Restart of Monitoring Agent window

    Reply Yes or No.


What to do next

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

Reply 1 or 2, as appropriate.

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

If you upgrade an agent and the upgrade includes new columns for an existing attribute group, stop and restart history collection to get the new attributes to be picked up by the Tivoli Enterprise Monitoring Server when history is being collected at the Tivoli Enterprise Monitoring Server. This applies to self-describing agents as well.


Parent topic:

Configure IBM Tivoli Monitoring components

+

Search Tips   |   Advanced Search