Presentation is loading. Please wait.

Presentation is loading. Please wait.

Demo: Installation of ESXi 4.1 U1

Similar presentations

Presentation on theme: "Demo: Installation of ESXi 4.1 U1"— Presentation transcript:

1 Demo: Installation of ESXi 4.1 U1
12 Topic 3: ESXi Installation

2 ESX 4.1 Installation 26 Topic 4: ESX Installation
To navigate and perform actions in the ESX Server installer, press the Tab key, spacebar, directional arrows, or Enter key. You can: Move the highlight between selection fields with the Tab key. Make a selection within a field using the arrow keys or by typing a value. Press Tab until the highlight is in the OK box, and press either the spacebar or Enter key. 26 Topic 4: ESX Installation

3 Resetting root Password ESX
If the root password for ESX host is lost, you can change the it on ESX host without re-installing Power On or Reboot the ESX host and at the GRUB menu, press 'a'. Type “single” at the end of the line (after the word “quiet”). The ESX host will boot to a # prompt. Type 'passwd' and enter a new UNIX password twice for root. Type 'reboot' By adding single to the end of the kernel arguments, the Service Console will be booted into single user mode. You will automatically be logged in as root without you having to type in a password. Changing the password is then a simple task. Once you reboot the server, you “own” it, it’s yours. Without physical security you have no security. 3 Topic 6: Troubleshooting ESX/ESXi

4 Troubleshooting ESXi CIM Management Agents
Use DCUI  Restart Management Agents under Troubleshooting Options From CLI type /sbin/ restart automatically restarts multiple CIM services Common Errors solved by restarting the Management Agents: Cannot connect ESX to VirtualCenter Cannot connect ESX to vCenter Server Cannot connect directly to ESX Server from the VMware Infrastructure Client Cannot connect directly to the ESX Server from the vSphere Client You cannot stop or start a virtual machine A virtual machine is shown as running in VirtualCenter when it is not 1 1 Topic 6: Troubleshooting ESX/ESXi

5 Chapter 3 Review Questions
1. During installation of ESX 4, for which account do you create a password? User1 Admin Administrator root 2. Which two server resources would most influence the sizing of hardware for an ESX host? Hard disk size Network card speed The amount of RAM The number of CPUs, Cores or Speed 3. You can enter a VLAN ID for the Service Console during the installation of VMware ESX? True False 4. What is the maximum memory size that an administrator can set the Service Console to in ESX? 800 MB 1600 MB 544 MB 272 MB 5. To configure an ESX host to boot from a fibre channel LUN? (Choose two) Configure the server BIOS to designate the fibre channel HBA card as the boot controller Configure the fibre channel controller to initiate a connection to the target boot LUN Configure the fibre channel switch with the World Wide Name of the ESX host In vCenter, configure a datastore and mark it as bootable Chapter 3 - Review Questions

6 The Management User Interface (MUI) (ESX/ESXi/vCenter)
ESX/ESXi Mgt IP, vCenter IP address or FQDN vCenter Download the vSphere Client to your desktop or management workstation 2 Topic 2: ESX/ESXi Management

7 Configuration of TSM in ESXi 4.1
TSM has two options: Local Tech Support Mode (ESX like command line) Remote Tech Support Mode (SSH Daemon) Supported Modes New to ESXi 4.1 Enabled on host or through vCenter 5 Topic 4: ESXi Installation

8 Add Network Wizard Can be used to create a vSwitch
Used to create/add one of three connection types Used for IP and subnet mask configuration of the VMkernel or SC port The VLAN ID can be configured ESX Wizard ESXi Wizard NOTE: To add additional connection types to an existing vSwitch, run the Add Network Wizard from the Properties link of the vSwitch 1 Topic 1: Creating & Modifying Virtual Networks

9 Configure Physical NICs
esxcfg-nics –s 1000 –d full vmnic0 esxcfg-nics –s 100 –d full vmnic1 esxcfg-nics –s 1000 –d full vmnic2 esxcfg-nics –s 100 –d full vmnic3 esxcfg-nics –l 9 5 Topic 2: Creating & Modifying Virtual Networks using CLI

10 Configure Virtual Switches
:64 Not supported in vCLI esxcfg-vswitch –a vSwitch4:64 esxcfg-vswitch –A PortVLAN101 vSwitch4 esxcfg-vswitch –A PortVLAN102 vSwitch4 esxcfg-vswitch –v 101 –p PortVLAN101 vSwitch4 TCP Segmentation Offload (TSO) and Jumbo Frame support are added in ESX Server 3i/3.5. Jumbo Frames must be enabled at the server level using the either the Service Console or the Remote CLI to configure the MTU size for each vSwitch. TSO is enabled on the VMkernel interface by default, but must be enabled at the virtual machine level. Enabling TSO support through the Enhanced vmxnet network adapter is available for virtual machines running the following guest operating systems: Microsoft Windows 2003 Enterprise Edition with Service Pack 2 (32-bit and 64-bit) Red Hat Enterprise Linux 4 (64-bit) Red Hat Enterprise Linux 5 (32-bit and 64-bit) SuSE Linux Enterprise Server 10 (32-bit and 64-bit) To enable TSO at the virtual machine level, you must replace the existing vmxnet or Flexible virtual network adapters with Enhanced vmxnet virtual network adapters. This may result in a change in the MAC address of the virtual network adapter. To enable TSO support for a virtual machine Log in to the VI Client and select the virtual machine from the inventory panel. The hardware configuration page for this server appears. Click the Summary tab, and click Edit Settings. Select the network adapter from the Hardware list. Record the network settings and MAC address that the network adapter is using. Click Remove to remove the network adapter from the virtual machine. Click Add. Select Ethernet Adapter and click Next. In the Adapter Type group, select Enhanced vmxnet. Select the network setting and MAC address that the old network adapter was using and click Next. Click Finish. Click OK. If the virtual machine is not set to upgrade VMware Tools at each power-on, you must upgrade VMware Tools manually. See the Basic System Administration Guide. TSO is enabled by default on a VMkernel interface. If TSO gets disabled for a particular VMkernel interface, the only way to enable TSO is to delete that VMkernel interface and re-create it with TSO enabled. esxcfg-vswitch –v 102 –p PortVLAN102 vSwitch4 esxcfg-vswitch –L vmnic2 vSwitch4 esxcfg-vswitch –L vmnic3 vSwitch4 VMNIC4 10 7 Topic 2: Creating & Modifying Virtual Networks using CLI

