EveryDay Virtualization

Month: October 2018

vSphere 6.7 Update 1 Available

October 17, 2018 / / 0 Comments

You have probably already seen this in the news already but vSphere 6.7 Update 1 has now released to download. Link Is below in case you need it:

vSphere 6.7 Update 1 Download Link

 

Also to get a bit more info on whats under the hood on the updated vSphere web client i would recommend the following:

https://blogs.vmware.com/vsphere/2018/10/fully-featured-vsphere-client-in-vsphere-6-7-update-1.html?src=so_5a314d05e49f5&cid=70134000001SkJn

https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-client-65-html5-functionality-support.html

 

ISSUES

So far VEEAM is the only thing ive heard so far that has an issue: https://www.veeam.com/kb2784

New Release: PowerCLI 11.0.0

October 15, 2018 / / 0 Comments

New version of  PowerCLI released version 11

Heres a brief breakdown of the updates included:

  • Added a new Security module
  • Added new cmdlets for Host Profiles
  • Added a new cmdlet to interact with NSX-T in VMware Cloud on AWS
  • Support for vSphere 6.7 Update 1
  • Support for NSX-T 2.3
  • Support for Horizon View 7.6
  • Support for vCloud Director 9.5
  • Multiplatform support for the Cloud module
  • Updated the Get-ErrorReport cmdlet
  • Removed the PCloud module
  • Removed the HA module

Dont forget its easy to update your powercli version (see below)

1
Update-Module VMware.PowerCLI

 

And finally heres a link to the vmware article with all the info

https://blogs.vmware.com/PowerCLI/2018/10/new-release-powercli-11-0-0.html

vCloud Identifying Chain Linked VM’s

October 5, 2018 / / 0 Comments

Currently working on a project to decommission a very old non updated vcloud infrastructure for a customer who wants to move back to vsphere. They don’t really utilize the full vCloud feature set as it was put in as part of a larger project that never came to fruition.  Part of the first step should be to see what chain linked virtual machines we have, as if not when we attempt to migrate them away we are just going to give ourselves a world of pain. The PowerCLI below should identify all the virtual machines within the VDC’s and how long the chain length is.

 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
if( (Get-Module -Name "VMware.VimAutomation.Cloud" -ErrorAction SilentlyContinue) -eq $null)

{Import-Module VMware.VimAutomation.Cloud}

Connect-CIServer -Server "your vcloud director fqdn" -ErrorAction Stop

$VApps = Get-CIVApp

Foreach($vapp in $VApps){

$vms = $vapp.ExtensionData.children.vm

foreach($vm in $vms){

$CL = $vm.VCloudExtension.any.VirtualDisksMaxChainLength

if($CL -gt 1){

$info = $vm.Name + " chain length=" + $CL

$info}

}}

PowerCli List HBA WWN’s

October 2, 2018 / / 0 Comments

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:

1
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:

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

 

 

© 2025 EveryDay Virtualization

Theme by Anders Norén — Up ↑