Skip to main content
NetApp Knowledge Base

FabricPool being unavailable after the MCC switchover

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

Applies to

  • ONTAP 9
  • FabricPool
  • StorageGRID

Issue

  • After the MCC switchover to the surviving side, the FabricPool became unavailable.
  • The following errors are observed in the EMS log intermittently:

Mon Jul 29 12:00:15 +0200 [<node_name>: OscHighPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "<object_store_name>" from node XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. Reason: Internal server error.
Mon Jul 29 12:00:15 +0200 [<node_name>: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "<object_store_name>" from node XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Mon Jul 29 12:15:16 +0200 [<node_name>: OscHighPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "<object_store_name>" from node XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. Reason: Internal server error.
Mon Jul 29 12:15:17 +0200 [<node_name>: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "<object_store_name>" from node XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.

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.