Upgrading with a fix pack for remote installations

If your remote installation has IBM® Tivoli® Monitoring Log File Agent, Logstash, or Tivoli Event Integration Facility, complete these steps as part of a fix pack upgrade. Complete these steps to use the latest version of your remote installation and to accept the latest changes in the components.

About this task

When you upgrade with a fix pack, the remote Log File Agent, Logstash, or Tivoli Event Integration Facility doesn’t get upgraded.

Usually the upgrade script handles Apache ZooKeeper, Liberty, and Log File Agent on a IBM Operations Analytics Log Analysis server and remote Apache Solr by default. For components in the same server where the upgrade is run, the upgrade is done automatically. If the component is on a remote computer, such as Logstash, use the install.sh script in the remote_install_tool directory.

For the manual upgrade, complete these steps on a remote server:

Procedure

  1. Stop Logstash and Tivoli Event Integration Facility:
    cd LA_HOME/utilities
    ./logstash-util.sh stop
    ./lfautil.sh -stop
    cd LA_HOME/DataForwarders/EIFReceivers/utilities
    ./eifutil.sh -stopAll

    Where LA_HOME is the Log Analysis configuration directory.

  2. Back up all Logstash and Log File Agent configuration files:
    cd LA_HOME/Logstash/logstash-<version>/logstash-scala/logstash/config
    cp -pi *.conf  <temporary_backup_directory>

    Where LA_HOME is the Log Analysis configuration directory, <version> is your version of Logstash, and <temporary_backup_directory> is your temporary backup directory.

    cd LA_HOME/IBM-LFA-6.30/config/lo/
    cp -pi *.conf <LFA_temporary_backup_directory>
    cp -pi *.fmt <LFA_temporary_backup_directory>

    Where LA_HOME is the Log Analysis configuration directory, and <LFA_temporary_backup_directory> is the Log File Agent temporary backup directory.

  3. Use the install.sh script in the remote_install_install directory on the IBM Operations Analytics Log Analysis server to install a new instance of Logstash, Log File Agent, or Tivoli Event Integration Facility on a remote server to a new directory.
  4. Copy the Logstash and Log File Agent configuration files into a new configuration directory:
    cd NEW_LA_HOME/Logstash/logstash-<version>/logstash-scala/logstash/config
    cp -pi <temporary_backup_directory>/*.conf .

    Where NEW_LA_HOME is the new Log Analysis configuration directory, and <version> is your version of Logstash.

    cd NEW_LA_HOME/IBM-LFA-6.30/config/lo/
    cp -pi <LFA_temporary_backup_directory>/* .

    Where NEW_LA_HOME is the new Log Analysis configuration directory, and <LFA_temporary_backup_directory> is the Log File Agent temporary backup directory.

  5. Edit the configuration file to a new directory path.
    1. Update the Logstash logstash-scala.conf file with the NEW_LA_HOME directory.
    2. Also, update all Log File Agent .conf files, such as syslog_log.conf, with the NEW_LA_HOME directory.
  6. Start Logstash and restart Log File Agent on the NEW_LA_HOME directory:
    cd NEW_LA_HOME/utilities
    ./logstash-util.sh start
    ./lfautil.sh -restart

    Where NEW_LA_HOME is the new Log Analysis configuration directory.

  7. Verify that Logstash, Log File Agent, and Tivoli Event Integration Facility can stream events to the IBM Operations Analytics Log Analysis server.
  8. After you confirm that data is streaming to all respective data sources, remove the previous LA_HOME directory:
    rm -rf LA_HOME

Results

Log File Agent Logstash, and Tivoli Event Integration Facility are upgraded.