Trainsignal Vmware 1zmi

[email protected]

:446 • Default name and are: – openfiler – * change default ! (note: root also works)

Creating a Free iSCSI SAN with OpenFiler VMware vSphere 5 Training

Configuring OpenFiler as an iSCSI SAN • • • • • • •

If using in a VM, create a second VMDK before boot Configure NTP Create partition and volume the IQN Create filesystem and select iSCSI Allow local network Enable iSCSI


Connecting vSphere to the OpenFiler iSCSI SAN To configure a new ESXi Server to use iSCSI: • Add a software iSCSI adaptor • Configure the new iSCSI adaptor to: – Use dynamic discovery – Enter the IP or hostname of the OpenFiler server (add CHAP credentials if necessary) – Perform a rescan • If it’s the first connection to the iSCSI SAN, use Add Storage to create a VMFS datastore on the new iSCSI SAN


What We Covered  Why Use OpenFiler?  ing OpenFiler  Installing OpenFiler  Configuring OpenFiler as an iSCSI SAN  Connecting vSphere to the OpenFiler iSCSI SAN

istering VMware ESXi Server Security VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

istering VMware ESXi Server Security VMware vSphere 5 Training

In This Lesson:  Basics of vSphere Security  Default vSphere Security Roles  Adding, Modifying, and Removing ESXi s and Groups  Using Windows AD s and Groups to Secure vSphere  Defining and Applying Roles and Permissions  vShield Overview  Securing Guest Virtual Machines


Basics of vSphere Security • ESXi server has local Linux-like s • vCenter, installed on Windows, uses Windows Active Directory (AD) s • vCenter, as a Linux appliance, can be configured to use Windows AD s • Recommend using Windows AD s and groups to define permissions to VC objects • All vSphere Client communications are encrypted • VLANs can be used to segment service console traffic


Basics of vSphere Security • • • •

• • • •

s and groups are assigned roles Roles are assigned to objects in the vSphere infrastructure Combining /group with a role is what created a permission By default only root can to ESXi and Win AD s on vCenter server can to vSphere Client – Assuming vCenter is installed in Windows It is not possible to run vCenter for Windows on a Windows AD domain controller Permissions take effect immediately, no need to log out and back in Permissions are inherited in a hierarchical manor, just like alarms the PoLP!


Default vSphere Security Roles • • • • • • • • •

No access Read-only VM power (sample) VM (sample) Resource pool (sample) VCB (sample) Datastore consumer (sample) Network consumer (sample)


Tasks to Perform… • Adding, modifying, and removing ESXi s and groups • Using Windows AD s and groups to secure vSphere • Defining and applying roles and permissions on different levels of the vSphere infrastructure


vShield Overview • • • • • • •

vShield vShield vShield vShield vShield vShield vShield

Zones App App with Data Security Edge Endpoint Manager Bundle



Securing Guest Virtual Machines • Treat security of guest VM as you would any other mission critical server • Install AV • Keep patches up to date • Limit , especially /root • Limit software install • Properly secure vSC Client, Web, and SSH access • Keep vSphere / ESXi patches up to date (use VMware Update Manager – VUM)


What We Covered  Basics of vSphere Security  Default vSphere Security Roles  Adding, Modifying, and Removing ESXi s and Groups  Using Windows AD s and Groups to Secure vSphere  Defining and Applying Roles and Permissions  vShield Overview  Securing Guest Virtual Machines

vSphere Virtual Networking VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

vSphere Virtual Networking VMware vSphere 5 Training

In This Lesson:  Virtual Networking  Network Adapters  Virtual Standard Switches (vSS)  vSS Functionality  Similarities Between pSwitch and vSS  Differences Between pSwitch and vSwitch  Types of vSwitches  Virtual Switch Ports  What is a VLAN?  MAC Address Changes  Forged Transmits


Virtual Networking • The virtual networking features of ESXi are the cornerstone of building an IP network for virtual machines that integrates seamlessly with the existing physical server environment


Network Adapters • The network adapters available for use in the virtual networking architecture can be identified from the Configuration | Network Adapters page

• ESXi host performs a discovery to identify network IP addresses. This facilitates understanding which networks an adapter is connected to. Note the IP range can be inaccurate if no addresses are found


Virtual Standard Switches (vSS) • vSS are logical objects that reside in the vmkernel of each ESXi host • Each virtual NIC connected to a virtual switch will have its own MAC address • vSS can be bound to one or more physical network adapters


vSS Functionality • Each virtual standard switch can contain one or more connection types or port groups that define the types of communication expected through the virtual switch • vSS operate at Layer 2 and can provide VLAN tagging, security, checksums, and segmentation offload units


Similarities Between pSwitch and vSS • Virtual standard switches are similar to physical switches in that both: – Maintain MAC address tables – Look up each frame’s destination MAC upon arrival – Forward frames to one or more ports – Avoid unnecessary deliveries


Differences Between pSwitch and vSwitch • Virtual switches are different from physical switches in that: – Virtual standard switches cannot be connected to other virtual switches the way physical switches can be – Virtual standard switches do not require Spanning Tree Protocol – Virtual standard switch isolation prevents loops in the switching configuration – Forwarding table data is unique to each virtual


Types of vSwitches • Internal only – Used for communication of two virtual machines on the same ESXi host • Single adapter – A virtual switch bound to a single physical adapter used for communication with resources on the physical network • NIC team – a virtual switch bound to 2 or more physical adapters used to provide redundancy and bandwidth aggregation for communication with resources on the physical network

VMkernel

VMkernel

VMkernel


Virtual Switch Ports • Virtual switches are made up of one more port groups or connection types that dictate the type of traffic ed by the virtual switch • The uplink ports of a virtual switch are the ports that are associated with a physical network adapter • The two port group or connection types are: – Virtual machine – VMkernel • vMotion VMkernel • Fault Tolerance Logging • Management traffic


Management Network Connection • The Management network connection type allows a virtual switch to communication to and from the ESXi management network • An IP address must be assigned to the Management network

Management network VMkernel


Management Network Configuration • A Management network port labeled as vmk0 is added to vSwitch0 during the installation of ESXi • Subsequent Management network ports will enumerate as: – vmk1 – vmk2, etc. • Multiple Management network ports creates redundancy through multiple points of entry at each IP address • Building a Management network port into a virtual switch with multiple uplinks provides redundancy with a single IP address configuration


