Hot! VMware Certified Professional 5 Tips – 4

Configure storage virtual appliance for vsphere

  • virtual appliance that packages suse linux and storage clustering services
  • a vsa runs on several exi hosts to abstract the storage resources that are installed on the host and to create a vsa cluster
  • provides a set of datastores that are accessible by all hosts within the data center
  • can have 2 or three vsa cluster members
  • status of the cluster is online when more than half of the members are online
  • Vsa enables these features
    • shared datastores for all hosts in the cluster
    • replica of each shared datastore
    • vmotion and ha
    • presents NFS volume
    • each node presents a file system via NFS that is mirrored to one other file system on another vsa
  • Installation
    • install VSA manager on existing vcenter server
  • 2 node vsa config uses a special vsa cluster service which runs on vcenter server, no storage associated with cluster service
  • vsa cluster network  must have at least 1 dedicated Ethernet switch that supports 802.1Q vlan trunking
  • Raid 10 is only supported raid config
  • total capacity of vsa cluster is sum of the capacities of all vsa datastores

 

  • Objective 3.3
    • create and configure vmfs and nfs datastores
      • identify vmfs, nfs datastore properties
        • both can boot vm
        • both can vmotion
        • NFS cannot have rdm
        • both have ha and drs
    • identify vmfs 5 capabilities
      • supports greater than 2TB storage devices for each vmfs extent
      • standard 1 MB file system block
      • support of greater than 2 TB disk size for rdm’s in physical compatibility mode
      • GPT format enables you to create datatstores up to 64 TB
      • max size of vmdk is still 2TB minus 512
      • max size of virtual rdm is still 2TB – 512 bytes
    • Right click datatstore to rename
    • Delete datastore
      • permanently deletes all file associated with vms on datastore
      • prereqs, remove all vms from datatstore, make sure no host is accessing datastore
    • Right click datastore to unmount and mount
    • When you unmount a datastore it remains intact, but can no longer be seen from the hosts that you specify
    • Extend/expand datastore
      • can add up to 32 extents of the same storage type to an existing vmfs datastore
      • grow an extent in an existing vmfs datastore
  • Upgrade vmfs 3 to vmfs 5
    • can be done with vm running on it
    • Verify volume to be upgraded has at least 2 MB of free space and 1 free file descriptor
    • click config tab, storage, select datastore, upgrade to vmfs5, perform rescan on all hosts

 

  • Place a vmfs datastore in maintenance mode
    • maintenance mode is available to datastores with in a storage drs enabled datastore cluster
    • can’t turn on for standalone datastores
    • virtual disks that are located on a datstore that is entering maintenance mode must be migrated to another datastore either manually or using storage drs
    • placement recommendations tab displays list of migration recommendations, faults tab lists virtual disks that can’t be migrated and why
    • datastore is in a state of entering maintenance mode until all virtual disks have been migrated
      • Prereqs
        • storage drs
        • no cd rom image files stored on datastore
        • at least 2 datastores in a cluster
      • right click datastore and select enter sdrs maintenance mode
  • Select preferred path for vmfs datastore
    • multiple 3rd party MPP’s can run in parallel with vmware NMP, when installed the 3rd party MPPs replace the behavior of the NMP and take complete control of the path failover and load balancing operations for specific devices
      • MRU: host selects path that is used more recently. When path becomes unavailable the host selects alternate path, host does not revert back to original path when it becomes available again
      • Fixed: uses designated preferred path, if it has been configured. Otherwise selects first working path discovered at boot time
    • Disable path
      • right click a path and disable
    • Determine use case for multiple VMFS/nfs datastores
    • By default host performer periodic path evaluation every 5 min, causing any unclaimed paths to be claimed by the appropriate MPP

 

  • Create and deploy vapps
    • applications can be packaged to run directly on top of vmware vsphere
    • format how the applications are packaged and managed is called vsphere app
    • a vapp is a container and can contain one or more vms
    • a vapp can power on/off be cloned
    • distribution format for vapp is ovf
    • to create
      • select file, new, vapp
    • configure resource allocation
      • cpu, shares, limit, reservation
      • memory, shares limit reservation
    • can allow for how IPS are allocated (fixed, transient, DHCP)
    • can control startup and shutdown of vms
    • clone vapp
      • can clone only when  turned off
    • export a vapp
      • file, export, ovf template
    • configure IP pools
      • go to datacenter, IP pools tab, add
  • Manage vm clones and templates
    • vm maximums, 32 vcpu, 1TB RAM, esxi host  max: 512 vms per host, 2048 vcpu per host, 2TB ram
  • Identify cloning and template options
    • clone is a copy of a vm, a template is a master copy of vm that can be used to create many clones
    • templates cannot be powered on or edited
    • when you clone a vm or deploy a vm from template, the resulting cloned vm is independent of the original vm and template
    • you must be connected to vcenter in order to clone a vm
    • clone to template
      • cloning a vm to a template creates a template copy of the vm while leaving the original vm in place
    • Convert to template
      • when you convert a vm to a template, you cannot edit or power on the template unless you convert it back to a vm

 

Bir Cevap Yazın