Latest Posts

Translate

Total Pageviews

Wednesday, 31 December 2014

There are two ways to connect with the Guest Operating System:-
1. vSphere Web Client > vCenter Server > Select ESXi Host > Select VM > Open Console.
and then you can check the sessions and terminate the session when you will terminate the session from here then it will terminate the VM console as well. 2. RDP Client > Connect with VM through IP or Name.
Run the command quser or tsadmin to view the session and then from the tsadmin console you can terminate the particular session

Generally Second Option is used by the system admins and first option is used by the vmware admin to access the guest os.

Tuesday, 30 December 2014

Details

Using theesxcli network nic downandesxcli network nic upcommands fails to restart a physical network adapter that is connected to an HP Virtual Connect Flex-10 Ethernet Module and is in a non-standard speed mode or a physical network adapter that resides in a Cisco UCS sever.

Using the esxcli network nic down and esxcli network nic up commands fails to restart a physical network adapter that is connected to an Emulex OneConnect 10Gb UCNA and is in a non-standard speed mode or a physical network adapter that resides in a IBM Blade Center Server.

Another command that does not work with a HP Flex-10 or Cisco UCS network adapter is theesxcli network nic set -n vmnicX -afor autonegotiating the speed of an adapter with sequence number X.

This issue has been observed on IBM Blade Servers utilizing the Emulex OneConnect 10Gb UCNA as well.

Solution

Use these commands only with the network cards running auto-negotiation/10Mb/100Mb/1000Mb/10000Mb speeds. Do not use these commands on a HP Flex-10, Cisco UCS / IBM Blade Center Server, Emulex OneConnect 10Gb UCNA network adapter with non-standard speed. These commands do not support HP Flex-10, Cisco UCS,Emulex OneConnect 10Gb UCNAand other cards with non-standard speeds.

Sunday, 28 December 2014

When i was delivering the vCAC Session then while doing the lab one of my client did mistake in vCAC appliance configuration and then when i findout the issue it was misconfiguration of details those were needed for the certificate generation after rectifying the mistake default tenant info become visible.

Hope this will be helpful for everyone in resolving same kind of issue.

Saturday, 27 December 2014

Symptoms

VMware vCenter Server showsLockdown Modeas enabled, but is disabled on the host.

vCenter Server continues to show the incorrect status for the host even after:

The vSphere Client is restarted.

The host management services are restarted.

The VirtualCenter Server service is restarted.

The host is removed and re-added to the vCenter Server inventory.

This issue occurs when using Autodeployed ESXi 5.x hosts.

If the host is restarted, Lockdown Mode is disabled, but vCenter Server shows that it is enabled.

Changing Lockdown Mode from vCenter Server fails with the error:

A general system error occurred: Invalid faultCall "HostSystem.EnableAdmin" for object "esxi host FQDN" on vCenter Server

Cause

This issue occurs because vCenter Server enables and disables Lockdown Mode for the ESXi hosts, without checking the current Lockdown status of the host to determine the current state. This means if vCenter Server (through the vSphere Client) puts a host into Lockdown Mode and the Direct Console User Interface (DCUI) is used to take the host out of Lockdown Mode, vCenter Server is not notified of the state change and still operates as if the host is in Lockdown Mode.

Resolution

This is a known issue.

Currently, there is no resolution.

To work around this issue, enable Lockdown Mode to make it consistent with vCenter Server and then disable Lockdown Mode through vCenter Server.

Hourly Heartbeats

Every hour, a heartbeat message is written to thevmksummarylog. This information can be useful to indicate the liveliness of the ESXi host and its logging, or to review virtual machine quantities or component memory usage over time.