Categories
VMware

vCenter “Virtual machine(s) invalid”

 

vCenter “Virtual machine(s) invalid”

 

  1. Check VM is hosted at which ESXi server.
  2. Login to ESXi server using SSH (example using Putty).
  3. check “Invalid VM” only using grep command vim-cmd vmsvc/getallvms | grep invalid 

    Invalid VM UPDATE

  4. Note three/four digit VM ID number(189) for the VM you wish to repair
  5. Type the reload command, to replace <VM ID> vim-cmd vmsvc/reload <VM ID>

  6. Virtual Machine will be Back to normal and PowerON hidden button start appear.
  7. PowerON virtual machine.

 

Thanks.

🙂

 

Categories
VMware

Installing Dell EQL MEM – ESXCLI

Installing Dell EQL MEM – ESXCLI Command

Prerequisite:

  • Download Mem-file from Dell Equallogic portal “dell-eql-mem-esx6-1.5.0.437336.zip”.
  • Copy on desire ESX server to execute it.

 

On Putty – Execute following

[[email protected]:~] esxcli software vib install –depot /vmfs/volumes/datastore1/dell-eql-mem-esx6-1.5.0.437336.zip
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: Dell_bootbank_dell-eql-host-connection-mgr_1.5.0-437336, Dell_bootbank_dell-eql-hostprofile_1.5.0-437336, Dell_bootbank_dell-eql-routed-psp_1.5.0-437336
VIBs Removed:
VIBs Skipped:
[[email protected]:~]

 

1

 

 

Thanks 🙂

 

 

 

Categories
VMware

Allow ui for web client ESXi6, ESXi5.5 by Installing VIB file on ESXi

 

Allow ui (user interface) for web client ESXi6, ESXi5.5 and etc.

 

VIB Files

 

[[email protected]:~]

[[email protected]:~] esxcli software vib install -v /vmfs/volumes/DataStore-RackServer/VMware_bootbank_esx-ui_1.24.0-7119706.vib

Installation Result

Message: Operation finished successfully.

Reboot Required: false

VIBs Installed: VMware_bootbank_esx-ui_1.24.0-7119706

VIBs Removed:

VIBs Skipped:

[[email protected]:~]

 

Categories
VMware

Dell Equallogic – Configure iSCSI SAN @ ESXi using VMware vSphere CLI

 

Configure iSCSI SAN for Dell Equallogic PS series @ ESXi using VMware vSphere CLI

 

 

C:\>cd “Program Files (x86)\VMware\VMware vSphere CLI\bin”

C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>setup.pl –configure –server=192.168.1.11

You must provide the username and password for the server.

Enter username: root

Enter password:

Do you wish to use a standard vSwitch or a vNetwork Distributed Switch (vSwitch/vDS) [vSwitch]:

Found existing switches vSwitch0, vSwitch1, vSwitch3.

vSwitch Name [vSwitchISCSI]:

Which nics do you wish to use for iSCSI traffic? [vmnic0 vmnic1 vmnic10 vmnic11 vmnic2 vmnic3]: vmnic2,vmnic3

IP address for vmknic using nic vmnic2: 10.10.10.11

IP address for vmknic using nic vmnic3: 10.10.10.12

Netmask for all vmknics [255.255.255.0]:

What MTU do you wish to use for iSCSI vSwitches and vmknics?  Before increasing

the MTU, verify the setting is supported by your NICs and network switches. [1500]: 9000

What prefix should be used when creating VMKernel Portgroups? [iSCSI]:

What VLanId do you wish to use for Portgroup for vSwitch to be configured [0]:

Do you wish to use SW iSCSI or HW iSCSI? (sw/hw) [SW]: HW

What PS Group IP address would you like to add as a Send Target discovery address (optional)?: 100.101.102.11

What CHAP user would you like to use to connect to volumes on this group (optional)?:

Would you like to apply Dell EqualLogic best practice settings to the iSCSI adapters?  See the Installation and User Guide for more information on the settings that will be applied. [yes]:

Configuring iSCSI networking with following settings:

