Solution: VPLEX: How to resolve GUI default monitors not reporting events
This issue is resolved in vCenter Server 6.0 Update 2, available at VMware Downloads.
To work around this issue, restart the management agents on the impacted hosts to clear the warning.
From the Local Console or SSH:
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
To check the status of vCenter Server Appliance services:
service –-status-all
To check the status of a specific service:
ls /etc/init.d
service ServiceName status
Where ServiceName corresponds to one of the services in /etc/init.d or the core list in the Additional Information section of this article. For example:
service vmware-vpxd status
If the vpxd service is running, you see output similar to:
vmware-vpxd is running
tomcat is running
Note: The tomcat service is within the vmware-vpxd service. You can check the status of tomcat by checking the status of vmware-vpxd. This service can be stopped and started outside of the vmware-vpxd service by running these commands:
vmware-vpxd tomcat-stop
To stop a vCenter Server Appliance service if it has started:
ls /etc/init.d
service ServiceName stop
Where ServiceName corresponds to one of the services in /etc/init.d.
Note: When you stop the VMware VirtualCenter Server service (vmware-vpxd), all connected users are disconnected from their session.
To start a vCenter Server Appliance service if it has stopped:
ls /etc/init.d
service ServiceName start
Where ServiceName corresponds to one of the services in /etc/init.d.
Note: If the VMware VirtualCenter Server service does not start, verify that it is able to get exclusive access to the vCenter Server repository. For more information, see Unable to get an exclusive access to the vCenter Server repository (1006369).
To restart a vCenter Server Appliance service:
ls /etc/init.d
service ServiceName restart
Where ServiceName corresponds to one of the services in /etc/init.d.
Note: When you restart the VMware VirtualCenter Server service, all connected users are disconnected from their vSphere/Virtual Infrastructure Client sessions.
Service Description | Service Name |
VMware VirtualCenter Server Service | vmware-vpxd |
Embedded vPostgres Database service | vmware-vpostgres |
VMware Tools Service | vmware-tools-services |
VMware vSphere Profile-Driven Storage Service | vmware-sps |
VMware vCenter Inventory Service | vmware-inventoryservice |
VMware vSphere Network Dump Collector service | vmware-netdumper |
VMware vSphere Log Browser | vmware-logbrowser |
VMware vSphere Auto Deploy service | vmware-rbd-watchdog |
VMware vSphere Web Client | vsphere-client |
[For vSphere 5.1 Only] vCenter Single Sign-On 5.1 | vmware-sso |
[For vSphere 5.5 Only] vCenter Single Sign-On 5.5 – VMware Directory Service |
vmdird |
[For vSphere 5.5 Only] vCenter Single Sign-On 5.5 – VMware Certificate Service |
vmcad |
[For vSphere 5.5 Only] vCenter Single Sign-On 5.5 – VMware Secure Token Service |
vmware-stsd |
[For vSphere 5.5 Only] vCenter Single Sign-On 5.5 – VMware Kdc Service |
vmkdcd |
[For vSphere 5.5 Only] vCenter Single Sign-On 5.5 – VMware Identity Management Service |
vmware-sts-idmd |
VMware is aware of this cosmetic issue. It is due to a bug identified by VMware in vSphere 6.0 Update 1b that results in this message not being cleared automatically following maintenance or service restoration.
Restarting the VPXA (vCenter Server) management agent on the VSAN cluster ESXi host nodes refreshes the information in vCenter Server and clears the message.
Removing and then re-adding a host to the VSAN cluster forces all hosts to update the information about the cluster membership, which clears the message.
# /etc/init.d/vpxa restart
Note: Wait approximately one minute before proceeding to the next host. This allow information from each host to update in vCenter Server one-at-a-time.
I have faced issue with regards to Unisphere i.e after entering the URL the browser shows blank page . Below were the various resolution steps for me :-
ESXI host 5.5 takes long time to boot and stays at VMW_Vaaip_Cx or vmw_vaaip_symm loaded successfully
Issue : ESXI 5.5 boot take long time and stays at ( Storage API like) loaded successfully , this may take an hour or so to bring the ESXI 5.5 completely.
Cause : This will be happening on the environment which have Microsoft cluster vm and RDM disk is presented to that Microsoft cluster vm . Especially the RDM lun is not showing as Perennially reserved =true. You can check whether the lun is perennially reserved or not by running the below command
esxcli storage core device list
Solution: Will explain how to fix this on ESXi 5.5 version , for rest of the version please check the vmware kb article number 1016106.
1.We need to know the LUN identifier ( naa.id ) for all the rdm disk and this identifier varies for different storage vendor.
2. There are multiple ways to get the identifier , simple way is to click edit settings on the vm and click the rdm lun and on the right hand side click manage path , note down the lun number and identifier.
3. We can also get the identifier from Configuration—storage adapter and click one of the hba .
4.ssh into the esxi server
5.Run the command for each RDM lun
esxcli storage core device setconfig -d naa.id –perennially-reserved=true
Today I was upgrading Vcenter 5.5 to 6.01 and face the below error during pre upgrade check .
The system name in the vCenter Server 5.5 SSL certificate and the vCenter Single Sign-On 5.5 SSL certificates are not compatible. Please replace either the vCenter Server SSL certificates or the vCenter Single Sign-On SSL certificates so both vCenter Server and vCenter Single Sign-On SSL certificates use the same system name.
The resolution that I followed was as below
Re-installing the vCenter Server stack