Skip to main content
NetApp Knowledge Base

SRM failover unsuccessful due to vSphere Replication enabled but misconfigured

  1. Last updated
  2. Save as PDF
Views:
91
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
virt
Last Updated:

Applies to

  • Clusters running Element
  • SRM (Site Recovery Manager)

Issue

SRM sessions are being generated for a non-existent peer in a vSphere Replication relationship that consumes all  session resources making SRM and SRA operation requests never start.  Thousands of entries in the SRM logs:
Cannot increment number of connections to <cs p:XXXXXXXXXXXXXXXX, TCP:XXXXXXXXXX:443> as max connections (50) already in use

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.