Siteminder fails to start because ClMgrs is using port 44442

edit: I wrote this before I saw it was linux, but the same concept applies, except the registry is located in /etc/CommVaultRegistry/Galaxy/InstanceXXX

Technically, that port should be an ephemeral port - ie. dynamically allocated and should not be not statically bound by any application. Applications should know that that port could become unavailable the next time it wants to use it.

Commvault queries the OS and picks from the ephemeral or ‘dynamic’ port range that Microsoft specifies: 

On my windows 2012 server, this is the output:

Protocol tcp Dynamic Port Range
---------------------------------
Start Port      : 33535
Number of Ports : 32000

This means that any application can lay claim to port 33535 and above for 32000 ports - i.e between 33535 and 65535. First come first serve!

For Linux the ephemeral port range is generally 32768–60999

As such siteminder is at fault for always requiring that port since it falls in the ephemeral / dynamic range - it should pick a port from outside of this range if it needs a static port that always has to be used (i.e that is why Commvault has 8400, 8403 etc.)

That being said, there is something you can do from our side.

When commvault starts up for the first time, it picks a bunch of dynamic ports to run its services on, it stores them in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\Runtime

For linux, it should be something like /etc/CommVaultRegistry/Galaxy/Instance001/Runtime/.properties

For this particular service, it ‘saves’ the last used port under SAVED_RecallService_v4

The next time the services run, it tries to reuse the port number listed there.

So all you really have to do is:

1. stop the Commvault Client Manager Service or all Commvault services
2. Start or restart siteminder so that it uses port 44442
3. Delete the registry key “SAVED_RecallService_v4” in the above location
4. Start the Commvault Client Manager Service or all Commvault services

This should then find a new port and use that going forward.

If you want to fix the port, so it always uses the same one, you can create a key called “FIXED_RecallService_v4” and set the decimal value to any available port (preferably outside the dynamic port range) - but that should not be necessary.

Hope this helps.