This post is more than 5 years old
2 Posts
0
6839
January 25th, 2016 08:00
RP4VM Failed to set the given vCenter Server credentials
Trying to setup RP4VMs for testing and getting an error on the final step within the Deployment Manager.
Failed to set the given vCenter Server Credentials
During this stage the cluster IP becomes active but it fails with the above message. I am using the administrator@vsphere.local account and able to successfully select which datastore to place the RP Repository and I have confirmed the repository is created on that datastore. There is no question about the credentials.
I am running the deployment manager on the vCenter Server itself and no windows firewall on Server 2012 R2
RPA cluster and vCenter Server at Secondary site is working fine with no issues... same setup other than Windows OS (Server 2012).
Attached dm.log file
drwolcot
2 Posts
1
January 25th, 2016 13:00
I did use admin/admin originally. However, I did get it to work. It appears the admin account was locked out?????
I attempted to login to the admin CLI (ssh cluster IP address) and login with the admin/admin account failed. I then ssh to the Cluster IP again using the security-admin/security-admin account and ran the command unlock_user.
This then allowed me to attempt to run your command you posted... update_vcenter_server_registration . However it was requesting a VCenter Server name and said it did not exist. Running the command get_vcenter_server_view came back with nothing confirming there were no VCenter Servers attached.
So I decided to manually add the VCenter Server in the Admin CLI using the command register_vcenter_server and supplying the requested information at the prompt (Server Name, vcenter IP, vcenter port, username, password, and certificate). I got the response that the "vCenter Server registered at RPA Cluster successfully."
In previous troubleshooting, I had manually added the RecoverPoint Web Client plugin into the directory C:\Program Files\VMware\vCenter Server\WebClient\plugin-packages and restarted the WebClient Service and this allowed the RecoverPoint plugin to show up in the WebClient.
After manually adding/registering vCenter Server in the admin CLI above and restarting the Web Client service, the Plugin is now showing correctly in the WebClient and I can manage and ProtectVMs.
Idan
675 Posts
1
January 25th, 2016 12:00
Hi there,
What RP credentials did you use in the same DM screen as the vCenter credentials one ? it should be admin/admin (that's the default in DM 2.3).
Looking at the DM logs won't tell us what RP user is used to set the vCenter credentials with on RP but the exception is timeout related so if it's not the credentials I would try to run update_vcenter_server_registration in the admin CLI (the next version will have this functionality in the plugin).
Regards,
Idan Kentor
RecoverPoint Corporate Systems Engineering
Email: idan.kentor@emc.com
Twitter: @IdanKentor
Idan
675 Posts
0
January 26th, 2016 01:00
I'm glad to hear that the suggested course of action worked.
Indeed the way to unlock a user is through the security-admin CLI user by using the unlock_user command. The admin user must of locked after 2 failed attempts.
As for the vCenter registration, this indeed can be done via update_vcenter_server_registration with the current vCenter name, which can be retrieved by running get_vcenter_server_credentials or by removing and adding back which you have done.
Regards,
Idan
Chong_Han
5 Posts
0
November 3rd, 2016 21:00
While using update_storage_registration, what does it mean one period ('.'), and enter again? Get stuck at this point while trying to change credential use.