Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Impacted Hardware:EMC Hardware: VPLEX SeriesImpacted Software:All GA Version of VPLEX GeoSynchronyThe below error is seen when trying to configure cluster-witness in VPlexcliVPlexcli:/> configuration cw-vpn-configure -i x.x.x.xNote: x.x.x.x will be the public ip address for the new Cluster-Witness Server The Cluster Witness requires a VPLEX Metro or VPLEX Geo configuration. Is this system configured as a Metro or Geo? (Y/N): YError while preparing certificate creation: Unable to get the certificate subject info file from x.x.x.x - Scp Invalid PasswordThe log summary for configuration automation has been captured in /var/log/VPlex/cli/VPlexconfig.logThe task summary and the commands executed for each automation task has been captured in /var/log/VPlex/cli/VPlexcommands.txtThe output for configuration automation has been captured in /var/log/VPlex/cli/capture/VPlexconfiguration-session.txtconfiguration cw-vpn-configure: Evaluation of > failed.cause: Command execution failed.cause: Unable to get the certificate subject info file from x.x.x.x - Scp Invalid Password
When deploying a new Cluster-Witness Virtual-Machine (VM), it is not uncommon for the user/field to deploy the VM with an IP address that is already used by someone else in their datacenter.Other times the VPLEX VASA OVA is deployed instead of the cluster-witness OVAWhen this happens you will get the following message when running configuration cw-vpn-configure Unable to get the certificate subject info file from x.x.x.x - Scp Invalid Password
How to verify if Cluster-Witness was deployed with an IP Address that already exists:1. Exit to the VPLEX Management-Server prompt2. From the Management-Server system prompt SSH to the Cluster-Witness public IP Address using the following command: service@ManagementServer:~> ssh 3. If you are prompted for a password, then this is most likely a duplicate IP address or the wrong OVA was deployed, a. Try the service password Mi@Dim7T b. If the service password yields a successful login then that means VASA was deployed instead of Cluster-Witness OVA. Delete the VM and re-download the Cluster-Witness OVA and use that for deployment, and check to make sure the Cluster-Witness OVA is for the code level the VPLEX is currently running on. Sample of what Cluster-Witness OVA will look like: VPlex-#.#.#.##.##.##-cluster-witness-server.ova VPlex-5.5.1.00.00.05-cluster-witness-server.ova c. If the service password does not work then continue with the below steps 4. Have the user/field shutdown the Cluster-Witness VM5. After the VM is off, ping the user provided IP address of Cluster-Witness service@ManagementServer:~> ping a. If you receive a successful ping response, then ask the user for a unique IP Address to used for the Cluster-Witness Server, then the Cluster-Witness needs to be re-deployed using a new and unique IP Address since this one is already in use. b. If you do not receive a successful ping, then re-deploy Cluster-Witness again use the same IP address, or have the user confirm the IP address is valid and not assigned to another device already.