Hello Commvault Experts,
I would like to seek clarification regarding the behavior of Commvault agent upgrades on IBM i (AS/400) systems.
When an agent upgrade is initiated and pushed from the Commvault Command Center/CommCell Console to an IBM i client, is there any scenario in which the upgrade process could disable, stop, modify, or otherwise affect SSH services (Port 22) on the target IBM i server?
We recently observed an SSH connectivity issue following an upgrade activity and are trying to determine whether:
- The Commvault upgrade process makes any changes to SSH configuration or service status on IBM i.
- Any Commvault components or upgrade scripts require restarting network services that could temporarily affect Port 22 availability.
- There are known issues, prerequisites, or documented cases where an IBM i client upgrade resulted in SSH becoming unavailable.
- Any specific logs on the CommServe, MediaAgent, or IBM i client should be reviewed to verify whether the upgrade had any interaction with SSH services.
My understanding is that Commvault agent upgrades should generally not disable IBM i SSH services, as SSH is an operating system service rather than a Commvault component. However, I would appreciate confirmation from anyone who has experience with IBM i client upgrades or has encountered similar behavior.
Thank you in advance for your insights.
