Hello everyone,
I am conducting an Exchange migration from 2007 to 2013. The client have 4 geographical site and each of those site have an Exchange CAS server on it. The sites
have also DCs on each of them.
There's two types of connection between sites one is MPLS that's 50MBPs and the other is p2p that's 2mbps. Client wants to have only 2 Exchange 2013 Server with
all the roles collocated on them and DAG between them.
I already have installed and configured DAG on the servers. One server is located in the Central data center and the other is located on a second geographical
site that also have a disaster recovery data center.
Client wants to configure the MAPI network on Exchange 2013 to use the P2P 2mbps connection and use the MPLS 50mbps connection for the replication NIC.
The problem is that both networks MPLS and P2P have the same IP subnet, same gateway e.g. (10.1.1.0/16) but a range of those IPs are configured on the router to
use the MPLS connectivity.
I have tried to add static route to the replication network to use the gateway but when trying to add a copy of a centralized database to the DAG. the DAG copies
the connection over the P2P line.
Is it possible to configure this with the same subnet or do I need to have the mpls connection on a totally different network and subnet?
I would appreciate all your suggestions and I am very sorry for my terrible explanation because I am my self confused about their network topology.
I will prepare a visio diagram of the network, IPs and everything to clear everything o
Exchange 2013 Migration in a complicated network environment
March 14th, 2015 7:00pm
Hi.
If you read documentation, then you know, that for DAG must be two subnets.
Here are the two networks and how they are routed to you depends on your network infrastructure and end architecture Exchange.
Planning for high availability and site resilience
Managing database availability groups
PS> I'm recomendet used BPA and exampel from documentation in the industrial plant.
Free Windows Admin Tool Kit Click here and download it now
March 14th, 2015 9:48pm
Hello Mohammed,
Good Day..
From the above information seems that you are planning for DR Site with DAG. Would recommend you to please follow the below articles, which will guide you to set the DAG Failover and Failback with DR site.
Regards,
MCP, MCTS,MCITP |Exchange Server
Praveen Kumar
---------------------------------------------------------------------
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts @ Techrid.com
March 14th, 2015 11:09pm
Hi Paveen, I am not planning for a DR. I already planned and it's active between both sites! my question is more about networking than Exchange.
I am just asking if it's possible for Exchange or the Windows 2012R2 Exchange is installed on to distinguish between the two lines (MPLS or P2P) if they are on the same subnet.
When I added the static route on Exchange server, I do trace route and the ping of the IP gets out on the correct gateway for the correct line however, when I make a copy of a database on a second member of the DAG which is on a different site the database copies on the P2P (2mbps connection) not on the MPLS.
I would appreciate if anyone can help me with this.
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2015 2:53am
I have solved the issue, it was very simple but due to lack of knowledge about networking it got complicated. the way I have configured the replication networks between both sites was that each replication NIC on each site should have a different subnet that configured on the MPLS network with the high speed and bandwidth. they must be different on each site.
For each replication NIC a persistent static route should be configured on Exchange server to tell the NIC where to direct traffic exactly.
After configuring the subnets on the replication NIC, I added the static routes and the replication started to work flawlessly.
This is the static route command that I run on the first machine on the first site, it tells the Replication NIC to direct traffic to the subnet network on the second site through the gateway 10.1.1.1
route -p add 10.5.1.0 MASK 255.255.0.0 10.1.1.1
On Exchange on the second site, I had to run the same command as well
route -p add 10.1.1.0 MASK 255.255.0.0 10.5.1.1
thanks everyone for the help.
April 3rd, 2015 4:29am
This topic is archived. No further replies will be accepted.
Other recent topics
