"Request timed out" error when you try to ping a Clustered Name that runs on Azure IaaS VMs
Consider the following scenario:
- You set up a Windows Server Failover Cluster on Azure IaaS virtual machines (VMs).
- You configure cluster Network Name resources for the Cluster Name or client access points for applications.
- At a command prompt, you try to ping these IP addresses from VMs that do not currently own the cluster Network Name resources.
This is expected behavior when Failover Cluster networking interacts with the Azure networking. Clustered IP address resources and their associated Network Name resource differ from a regular IP address. Clustered IP address resources have very limited functions and do not respond to ping requests over ICMP.
The IP address for Cluster Name is intended to be an endpoint for management of the cluster and is not for network communication. If the Cluster IP Address resource has an invalid IP address, it cannot be used for remote cluster management. Instead, you can manage the cluster locally by specifying a local connect that has a period (.) or by specifying a name for the node.
The IP address for a client access point is an Azure Load Balancer address. It's associated with endpoints or back-end pools in Azure that have specific ports that are used by clustered resources.
For more information, see the following Server & Management Team Blog article:
ID Artikel: 3190161 - Tinjauan Terakhir: 09/12/2016 23:33:00 - Revisi: 4.0