Assigning Static IP Address For Database Availability Group…

by Rajith Jose Enchiparambil on January 17, 2010

Database Availability Group (DAG) uses an IP address assigned by a DHCP server by default. Please check my previous articles about configuring DAG and points to note if you are not familiar with DAG. You can use the exchange console or the shell to configure the properties of a DAG, including the witness server and directory used by the DAG. The shell enables you to configure the DAG properties that are not available in the console. As an administrator, you can assign a static IP address for the DAG, though it is not a requirement. DAG doesn’t really care as long as it has an IP address and the name of the DAG is resolvable. The DAG name is not used by users or admins anyway. It is only used by the system for internal communication.

To find the current ip address of the DAG, run the command

Get-DatabaseAvailabilityGroup -identity "dagname" | fl *ip*

To configure a static IP address (say 192.168.1.104) for the DAG, run

Set-DatabaseAvailabilityGroup -identity "dagname" -DatabaseAvailabilityGroupIpAddress 192.168.1.104

If you have a DAG that spans multiple subnets (for high availability), you can configure multiple ip addresses for the DAG. To configure multiple ip addresses, run

Set-DatabaseAvailabilityGroup -identity "dagname" -DatabaseAvailabilityGroupIpAddress 192.168.1.104, 192.168.2.104

SUBSCRIBE FOR DAILY ARTICLE UPDATES VIA EMAIL

Get the published articles delivered straight to your inbox. Your details will not be passed to any third party company.

Rajith Jose Enchiparambil

Exchange Architect, Blogger, Husband & Dad. I have been in IT for the last 11 years, with Exchange Server becoming the prime area in the last few years. I am active on TechNet forums & Experts Exchange.

View all contributions by Rajith Jose Enchiparambil

Using Get-SetupLog.ps1 To Analyze Setup Logs In Exchange 2013

A handy script for analyzing Exchange setup logs, Get-SetupLogs.ps1 has not been shipped with Exchange 2013. This excellent script parses through the setup log file in C:\ExchangeSetupLogs folder and displays an easy to read output in the shell with different colours for warnings and error. This has been around since Exchange 2007, but is missing [...]
Read More
The Migration Mailbox For The Organization Is Either Missing Or Invalid Error During Exchange 2013 Mailbox Move

You get the following error while trying to move mailbox locally in Exchange 2013. The Migration mailbox for the organization is either missing or invalid. I was contacted about this error by one of my blog readers after posting Cannot Open Microsoft System Attendant Mailbox Error During Exchange 2013 Mailbox Move. In this case, the [...]
Read More
Cannot Open Microsoft System Attendant Mailbox Error During Exchange 2013 Mailbox Move

A local mailbox move in Exchange 2013 fails with the error that the System Attendant Mailbox cannot be opened. I thought System Attendant was a thing of the past! Exchange 2013 doesn’t have system attendant mailbox or even the System Attendant service (mad.exe). But, the error clearly mentions about the failure to open the [...]
Read More
How To Find Which Store Worker Process Is Responsible For A Mailbox Database In Exchange 2013

Exchange 2013 has a new store named the Managed Store. In order to provide failure isolation in the database level in 2013, Microsoft has introduced two new processes as part of the managed store concept. First is the Store Worker Process(Microsoft.Exchange.Store.Worker.Exe) which does the same job that store.exe handled in previous versions. The only difference [...]
Read More
Upload GAL Photos Using Exchange 2013 OWA Options (ECP)

The “self service” option in OWA 2013 (ECP) has been enhanced with the option for uploading GAL photo by the end user. In Exchange 2010 ECP, end users were able to edit their contact details, address etc depending on the role assignment policy. In Exchange 2013 ECP ( OWA –> Options), the end user can [...]
Read More

6 comments… add one

Manne August 22, 2012 at 9:57 pm

Hi!
Thank you for the post.

If you have servers in multiple sites (hence at least two IP-addresses) – which site should the DNS-record for the “dagname” be pointing to (since you only have one name and two IP-addresses…).

Reply edit
- Rajith Enchiparambil September 21, 2012 at 7:02 am
  
  Hi Manne,
  
  Depending on which site owns the site, Exchange will automatically change the IPs back and forth. All you need to do is add both the IPs and Exchange will take care of the rest.
  
  Reply edit
Luke October 17, 2012 at 9:42 am

Usefull Informations….

Reply edit
- Rajith Enchiparambil October 18, 2012 at 8:30 am
  
  Thanks Luke.
  
  Reply edit
Devi February 3, 2013 at 9:46 am

HI Rajith,

While changing DAG IP address from dhcp to static in production, we need any downtime ?

Thanks
Devi

Reply edit
- Rajith Enchiparambil March 6, 2013 at 8:26 pm
  
  Hi Devi,
  
  No downtime as such is required, although I would encourage you to do it out of hours.
  
  Reply edit

Assigning Static IP Address For Database Availability Group…

Rajith Jose Enchiparambil

Using Get-SetupLog.ps1 To Analyze Setup Logs In Exchange 2013

The Migration Mailbox For The Organization Is Either Missing Or Invalid Error During Exchange 2013 Mailbox Move

Cannot Open Microsoft System Attendant Mailbox Error During Exchange 2013 Mailbox Move

How To Find Which Store Worker Process Is Responsible For A Mailbox Database In Exchange 2013

Upload GAL Photos Using Exchange 2013 OWA Options (ECP)

Website Hits

Recent Comments

Archives