The functional specifications of the Dual IP feature are as follows:
After installing the Dual IP package, you can configure an optional secondary IP address in CMS to connect to a survivable Communication Manager system. The secondary IP address can be a hostname or an actual IP address and port number. Do the configuration during the cmssvc setup, cmssvc swsetup, and cmsadm acd_create commands for each ACD.
If you do not install the Dual IP package, the administration options for the second IP address are not displayed. The option for one IP address for the link to Communication Manager is displayed.
-
When establishing a TCP/IP connection to
Communication Manager,
CMS tries to connect to the primary IP address five times, waiting 30 seconds between each attempt. If unable to connect,
CMS tries the Survivable
Communication Manager IP address, if assigned, two times, waiting 30 seconds between each attempt.
If connection to the Survivable Communication Manager IP address also fails, CMS tries connecting to the primary IP address five times, waiting 30 seconds between each attempt until one of the connections starts functioning.
If the main link fails at any time, the entire connection cycle is attempted again until a connection is established with the main Communication Manager or ESS/LSP.
After the TCP/IP connection is established with the Communication Manager system, CMS requests data. Therefore, a delay occurs before CMS starts processing data, which is normal for link establishment.
If the link is fully established through the secondary IP, an informational message is recorded in the CMS elog file.
A new link indicator is used by the clients to show the alternative connection status.
-
After
Communication Manager fragmentation is resolved, when the primary
Communication Manager system gains control again and the ESS is not in control, the ESS eventually drops the link as it becomes inactive. When the link drops,
CMS tries to re-establish the connection to the primary link.