11 Configure the VMkernel Port
esxcfg-vswitch –a vSwitch4:16 Cannot set both vMotion and FT logging on same vSwitch from CLI esxcfg-vswitch –A vMotion vSwitch4 esxcfg-vswitch –L vmnic2 vSwitch4 esxcfg-vswitch –L vmnic3 vSwitch4 esxcfg-vmknic –a –i –n vMotion vim-cmd hostsvc/vmotion/vnic_set vmk0 A VMkernel port is a special type of port group on a virtual Ethernet switch which is used to assign an IP address to the VMkernel. The VMkernel only needs an IP address for vMotion, software-initiated iSCSI or NFS access Additional vimsh commands: And Commands in the slide are: Create a vSwitch named vSwitch4 with 16 ports (8 usable) esxcfg-vswitch –a vSwitch4:16 Create a portgroup on vSwitch4 named vMotion esxcfg-vswitch –A vMotion vSwitch4 Link vmnic2 & vmnic3 to vSwitch4 esxcfg-vswitch –L vmnic2 vSwitch4 esxcfg-vswitch –L vmnic3 vSwitch4 Use esxcfg-vmknic command to change portgroup labeled vMotion into a VMkernel port esxcfg-vmknic –a –i –n vMotion Select vMotion checkbox or turn on vMotion vim-cmd hostsvc/vmotion/vnic_set vmk0 Select FT logging checkbox or turn on FT logging (Cannot be done from CLI on same vSwitch as vMotion command above) vim-cmd hostsvc/advopt/update FT.Vmknic string vmk0 Create Default Gateway for VMkernel port esxcfg-route Create static route for the VMkernel port esxcfg-route –a List VMkernel port routing table esxcfg-route –l vim-cmd hostsvc/advopt/update FT.Vmknic string vmk0 vim-cmd hostsvc/advopt/update Net.ManagementIface string vmk0 ESXi only esxcfg-route esxcfg-route –a esxcfg-route –l 11 9 Topic 2: Creating & Modifying Virtual Networks using CLI

12 Adding a second Service Console
esxcfg-vswitch –a vSwitch4:16 esxcfg-vswitch –L vmnic2 vSwitch4 esxcfg-vswitch –L vmnic3 vSwitch4 esxcfg-vswitch –A SCon2 vSwitch4 esxcfg-vswif –a –i n p SCon2 vswif1 Commands used in slide: Create a vSwitch named vSwitch4 with 16 ports (8 usable) esxcfg-vswitch –a vSwitch4:16 Link vmnic2 & vmnic3 to vSwitch4 esxcfg-vswitch –L vmnic2 vSwitch4 esxcfg-vswitch –L vmnic3 vSwitch4 Create a portgroup on vSwitch4 named SCon2 esxcfg-vswitch –A SCon2 vSwitch4 Use esxcfg-vswif command to change portgroup labeled SCon2 into a Service Console port esxcfg-vswif –a –i n p SCon2 vswif1 Create a portgroup on vSwitch4 named IPStorage esxcfg-vswitch –A IPStorage vSwitch4 Use esxcfg-vmknic command to change portgroup labeled IPStorage into a VMkernel port esxcfg-vmknic –a –i –n IPStorage Put both the new Service Cconsole Port & the VMkernel port on VLAN 33 esxcfg-vswitch –v 33 –p SCon2 vSwitch4 esxcfg-vswitch –v 33 –p IPStorage vSwitch4 esxcfg-vswitch –A IPStorage vSwitch4 esxcfg-vmknic –a –i –n IPStorage esxcfg-vswitch –v 33 –p SCon2 vSwitch4 esxcfg-vswitch –v 33 –p IPStorage vSwitch4 12 9 Topic 2: Creating & Modifying Virtual Networks using CLI

13 Viewing Multipathing Path States:
Active (I/O), Active, Disabled, and Dead Preferred path is designated with an * Active (I/O) is the current path being used under Fixed and MRU If a path fails, the surviving paths carry all the traffic. Path failover might take a minute or more, because the fabric might converge with a new topology to try to restore service. This delay is necessary to allow the SAN fabric to stabilize its configuration after topology changes or other fabric events. Example of iSCSI Multipathing Example of Fibre Channel Multipathing 5 Topic 1: Storage Concepts

14 Storage I/O Control (SIOC)
New in 4.1 QoS for storage access on a per VM basis Enabled on a per Datastore basis All hosts accessing SAN must be in same vCenter Sets a threshold for when Disk Shares will be used to prioritize disk IOPs Disk shares are calculated across all hosts managed by vCenter Setting the Congestion Threshold Value for Storage I/O Control The congestion threshold value for a datastore is the upper limit of latency that is allowed for a datastore before Storage I/O Control begins to assign importance to the virtual machine workloads according to their shares. You do not need to adjust the congestion threshold setting in most environments. Do not make any changes to these settings unless you are working with the VMware support team or otherwise have thorough information about the values to provide for the settings. For more information, see the VMware Knowledge Base article, Setting the Congestion Threshold Value for Storage I/O Control. Storage I/O Control Best Practices: Enable Storage I/O Control on all datastores Avoid external access for SIOC enabled datastores When multiple datastores share the same set of spindles ensure all have SIOC enabled with comparable settings Change latency threshold based on used storage media type: For FC storage the recommended latency threshold is 20 – 30 MS For SAS storage the recommended latency threshold is 20 – 30 MS For SATA storage the recommended latency threshold is 30 – 50 MS For SSD storage the recommended latency threshold is 15 – 20 MS Define a limit per VM for IOPS to avoid a single VM flooding the array For instance limit the amount of IOPS per VM to a 1000 Shares and IOPs Limits are visible per VM in the Datastores inventory view from the Virtual Machines tab Recommended Congestion Thresholds: SSD – ms SAS – ms SATA – ms Shares and IOPs Limits are set on a per VM per VMDK basis from the Resources tab 2 Topic 1: Storage Concepts

15 Configure Software Initiator
Enable the iSCSI initiator, the iSCSI name is automatically filled in Change iSCSI name to match your setup The iSCSI initiator needs to enabled, then return to the same menu to reconfigure the initiator. 1 Topic 2: iSCSI Storage (GUI & Command Line)

16 Discovering iSCSI Targets
Enter the IP address/Port of each iSCSI target Maximum targets: 64 Static Discovery Enter iSCSI Target Name Dynamic Discovery Uses “Send Targets” to discover LUNs and all available paths Static Discovery will only find the specific iqn number listed. Dynamic Discovery finds all of the targets that are defined at the storage processor for this initiator. 2 Topic 2: iSCSI Storage (GUI & Command Line)

