In OpenSwitch 15.1, a mutually-aware OpenSwitch server supports concurrent coordination modules.
A coordination module connects to an OpenSwitch server to control client logins and failover patterns. You can customize OpenSwitch to fit your requirements, and you can run multiple CMs against multiple OpenSwitch servers to create a redundancy environment so that no single OpenSwitch is a point of failure.
When multiple CMs connect to one OpenSwitch, these activities, which are transparent to the end user, take place:
Each CM registers its unique name with OpenSwitch using the Client-Library CS_APPNAME parameter. The unique name is generated by combining the host name and the process ID.
When the OpenSwitch server accepts a CM connection, it assigns the CM a unique ID number, and sends that number back to the CM as a message before the connection event is completed. OpenSwitch maintains an internal list of inactive CMs that are currently available.
If a CM becomes unresponsive for the period of time specified by the COORD_TIMEOUT configuration parameter, OpenSwitch retrieves the next CM ID number from the internal list of inactive CMs. All future notifications include the new ID as part of the notification.
For more information about using concurrent coordination modules, see Chapter 2, “Using Coordination Modules” in the OpenSwitch Coordination Module Reference Guide.
