Skip to main content
NetApp Knowledge Base

Object Store Availability Timeout During Tiering Setup

  1. Last updated
  2. Save as PDF
Views:
28
Visibility:
Public
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

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.