We are setting up a new Exchange 2010 environment. We will have individual servers for each role. 2 CAS Servers, 2 HUBS, 3x Mailbox.
The CAS server will be front-ended with a HW LB, so we will not be using NLB. We will set the CAS in a CAS Array.
We are considering putting two NICS in the CAS and HUB servers. I'll call them the "Front End" and "Back End" NICs.
For the CAS servers one which will be facing towards the HW LBs (Front End) and ultimately the Internet to handle Internet based Client Access, which will be the only Client Access we will have for OutLook Anywhere and OWA, etc. The other NIC will be for the Back End MAPI network connecting to the mailbox and hub servers, etc. For the HUBs one will face the Internet for SMTP in/out and the other the MAPI network.
I have a few things I am trying to figure out with this approach.
1. Is it necessary and/or best practice to have two NICS in the CAS and/or HUB servers?
2. The "Internet Facing" NICS will have the gateway set to the FW/LB while the "backend" NIC will have no gateway, seeing as all the other Exchange servers are on the same subnet. That should be fine for now, but what if we put Exchange servers in another Data Center and need to and split a DAG across, and perhaps want to provide CAS and HUB servers from the secondary data center if the primary fails. Do we have to make sure that the CAS and HUB servers communicate via the MAPI nework rather than going out the "front-end"?
3. Finally, on the FW/LB facing NICS, should they be registered in AD DNS. I suspect note because we want all the MAPI traffic hitting the "backend" NICs.
The CAS server will be front-ended with a HW LB, so we will not be using NLB. We will set the CAS in a CAS Array.
We are considering putting two NICS in the CAS and HUB servers. I'll call them the "Front End" and "Back End" NICs.
For the CAS servers one which will be facing towards the HW LBs (Front End) and ultimately the Internet to handle Internet based Client Access, which will be the only Client Access we will have for OutLook Anywhere and OWA, etc. The other NIC will be for the Back End MAPI network connecting to the mailbox and hub servers, etc. For the HUBs one will face the Internet for SMTP in/out and the other the MAPI network.
I have a few things I am trying to figure out with this approach.
1. Is it necessary and/or best practice to have two NICS in the CAS and/or HUB servers?
2. The "Internet Facing" NICS will have the gateway set to the FW/LB while the "backend" NIC will have no gateway, seeing as all the other Exchange servers are on the same subnet. That should be fine for now, but what if we put Exchange servers in another Data Center and need to and split a DAG across, and perhaps want to provide CAS and HUB servers from the secondary data center if the primary fails. Do we have to make sure that the CAS and HUB servers communicate via the MAPI nework rather than going out the "front-end"?
3. Finally, on the FW/LB facing NICS, should they be registered in AD DNS. I suspect note because we want all the MAPI traffic hitting the "backend" NICs.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 2 Comments.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.