メインコンテンツまでスキップ

vCenter で VASA Provider 証明書を再生成する方法

Views:
447
Visibility:
Public
Votes:
0
Category:
netapp-hci
Specialty:
virt
Last Updated:

環境

  • VMware vCenter Server向けNetApp Elementプラグイン
  • VMware ESXi

説明

  • vCenterでSSL証明書に問題が発生した場合、ユーザがvCenter向けElementプラグイン(VCP)を使用してVVolを管理できず、代わりにSSL証明書のエラーが表示される可能性があります。
  • vCenterではストレージプロバイダがアクティブと表示されることがありますが、ESXiホストは「Not connected」と表示されます。VVOLデータストア が「(非アクティブ)」と表示されます。
  • ESXホスト側のエラーの例(/var/log/vvold.log):

<DATE / TIME> warning vvold[2100222] [Originator@6876 sub=Default] VasaSession::GetEndPoint: failed to get endpoint, err=SSL Exception: Verification parameters:
--> PeerThumbprint: <thumbprint value>
--> ExpectedThumbprint:
--> ExpectedPeerName: <IP Address>
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate, using default
<DATE / TIME> info vvold[2100222] [Originator@6876 sub=Default] VasaSession::Initialize url is empty
<DATE / TIME> warning vvold[2100222] [Originator@6876 sub=Default] VasaSession::DoSetContext: Empty VP URL for VP (<hostname>)!
<DATE / TIME> info vvold[2100222] [Originator@6876 sub=Default] Initialize: Failed to establish connection

 

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.