RSS

Tag Archives: esxi

VMware: Finally a better maintenance mode sequence

I guess most of us have had the experience of getting an ESXi host into maintenance mode and finding that it got stuck with one last VM. When you look into host, you also see shutdown VMs and templates still hosted by this ESXi and you have to manually move them out before trying to get that last VM fixed so that you can get into the maintenance mode.

Great news with the vSphere 6.0 Update 2, now the order of evacuation for host going into maintenance mode is improved! Specifically:

Starting with vSphere 6.0 Update 2, when a host enters Maintenance Mode the host will evacuate all the powered off VMs and templates first, and then proceed to vMotion all the powered on VMs.

http://blogs.vmware.com/vsphere/2016/03/maintenance-mode-improvements-in-vsphere60u2.html

 
Leave a comment

Posted by on March 18, 2016 in vmware

 

Tags: ,

Finally web client for ESXi hosts!

For many who have moved on to vSphere 5.1 and beyond, and despite VMware’s focus on web-based management instead of the fat client, we still had to use the fat client to connect to and managed ESXi hosts. Great news as now there is a web based client to manage ESXi host directly. You do have have to install a VIB to your host for this to happen (I am sure this will be integrated in later versions) and it only works on 5.5 U3 and above, which will be released later.

http://blogs.vmware.com/vsphere/2015/08/introducing-vsphere-host-client-fling.html

 
Leave a comment

Posted by on August 13, 2015 in vmware

 

Tags: ,

HP blades and vSphere ESXi compatibility matrix

The most challenging part of having a blade enclosure system like HP c7000 blade encloure series is the getting the firmware to match the components. For example, you may start off with BL460c G7 blades and 1 year down the road decide to add Gen8 blades into the same enclosure. It is not a simple question of just plugging them in, many times it will not work as the underlyin OA firmware may not support Gen8 blades. However, one cannot just go ahead and upgrade the OA firmware without first checking the firmware versions of the G7 blades and iLOs to ensure that the new firmware is supported by each other. This is usually not too big a problem when the blades are new and estate is small, but if you have them deployed globally and over a few years, you can be assured that firmware versions will be very varied. And any attempts to standardize just say the OA firmware can difficult.

This is why HP has a compatibility matrix for its system. It used be a bit more complex (but easier) as the table would state the minimum firmware version for each component to work with each other. So you may want to upgrade the OA firmware to 3 versions higher but keep the rest the same, it would be not an issue. However, they have since streamlined this and force everyone to upgrade to a single version level. So if you want to upgrade the OA firmware to 3 version upwards, you need to upgrade all other components to the same version base.

http://h18000.www1.hp.com/products/blades/components/matrix/compatibility.html

Now if you are runnning ESXi hosts on these blades, your have to consider recommended driver versions which works in tandem with the OS version and the HP blade firmware.

http://vibsdepot.hp.com/hpq/recipes/

 

 
Leave a comment

Posted by on August 27, 2014 in Operations, vmware, Windows

 

Tags: , ,

PowerCLI: one-liner to verify root password on ESXi hosts

There is only one account with full admin privilege on ESXi host before 5.5 and that is the root account. In the financial sector like a bank, you are required to use a password broker to manage your root password. That is, you check in the initial root password to the broker (like cyberark) and it will reset the password regularly. When you need to perform work on the host using root passwords, you will need to check out the password with dual authentication. Of course, this really makes life hard for us admins when we need to perform bulk work that requires root passwords. For example have to move hundreds of host from one vCenter to another.

I use this one-liner below to verify if a host is using the default root password (which were standardized previous). This is useful as part of audit remediation as some hosts may be rebuilt due to an issue and the root passwords was not re-checked in to the broker to be managed. One caveat I found is that for the same PowerCLI session, you should not be logged into any of the vCenters where the hosts are managed via connect-viserver before running this. The h.csv file is just a list of host name with “name” as the column.


import-csv .\h.csv | %{ $err = @() ; connect-viserver $_.name -user root
-password "default" -EA silentlycontinue -EV err ; if ($err.count -gt 0)
{ $_.name | out-file .\hosts_std_root.txt -append }
else {disconnect-viserver $_.name -force -confirm:$false} }

I use this one-liner below to test each ESXi host before I start work AFTER checking out each root passwords. The creds.csv file is list of name,password.


dir creds.csv | % {import-csv .\$($_.name) |
%{ $err = @() ; connect-viserver $_.name -user root -password $_.password -EA silentlycontinue -EV err ;
if ($err.count -gt 0) { $_.name | out-file .\esx_wrong_root.txt -append }
else {disconnect-viserver $_.name -force -confirm:$false} }}
 
2 Comments

Posted by on May 3, 2014 in powershell, Scripts, vmware

 

Tags:

VMware: ESXi host have permission error in hardware status and inventory not foun

Recently, one of the ESXi host went down due to a hardware issue, but after we recovered the host and reconnected the host, I get the following error:

– In Hardware status page, I get “you do not have permission for this command”
– In inventory search, I can find the ESXi host, but when I click to it, it says “This entity does not exist in vCenterXXXXX” Read the rest of this entry »

 
Leave a comment

Posted by on July 25, 2013 in vmware

 

Tags: , ,

Powershell: Batch update of DNS server list in ESXi hosts

A quick one-liner to update the DNS serer list of all ESXi hosts in a cluster.

get-vmhost -location "MyVMClusterName |
get-vmhostnetwork |
set-vmhostnetwork -dnsaddress "1.1.1.1","2.2.2.2"

 
Leave a comment

Posted by on June 28, 2013 in powershell, Scripts, vmware

 

Tags: , , ,