17 Configure Software Initiator: CHAP Authentication
Challenge-Handshake Authentication Protocol (CHAP) is disabled by default Authentication can be Host to Target or Target to Host Enable CHAP and enter CHAP name and CHAP secret Several mechanisms can be used to limit which volumes an ESX Server host can access on an iSCSI storage system. You must configure the ESX Server and the iSCSI storage system to support your storage access control policy. Discovery - A discovery session is part of the iSCSI protocol, and it returns the set of targets you can access on an iSCSI storage system. The two types of discovery available on ESX Server are dynamic and static. Dynamic discovery obtains a list of accessible targets from the iSCSI storage system, while static discovery can only try to access one particular target by target name. Authentication - iSCSI storage systems authenticate an initiator by a name and key pair. ESX Server supports the CHAP protocol, which VMware recommends for your SAN implementation. The ESX Server host and the iSCSI storage system need to have CHAP enabled, and to have common credentials. In the iSCSI login phrase, the iSCSI storage system exchanges and checks these credentials. Access Control - A policy set up on the iSCSI storage system. Most implementations support one or more of three types of access control: By initiator name By IP address By the CHAP protocol Only initiators that meet all rules attached to the iSCSI volume can access it. CHAP can be set for: All Targets Each Target Server Each Target LUN individually 2 Topic 2: iSCSI Storage (GUI & Command Line)

18 Viewing and Creating a VMFS Datastore
Changing the block size of your local VMFS during the install… If you want to do this now, the only way to do it is by mucking around with the installer internals (and knowing how to use vi). It’s not that difficult if you’re familiar with using a command line. Try these steps for changing it with a graphical installation: boot the ESX installation DVD in text mode switch to the shell (Alt-F2) ps | grep Xorg kill the PID which comes up with something like “Xorg -br -logfile …”. On my system this comes up as PID 590, so “kill 590″ cd /usr/lib/vmware/weasel vi scroll down to the part which says “class vmfs3FileSystem(FileSystemType):” edit the “blockSizeMB” parameter to the block size that you want. it will currently be set to ’1′. the only values that will probably work are 1, 2, 4, and 8. save and exit the file cd / /bin/weasel After that, run through the installer as you normally would. To check that it worked, after the installer has completed you can go back to a different terminal (try Ctl-Alt-F3 since weasel is now running on tty2) and look through /var/log/weasel.log for the vmfstools creation command. 6 Topic 4: VMFS Datastores (GUI & Command Line)

19 Add an Extent to Existing VMFS
The list of possible extents to add will not include LUNs with an existing VMFS, or an RDM mounted to a VM 6 Topic 4: VMFS Datastores (GUI & Command Line)

20 Expand an ESX/ESXi 4.1 VMFS Volume
ESX/ESXi 4 can dynamically expand VMFS volumes The first step would be to Expand the LUN originally chosen for the datastore The SAN administrator would have to use the SAN Manufacturer’s management software to perform the expansion Following is an example performed on a Dell Equalogic iSCSI SAN LUN Select Properties to begin the process Select the LUN or Disk showing as Expandable Now, select Increase to begin the Expansion Notice Capacity is now 10 GB Notice only one Extent of 10 GB 13 Topic 4: VMFS Datastores (GUI & Command Line)

21 Manage vSphere Licenses
8 Topic 1: Licensing

22 Microsoft Server Virtualization Validation Program
Validate Microsoft Server Apps for Support before virtualizing them with vSphere 4 3 Topic 1: Licensing

23 Datastores: Folders and Datastores
Create Folders to organize Datastores logically SIOC Shares and IOPs shown per VM 23 All Datastores across all hosts in vCenter are visible Datastore information available on many tabs Organize Datastores using Folder objects Permissions may be set on Folders 9 Topic 3: vCenter Server Inventory

24 Networks: Portgroups & Distributed Switches (vDS)
Context menu for a Distributed Switch has several options Context menu for a Portgroup has only a few options 24 All Networks and vDSs across all hosts in vCenter are visible Networks (Portgroups from simple vSwitch) have far fewer tabs than those from vDS Permissions may be set on Portgroup or vDS/DVUplink/DVPG 9 Topic 3: vCenter Server Inventory

25 Guided Consolidation Select which systems to analyze
Consolidation phase converts physical machines to VMs Guided Consolidation, recommended for smaller IT environments, enables you to streamline your datacenter by moving business applications, spread across multiple disparate physical systems, into a centrally managed virtual environment. In the virtualized environment, the physical systems that run your business applications are transformed into virtual machines. Multiple virtual machines can be hosted on a single physical system, enabling more efficient use of computing resources. Consolidating your datacenter involves the following process: Discover – Physical systems in your datacenter are discovered and you select the systems you want analyzed. See Discovering Physical Systems. Analyze – Selected physical systems are analyzed and performance data on each selected system is collected. Generally, the longer the duration of the analysis phase the higher the confidence in the vCenter Server’s recommendations. See Viewing Analysis Results. Consolidate – Performance data is compared to the resources available on the virtual machine host systems. The selected physical systems are converted to virtual machines and imported into vCenter Server on the recommended hosts where they are managed along with other components of your virtual environment. See Consolidating Candidates. Use the consolidation feature to start building your virtual environment, or to further consolidate your datacenter as it grows. Analysis Limit Up to 100 systems can be simultaneously analyzed. If you select more than one hundred systems, systems will be added, in the order they appear, until the maximum number of systems is reached. Guided Consolidation Cache and VC performance Guided Consolidation caches information about discovered systems, and a very large cache can negatively impact vCenter Server performance. Do not run Guided Consolidation over more than 20,000 systems without clearing the cache. To disable Guided Consolidation and clear the cache Select Administration > VirtualCenter Management Server Configuration. Select Advanced Options. Click Add Row. Enter the following in the Key field: dontStartConsolidation Enter the following in the Value field: true Restart the vCenter Server. To disable Consolidation without clearing the cache, uninstall the collector service. There is no need to restart the vCenter Server. 2 Topic 4: Managing vCenter Server

26 vCenter Server 4.x Database Sizing
In vCenter 4.x go to the Administration Menu & choose vCenter Server Settings In vCenter Server 2.5 for ESX 3.5, go to the Administration Menu & choose VirtualCenter Management Server Configuration. You can change the numbers in the Physical Hosts and Virtual Machines dialog boxes to see changes in database size estimates. Use different numbers to produce estimates 4 Topic 5: Planning vCenter Server Deployment

27 VMware Tools Configurable Features
Time Synchronization Tools on the taskbar Upgrade Availability Connected Devices Preconfigured Scripts Shrink is not available on VMs with Normal mode Note: Be careful in selecting the “Time synchronization between the virtual machine and the console operating system. If your ESX host does not have the correct time this could force the guest to have the incorrect time as well. This will cause Kerberos problems in Windows domains if time is skewed by more than 5 minutes difference from domain controllers. 3 Topic 1: Create a VM

28 Deploy VM from Template
6 Topic 2: Create Multiple VMs, Templates & Clones

29 Customization Specification Manager
Specifications can be created, saved, copied, imported, exported or edited In vCenter, Edit menu  Customization Specifications. 15 Topic 2: Create Multiple VMs, Templates & Clones

30 Import Virtual Appliances
Select host or cluster Import from VA marketplace, file, or URL Appliance is validated for ESX prior to import 11 Topic 3: Virtual Appliances

