Users Guide

Troubleshooting
Table 2. Common problems and recommended actions
Problem Recommended Actions
Plug-in not visible after
installation
Verify the successful installation of the plug-in and the plug-in version:
1. Log in to http://vCenter-server-IP-address/mob/content/
ExtensionManager/extensionList using vCenter Server credentials to access
the Managed Object Browser (MOB).
2. Look for the plug-in name com.vcplugin.plugin in the extension list and then click
the name to check the plug-in version.
If the installation was successful, log out of vCenter and log in again. The vSphere client
displays a message indicating that plug-ins that were installed or updated. They will be
ready for use next time you log in to vSphere client.
vCenter vSphere client cannot be
accessed from any host (error
404)
Potential solutions:
● Add vCenter host entry in the hosts file in the appropriate path below:
○ Windows: C:\Windows\System32\drivers\etc\hosts file
○ Linux: /etc/hosts
● Verify that the host is connected to storage system. In the ME4 Series storage system
CLI, enter show initiators to view the list of initiators that are known to the
system. For each initiator, the output shows whether the initiator was discovered, the
initiator ID, and other information. On the host, find the adapter with the corresponding
ID and verify whether the storage system shows that initiator as being discovered or
not.
● Verify that the datastore is mounted on hosts after a mount operation:
1. Go to Storage.
2. Select the datastore.
3. Click the Hosts tab.
4. View the list of mounted hosts.
● Verify that the datastore is unmounted from hosts after an unmount operation:
1. Go to Storage.
2. Select the datastore.
3. Click the Hosts tab.
4. Verify that the unmounted host entry is not listed.
● Verify task details for plug-in specific operations:
1. Click Menu.
2. Select Tasks.
3. Click the task in the Task Console.
4. Check the task status.
VMware error code 503
Indicates that the vCenter Server vSphere UI service is not running. To start the service,
enter the service-control --start vSphere-ui command.
6
Troubleshooting 17