VMware Hands-on Labs - HOL-1811-02-SDC


Lab Overview - HOL-1811-02-SDC - Getting Started with vSphere with Operations Manager

Lab Guidance


Note: It will take more than 90 minutes to complete this lab. You should expect to only finish 2-3 of the modules during your time.  The modules are independent of each other so you can start at the beginning of any module and proceed from there. You can use the Table of Contents to access any module of your choosing.

The Table of Contents can be accessed in the upper right-hand corner of the Lab Manual.

This introductory lab will explore the components and their  capabilities within vSphere 6.5. It will cover how to implement these  in addition to basic administration topics. This lab also explores the  key features of vSphere 6.5 and how to operationalize them. You will  learn how to deploy and manage upgrades and migrations, enhance  availability, monitor and optimize workload performance, and learn how  proactive analysis of logs can detect problems before they affect your  workloads. This is an excellent place to begin your experience with VMware vSphere.

The lab is broken into 8 Modules which can be taken in any order:

Lab Module List:

 Lab Captains:

 

This lab manual can be downloaded from the Hands-on Labs Document site found here:

http://docs.hol.vmware.com 

This lab may be available in other languages.  To set your language preference and have a localized manual deployed with your lab, you may utilize this document to help guide you through the process:

http://docs.hol.vmware.com/announcements/nee-default-language.pdf


 

Location of the Main Console

 

  1. The area in the RED box contains the Main Console.  The Lab Manual is on the tab to the Right of the Main Console.
  2. A particular lab may have additional consoles found on separate tabs in the upper left. You will be directed to open another specific console if needed.
  3. Your lab starts with 90 minutes on the timer.  The lab can not be saved.  All your work must be done during the lab session.  But you can click the EXTEND to increase your time.  If you are at a VMware event, you can extend your lab time twice, for up to 30 minutes.  Each click gives you an additional 15 minutes.  Outside of VMware events, you can extend your lab time up to 9 hours and 30 minutes. Each click gives you an additional hour.

 

 

Alternate Methods of Keyboard Data Entry

During this module, you will input text into the Main Console. Besides directly typing it in, there are two very helpful methods of entering data which make it easier to enter complex data.

 

 

Click and Drag Lab Manual Content Into Console Active Window

You can also click and drag text and Command Line Interface (CLI) commands directly from the Lab Manual into the active window in the Main Console.  

 

 

Accessing the Online International Keyboard

 

You can also use the Online International Keyboard found in the Main Console.

  1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar.

 

 

Activation Prompt or Watermark

 

When you first start your lab, you may notice a watermark on the desktop indicating that Windows is not activated.  

One of the major benefits of virtualization is that virtual machines can be moved and run on any platform.  The Hands-on Labs utilizes this benefit and we are able to run the labs out of multiple datacenters.  However, these datacenters may not have identical processors, which triggers a Microsoft activation check through the Internet.

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoft licensing requirements.  The lab that you are using is a self-contained pod and does not have full access to the Internet, which is required for Windows to verify the activation.  Without full access to the Internet, this automated process fails and you see this watermark.

This cosmetic issue has no effect on your lab.  

 

 

Look at the lower right portion of the screen

 

Please check to see that your lab is finished all the startup routines and is ready for you to start. If you see anything other than "Ready", please wait a few minutes.  If after 5 minutes your lab has not changed to "Ready", please ask for assistance.

 

Module 1 - vCenter Server Appliance as a First Choice (60 minutes)

Introduction


This Module contains the following lessons:


vCenter Server Appliance Overview


With the release of vSphere 6.5, the vCenter Server Appliance (vCSA) has surpassed the feature set and performance of the Windows Installable vCenter server. Configuration maximums have been equal between the two since vSphere 6.0.  There are two components: vCenter and Platform Services Controller.  Depending on the size/deployment model, these can be embedded or external.  These concepts and the architecture will be covered later in this module.


 

Why VCSA 6.5 Should Be The Default Deployment Choice

For starters, the installer has gotten an overhaul with a new modern look and feel. Users of both Linux and Mac will also be ecstatic since the installer is now supported on those platforms along with Microsoft Windows. If that wasn’t enough, the vCenter Server Appliance now has features that are exclusive such as:

There are several other general improvements:

 

 

Security

Although the vCenter Server Appliance (vCSA) has previously been built on a customized 'VMware edition' of a SUSE Enterprise Linux appliance, the vCSA 6.5 runs PhotonOS. PhotonOS is a Linux OS that is purpose-built for virtualization by VMware. Therefore it comes pre-hardened and does not support the installation of third party software. The configuration disables unnecessary services, uses special host firewall and network interfaces, and removes local accounts except for the application's administration. VMware pre-hardens the vCenter Server Appliance using the applicable guidelines of the Unix SRG STIG. Customers do not install software within the VCSA except for updates obtained from VMware. There is no general-purpose interface to the Linux operating system. Even the SSH interface, reserved for administrators, is disabled by default.

 

 

Module Lessons

The remainder of this module focuses on lessons around these feature enhancements.

 

vSphere Update Manager Integration


vSphere Update Manager is now integrated with the vCenter Server Appliance (vCSA). When you deploy the vCenter Server Appliance (vCSA), the VMware vSphere Update Manager Extension service starts automatically. You can no longer connect a vSphere Update Manager instance that is installed on a Windows Server machine with the vCenter Server Appliance (vCSA). Attempts to connect vSphere Update Manager during installation on a Windows operating system to a vCenter Server Appliance (vCSA) fail with an error.

vSphere Update Manager deployed with the vCenter Server Appliance uses a PostgreSQL database. While vSphere Update Manager and the vCenter Server Appliance (vCSA) share the same PostgreSQL database instance, they use separate PostgreSQL databases which run on the vCenter Server Appliance (vCSA). In case you need to reset the vSphere Update Manager database, the vCenter Server Appliance (vCSA) database remains intact.

vSphere Update Manager enables centralized, automated patch and version management for VMware vSphere and offers support for VMware ESXi hosts, virtual machines, and virtual appliances (Upgrade and patch operations of virtual appliances will be deprecated in a future release).

With vSphere Update Manager, you can perform the following tasks:

  1. Upgrade and Patch ESXi hosts
  2. Install and update third-party software on hosts
  3. Upgrade virtual machine hardware, VMware Tools, and Virtual Appliances

vSphere Update Manager Web Client

  1. vSphere Update Manager Web Client for the vSphere Web Client - View scan results and compliance states for vSphere Inventory

It is also recommended to complete HOL-1811-03-SDC "vSphere with Operations Management: Advanced Topics" to gain in-depth knowledge about administering vSphere Update Manager. Module 5, in that lab, covers this topic in Lesson 1.


 

What's new in vSphere Update Manager 6.5

 

 

Update Manager Web Client

The client component of Update Manager is a plug-in to the vSphere Web Client. The Update Manager client component provides you with the full set of capabilities you need to perform patch and version management for your vSphere inventory.

The Update Manager plug-in for the vSphere Web Client requires no installation. After starting the Update Manager service in the vCenter Server Appliance (vCSA), the Update Manager client component is automatically enabled in the vSphere Web Client. An Update Manager icon appears on the Home screen, and the Update Manager appears amongst the top-level tabs in the vSphere Web Client.

You can access the Administration view of Update Manager from vSphere Web Client Home screen.
You can access the Compliance view of Update Manager by selecting an object from the vSphere inventory and navigating to the Update Manager tab.

 

 

Update Manager Download Service

vSphere Update Manager Download Service (UMDS) is an optional module of Update Manager that you can use to download patch definitions on a system that is separate from the Update Manager server. Use UMDS in case your Update Manager deployment system is secured and the machine on which the Update Manager server is installed has no access to the Internet.

You have two options for installation of UMDS. You can install UMDS on a 64-bit Windows operating systems. You must not install the UMDS on the same Windows machine where the Update Manager server is installed. 
You can also install the UMDS on a Linux-based system. In vSphere 6.5 release, an installer for UMDS 6.5 is delivered with the ISO file of the vCenter Server Appliance (vCSA). As a prerequisite to install the UMDS on Linux, you need a Linux server on which you must preconfigure the PostgreSQL database and a 64-bit DSN. Mount the ISO file of the vCenter Server Appliance (vCSA) to the Linux machine, and install and configure UMDS 6.5.

To use UMDS, the download service must be of a version that is compatible with the Update Manager server. For more information about the compatibility between Update Manager and the UMDS, see the Installing and Administering VMware vSphere Update Manager documentation.

 

 

 

Update Manager Utility