31 VMware vCenter Converter 4.3 Standalone
vCenter Converter Standalone can be installed on any computer Client / Server architecture allows client and server to be on different computers Sysprep folder must be accessible from Client running Converter Reconfigure installs hardware drivers for the VM but will break VMware tools already installed if source is an ESX VM Select provisioning and location of each disk individually Dropped in v4.3 29 Topic 4: VMware Converter (P2V – V2V)

32 Enterprise Converter 4.2.1 Usage
vCenter Server Plug-in enables Converter Enterprise Converter is an optional component during vCenter Server installation Nearly identical capabilities of Standalone Converter Version 4.3 6 Topic 4: VMware Converter (P2V – V2V)

33 VM Properties - Hardware tab
DEVICE Add Edit Remove Floppy OFF ON / OFF CD/DVD Network Adapter ON/OFF USB N/A SCSI Controller Hard Disk ON*/OFF Parallel Port Serial Port SCSI Device ON = VM Powered On OFF = VM Powered Off * = Cannot have snapshots Requires ver. 7 Hardware NEW to ESX and ESXi 4.1 Add Serial Ports Use the Add Hardware wizard to add a serial port to a virtual machine. You can configure a virtual serial port in several ways. Use physical serial port on the host - Uses an external modem or a hand-held device in your virtual machine. Output to file - Captures the data that a program running in the virtual machine sends to the virtual serial port. Connect to a named pipe - Enables two virtual machines or a virtual machine and a process on the host to communicate as if they were physical machines connected by a serial cable. For example, this can be used for remote debugging on a virtual machine. Connect via a remote network - Enables a serial connection to and from a virtual machine's serial port over the network. Virtual Serial Port Concentrator (vSPC) aggregates traffic from multiple serial ports onto one management console. It behaves similarly as physical serial port concentrators. Using a vSPC also allows network connections to a virtual machine's serial ports to migrate seamlessly when the virtual machine is migrated using vMotion. New in 4.1 Virtual Serial Port Concentrator – allows redirection of VMs’ serial ports over a standard network link using telnet or ssh, allows for vMotion Remainder Shown as Powered Off Shown as Powered On 11 Topic 5: Manage VMs

34 VM Properties - Options tab
From vApps: Ensuring seamless application movement and choice between clouds VMware vSphere includes support for vApp, a logical entity comprising one or more virtual machines, which uses the industry standard Open Virtualization Format to specify and encapsulate all components of a multi-tier application as well as the operational policies and service levels associated with it. Just like the UPC bar code contains all information about a product, the vApp gives application owners a standard way to describe operational policies for an application which the cloud OS can automatically interpret and execute. vApps can be comprised of any applications running on any OS, and provide a mechanism for customers to move their applications between internal clouds or external clouds with still the same service levels. From VMware help: Virtual Machine VMI Paravirtualization VMI is a paravirtualization standard that enables improved performance for virtual machines capable of utilizing it. This feature is available only for versions of the Linux guest operating system that support VMI paravirtualization. Note: Enabling paravirtualization utilizes one of the virtual machine’s PCI slots. Also, enabling paravirtualization can limit how and where the virtual machine can be migrated. Consider the following before enabling this feature: ■ These hosts support VMI paravirtualization: ESX/ESXi 3.5 and greater and Workstation 6.x and greater. You can migrate Hardware version 4 virtual machines with paravirtualization enabled from ESX/ESXi hosts to Workstation hosts without loss of functionality. ■ You can manually move a powered-off virtual machine with paravirtualization enabled to a host that does not support paravirtualization. However, this can result in reduced performance. ■ You cannot migrate a powered-on or suspended virtual machine with paravirtualization enabled to a host that does not support paravirtualization. ■ VMI paravirtualization does not support Fault Tolerance. ■ Automated vCenter Server DRS migrations of virtual machines with paravirtualization enabled to hosts that do not support paravirutualization are not allowed. Set N-Port ID Virtualization Options (NPIV) N-port ID virtualization (NPIV) provides the ability to share a single physical Fibre Channel HBA port among multiple virtual ports, each with unique identifiers. This allows control of virtual machine access to LUNs on a per-virtual machine basis. Each virtual port is identified by a pair of World Wide Names (WWNs): a World Wide Port Name (WWPN) and a World Wide Node Name (WWNN). These WWNs are assigned by vCenter Server. NPIV support is subject to the following limitations: ■ NPIV must be enabled on the SAN switch. Contact the switch vendor for information about enabling NPIV on their devices. ■ NPIV is supported only for virtual machines with RDM disks. Virtual machines with regular virtual disks continue to use the WWNs of the host’s physical HBAs. ■ The physical HBAs on the ESX/ESXi host must have access to a LUN using its WWNs in order for any virtual machines on that host to have access to that LUN using their NPIV WWNs. ■ The physical HBAs on the ESX/ESXi host must support NPIV. If the physical HBAs do not support NPIV, the virtual machines running on that host will fall back to using the WWNs of the host’s physical HBAs for LUN access. ■ Each virtual machine can have up to 16 virtual ports. NPIV-enabled virtual machines are assigned NPIV-related WWNs, which are used to communicate with physical HBAs through virtual ports. Therefore, virtual machines can utilize up to 4 physical HBAs for NPIV purposes. Specify Virtualized CPU and MMU Settings Current CPUs have hardware support for virtualization. ESX can automatically determine if a virtual machine should use hardware support for virtualization. However, overriding the automatic selection can provide better performance for some use cases. NPIV is supported only for VMs with RDM disks 14 Topic 5: Manage VMs

35 Extend partitions using gparted
To extend any partition on any version of Windows Extend drive .vmdk using CLI or using the VIC Mount the gparted.iso to CD/DVD-ROM of VM Boot to gparted and extend the drive Reboot Windows (works for Linux too, may need extra steps) Gnome Partition Editor The GParted application is the GNOME partition editor for creating, reorganizing, and deleting disk partitions. A disk device can be subdivided into one or more partitions. The GParted application enables you to change the partition organization on a disk device while preserving the contents of the partitions. With GParted you can accomplish the following tasks: Create a partition table on a disk device. Enable and disable partition flags such as boot and hidden. Perform actions with partitions such as: create or delete resize or move check label copy and paste GParted uses GNU libparted to detect and manipulate devices and partition tables. Several optional file system tools provide support for file systems not included in libparted. GParted is developed on GNU/Linux. It can be used on other operating systems, such as Windows, by booting from media containing GParted Live. Gparted is FREE, Open Source, 3rd party software and available as a LiveCD ISO 4 Topic 5: Manage VMs

36 Web Access Tasks When logged into vCenter, Datacenter and Alarm information is available 13 Topic 8: Web Access

