question

SumitChawla-7194 avatar image
0 Votes"
SumitChawla-7194 asked jiayaozhu-MSFT commented

DFS Namespace Server Role on Azure VM configured failover cluster failing IP addressing issue

I am trying a POC to have high available standalone DFS namespace server. For this, I have configured, 2 VM’s on Azure with a shared premium disk and provisioned a cluster. Both the VM’s are on-prem domain joined through Express Route.
The Ip address of both the VM’s lie in the same subnet(x.x.x.45. and x.x.x.47). I have used windows server 2019 so cluster uses distributed server name and takes the Ip address of the active VM in the cluster. When I configure the DFS Namespace Server Role on this cluster, it provisions a Server (Network Name); dfs-test is the name in my case. I assign a static Ip address to this server name (dfs-test) and the Ip address(x.x.x.44) also belongs to the same subnet. However, I see corresponding to this action inside VM, a network interface is created in the Azure and it is not attached to any machine. Also, I see that a computer object is created in AD for dfs-test as well an entry in DNS is created in corp DNS server for dfs-test pointing to x.x.x.44. The issue is I want to access this location on network \\dfs-test (\\x.x.x.4) which is not happening. I am anticipating since this IP address is not assigned to any machine, it is not routed anywhere. The ping test also fails from other machines in the same domain. Any idea, what is the missing configuration here which allows me to access this DFS role (dfs-test) with Ip address x.x.x.44 over the network.

azure-virtual-machineswindows-server-clusteringwindows-server-storage
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

I would like to check if the reply could be of help? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

Best Regards,
Joan

0 Votes 0 ·

1 Answer

jiayaozhu-MSFT avatar image
0 Votes"
jiayaozhu-MSFT answered jiayaozhu-MSFT commented

Hi,

Thanks for posting on our forum!

Firstly, I need to identify whether your issue is more related with Azure platform or with Windows OS platform. In this case, I need to gain a deeper insight of your network configuration, both in Azure and in Windows. Like where do you set your static ip (x.x.x.44)? In Windows OS or in Azure. If it is in Windows, it is normal that you cannot see it in Azure. Anyway, please give me the screenshots for network configuration for DFS and in Azure respectivelly and the screenshots for anything that you think is weird, like:

"Also, I see that a computer object is created in AD for dfs-test as well an entry in DNS is created in corp DNS server for dfs-test pointing to x.x.x.44. The issue is I want to access this location on network \\dfs-test (\\x.x.x.4) which is not happening."

Last but not least, would you please repeat your demand? Which do you want us to help you solve with?

Thanks for your support and understanding! The more useful information we can get, the more efficient help you can receive.

BR,
Joan


If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

117120-1st.png

Here are more details as per the picture above:
VM1 on azure: x.x.x.45
VM2 on azure: x.x.x.47

Both the above VM's are on-prem domain joined through express route.
Both the above VM's are reachable from other on-prem machines in the domain.
Both the above VM's form a cluster: dfs-test-cluster.x.x.x.com
Role configured on cluster: DFS Namespace
Role Name: dfs-test
IP address : x.x.x.44 (statically assigned from within windows)

Other information: When we assign static IP address to the dfs-test from windows, it creates a Network Interface in Azure with the same IP address but does not attach it to any VM.
117211-2nd.png

Question: How can we reach dfs-test(x.x.x.44) from other on-prem machines since that will be our server name while for accessing shares i.e. \\dfs-test\fixes?

Goal: Need to have high availability DFS-N server, therefore, if x.x.x.45 fails, x..x.x.47 should become active node in the cluster and we should be able to reach x.x.x.44 through x.x.x.47.


0 Votes 0 ·
1st.png (214.0 KiB)
2nd.png (51.4 KiB)

Hi,

Thanks for your patience!

After long time research, I suppose this issue may be more related with Azure net, you can re-post your issue to this forum:
https://docs.microsoft.com/en-us/answers/topics/azure-virtual-network.html

Besides, since your environment is a complex one that may need real-time telecommunication remotely with our supporters, you can open a case with our senior supporters. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below.
Global Customer Service phone numbers:
https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

Thanks for your support and understanding!

BR,
Joan

0 Votes 0 ·