Here is general guidelines along with MS best practices how to configure NIC card settings when setting up Exchange 2010 DAG servers. Use this as reference for your deployments.
Exchange 2010–Mailbox DAG Network configurations for the purpose of this document we will call
- NIC1= Production (it has DGW configured)
- NIC2=Replication (it does not have DGW, Use NetSH to configure static persistent route)
NIC Binding order = Production NIC is listed first, Replication NIC is second other NIC if available in any order….
| DAG Members (Network Adaptor Settings) | NIC1 = Production (MAPI Access, Outlook users ) | NIC2 = Replication (Seeding and heartbeat purpose) |
| Client for Microsoft Networks | Enabled | Unchecked |
| QoS Packet Scheduler | Optional | Optional |
| File and Printer Sharing for Microsoft Networks | Enabled | Unchecked |
| Internet Protocol Version 6 (TCP/IP v6) | Enabled (Optional ) | Optional |
| Internet Protocol Version 4 (TCP/IP v4) | Enabled | Enabled |
| Link-Layer Topology Discovery Mapper I/O Driver | Enabled | Enabled |
| Link-Layer Topology Discovery Responder | Enabled | Enabled |
| Register Connection in DNS | Enabled | Unchecked |
| Default Gateway | Enabled | Disabled |
| NIC Binding order, ( go to Network Connections, Advance, & Advance Settings , Press ALT key to see the advance settings, Make sure the **replication NIC** is listed on TOP | Listed First | Listed second |
Replication NIC Card (Private network)
- · NIC BINDINGS
- · Go to Network Connections
- · Advance
- · Advance Settings
- · Make sure the replication NIC is listed on TOP
| NetSH Interface ip show route |
DGW = 10.80.3.1 in this example
| netsh Interface ipv4 add route 10.80.3.102/32 "inside" 10.80.3.1 store=persistent |
To delete any static route
| netsh interface ipv4 delete route 10.0.0.0/8 "Internal" 10.0.0.5 |
See the Static route
| netsh interface ip show route |
Reset the Interface ( very powerful)
| netsh interface tcp reset |
Respectfully,
Oz Casey, Dedeal ( MVP north America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)
2 comments:
Good article but your NIC binding order contradicts itself. You correctly state in the table that the Production Network should be 1st in the binding order, with the Replication network 2nd but then you've added a comment:
"Make sure the **replication NIC** is listed on TOP" - which is not correct.
Just to back up the above comment.
The NIC binding order info is incorrect: You can only have *one* NIC at the top of the binding order.
Post a Comment