Virtual Machine Port Group • A virtual machine port group provides associated virtual machines with access to other systems on physical networks by providing a switch-to-switch connection between the virtual switch and physical switch

VMkernel


Virtual Machine Cov

VMkernel

Communication between physical and virtual machines. Production LAN


What is a VLAN? • A VLAN is a logical configuration of a network on switch port to segment IP traffic


VLANs • Using VLANs reduces hardware needs by allowing a switch to segment IP traffic into multiple IP subnets on a port by port configuration

192.168.100.0/24

172.16.100.0/24

10.100.100.0/24


VLANs Across Geographies • VLANs allow IP subnets to extend beyond the distance limitations of the physical medium • A trunk port is a port that has knowledge of all VLANs configured • In the example here, the port that connects each switch to the nearest route is configured as a trunk port 192.168.100.0/2 172.16.100.0/24 4 10.100.100.0/24 192.168.100.0/2 172.16.100.0/24 4 10.100.100.0/24 192.168.100.0/2 172.16.100.0/24 4 10.100.100.0/24


VLANs – Virtual to Physical • Virtual switches in ESXi provide for the 802.1q VLAN tagging standard to allow virtual machines to be seen as part of VLANs configured on physical switches • In the example, the Red VLAN and Orange VLAN both contain physical and VMs that operate in their own independent broadcast domains


VLANs – Virtual to Physical

VMkernel

Physical switch port connected to uplink NIC is a trunk port


vSwitch VLANs • A virtual switch can have multiple VLANs configured by creating multiple port groups that have been assigned VLAN IDs to correspond to the VLAN IDs configured on the physical switches • vSwitch2, shown below, is configured with two virtual machine port groups named RedVLAN and OrangeVLAN with respective VLAN IDs of 100 and 101


MAC Address Changes • This setting denies incoming traffic to a VM when the MAC address defined in the configuration file (.VMX) does not match the MAC address inside the guest operating system

Don’t match. Don’t ACCEPT.

ethernet0.addressType = "generated" uuid.location = "56 4d 13 99 c9 e1 d9 41-e3 e7 c0 c1 b1 a6 2f 42" uuid.bios = "56 4d e4 66 62 74 85 7a-83 9c f9 da d5 ethernet0.generatedAddress = "00:50:56:ac:b3:5a" ethernet0.generatedAddressOffset = "0"


Forged Transmits • This setting denies outgoing traffic from a VM when the MAC address defined in the configuration file (.VMX) does not match the MAC address inside the guest operating system

Don’t match. Don’t SEND. ethernet0.addressType = "generated" uuid.location = "56 4d 13 99 c9 e1 d9 41-e3 e7 c0 c1 b1 a6 2f 42" uuid.bios = "56 4d e4 66 62 74 85 7a-83 9c f9 da d5 .ethernet0.generatedAddress = "00:50:56:ac:b3:5a" ethernet0.generatedAddressOffset = "0"


What We Covered  Virtual Networking  Network Adapters  Virtual Standard Switches (vSS)  vSS Functionality  Similarities Between pSwitch and vSS  Differences Between pSwitch and vSwitch  Types of vSwitches  Virtual Switch Ports  What is a VLAN?  MAC Address Changes  Forged Transmits

Using the vSphere Distributed Virtual Switch (dvswitch) VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Using the vSphere Distributed Virtual Switch (dvswitch) VMware vSphere 5 Training

In This Lesson:  vSphere Distributed Switch  Private VLANs – pVLANs  Networking Policies  Configuration Tasks


vSphere Distributed Switch • Creates a centralized Virtual Switch that multiple ESXi hosts can subscribe to • Reduces networking configuration and changes • Allows you to centrally manage networking for VMs across multiple ESXi hosts • Consistent network configuration and stats as VMs are migrated using vMotion • dvPort groups similar to standard vSwitch port groups but on the vDS level • Increased capabilities – security, traffic control, VLAN, and more • Ability to add 3rd party switch – Nexus 1000V


Private VLANs – pVLANs • Primary – Original VLAN that can be subdivided into multiple secondary pVLANs • Secondary – They exist only inside the primary – Each secondary pVLAN has a VLAN ID – It associates each packets with an ID that the physical switch can use to identify the mode (Promiscuous, Isolated, or Community)


pVLANs Secondary Mode Nodes • Promiscuous – May send and receive packets to any secondary pVLAN – Typically routers are attached to promiscuous ports • Isolated – May only send and receive packets from the promiscuous pVLAN • Community – May send andreceive packets between any secondary pVLAN and also with the promiscuous pVLAN


Private VLANs


Networking Policies • VLAN (vDS only) – Allows virtual networks to physical VLANs • Port blocking (vDS only) – Sets blocking policies on dvPorts • Load balancing • Security • Traffic shaping


Configuration Tasks • • • • • •

Create a new dvswitch Add hosts and vmnics to dvswitch Create a dvPort group Migrate legacy vSwitches and VM networks to dvswitch Migrate VMKernel virtual adapters to dvswitch View dvswitch – Mapping – Advanced configuration – Alarms


What We Covered  vSphere Distributed Switch  Private VLANs – pVLANs  Networking Policies  Configuration Tasks

Moving Virtual Machines with vMotion VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Moving Virtual Machines with vMotion VMware vSphere 5 Training

In This Lesson:  Why You Need vMotion  vMotion Requirements  vMotioning Virtual Machines


Why You Need vMotion • The most incredible feature of vSphere • vMotion is used to move RUNNING virtual machines off of one ESXi server to another ESXi server • VMs disk files stay where they are (on shared storage)

Why You Need vMotion Uses for vMotion: • Balance the load on ESXi Servers (DRS) • Save power by shutting down ESXi using DPM • Perform patching and maintenance on an ESXi server • Update Manager • HW maintenance

Graphic Thanks to VMware.com


vMotion Requirements • vSphere Essentials Plus, Standard, Enterprise, or Enterprise Plus • Shared storage between ESXi servers – iSCSI, FC, or NFS • VMkernel interface on both ESXi servers with vMotion enabled • Works with standard switches or dvSwitches (should keep the same network name) • U compatibility, or family compatibility if using Enhanced vMotion Compatibility (EVC) on your cluster


vMotioning Virtual Machines


What We Covered  Why You Need vMotion  vMotion Requirements  vMotioning Virtual Machines

