When an end user requests a connection, the connectivity software establishes a connection to the first available OpenSwitch server. When an OpenSwitch server fails, end-user connections are dropped. When the end user reconnects, the connectivity software establishes a connection to the alternate OpenSwitch server.
OpenSwitch CMs process end-user login requests to servers controlled by OpenSwitch. When the RCM receives a login request, it tells the OpenSwitch server to log the user in to the requested server. It does not determine if the server is available or if a failover process has occurred. If OpenSwitch determines that the server is not available, it sends the RCM a login failure notification (see “End-user login or connection failure”). After the RCM has processed the failure, OpenSwitch changes the server status to DOWN and requests a connection to the standby server.
When processing a login request, the RCM does not distinguish
between an application end user and
a DSS user. Only upon login request
failure does the RCM note the type of user requesting to log in.
If an application end-user login fails, the RCM begins the failover
process. See “Application end users”.
If the Open Switch server fails, your environment is protected because user logins are switched to the secondary OpenSwitch server.
