Ipswitch - Channel Drops



The Ipswitch Channel allows replicated data and status/control information to pass between the servers in a Ipswitch Failover cluster. When the Ipswitch Channel disconnects unexpectedly, it is referred to as a channel drop. Channel drops interrupt the replication of data and transmission of status/control information and can result in false failovers. This behavior is not by design and can be caused by the issues described below.

More Information

Performance issues


The message " java.io.IOException: An existing connection was forcibly closed by the remote host" appears in the active server's NFLog.txt file, and the channel connection between the servers is lost.


This condition is unusual and generally points to an application, or Windows itself, experiencing a fault on the passive server. The most likely issue here is a sudden reboot / restart of the passive server and may be due to one of the following causes:

  • The server is configured for automatic software update management and some updates force a server reboot.
  • There is a software or Operating System issue which occasionally results in a BSOD and system restart.
  • The Ipswitch Failover Server service itself experiences problems and may hang or terminate unexpectedly.


  • If this is occurring, it should be possible to determine the likely source of the hang or reboot by examining the Windows event logs.
  • Alternatively, if the server does not show any evidence of a system restart or application hang, the issue may be due to one or both of the channel NICs forcing a channel disconnection. See Channel hardware or driver issues below for more information on this topic.

Passive server does not meet minimum hardware requirements


The data rate between the servers is very high during a Full System Check and the channel drops.


The passive server does not meet the recommended hardware requirements for Ipswitch Failover or it meets them but is much less powerful than the active server.  The underpowered server cannot apply the received replication data from the active server at the rate that the data is sent to the passive server.


In order to avoid reinstalling your Ipswitch Failover solution, it is best to tackle this issue by upgrading the hardware (for example, memory, CPU) on the passive server. It is important to establish the identity (Primary or Secondary) of the affected server before you perform the upgrade. An upgraded Primary server may require a new Ipswitch Failover license if the Heartbeat Signature (HBSIG) is changed. Upgrading the Secondary server will not require a new license.

Hardware or driver issues on channel NICs


The Ipswitch Channel drops or disconnects and reconnects intermittently.


  • Old/wrong drivers on the channel NICs.
  • If the physical connection for the Ipswitch Channel connection uses a hub or Ethernet switch, a hardware fault may cause the channel to drop.
  • Defective Ethernet patch or crossover cables.
  • Improper configuration of the NICs used for the channel connection.
  • ISP problems in a WAN environment.


  • Verify that channel NIC drivers are the correct/latest versions. This is a known issue with HP/Compaq ProLiant NC67xx/NC77xx Gigabit Ethernet NICs but may affect other NIC types as well. See IKB-116 Ipswitch Failover and Gigabit Ethernet NIC drivers. (NC77XX) .
  • Verify hubs and Ethernet switches are operating properly. Identify and replace any defective components.
  • Test for defective Ethernet patch or crossover cables and replace if defective.
  • Correctly configure the NICs used for the channel connection.
  • Check the physical link for ISP problems.

Firewall connection

In both a LAN or WAN deployment of Ipswitch Failover, the channel may be connected via one or more Internet firewalls. Since firewalls are intended to block unauthorized network traffic, it is important to ensure that any firewalls along the route of the channel are configured to allow channel traffic.


The Ipswitch Channel cannot connect or connects and disconnects continuously.


In a WAN deployment, port #57348 (or any other port configured for the Ipswitch Channel) is closed on one or more firewalls on the route between the channel NIC on the Primary, Secondary, and Tertiary (if installed) servers.


Open port #57348 (and any other port configured for the Ipswitch Channel) on all firewalls on the route between the channel NIC on the Primary, Secondary, and Tertiary (if installed) servers .

Incorrect Ipswitch Channel configuration


  • IP conflicts are encountered on one of the channel IP addresses.
  • The Ipswitch Channel does not connect or connects and disconnects.


Identical IP addresses at each end of the channel, IP addresses in different subnets without static routing at each end of the channel, or a channel NIC configured for DHCP when a DHCP server is not available.

