Archive for VMware

Restarting the Management agents on an ESXi or ESX host

Restarting the Management agents on an ESXi or ESX host

From the Direct Console User Interface (DCUI):

  1. Connect to the console of your ESXi host.
  2. Press F2 to customize the system.
  3. Log in as root.
  4. Use the Up/Down arrows to navigate to Restart Management Agents.Note: In ESXi 4.1 and ESXi 5.0, 5.1 and 5.5, this option is available under Troubleshooting Options.
  5. Press Enter.
  6. Press F11 to restart the services.
  7. When the service has been restarted, press Enter.
  8. Press Esc to log out of the system.

From the Local Console or SSH:

  1. Log in to SSH or Local console as root.
  2. Run these commands:/etc/init.d/hostd restart
    /etc/init.d/vpxa restartNote: In ESXi 4.x, run this command to restart the vpxa agent:/etc/opt/init.d/vmware-vpxa restart
  3. Alternatively:
  • To reset the management network on a specific VMkernel interface, by default vmk0, run the command:esxcli network ip interface set -e false -i vmk0; esxcli network ip interface set -e true -i vmk0Note: Using a semi-colon (;) between the two commands ensures the VMkernel interface is disabled and then re-enabled in succession. If the management interface is not running on vmk0, change the above command according to the VMkernel interface used.
  • To restart all management agents on the host, run the command:services.sh restartNote: For more information about restarting the management service on an ESXi host, see Service mgmt-vmware restart may not restart hostd in ESX/ESXi (1005566).

Restarting the Management agents on ESX

To restart the management agents on an ESX host:

  1. Log into your ESX host as root from either an SSH session or directly from the console.
  2. Run this command:service mgmt-vmware restartCaution: Ensure Automatic Startup/Shutdown of virtual machines is disabled before running this command or you risk rebooting the virtual machines. For more information, see Restarting hostd (mgmt-vmware) on ESX hosts restarts hosted virtual machines where virtual machine Startup/Shutdown is enabled (1003312) and Determining whether virtual machines are configured to autostart (1000163).
  3. Press Enter.
  4. Run this command:service vmware-vpxa restart
  5. Press Enter.
  6. Type logout and press Enter to disconnect from the ESX host.If this process is successful, it appears as:[root@server]# service mgmt-vmware restart
    Stopping VMware ESX Server Management services:
    VMware ESX Server Host Agent Watchdog [ OK ]
    VMware ESX Server Host Agent [ OK ]
    Starting VMware ESX Server Management services:
    VMware ESX Server Host Agent (background) [ OK ]
    Availability report startup (background) [ OK ]
    [root@server]# service vmware-vpxa restart
    Stopping vmware-vpxa: [ OK ]
    Starting vmware-vpxa: [ OK ]
    [root@server]#

How to know RDM mapped drive connected to which LUN in storage

In VMware virtual machine how to know RDM mapped drive connected to which LUN in Storage .
1- Go to virtual machine and edit virtual machine setting.
2- Click on Hard disk which is RDM drive.
3- click on Manage Pathsrdm1

on popup window you will get LUN information rdm2

Note down the LUN information  naa.xxxxx…………………..

4- Go to ESX Host >Configuration >Storage Adapters>
5- Click on HBA
6- Go to details rdm3

Check your LUN id  and Host LUN IDrdm5

Now you can identify your RDM mapped drive on your ESX Host .

Important Note :-The same RDM Mapped drive Host LUN ID may be different on another  ESX Host Because ESX Host LUN ID defined by Storage Manager Software while mapping LUN to ESX Host. Best Practice is always give same Host LUN ID for  all ESX Hosts while mapping the LUN to ESX Host.

 

Unable to increase disk size on virtual machine in ESX server

you are unable to increase disk size on virtual  machine ,Disk Provisioning option has grayed out even you have disk space on data store . this may be following cases you have migrated P2V , and your disk adapter type is IDE or Snapshot is associated with the virtual machine.

 

IDEIf you have space on data store and disk provisioning option has grayed out then check before doing anything your disk type ,in this image Disk controller type is IDE in this case you can not increase the disk size. you will have to convert your ddb.adaptorType = “ide” the the disk controller type to “lsilogic

How to convert IDE to SCSI follow the link

How to Convert a virtual IDE disk to a virtual SCSI disk  Step by step How to convert adapter stepbystep

SCSI

SCSI disk option will give you to increase the disk size.

If your Disk is SCSI and Disk Provisioning option are grayed out.Then you are probably running off a snapshot.

Snapshot

 

See the disk file, an we have -000001.vmdk?
That points to this running off a snapshot.  Go to snapshot manager and check it out .delete all to consolidate. See image below
snap1delimage
Now you would be able to increase the disk size. check article 

 

How to know vender by MAC address

if you want to know network card vender by MAC address .MAC address first  16 bit is assign to vender  OUI code .
Search your MAC address starting 16 bit below link
http://standards.ieee.org/develop/regauth/oui/oui.txt

VMware uses the Organizationally Unique Identifier (OUI) 00:50:56 for manually generated addresses
Xen project  uses the Organizationally Unique Identifier (OUI)  00:16:3e: for manually generated addresses

The VMRC console has disconnected attempting to reconnect

I got bellow error from Vsphere client  while accessing console.

I just logged in from another PC it is working fine  . There were no error as above.

Re install the Vsphere client and try.

Maximums Configuration for VMware vSphere 5.1

When you select and configure your virtual and physical equipment, you must stay at or below the maximums supported by vSphere 5.1. The limits presented in the following tables represent tested, recommended limits, and they are fully supported by VMware.

 

 

How to install windows 8 on VMware ESXi 5

I was trying to convert windows 8 P2v on vmware ESXi 5 . Windows 8 converted successfully . but when I powered on it stuck windows start up screen and  endless spinning circle .I was thinking P2V was not successful then i tried to install fresh windows 8 but there was same issue .

I Google it and got VMware article to patch the ESXi 5.0 to fix this bug. But there was easy solution .While creating virtual machine for  windows 8 choose windows 7 64 bit operating system and install windows 8. Its resolved the issue for me .