Moving Virtual Storage with svMotion VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Moving Virtual Storage with svMotion VMware vSphere 5 Training

In This Lesson:  What is svMotion?  svMotion Requirements  svMotion and Thin Provisioning  Using svMotion  Migrating VMs with Snapshots – New in vSphere 5


What is svMotion? • Move the storage of RUNNING virtual machines from one datastore to another datastore • The running VM stays on the server that it is on • The memory for that VM never moves

What is svMotion? Uses for svMotion: • Balance the datastore utilization • Space • Performance • Perform SAN maintenance or swap out



svMotion Requirements • vSphere Enterprise or Enterprise Plus is required • Moving a powered on VM with snapshots is not ed • Note that to use the option to “change both host and datastore”, the VM must be powered off • Moving a large VMDK can take a long time, depending on your network connection


svMotion and Thin Provisioning • When you migrate storage you have the option to change from – Thin to thick – Thick to thin • Why would you want to change to a thick virtual disk from a thin virtual disk?

• Answer: Fault Tolerance (FT)


Using svMotion


Migrating VMs with Snapshots- New in vSphere 5 • With ESXi 5 / vSphere 5, you can now perform a svMotion on a VM that has snapshots Let me show you how…


What We Covered  What is svMotion?  svMotion Requirements  svMotion and Thin Provisioning  Using svMotion  Migrating VMs with Snapshots – New in vSphere 5

Performance Optimization with Distributed Resource Scheduler (DRS) VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Performance Optimization with DRS VMware vSphere 5 Training

In This Lesson:  Introduction to Distributed Resource Scheduler (DRS)  DRS Requirements  Creating a DRS Enabled Cluster  DRS/HA Cluster Settings  Understanding Resource Pools  Creating Resource Pools in Your DRS Cluster


Introduction to Distributed Resource Scheduler (DRS) The number of VMs grows The utilization of those VMs grows All this grows disproportionally It constantly expands and contracts throughout the day, week, or month • Over time, how are you going to balancing this constantly fluctuating load? • • • •


Introduction to Distributed Resource Scheduler (DRS) • Distributed resource scheduler is commonly known as DRS • It doesn’t stand for “dynamic” resource scheduler • DRS understands the resources of the virtual infrastructure – U – Memory – Power – Storage • DRS ensures that a VM gets the resources it needs • DRS does not try to achieve load balancing



Introduction to Distributed Resource Scheduler (DRS) • Hosts and Clusters provide the resources • The VMs consume the resources • Goals of DRS: – Prevent one VM from monopolizing all resources – Guarantee service levels – Offer most efficient use of server hardware – Make your life as a VMware easier


Introduction to Distributed Resource Scheduler (DRS) • DRS is enabled on a cluster • Automation levels are: – Manual – suggestions – Partially automated – auto place on power on and suggestions – Fully automated – you set the migration threshold • You can create migration rules to keep VMs together or apart • DRS can auto-place new VMs in the cluster


DRS Requirements vSphere Enterprise or Enterprise Plus Shared storage between hosts All VMs in the cluster must be on that shared storage DRS will use VMotion so it needs to work between hosts Beware of U compatibility issues and if so, consider Enhanced VMotion Compatibility (EVC) • Checkout the DRS tab and Resource Allocation tab on the cluster as well as the cluster properties • • • • •


Understanding Resource Pools • Different ways to reserve resources: – Reservation – reserve a certain amount of U or memory – Limit – set an “upper bound” of resources to this VM – Assign shares – give shares of U or memory resources • Shares set the priority of U and RAM for a VM – Set as high, normal, and low with 4:2:1 ratio – Or, you can set a custom weight • You can also set share values and IOPS per VM – These will be used with SIOC and SDRS (see other lessons on those topics)

Additional Resources


What We Covered  Introduction to Distributed Resource Scheduler (DRS)  DRS Requirements  Creating a DRS Enabled Cluster  DRS/HA Cluster Settings  Understanding Resource Pools  Creating Resource Pools in Your DRS Cluster

Implementing High Availability with VMware HA (VMHA) VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Implementing High Availability with VMware HA VMware vSphere 5 Training

In This Lesson:  Why Do You Need High Availability (HA)?  VMHA Saving the Day  VMHA Master / Slave  Requirements for VMHA  Best Practices for VMHA


Why Do You Need High Availability (HA)? • Quickly bring back up critical business applications in the event of an ESXi server failure • Decrease downtime and improve availability • Examples of business critical applications: – Exchange / email – SQL server / database – Corporate file server and intranet / web


VMHA Saving the Day • Let’s say that you have an ESXi server hardware failure (bad U or disconnected network cable) • Or, you could have an ESXi server software OS crash (unlikely) • VMHA powers all VMs running on that server on other servers in the VMHA cluster and apps are up in the time it takes guest OS to boot • VMHA monitors not only ESXi host failures but also guest OS failures • Uniform HA protection for all VM guests and all applications, no matter the OS or app • Smart failover to best ESXi host (requires DRS) • s up to 32 ESXi servers in a cluster • Enhanced isolation response


VMHA Master / Slave • 1 Master host per cluster known as the Fault Domain Manager Master (FDMS) • FDMS host is determined via an election process • FDMS host with the most mounted datastore has better election chances • VMHA check for host failure using the management network and via datastore heartbeat • FDMS host – Monitors the state of slave hosts – Monitors the state of all protected VMs – Manages the lists of cluster hosts and protected VMs • FDMS is vCenter’s management interface into the cluster’s health state


Requirements for VMHA • • • • • • • •

Shared storage for VMs running in HA cluster All hosts should have access to all VM networks Can use DRS with VMHA or just VMHA only All hosts must be licensed for VMware HA Create a VMHA enabled cluster All hosts must have a static IP address At least two hosts in the cluster At least one management network, best practice says two


Best Practices for VMHA • Keep an eye on cluster validity • Recommend you disable host monitoring as you make changes to your network or dvSwitches • All networks and VMs on HA clusters must have compatible networks • By default network isolation IP is the default gateway but you can configure others • das.isolationaddressX where X can be a value between 1-10 • Use network redundancy between ESXi servers


Best Practices for VMHA • Configure redundant network paths: – ESX – secondary SC port – ESXi – secondary VMKernel port • Configure the restart priority for VMs based on your most critical applications • Configure isolation response IP info • Configure VM Monitoring in HA cluster settings to have VMware monitor the guest OS • Configure alarms to alert you on cluster changes


