Cannot update Service Manager link when using non-standard ports

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation
• CA Automic Operations Manager
• CA Automic Oracle

Issue/Introduction

Update Service Manager Link in Admin perspective throws error when SMGR_PORT_RANGE does not start with the port being used: Process with Process ID '[PID]' is not available in the Service Manager.  

Steps to reproduce:

1. Start the service manager on port 8874
2. Update SMGR_PORT_RANGE in UC_SYSTEM_SETTINGS to (8871,8879) OR (8871,8874)
3. Attempt to Update the service manager link from Administration perspective -> Agents

    Expected behavior:
    See message that the service manager link was updated

    Actual behavior: 
    Popup error shows: Process with Process ID '[PID]' is not available in the Service Manager.

    If SMGR_PORT_RANGE is updated to (8874,8879) so that the port the smgr is running on is first, it works as expected. Having just 8874 in SMGR_PORT_RANGE, it works as expected.

Environment

Release : 12.3, 21.0.x

Component : AUTOMATION ENGINE, Service Manager

Cause

Multiple Service Managers running on the same server.

Resolution

After possible server reboot, issue disappeared on its own both on Broadcom test systems and at customer site.  If it happens, we'll want:

See if it's reproducible with SMGR_SUPPORT_LEGACY_SECURITY set to Y in UC_SYSTEM_SETTINGS
Reproduce with tcp/ip=2 and database=4 traces set on WPs
Send WP logs, WP traces, CP logs

----------

For the issue where multiple Service Managers are running on the same server (12.3 and 21) the SMGR_PORT_RANGE in UC_SYSTEM_SETTINGS must can only use a single port number.
In order to use a defined range like (8871,8879), there can only be a single Service Manager running on the server.