The Update Manager Utility allows you to change the database password and proxy authentication, re-register Update Manager with vCenter Server, and replace the SSL certificates for Update Manager. For more information about reconfiguring the Update Manager settings by using the utility, see the Reconfiguring VMware vSphere Update Manager documentation.

When you install Update Manager or UMDS, vSphere Update Manager Utility is silently installed on your system as an additional component.

 

 

Migration Options

VMware provides supported paths for migrating Update Manager from a Windows operating system to run in the vCenter Server Appliance (vCSA).

Update Manager can be migrated to vCenter Server Appliance (vCSA) in the following vCenter Server deployment models:

For detailed information how to perform migration, see the Installing and Administering VMware vSphere Update Manager  and the vSphere Upgrade documentation.

 

vCenter Server Availability


VMware vCenter® Server Appliance™ (vCSA) sits at the heart of vSphere and provides services to manage various components of a virtual infrastructure like ESXi hosts, virtual machines, and storage and networking resources. As large virtual infrastructures are built using vSphere, vCenter Server becomes an important element in ensuring the business continuity of an organization. vCenter Server must protect itself from a set of hardware and software failures in an environment and must recover transparently from such failures. vSphere 6.5 provides a brand new high availability solution for vCenter Server, known as vCenter Server High Availability, or VCHA. VCHA is only available for the vCenter Server Appliance.

vCenter Server High Availability protects vCenter Server Appliance against host and hardware failures. The active-passive architecture of the solution can also help you reduce downtime significantly when you patch the vCenter Server Appliance.

vCenter High Availability is a three-node cluster that contains an Active, Passive, and Witness nodes. Two different configuration paths are available called Basic and Advanced. What you select depends on your existing configuration but both Basic and Advanced result in exact same capabilities. In other words, use Basic whenever possible. If the vCenter Server being enabled for vCenter HA is being managed by a different vCenter Server in a separate SSO Domain or the Active, Passive, and Witness nodes are going to be managed by different vCenter Servers, the Advanced workflow will be required.


 

Architecture Overview

 

A vCenter HA cluster consists of three vCenter Server Appliance instances. The first instance, initially used as the Active node, is cloned twice to a Passive node and to a Witness node. Together, the three nodes provide an active-passive failover solution.

Deploying each of the nodes on a different ESXi instance protects against hardware failure. Adding the three ESXi hosts to a DRS cluster can further protect your environment. If using the Basic workflow to enable vCenter HA, then the workflow will automatically place the nodes on different hosts and create anti-affinity rules for you if DRS is enabled. If the Advanced workflow is being used then node placement is manual as is the creation of any DRS rules.

When the vCenter HA configuration is complete, only the Active node has an active management interface (public IP). The three nodes communicate over a private network called vCenter HA network that is set up as part of configuration. The Active node and the Passive node are continuously replicating data.

 

 

Roles for each type of node in a vCenter HA cluster

Active Node:

Passive Node:

Witness Node:

 

 

How does vCenter Server High Availability work?

Availability of the vCenter Server Appliance works as follows under the following failure conditions:

  1. Active node fails: As long as the Passive node and the Witness node can communicate with each other, the Passive node will promote itself to Active and start serving client requests.
  2. Passive node fails: As long as the Active node and the Witness node can communicate with each other, the Active node will  continue to operate as Active and continue to serve client requests.
  3. Witness node fails: As long as the Active node and the Passive node can communicate with each other, the Active node will continue to operate as Active and continue to serve client requests. The Passive node will continue to watch the Active node for failover.
  4. More than one node fails or is isolated: This means all three nodes - Active, Passive, and Witness - cannot communicate with each other. This is more than a single point of failure and when this happens, the cluster is assumed non-functional and the vCenter Server application shuts down to protect itself from data corruption.
  5. Isolated node behavior: When a single node gets isolated from the cluster, it is automatically taken out of the cluster and all services are stopped. For example, if an Active node is isolated, all services are stopped to ensure that the Passive node can take over as long as it is connected to the Witness node. Isolated node detection takes into consideration intermittent network glitches and resolves to an isolated state only after all retry attempts have been exhausted.

Note that the RTO for a failover is approximately 5 minutes.

 

Platform Services Controller Topologies & Platform Services Controller High Availability


The Platform Services Controller provides a set of common infrastructure services to the vSphere environment. The services include licensing, certificate management, and authentication with vCenter Single Sign-On.  In this module we will cover each of these topologies and the High Availability options for the Platform Services Controller.


 

vCenter Server and Platform Services Controller Deployment Types

As mentioned, you can deploy vCenter Server as an Appliance or install vCenter Server for Windows.  With Windows, you can also install/configure with an embedded or external Platform Services Controller. Like vCenter, the Platform Services Controller can be installed as an appliance or installed on Windows.

Before you deploy the vCenter Server Appliance or install vCenter Server for Windows, you must determine the deployment model that is suitable for your environment. The different types of deployment models are discussed in detail in the following lessons.

 

 

Platform Services Controller High Availability with vCSA - Walkthrough

This walkthrough demonstrates how to install and configure highly available Platform Services Controllers using the VMware vCenter Server Appliance. Use the arrow keys to navigate through the screens.  Please take note that this is based on vSphere 6.0 which may differ slightly from the 6.5 process.  Once completed, remember to close the browser tab this was open in. For detail about the process for 6.5, you may also refer to this KB article which includes a walkthrough.

https://featurewalkthrough.vmware.com/#!/vsphere-6-0/vcenter-server-install/vcenter-server-6-0-psc-ha-vcsa

 

vCenter Server Appliance (vCSA) Backup


In vSphere 6.5, the vCenter Server Appliance (vCSA) has an out-of-the-box file-based backup and restore solution. You can back up to a single folder all of vCenter Server’s core configuration, inventory, and historical data. All of this data is streamed over FTP (or SFTP / FTPS) or HTTP / HTTPS. When it is time to restore to a previous backup, you can deploy a fresh appliance, point to the folder location of the vCenter Server backup files, and restore all of vCenter Server's configuration and inventory data (with optional historical data) from the backup.

In this lesson we will go through the steps to create a backup of the vCenter Server Appliance (vCSA) and then verify the back up.  The restore process will be described and shown in the following lesson Hands-on Labs Interactive Simulation: vCenter Appliance Restore in the next lesson.


 

Open Chrome Browser from Windows Quick Launch Task Bar

 

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Log in to Appliance Management UI

 

You will back up your vCenter Server Appliance (vCSA) configuration files, inventory, and selected historical data to a folder of files placed on an FTP server.



Log in to the Appliance Management UI to monitor the vCenter Server Appliance (vCSA) and begin the vCenter Server backup process.

  1. Click the HOL Admin bookmark.
  2. Click the vcsa-01a Mgmt shortcut in the drop-down.
  3. Type root for the username.
  4. Type VMware1! for the password.
  5. Click the Login button.

 

 

Back up the vCenter Server Appliance (vCSA) using the Backup Appliance Wizard

 

Backing up the vCenter Server Appliance (vCSA) starts on the summary page of the Appliance Management UI (port 5480 of your vSphere web client IP / hostname).


To begin the process of backing up the appliance:

  1. Click the Backup icon in the upper right corner of the Appliance Management UI.

 

 

Verify the backup was successful

 

Once the backup is complete, we need confirm the backup was successful.

  1. Overwrite the address box with ftp://192.168.110.60.
  2. An Authentication Required window will be displayed.  Type root in the User Name field.
  3. Type VMware1! in the Password field.
  4. Click the Log In button.

 

Hands-on Labs Interactive Simulation: vCenter Server Appliance Restore


The vCenter Server Appliance Restore process consists of two stages:

This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.

This simulation will go through each stage to restore a vCenter Server Appliance.

  1. Click here to open the interactive simulation.  It will open in a new browser window or tab.
  2. When finished, click the "Return to the lab" link or close the windows to continue with this lab.

Migration Assistant


VMware provides supported paths for migrating and upgrading from vCenter Server version 5.5 and version 6.0 installations on Windows to the vCenter Server 6.5 Appliance. This section will provide a brief overview of these migration paths and the Migration Assistant for vSphere 6.5


 

Supported vSphere Migration Paths

 

You can migrate the following deployments as described in the following table.

 

 

Overview of Migration from vCenter Server on Windows to an Appliance

 

The Migration Assistant contains the following characteristics:

 

 

Migration Workflow

 

The workflow shown here describes the high level tasks for vCenter Server on Windows Migration to a vCenter Server Appliance on Linux.

Note: For a deeper understanding of the Migration Assistant, make sure to complete HOL-1811-02-SDC Module 7 - vCenter Server Appliance Migration as it demonstrates use cases for the Migration Assistant.

 

