Skip to main content
NetApp Knowledge Base

CONTAP-157346: FabricPool object-store shows unavailable even though its available

  1. Last updated
  2. Save as PDF
Views:
27
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

When object-store toggles frequently between unavailable and available; due to say - network issues or object-store unavailability issues, object-store status may continue to show unavailable even though it is available. This will result in FabricPool tiered data being not able to be accessible to client workloads and tiering stops. Following is the typical messages in the sktrace.log in quick succession :

  • CLOUD_BIN_ERR:  object_store_aliveness_cb: Object store config state change. s3_handle=1, state=2(available), osc_error=0(Success)
  • CLOUD_BIN_ERR:  object_store_aliveness_cb: Object store config state change. s3_handle=1, state=1(unavailable), osc_error=72(Service unavailable)

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.