[EOL/EOE] In HA mode, NSM GUI Client does not automatically connect to the secondary server

Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE). Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.

NSM GUI client is not automatically trying to connect to the secondary server when the primary is in standby

When an NSM Server is deployed in High Availability mode, customers can provide the primary server IP address in the NSM GUI client. The NSM GUI client will automatically connect to the secondary server if the primary NSM server is in standby. This will happen only if the GUI client on the client machine connected to one of the servers successfully at least once in the past. If the GUI client had never connected to any of the NSM servers then the GUI client will not have any information in the cache regarding the HA setup of the server.

On a client machine where the GUI client is freshly installed, if providing just the primary server IP address for login, the GUI client may not automatically connect to the secondary. This is because the client never connected any of these servers earlier and doesn't have any information in the cache.

To resolve the situation, manually provide the IP address of the secondary server to login after which the GUI client will maintain information about the cluster in the cache and will automatically connect to the active server.

Knowledge Base