RecoverPoint and RecoverPoint for VMs: Newly added RPA is not visible from the remaining cluster

The issue occurs when the existing RPAs have a nondefault certificate (self-signed or CA-signed), and the new RPA has the default certificate.

From cluster logic logs:

 (BaseInstallationServerAdapter.java:100) ERROR - Failed to connect to vRPA with IP <newlyadded RPA IP>

  com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 401: null

        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:302)

        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:244)

        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:202)

        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:115)

        at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:109)

This is according to SPEC.
All RPAs in a cluster must have the same certificate (different clusters can have different certificates).
Certificate should be changed for each RPA using boxmgmt menu.
If newly added RPA has a different(Default) certificate, cluster fails to communicate with it and update Cluster fezick with newly added RPA details.

Workaround:

Change the default certificate of newly deployed RPAs with the custom certificate (same as other RPAs in the cluster) and then add the RPA to the cluster.
If the new RPA is already added to the cluster, change the RPA certificate with the customer certificate to make it visible to the remaining appliance.

Resolution:
Dell engineering is investigating this issue. A permanent fix is still in progress. Contact the Dell Customer Support Center or your service representative for assistance and reference this solution ID.