Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
Cluster Network Setting in Exchange 2010 DAG not getting updated

Discussion Cluster Network Setting in Exchange 2010 DAG not getting updated

  • 23 April 2012 21:34
     
     
    Masuk untuk Memilih
    0

    We have a customer with an Exchange 2010 DAG they just rebuild that have noticed the DAG’s IP no longer functions. In the failover cluster manager there is no IP set, and we are unable to set one as the incorrect network is displayed. Replication and manual failovers of the DAG are still functioning but we assume that the automatic failover will not since the cluster network name is not online.

    The DAG address should be configured as 192.168.16.200. The clustered network 1 (MAPI) is 192.168.16.x and the clustered network 2 (DAG replication) is 10.0.0.x. The failover manager only allows us to select a DAG IP from the 10.0.0.x network which is the wrong one.

    Cluster Network 1 should have this setting ticked "allow client to connect to through this network", while Cluster Network 2 should not as Cluster Network 1  should be the MAPI Network and Cluster Network 2 should be the Replication Network. We are working on the assumption this is why we cannot select an IP from 192.168.16.x because network 1 has this option unchecked.

    We have tried changing the network prioritisation manually as per this article which has made no difference.
    http://blogs.msdn.com/b/clustering/archive/2011/06/17/10176338.aspx

    Also tried changing the allow clients to connect setting directly via the registry as per this article, but the setting still reverts back .
    http://lokna.no/?p=998

    The two nodes both have 3 NICs, the two as described above (DAG and MAPI) and a third labelled primary which is on the same subnet as the MAPI one. It is the primary network (not one of the clustered networks) which has a default gateway defined. Can anyone give any  solution about this issue?

     

Semua Balasan

  • 10 Mei 2012 2:38
     
     
    Masuk untuk Memilih
    0

    I would not have two NICs on the same subnet even without two default gateways.  If you are worried about traffic volume for MAPI on a certain NIC, you could team your NICs to handle this.  What physical server do you have for Exchange?  Dell or HP?  If it's a VM, then I would not have two NICs like this and I would remove one so as to consolidate pulbic and MAPI onto one NIC.  This may be causing you the issue and it may not be. 

    When you do a 'Get-DatabaseAvailabilityGroup |fl' what does 'DatabaseAvailabilityGroupIpv4Addresses'?

    For 'Get-DatabaseAvailabilityGroupNetwork |ft identity,ignorenetwork,isvalid -auto' do you see any networks being ignore or listed as not valid?

    JAUCG

     
  • 27 Mei 2012 1:23
     
     
    Masuk untuk Memilih
    0

    Hi , The issue got resolved. The issue was "register
    this connection’s address in DNS’ setting on the NIC on each of the mailbox
    servers were missing. This article      http://blogs.technet.com/b/timmcmic/archive/2012/05/21/exchange-2010-mapping-dag-network-states-to-cluster-network-states.aspx  helped to get the issue sorted. Thanks, Imrul Emon 

     
  • 28 Mei 2012 21:07
     
     
    Masuk untuk Memilih
    0
    Good job.  Make sure to mark your question as answered so people know that this is resolved.   Thanks.

    JAUCG