Objective 7 – Troubleshoot a vSphere Deployment

My apologies right out of the gate if you end up landing on this page. I ran out of time while studying and had to abandon this project. I would love to see it through to the end, so if you’d like to contribute of have me linkback to your page, please reach out, I’d love to hear from you.

Objective 7.1: Troubleshoot vCenter Server, ESXi Hosts, and Virtual Machines

Knowledge

  • Monitor status of the vCenter Server service
    • administration->System config->Services
  • Perform basic maintenance of a vCenter Server database
  • Monitor status of ESXi management agents
  • Determine ESXi Host stability issues and gather diagnostics information
  • Monitor ESXi system health
  • Locate and analyze vCenter Server and ESXi logs
  • Determine the appropriate Command Line Interface (CLI) command for a given troubleshooting task
  • Troubleshoot common issues, including:
    • vCenter Server service
    • SSO
    • vCenter Server connectivity
    • Virtual machine resource contention, configuration and operation
    • Platform Services Controller (PSC)
    • Problems with installation
    • VMware Tools installation
    • Fault Tolerant network latency

 Objective 7.2: Troubleshoot vSphere Storage and Network Issues

  • Identify and isolate network and storage resource contention and latency issues
  • Monitor networking and storage resources using vCOPs alerts and all badges
  • Verify network and storage configuration
  • Verify a given virtual machine is configured with the correct network resources
  • Monitor/Troubleshoot Storage Distributed Resource Scheduler (SDRS) issues
    • To diagnose problems with Storage DRS, you can clear Storage DRS statistics before you manually run Storage DRS.
    • IMPORTANT When you enable the option to clear Storage DRS statistics, statistics are cleared every time Storage DRS runs until you disable the option. Always disable the option after you diagnose the Storage DRS problem.
    • SDRS cluster-> manage->settings->Storage DRS ->advanced-> ClearIoStatsOnSdrsRun = 1
  • Recognize the impact of network and storage I/O control configurations
  • Recognize a connectivity issue caused by a VLAN/PVLAN
  • Troubleshoot common issues with:
    • Storage and network
    • Virtual switch and port group configuration
    • Physical network adapter configuration
    • VMFS metadata consistency

Objective 7.3: Troubleshoot vSphere Upgrades

  • Collect upgrade diagnostic information
  • Recognize common upgrade issues with vCenter Server and vCenter Server Appliance
  • Create/Locate/Analyze VMware log bundles
  • Determine alternative methods to upgrade ESXi Hosts in event of failure
  • Configure vCenter Server logging options

Objective 7.4: Troubleshoot and Monitor vSphere Performance

  • Monitor CPU and memory usage (including vRealize OM badges and alerts)
  • Identify and isolate CPU and memory contention issues
  • Recognize impact of using CPU/memory limits, reservations and shares
  • Describe and differentiate critical performance metrics
  • Describe and differentiate common metrics, including:
    • Memory
    • CPU
    • Network
    • Storage
  • Monitor performance through esxtop
  • Troubleshoot Enhanced vMotion Compatibility (EVC) issues
  • Troubleshoot virtual machine performance with vRealize Operations
  • Compare and contrast Overview and Advanced Charts

Objective 7.5: Troubleshoot HA and DRS Configurations and Fault Tolerance

  • Troubleshoot issues with:
    • DRS workload balancing
      • Review management guide page 117-end
    • HA failover/redundancy, capacity and network configuration
    • HA/DRS cluster configuration
    • vMotion/Storage vMotion configuration and/or migration
    • Fault Tolerance configuration and failover issues
      • The following guidelines allow you to configure your host’s networking to support Fault Tolerance with different combinations of traffic types (for example, NFS) and numbers of physical NICs.
        • Distribute each NIC team over two physical switches ensuring L2 domain continuity for each VLAN between the two physical switches.
        • Use deterministic teaming policies to ensure particular traffic types have an affinity to a particular NIC (active/standby) or set of NICs (for example, originating virtual port-id).
        • Where active/standby policies are used, pair traffic types to minimize impact in a failover situation where both traffic types will share a vmnic.
        • Where active/standby policies are used, configure all the active adapters for a particular traffic type (for example, FT Logging) to the same physical switch. This minimizes the number of network hops and lessens the possibility of oversubscribing the switch to switch links.
      • FT does not support:
        • Snapshots
        • Storage vmotion
        • Linked clones
        • vSAN or vVol
        • SBPM
        • VMCP
        • I/O filters
        • Physical RDM
        • Larger than 2TB vmdk
      • Requirements
        • EVC (sandy bridge or later) (amd bulldozer or later)
        • Dedicated 10Gb network for FT Logging
          • Multiple pNics are required
          • Vmotion and FT logging must be on different subnets
        • vSphere standard/enterprise (up to 2vCPU) or Enterprise Plus (up to 4vCPUs)
        • HA enabled cluster
        • Host must have hardware virtualization enabled in the bios.
        • Memory reservation of FT protected machine is set to the full configured memory size
  • Explain the DRS Resource Distribution Graph and Target/Current Host Load Deviation
  • Explain vMotion Resource Maps
    • Shows connection maps. Items that can’t be vmotioned are shown with a red x (?)
    • Only available within the C# client.

 

Advertisements