Events are logged after an IP address change on an Exchange cluster

After you change the Internet Protocol (IP) address of the nodes on a cluster or of the Exchange Virtual Server (EVS) on a cluster node, resources successfully fail over. However, in several minutes, some resources may not pass the IsAlive check, and this causes the Exchange Virtual Server to fail over:

• Hypertext Transfer Protocol (HTTP) virtual server instance
• Internet Message Access Protocol, Version 4rev1 (IMAP4) virtual server instance
• Post Office Protocol version 3 (POP3) virtual server instance
• Simple Mail Transport Protocol (SMTP) virtual server instance

The following events may be logged in the application event log:

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2074
Computer: NODE-1
Description: Exchange HTTP Virtual Server Instance - (VIRTUAL-1): Cluster Service failed the isalive checking for the resource

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2074
Computer: NODE-2
Description: Exchange IMAP4 Virtual Server Instance - (VIRTUAL-1): Cluster Service failed the isalive checking for the resource

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2074
Computer: NODE-2
Description: Exchange POP3 Virtual Server Instance - (VIRTUAL-1): Cluster Service failed the isalive checking for the resource

The following event may be logged in the system log:

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 114
Computer: NODE-2
Description: Instance 100 has invalid secure binding descriptor 192.168.10.10:443:VIRTUAL-1 (host name ignored).

This issue may occur if one or both of the following conditions are true:

• The IP address of the cluster nodes was physically changed.
• The IP address of the Exchange Virtual Server is physically changed.

After you change the IP address of the cluster nodes, the network adapter and IP resources in the cluster and resource groups must be re-established. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: After you change the IP address of the Exchange Virtual Server, Internet Information Services (IIS) resources must be updated to set the new IP address in the metabase. In this scenario, the cluster service still tries to monitor the IIS resources by using the original IP address that was assigned to the cluster node.

After you change the IP address, the original Exchange Virtual Server IP address may remain in several places. In this scenario, the original values are read by the server cluster. Therefore, the cluster resources fail the IsAlive check and cannot remain online.

To resolve this issue, make sure that the protocol resources are updated correctly:

1. In the Cluster Administrator program, make sure that the settings for Network and the new IP addresses on the Parameters tab of all the IP address resources are correct.
2. In Exchange System Manager:
   1. Locate the Protocols area under the Exchange Virtual Server that you want to modify.
   2. Expand the HTTP, IMAP4, SMTP, and POP3 virtual servers.
   3. Open the properties of these virtual servers, and then verify the IP address in the advanced properties.

After you make these changes, wait at least 15 minutes for these changes to replicate from Active Directory to the metabase. After that time, the Cluster service IsAlive checks should be successful.