Conclusion


The vCenter Server Appliance is the new standard when it comes vCenter. It has surpassed the Windows based vCenter in functionality and matches it in scalability. This module introduced to many of the new features that are part of the vCenter Server Appliance, discussed architectural considerations, and described migrations paths to assist with moving to the Appliance.


 

You've finished Module 1

Congratulations on completing Module 1.

If you are looking for additional information on vCenter Server Appliance, try one of these:

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

If this is the last module you would like to take in this lab, you may end your lab by clicking on the END button.    

 

Module 2 - Next Generation Management Clients (45 Minutes)

Introduction


This Module contains the following lessons:


VMware Host Client Overview


The VMware Host Client is an HTML5-based client that is used to connect to and manage single ESXi hosts.

You can use the VMware Host Client to perform administrative and basic troubleshooting tasks, as well as advanced administrative tasks on your target ESXi host. You can also use the VMware Host Client to conduct emergency management when vCenter Server is not available.

It is important to know that the VMware Host Client is different from the vSphere Web Client, regardless of their similar user interfaces. You use the vSphere Web Client to connect to vCenter Server and manage multiple ESXi hosts, whereas you use the VMware Host Client to manage a single ESXi host.

VMware Host Client functions include, but are not limited to the following operations:

NOTE: The VMware Host Client only works for administrative users.


 

VMware Host Client Requirements

 

Make sure that your browser supports the VMware Host Client.

The following Guest Operating systems and Web Browser versions are supported for the VMware Host Client.

Supported Guest Operating Systems and Browser Versions for the VMware Host Client are shown here in the above table.

 

 

Using the VMware Host Client

The embedded VMware Host Client is an HTML5-based client that has a similar interface to the vSphere Web Client but is only used to manage single ESXi hosts. You use the VMware Host Client to conduct emergency management when vCenter Server is temporarily unavailable.

 

vSphere HTML5 Client and Web Client Enhancements


New Web Client UI features like Custom Attributes, Object Tabs, and Live Refresh are presented alongside other performance and usability improvements.

In the following steps lets explore the vSphere Web Client's latest features as part of this overview.

 


 

HTML5-based vSphere Client

The HTML5-based vSphere Client (or just vSphere Client) is now the preferred method for managing your vSphere infrastructure. For the time being, there are some tasks which still require the Web Client, which has also been improved in 6.5.

There are currently two versions of the new HTML5-based vSphere Client (or just vSphere Client) – an unsupported Fling version that receives regular (sometimes weekly) updates with new features and bug fixes. There is also a GA (generally available) fully supported version that is bundled with vCenter Server 6.5 and later. As we add new features and functionality to the vSphere Client, they will be added first to the Fling version and once mature will be moved to the GA version of vCenter Server through patches and updates. For example, the original release of vCenter Server 6.5 (November 15, 2016) contained a version of the vSphere Client that was roughly v2.7 of the vSphere Client Fling. When VMware released vCenter Server 6.5.0b (March 14, 2017) the vSphere Client was updated to be roughly equivalent to version 3.2 of the Fling but in a fully supported package. More information about this particular update can be found here: https://blogs.vmware.com/vsphere/2017/03/first-vsphere-client-html5-update-vsphere-6-5-b.html.

VMware will continue to release updates to the vSphere Client Fling on a frequent basis and then bring those features into the GA product through patches and updates until the vSphere Client is complete. The vSphere Client is a top priority for VMware and feedback remains to be very important. Please consider using the built-in feedback tool within both the Fling and GA versions of the vSphere Client to help us prioritize features and deliver a cross-platform client that enables a smooth, performant, and enjoyable vSphere administration experience.

 

Some of the key features of the vSphere Client are:

Functionality Updates for the vSphere Client

http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-client-65-html5-functionality-support.html

 

 

 

 

vSphere Web Client

As mentioned before, while the vSphere Client is the preferred tool to manage vSphere, there are some tasks that will still require you to use the vSphere Web Client. The rest of this lesson walks you through the Web Client to make sure you are familiar with it.

 

 

Open Chrome Browser from Windows Quick Launch Task Bar

 

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Navigation and shortcuts

 

  1. Open the vSphere Web Client for the RegionB vCenter using your Google Chrome web browser
  2. User name: administrator@vsphere.local
  3. Password: VMware1!
  4. Click Login

Note: The Inventory Tree will be the default view.

 

 

Custom Attributes

 

 The following steps will cover creating, renaming and deleting Custom Attributes.

  1. Select "vcsa-01b.corp.local"
  2. Click Home button
  3. Select Tags & Custom Attributes

 

 

Live Refresh

 

Live refresh improves the original mechanism for refreshing recent tasks, triggered alarms and the trees to now happen in real time. All users logged into vSphere Web Client will see the real time updates as long as they have permission to see the changes.

 

 

 

Conclusion

This concludes the section "vSphere HTML5 Client and Web Client Enhancements".  You should now have a solid understanding of the enhancements made to the vSphere Web Client and the difference between the various clients.

 

Conclusion


This module introduced you to the tools you will be using to manage your ESXi hosts and your virtual infrastructure. As you complete other Modules in this lab, you will be using the vSphere Client, they preferred client moving forward, except where one of the other clients is required.


 

You've finished Module 2

Congratulations on completing  Module 2.

If you are looking for additional information on Management Clients, try one of these:

Proceed to any module below which interests you most. 

 

 

 

How to End Lab

 

If this is the last module you would like to take in this lab, you may end your lab by clicking on the END button.   

 

Module 3 - Getting Familiar with vRealize Operations (30 Minutes)

Overview of vRealize Operations Management


VMware vSphere with Operations Management (vSOM) delivers an environment optimized for efficient server virtualization management. This is accomplished by pairing VMware vSphere, the world's leading virtualization platform along with vRealize Operations Manager.  This combination adds critical capacity management, intelligent alerting, performance monitoring and a host of other features/capabilities.  It is designed for businesses of all sizes to run applications at high service levels and maximize hardware savings through higher capacity utilization and consolidation ratios.


 

Simplify IT Management of Virtual Infrastructure Environments

 

vSphere with Operations Management offers a more intuitive user interface than vCenter Server and improves monitoring capabilities by adding predictive analytics to enable faster problem discovery and remediation as well as more efficient resource management.

Key Features of VMware vSphere with Operations Management

Unified Command Console displays key performance indicators in easily identifiable colored badges and provides a comprehensive view into what is driving current and potential future performance and capacity management issues.

Performance Monitoring and Capacity Management analyzes vCenter Server performance data and establishes dynamic thresholds that adapt to the environment and provide smart alerts about health degradations, performance bottlenecks and capacity shortfalls:

 

 

Video: vSphere with Operations Management - Overview (3:13)

Here is a short video that will show you the benefits of using vSOM in your environment.

 

Understanding the User Interface - vRealize Operations Manager



 

User Interface Overview

vRealize Operations Manager 6.6 is a complete redesign, and simplification, of the User Interface for Operations Manager. One of the major  advantages to the new Product User Interface (UI) is that the content panels are consistent while also being contextually relevant. In this section we will highlight a few of the major interface components, so that you can easily navigate the Product UI.

 

 

Open Chrome Browser from Windows Quick Launch Task Bar

 

If the Google Chrome browser is not open from a previous lesson, launch the Chrome browser:

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Gain screen space in vRealize Operations Product UI by zooming out - (Chrome)

 

You may find that all information cannot be properly viewed on the screen.  If this is the case:

  1. Select the Options menu in Chrome.
  2. Click the '-' button to zoom out to 90% or whatever percent allows for adequate viewing.

Note: This will provide more viewing space while still allowing you to read the text.

 

 

Log into vRealize Operations Manager

 

  1. Click on the Bookmark vROPS and confirm you are connecting to vrops-01a.corp.local.
  2. Ensure the Authentication Source is VMware Indentity Manager.
  3. Click REDIRECT

 

 

vIDM

 

  1. Userid: hol
  2. Password: VMware1!
  3. Click Sign In

 

 

New simplified Home Page

 

The new home page reflects the new simplified UI design in vRealize Operations Manager 6.6. It is made up of three focus areas;

  1. Title Bar
  2. Navigation Pane
  3. Content Pane  

This lesson will provide a summary of each.

 

 

Recommended Actions

 

 

 

Notifications

 

The Collection Notifications helps the Operations Manager admin know if there are any data sources that are not sending data. A Click into the Adapter info brings the admin right to information needed to diagnose any issues.

 

 

Refresh

 

The Refresh button, what can we say? It refreshes the page of course!

 

 

Quick Search

 

