Skip to main content
NetApp Knowledge Base

Fabric pool disconnected due to invalid DNS configuration

Views:
50
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Fabricpool

Issue

  • The object-store is in unavailable state.

Cluster::*> object-store show
(storage aggregate object-store show)
Aggregate        Object Store Name Availability   Mirror Type
--------------   ----------------- -------------  -----------
aggr1_fabricpool  fabric-pool       unavailable    primary
aggr2_fabricpool  fabric-pool       unavailable    primary

  • From the event logs:-
Cluster::*> event log show -event *SG-fabric-pool-dr*
Time                Node               Severity      Event
------------------- ---------------- ------------- ---------------------------
6/13/2024 15:56:45  Node04            EMERGENCY    object.store.unavailable: Unable to connect to the object store "fabric-pool" from node 71b1612d-8292-11ed-b2bb-d039eaa29402. Reason: Operation Timedout.

 
  • Unable to ping to Object-store DNS “XXXX.dhc.local” form InterCluster LIFs.
  •  Able to ping DNS IP "10.199.217.XX" from InterCluster LIFs.
  •  Ran the “object-store profiler test” from Node-01, it failed with the error “wrong port or server not reachable”.

 

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.