Page 2 of 3

PowerCli List HBA WWN’s

Whenever you get storage masked to your esxi node/cluster you always going to need to know what HBA WWN addresses are (assuming your using HBA not iSCSI etc) here is a quick powercli hba statement you can use to refresh your memory


For a cluster the following:

Get-Cluster clustername | Get-VMhost | Get-VMHostHBA -Type FibreChannel | Select VMHost,Device,@{N="WWN";E={"{0:X}" -f $_.PortWorldWideName}} | Sort VMhost,Device


And if you want to do a single host:

Get-VMhost -Name hostname| Get-VMHostHBA -Type FibreChannel | Select VMHost,Device,@{N="WWN";E={"{0:X}" -f $_.PortWorldWideName}} | Sort VMhost,Device



Perennial Reserved RDM’s

I got asked a couple of days about why an esxi server was taking roughly 45 mins to come back up after a reboot. Looking at the node when it eventually came back up showed that it had a number of RDM’s that were associated to virtual machines. Those virtual machines were mostly Windows RDM’s  used for MSCS. What was happening is that when esxi was booting it could see all theses luns and was trying to read the header, it was that delay in its attempts to read the header that was causing the 5 min boot time.

What was needed was to reserve those luns so that they were ignored on the boot scan. Using the powercli below we can define the target cluster, scan through the virtual machines within an identify all the raw devices and mark then as reserved.  It will then do this on each nodes in the cluster which reduced your boot time from say 45mins to a few minutes (depending on your hardware)


$TargetCluster = "Cluster Name"

$VMhosts = Get-Cluster $TargetCluster| Get-VMHost

$RDMDisks = Get-VM -Location $TargetCluster | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select ScsiCanonicalName

foreach($VMhost in $VMhosts) {
Write-Host "Connected To Server : " $VMhost
$esxcli = Get-ESXCLI -VMHost $VMhost
foreach($RDMDisk in $RDMDisks) {
Write-Host "Setting Perennially Reserved On : " $RDMDisk
$$false, ($RDMDisk.ScsiCanonicalName), $true)

Studing For VCP6-NV (2V0-642) (UPDATE – I Passed ?)

Quick update i took the exam on Friday morning and happy to say passed with a score of 433 (300 is the pass mark).

Personally i think it was a tricky exam but not as difficult as i anticipated it to be, i used the references ive already mentioned before and bolstered it up with 2 pluralsight courses i got access to on a 6 month trial basis.

I’m not going to go into the question i was given but i would say if you follow the links ive provided and the VMware blueprint  you should be ok.



Im a VMware vExpert 2018

To add to an already amazing year in world of virtualisation, today I was named a VMware vExpert 2018 . I’m honoured, humbled, and proud of my contributions to this amazing virtualisation community. The vExpert list is constantly growing, and it’s amazing to be part of this list of experts.

vExperts demonstrate significant contributions to the community and a willingness to share their expertise with others.

Studing For VCP6-NV (2V0-642)

So not had a chance to post much recently as im studying for my VCP6-NV (2V0-642). Figured i would post a couple of the places i have been using:

  1. These excellent vBrownBag Sessions

2. VMware Hands on Lab (HOL)

3. NSX 6.2 Documentation


vSphere Web Client (Flash) And Windows 2016

Had an interesting one the other day,  deploying windows 2016 servers for a customer, setting one up as a jump server for support staff i naturally wanted to check that we could access the vSphere web console correctly using both flash and html variants.

By reading this post you can imagine that it didn’t work due to our old friend flash. However there is an easy fix

dism /online /add-package /packagepath:"C:\Windows\servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum"


Running this will get the respective flash component installed to enable you to use the web client again. More details are available at Technet Article


ESXi And Windows Domain Controller Time Source

Bit of an old reference for the day but one i must admit i have forgotten previously, when using a windows domain controller time source for your ESXi infrastructure you may notice that with the default settings you find that it wont synchronize.

Thankfully VMware have a workaround that requires a couple of changes on the ESXi hosts to change the NTP client settings. Instructions are even provided on how to configure you domain controllers w32time service to point to one of the many internet NTP services so you always have good/reliable time source configured.


For the ESXi client NTP changes heres the article reference


New Release: VMware PowerCLI 10.1.0

A New version of PowerCLI has been released today to support the recent releases of vSphere 6.7/ vSAN 6.7 and NSX-T 2.1.

It includes the 20th module  vmware.vim that we can use to work with API’s in VMware on AWS so that should be something to look into later.

If like me and run via a Linux Powershell then to update the  PowerCLI modules all you need to do is the following (via the powershell prompt):

Update-Module VMware.PowerCLI

Heres a link to the VMware article that talks about some of the new features:

New Release: VMware PowerCLI 10.1.0


vCSA 6.5 How To Reset The Root Password

A nice and easy one, but one that i must admit have fallen foul to a couple of times.

If your worried your going to break something then take a snapshot of the applicance prior to all this.

1. Start the appliance up and press the space bar to freeze the GRUB menu.  You need to be fairly quick on this bit (usually takes me a couple of times)

2. Press e to enable edit mode.

3. Append rw init=/bin/bash to the end of the line

4. Press F10 to reboot. The appliance will now boot up to a shell

5. Type passwd to change the root password. Type it twice and press Enter to confirm.

6. Reboot the appliance using the power options from the VMRC or vSphere client menu, or type reboot (which ever takes your fancy).

And your done…. (if you took a snapshot do your tests then dont forget to remove it)

vCSA 6.5 Update 1 VMDK and Partition Resizing

Sometimes we have a requirement to increase the size of the drives on the vCSA Appliance due to a need for extra space for logs or we have just increased the infrastructure and need to increase the DB sizing etc. To help identify the VMDK’S to there respective mount points I have listed below the there standard sizes.

DiskSizePurposeMount Point
VMDK112GB/ and Boot / and Boot
VMDK21.8GBVCSA’s RPM packagesNot Mounted
VMDK425GBCore /storage/core
VMDK510GBLog /storage/log
VMDK610GBDB /storage/db
VMDK715GBDBLog /storage/dblog
VMDK810GBStats Events and Tasks /storage/seat
VMDK91GBNet Dumper /storage/netdump
VMDK1010GBAuto Deploy /storage/autodeploy
VMDK1110GBImage Builder/storage/imagebuilder
VMDK12100GBUpdate Manager /storage/updatemgr

For example if we need to increase the storage for the logs volume, vCSA 6.5 will allow us to do this via a hot addition (so no downtime). We just need first increase the size of VMDK5 from say 10GB to 15GB using either the vSphere Web Client or PowerCLI. Once this is complete we need to do a resize on the volume, as we like PowerCLI we will do it using some of the CIS cmdlets by doing the following:

Connect-CisServer -Server -User administrator@vsphere.local -Password VMware123!
$diskResize = Get-CisService -Name ''

(I will be doing a post later to go over some of the checks we can do on the vCSA using the CIS cmdlets)

« Older posts Newer posts »