Object Store Availability Timeout During Tiering Setup

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 25

Visibility:: not set

Votes:: 0

Category:: netapp_console

Specialty:: ds_cvo

Last Updated:

Applies to

NetApp ONTAP/CVO 9+
Cloud Tiering
Azure Blob Storage

Issue

During Cloud tiering setup from the NetApp Console, the following error is observed on the Networking page of the wizard:

Cannot verify availability of the object store from node "Cluster01". Reason: Connection timeout

Cause

A network connectivity issue is preventing communication from the intercluster LIF gateway to the Azure private endpoint for the object store. The likely causes are:

Missing or incorrect routing from the intercluster LIF subnet to the Azure private endpoint
Azure Private DNS not in use, and the object store does not allow public access
DNS failing to resolve the object store FQDN.
Firewall or network security group (NSG) rules blocking traffic

Solution

Ensure that the intercluster LIF subnet has a valid route to the Azure private endpoint. Perform the following checks from the ONTAP CLI to isolate the point of failure:

1. Verify DNS Resolution: Ensure the cluster can resolve the object store FQDN (note if it resolves to a Private IP).

vserver services name-service getxxbyyy gethostbyname -node <node_name> -vserver <admin_vserver> -hostname <object_store_fqdn>

2. Test the Network Path (Port 443): Test if the specific node can reach the resolved IP address on the required HTTPS port.

network test-path -node <node_name> -destination-ip <resolved_ip> -destination-port 443

3. Run a Traceroute to Isolate Drops: If the test-path fails, run a traceroute using the specific intercluster SVM that owns the intercluster LIF to see where the traffic stops.

network traceroute -vserver <node_svm_name> -lif <intercluster_lif_name> -destination <resolved_ip>

Partner Notes

partnerNotes_text

Additional Information

additionalInformation_text

Internal Notes

internalNotes_text