37 Generate Virtual Machine Shortcut
Provides a way to access a VM through a URL Useful for including in an instant message or an message Similar to the MMC Taskpad The Remote Console provides a way to delegate access to a VM through a URL to a sub-administrator Useful for including in an instant message or an message Somewhat similar to the Taskpad MMC that can be create for a sub-administrator in a Windows Active Directory Domain 4 With both checkboxes, the view is limited to a single VM with no tab options With the second checkbox, only one VM will show with the tabs Without either check box, the link points to the top of Web Access With the top checkbox, all VMs show, but tabs for Alarms, Tasks, and Events are not shown Obfuscate will encrypt the link so that it’s options are not obvious Topic 8: Web Access

38 Resource Shares Dynamic resource management
Only used if there is resource contention Prevents a single VM from utilizing all the resources Prioritizes specific VM resource usage during contention 1000 Shares – 25% Number of Shares Equal (each has 25%) 2000 Shares – 22% 1000 Shares – 11% 4000 Shares – 45% Changing Share Values (% varies on # of shares) Starting a VM changes resource allocation 2000 Shares – 20% 1000 Shares – 10% 4000 Shares – 40% Turning off VM changes resource allocation 2000 Shares – 22% 1000 Shares – 11% 4000 Shares – 45% 1000 Shares Turned off 38 3 Topic 5: Resource Pools and Monitoring

39 Performance Monitoring - Overview
Can monitor a Datacenter, Cluster, Resource Pool, Host or VM Can view thumbnail charts of child objects Overview Performance Charts The VMware® Overview Performance Charts show the performance statistics that VMware considers most useful for monitoring performance and diagnosing problems. You can examine data about clusters, datacenters, datastores, hosts, resource pools, virtual machines, and vApps. To easily compare different metrics, you can view charts for an object side-by-side, for example, CPU usage and memory usage. This enables you to quickly troubleshoot performance issues, monitor usage trends, do capacity planning, and determine which resources to increase and decrease on your hosts and virtual machines. The help topic for each chart contains a description of the chart, the statistics displayed in the chart, and an analysis section for troubleshooting and resolving problems. To view the overview charts, the VMware vSphere Client must be connected to a vCenter Server. VM based Overview showing Storage with pie charts of Space by Datastore and Space by file type 4 Datacenter based Overview showing thumbnails of datastores Cluster based Overview showing thumbnails of hosts Cluster based Overview showing thumbnails of VMs Host based Overview showing all host resources Topic 2: VM Performance Monitoring

40 Customize Performance Chart
Use a Stacked Graph to drill down to find a problem Hover over a color bar to get detailed information 3 Topic 2: VM Performance Monitoring

41 Problem: High Memory Utilization
Memory problem indicators High Balloon driver usage High VMkernel swap file usage High Memory usage inside VM Solutions: Changes to the constrained VM Add shares, increase Memory reservation, change Memory limit Increase available memory vMotion this virtual machine (Host Memory) Changes to other VMs: Shut down, vMotion, or remove shares from other virtual machines Decrease available memory Changes to Resource Pool or Cluster Move VMs in or out of Pool Change shares , limit , reservation Initially started numerous VM’s which caused high ballooning in the VM’s. As Transparent Page Memory Sharing engaged the ballooning steadily went down until it got to 0 in ESX In the ESX 4.0 example shown, Consumed Memory was reduced instead of Balloon. As the machines idled after the initial boot, there was no demand for the additional memory so VMware 4.0 cleared the memory making it available for other processes rather than flush the Balloon or the Swap. In ESX 3.5, any sustained Balloon memory indicated a problem. However, in ESX 4.0, to determine if there is a memory over commit problem, in addition to looking at Balloon and Swap, you now have to look at Consumed Memory. VMware will maintain a 6% buffer of free memory to provide for rapid spikes in memory requirements. So if Consumed Memory is below 94% of total host memory and the Balloon and Swap are stable and not thrashing in size, then there is no immediate problem. Look at the total of Consumed, Balloon, and Swap compared to Total memory to determine if there is a potential future problem if demand were to suddenly spike on multiple VMs. Of course, all hosts must be considered when DRS is enabled as vCenter will be able to vMotion VMs to other hosts where possible to resolve individual host problems within the cluster. In task Manager inside the VM, it showed that there was only 11MB of free memory initially, then it stabilized at 175MB available Memory Usage inside VM In the chart to the right, High ballooning activity settled over time in ESX 3.x In ESX 4.x Balloon Memory is not automatically flushed as a first priority, Consumed Memory may be reduced instead. 1 Topic 2: Performance Monitoring

42 Veeam Monitor Demo 3 Topic 2: VM Performance Monitoring

43 Alarm Settings There are 10 Datastore specific event Triggers
Plus additional Event triggers for Datacenters, Networks, vNetwork Distributed Switches, Distributed Virtual Port Groups, and vCenter Server There are 9 Host state Triggers Over 100 Virtual Machine Event Triggers to choose from Once an alarm has been triggered, Now What? 10 Action choices for Virtual Machines Choose when and how often to act. Just the 3 basic Actions available for Cluster Alarms 9 Action choices for Hosts There are 27 Cluster specific event Triggers There are almost 100 Host Event Triggers Click in each column to change setting Values in Drop downs can be overwritten by typing 3 Datastore State Triggers Use these settings to avoid alarms repeating over short periods of time or small changes to trigger thresholds 10 Topic 3: Configuring Alarms

44 Storage Views - Reports
Reports may be exported by right clicking on the screen to these formats .xls, .htm, .html, CSS (.htm), .csv, .xml 6 Topic 1: Storage Views & Topology Maps

45 Cluster Map View: Host to Datastore
Cluster Map View: Host to Network and Datastore Cluster Map View Host Map View Cluster Map View: Host to Datastore Cluster Map View: VM to Datastore Cluster Map View: VM to Network Cluster Map View: Host to Network Cluster Map View: Host to VM 7 Topic 1: Storage Views & Topology Maps

46 Storage vMotion in vSphere 4
Built-in to the Migrate Wizard vMotion or Storage vMotion, not both at once Can cold migrate both at once Can reprovision (thin/thick) the disk while migrating (hot/cold) 2 When Advanced button clicked, choose datastore Topic 2: Storage vMotion

47 How vMotion Works VM1-1 VM1-1 ESXi Host 1 ESXi Host 2
Step One: 1 VM1-1 Users currently accessing VM1-1 on ESXi1 Initiate migration of VM1-1 from ESXi1 to ESXi2 while VM1-1 is up and running 4 ESXi Host 1 Step Two: Pre-copy memory from ESXi1 to ESXi2 Log ongoing memory changes Copy changed memory, Log new changes Repeat copying changed memory until remaining changes are small enough to copy during the quiesce 2 3 3 VM files 2 Memory VM Motion Network CorpNet Network Remaining Memory VM state – Registers, etc Quiesce virtual machine on ESXi1 Copy remaining memory to ESXi2 Copy VM State information (registers, etc) Step Three: Shared Storage 4 Step Four: Start VM1-1 on ESXi2 Users now access VM1-1 on ESXi2 ESXi Host 2 Step Five: Delete VM1-1 from ESXi1 after migration is successful 4 VM1-1 4 Topic 3: Configuring vMotion

48 Dynamic Balancing / History
Monitor VM, resource pool, and host statistics Balances and maintains resources for pools and VMs DRS Recommendations of which VMs to migrate 2 Topic 4: Distributed Resource Scheduler (DRS) Cluster

49 Virtual Machine to Host Rules
Use DRS Groups Manager to create groups of VMs and groups of Hosts Create a rule to match VM group with Host group 5

50 Expandable Reservations
Allow use of available parent resources when a Resource Pool’s Reservation for a resource has been reached Maximum of up to 8 levels of resource pools allowed Events that trigger Expandable Reservation use: Power on VM Create child resource pool Change resource pool reservation What is necessary to start VM67-1 below? 718 MB MB = 206 MB overhead 3 Topic 5: Resource Pools and Monitoring

51 Creating a Distributed Virtual Switch
Created in Inventory  Networking 3 objects created: dvSwitch, dvUplinks, dvPortGroup Creating a dvSwitch actaull creates three objects: dvSwitch – The virtual object that passes traffic through to VMs on a host or separate hosts or external network entities dvSwitch-DVUplinks – The object that conatins the list of dvUplinks. Each dvUplink can connect to a different vmnic on a different ESX/ESXi host dvPortGroup – The Portgroup that VMs use to perform network functions, just like that on a standard vSwitch Select which hosts are going to use this switch. Only unallocated NICs can be selected. A default Portgroup called dvPortGroup can be created. 5 Topic 6: vNetwork Distributed Switches

52 Edit dvSwitch Settings
A private VLAN is technique in computer networking where a VLAN contains switch ports that are restricted, such that they can only communicate with a given "uplink". The restricted ports are called "private ports". Each private VLAN typically contains many private ports, and a single uplink. The uplink will typically be a port (or link aggregation group) connected to a router, firewall, server, provider network, or similar central resource. The switch forwards all frames received on a private port out the uplink port, regardless of VLAN ID or destination MAC address. Frames received on an uplink port are forwarded in the normal way (i.e., to the port hosting the destination MAC address, or to all VLAN ports for unknown destinations or broadcast frames). "Peer-to-peer" traffic is blocked. A typical application for a private VLAN is a hotel where each room has a port for Internet access. Allowing direct data link layer communication between customer nodes would expose the local network to various security attacks, such as ARP spoofing, as well as increasing the potential for damage due to misconfiguration. Another application of private VLANs is to simplify IP address assignment. Ports can be isolated from each other at the data link layer (for security, performance, or other reasons), while belonging to the same IP subnet. Note that while private VLANs provide isolation at the data link layer, communication at higher layers may still be possible, through the uplink connection and any routers or firewalls that are configured there. A private VLAN is identified by its primary VLAN ID. A primary VLAN ID can have multiple secondary VLAN IDs associated with it. Primary VLANs are Promiscuous, so that ports on a private VLAN can communicate with ports configured as the primary VLAN. Ports on a secondary VLAN can be either Isolated, communicating only with promiscuous ports, or Community, communicating with both promiscuous ports and other ports on the same secondary VLAN. Portgroups defined on a dvSwitch that is configured for Private VLANs can be assigned to either the Primary VLAN or any of the Secondary VLANs. Physical NICs can only be changed on the configuration tab of the ESX host. 4 Topic 6: vNetwork Distributed Switches

53 Edit dvSwitch Uplink Policy Settings
Configure Advanced dvPort Group Properties Allow port policies to be overridden Select this option to allow dvPort group policies to be overridden on a per-port level. Click Edit Override Settings to select which policies can be overridden at the port level. Edit Override Settings Select which policies can be overridden at the port level. Live port moving allowed This setting allows ports to be moved while they are in use. Config reset at disconnect When a dvPort is disconnected from a virtual machine, the configuration of the dvPort is reset to the dvPort group setting. Any per-port overrides are discarded. Port name format A template for assigning dvPort names for this dvPort group. Security Policies can only be set at the Portgroup level The uplink ports always support trunking. VLAN tags are only placed on packets if VLAN are defined at the portgroup level. Filter what VLANs are allowed on this screen NIC Teaming can not be changed at the dvSwitch level Both outbound and inbound traffic shaping can be set at either the dvSwitch level or the portgroup level 8 Topic 6: vNetwork Distributed Switches

54 Edit dvSwitch Port Group Settings
Port binding: Choose when ports are assigned to virtual machines connected to this dvPort group. Select Static binding to assign a port to a virtual machine when the virtual machine is connected to the dvPort group. Select Dynamic binding to assign a port to a virtual machine the first time the virtual machine powers on after it is connected to the dvPort group. Select Ephemeral for no port binding. VLAN Type: Select the type of VLAN for the Port Group. Select VLAN Trunking to send VLAN tags to the Virtual Machines on this Port Group. Configure which VLANs are to be available to this Port Group. Select Private VLAN to configure which Private VLAN should be set for this Port Group. Port binding defines when port numbers are assigned to a VM for use by Teaming policies Same options as Standard vSwitches 7 Topic 6: vNetwork Distributed Switches

55 Private VLANs Promiscuous – Uplinks, DHCP, Common services
Can see and be seen by every VM on the Primary VLAN Created by default, only one required Community – Groups of VMs Can see other VMs in the same Community PVLAN and VMs/ports in the Promiscuous PVLAN Create as many as needed Isolated – Individual VMs Can only see VMs/ports in the Promiscuous PVLAN Cannot see other VMs, even in the same Isolated PVLAN Only one required, will need to be created Private VLANs are useful for isolating machines in the DMZ such that each machine cannot communicate with other machines in the DMZ. If one machine is compromised, that machine can not be used to compromise other machines in the DMZ even though they are on the same subnet. Where machines are required to communicate, they can be put into a Community rather than in the Isolated Secondary. The classic example of PVLANs is a hotel. Individual rooms are placed in the Isolated Secondary Private VLAN so that guests cannot hack each other, but still have internet access. A Community Secondary PVLAN is created for each Conference room so that guests in the room can communicate and get to the internet, but cannot see guests in the guest rooms or other conference rooms. Uplink ports are almost always in the Promiscuous Secondary PVLAN so that users can have access to other subnets and the Internet. In addition, common services such as DHCP or DNS can be placed in the Promisuous so that all users have access to those services. Set PVLAN on the dvPortGroup Create PVLANs at the dvSwitch 1

56 Migrating Service Console Port or VMkernel Port to vDS
Service Console ports and VMkernel Ports from a Standard virtual switch may be easily migrated to a vNetwork Distributed switch using the same wizard that can create them on the dvSwitch. New Virtual Adapter allows the creation of a new Service Console Port or VMkernel Port on the vDS. What follows is the process of migrating an existing Service Console Port to a vDS Creating a new Service Console Port or VMkernel Port on the vDS is just as easy. Migrating an existing VMkernel Port to the vDS is the same process just performed 6 Topic 6: vNetwork Distributed Switches

57 Network I/O Control (NIOC)
New in 4.1 QoS policies based on Network Traffic Flow Types Defined on only on a vDS, only available in Enterprise Plus Edition Based on Limits (absolute max across team) and Shares (relative value of outbound traffic on vmnic) Network Resource Pools define controllable traffic types ESX hosts deployed with 10GigE NICs are likely to be deployed (for the time being) with only two 10GigE interfaces. Multiple traffic types will be converged over the two interfaces. So long as the load offered to the 10GE interfaces is less than 10GE, everything is ok—the NIC can service the offered load. But what happens when the offered load from the various traffic types exceeds the capacity of the interface? What happens when you offer say 11Gbps to a 10GigE interface? Something has to suffer. This is where Network IO Control steps in. It addresses the issue of oversubscription by allowing you to set the relative importance of predetermined traffic types. Network IO Control isolates the traffic types and ensures one traffic type is not dominated by others. It ensures or guarantees a minimum level of service for each traffic type when those traffic types (or flows) compete for a vmnic (physical NIC) Note that NetIOC is available only with the vDS. It is not available on the standard switch (vSS). NetIOC is controlled with two parameters—Limits and Shares. Limits, as the name suggests, sets a limit for that traffic type (e.g VM traffic) across the NIC team. The value is specified in absolute terms in Mbps. When set, that traffic type will not exceed that limit *outbound* (or egress) of the host Shares specify the relative importance of that traffic type when those traffic types compete for a particular vmnic (physical NIC). Shares are specified in abstract units numbered between 1 and 100 and indicate the relative importance of that traffic type. For example, if iSCSI has a shares value of 50, and FT logging has a shares value of 100, then FT traffic will get 2x the bandwidth of iSCSI when they compete. If they were both set at 50, or both set at 100, then they would both get the same level of service (bandwidth). There are a number of preset values for shares ranging from low to high. You can also set custom values. Note that the limits and shares apply to output or egress from the ESX host, not input. Remember that shares apply to the vmnics; limits apply across a team. Select the networking inventory panels; click on the vDS switch and then select the “Resource Allocation” tab. Here you will see the various traffic types supported or identified. NetIOC currently categorizes the traffic types as follows: - FT - iSCSI - vMotion - Management - NFS - VM traffic For each traffic type you can specify a limit in Mbps and a share value. Right clicking on the traffic type brings up the configuration panel. iSCSI Traffic Resource Pool applies to only Software based iSCSI traffic Types of Network Traffic Resource Pools 6 Topic 6: vNetwork Distributed Switches

58 Create Host Profile Host Profiles Screen or Hosts and Cluster Screen 4
Topic 7: Host Profiles

59 Edit Host Profile Hosts attached to the profile are checked for compliance to the Configuration settings by default. Each configuration option can be set as fixed or to prompt the user for specific settings when the profile is applied such as hostname. 1 Topic 7: Host Profiles

60 Create a Linked Mode Group
During the vCenter Install Process A Linked Mode group allows you to log in to any single instance of vCenter Server and view and manage the inventories of all the vCenter Server systems in the group. You can join multiple vCenter Server systems to form a Linked Mode group. You can configure a Linked Mode group during vCenter Server installation or after vCenter Server is installed. To join a vCenter Server group, you enter the fully qualified domain name (or IP address) of a remote machine on which vCenter Server 4.0 is running. The remote machine can be any vCenter Server 4.0 instance that is or will become a member of the Linked Mode group. You must also provide the Lightweight Directory Access Protocol (LDAP) port number of the remote vCenter Server instance. vCenter Server instances in a group replicate shared global data to the LDAP directory. The global data includes the following information for each vCenter Server instance: Connection information (IP and ports) Certificates Licensing information User roles After Install use the programs menu 5 Topic 8: Linked Mode Group of vCenter Servers

61 vSphere Host Update Utility: ESXi Patching
Used to patch ESXi 3 or ESXi 4 or ESXi 4.1 Cannot be used to patch ESX 3.x or ESX 4 Select the patches to install and Click the Install button 8 Topic 1: Patching ESX/ESXi Standalone Hosts

62 Update Manager Baselines
Created for VM, Virtual Appliance, and Host patches Choose which patches to apply Patches are selected from the Patch Repository Patch metadata must be downloaded prior to creating a baseline 7 Topic 2: Patching with Update Manager

63 Update Manager Tab Attach a baseline to scan, stage or remediate (patch) host or VM Scans, staging or patching can be run immediately or can be scheduled 2 Topic 2: Patching with Update Manager

64 Update Manager Remediation Defaults and Configuration Options
Guest Settings - Snapshot a VM prior to installing a patch, can auto delete the snapshot Host/Cluster Settings - Maintenance mode failure options Port Settings configuration 4 Topic 2: Patching with Update Manager

65 Update Manager Downloads
Schedule the download of patches Repository Location Set during Install C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Data (Default) Configured After Install Modify <patchStore> tag in C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml file 2 Topic 2: Patching with Update Manager

66 Remediation ESX/ESXi Hosts use the Hosts and Clusters View
VMs use the VMs and Templates View New cluster Remediation options in vSphere 4.1 allow disabling of services during remediation of a host such as disabling HA admission control so that more VMs can be loaded onto each host while the target host is in maintenance mode. FT can be disabled during remediation in order to all the FT software level to be upgraded on all hosts before enabling it again. Now Remediate a Host 8 Topic 2: Patching with Update Manager

67 ESX/ESXi Upgrade using Update Manager
Upload the upgrade files Use Host Upgrade option in New Baseline Wizard Attach Baseline and Remediate as usual Can be used to upgrade 3.x to 4.x or 4.0 to 4.1 Upgrade files only need to be uploaded one time per version 8 Topic 3: Upgrades and Migrations

68 vSphere Host Update Utility: ESX/ESXi Upgrade
Used to upgrade ESX/ESXi 3.x to 4.0 or patch ESXi Discontinued with vSphere 4.1 Upgrade host when vCenter Update Manager fails Can upgrade either standalone or vCenter managed hosts Can not customize partition table of the COS with this utility 12 Topic 3: Upgrades and Migrations

69 VMware HA in Action VC Server ESXi Host HA HA ESXi Host ESXi Host HA 2
Virtual Machine A Virtual Machine B HA ESXi Host VC Server Virtual Machine B Virtual Machine C Virtual Machine D HA ESXi Host Virtual Machine A Virtual Machine E Virtual Machine F ESXi Host HA 69 2 Topic 2: High Availability (HA)

70 Host Isolation Network problems can create host isolation conditions
Two Isolation Response Choices Power Off VMs so new host(s) can power them on or Leave VMs Powered (locked) Virtual Machine A Virtual Machine B Failure Detection and Host Network Isolation Agents communicate with each other and monitor the liveness of the hosts in the cluster. This is done through the exchange of heartbeats, by default, every second. If a 15-second period elapses without the receipt of heartbeats from a host, and the host cannot be pinged, it is declared as failed. In the event of a host failure, the virtual machines running on that host are failed over, that is, restarted on the alternate hosts with the most available unreserved capacity (CPU and memory.) NOTE In the event of a host failure, VMware HA does not fail over any virtual machines to a host that is in maintenance mode, because such a host is not considered when VMware HA computes the current failover level. When a host exits maintenance mode, the VMware HA service is reenabled on that host, so it becomes available for failover again. Host network isolation occurs when a host is still running, but it can no longer communicate with other hosts in the cluster. With default settings, if a host stops receiving heartbeats from all other hosts in the cluster for more than 12 seconds, it attempts to ping its isolation addresses. If this also fails, the host declares itself as isolated from the network. When the isolated host's network connection is not restored for 15 seconds or longer, the other hosts in the cluster treat it as failed and attempt to fail over its virtual machines. However, when an isolated host retains access to the shared storage it also retains the disk lock on virtual machine files. To avoid potential data corruption, VMFS disk locking prevents simultaneous write operations to the virtual machine disk files and attempts to fail over the isolated host's virtual machines fail. By default, the isolated host leaves its virtual machines powered on, but you can change the host isolation response to Shut Down VM or Power Off VM. NOTE If you ensure that your network infrastructure is sufficiently redundant and that at least one network path is available at all times, host network isolation should be a rare occurrence. With vCenter 2.5 Update 3 VMware added extra HA advanced configuration options, this is the complete list: das.failuredetectiontime - Amount of milliseconds, timeout time for isolation response action(with a default of milliseconds). das.isolationaddress[x] - IP address the ESX hosts uses for it’s heartbeat, where [x] = 1‐10. It will use the default gateway by default. das.usedefaultisolationaddress - Value can be true or false and needs to be set in case the default gateway, which is the default isolation address shouldn’t be used for this purpose. das.poweroffonisolation - Values are False or True, this is for setting the isolation response. Default a VM will be powered off. das.vmMemoryMinMB - Higher values will reserve more space for failovers. das.vmCpuMinMHz - Higher values will reserve more space for failovers. das.defaultfailoverhost - Value is a hostname, this host will be the primary failover host. das.failuredetectioninterval - Changes the heartbeat interval among HA hosts. By default, this occurs every second (1000 milliseconds). das.allowvMotionNetworks - Allows a NIC that is used for vMotion networks to be considered for VMware HA usage. This permits a host to have only one NIC configured for management and vMotion combined. das.allowNetwork[x] - Enables the use of port group names to control the networks used for VMware HA, where [x] = 0 - ?. You can set the value to be ʺService Console 2ʺ or ʺManagement Networkʺ to use (only) the networks associated with those port group names in the networking configuration. das.isolationShutdownTimeout - Shutdown time out for the isolation response “Shutdown VM”, default is 300 seconds. In other words, if a VM isn’t shutdown clean when isolation response occurred it’s being powered off after 300 seconds. das.bypassNetCompatCheck - Disable the “compatible network” check for HA that was introduced with Update 2. Default value is “false”, setting it to “true” disables the check. Virtual Machine Monitoring HA advanced options das.failureInterval = The polling interval for failures. Default value is 30. das.maxFailureWindows = Minimum amount of seconds between failure. Default value is 3600 seconds, if VM fails within 3600 seconds VM HA doesn’t restart the machine. das.maxFailures = Maximum amount of VM failures, if the amount is reached VM HA doesn’t restart the machine automatically. Default value is 3. das.minUptime = The minimum uptime in seconds before VM HA starts polling. The default value is 120 seconds. Yb-jw HA ESXi Host Virtual Machine B Virtual Machine C Virtual Machine D Switch HA ESXi Host Virtual Machine A Virtual Machine E Virtual Machine F ESXi Host HA 70 VMware HA waits 15 seconds before determining host isolation This interval is configurable in Advanced Options under HA Settings (das.failuredetectiontime = # of milliseconds, is the default) 3 Topic 2: High Availability (HA)

71 HA VM Monitoring Will restart a VM if the VMware Tools Heartbeat is not seen for a specified period of time. 3 Topic 2: High Availability (HA)

72 Configure Network Settings
Login to Console or Web Interface to change root password Default password: Configure IP Settings 1 Topic 7: VMware Date Recovery

73 Configure Data Recovery Appliance and Setup Backup Job
Login and Run the Getting Started Wizard Backups will occur once per day during the Backup Window 8 Topic 7: VMware Date Recovery

74 vRanger Pro - Screenshots
New Features Supported in 4.5 Active Block Mapping (ABM) - This patent-pending feature eliminates inactive blocks from protected data to speed full, incremental and differential backups. With ABM, backup jobs can complete faster than ever before possible. Only active blocks are read, transmitted and stored. Inactive blocks, including files deleted from the Windows recycle bin, are not read into the backup image. KEY BENEFITS: For the first time, empty blocks are eliminated from backup reads to dramatically speed full backups. Used in combination with CBT, ABM speeds incremental and differential backups still more. Change Block Tracking (CBT) - This feature queries the vStorage API to retrieve changed blocks rather than scanning the image to find them. CBT dramatically speeds incremental and differential backups. Object-Level Recovery (OLR) for Microsoft Exchange - This capability uses proven technology from Quest Recovery Manager for Exchange (RME) to enable fast restore of individual objects from the vRanger Pro image archive. Recover the Exchange database and then select individual messages, folders, and other objects for quick, simple recovery. Note that a valid license of RME is also required. Avoid the long process of having the restore an entire VM to retrieve a single . VSS Driver - This new feature provides a runtime process for guests with database applications, to ensure backup data integrity and log file truncation. This feature, introduced with vRanger 4.5 is also supported with Ensure the integrity of your application backups. Ensure the manageability of your application log files. Custom Backup Groups - Create backup jobs that combine more than one VM from the same ESX Server, from across ESX Servers, and from different vCenter deployments. Create a backup job for a vCenter folder, to dynamically include the current list of VMs in the folder as they change without having to reconfigure the backup job. Cut down on job scheduling time and administrative overhead. Adhere to backup policies more consistently. 1 Topic 8: Third Party Backups

Download ppt "Demo: Installation of ESXi 4.1 U1"

Similar presentations

Ads by Google