December | 2015 | shanfitz

SCRIPT SYNOPSIS / REASON CREATED – At the time of this script, we have over 800 VMs across multiple datacenters. In a few of those DCs, we have a small number of VMs that have RDMs attached (for use with Microsoft Clustering). Our current environment is VMware 5.5 hosts, so we still are VERY careful when doing anything (vMotion, etc.) on these VMs with RDMs. Per the article at https://blogs.vmware.com/apps/2015/02/say-hello-vmotion-compatible-shared-disks-windows-clustering-vsphere.html this will be a non-issue for us when we get all hosts upgraded to vSphere 6.

OVERVIEW OF STEPS – This is a very simple script that connects to your vCenter with the supplied credentials and then gets all VMs in the environment, specifically looking for VMs with a disk type of “RawPhysical” or “RawVirtual.” Once the script identifies VMs with these types of disks, it outputs the Parent (VM) Name, Disk File Type, and SCSI Canonical Name. There is an additional line of code that is currently remarked out that can output the results to a CSV file if desired.

<# Script to Determine which VMs have RDMs attached



Created by Shannon Fitzpatrick, 12.07.15

Website: www.shanfitz.com

Twitter: @shanfitz



Last Modified Date: 12.07.15

Modifications Made: Initial Script Creation



#>



# Variables

$user = "administrator@vsphere.local"

$pass = "Password"

$vcenter = "vcenter.name"



# Connect to vCenter

connect-viserver $vcenter -user $user -password $pass



# Display VMs in environment with attached RDMs

Get-VM | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select Parent,Name,DiskType,Filename,ScsiCanonicalName



# Unremark the below command if you want to export data to a CSV file

# Get-VM | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select Parent,Name,DiskType,Filename,ScsiCanonicalName | Export-csv c:\output\rdmdisks.csv



# Disconnect vCenter

disconnect-viserver * -confirm:$false

<# Script to Determine which VMs have RDMs attached

Created by Shannon Fitzpatrick, 12.07.15

Website: www.shanfitz.com

Twitter: @shanfitz

Last Modified Date: 12.07.15

Modifications Made: Initial Script Creation

# Variables

$user = "administrator@vsphere.local"

$pass = "Password"

$vcenter = "vcenter.name"

# Connect to vCenter

connect-viserver $vcenter -user $user -password $pass

# Display VMs in environment with attached RDMs

Get-VM | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select Parent,Name,DiskType,Filename,ScsiCanonicalName

# Unremark the below command if you want to export data to a CSV file

# Get-VM | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select Parent,Name,DiskType,Filename,ScsiCanonicalName | Export-csv c:\output\rdmdisks.csv

# Disconnect vCenter

disconnect-viserver * -confirm:$false

SCRIPT SYNOPSIS / REASON CREATED – With Several Hundred Hosts in our environment, we seemingly are constantly applying host patches…many times, before we get all hosts updated to a current version, there are additional patches/fixes that need to be applied. The goal for this script is to make it easier to update all VMHosts in a designated cluster.

OVERVIEW OF STEPS – After manually putting the host(s) to be remediated into Maintenance Mode, the script below connects to vCenter, creates custom baselines (if not previously created), attaches baselines to the designated cluster, scans for needed patches, and then remediates the host(s) while disabling Power Management/FT/HA and runs simultaneously on all hosts in the cluster.

<# PowerCLI Script for Creating Patch Baselines and Remediating Hosts in a Cluster

Created by Shannon Fitzpatrick, 12.01.15
Twitter: @shanfitz
Website: www.shanfitz.com

Based up script examples found at http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-update-manager-powercli-60-inst-admg.pdf

Last Modified by Shannon Fitzpatrick, 12.01.15 (initial script creation)
#>

# Setup common variables to use
$vi_server = "vcenter.site.company.net" # Set to your vCenter hostname|IP
$vcuser = "administrator@vsphere.local" # Set to your vCenter username to connect
$vcpass = "AdminPa$$" # Set to your vCenter username password to connect

#Connect to vCenter
Connect-VIServer -Server $vi_server -User $vcuser -Password $vcpass

# Setup variable to use in script for all hosts in a specific cluster
$clustername = "Development"
$cluster = Get-Cluster $clustername

