Whenever you
add additional network to the DAG network for example additional interface for
ISCSI, additional LAN Interface for Storage or additional LAN interface to take
backup this may leads to collide with Exchange 2013 DAG network automatically
and may result issue as follows,
- · Random disrupt on the email connecitivity
- · Issue on the email flow
- · Queue in the transport service.
This can be
verified on running the cmdlet
Get-DatabaseAvailabilityGroupNetwork
| format-list Subnet
It shows as
Misconfigured.The cause for the issue is
by default in Exchange 2013, DAG networks are automatically configured by the
system. Make sure the binding of the network interface that is newly added
other than default DAG networks need to be moved below. This can be achieved on
selecting network connection – advance connection - bindings
Solution
1. Enable the DAG network as manual
Set-DatabaseAvailabilityGroup
-ManualDagNetworkConfiguration $true
2. Disabling the network in DAG
Set-DatabaseAvailabilityGroupNetwork
-Identity DAG2\DAGNetwork02 -ReplicationEnabled:$false -IgnoreNetwork:$true
3. Verify the DAG network
Get-DatabaseAvailabilityGroupNetwork
| format-list Subnet
4. Verification of Network role Status in Cluster
Check the
Network role status in the cluster service (New Network 01)
if Role 0 (0×0) tells the cluster not
to use the network;
if Role 1 (0×1) tells the cluster that
this is a private network;
if Role 3 (0×3) tells the cluster that
this is a public network.
C:\Windows\system32>cluster
network 'New Network 01' /prop
Listing
properties for 'New Network 01':
T
Network Name Value
-- -------------------- ------------------------------
-----------------------
SR Cluster Network 1 Name Cluster Network 1
MR Cluster Network 1 IPv6Addresses
MR Cluster Network 1 IPv6PrefixLengths
MR Cluster Network 1 IPv4Addresses 100.200.26.0
MR Cluster Network 1 IPv4PrefixLengths 24
SR Cluster Network 1 Address 100.200.26.0
SR Cluster Network 1 AddressMask 255.255.255.0
S
Cluster Network 1 Description
D
Cluster Network 1 Role 3 (0x3)
D
Cluster Network 1 Metric 10000 (0x2710)
D
Cluster Network 1
AutoMetric 1
(0x1)
If role is
not 0 then set the Role to 0:
Cluster network 'New
Network 01' /prop Role=0
5. Verifying the Cluster properities
[PS]
C:\Windows\system32>cluster /prop
6. Listing the Cluster Network properities
[PS]
C:\Windows\system32>cluster network /prop
7. Verifying the Cluster Network Interface status
[PS]
C:\Windows\system32>cluster netint
8. Checking the Quorum Type
[PS]
C:\Windows\system32>cluster /quorum
9. Check out the incoming and Outgoing Connection status
Get-MailboxDatabaseCopyStatus
* -ConnectionStatus | Select-Object MailboxServer, ID, *Connections, *network |
Export-Csv C:\temp\repl.csv
10. Check the all the network informated connected to the server
Get-DatabaseAvailabilityGroupNetwork
-Server | Select Name, MapiAccessEnabled,
ReplicationEnabled, IgnoreNetwork
No comments:
Post a Comment