Hi Quote:Do we need the DAG IP assigned to this adapter? A: No you neednt. Quote: if it's not required, how can I get rid of it? A: For every subnet a DAG members MAPI NIC is in, we must obtain a DAG IP. This DAG IP is a separate IP than is located on the MAPI NICs themselves. You cant get rid of it. This article is about how to set it and failover. I think it will be helpful to you. TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Terence Yu TechNet Community Support

Hi Quote:Do we need the DAG IP assigned to this adapter? A: No you neednt. Quote: if it's not required, how can I get rid of it? A: For every subnet a DAG members MAPI NIC is in, we must obtain a DAG IP. This DAG IP is a separate IP than is located on the MAPI NICs themselves. You cant get rid of it. This article is about how to set it and failover. I think it will be helpful to you. TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Terence Yu TechNet Community Support

Hi, You dont need to use the IP of DAG for the NIC. If you want to change you can give try to change DAG IP You can assign IP to DAG either while creating the DAG using below cmdlet. New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer EXHUB2 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8,192.168.0.8 Or You can change the IP of DAG, you can use below cmdlet. set-databaseavailabilitygroup -name DAG1 -databaseavailabilitygroupIPAddress 10.1.20.X (as per your network). This way you can give a shot to separate the things.Abhijeet D

Hi, You dont need to use the IP of DAG for the NIC. If you want to change you can give try to change DAG IP You can assign IP to DAG either while creating the DAG using below cmdlet. New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer EXHUB2 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8,192.168.0.8 Or You can change the IP of DAG, you can use below cmdlet. set-databaseavailabilitygroup -name DAG1 -databaseavailabilitygroupIPAddress 10.1.20.X (as per your network). This way you can give a shot to separate the things.Abhijeet D

Hi, You dont need to use the IP of DAG for the NIC. If you want to change you can give try to change DAG IP You can assign IP to DAG either while creating the DAG using below cmdlet. New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer EXHUB2 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8,192.168.0.8 Or You can change the IP of DAG, you can use below cmdlet. set-databaseavailabilitygroup -name DAG1 -databaseavailabilitygroupIPAddress 10.1.20.X (as per your network). This way you can give a shot to separate the things. Abhijeet D He does have them separate - one IP for the NIC and the other IP is the DAG. The OP's question is should the DAG IP show up in ipconfig and where it is coming from. If you don't specify a static IP at DAG creation time, then it will use DHCP. The IP is required for failover clustering and should be present. Also note that SP1 allowed a static IP to be set on the DAG from EMC, in RTM it was only possible in EMS (as you show in the script above). Can you confirm that is indeed your question, ILoveExchange? (Great name BTW!) Cheers, Rhoderick

Hi, You dont need to use the IP of DAG for the NIC. If you want to change you can give try to change DAG IP You can assign IP to DAG either while creating the DAG using below cmdlet. New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer EXHUB2 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8,192.168.0.8 Or You can change the IP of DAG, you can use below cmdlet. set-databaseavailabilitygroup -name DAG1 -databaseavailabilitygroupIPAddress 10.1.20.X (as per your network). This way you can give a shot to separate the things. Abhijeet D He does have them separate - one IP for the NIC and the other IP is the DAG. The OP's question is should the DAG IP show up in ipconfig and where it is coming from. If you don't specify a static IP at DAG creation time, then it will use DHCP. The IP is required for failover clustering and should be present. Also note that SP1 allowed a static IP to be set on the DAG from EMC, in RTM it was only possible in EMS (as you show in the script above). Can you confirm that is indeed your question, ILoveExchange? (Great name BTW!) Cheers, Rhoderick

Well I suggested this if he can change DAG IP so he can give try to get rid of IP which is being shown in NIC ipconfig which is actually of DAG. Yes he can do it through EMS or EMC in SP1. I love EMS :D so in script. Thanks I like mhy name toooo :DAbhijeet D

Well I suggested this if he can change DAG IP so he can give try to get rid of IP which is being shown in NIC ipconfig which is actually of DAG. Yes he can do it through EMS or EMC in SP1. I love EMS :D so in script. Thanks I like mhy name toooo :DAbhijeet D

Why the DAG IP showing in the NIC configuration? On our Mailbox Server 2 it's not showing in IP Configuration on Maibox Server 1. The DAG has assigned a Static IP.

Hi Dag IP will show on active node. There is no problem. Terence Yu TechNet Community Support

Hi Dag IP will show on active node. There is no problem. Terence Yu TechNet Community Support