The Quick Search function auto-fills as you type and allows you to locate and view Objects in your environment with a single mouse click.  

 

 

Main Menu

 

The Main Menu is made up of:

 

 

Navigation Pane - Home

 

The Recomended Actions Page is the first page an admin will look at. It has a consolidated view of any actions the admin need to effect Object in the Virtual Infrastructure.

The view is broken into two primary windows, Scope and Suggested fix. Scope covers logical grouping of Objects and all issues for these object groupings. For instance All virtual machines and all alerts for all Virtual machines. Suggested Fix provides recomendations on how to fix a challenge seen by Operations and offers actions that can be taken to apply the fix.

 

 

Operations Overview

 

The Operations Overview page gives a quick snapshot view of the entire environment that Operations is aware of. It covers a count snapshot of all objects n the Environment, with growth count charts.  A widget that quickly shows count of alerts for Virtual Datacenters, along with Top 15 widget that show admin quickly the high level health of the infrastructure.

 

 

Capacity Overview

 

The Capacity Overview page shows the current capacity status of CPU, Memory, and Storage across the infrastructure, along with current high level reclaimable capacity numbers .

 

 

Workload Balance

 

The Workload Balance page shows the current balance status of the infrastructure, based on the new Workload Balance functionality in vRealize Operations.

 

 

Log Insight SSO

 

Click on LOGIN VIA SSO

 

 

Log Insight

 

The Log Insight page gives direct access to the Log Insight UI from vRealize Operations.

 

 

vRealize Business

 

The Business Management page gives diect SSO access to the vRealize Business for Cloud (vRBC) UI, when vRBC is Installed and configured. This is not the case in this HOL Lab. Also since the lab does not have internet access the intro Video will not load.

 

 

Navigation Pane - Dashboards

 

Dashboards, Views and Reports are all methods for viewing Objects/Metrics collected (or calculated) by vRealize Operations.  Customizing Dashboards or Reports is not enable for vRealize Operations Standard which is part of the vSOM license key.  You can create customized Views with vRealize Operations Standard.

Note: You can click on any of the navigation links to verify data displayed in the Content Pane. We will cover Dashboards and Alerts in detail in an upcoming modules.  Worth noting is that there are three distinct editions of vRealize Operations.  They are Standard, Advanced and Enterprise.  From a high level, Standard is Out-of-the-Box functionality.  This version is EULA limited and cannot be mixed with Advanced or Enterprise licenses within the same vRealize Operations cluster.  Advanced is customized infrastructure visibility.  While Enterprise extends to customized application level visibility.  As an example, the Dashboard edit button is greyed out because this feature is not enabled for vRealize Operations Standard, which is the edition for vSOM.

 

 

Navigation Pane - Alerts

 

The Alerts Page shows a chronologically sorted list of recent Alerts in your environment that need attention.  Alerts are categorized based on their criticality, status, and impact on health, risk, or efficiency.

  1. You can quickly filter Alerts by keyword in the form on the right side.
  2. You can Group Alerts by Time, Criticality, Definition, and Object Type

 

 

Alert Settings

 

The Alert Settings page allows you to customize:

 

 

 

Navigation Pane - Environment

 

The Environment Overview page shows how objects like Virtual Machines, Datastores, Operatings Systems, etc. are grouped in Operations Manager. This page is also how admins can drill up and down the hierarchy and to view and understand the relationships of all objects in vRealize Operations Manager

Groups and Applications currently have three constructs; Custom Groups, Applications and Custom Datacenters.  Custom Groups is the most powerful construct and is used by policies to segment what policy is associated with what object. Applications is a legacy construct associated with VMware Infrastructure Navigator (VIN).  Unless you have installed and integrated VIN, you will not need to use this construct.  And Custom Datacenters is a construct used for Workload Placement (WLP).  

 

 

Navigation Pane - Administration

 

The Administration Page contains all administration options including Solutions (Adapters), User Management and Support tools.

 

 

 

Conclusion

This concludes the section "Understanding the User Interface - vRealize Operations".  You should have a solid understanding of navigating and identifying where key content is located within vRealize Operations.

 

Exploring vRealize Operations Manager


vRealize Operations Manager 6.6 is a complete redesign, and simplification, of the User Interface for Operations Manager. This section will cover a couple of key areas of the vRealize Operations Manager tool by exploring Dashboards and Reports.


 

Open Chrome Browser from Windows Quick Launch Task Bar

 

If the Google Chrome browser is not open from a previous lesson, launch the Chrome browser:

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Log into vRealize Operations Manager

 

  1. Click on the Bookmark vROPS and confirm you are connecting to vrops-01a.corp.local.
  2. Ensure the Authentication Source is VMware Indentity Manager.
  3. Click REDIRECT

 

 

Exploring Dashboards

 

vRealize Operations Dashboards present a visual overview of the performance and state of objects in your virtual infrastructure.  You use dashboards to determine the nature and timeframe of existing and potential issues within your environment.  Through the Advanced and Enterprise editions, this can be extended to your physical infrastructure as well.

When you first log in to vRealize Operations Manager, you will land on the Home page. To access the available dashboards click on Dashboards, you will land on the Getting Started Dashboard.

From this page you can scroll through the different Catagories of Dashboards and select them to use. This will then activate them in the UI and add them to the list on the in the left pane..

 

 

Exploring Reports

 

Click on Reports in the Dashboards menu.  Reports are a scheduled snapshot of views and dashboards.  

With vRealize Operations Manager reporting functions, you can generate a report to capture details related to current or predicted resource needs.  You can download the report in PDF or CSV file format for future and offline needs.  Reports can also be scheduled to run at a user defined interval and emailed to recipients.

 

 

Conclusion

This concluded this lesson.  You should now have a solid understanding of Dashboards and Reports.

 

Module 4 - Introduction to vRealize Log Insight (30 Minutes)

Overview of vRealize Log Insight


vRealize Log Insight delivers real-time log management for VMware environments, with machine learning-based Intelligent Grouping, high performance search and better troubleshooting across physical, virtual, and cloud environments.

High Performance Ingestion

vRealize Log Insight can process any type of log or machine generated data. vRealize Log Insight supports very high throughput rates and low latency. vRealize Log Insight possesses a collection framework, which accepts data through syslog, Windows and Linux agents, or via a RESTful Ingestion API.

Scalability

vRealize Log Insight can scale out by using multiple virtual appliance instances. This enables linear scaling of the ingestion throughput, increases query performance and allows for ingestion high availability. In cluster mode, vRealize Log Insight provides master and worker nodes. Both master and worker nodes are responsible for a subset of data. Master nodes can query all subsets of data and aggregate the results. vRealize Log Insight provides an internal Load Balancer for scale out, allowing you to load balance and scale out from out of the box.

Real-Time Search

Data ingested by vRealize Log Insight is available for search within seconds. Also, historical data can be searched from the same interface with the same low latency.

vRealize Log Insight supports complete keyword queries. Keywords are defined as any alpha-numeric, hyphen, or underscore characters. In addition to the complete keyword queries, vRealize Log Insight supports glob queries (for example, erro?, vm*) and field based filtering (for example, hostname does NOT match test*, IP contains "10.64"). Furthermore, log message fields that contain numeric values can be used to define selection filters (for example, CPU>80, 10<threads<100, and so on).

Search results are presented as individual events. Each event comes from a single source, but search results may come from multiple sources. You can use vRealize Log Insight to correlate the data on one or multiple dimensions (for example, time and request identifiers) providing a coherent view across the stack. This way, root cause analysis becomes much easier.

vRealize Log Insight Agent

vRealize Log Insight uses a native Windows and Linux agent to gather log data from Windows and Linux servers as well as desktops. You can collect events from Windows event channels and log files, and forward them to the vRealize Log Insight server. Some of the benefits are centralized configuration, ease of use, data compression, and encryption.  3rd party agents are supported as well, but those benefits listed above provide unique advantages by using our native agent.

Intelligent Grouping

vRealize Log Insight uses a new machine learning technology. Intelligent Grouping scans incoming unstructured data and quickly groups messages together by problem type in order to give you the ability to rapidly understand issues that may span your physical, virtual, and hybrid cloud environments. The Event Trends tab in the Interactive Analytics page provides automatic analysis of your events with context around new insights and anomaly detection. We can now see how events are trending in a specified time interval and easily detect ones that are potentially affecting the health of your environment or application.

Aggregation

Fields that are extracted from log data can be used for aggregation. This is similar to the functionality that GROUP-BY queries provide in a relational database or pivot-tables in Microsoft Excel. The difference is that there is no need for extract, transform, and load (ETL) processes and vRealize Log Insight scales to any size of data.

