メインコンテンツへスキップ

Cloud Volumes ONTAP は、Azure Blob がアクセスを失ったときに pha.obj.storeUnavailable をレポートします

Views:
19
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cvo
Last Updated:

環境

  • ONTAP 9
  • Cloud Volumes ONTAP(CVO)
  • Microsoft Azure

問題

  • ONTAP Azureノード/クラスタがBLOBストレージへのアクセスを失い、すぐに回復する
  •  アラートを受信しました:

pha.obj.storeUnavailable:ONTAP could not communicate with the object store,"object_store0"

  • EMS ログ:

バックエンド オブジェクト ストアへの通信が失われました...
[<node>: OscHighPriThreadPool: pha.obj.storeUnavailable:EMERGENCY]: ONTAP could not communicate with the object store, "object_store0".
[<node>: PHO_SCAN: pha.obj.scanFailure:error]: ONTAP could not get a list of objects from the object store, "object_store0", at "roots.blob.core.windows.net", using IP address "10.x.x.x" with error: store is inaccessible.
[<node>: pha_main010: scsi.cmd.adapterHardwareErrorEMSOnly:error]: Disk device 0d.1L0: Adapter detected hardware error: HA status 0xb: cdb <CDB>. Disk 0d.1 S/N [SN] UID [UID] Target Address [unknown]

通信が正常に回復しました...
[<node>: OscLowPriThreadPool: pha.obj.storeAvailable:notice]: ONTAP successfully communicated with the object store, "object_store0".
[<Node>: pha_main010: scsi.cmd.retrySuccess:debug]: Disk device 0d.1L0: request successful after retry #2/#0: cdb <CDB> (100011).

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.