# Create Custom Baselines for patching (use if not previously created)
$criticalPatchBaseline = New-PatchBaseline -Dynamic -Name "Dynamic Baseline - Critical Patches" -SearchPatchSeverity Critical
$noncriticalPatchBaseline = New-PatchBaseline -Dynamic -Name "Dynamic Baseline - Non-Critical Patches" -SearchPatchSeverity Low,Moderate,Important

# Get Custom Baselines for patching (use if baselines have been previously created in the environment)
$criticalPatchBaseline = Get-PatchBaseline -Name "Dynamic Baseline - Critical Patches"
$noncriticalPatchBaseline = Get-PatchBaseline -Name "Dynamic Baseline - Non-Critical Patches"

# Attach Baselines to Cluster
$cluster | Attach-Baseline -Baseline $criticalPatchBaseline, noncriticalPatchBaseline

# Scan Cluster for Needed patches per attached Baselines
$cluster | Scan-Inventory

# Retrieve all Baselines attached to the Cluster
$baselines = $cluster | Get-Baseline

# Remediate all Hosts in the Cluster (Disable PM, FT, HA on cluster and patch all hosts simultaneously)
Update-Entity -Baseline $baselines -Entity $cluster -ClusterDisableDistributedPowerManagement:$true -ClusterDisableFaultTolerance:$true -ClusterDisableHighAvailability:$true -ClusterEnableParallelRemediation:$true -confirm:$false

# Disconnect from vCenter
Disconnect-VIServer * -Confirm:$false

<# PowerCLI Script for Creating Patch Baselines and Remediating Hosts in a Cluster

Created by Shannon Fitzpatrick, 12.01.15

Twitter: @shanfitz

Website: www.shanfitz.com

Based up script examples found at http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-update-manager-powercli-60-inst-admg.pdf

Last Modified by Shannon Fitzpatrick, 12.01.15 (initial script creation)

# Setup common variables to use

$vi_server = "vcenter.site.company.net" # Set to your vCenter hostname|IP

$vcuser = "administrator@vsphere.local" # Set to your vCenter username to connect

$vcpass = "AdminPa$$" # Set to your vCenter username password to connect

#Connect to vCenter

Connect-VIServer -Server $vi_server -User $vcuser -Password $vcpass

# Setup variable to use in script for all hosts in a specific cluster

$clustername = "Development"

$cluster = Get-Cluster $clustername

# Create Custom Baselines for patching (use if not previously created)

$criticalPatchBaseline = New-PatchBaseline -Dynamic -Name "Dynamic Baseline - Critical Patches" -SearchPatchSeverity Critical

$noncriticalPatchBaseline = New-PatchBaseline -Dynamic -Name "Dynamic Baseline - Non-Critical Patches" -SearchPatchSeverity Low,Moderate,Important

# Get Custom Baselines for patching (use if baselines have been previously created in the environment)

$criticalPatchBaseline = Get-PatchBaseline -Name "Dynamic Baseline - Critical Patches"

$noncriticalPatchBaseline = Get-PatchBaseline -Name "Dynamic Baseline - Non-Critical Patches"

# Attach Baselines to Cluster

$cluster | Attach-Baseline -Baseline $criticalPatchBaseline, noncriticalPatchBaseline

# Scan Cluster for Needed patches per attached Baselines

$cluster | Scan-Inventory

# Retrieve all Baselines attached to the Cluster

$baselines = $cluster | Get-Baseline

# Remediate all Hosts in the Cluster (Disable PM, FT, HA on cluster and patch all hosts simultaneously)

Update-Entity -Baseline $baselines -Entity $cluster -ClusterDisableDistributedPowerManagement:$true -ClusterDisableFaultTolerance:$true -ClusterDisableHighAvailability:$true -ClusterEnableParallelRemediation:$true -confirm:$false

# Disconnect from vCenter

Disconnect-VIServer * -Confirm:$false

shanfitz

Monthly Archives: December 2015

PowerCLI – Indentify VMs with RDM disks

Create Patch Baselines and Remediate Hosts in a Cluster

"Do or Do Not. There is no Try" – Yoda

@shanfitz:

@shanfitz:

"Do or Do Not. There is no Try" – Yoda