跳转到主内容

FabricPool在MCC切换后不可用

Views:
2
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2010118935</a>
Last Updated:

适用场景

  • ONTAP 9
  • FabricPool
  • StorageGRID

问题描述

  • 在MCC切换到运行正常的端后、FabricPool变得不可用。
  • EMS日志中会间歇性出现以下错误:

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.