Skip to main content
NetApp Knowledge Base

CONTAP-234081: TLS_AES_256_GCM_SHA384 breaks cluster peering relationship

  1. Last updated
  2. Save as PDF
Views:
38
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Issue

If TLS_AES_128_GCM_SHA256 is disabled and thus TLS_AES_256_GCM_SHA384 is forced to be used for TLSv1.3 cluster peering, the relationship will not be functional. The cluster peer will show as unavailable and it will not be pingable.
[cluster1::> cluster peer show]
[Peer Cluster Name Cluster Serial Number Availability Authentication]
[------------------------- --------------------- -------------- --------------]
[cluster2 1-80-000011 Unavailable ok]
[cluster1::*> cluster peer ping -destination-cluster cluster2 -type data]
[Warning: Unable to list entries in cluster cluster2. Failed to contact peer cluster "cluster2" at addresses:]

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.