What We Covered  Why Do You Need High Availability (HA)?  VMHA Saving the Day  VMHA Master / Slave  Requirements for VMHA  Best Practices for VMHA

Super High Availability with VMware Fault Tolerance (FT) VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Super High Availability with VMware Fault Tolerance (FT) VMware vSphere 5 Training

In This Lesson:  Introduction to VMware Fault Tolerance (FT)  Requirements of FT  Constraints of FT  Testing to See If You Can Use FT with VMware Site Survey  Enabling VMware FT  Testing Failover with a Virtual Machine Using FT


Introduction to VMware Fault Tolerance (FT) • FT provides continuous availability for a VM – Zero downtime • Takes VMHA to the next level • Works for all applications and 99% of guests operating systems • Does this by creating a “live shadow” copy of the running VM then keeping them in “lockstep” using VMware’s vLockstep • If an ESXi server fails, the shadow will take over and a new shadow will be created in the cluster on another ESX server


Introduction to VMware Fault Tolerance (FT) • Primary VM is called the “Primary” and the copied/lockstep VM is the “secondary” • The virtual disk for the VM is on shared storage and never moves • “Continuous VMotion”



Requirements of FT • Us on all FT ESXi servers must match and be from a specific list of processors (see KB) • Hardware virtualization enabled in the BIOS • Recommended minimum # of 1GB NICs = 3 • One NIC on each server must be enabled for FT logging and vMotion • ESXi servers must be running same build • VMs on shared SAN, accessible by servers • Must be enabled in a HA cluster • vSphere Enterprise or Enterprise Plus


Constraints of FT • • • • • • • • •

Single vU in each VM only (no SMP) Requires specific hardware Recommended minimum of 4 VMs running FT on an ESX server “Line of site” between ESXi servers due to latency Only thick disk is ed Snapshots are not allowed (includes via VADP backup products) Cannot invoke a svMotion on a VM with FT enabled Linked clones are not allowed on a VM with FT enabled Some guests not ed and some guests require shutdown to enable


Testing to See If You Can Use FT with VMware Site Survey • Checkout Eric Sloof’s (www.ntpro.nl) FT Checklist… • Site Survey saves time by automating this check • Run Site Survey on your cluster to see if you can use FT

Image Thanks to www.LandSoCAL.com

Enabling VMware FT

• Once requirements have been met, enabling FT is easy – Right-click on a VM – Go to Fault Tolerance – Click Turn On Fault Tolerance


What We Covered  Introduction to VMware Fault Tolerance (FT)  Requirements of FT  Constraints of FT  Testing to See If You Can Use FT with VMware Site Survey  Enabling VMware FT  Testing Failover with a Virtual Machine Using FT

Upgrading from VMware vSphere 4 to vSphere 5 VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Upgrading from VMware vSphere 4 to vSphere 5 VMware vSphere 5 Training

In This Lesson:  Upgrade Steps  vCenter 5  Update Manager Upgrade  ESX/ESXi Upgrade  VM Upgrade


Upgrade Prerequisites • that your ESX/ESXi servers will run vSphere 5 • that your licenses will the level of vSphere that you require – Beware of vRAM • Plan, plan, and plan some more • Review the upgrade guide – which scenario are you?


Upgrade Steps 1. 2. 3. 4. 5. 6. 7. 8.

Run vCenter Host Agent Pre-Upgrade Checker Upgrade vCenter Server Upgrade vSphere Client Upgrade your licengrade Update Manager Upgrade ESX/ESXi hosts Upgrade VM Tools and VM Hardware Upgrade datastores to VMFS-5


vCenter 5        

Requires VC downtime No production down time Database Schema will be upgraded different vCenter server Backup database ODBC credentials Uninstall UM and converter extensions vSphere compatibility matrixes


Update Manager Upgrade   

Backup database ODBC credentials Uninstall UM client extensions


ESX/ESXi Upgrade    

Requires host downtime Host in Maintenance Mode Host Upgrade Utility (GUI) 15 – 25 minutes for upgrade


VM Upgrade     

Requires VM downtime VMware Tools upgrade VM Hardware version 8 Automated upgrade via Update Manager Manual upgrade


What We Covered  Upgrade Steps  vCenter 5  Update Manager Upgrade  ESX/ESXi Upgrade  VM Upgrade

vSphere Command Line Interface (CLI) Options VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

vSphere Command Line Interface (CLI) Options VMware vSphere 5 Training

In This Lesson:  istering vSphere Using the CLI  Four vSphere CLI Options  Using ESXi Tech Mode  Using esxcfg and esxcli Commands  Getting Started with PowerCLI  Project Onyx  vCLI Basics  Installing and Using vMA


istering vSphere Using the CLI • • • •

Faster (once you get used to it) Scripting for frequent tasks or mass changes (aka “automation”) Integration with other products Because it’s cool


Four vSphere CLI Options 1. ESXi tech mode / remote TSM (SSH) – formerly known as the “hidden ESXi console” 2. PowerCLI / PowerShell and Project Onyx 3. vSphere CLI (vCLI) – from Windows 4. vSphere Management Assistant (vMA) www.VMware.com/go/systools


Using ESXi Tech Mode • Tech mode = ESXi console – Now ed • Remote tech mode = remote ESXi console via SSH – Enable and connect with an SSH client • Both can be enabled on the ESXi console via DCUI or via the vSphere client


Using esxcfg and esxcli Commands • Traditional ESXi configuration commands via TSM start with esxcfg-* • However, esxcfg-* commands have now been “depracated” and you should use esxcli instead • esxcli is all new in vSphere 5 and can do just about anything!


Getting Started with PowerCLI • PowerCLI is using Microsoft PowerShell with vSphere • the Windows PowerCLI Installer – Gives you a command line • the free Quest PowerGUI – Gives you a GUI for PowerCLI as well as pre-created scripts


Project Onyx • A free tool from VMware labs that shows you the PowerCLI commands for the configs you perform, using the vSphere client • http://labs.vmware.com/flings/onyx

Graphic thanks to VMware.com


vCLI Basics • vSphere CLI (vCLI) is a Windows application that gives you CLI tools for ESXi / vSphere • It offers esxcfg and esxcli commands Now, let’s install it and I’ll show you how it works…


