Hi,
I've one DAG with 6 servers.
CAS and MBX are installed on the same servers, running Exchange 2013 SP1 on Windows Server 2012 R2
DAG is configured without a cluster administrative access point.
Our hardware loadbalancers can be configured to do NAT or Direct Server Return (DSR).
The loadbalancer runs within the same subnet as the Exchange servers.
Yesterday I switched from using NAT to DSR. To do that I've added a loopback adapter and gave it the same IP as the load balancers virtual server + Subnet 255.255.255.255
Then I allowed the Exchange server to process the packets.
netsh interface ipv4 set interface "team" weakhostreceive=enabled
netsh interface ipv4 set interface "loopback" weakhostreceive=enabled
netsh interface ipv4 set interface "loopback" weakhostsend=enabled
Everything seemed to work fine and the logs showed client ip addresses instead the load balancer ip address connecting to the server.
After checking the Eventlogs I saw that this broke my DAG-replication.
Cluster network 'Cluster Network 3' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Any idea how to fix this?
I like the idea of using DSR and see real client ips or are you all using NAT?
Thank you.
Kind regards,
Carsten
Name : dag1
Servers : {ex1, ex2, ex3, ex4, ex5, ex6}
WitnessServer : witnesseerver.domain.com
WitnessDirectory : C:\Witness\dag.domain.com
AlternateWitnessServer :
AlternateWitnessDirectory :
NetworkCompression : InterSubnetOnly
NetworkEncryption : InterSubnetOnly
ManualDagNetworkConfiguration : False
DatacenterActivationMode : Off
StoppedMailboxServers : {}
StartedMailboxServers : {}
DatabaseAvailabilityGroupIpv4Addresses : {255.255.255.255}
DatabaseAvailabilityGroupIpAddresses : {255.255.255.255}
AllowCrossSiteRpcClientAccess : False
OperationalServers :
PrimaryActiveManager :
ServersInMaintenance :
ServersInDeferredRecovery :
ThirdPartyReplication : Disabled
ReplicationPort : 64327
NetworkNames : {}
WitnessShareInUse :
DatabaseAvailabilityGroupConfiguration :
AutoDagSchemaVersion : 1.0
AutoDagDatabaseCopiesPerDatabase : 1
AutoDagDatabaseCopiesPerVolume : 1
AutoDagTotalNumberOfDatabases : 0
AutoDagTotalNumberOfServers : 0
AutoDagDatabasesRootFolderPath : C:\ExchangeDB
AutoDagVolumesRootFolderPath : C:\ExchangeVol
AutoDagAllServersInstalled : False
AutoDagAutoReseedEnabled : True
AutoDagDiskReclaimerEnabled : True
AutoDagBitlockerEnabled : False
ReplayLagManagerEnabled : False
MailboxLoadBalanceMaximumEdbFileSize :
MailboxLoadBalanceRelativeLoadCapacity :
MailboxLoadBalanceOverloadedThreshold :
MailboxLoadBalanceUnderloadedThreshold :
MailboxLoadBalanceEnabled : False
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=dag1,CN=Database Availability Groups,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=Company,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity : dag1
ObjectCategory : domain.com/Configuration/Schema/ms-Exch-MDB-Availability-Group
ObjectClass : {top, msExchMDBAvailabilityGroup}
OrganizationId :
OriginatingServer : dc1.domain.com
IsValid : True
ObjectState : Unchanged