You can generate aggregate views of the data and identify specific events or errors without having to access multiple systems and applications. For example, while viewing an important system metric, for example the number of errors per minute, you can drill down to a specific time-range of events and examine the errors that occurred in the environment.

Runtime Field Extraction

Raw log data is not always easy to understand, and you might need to process some data to identify the fields that are important for searching and aggregation. vRealize Log Insight extracts most fields automatically, and you can dynamically extract a new field from the data. It is as easy as double-clicking the message text and selecting “Extract Field”.  The regex is provided automatically based on your selection. The extracted fields can be used for selection, projection, and aggregation.

Dashboards

You can create dashboards of useful metrics that you want to monitor closely. Any query can be turned into a dashboard widget and summarized for any range in time. You can check the performance of your system for the last five minutes, hour, or day. You can view a breakdown of errors by hour and observe the trends in log events.

Security Considerations

IT decision makers, architects, administrators, and others who must familiarize themselves with the security components of vRealize Log Insight must read the VMware vRealize Log Insight Security Guide. For more information, you can visit the vRealize Log Insight Documentation found at https://www.vmware.com/support/pubs/log-insight-pubs.html

The Security Guide contains concise references to the security features of vRealize Log Insight. Topics include the product external interfaces, ports, authentication mechanisms, and options for configuration and management of security features.


 

Dashboards Overview

 

Dashboards – Think of the dashboards page as an overview section.  Dashboards provide the ability to quickly visualize log data and determine potential issues within an environment. Log Insight provides two different types of widgets inside a dashboard: charts and queries. Charts are a visual representation of data and the most commonly used widget. Queries are saved pieces of information that provide both a visual and textual representation of data on the Interactive Analytics page, but they are listed only by a defined name on the dashboards page. Query widgets are typically used when a chart widget does not necessarily provide useful information.

Interactive Analytics – Allows administrators and engineers to perform searches using plain language or REGEX strings and view log message detail to determine problem areas and perform root cause analysis.

 

 

Interactive Analytics Overview

 

The Interactive Analytics page allows administrators and engineers to drill down into log messages, to determine problem areas, and to perform root cause analysis.

At the top of the page, just below the navigation bar, you will notice a section with a black background. This section gives you a visual representation of your log data.

The chart in this section should look similar to the chart widgets that you saw on the Dashboards page. By default, the overview chart is a bar chart that displays the count of all events over time for the log messages seen over the last five minutes. Log Insight refers to ingested data as events. The events visually represented on the overview chart can be manipulated in a variety of ways, but most commonly are changed through the use of functions and groupings.

There are many options available once you have created a custom query in the Interactive Analytics page:

 

 

Content Packs Overview

Content packs provide a powerful way to extend Log Insight through pre-defined knowledge about particular events. To browse to the Content Packs section, select the three bars icon in the navigation bar and select Content Packs.

A content pack is made up of various components. These components can include:

 

 

Administration Overview

The administration section provides health information as well as allows for the modification of configuration settings. All information displayed during the initial configuration wizard of the product can be modified from the administration section. There are other aspects of the administration section that are not configurable during the initial configuration wizard such as where cluster members and agents can be managed.

 

 

Configuring vRealize Log Insight

Now that we understand the purpose of vRealize Log Insight, the next step is to configure our environment.

 

Exploring vSphere Log Events


In this section we will use Log Insight explore the logs of a vSphere environment. Often, without a log analysis tools such as Log Insight, log errors are not viewed until production workloads have degraded or failed and the business is impacted. With Log Insight we can uncover log events and patterns that may ultimately lead to problems so we can take action beforehand. In this section we will focus on log analysis and dashboards, though you can use these same principles to create alerts and forward them to vRealize Operations or via SMTP.


 

Launch Chrome

 

  1. Open Google Chrome browser by double clicking on "Google Chrome" icon on desktop

 

 

View Logs in vRealize LogInsight

 

  1. Click on "vRLogInsight" Favorite in the tool bar - Because we are running the vCenter version of vRealize LogInsight, you will be prompted to trust the SSL Cert as you can only change the SSL Cert for the web interface into LogInsight with the vRealize Suite Version of LogInsight.
  2. Click on "Advanced"
  3. Then Click on "Proceed to log-01a.corp.loca (unsafe) - Don't worry, its safe

 

 

Login to LogInsight

 

  1. Username: admin
  2. Password: VMware1!
  3. Click Login

 

 

Log Insight Dashboard General Overview

 

If you have successfully connected to a vCenter, earlier in this module, the first screen you will see is the General Overview dashboard.

  1. If you are not already at this screen click the Dashboard tab.
  2. This is the dashboard category tile; it tells you the source of the dashboards that are available (to see a complete list of installed dashboards click the down arrow next to the category title). Dashboards are either created within Log Insight or come as part of a Content Pack. By default, the vSphere Content Pack comes pre-installed. Dashboards from any other content pack that you install can be found by clicking the arrow.
  3. This section is a list of actual dashboards for the current category - The image above shows the dashboards from the VMware - vSphere content Pack.
  4. This section of the screen allows you to apply a date/time range filter to limit the data you are viewing within the dashboard.
  5. This section shows the filters which are available as part of this dashboard. The filters allow you to quickly focus the dashboard on a specific object/item of interest.
  6. Widgets, the widget in Log Insight are configured to query the consolidated log database and show specific areas of regular interest. In this case, the widget is showing a graphical representation of all the vSphere log messages and when they were generated. Widgets can be arranged in multiple ways and sizes.

 

 

Switch to Interactive Analytics

 

  1. Click the Interactive Analytics tab

 

 

Filters

 

After deleting the Event Type, the log messages are retained.  They are only removed from this query and the system automatically creates a filter or constraint excluding that specific event type.

 

 

Navigate to the Dashboards page

 

  1. Click the Dashboards tab

 

Module 5 - Administration Basics (60 Minutes)

Introduction


This Module contains the following lessons:


Cluster Management


A vSphere cluster is a construct that lets you aggregate compute resources. The Clusters construct allows for features like vSphere High Availability (HA) and vSphere Distributed Resource Scheduler (DRS). The cluster construct provides the ability to manage a group of VMs and ESXi hosts to improve resource utilization. When you power on a virtual machine that is part of a cluster, it can be given resources from anywhere in the cluster, rather than being tied to a specific vSphere ESXi host.  If an ESXi host fails, the VM is restarted on another ESXi host within the cluster (assuming HA is configured).  If an ESXi host experiences contention, DRS provides the ability to vMotion the VM to another ESXi host in the cluster that has available resources.


 

Video: Create vCenter Inventory (Datacenter, Cluster, Hosts) for VMware vSphere (2:51)

The following video will show the basics to getting started creating your VMware vCenter Server Inventory using the vSphere Web Client. Please note that these tasks can also be completed using the vSphere Client, which is also known as the HTML5 Client.

 

Create and Edit a Virtual Machine


In this lesson, you will walk through creating a virtual machine and editing its settings.


 

Launch Google Chrome

 

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Create a Virtual Machine

 

There are several ways to create a new VM using the vSphere Client.  We will be using the Actions Menu under the VMs and Templates dropdown. 

  1. Click on the Menu dropdown at the top of the screen.
  2. Select "VMs and Templates" from the drop-down menu.

 

 

Video: Create VM, Install Guest OS and Install VMware Tools (4:09)

We have just completed creating our virtual machine, but at this point, there is no operating system installed.  The Hands-on Lab Environment does not have sufficient resources to allow us to complete the process of installing the guest OS and VMware tools.  The following video will show the remainder of the process. Note that the video uses the vSphere Web Client. This will give you a chance to see what that client looks like. All of these tasks can also be completed using the vSphere Client.

 

 

Edit the Settings of a Virtual Machine

 

Once we have created a virtual machine, we can change the hardware that is associated with it, just like a physical machine.

  1. Right-Click on "linux-micro-01a.corp.local".
  2. Click "Edit Settings" to add additional physical resources to the virtual machine.

 

Migrate a Virtual Machine


VMware vMotion enables the live migration of running virtual machines from one physical server to another with no perceivable impact to the end user.  vMotion is a key technology for creating a dynamic, fully automated datacenter.

With vMotion you can:


 

Migrate Powered-On Virtual Machine with vMotion

 

First we want to confirm where the Virtual Machine (VM) is running.

  1. Confirm you are still highlighted on the VMs and Templates tab in the navigation pane.
  2. Click on "linux-micro-01a".
  3. Click the "Summary" tab in the context pane.
  4. Note that the IP address for the VM is 192.168.120.51
  5. Confirm the "Host" the VM is running on. In this case, the VM is running on "esx-01a.corp.local".

 