Installing and Using vMA • vSphere Management Assistant (vMA) • A Linux-based virtual appliance that has “the vCLI” already in it • vMA offers – esxcfg and esxcli command line istration for ESXi / vSphere – “fast” authentication that allows you to authenticate once and then perform multiple commands Now, let’s install it and I’ll show you how it works…


What We Covered  istering vSphere Using the CLI  Four vSphere CLI Options  Using ESXi Tech Mode  Using esxcfg and esxcli Commands  Getting Started with PowerCLI  Project Onyx  vCLI Basics  Installing and Using vMA

vSphere Auto Deploy

VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

vSphere Auto Deploy VMware vSphere 5 Training

In This Lesson:  What is Auto Deploy?  Auto Deploy Components  Auto Deploy First Boot Process  Infrastructure Requirements  Installation and Configuration Tasks  Test and Repair Rules Compliance  Auto Deploy PowerCLI  Setting Up Syslog Server  Setting Dump Collector


What is Auto Deploy? • Auto Deploy allows you to quickly provision one or more stateless physical hosts with ESXi. Furthermore, Auto Deploy allows you to match certain criteria in the physical host to rule sets and deploy the appropriate ESXi image that has all the hardware drivers • Auto Deploy allows you to automatically add ESXi hosts to vCenter and apply host profiles


Auto Deploy Components • Auto Deploy Server • Rules – Active Rule Set – Working Rule Set • Image Profiles – Default Image Profiles – Custom Image Profiles • Host Profiles • Answer Files


Auto Deploy First Boot Process • Stateless host PXE boots and gets an IP address from DH • DH points the host to the TFTP server via option 66 • The host s TFTP server and s a gPXE configuration file as specified in option 67 • gPXE config file instructs the host to make HTTP boot request to Auto Deploy server • Auto Deploy queries the rules engine for information about host • An Image Profile and a Host Profile is attached to the host based on a rule set • ESXi is installed into host RAM, is added to vCenter and is configured • vCenter maintains the Image Profile and Host Profile for each host in its database


Infrastructure Requirements • DH – Option 66: FQDN or IP address of TFTP Server – Option 67: undionly.kpxe.vmw-hardwired • Router Configuration • PXE • TFTP


Installation and Configuration Tasks • • • • • •

Install and configure Auto Deploy Install TFTP server Configure DH Configure DNS Install and configure Dump Collector Install and configure Syslog Server


What You Are Going to Need • • • • • •

vCenter 5 setup files VMware PowerCLI TFTP server (we are using WinAgents TFTP) Windows Server 2008 DH and DNS ESXi 5 offline bundle A host capable of running ESXi 5


Test and Repair Rules Compliance • Make changes to a rule: – Copy-DeployRule -DeployRule Staging1 –ReplaceItem Prod • host accessibility: – Get-VMHost -Name esx6.wiredbraincoffee.com • Test and bind to a value: – $tr = Test-DeployRuleSetCompliance esx6.wiredbraincoffee.com • Remediate Host: – Repair-DeployRuleSetCompliance $tr


Auto Deploy PowerCLI • • • • • • • • • •

Get-Help cmdlet_name Get-Help cmdlet_name –Detailed Get-DeployCommand New-DeployRule Get-DeployRule Copy-DeployRule Add-DeployRule Remove-DeployRule Set-DeplyRule Get-DeployRuleset


Auto Deploy PowerCLI • • • • • • • • • •

Switch-ActiveDeployRuleset Get-VMHostMatchingRules Test-DeployRulesetCompliance Repair-DeployRulesetComplaince Apply-ESXImageProfile Get-VMImhostProfile Repair-DeployImageCache Get-VMHostAttributes Get-Deploymachine Identity Set-DeplyMachineIdentity


Setting Up Syslog Server • Esxcli: – Esxcli system syslog • Host Profiles: – Select the host and go to View | Management | Host Profiles – For a new profile, click Create Profile, or right-click a profile you want to modify and select Edit Profile – In the Edit Profile dialog, set up the syslog server host profile – Select Advanced configuration option


Setting Up Dump Collector • Esxcli: – esxcli system coredump network set --interface-name vmk0 --server-ipv4 192.168.2.52 --server-port 6500 – esxcli system coredump network set --enable true – esxcli system coredump network get • Host Profiles: – Under Network Configuration – Expand Network Coredump Settings and click Edit – Enter the server port and IP address and the host NIC to use and click the check box to enable ESXi Dump Collector – Click OK to save the host profile settings


What We Covered  What is Auto Deploy?   Auto Deploy Components   Auto Deploy First Boot Process   Infrastructure Requirements  Installation and Configuration Tasks   Test and Repair Rules Compliance  Auto Deploy PowerCLI   Setting Up Syslog Server  Setting Dump Collector 

Storage DRS


Storage DRS VMware vSphere 5 Training

In This Lesson:  Storage DRS Explained  Datastore Clusters Explained  SDRS Initial Placement  SDRS Load Balancing  Datastore Maintenance with SDRS  SDRS Affinity Rules  Configuring and Using Storage DRS


Storage DRS Explained • Today (without SDRS)… – When you create a new VM, you have to manually try to find a datastore with available space and low latency – From there, you are essentially hoping for the best storage results for the VM – Periodically, you do your best to check to see if VMs are receiving low latency and you try to monitor datastores for low space – This is “best effort” VM to storage management • This is inefficient and it is costing all parties time and money • All this manual intervention leaves lots of room for potential application outages and slowdowns • You are using DRS for U and RAM but it does nothing for storage


Storage DRS Explained • With the New Storage DRS… – VMs (and their VMDKs) are automatically placed on the datastore with the lowest latency and most space available – VMs are automatically balanced by being svMotion’ed to a better datastore if they aren’t receiving the latency they need • This will save the VMware and SAN lots of time (and the company, money). SDRS saves opex.


Datastore Clusters Explained • Like SDRS, datastore clusters are new in vSphere 5 • Without SDRS in use, a datastore cluster is a group of datastores • With SDRS, a datastore cluster is the unit used to load balance VM storage across, just like a DRS cluster



SDRS Initial Placement • Initial placement on the “correct” datastore in the datastore cluster happens at: – Creation time – When a clone is created – When a VM is relocated • SDRS VMDK affinity and anti-affinity rules are available


SDRS Load Balancing • SDRS is triggered based on– High latency – Low space • Space is continuously collected and the default threshold is 80% utilization • I/O latency is evaluated every 8 hours based on last 24 hour trend and the default threshold is 15ms • Storage DRS does do a cost/benefit analysis • SDRS works with SIOC