During the installation of Ipswitch Failover, some configuration data from the Primary server is copied to the Secondary server. This includes configuration information for any NICs. The Help text displayed on the Ipswitch Failover Setup wizard describes how to configure the IP address for each NIC on the Secondary server. If this step is not completed, it is possible for one or more channel NICs on the Secondary server to contain a variety of incorrect addresses derived from the Primary server.

For example, assume you want the following correct configuration after deployment:


Principal (Public) NIC:
Channel NIC #1:
Channel NIC #2:


Principal (Public) :
Channel NIC #1:
Channel NIC #2:

Immediately following the restore/Plug and Play phase of the Secondary installation, Channel NIC #1 on the Secondary server may have acquired any of the following IP addresses:

(d) No static IP address (for example, NIC is configured to use DHCP)

Clearly, none of these will allow a connection to address on the Primary server - (a) and (c) are in a different subnet, (b) is a duplicate IP address, and (d) will fail because there is normally no DHCP server connected to the channel NICs.

Which address is assigned to Channel NIC #1 on the Secondary server depends on the exact driver configuration of the NICs on that server, as compared with the NICs on the Primary server. The most likely result, and the one usually expected during deployment, would be for the IP address of Channel NIC #1 on the Primary server to be transferred to Channel NIC #1 on the Secondary server.

On rare occasions, if the Primary and Secondary servers have NICs of the same type in a different order, both the name and IP address of a channel NIC on the Primary server may be transferred to the Principal (Public) NIC on the Secondary; or the name and IP address of the Principal (Public) NIC may be transferred to a channel NIC. Similarly, the names of the channel NICs may be reversed on the Secondary server under these circumstances. If this happens, it can be hard to reconcile the names of the NICs with their physical identities, making it difficult to assign the correct IP address to each NIC on the Secondary server.


It is part of the normal Ipswitch Failover installation process to manually assign the correct IP addresses to each NIC on the Secondary server. If there is no channel connection between the servers, check that the IP addresses on the Secondary server's channel NICs are correctly configured. You should also double-check the settings for the Principal (Public) NIC, since any configuration error here may not be apparent until a switchover is performed or a failover occurs.

It is possible to capture the identities of all of the NICs on the Secondary server prior to installing Ipswitch Failover, by opening a Windows Command Prompt on that server and executing the following command:

ipconfig /all > ipconfig.txt

This saves the current name, TCP/IP configuration, and MAC address of each NIC on the Secondary server to a file called ipconfig.txt , which will be present on that server after the Plug and Play phase of the Ipswitch Failover install has completed. At this point, it is possible to compare the pre-install and post-install state of each NIC by running ipconfig /all from a Windows command prompt and comparing the output of this command with the content of the file ipconfig.txt . The MAC address of each NIC is tied to the physical identity of each card, and never changes - so it is possible to identify each NIC by its MAC address and determine its original name and network configuration, even if these have been updated by the Plug and Play process.

Subnet / Routing issues:

In a LAN


The Ipswitch Channel disconnects or fails to connect in a LAN deployment.


The Ipswitch Channel may disconnect or fail to connect due to the Principal (Public) NIC and/or one or more channels sharing the same subnet


If Ipswitch Failover is deployed in a LAN environment, the Principal (Public) IP address and the channel IP address on a server should be in separate subnets. If there are multiple redundant channels, each should have its own subnet. Check the network configuration for each NIC on both servers in the pair, and correct any issues.

In a WAN


The Ipswitch Channel disconnects or fails to connect in a WAN deployment.


When the Ipswitch Channel disconnects or fails to connect in a WAN deployment it may be the result of the static route not being configured or that it has been configured incorrectly.

When Ipswitch Failover is deployed in a WAN, it is generally not possible for the Principal (Public) IP address and the channel IP addresses to be in different subnets, since there is usually a single network path between the two servers. In order to ensure that channel traffic is routed only between the endpoints of the channel, it is necessary to configure a static route between these endpoints.


Please refer to IKB-466 How to create a static route for the Ipswitch Channel connection in a WAN environment , for a detailed discussion about WAN channel routing issues, and for instructions on how to configure a static route for the Ipswitch Channel.

Applies To

Ipswitch Failover

Related Information



0 out of 0 found this helpful



Please sign in to leave a comment.