Our security team are complaining that when they reboot their Siteminder servers, their process fails to start because ClMgrS process appears to be using port 44442. Siteminder needs that port in order to start up. What we end up having to do is to stop the commvault process in the client to let the Siteminder start; then restart commvault.
Does anyone know why Commvault need that port? It is not in the list of standard ports that Commvault uses.
Anyone know how to exclude that port by the CommVault agent?
Best answer by Damian Andre
View original