topic Adding a cloud-tier from remote cluster ends with timeout in Object Storage

Adding a cloud-tier from remote cluster ends with timeout

kombayn — Mon, 22 Jul 2024 10:20:26 GMT

Hello

I've created an object store on one cluster and trying to add it as a cloud tier on other cluster to create fabric-pool and offload some data from primary cluster. I've got intercluster LIFs in singe VLAN on both clusters and they're pinging each other. I've added cloud tier on primary cluster, but when I'm trying to attach local tiers to it I've got "ERROR: Cannot verify availability of the object store from node xxx. Reason: Connection timeout.." I'm struggling to find a reason for this timeout - I've checked and renewed access keys, I've checked certificate and cannot find a reason.

Re: Adding a cloud-tier from remote cluster ends with timeout

Bharath1 — Tue, 23 Jul 2024 06:38:54 GMT

Hi there!
Since you mentioned that the intercluster LIFs are pinging each other, it's likely not a basic connectivity issue.

You can use storage profiler command to check connection and letency

cluster1::>storage aggregate object-store profiler start -object-store-name my-store -node my-node

Can you please look into this KB might help you.
Error: Cannot verify availability of the object store from node to ONTAP S3 due to hostname not resolved - NetApp Knowledge Base

Re: Adding a cloud-tier from remote cluster ends with timeout

kombayn — Tue, 23 Jul 2024 08:58:21 GMT

Hi there. Thanks for the useful command.

I've already found the root cause. One of my intercluster LIFs had a service policy "default-management" instead of "intercluster". Once I've changed the service-policy connection went smoothly.