Using a standard vSwitch ‘vSwitchISCSI’

Using NICs ‘vmnic2,vmnic3’

Using IP addresses ‘10.10.10.11,10.10.10.12’

Using netmask ‘255.255.255.0’

Using MTU ‘9000’

Using prefix ‘iSCSI’ for VMKernel Portgroups

Using HW iSCSI initiator

Adding PS Series Group IP ‘100.101.102.11’ to Send Targets discovery list. Applying best practice configuration settings

The following command line can be used to perform this configuration:

C:\Program Files (x86)\VMware\VMware vSphere CLI\bin\setup.pl –configure –server=192.168.1.11 –vswitch=vSwitchISCSI –mtu=9000 –nics=vmnic2,vmnic3 –ips=172.16.1.21,172.16.1.22 –vlanid=0 –netmask=255.255.255.0 –vmkernel=iSCSI –groupip=100.101.102.11 –bestpractices

Do you wish to proceed with configuration? [yes]: Cambridge English:

The answer must be ‘yes’ or ‘no’

Do you wish to proceed with configuration? [yes]: Advanced (CAE)*

Do you wish to proceed with configuration? [yes]:

Configuring networking for iSCSI multipathing:

vswitch = vSwitchISCSI

mtu = 9000

nics = vmnic2 vmnic3

ips = 172.16.1.21 172.16.1.22

netmask = 255.255.255.0

vmkernel = iSCSI

EQL group IP = 172.16.1.11

bestpractices = 1

Creating vSwitch vSwitchISCSI.

Setting vSwitch MTU to 9000.

Creating portgroup iSCSI0 on vSwitch vSwitchISCSI.

Assigning IP address 172.16.1.21 to iSCSI0.

Creating portgroup iSCSI1 on vSwitch vSwitchISCSI.

Assigning IP address 172.16.1.22 to iSCSI1.

Creating new bridge.

Adding uplink vmnic2 to vSwitchISCSI.

Adding uplink vmnic3 to vSwitchISCSI.

Setting new uplinks for vSwitchISCSI.

Setting uplink for iSCSI0 to vmnic2.

Setting uplink for iSCSI1 to vmnic3.

vmk3 is not usable for port binding with vmhba37, skipping.

Bound vmk3 to vmhba36.

Bound vmk4 to vmhba37.

Set SATP Host System Best Practices.

Checking global HBA settings for adapter vmhba37.

Updating DelayedAck from true to false

Updating LoginTimeout from 5 to 60

Checking global HBA settings for adapter vmhba36.

Updating DelayedAck from true to false

Updating LoginTimeout from 5 to 60

Refreshing host storage system.

Adding discovery address 172.16.1.11 to storage adapter vmhba37.

Adding discovery address 172.16.1.11 to storage adapter vmhba36.

Rescanning all HBAs.

Network configuration finished successfully.

No Dell EqualLogic Multipathing Extension Module found.

Continue your setup by installing the module with the –install option or through vCenter Update Manager.

C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>

Categories
VMware

How to install vSphere vCLI 6.0

Install VMware-vSphere-CLI-6.5.0-4566394 

 

I have face new challenges with vmware vsphere cli, while using it on new fresh installation of windows 10 laptop.

Basics or prerequisite from VMware vSphere CLI guide i forget and start scratching google and digging other blogs that consumed more than couple of hours.

 

VMware vsphere VCLI guide… clearly provide a pre-requiste and it states that;

Pre-requisite

Pre-requiste for windows;

Install Visual C++ 2008 redistributable for 32-bit.
ActivePerl or Strawberry Perl version 5.14

Install VMware vSphere vCLI software;

Download software from vmware (my version : VMware-vSphere-CLI-6.5.0-4566394)
Install software  VMware vSphere CLI

 

Post Installation issues with Scripts:

after installing a file as well when try to connect to my ESXi server to install Dell Equallogic MEM files.

Download MEM files and keep it in C:\ folder MEM, use script give error:

Error without directory

SOLUTION:

CHANGE DIRECTORY TO vCLI installation of bin drive

C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>

Copy SETUP.PL on this path for Dell Equallogic MEM

WORKING WITH DIRECTORY

 

ISCSI configuration with best practices working.

 

Thanks,

Kabeer Siddiqui.

 

 

 

Categories
VMware

‘Replace a process level token Privilege.’ – Windows vCenter 6.5 upgrade error

Please ensure extensions are compatible with the new vCenter Server and re-register extensions with the new vCenter Server after upgrade. Please refer to the vSphere documentation on extensions, and the upgrade and interoperability guides.Error: User Running the upgrade does not have ‘Replace a process level token Privilege.’ Resolution: Assign a process level token privilege to the user

error1

 

 

Resolution:

In RUN: type GPEDIT.MSC

Capture

Add a user (example domain\vmadmin) by Click add USer or Group.

Continue installation with no errors !!!

 

 

Thanks,

Kabeer

 

Categories
VMware

VMware : Suspend Virtual Machine after 15 minutes.

 

VMware vCenter or VMware ESX (All editions), Windows Client(XP, 7, 8, 10 all editions) get suspended after every 15mins.

Resolution:

This issue is not from VMware. It is a windows client settings that need to change from Power setting.

Below is a steps in .JPG format.

 

1

Right click on windows and select control Panel.

2

Select Hardware and Sound.

Click on Power Options

3

Click…. Balanced (recommended)

4

Click “Change Settings that are currently unavailable”

5

change the below options

6

change the below options to “Never”

7

 

 

Thanks 🙂 🙂 🙂

Categories
VMware

Step by Step Install VMware vCenter 6.5

 

Installation procedure all in JPEG format. Please check.

VMware Version : vCenter 6.5

OS: Windows 2012 R2

 

2017-01-03_142514

 

2017-01-03_142523

 

2017-01-03_142550

 

2017-01-03_142600

 

2017-01-03_142705

 

2017-01-03_142836

 

2017-01-03_142844

 

2017-01-03_142858

 

2017-01-03_142905

 

2017-01-03_142926

 

2017-01-03_142934

 

2017-01-03_142946

 

2017-01-03_142953

 

2017-01-03_143021

 

2017-01-03_143031

 

2017-01-03_143038

 

2017-01-03_143228

 

2017-01-03_143519

 

2017-01-04_102451

 

Thanks 🙂 🙂 🙂

Kabeer Siddiqui.

 

Categories
VMware

Step by step Install VMWare ESXi 6.5

 

Installation steps in JPEG snapshots.

Have a look 🙂 .

Download ESXi 6.5 from vmware.com/donwloads.

123456789101112131415

 

Thanks 🙂 🙂 🙂

Categories
VMware

unable to create a swap file. the value of ‘sched.swap.dir’

 

For the official recommended one from VMware pls follow this link

Storing a virtual machine swap file in a location other than the default in ESX/ESXi (1004082

Issue:

After Storage migration. VM still pointing vswp file in old datastore and unable to power on and issue a following error.

Error : unable to create a swap file. the value of ‘sched.swap.dir’

Solution:

To change the swap file location for a single virtual machine:

  1. Power off the virtual machine.
  2. Unregister the virtual machine. Right-click the virtual machine in the Inventory and choose Remove from Inventory.
  3. Connect to the host using SSH
  4. browse the datastore where virtual machine is resided;
  5. Change directory to the folder where the virtual machine resides:

    cd /vmfs/volumes/datastore_name/virtual_machine_folder/

  6. Edit the virtual machine’s configuration file with a text editor.
  7. Edit vi using commands:
    1. Esc :i
    2. replace the following;
      1. sched.swap.dir = /vmfs/volumes/old_datastore_name/dir_name
      2. sched.swap.dir = /vmfs/volumes/new_datastore_name/dir_name
  8. save the vi file using command “:wq
  9. Register the virtual machine again.
  10. PowerON VM without any error.

 

Note:- Resolve issue for ESXi 6 as well.

It works :).

 

Thanks,

Kabeer Siddiqui