Working with Virtual Machine Snapshots


Snapshots preserve the state and data of a virtual machine at the time you take the snapshot. Snapshots are useful when you must revert to a previous virtual machine state. You can also take multiple snapshots of a virtual machine to create restoration points in a linear process. With multiple snapshots, you can save many positions to accommodate many kinds of work processes. The Snapshot Manager in the vSphere Web Client provides several operations for creating and managing virtual machine snapshots and snapshot trees. These operations let you create snapshots, restore any snapshot in the snapshot hierarchy, delete snapshots, and more.

A Virtual Machine snapshot preserves the following information:

In this lesson, you will create a Virtual Machine snapshot, make changes to the Virtual Machine's hardware and configuration state, and then revert back to the original state of the Virtual Machine by leveraging the vSphere Client Snapshot Manager.


 

Taking a Snapshot

 

The previous lesson left the vSphere Client open at the VMs and Templates navigation pane.  If you closed Google Chrome or the Web Client, navigate back to VMs and Templates in the vSphere Client.

To start the VM Snapshot Wizard:

  1. Locate linux-micro-01a and right click on the VM
  2. Hover over Snapshots
  3. Select Take Snapshot in the drop-down menu

 

 

Manage Snapshots

 

We can view the snapshot history of the virtual machine with the Snapshot.

  1. Locate linux-micro-01a and right click on the VM
  2. Hover over Snapshots
  3. Select Manage Snapshots in the drop-down menu

 

 

Reconfigure the Virtual Machines - Power Off VM

 

Let's power off our virtual machine now:

  1. Right-Click on linux-micro-01a
  2. Expand the drop-down menu by hovering over Power
  3. Click Power Off from drop-down and select Yes in the pop-up box

 

 

Manage Snapshots - Revert Virtual Machine Settings

 

In this step, you will revert the VM's CPU/Memory configuration back to the original state using the latest snapshot

  1. Select linux-micro-01a in the navigation pane, if it is not already highlighted
  2. Click on the Actions drop-down
  3. Hover over Snapshots
  4. Click Revert to Latest Snapshot

Note: This could also be completed by selecting "Manage Snapshots". That method provides greater control when you have multiple snapshots.

 

 

Lab Clean-up - Delete Snapshots

 

  1. Locate linux-micro-01a and right click on the VM
  2. Hover over Snapshots
  3. Select Manage Snapshots in the drop-down menu

 

 

Lab Clean-up - Delete Snapshots (Continued)

 

  1. Click the Delete All button, and click OK on the pop up that appears.
  2. Click Done.

 

 

 

Video: Virtual Machine Snapshots for VMware vSphere (2:32)

For our lab, the snapshot was used to revert our virtual machine to a previous hardware state.  A typical use case can be to take a snapshot of a virtual machine before the installation of a software package.  If something goes wrong, you can revert to a previous state and retry the installation.  The following video will provide additional insight into the value of virtual machine snapshots. Note that the video uses the vSphere Web Client. This will give you a  chance to see what that client looks like. All of these tasks can also  be completed using the vSphere Client.

 

Cloning Virtual Machines and Using Templates


VMware provides several ways to provision vSphere virtual machines.  One method is to create a single virtual machine, install an operating system on it and then use that virtual machine as a base image from which to clone other virtual machines. Cloning a virtual machine can save time if you are deploying many similar virtual machines. You can create, configure, and install software based on a single virtual machine. You can clone it multiple times, rather than creating and configuring each virtual machine individually.

Another provisioning method is to clone a virtual machine to a template. A template is a master copy of a virtual machine that you can use to create and provision virtual machines. Creating a template can be useful when you need to deploy multiple virtual machines from a single baseline, but want to customize each system independently of the next. A common value proposition for using templates is to save time. If you have a virtual machine that you will clone frequently, make that virtual machine a template and deploy your virtual machines from that template.

In this lesson, you will clone an existing Virtual Machine to a Template and deploy a new Virtual Machine from that Template.


 

Clone Virtual Machine to Template

 

You should still be on the VMs and Templates tab in the navigation pane.

  1. Locate linux-micro-01a and right-click on the VM.
  2. Hover over Clone
  3. Select Clone to Template

 

 

Deploy a Virtual Machine from a Template

 

  1. Right Click the Template Tiny Linux Template
  2. Click on "New VM from This Template..."

 

 

Cleanup - Power Off TinyLinux-VM

 

Let's power off our virtual machine now:

  1. Right-Click on TinyLinux-VM
  2. Expand the drop-down menu by hovering over Power
  3. Click Power Off from drop-down and select Yes in the pop-up box

 

 

Video: Virtual Machine Cloning and Templates for VMware vSphere (4:04)

For additional features of cloning and templates for vSphere, please watch the following video. Note that the video uses the vSphere Web Client. This will give you a  chance to see what that client looks like. All of these tasks can also  be completed using the vSphere Client.

 

Abstraction of Storage for More Efficient Management and Better Control



 

vSphere Storage Overview

The following lesson provides an overview of the different types of storage available in vSphere.  The vSphere Hypervisor, ESXi, provides host-level storage virtualization, which logically abstracts the physical storage layer from virtual machines.  

A vSphere virtual machine uses a virtual disk to store its operating system, program files, and other data associated with its activities. A virtual disk is a large physical file, or a set of files, that can be copied, moved, archived, and backed up as easily as any other file. You can configure virtual machines with multiple virtual disks.  

To access virtual disks, a virtual machine uses virtual SCSI controllers. These virtual controllers include BusLogic Parallel, LSI Logic Parallel, LSI Logic SAS, and VMware Paravirtual. These controllers are the only types of SCSI controllers that a virtual machine can see and access.  

Each virtual disk resides on a vSphere Virtual Machine File System (VMFS) datastore or an NFS-based datastore that are deployed on physical storage. From the standpoint of the virtual machine, each virtual disk appears as if it were a SCSI drive connected to a SCSI controller. Whether the actual physical storage device is being accessed through parallel SCSI, iSCSI, network, Fibre Channel, or FCoE adapters on the host is transparent to the guest operating system and to applications running on the virtual machine.  

The vSphere storage management process starts with storage space that your storage administrator allocates on different storage systems prior to vSphere ESXi assignment.  vSphere supports two types of storage - Local and Networked. Both are detailed in the following pages.

 

 

Viewing a Datastores Configuration

This lab will show you where you can examine details about the storage used by your virtual infrastructure.

 

 

Common Virtualized Storage terms

This lesson will wrap up by providing an overview of a few common terms:

 

Managing Your Storage


vRealize Operations Manager has various tools that will assist you in managing your storage.  Alerts that will identify when there are problems in the environment, dashboards that will allow you to monitor your environment proactively, and out of the box reports that can be fully customized.


 

Open Chrome Browser from Windows Quick Launch Task Bar

 

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Log into vRealize Operations Manager

 

  1. Click the "vROps" bookmark in Google Chrome. Insure you are connecting to "vrops-01a.corp.local".
  2. In sure the "Authentication Source:" is "Local Users".
  3. Type admin in the User name field.
  4. Type VMware1! in the Password field.
  5. Click the "Log in" button.

Note: All of the user credentials used in this lab are listed in the README.TXT file on the desktop.

 

 

Navigate to Dashboards

 

  1. Click on the Home drop down menu.
  2. Click on Dashboards.

 

  1. Click on the All Dashboard dropdown menu
  2. Check the Operations checkbox

 

 

vSphere Datastores Dashboard

 

vRealize Operations has numerous dashboards that we can use to help manage our infrastructure, including our storage.

  1. Under the Dashboards list, click on Datastore Usage Overview.

 

 

Native vSAN Management

 

vSAN Management is nateively integrated with the latest versions of vRealize Operations Manager.

  1. The lab environment does not use vSAN, however clicking on the vSAN Operations Overview or the Optimize vSAN deployments would provide you important information to help you manage any vSAN clusters that are in use.

For additional visibility into your storage environment, the vRealize Operations Management Pack for Storage Devices (MPSD) can be installed on any Advanced or Enterprise edition of vRealize Operations Manager.  The Management Pack can connect to any storage device that has a VASA provider, and SAN/NAS Switches from Brocade or Cisco using SMI-S. Performance Data is collected from Host HBA’s, NIC, VMs, and SAN/NAS switches.

MPSD provides visibility into your storage environment. Using Common Protocols to collect performance and health data from the storage devices. Pre-defined dashboards allow you to follow the path from a VM to the storage volume and identify any problem that may exist along that path. There is no visibility beyond the storage path unless additional vendor hardware storage management packs are installed and these again would require Advanced or Enteprise editions of vRealize Operations Manager.  Here are some of the benefits of MPSD:

Note:  Management Packs allow for extensibility of vRealize Operations Manager.  Management Packs dealing with infrastructure components require Advanced or Enterprise editions of vROps.  There are also application level management packs for SQL, Oracle and others.  Application level management packs require the Enterprise edition of vROPs.

 

Build and Manage your Virtual Infrastructure - Scale Out


vSphere with Operations Manager is suitable for small environment and scales up to meet the demands of large enterprises. With a scale up and scale out architecture vSOM can grow with your environment.  The flexible architecture allows for geographical deployments.


 

vCenter Server - Configuration Maximums

 Note: Click on the link for a complete list of current vSphere v6 Configuration Maximums. Guidance for future releases are provided at GA (General Availaibity).

 

 

vRealize Operations - Architecture Overview Video (3:30)

 

 

vRealize Operations Manager - Configuration Maximums

vRealize Operations (vROps) provides a scalable cluster/node architecture that can scale to the largest of environments.

Note: Configuration maximums apply to vRealize Operations v6.1 and v6.2.  Guidance for future releases are provided at GA (General Availaibity).

 

 

vRealize Operations - Scalability Video (3:03)

 

Conclusion


This module walked you through many of the daily management tasks that are performed by virtualization administrators world wide on a daily basis. You learned various ways to create, edit, and manage Virtual Machines. You also learned about the various types of storage that Virtual Machines can leverage, and the tools that vSphere with Operations Management provides to help you monitor that storage. Finally you learned about vSphere's scalability.

We hope you have enjoyed taking this module and have a better understanding of using vSphere 6.5. Be sure to take the survey at the end.


 

You've finished Module 5

Congratulations on completing Module 5.

If you are looking for additional information on administering and managing vSphere with Operations Management, try one of these:

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

If this is the last module you would like to take in this lab, you may end your lab by clicking on the END button.    

 

Module 6 - Upgrading vCenter (30 Minutes)

Introduction


This Module contains the following lessons:


Upgrading vCenter


vSphere provides many options for upgrading your vSphere deployment. For a successful vSphere upgrade, you must understand the upgrade options, the configuration details that impact the upgrade process, and the sequence of tasks.  This module will discuss how to upgrade vCenter Server to the latest version using the standard upgrade workflows. Due the time required to upgrade an environment, we will only be discussing each upgrade path.


 

Overview of the vCenter Server Upgrade Process

VMware provides many options to upgrade to vCenter Server 6.5.

You can upgrade or migrate your vCenter Server version 5.5 or version 6.0 installation to version 6.5 using the method that best addresses your deployment goals and requirements. You will not be able to upgrade directly to vCenter Server 6.5 from vCenter Server 5.1 or earlier. You must first upgrade to vCenter Server version 5.5 or 6.0.

 

 

vCenter Server High-level Upgrade Tasks

 

Select your upgrade:

 

 

vCenter Server Supported Upgrade Methods

If you plan to run vCenter on a Physical Server on Windows, verify your hardware meets the necessary to requirements to run vCenter.

 

 

vCenter Server Components and Services

vCenter Server 6.5 provides a centralized platform for management, operation, resource provisioning, and performance evaluation of virtual machines and hosts.

When you upgrade to vCenter Server with an embedded Platform Services Controller, or to vCenter Server Appliance with an embedded Platform Services Controller, vCenter Server, the vCenter Server components, and the services included in the Platform Services Controller are deployed on the same system.

When you upgrade to vCenter Server with an external Platform Services Controller, or deploy the vCenter Server Appliance with an external Platform Services Controller, vCenter Server and the vCenter Server components are deployed on one system, and the services included in the Platform Services Controller are deployed on another system.

The following components are included in the vCenter Server and vCenter Server Appliance installations:

 

 

vCenter Server Upgrade Compatibility

The upgrade to vCenter Server affects other software components of the data center. vCenter Server 6.5 can manage ESXi version 5.5 or 6.0 hosts in the same cluster with the next version ESXi. The next major release of vCenter Server cannot manage ESXi 5.1 or earlier hosts.

As mentioned at the beginning of this module, you cannot upgrade to vCenter Server 6.5 from vCenter Server 5.1 or earlier. You must first upgrade to vCenter Server version 5.5 or 6.0.

 

Conclusion


This module introduced you to some of the considerations you will have when upgrading from a previous version of vSphere to vSphere 6.5


 

You've finished Module 6

Congratulations on completing Module 6.

If you are looking for additional information on upgrading for vSphere 6.5, try one of these:

Proceed to any module below which interests you most.

 t

 

 

How to End Lab

 

If this is the last module you would like to take in this lab, you may end your lab by clicking on the END button.    

 

Module 7 - vCenter Server Appliance Migration (30 Minutes)

Introduction


This Module contains the following lessons:


Hands-on Labs Interactive Simulation: vCenter Server Appliance Migration


The purpose of this module is to demonstrate how to upgrade and migrate a “Windows vCenter Server 5.5” with a local “SQL Server Database” connected to an external “Windows SSO Server” to the new “vCenter Server Appliance (VCSA)” with a “vPostgres Embedded Database” connected to an external “Platform Services Controller (PSC)”.

You can accomplish this by using the Migration Assistant for vSphere 6.5, which is initiated separately on the source Windows vCenter Server and Windows Single Sign-On Server respectfully.

Please note: VMware recently announced vCenter Server Migration Tool: vSphere 6.0 Update 2m. This is a separate release from the Migration Assistant for vSphere 6.5 we are discussing in this module.  During 2013, VMware released the VCS to VCVA Converter Fling based on a winning idea from the annual Fling contest. The VCS to VCVA Converter Fling allowed customers to migrate their entire Windows vCenter Server 5.5 which included configuration, inventory, historical data, and identity to a vCenter Server Appliance 5.5. While the VCS to VCVA Converter Fling was able to address our needs for an end to end migration tool, it was released with a subset of features. This allowed for quicker availability of the Fling and customer feedback. VMware took its learning from the VCS to VCVA Converter Fling improving and adding more features, resulting in vSphere 6.0 Update 2m.

A key difference between these two releases is vSphere Update Manager 5.5 / 6.0 is able to be upgraded and migrated to vCenter Server Appliance 6.5 using the Migration Assistant for vSphere 6.5.  This is because vSphere Update Manager will run on the vCenter Server Appliance version 6.5.


 

Migration Process Overview

 

Migrating a Windows vCenter with an external SSO to the new vCenter Server Appliance with an external Platform Services Controller is a 2-step process.  If you choose to, the process will enable you to migrate everything (Configuration, events, tasks, and performance metrics) to the new vCenter Server Appliance.  This is optional and may impact migration's length of time to complete.

Prior to this tool, a manual migration like this would result in a new Universal Unique Identifier (UUID) and new Managed Object Reference (MoRef) ID, thus causing challenges for external applications.

This vCenter Server Appliance migration process consists of two stages (for each source):

• Stage 1: Deploy a fresh appliance / OVF

• Stage 2: Setting up the appliance server

This simulation will go through each stage of the vCenter Server Appliance Migration which is too time-consuming and resource intensive to do live in the lab environment.

1. Click here to open the interactive simulation.  It will open in a new browser window or tab.

2. When finished, click the "Return to the lab" link or close the window to continue with this lab.

 

Conclusion


In this module you were able to step through the migration process to move to vSphere 6.5. The built in migration tool greatly simplifies this process as compared to previous versions of vSphere.


 

You've finished Module 7

Congratulations on completing  Module 7.

If you are looking for additional information on vCenter Server Appliance Migration, try one of these:

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

If this is the last module you would like to take in this lab, you may end your lab by clicking on the END button.    

 

Module 8 - High Availability and Business Continuity (60 Minutes)

Introduction


This Module contains the following lessons:


vCenter Server High Availability Overview


The next release of vCenter introduces a native option to protect a vCenter Server deployment from hardware failures

High availability (HA) involves setting up a vCenter Server passive node and a witness node in addition to the vCenter Server active node that you are trying to protect. vCenter Server HA provides a much improved HA experience. This lab will explain vCenter Server HA


 

vCenter Server High Availability

 

The high availability setup involves setting up a vCenter Server passive node and a Witness node in addition to the vCenter Server active node that you are trying to protect. The three nodes form the vCenter Server HA cluster.

 

 

Basic and Advanced Workflows for vCenter Server HA