Datastore Maintenance with SDRS • When a datastore is put into maintenance mode, all ed VMs’ VMDKs are evacuated • Templates, ISOs, and uned VMs remain



SDRS Affinity Rules



SDRS Notes • It will take at least 16 hours of I/O statistics before SDRS will make its first recommendation based on latency, so don’t expect it to make recommendations immediately • You can create a scheduled task to modify SDRS settings (perhaps during a backup period, to prevent unnecessary migrations) • SDRS is available with a vSphere Enterprise Plus license only • For questions ing SDRS with your SAN features (autotiering, replication, dedup, and thin provisioning), see Duncan’s post-


What We Covered  Storage DRS Explained  Datastore Clusters Explained  SDRS Initial Placement  SDRS Load Balancing  Datastore Maintenance with SDRS  SDRS Affinity Rules  Configuring and Using Storage DRS

Policy-driven Storage


Policy-driven Storage VMware vSphere 5 Training

In This Lesson:  Policy-driven Storage Explained  Storage Vendor Profiles and VASA  Configuration of Policy-driven Storage


Policy-driven Storage Explained • Today, when you create a new datastore, the process of selecting what SAN LUN it will be stored on is manual • Also, when you perform the more common task of creating a new VM, the process of selecting what datastore they will be stored on is manual • VMware s have to work with SAN s to perform all these tasks – Even if you are the SAN , it still takes additional work • Multiple steps for vSphere and SAN s can be saved by using policy-driven storage, resulting in significant time and money (opex)


Policy-driven Storage Explained • Policy-driven storage allows you to: – Define storage capabilities (ie: capacity, performance, availability, redundancy) • Custom • Learned from SAN hardware (via VASA) – Associate storage capabilities with datastores – Create storage profiles (Gold/Silver/Bronze) – Associate a VM with a profiles – All this allows vSphere to place a VM on a datastore that meets its needs – automatically - and it allows you to report and find if VMs are on the right storage


Name Change Alert • Policy-driven Storage is now Profile-driven Storage




Storage Vendor Profiles and VASA • Storage capabilities come from either VASA or they are defined • vSphere Storage APIs – Storage Awareness = VASA • VASA-capable arrays are setup as vSphere “Storage Providers” • VASA-capable arrays then tell vSphere: – Their capabilities – Their performance (useful for SDRS)

“Note to self: find out if my storage s VASA”


Configuring Policy-driven Storage 1. Obtain storage capabilities – VASA (vCenter Storage Providers) – Create -defined storage capabilities 2. Create a VM Storage Profile 3. Assign -defined storage capabilities to datastores 4. Assign VMs a storage profile – When created – On each VM’s Properties, Profiles tab


What We Covered  Policy-driven Storage Explained  Storage Vendor Profiles and VASA  Configuration of Policy-driven Storage

Understanding the New vSphere 5 vRAM Pooled Pricing VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Understanding the New vSphere 5 vRAM Pooled Pricing VMware vSphere 5 Training

In This Lesson:  Why is vSphere 5 vRAM Pooled Pricing So Important?  3 Major Changes with vSphere 5 Licensing  vRAM Pooled Pricing in Action  vSphere 5 vRAM Entitlements  Requirements to Access vRAM Pooled Pricing Reports  vSphere 5 License Validator Script  Using vSphere License Advisor  4 Ways to Reduce Your vRAM Pool Utilization


Why is vSphere 5 vRAM Pooled Pricing So Important? • A significant change to vSphere licensing • Places a soft limit on virtual machines when a pool-wide limit is reached (with vCenter Standard) • You will be violating your end license agreement (EULA) and receive a warning if you exceed the pool with vSphere Standard, Enterprise, or Enterprise Plus • You will be violating your end license agreement (EULA) and will not be able to power on a VM if you exceed the pool with vSphere Essentials and Essentials Plus (vCenter Foundations) • This change should affect how you provision your VMs and it may affect your cost


3 Major Changes with vSphere 5 Licensing 1. vSphere is still sold per U socket 2. vSphere advanced edition is gone AND vSphere U core and physical RAM capacity per host restrictions are gone 3. Each vSphere edition now comes with a vRAM entitlement that is pooled by vCenter, per version


vRAM Pooled Pricing in Action • vRAM pooled pricing is based on configured vRAM in use by Powered On virtual machines




vSphere 5 vRAM Entitlements vSphere Hypervisor Free Edition = 32GB per server vSphere Essentials and Essentials Plus = 32GB vSphere Standard = 32GB vSphere Enterprise = 64GB vSphere Enterprise Plus = 96GB Again, vSphere 5 is still sold on a per U socket license (or in a kit) but now each edition has specific vRAM entitlements that will be pooled, per vCenter, per version of vSphere • A new version of vSphere is available, vSphere Desktop Edition, that is sold based on a per VDI desktop basis. • • • • • •


vSphere 5 vRAM Entitlements • August 3 Updates: – vRAM Entitlements were increased – Cap the amount of vRAM counted per VM at 96GB – Calculate a 12 month average of configured vRAM rather than a high water mark


Requirements to Access vRAM Pooled Pricing Reports • vSphere web client (server) must be installed • Traditional Windows-based vSphere Client must be used • Go to Home  Licensing  Reporting (tab)


vSphere 5 License Validator Script

http://www.virtu-al.net/2011/07/14/vsphere-5-license-entitlements


Using vSphere License Advisor • A free tool from VMware that advises you on vSphere license usage • Especially important if planning an upgrade from vSphere 4 to 5 • Tiny Windows install that connects to a single vCenter server • The tool does not recognize multiple vCenter servers in linked mode • Requires that the Java runtime engine (JRE) be installed • Offers the ability to export data


Using vSphere License Advisor



4 Ways to Reduce Your vRAM Pool Utilization 1. Rightsize the memory on each of your virtual machines 2. Power off virtual machines that are unused 3. Understand application memory utilization and find ways to reduce it 4. that all hosts in your enterprise with vSphere licenses count toward the pool (including VMHA hosts who are in standby mode and even remote servers if you are using vCenter linked mode) Tips: • vSphere licenses are per socket and not per core • You could implement chargeback to charge the groups in your company who use the most memory • Standardize on the same license of vSphere


