Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, December 20, 2016 9:26 PM
Some confusion for me in guidance for NIC's and IP's for Exchange 2016, e.g. "Rapid Migrating Guide from Exchange 2010 to Exchange 2016" and "Preferred Architecture" seem to indicate different NIC setups. --The guides are for significantly different scenarios, so that's not really the point. [Rapid...] indicates traditional, multi-nic; howevere, [PA] indicates only one NIC.
If existing Exchange 2010 3 NICs (repl net, mapi net, certauth net) - will the added 2016 servers require more than one NIC? When administering the server, we RDP to the mapi net's IP. the cert auth is a separate NIC for iphone certificate authentication. Seems like I can collapse from three nic's to two, but not all the way to one. I.e. one nic for repl, mapi, and [RDP] and one for certauth? Does this seem right? Despite the physical nics, it seems I still need all three separate subnets, yes?
All replies (5)
Tuesday, December 20, 2016 9:43 PM
nope you don't need three nic. You are good with one NIC only.
FYI there no more MAPI in 2016. Everything is HTTP based.
Where Technology Meets Talent
Tuesday, December 20, 2016 9:46 PM
OK - so *duh* on me about MAPI. :) Too caught up in the conversion part. Still two IP addresses though? two separate networks, right?
Tuesday, December 20, 2016 9:51 PM
You CAN and YOU can't it is your choice. Depending how many user and how much traffic you have.
If you have few hundred users then keep it simple but if you have thousands of users then you keep the two separated.
check this out
In previous versions of Exchange, we recommended at least two networks (one MAPI network and one Replication network) for DAGs. In Exchange 2016, multiple networks are supported, but our recommendation depends on your physical network topology. If you have multiple physical networks between DAG members that are physically separate from one another, then using a separate MAPI and Replication network provides additional redundancy. If you have multiple networks that are partially physically separate but converge into a single physical network (for example, a single WAN link), then using a single network (preferably 10 gigabit Ethernet) for both MAPI and Replication traffic is recommended. This provides simplicity for the network and the network path.
https://technet.microsoft.com/en-us/library/dd638104(v=exchg.160).aspx#NR
- Each member of the DAG must have at least one network adapter that's able to communicate with all other DAG members. If you're using a single network path, we recommend that you use a minimum of 1 gigabit Ethernet, but preferably 10 gigabit Ethernet. In addition, when using a single network adapter in each DAG member, we recommend that you design the overall solution with the single network adapter and path in mind.
Where Technology Meets Talent
Tuesday, December 20, 2016 10:06 PM
OK - cool, I recognize the PA, but there are parts in here that confuse me " If you're using a single network path, we recommend that you use a minimum of 1 gigabit Ethernet, but preferably 10 gigabit Ethernet. In addition, when using a single network adapter in each DAG member, we recommend that you design the overall solution with the single network adapter and path in mind."
1. We have a two-site setup currently with Exchange 2010, but we're not connected at 1GB across the WAN. Who is?
2. What does it mean "with the single network adapter and path in mind" mean?
Also, "If you have multiple networks that are partially physically separate but converge into a single physical network (for example, a single WAN link)" is unclear. For us, each site is in it's own subnet, but we are routed so that all function pretty much like they are in the same network segment.
3. I *guess* that's what is meant by "single physical network." ??
Finally, for cert auth for iphones, it had to be offloaded to a different nic and iis in exchange 2010, is this unchanged in 2016?
Tuesday, December 20, 2016 10:29 PM
did you look at the Storage Calc?
One thing you also need to make sure that the latency between the two DC should be than 50 msc.
1. We have a two-site setup currently with Exchange 2010, but we're not connected at 1GB across the WAN. Who is? No one , a very few but latency has to be less than 50msc.
2. What does it mean "with the single network adapter and path in mind" mean? Path -- i'd ask Exchange Team.
3. I *guess* that's what is meant by "single physical network." ?? they have to be on the same physical subnetwork don't put them in different subnets.
Where Technology Meets Talent