Skip to main content
NetApp Knowledge Base

MetroCluster onboard key manager sync fails

Views:
27
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • ONTAP 9
  • Onboard Key Manager

Issue

Onboard key manager sync fails on a MetroCluster with the following log messages:

5/16/2024 21:08:42 CL01N01 DEBUG csm.connectionFailed: CSM failed to create a connection: localBladeUUID = CL01N01:dblade, remoteBladeUUID = CL01N02:dblade, uniquifier = 0e06188c82cfedef09, transportType = CT, sessionTag = CPEER, localVifId = 1032, remoteVifIP = 192.168.10.1, CsmError = CSM_CONNTIMEOUT, ctLoError = CTLOPCP_ERR_UNKNOWN, socketError = 60, and TLSerror = 0.
5/16/2024 21:08:09 CL01N01 INFORMATIONAL crypto.debug: Onboard key hierarchy creation failed: NKEK key creation failed: 30.
5/16/2024 21:08:09 CL01N01 ALERT crypto.ssal.failed: SSAL operation failed: SSAL Seal operation failed.
5/16/2024 21:08:05 CL01N02 DEBUG csm.connectionFailed: CSM failed to create a connection: localBladeUUID = CL01N02:dblade, remoteBladeUUID = CL01N01:dblade, uniquifier = 0e06188d0065zy8b, transportType = CT, sessionTag = CPEER, localVifId = 1033, remoteVifIP = 192.168.10.2, CsmError = CSM_CONNTIMEOUT, ctLoError = CTLOPCP_ERR_UNKNOWN, socketError = 60, and TLSerror = 0.

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.