What We Covered  Why is vSphere 5 vRAM Pooled Pricing So Important?  3 Major Changes with vSphere 5 Licensing  vRAM Pooled Pricing in Action  vSphere 5 vRAM Entitlements  Requirements to Access vRAM Pooled Pricing Reports  vSphere 5 License Validator Script  Using vSphere License Advisor  4 Ways to Reduce Your vRAM Pool Utilization

Network I/O Control (NIOC) VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Network I/O Control (NIOC) VMware vSphere 5 Training

In This Lesson:  What is Network I/O Control?  New in vSphere 5 NIOC  Configuring Network I/O Control


What is Network I/O Control? • Provide QoS for network traffic by type • Requires vSphere Enterprise Plus and use of vDS



What is Network I/O Control? New feature in vSphere 4.1 AKA NetIOC or NIOC QoS for the virtual network Uses shares, which you are already used to using in vSphere with resources pools • Ensures best performance for critical vSphere infrastructure services when there is high network utilization – NFS – iSCSI – FT – vMotion • For more information, see vSphere Network I/O Best Practices http://www.vmware.com/resources/techresources/10119 • • • •


New in vSphere 5 NIOC • -defined network resource pools – Enables multi-tenancy deployment – Bridges virtual and physical infrastructure QoS by using per resource pool 802.1p tagging


Configuring Network I/O Control



What We Covered  What is Network I/O Control?  What’s New in vSphere 5 NIOC?  Configuring Network I/O Control

Storage I/O Control (SIOC) VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

Storage I/O Control (SIOC) VMware vSphere 5 Training

In This Lesson:  Why You Need Storage I/O Control (SIOC)  How SIOC Works  SIOC Requirements  Enabling SIOC in vSphere  Monitoring SIOC Performance


Why You Need Storage I/O Control (SIOC) • General consensus is that most virtualization performance issues are caused by latency in shared storage • Storage I/O Control provides “Quality of Service” (QoS) to ensure that all VMs get the storage performance the require • In summary, SIOC is necessary so that one VM doesn’t slow down another (regarding storage resources)


How SIOC Works

Graphics Thanks to VMware.com


SIOC Requirements • • • • •

Datastores must be managed by a single vCenter server FC, iSCSI, and NFS are ed (RDMs are not) for NFS is new in vSphere 5! Datastores with multiple extents are not ed vSphere 4.1 or later (vSphere 5 to use NFS)


Enabling SIOC in vSphere • SIOC is enabled per datastore • Once enabled, ESXi monitors the latency of that datastore • To enable SIOC: – Go to the ESXi Server – Configuration tab – Storage – Select the Datastore – Click Properties


Enabling SIOC in vSphere • Set the number of shares and maximum number of IOPS per VM – Default is Normal/1000 – Unlimited IOPS • Note:

“If the limit you want to set for a virtual machine is in of MB per second instead of IOPS, you can convert MB per second into IOPS based on the typical I/O size for that virtual machine. For example, to restrict a backup application with 64KB IOs to 10 MB per second, set a limit of 160 IOPS.”


Enabling SIOC in vSphere • To set the shares and maximums – Go to the Datastores view in the vSphere Inventory – Select the Virtual Machines tab or – Go to the Properties of each VM – Resources tab • Monitor SIOC Latency and IOPS in the Datastore Inventory, Performance tab


What We Covered  Why You Need Storage I/O Control (SIOC)  How SIOC Works  SIOC Requirements  Enabling SIOC in vSphere  Monitoring SIOC Performance

ESXi Firewall


ESXi Firewall VMware vSphere 5 Training

In This Lesson:  ESXi Firewall Defined  Configuration Files  Rule Set Add  Service Behavior  ESXI Shell Firewall Configuration


ESXi Firewall Defined • The ESXi Firewall is a new service-oriented, stateless firewall used to protect the management interface of ESXi • The firewall can be configured either from a GUI through the vSphere client or via the command-line using esxcli


Configuration Files • Rule set configuration files • Service configuration files


Rule Set Add • /etc/vmware/firewall/ Option

Description

<service id='nnnn'>

Numeric identifier for the service. If the configuration file contains only one service, you do not need a service ID. Use <service>

Usually the name of the service

Numeric identifier for the rule

Port direction (inbound or outbound)

<protocol>

Protocol for the port (t or udp)

<porttype>

Type of port, destination or source (dst or src)

<port>

Port number or range of ports. To enter a range, use and <end> tags

<enabled>

Status of the service when the rule set is applied (true or false)

<required>

Whether the ruleset is required and cannot be disabled (true or false)


Example: Rule Set Configuration File <service id='0000'> serviceName inbound <protocol>t <porttype>dst <port>80 inbound <protocol>t <porttype>src <port> 1020 <end>1050 <enabled>true <required>false


Service Behavior • Start automatically if any ports are open and stop when all ports are closed • Start and stop with host • Start and stop manually


ESXi Shell Firewall Configuration Command

Description

esxcli network firewall get

Returns the enabled or disabled status of the firewall and lists default actions

esxcli network firewall set --defaultaction

Update default actions

esxcli network firewall set –enabled

Enable or disable the ESXi firewall

esxcli network firewall load

Load the firewall module and rule set configuration files

esxcli network firewall refresh

Refresh the firewall configuration by reading the rule set files if the firewall module is loaded

esxcli network firewall unload

Destroy filters and unload the firewall module

esxcli network firewall ruleset list

List rule sets information

esxcli network firewall ruleset set --allowedall

Set the allowedall flag

esxcli network firewall ruleset set --enabled

Enable or disable the specified rule set

esxcli network firewall ruleset allowedip list

List the allowed IP addresses of the specified rule set

esxcli network firewall ruleset allowedip add

Allow access to the rule set from the specified IP address or range of IP addresses

esxcli network firewall ruleset allowedip remove

Remove access to the rule set from the specified IP address or range of IP addresses


What We Covered  ESXi Firewall Defined   Configuration Files   Rule Set Add   Service Behavior   ESXI Shell Firewall Configuration 

VMware Data Recovery (VDR) 2 VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

VMware Data Recovery (VDR) 2 VMware vSphere 5 Training

In This Lesson:  Introduction to VMware Data Recovery (VDR) 2  New VDR Features in vSphere 5  Limitations of VDR  Installing VDR  VDR Initial Configuration  Backup and Restore with Data Recovery


