Connection timeout errors during patch installs, upgrades, and rollback operations
While performing maintenance activities such as EEB patch installation, software upgrade, or rollback on your NetBackup Flex Scale cluster, the operations may fail with a connection timeout error.
The following message may appear in the product logs:
ERROR Unable to connect to <cluster node #>: [Errno 110] Connection timed out
Cause
This error typically occurs if the network interface eth4 is down on any of the cluster nodes. NetBackup Flex Scale uses eth4 for communication between the cluster nodes. Whenever eth4 is down, it breaks that communication path and all ssh commands fail to execute with a timeout error.
Solution
Ensure that the network interface eth4 is up on each of the cluster nodes and then perform the maintenance tasks in the cluster.