Background:
We have about 700 on-premise Exchange users from which about 500 to 600 are active daily. Rest of our users (~10000) are on O365. We are in the process of migrating from Exchange 2010 hybrid to Exchange 2013 hybrid. We have business requirements that force
us to continue with hybrid deployment so that is not going to change.
Current on-premise environment:
2 x CAS
3x MB (3 databases in a DAG)
2 x HUB
All of these are EX2010SP3 ru5 running on virtualized 2008R2 servers. Virtualization platform is VMware 5.5.
On-premise environment for new Exchange 2013SP1:
3 virtualized 2012R2 servers with enough RAM and with MB and CAS roles in all of them. 3 databases (in a DAG).
Traffic to CAS servers is going to be loadbalanced (and maybe also SSL Offloaded) using F5 ADC if we figure out how to handle MRSproxy traffic (that cannot be SSL offloaded according to documentation).
Problem:
Our problem at the moment (besides that MRSproxy SSL offload) is that for some reason i cannot create a new working DAG for Exchange 2013, because Exchange does not recognice the other network interface.
I have configured two nics to all three servers. One nic for MAPI traffic (public), and one nic for replication (private), just like i've done dozens of times with Exchange 2010. Exchange 2013SP1 automatic DAG network configuration only adds public MAPI subnet
and if i try to add private replication subnet to DAG manually, it says "Subnet '192.168.31.0/24' isn't present in the database availability group. It will be added to the database availability group's networks, but it will have no effect until a
corresponding subnet has been physically configured on a server in the database availability group."
The weirdest thing here is that those nics are just fine and i can ping all servers using their private nics/IP's. There are no extra protocol bindings on them (removed "Client for MS Networks" and "File and printer sharing"). Binding order
is MAPI first, replication after and i have also removed "Register this connection address to DNS" from replication nic like documentation says. I'm using only IPv4, but also IPv6 is enabled, since it is not supported to disable it with Exchange
2013. All ports are open both ways in firewall to replication subnet. Replication subnet is in the same VLAN as MAPI, but it should not matter, since they are completely different subnets. There is only one gateway configured and it is the one in the MAPI
interface.
I first created a new Exchange 2013 DAG without IP (no AAP) and i thought it was the reason for this, but nothing changed after i deleted it and created a traditional DAG with IP.
Here is the output from Get-DatabaseAvailabilityGroupNetwork command:
--------------------
Get-DatabaseAvailabilityGroupNetwork dag01 | select Name,Subnets,Interfaces
Name Subnets
Interfaces
---- -------
----------
MapiDagNetwork {{xxx.xxx.xxx.0/24,Up}}
{{EXC1,Up,xxx.xxx.xxx.201}}
ReplicationDagNetwork {{192.168.31.0/24,Misconfigured}} {}
--------------------
As you can see, for some reason Exchange does not list interface for "ReplicationDagNetwork" at all, yet there is one and it has an IP configured (192.168.31.101 with mask 255.255.255.0).
Here is the screen capture of the error message:
http://i.snag.gy/yoAbn.jpg
Any ideas what is happening here and why?
Thanks in advance...