One of my clients implemented AlwaysOn Multi-subnet listener. This is one of the message which I have heard from few other AlwaysOn availability group customers who are having multi-subnet deployment. This client reported that they are not able to bring listener online on one node, which was added newly. When they attempted to fail over AG resource in the cluster, we could see below messages reported in event logs. Let us see how we can fix errors related to no matching network.
Log Name: System
Event ID: 1045
Source: IP Address Resource
Description: IP Address Resource NT AUTHORITY\SYSTEM No matching network interface found for resource ‘Cluster IP Address’ IP address ‘10.10.10.10’ (return code was ‘5035’). If your cluster nodes span different subnets, this may be normal.
Log Name: System
Event ID: 1069
Source: Resource Control Manager
Description: Cluster resource ‘Cluster IP Address’ of type ‘IP Address’ in clustered role ‘Cluster Group’ failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Above message contains return code 5035 which means A cluster network is not available for this operation.
As we can see in the warning, this is expected since we are at a site that does not have a NIC with a 10.10.x.x IP address. This is standard behavior in multisite clusters since we have to set up a network for each subnet in use at each site to allow the cluster to properly manage bringing IP addresses online and offline based on the networks available to the cluster node we are moving to.
For failover to work, we must have two IP address, one for each subnet for Windows Cluster IP as well as AlwaysOn listener IP address.
Reference: Pinal Dave (http://blog.SQLAuthority.com)