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

外部キーマネージャ(KMIP)への接続中にノードタイムアウトが発生しました

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

環境

  • ONTAP 9
  • 外部キー管理(EKM)/ KMIP構成

問題

一方のノードは設定済みの外部KMIP鍵管理サーバーに接続できなかったが、パートナーノードは正常に接続できた。以下の症状とログ出力が見られ、問題は継続しました:

::> security key-manager external show-status output:

Node: nascls032-n03
Vserver: nascls032
KeyServerPort: 5696
KMIP is operational: false
Reason: IO
KeyServer   Role    Server Status    Reason
----------------------------------------------
10.176.175.121 primary  not-responding  IO
10.223.204.26 primary  not-responding   IO

EMSログ:

[node01:mgwd:km.keyserver.notavailable:alert]: The external key management server "10.xx.yy.121:5696" is not available for Vserver "vserver01", status: "not-responding".
[node01:mgwd:km.keyserver.notavailable:alert]: The external key management server "10.xx.yy.26:5696" is not available for Vserver "vserver01", status: "not-responding".

KMIP2クライアントログ:

ERR: kmip2::kmipCmds::KmipConnection:[cryptsoftErrorCb]: Error: kmip_ssl_conn_do_handshake: 10.xx.xy.121
ERR: kmip2::tables::kmip_keyserver_status:[setKeyServerStatus]: Received an exception in setting up TLS connection: IO(10) Cryptsoft error code 10 = IOError: TCP connection never established, TLS handshake cannot begin.

  • 影響を受けたノードからのTCP接続テストはタイムアウトしたが、パートナーノードでは成功した。

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.