Configure SSH connection thresholds for LCM jobs

Adjust the default values for SSH connection attempts during Lifecycle Manager (LCM) jobs as necessary for your environment.

  1. Edit the opscenterd.conf configuration file. The location of this file depends on the type of installation:

    • Package installations: /etc/opscenter/opscenterd.conf

    • Tarball installations: INSTALL_DIRECTORY/conf/opscenterd.conf

  2. Adjust the available SSH connection values in the [lifecycle_manager] section.

    The following example doubles the default values for SSH connection attempts by LCM:

    [lifecycle_manager]
    ssh_connect_timeout_in_seconds = 60
    ssh_max_attempts = 6
    ssh_retry_delay_in_seconds = 20
    • [lifecycle_manager] ssh_connect_timeout_in_seconds: The number of seconds to wait for the SSH server on a target node to respond to a connection attempt during an LCM job. Default: 30 seconds.

    • [lifecycle_manager] ssh_max_attempts: The maximum number of times to attempt an SSH connection to a given target during an LCM job. Default: 3.

    • [lifecycle_manager] ssh_retry_delay_in_seconds: The number of seconds to wait between SSH connection retries during an LCM job. Default: 10 seconds.

  3. Restart OpsCenter.

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2025 | Privacy policy | Terms of use Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: Contact IBM