Introduction to VMware Data Recovery (VDR) 2 • VDR is a VMware virtualization-specific backup and recovery application for VMware vSphere 4 and 5 • Easy to deploy as an appliance, integrates with vCenter, and istered from vCenter • Provides backup and restore of guest Virtual Machines • Advanced features like: – De-duplication – File level restore – Incremental/differential backup • Included with vSphere Editions – Essentials Plus, Standard, Enterprise, and Enterprise Plus


Introduction to VMware Data Recovery (VDR) 2 • Appliance and plug-in – No physical server and no COS to install • Fully integrated with vCenter • Works if VMs are on or off • Uses snapshots for anytime BU • s VSS for Windows BU • Uses VADP (vSphere API for Data Protection) framework


Introduction to VMware Data Recovery (VDR) 2 • Can backup entire vSphere infrastructure in a few clicks • No agents and works on any OS • Complete management of backup and recovery through the vSphere Client • Included with vSphere • Deduplication and compression are automatic


New VDR Features in vSphere 5 • In vSphere 4.1, VDR 1.2 offered: – Linux file level restore – VSS in Win 2008 and Win 2008 R2 at the app level – Up to 10 appliances per vCenter (and up to 100 VMs per appliance) – VDR log can be sent to the syslog server


New VDR Features in vSphere 5 • In vSphere 5, VDR 2.0 offers: – Now uses Cent OS 5.5 64-bit – better scalability and stability – Swap files not included in backups anymore – Integrity checks and reclaim operations can be scheduled, resumed, and run in the background – Overall performance of backups and other operations has been improved – Email reporting has been added


Limitations of VDR • Backup datastore recommended to be no more than 1TB of de-dup data and 2 destination total (500MB if CIFS) • 8 concurrent VMDK backups • Maximum of 100 VMs can be backed up per VDR appliance – You can add another VDR appliance • Maximum of 10 VDR appliances per vCenter Server – Maximum of 1000 VMs per vCenter that can be backed-up with VDR • Does not provide a method to get backup data onto tape or offsite


Installing VDR • 60 Day evaluation is available with vSphere – Or, you must be using Essentials Plus, Standard, Enterprise, Enterprise Plus, or purchased a la carte with Essentials • VDR on the same page that you vSphere • VDR is a single file in ISO format • Either burn to media, mount the ISO, or unzip the ISO to gain access to the files inside • Deploy the VDR appliance from the OVF file • Install the VDR vSphere Client plug-in with the Windows installer


VDR Initial Configuration You must add a storage destination before powering up VDR You can add a VMDK virtual disk destination or network share A VMDK, kept with the VM, is my favorite Once you create a VMDK destination, format and mount it VMware recommends using a thick VMDK for performance reasons • Powering on VDR is like powering on any VM • After initial power on, use the CLI to change the root • Default name and : – root – vmw@re • • • • •


VDR Initial Configuration • Once powered on and is changed, do the following from the web interface: – Set a static IP address (can also do using CLI) – Set the correct time zone – Reboot – Double check configurations once it comes back • To power off the VDR appliance properly, use the web interface or CLI


Backup and Restore with Data Recovery

Graphics Thanks to VMware.com


What We Covered  Introduction to VMware Data Recovery (VDR) 2  New VDR Features in vSphere 5  Limitations of VDR  Installing VDR  VDR Initial Configuration  Backup and Restore with Data Recovery

istering vSphere Using an iPad VMware vSphere 5 Training Instructors: David Davis and Elias Khnaser

istering vSphere Using an iPad VMware vSphere 5 Training

In This Lesson:  Features of the vSphere Client for iPad  Requirements for the vSphere Client for iPad  Installing vCenter Mobile Access (vCMA)  Installing vSphere Client for iPad  istering vSphere Using an iPad


Features of the vSphere Client for iPad • Search for vSphere hosts and VMs • Monitor the performance of vSphere hosts and VMs • Manage virtual machines with the ability to start, stop and suspend • View and restore virtual machines’ snapshots • Reboot vSphere hosts or put them into maintenance mode • Diagnose vSphere hosts and virtual machines using built-in ping and traceroute tools


Requirements for the vSphere Client for iPad • vSphere and vCenter already in place • vCenter Mobile Access (vCMA) virtual appliance available from the VMware Labs: http://labs.vmware.com/flings/vcma • Network connection to the vCMA – Via LAN or Internet VPN • vSphere Client for iPad – Via iTunes store • Note: this is all free except your vSphere and vCenter infrastructure


Installing vCenter Mobile Access (vCMA) • vCMA is a free virtual appliance from VMware Labs • It allows you to manage your virtual infrastructure from mobile devices, like smartphones and iPads – Via web browser and the vSphere Client for iPad • the OVF file and Deploy it, through the vSphere Client http://labs.vmware.com/flings/vcma


Installing vSphere Client for iPad • A free Apple iPad client for istering vSphere • Requires local LAN access or VPN access to the vCMA • Just like any iPad app, ed through iTunes and installed on the iPad • Search in iTunes for “vSphere Client” or go tohttp://itunes.apple.com/us/app/vm ware-vsphere-clientfor/id417323354?mt=8&ls=1


istering vSphere Using an iPad • To connect: – Get the IP address (or DNS name) of the vCMA VM – Enter that IP address (or DNS name) in the Settings on the iPad, for the vCMA, when you first launch the client • Connect to the vSphere infrastructure using the vSphere Client for iPad by entering your vCenter server name, name, and • You’re ready!


What We Covered  Benefits of the vSphere Client for iPad  Requirements for the vSphere Client for iPad  Installing vCenter Mobile Access (vCMA)  Installing vSphere Client for iPad  istering vSphere Using an iPad

Trainsignal Vmware 1zmi

Overview 26281t

More details 6y5l6z

Related Documents 3h463d

Trainsignal Vmware 1zmi

Vmware-vmware-it-case-study.pdf 3d2b64

Vmware Troubleshoot 3x5822

Presentacion Vmware 2322d

Vmware Alignment 5q2653

Vmware Vdiskmanager 2n73y

More Documents from "Onkar Ashok Kelji" 6pd4v

Trainsignal Vmware 1zmi

Lean Tpm - Downtime Waste Controls 5b1c3

How To Configure Sametime Business Cards And Photo Read From Connections Profiles. 4k3153

46028332127-annayya-02 4m1f5t

Autozine Technical School - Engine Smoothness 3 414e67

Radioactivity Worksheet............. 6q213g