After new vApp deployment External Databases showing inconsistence connection

Products

CA Identity Manager

Issue/Introduction

We installed a new Identity Suite vApp 14.4 connecting to an external MS SQL 2019 database with always-on feature to host the runtime DB.

We did this by adding:

;DatabaseName=<database name>;MultiSubnetFailover=True

to the end of the connection URL in the external database configuration.

All test connections show success

The problem starts after the vApp setup and deployment for 3 vApps, the External Databases appears to be inconsistently losing connection from the status page listed in the IGA Virtual Appliance dashboard.

The status page when using SSH is showing random failed and succeeded connection to each IM, IP, IG external database, when running status checks....

-------------------------------------------------------------------------------------------------------------------------------------------------

Example:

External Database Server_name.domain.com

[OK] Connection to IM database (*****Server name removed******:60002) succeeded
[ERROR] Connection to IP database (*****server name removed******:60002) failed
[OK] Connection to IG database (*****server name removed******:60002) succeeded

External Database Server_name.domain.com
[ERROR] Connection to IM database (*****server name removed******:60002) failed
[OK] Connection to IP database (*****server name removed******:60002) succeeded
[ERROR] Connection to IG database (*****server name removed******:60002) failed

-------------------------------------------------------------------------------------------------------------------------------------------------

We are running 3 vApps: vApp 1: IM, US, PS, CS

vApp 2: IM, US, PS, CS

vApp 3: CL, IG, IP

-------------------------------------------------------------------

Environment

Release : 14.4

Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)

Resolution

For 14.4 connection URL is done only using basic details, hostname and port. That is the reason you see that issue, this has been addressed for the upcoming release 14.4.1 which uses the actual connection string mentioned in the connection URL section for DB config. This can be considered a false positive. This issue shows up due to load balancing which is not considered during monitoring, the "s" command.