Connections from Client to CIM Server

If your client fails to complete a connection to a CIM server, use these suggestions to help verify the connection parameters and the health of the CIM server.

Using SLP
Check the connection parameters using an SLP client (available on the Web). Run the SLP client on the same subnetwork as the managed server. Verify that the managed server advertises the expected CIM service and the correct URL.
Using a Web Browser
To verify that you can reach the CIM service at the advertised location, connect to the managed server with a Web browser. Use a URL of the form https://<cim-server.mydomain.com>:5989/ (substituting the name of the actual server), and verify that the server is responding on the expected port. Port 5989 is the default port for CIM-XML connections, but your installation might be different.
Using a Command-Line Interface
Using a command-line interface allows you to bypass any issues related to the correct invocation of the interface functions in a programmatic client.
Verifying User Authentication Credentials
If you are certain that the connection parameters are correct, verify the authentication parameters. To complete a connection, you must authenticate as a user that is known to the managed server.
Rebooting the Server
If all your connection parameters are correct and you are certain of your authentication credentials but you still cannot complete a connection, reboot the managed server or restart the management agents on the server.
Using Correct Client Samples
If you are using sample clients supplied by VMware, check the documentation to be sure that the samples are intended to work with the CIM server to which you are trying to connect. The samples might hard-code parameters, such as the port and namespace, that affect the connection.
Using Other CIM Client Libraries
Using the WS-Management Library
If you are unable to find a satisfactory client library to make a WBEM connection, use WS-Management. ESXi includes a WS-Man server to support CIM operations.

Parent topic: Troubleshooting CIM Connections