Exchange 2010 DAG port

The Technet site contains a nice reference to all ports used by Exchange 2010 and its various roles, as well as an overview of the firewall rules created by Exchange 2010’s setup. Very handy when you need to provide IP and port information to the network people.

One port which stands out from the rest is the port used for DAG log shipping and seeding, which is 64327 by default. Looking back at Exchange 2007 this is good; the port is static and DAGs use regular TCP, where CCR/SCR in Exchange 2007 uses 445 for log shipping (over SMB) and a dynamic port for seeding. And if it’s two things some network people hate it’s SMB and dynamic ports. On the other hand, 64327 in the dynamic range defined by IANA; according to IANA dynamic ports cannot be registered (claimed).

Fortunately, the port can be changed when required. To change the port for a DAG use the Set-DatabaseAvailabilityGroup cmdlet with the ReplicationPort parameter like this, where <n> can be any number between 1 and 65535:

Set-DatabaseAvailabilityGroup -Identity DAGID -ReplicationPort <n>.

Note that Exchange will not adjust the Windows Firewall rules accordingly, so you need to create a firewall exception on each DAG member to make replication work. Even better, you should do this before changing the DAG port to prevent interrupting the replication longer than necessary.

3 thoughts on “Exchange 2010 DAG port

  1. I see that MB server to MB server communication uses four ports total:

    TCP 135 (RPC Endpoint Mapper), TCP Dynamic (High Port RPC), UDP 3343 (CluSvc heartbeat) and TCP 64327 (Log Shipping/Seeding).

    I have Mailbox servers set up with two interfaces: one for MAPI traffic and one for DAG. My question is which interface does port 3343 use for heartbeat? Is it the MAPI or DAG interface? We’re locking down our firewall settings between data centers and I want to ensure that DAG replication still occurs after we lock the firewall down. Any assistance is appreciated!

    • To prevent single point of failure, it is best practice to have at least 2 networks enabled for cluster heartbeat. Depending on your set up, heartbeat might switch to the alternate network when communications on one network fails. How have you configured the networks in failover clustering?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s