From http://technet.microsoft.com/en-us/library/dd351172.aspx When creating a DAG, you provide a unique name for the DAG of up to 15 characters. In addition to providing a name for the DAG, you must also assign one or more IP addresses (either IPv4 or both IPv4 and IPv6) to the DAG. The IP addresses you assign must be on the subnet intended for the MAPI network and must be available for use. You do not bind the IP to the NIC, that is a function of Windows Failover Cluster, and the IP will move to the other server if the cluster group moves. Remember that DAG needs to leverage some of the capabilities of clustering "under the hood" so to speak. Cheers, Rhoderick

Why the DAG IP showing in the NIC configuration? On our Mailbox Server 2 it's not showing in IP Configuration. The DAG has assigned a Static IP.

Because the cluster group can only be brought online in a single node in the cluster at a given time. Open the failover cluster manager, and look in the cluster core resources section - you will see the IP listed there. That IP will also show on the active node when you run ipconfig/ Along the top you can see the current server. This is a sample from one of my labs: If you want run the following to see who has the cluster group, and thus is the Primary Active manager in EMS: Get-DatabaseAvailabilityGroup -status| select Name, PrimaryActiveManager Look at the PrimaryActiveManager entry, that will be the box with the DAG IP visible. make sense?Cheers, Rhoderick

Hi, You dont need to use the IP of DAG for the NIC. If you want to change you can give try to change DAG IP You can assign IP to DAG either while creating the DAG using below cmdlet. New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer EXHUB2 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8,192.168.0.8 Or You can change the IP of DAG, you can use below cmdlet. set-databaseavailabilitygroup -name DAG1 -databaseavailabilitygroupIPAddress 10.1.20.X (as per your network). This way you can give a shot to separate the things.Abhijeet D

Hi - We have Exchange 2010 with 2 node DAG MBX01 and MBX02. I have setup 2 NICS in a Team using Broadcom Advanced Control Suite 3 on both Mailbox Servers in the DAG. When I do ipconfig /all on MBX01 I see that it has assigned two IPv4 Addresses in Team adapter both are preferred. The second IP is our DAG IP. Ex. Ethernet adapter Team 1 - Corp: Connection-specific DNS Suffix . : Description..............................: BASP Virtual Adapter Physical Address......................:F0-4D-A2-0A-40-01 DHCP Enabled..........................: No Autoconfiguratjion Enabled.........:Yes IPv4 Address.............................:10.1.20.100(Preferred) Subnet Mask..............................:255.255.254.0 IPv4 Address..............................:10.1.20.30(Preferred) (This is DAG IP) Subnet Mask...............................:255.255.254.0 Default Gatgeway.........................10.1.20.10 DNS Servers.................................10.1.20.1 10.1.20.2 NetBIOS over Tcpip.......................Enabled I have no idea how it got assigned. My Question is: Do we need the DAG IP assigned to this adapter? if it's not required, how can I get rid of it? Thank you,

Hi Dag IP will show on active node. There is no problem. Terence Yu TechNet Community Support

Hi, You dont need to use the IP of DAG for the NIC. If you want to change you can give try to change DAG IP You can assign IP to DAG either while creating the DAG using below cmdlet. New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer EXHUB2 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIPAddresses 10.0.0.8,192.168.0.8 Or You can change the IP of DAG, you can use below cmdlet. set-databaseavailabilitygroup -name DAG1 -databaseavailabilitygroupIPAddress 10.1.20.X (as per your network). This way you can give a shot to separate the things. Abhijeet D He does have them separate - one IP for the NIC and the other IP is the DAG. The OP's question is should the DAG IP show up in ipconfig and where it is coming from. If you don't specify a static IP at DAG creation time, then it will use DHCP. The IP is required for failover clustering and should be present. Also note that SP1 allowed a static IP to be set on the DAG from EMC, in RTM it was only possible in EMS (as you show in the script above). Can you confirm that is indeed your question, ILoveExchange? (Great name BTW!) Cheers, Rhoderick

Well I suggested this if he can change DAG IP so he can give try to get rid of IP which is being shown in NIC ipconfig which is actually of DAG. Yes he can do it through EMS or EMC in SP1. I love EMS :D so in script. Thanks I like mhy name toooo :DAbhijeet D

Hi Quote:Do we need the DAG IP assigned to this adapter? A: No you neednt. Quote: if it's not required, how can I get rid of it? A: For every subnet a DAG members MAPI NIC is in, we must obtain a DAG IP. This DAG IP is a separate IP than is located on the MAPI NICs themselves. You cant get rid of it. This article is about how to set it and failover. I think it will be helpful to you. TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Terence Yu TechNet Community Support

Hi If someone's advice is helpful to you, please mark his case.Terence Yu TechNet Community Support

Hi If someone's advice is helpful to you, please mark his case.Terence Yu TechNet Community Support

Hi If someone's advice is helpful to you, please mark his case.Terence Yu TechNet Community Support