There are two workflows that can deploy vCenter server HA – Basic & Advanced. The Basic workflow can be used in most circumstances such as when a vCenter Server is self-managed (i.e. the vCenter Server is managing the hosts that itself is running on) or if it is running under another management vCenter Server that is part of the same SSO Domain. As its name suggests, this workflow is very simple and creates the Passive and Witness nodes automatically. It also creates DRS anti-affinity rules if DRS is enabled on the destination cluster and uses Storage DRS for initial placement if enabled. There is some flexibility built into this workflow such that users can choose specific destination hosts, datastores, and networks for each node. But the idea is that this is a very simple, easy way to get a vCenter HA cluster up and running.

The alternative is the Advanced workflow. This workflow can be used when the Active, Passive, and Witness nodes are to be deployed to different clusters, vCenter Servers that are not part of the same SSO Domain, or even other data centers. This process requires the administrator to manually clone the source vCenter Server for the Passive and Witness nodes and then place those nodes in the desired locations with the appropriate IP address settings. This is certainly a more involved process but allows for greater flexibility for those customers who require it.

 

The graphic above breaks down when to use the Basic or Advanced workflows to enable vCenter HA. Remember that these two workflows produce an identical solution. There is no additional functionality gained by using the advanced workflow. The Basic workflow should be used whenever possible as it is really the easy button for enabling vCenter Server HA. There is far more work when performing the Advanced workflow.

 

 

vCenter High Availability Additional Information

For more information in VCHA, please refer this lightboard video. Also, the next lesson will walk you through configuring VCHA using a simulation.

 

vCenter Server Appliance: Platform Services Controller High Availability (PSC HA)


The vCenter Server Appliance 6.5 introduces a native option to protect a vCenter Server deployment from failures in hardware, hosts, and vCenter Appliance services.  

The Platform Services Controllers (PSC) will also support High Availability natively, but do require an external load balancer when configuring external Platform Services Controllers for High Availability. In this lab, we have provided an Interactive Simulation (iSIM) on configuring High Availability for the vCenter Server Appliance. Also configuring the Platform Services Controllers for High Availability is an advanced task, so we have only provided some basic architectural information about this configuration.


 

Platform Services Controller High Availability (PSC HA)

In a few pages from this one, we have an Interactive Simulation (iSIM) on configuring vCenter Server High Availability, it contains the previous version of the vSphere Web Client. So be aware in the simulation after clicking on the vCenter server, we then click on the Manage tab instead of the Configuration tab that is in the new version. There will be some name differences as well as what is in the pages that will look different between the old and newer version of the vSphere Web Client. But the setup is essentially the same process.

 

We are also providing Platform Services Controller High Availability (PSC HA) which means you will need to use a third-party load balancer to get High Availability (HA) for your Platform Services Controller (PSC) infrastructure.  

The PSC will operate more like DNS, where each vCenter will now know where all the Platform Services Controllers are in it’s domain. In the event that any Platform Services Controllers service fails, then the vCenter will automatically fail over to the next Platform Services Controller. The diagram above shows how this works. The large arrows are where the vCenter is affinitized to (where it was installed against). If a Platform Services Controller fails, the vCenter can fail over through one of the dotted lines to another Platform Services Controller.

The High Availability mode is realized when the vCenters and Platform Services Controllers are all at the same functional level (everything is at same major build level). You can operate in mixed mode but PSC HA won’t be operational.

For more detailed information on how to configure High Availability for the Platform Services Controllers along with the vCenter Server Appliance 6.5, refer to this VMware KB article here.

NOTE: Links in the lab manual are for reference only and the Hands On Lab environments MAY NOT be connected to the internet. So we are unable to access them in most cases, however we can save the link by taking note of the web address or taking a picture with the camera on a cellular phone.

 

 

vSphere Web Client (Newest Version)

 

NOTE: In this lesson, we are only referring the screen captures and not actually looking at and manipulating anything in the lab environment you are currently working in.

Depending on what version of the vSphere Web Client we may be looking at, we will see some slight differences such as names of tabs and buttons in the main content pane. In this particular lesson where we are discussing the configuration of High Availability for the vCenter Server:

  1. We see that the tab name is called Configure to get to the configuration section for vCenter Server High Availability. (in the new version the tab is called Manage)
  2. Then once we click on vCenter HA, we then click on the Configure button. (in the old client the button is called New Configuration)

 

 

vSphere Web Client (Previous Version)

 

In the Interactive Simulation (iSIM) that we will watch shortly, we have the previous version of the vSphere Web Client than what is currently in the lab environment:

  1. The simulation has us click on the vCenter Server and then the Manage tab. (in the new client the tab is called the Configure tab)
  2. Then we will select vCenter HA and click on the New Configuration button to start to configure High Availability. (in the new client the button is called Configure)

 

 

Hands On Labs - Interactive Simulation (iSIM): vCenter Server High Availability

Now we are going to launch the Interactive Simulation (iSIM). This simulation will walk us through the configuration of vCenter Server High Availability. Once finished with the Interactive Simulation (iSIM), please return to this page of the lab manual to continue with this module.

Interactive Simulation (iSIM): vCenter Server High Availability - CLICK HERE TO START THE INTERACTIVE SIMULATION (iSIM)

NOTE: The current video was recorded with the previous version of the vSphere Web Client. So you will see some the tab names and screens are slightly different from the most current version of the vSphere Web Client. Also, when in the Interactive Simulation (iSIM) where it has you type something into a text field, it will enter in the proper text for you no matter what you try to type into the text fields.

 

 

vCenter Server Appliance and Platform Services Controller High Availability Overview Complete

Although this was a brief overview of the architecture associated to setting up external Platform Services Controllers in High Availability, we hope that the options for vCenter Server architecture makes more sense now as to why and how you may architect a vSphere environment based on individual needs.

 

Demonstrate resilience to network component failures


This lab shows how to use the VMware vSphere web client to enable and configure network redundancy to protect the systems against network failures.


 

Open Chrome Browser from Windows Quick Launch Task Bar

 

  1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

 

 

Login to vCenter

 

 

Firstly let’s look at the status of the lab and the Platform Services Controller configuration:

Login in to RegionA vCenter and verify it is operating as expected

  1. Click on link in Favorites Bar - RegionA vCenter
  2. Check the Use Windows session authentication checkbox
  3. Click Login

 

 

Navigate to Hosts and Clusters

 

  1. First, go to the "Home" button
  2. Select "Hosts and Clusters"

 

 

Verify the Teaming and failover virtual switch

 

  1. Ensure you are on the Networking navigation tab.
  2. Click VM-RegionsA01-vDS-COMP.
  3. Select the Configure tab.
  4. Click the Policies under Settings section.
  5. Observe the Teaming and Failover configuration for the VM Network portgroup.

Here we can see that the portgroup has been configured to distribute the network traffic across all available uplinks using the Route based on originating virtual port policy. It will detect a network failure only if a link is declared down at the layer 2 level. We can also see that if an uplink comes back online again after a failure, it will be automatically added to the network team.

 

 

 

Using the vSphere Web Client, we can easily trace the network interfaces being used by a virtual machine for example. In this case we can see that virtual machine html5-app has network traffic being routed through vmnic0 and vmnic1.

 

vSphere Replication


VMware vSphere Replication is a hypervisor-based, asynchronous replication solution for vSphere virtual machines. It is fully integrated with VMware vCenter Server and the vSphere Web Client. vSphere Replication delivers flexible, reliable and cost-efficient replication to enable data protection and disaster recovery for all virtual machines in your environment.

VMware Business Continuity and Disaster Recovery (BC/DR) solutions drive automation, efficiency, data protection, and validation of an organization's enterprise-level BC/DR strategy. Learn how to reduce downtime and increase availability for your applications and services with Site Recovery Manager (SRM).

 For a deeper level of understanding of Site Recovery Manager (SRM) and vSphere Replication, please consider the following lab: HOL-1805-01-SDC: Site Recovery Manager - Data Center Migration and Disaster Recovery.


Conclusion


This module introduced you to the tools and features that you have access to that will help you ensure that your virtual infrastructure stays available through a variety of use cases and scenarios. It discussed the new High Availability feature for the vCenter Server Appliance. It also showed you you could protect your network against failure, and this in introduced some advanced Business Continuity/Disaster Recovery topics.


 

You've finished Module 8

Congratulations on completing Module 8.

If you are looking for additional information on High Availability and Business Continuity, try one of these:

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

If this is the last module you would like to take in this lab, you may end your lab by clicking on the END button.  

 

Conclusion

Thank you for participating in the VMware Hands-on Labs. Be sure to visit http://hol.vmware.com/ to continue your lab experience online.

Lab SKU: HOL-1811-02-SDC

Version: 20171020-145922