1 Rookie
•
18 Posts
0
40
March 26th, 2025 20:57
Error when adding vCenter in PowerStore Manager
Hello team, I get an Error when adding vCenter in PowerStore Manager "failed to load vcenter services". We tried with both IP address and FQDN and same error. the ports 443 & 8443 are open in firewall. We can ping vCenter server IP from Powerstore. Any idea what the cause could be and how to solve it? any configuration settings should be set in vCenter before adding it in PowerStore Manager? thanks
No Events found!
DELL-Sam L
Moderator
Moderator
•
7.4K Posts
0
March 27th, 2025 09:50
Hello Ayman_Hassan,
The failure to load vCenter services in PowerStore may be due to several issues, including SSL certificate mismatches, connectivity problems, or timing issues related to the VASA server certificate not loading into the keystore. After enabling the Security Technical Implementation Guide (STIG), some systems may experience connection issues with vCenter. To resolve this, ensure that the PowerStore credentials for the VASA provider are correct, check the validity of the SSL certificate, and if necessary, update the configuration in PowerStore Manager to accept the new vCenter SSL certificate. Additionally, if the VASA server certificate is not visible on port 8443, changing the admin password and restarting the ControlPath container may help restore the connection.
Here is also a link to a KB for STIG if you have enabled it and are using it. https://www.dell.com/support/kbdoc/000225415/powerstore-unable-to-establish-vcenter-server-connection-after-stig-enablement
jerrytomson
1 Rookie
1 Rookie
•
1 Message
0
March 27th, 2025 17:37
The error "failed to load vcenter services" when adding vCenter in PowerStore Manager can be caused by several factors. Here are some troubleshooting steps to resolve it:
1. Verify vCenter API and Credentials
Ensure that the vCenter Server API is accessible by opening this URL in a web browser:
https://<vcenter-ip-or-fqdn>/sdkIf it doesn't load, the vCenter services may not be running properly.
Confirm that you are using valid administrator credentials with the required permissions.
2. Check Firewall & Network Connectivity
Since ports 443 and 8443 are open, also verify if PowerStore can reach vCenter via port 902, which is required for some vSphere services.
Use telnet from PowerStore to vCenter:
telnet <vcenter-ip> 443 telnet <vcenter-ip> 8443 telnet <vcenter-ip> 902If any fail, check firewall rules.
3. Restart vCenter Management Services
If API access fails or the error persists, restart vCenter services:
SSH into the vCenter Server Appliance (VCSA).
Run:
service-control --restart --allWait a few minutes and try adding vCenter again.
4. Verify SSL/TLS Certificate
If PowerStore Manager is unable to validate vCenter’s SSL certificate, try disabling certificate validation (only for testing).
If there is a certificate issue, manually import the vCenter certificate into PowerStore.
5. Enable PowerStore vCenter Integration
In vCenter, ensure that the vSphere Web Services API is enabled.
If vCenter is using Enhanced Linked Mode, try adding the primary vCenter instance instead of a secondary one.
6. Check PowerStore Logs
If the issue persists, check PowerStore Manager logs for more details:
Navigate to Support > Logs and download the logs.
Look for errors related to vCenter authentication or connectivity.
If none of these steps resolve the issue, consider upgrading PowerStore OS or vCenter to the latest supported versions. Let me know if you need further guidance! 🚀
Ayman_Hassan
1 Rookie
1 Rookie
•
18 Posts
0
March 27th, 2025 12:56
@DELL-Sam L Hello Sam, we tried again today and the port 443 was not open for one of the management IPs. Here we do not configure VASA. thanks a lot
DELL-Sam L
Moderator
Moderator
•
7.4K Posts
0
March 27th, 2025 14:51
Hello Ayman_Hassan,
It would be best to open support case for your issue so that we can see what is going on.
Ayman_Hassan
1 Rookie
1 Rookie
•
18 Posts
0
March 28th, 2025 09:04
@jerrytomson Hi Jerry, Thanks a lot for the detailed steps. The issue is solved. The port 443 was not open for one of the management IPs.