VOpsStandard Installation and User Guide

vOPS Server Standard 6.
0
Installation and User Guide
2012 Quest Software, Inc.

ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under
a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of
the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic
or mechanical, including photocopying and recording for any purpose other than the purchasers personal use without the
written permission of Quest Software, Inc.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel
or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products.
EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR
THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR
STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO
EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR
INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS
INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT,
EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or
warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make
changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to
update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
www.quest.com
email: legal@quest.com
Refer to our Web site for regional and international office information.
Patents
Patents pending.
Trademarks
Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag
and Follow, Vintela Single Sign-on for Java, vFoglight, vOPS, vKernel, and the vKernel logo are trademarks and registered
trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest
Softwares trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and
registered trademarks are property of their respective owners.
Third Party Contributions

vOPS contains some third party components. For a complete list, see the License Credits page in vOPS online help.
Installation and User Guide

August 2012
Version 6.0
vOPS Server Standard: Installation and User Guide
Table of Contents
Introduction to this Guide..................................................................................................................................................8
About Quest Software, Inc. ............................................................................................................................................................. 8
Contacting Quest Software ..................................................................................................................................................... 8
Contacting Quest Support ....................................................................................................................................................... 8
Installing vOPS Server Standard.....................................................................................................................................10

System Requirements ................................................................................................................................................................... 10
Installing as a VMware Virtual Machine ........................................................................................................................................ 11
Powering On and Initializing the Virtual Machine .................................................................................................................. 14
Setting a Static IP Address or Changing the Network Time Server ...................................................................................... 14
Installing as a Microsoft Hyper-V Virtual Machine......................................................................................................................... 15
Power On and Initialize the Virtual Machine.......................................................................................................................... 17
Installing as an RHEVM Virtual Machine....................................................................................................................................... 18
Power On and Initialize the Virtual Machine.......................................................................................................................... 21
Connecting to the RHEVM postgres Database remotely ...................................................................................................... 21
Initial Configuration of vOPS Server Standard .............................................................................................................................. 21
License Agreement ............................................................................................................................................................... 22
Connection Management ...................................................................................................................................................... 22
Initial Data Collection............................................................................................................................................................. 25
Logging in to vOPS Server Standard ............................................................................................................................................ 26
Managing Licenses ....................................................................................................................................................................... 27
Activating a Trial License ...................................................................................................................................................... 28
Activating a Purchased License ............................................................................................................................................ 29
Installing a License Received by E-mail................................................................................................................................ 32
Migrating Licenses from another Appliance .......................................................................................................................... 33
Deactivating All Licenses ...................................................................................................................................................... 33
Installing and Configuring the vKernel Hyper-V Collector ............................................................................................................. 33
System Center Integration............................................................................................................................................................. 36
Dashboard.........................................................................................................................................................................37
Configurable Dashboards and Dashboard Management ...................................................................................................... 37
Get Started Dashboard ......................................................................................................................................................... 40
Alarms and Bottlenecks......................................................................................................................................................... 40
Table of Contents
Capacity Efficiency and Availability........................................................................................................................................ 40

Infrastructure Overview.......................................................................................................................................................... 41
vScope Dashboards............................................................................................................................................................... 42
Performance Analyzer ..................................................................................................................................................... 43

Real Time Alarms .......................................................................................................................................................................... 43
Alarms Set in vCenter ............................................................................................................................................................ 44
Alarms Set in System Center................................................................................................................................................. 45
Root Cause............................................................................................................................................................................ 45
Actions History....................................................................................................................................................................... 46
Alarms by Resource............................................................................................................................................................... 46
Alarm History ......................................................................................................................................................................... 47
Alarm Configuration ............................................................................................................................................................... 47
Trend Alarms ................................................................................................................................................................................. 49
Alarm History ......................................................................................................................................................................... 49
Default Trend Alarms ............................................................................................................................................................. 54
Hypervisor Alarms ......................................................................................................................................................................... 54
Current Alarms....................................................................................................................................................................... 54
Alarm History ......................................................................................................................................................................... 55
Current Bottlenecks ....................................................................................................................................................................... 55
Summary................................................................................................................................................................................ 55
Root Cause............................................................................................................................................................................ 56
CPU ....................................................................................................................................................................................... 57
Memory .................................................................................................................................................................................. 58
Storage .................................................................................................................................................................................. 58
Throughput............................................................................................................................................................................. 59
Latency .................................................................................................................................................................................. 59
Datastore Performance.................................................................................................................................................................. 60
Performance vScope ............................................................................................................................................................. 60
Capacity Manager ............................................................................................................................................................ 62

Availability...................................................................................................................................................................................... 62
Capacity Availability ............................................................................................................................................................... 62
VM Reservations.................................................................................................................................................................... 67
Future Requirements ............................................................................................................................................................. 70
Datastore Statistics................................................................................................................................................................ 71
Top Consumers ..................................................................................................................................................................... 72
Current Bottlenecks ....................................................................................................................................................................... 73
Summary................................................................................................................................................................................ 73
Root Cause............................................................................................................................................................................ 73
CPU ...................................................................................................................................................................................... 74
Table of Contents
Memory ................................................................................................................................................................................. 75
Storage .................................................................................................................................................................................. 75
Throughput............................................................................................................................................................................. 76
Latency .................................................................................................................................................................................. 77
Future Bottlenecks......................................................................................................................................................................... 77
Overview ................................................................................................................................................................................ 77
Root Cause............................................................................................................................................................................ 78
Predictive Alarms........................................................................................................................................................................... 78
Active Alarms ......................................................................................................................................................................... 78
Capacity vScope.................................................................................................................................................................... 81
Optimizer........................................................................................................................................................................... 83
Rightsizer....................................................................................................................................................................................... 83
Summary................................................................................................................................................................................ 83
CPU ....................................................................................................................................................................................... 84
Memory .................................................................................................................................................................................. 85
Storage .................................................................................................................................................................................. 85
Rightsizer Constraints............................................................................................................................................................ 85
Wastefinder.................................................................................................................................................................................... 87
Abandoned VM Images ......................................................................................................................................................... 87
Powered Off VMs................................................................................................................................................................... 88
Unused Template Images...................................................................................................................................................... 88
Potential Zombie VMs............................................................................................................................................................ 89
Efficiency vScope................................................................................................................................................................... 90
Change Analyzer .............................................................................................................................................................. 92

Common Features in Change Analyzer......................................................................................................................................... 92
Risk Definitions ...................................................................................................................................................................... 92
Filters ..................................................................................................................................................................................... 93
Change Summary.......................................................................................................................................................................... 94
Infrastructure History ..................................................................................................................................................................... 95
Reverting Changes ................................................................................................................................................................ 97
VM Comparison ............................................................................................................................................................................. 98
Change Assessment.................................................................................................................................................................... 100
Change and Comparison Alarms................................................................................................................................................. 106
Change Alarms .................................................................................................................................................................... 107
Comparison Alarms ............................................................................................................................................................. 107
Reporting and Chargeback ........................................................................................................................................... 109

Summary Reports........................................................................................................................................................................ 109
Inventory ...................................................................................................................................................................................... 111
Table of Contents
List View............................................................................................................................................................................... 111

Detailed View ....................................................................................................................................................................... 114
Chargeback ................................................................................................................................................................................. 114
Creating Customized Pricing Models................................................................................................................................... 116
Cost Index vScope....................................................................................................................................................................... 119
The vKernel Cost Index (VCI) .............................................................................................................................................. 120
Common Features.......................................................................................................................................................... 122

Global Search .............................................................................................................................................................................. 122
Product Navigation ...................................................................................................................................................................... 122
Navigation Tree ........................................................................................................................................................................... 123
Infrastructure node............................................................................................................................................................... 123
Organizing your VMs ........................................................................................................................................................... 124
Business Views.................................................................................................................................................................... 125
Free-Form Business Views.................................................................................................................................................. 126
Smart Business Views ......................................................................................................................................................... 126
Resource Graphs......................................................................................................................................................................... 127
Reports ....................................................................................................................................................................................... 128
Table Reports ...................................................................................................................................................................... 128
Saving Reports .................................................................................................................................................................... 129
Emailing Reports.................................................................................................................................................................. 129
Scheduling Reports.............................................................................................................................................................. 130
Diagnose a VM ............................................................................................................................................................................ 130
Settings........................................................................................................................................................................................ 132
Settings > General > Environment....................................................................................................................................... 132
Settings > General > Database (DB) Settings ..................................................................................................................... 133
Settings > General > Savings .............................................................................................................................................. 135
Settings > General > Prices ................................................................................................................................................. 136
Settings > General > Scheduled Tasks ............................................................................................................................... 136
Settings > General > Deployment Tasks ............................................................................................................................. 137
Settings > General > Automated Tasks ............................................................................................................................... 137
Settings > General > Proxy.................................................................................................................................................. 138
Settings > General > Miscellaneous .................................................................................................................................... 139
Settings > Notifications > Alerts ........................................................................................................................................... 139
Settings > Notifications > System ........................................................................................................................................ 140
Settings > Notifications > Address Book.............................................................................................................................. 140
Settings > Notifications > Email ........................................................................................................................................... 141
Settings > Thresholds .......................................................................................................................................................... 141
Settings > Users .................................................................................................................................................................. 146
Settings > License .............................................................................................................................................................. 147
Settings > Configuration Groups.......................................................................................................................................... 148
Table of Contents
Settings > Dashboard URLs ................................................................................................................................................ 149
Index................................................................................................................................................................................ 150
Introduction to this Guide

This Installation and User Guide provides system requirements, installing, configurating, and log
in instructions for the vOPS Server Standard. In addition, this guide provides conceptual
information and instructions on how to use the browser interface.
About Quest Software, Inc.

Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and innovative IT
management solutions that enable more than 100,000 global customers to save time and money
across physical and virtual environments. Quest products solve complex IT challenges ranging
from database management, data protection, identity and access management, monitoring, user
workspace management to Windows management. For more information, visit www.quest.com.
Contacting Quest Software

Email
info@quest.com
Mail
Quest Software, Inc.

World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site
www.quest.com
Refer to our Web site for regional and international office information.
Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have
purchased a Quest product and have a valid maintenance contract. Quest Support provides
unlimited 24x7 access to our Support Portal at http://www.quest.com/support.
From our Support Portal, you can do the following:

Introduction to this Guide
Retrieve thousands of solutions from our Knowledge Base

Download the latest releases and service packs
Create, update, and review Support cases
View the Global Support Guide for a detailed explanation of support programs, online services,
contact information, policies, and procedures. The guide is available at: http://www.quest.com/
support.
1
Installing vOPS Server Standard
vOPS Server Standard is delivered as a fully configured virtual machine, which can be installed on
one of three platforms: VMware, Microsoft Hyper-V, or Red Hat Enterprise Virtualization
Manager (RHEVM). Before beginning installation, review the System Requirements and ensure
that your target system meets the requirements.
Refer to the appropriate section for installation instructions:
Installing as a VMware Virtual Machine on page 11
Installing as a Microsoft Hyper-V Virtual Machine on page 15
Installing as an RHEVM Virtual Machine on page 18
System Requirements
The vOPS Server Standard installation guidelines vary depending on how many virtual machines
(VMs) are being monitored. The table below outlines the system requirements for installing vOPS
Server Standard.
Number of VMs
1 to 200
200 to 1000
1000 to 3000
vOPS Server Virtual Machine

Number of CPUs
Memory Allocation
Memory Reservation
Allocated Storage
4
8 GB
8 GB
64 GB
4
8 GB
8 GB
64 GB
4
8 GB
8 GB
64 GB
Either
Either
Either
Less than 90%

Optional
Less than 80%

Optional
Less than 80%

Not Recommended
vOPS Server Database Selection

Internal or External
vOPS Server External
Database Server
Average CPU Use
Network Storage
11
Chapter 1Installing vOPS Server Standard
Number of VMs
VMware vCenter
Average CPU Use
5 Minute Interval Statistics Level
Minimum Privileges
vCenter Database Server

Average CPU Use
Network Storage
1 to 200
200 to 1000
1000 to 3000
Less than 90%

2 or 3
Read Only +Browse
Datastore
Less than 80%

2 or 3
Read Only + Browse
Datastore
Less than 80%

2
Read Only + Browse
Datastore
Less than 90%

Optional
Less than 80%

Optional
Less than 80%

Not Recommended
VMware Software Requirements:

VMware Player 1.0.0 or later
VMware Workstation 5 or later
VMware ESX Server 3.x or later
Virtual Center 2.5 or later, or VMware Server 1.03 or later
Hyper-V Software Requirements:
Systems Center Operations Manager 2007 R2 and Systems Center Virtual Machine Manager
2008 R2
Or
Systems Center Operations Manager 2012 and Systems Center Virtual Machine Manager
2012
Red Hat Software Requirements:
Red Hat Enterprise Virtualization 3.0
Installing as a VMware Virtual Machine

vOPS Server Standard is delivered as a fully configured VMware virtual machine that can be
installed directly using the VMware Deploy OVF Template option.
To download and install vOPS Server Standard:
1 Download the VMware version of vOPS Server Standard from the following location:
http://www.vkernel.com/downloads/all/
2 Save the file to a Windows server or workstation. The file is a compressed, self-extracting
executable (.exe).
3 Double-click to run the file. It creates a directory with the OVF file, three VMDK files, the
Hyper-V Collector directory, a Read Me file, the end user license agreement, and the user
documentation.
4 Open the VMware vSphere Client and select File > Deploy OVF Template.
Refer to the VMware documentation for more information on running the vSphere Client.

The Deploy OVF wizard opens.

5 Click Browse to navigate to the location of the extracted OVF file and select it.
Click Next.
6 On the OVF Template Details page, verify the Product and Version number.
Click Next.
12

7 On the Name and Location page, type a name for the virtual machine, and select a
destination folder.
Click Next.
8 On the Resource Pool page, select a location within the infrastructure hierarchy.
Click Next.
9 On the Storage page, select the datastore that the VM will reside within.
13
14
Click Next.
10 On the Disk Format page, select the type of datastore provisioning.
Click Next.
11 Review the deployment settings and click Finish.
Powering On and Initializing the Virtual Machine

After installing the OVF, you must power on and initialize the virtual machine.
Open vCenter, select the vOPS Server Standard virtual machine you just installed and click Power
on the virtual machine.
Once the appliance is started, it initializes the operating system and starts vOPS Server Standard.
The DHCP server automatically obtains the IP address. By default, Pool.ntp.org is used as the
Network Time Protocol (NTP) server. These options can be changed after vOPS Server Standard
has started successfully.
Wait until the IP address of vOPS Server Standard appears in the vCenter Summary tab. After the
IP address appears it will take several more minutes to start the application server. Once that is
completed, you can access vOPS Server Standard using the IP address and a standard web
browser.
If there is no DHCP server available, you must manually enter the IP address before vOPS Server
Standard will be usable. Open a console window and respond to the questions about the IP address
and the network time server.
Setting a Static IP Address or Changing the Network Time Server

1 Open a VI Client console window and log in as root, with password for the password.
2 Change the directory to: /usr/local/vkernel/scripts.
3 Run the changeIp.sh script. Follow the prompts to set the desired IP address and network
time server.
Once that is completed, you can access vOPS Server Standard using the IP address and a standard
browser.
15
Installing as a Microsoft Hyper-V Virtual Machine

vOPS Server Standard is delivered as a fully configured Hyper-V virtual machine that can be
installed directly using the Microsoft Hyper-V Manager.
To download and install vOPS Server Standard:
1 Download the Microsoft Hyper-V version of vOPS Server Standard from the following
location: http://www.vkernel.com/downloads/all/
2 Save the compressed, self-extracting .exe file to a Windows server or workstation.
3 Double-click to run the file. It creates a directory containing the required VHD directories,
the Hyper-V Collector directory, a Read Me file, the end user license agreement, and the user
documentation.
4 Open the Microsoft Hyper-V Manager, right-click on the desired Hyper-V host and select
Import Virtual Machine.

Refer to the Microsoft documentation for more information on running the Hyper-V
Manager.
The Import Virtual Machine dialog opens.

5 Select Copy the virtual machine (create a new unique ID).

6 Click Browse to browse to and select the location of the extracted VHD directories.
7 In the Import Virtual Machine dialog box, click Import.
The virtual machine is imported and appears in the list of virtual machines for the host.
8 Right-click the vOPS Server Standard virtual machine and select Settings.
9 In the left pane, select the Network Adapter.

10 In the right pane, specify the appropriate network adapter configuration information.
16
17
11 Click OK.
Power On and Initialize the Virtual Machine

Open the Hyper-V Manager, select the vOPS Server Standard virtual machine you just installed
and click Start.
Once the appliance is started, it initializes the operating system and starts vOPS Server Standard.
The IP address is obtained from the DHCP server automatically. By default, Pool.ntp.org is used
18
as the Network Time Protocol (NTP) server. These options can be changed after vOPS Server
Standard has started successfully.
Once the virtual machine is running, right-click on the vOPS Server Standard virtual machine and
click Connect.
1 The console opens. Log in as root, with password for the password.
2 Run the ifconfig command.
3 Access vOPS Server Standard using the IP address (inet addr:) and a standard web
browser.
If there is no DHCP server available, you must manually enter the IP address before vOPS Server
Standard will be usable. Respond to the questions about the IP address and the network time
server.

1 Open the Hyper-V Manager and connect to the virtual machine.
2 Log in as root with password for the password.
3 Change the directory to: /usr/local/vkernel/scripts.
4 Run the changeIp.sh script. Follow the prompts to set the desired IP address and network
time server.
After you complete these steps, you can access vOPS Server Standard using the IP address and a
standard web browser.
Installing as an RHEVM Virtual Machine

vOPS Server Standard is delivered as a fully configured RHEVM virtual machine. It is installed
directly using the RHEVM.
To download and install vOPS Server Standard and the rhevm-image-uploader:
1 Download the vOPS for Red Hat virtual machine from the following location:
http://www.vkernel.com/downloads/all/
2 Save the Open Virtualization Format file (.ovf) to a Windows server or workstation.
3 Red Hat provides a utility named rhevm-image-uploader that allows you to upload and
import the appliance into an RHEV system. You must first install the rhevm-image-uploader,
which can be found on the Red Hat Network, at the following location:
http://rhn.redhat.com/errata/RHEA-2012-0118.html
4 Downloaded the rhevm-image-uploader and transfer it to the RHEVM server using a utility
such as WinSCP.
a Connect to the RHEVM server with an account you have previously created.
WinSCP opens to your account's home directory.
19
b Drag and drop the rhevm-image-uploader into the user directory on the right.
5 After the package has been copied to the RHEVM server, log onto the console as root,
change to the user directory of the account you used in the previous step, and run the
following command:
#yum locallinstall rhevm-image-uploader-3.0.0_0000-0.noarch.rpm
Substitute the current package number and version in place of 3.0.0_0000-0.

6 After the utility has been installed, edit the file /etc/rhevm/imageuploader.conf and set the
correct values for user, passwd, and rhevm.
Using Red Hat Enterprise Virtualization Manager Reports

The Red Hat Enterprise Virtualization Manager Reports functionality depends on the presence of
the history database, which is installed separately. Both the history database and the Red Hat
Enterprise Virtualization Manager Reports are optional components. They are not installed by
default when you install the Red Hat Enterprise Virtualization Manager.
Install Required Packages
Use yum to initiate installation of the rhevm-reports-dwh package, or the rhevm-reports

package if you also intend to install Red Hat Enterprise Virtualization Manager Reports. You must
run this command as the root user on the system hosting the Red Hat Enterprise Virtualization
Manager.
To install both the data warehouse package and the Red Hat Enterprise Virtualization Manager
Reports package, run the following command:
# yum install rhevm-reports
Confirm Package Installation
The required packages are downloaded. After all the packages have been downloaded they are
listed for review. You are prompted to confirm that you want to continue with the installation.
Confirm the operation. Yum installs the packages. Some further configuration is required before the
reports functionality can be used.
Configure History Database
You need to use the rhevm-dwh-setup command to configure the extract, transform, and load
(ETL) process, and the database scripts used to create and maintain a working history database.
20
You must run this command as the root user on the system hosting the Red Hat Enterprise
Virtualization Manager.
# rhevm-dwh-setup
For the history database installation to take effect it is necessary to restart the jbossas service. The
rhevm-dwh-setup command prompts you to confirm whether to stop the JBoss service. Type yes
and press Enter.
The jbossas service is stopped, and the rhevm_history database is created and configured.
Finally, the jbossas service is restarted.
After this process is complete, the Red Hat Enterprise Virtualization Manager is configured to log
information to the rhevm_history database for reporting purposes.
Selecting the RHEV Export Domain

The next step is to determine which export domain to use. The rhevm-image-uploader utility
needs the name of an RHEV export domain to upload the appliance to. You can use the RHEVM
admin interface to learn which export domains are currently available, or to configure a new one in
case no export domain is available yet.
After the utility is installed and configured, and you have identified the export domain, importing
the appliance is a three-step process.
To import the appliance:
1 Upload the appliance into the export domain with the rhevm-image-uploader utility. From
the RHEVM, run the command:

#rhevm-image-uploader -e <export domain> --name <name> upload <filename.ovf>
where <export domain> is the name of the export domain, and <name> is the VM that you
want to create from this appliance.
2 Create a VM from the appliance in the export domain.
a Open the RHEV admin interface and select the Storage tab.
b Locate and select the export domain from step 1, and click Import.
c Click OK on the confirmation dialog box. The import operation starts and runs in the
background.
3 Attach the VM to the rhevm network. At minimum, the appliance needs access to the rhevm
management network.
21
The rhevm-image-uploader utility does not create any network interfaces. Therefore, you
must manually create a network interface and add it to the rhevm network.
a In the RHEV admin interface, click the Virtual Machines tab.
b Locate and select the virtual machine created in step 2.
c Click Network Interfaces, then click New.
d Use the default values provided and click OK.
Power On and Initialize the Virtual Machine

Right-click on the Virtual Machine and click Run.

1 Right-click on the VM and select Console.
2 Log in as root with password for the password.
3 Change the directory to: /usr/local/vkernel/scripts and run the changeIp.sh script.
Follow the prompts to set the desired IP address and network time server.
Connecting to the RHEVM postgres Database remotely

Remote access to postgres SQL database needs to be configured.
To configure remote access from the console of the RHEVM server:
1 Allow remote host to connect:
#vim /var/lib/pgsql/data/pg_hba.conf
Add the remote host (or network) and set to trust level of access.
For example: hostallall192.168.16.0/24trust
2 Configure postgres to listen on all addresses:
#vim /var/lib/pgsql/data/postgres.conf
Edit the listen_address value, and remove the preceding #:

listen_address = '*'
3 Restart postgres.
#service postgres restart
Initial Configuration of vOPS Server Standard

To begin using vOPS Server Standard, open a standard web browser (Mozilla Firefox or Microsoft
Internet Explorer, with Adobe Flash 10 or later, are recommended) and type in the IP address of
the vOPS Server Standard virtual machine.
22
The page loads and request a username and password. The default username is vkernel and the
default password is vkernel.
License Agreement
Read and accept the license agreement in order to use vOPS Server Standard.
Connection Management
The environment connection screen appears and the Add Connection Configuration prompt opens.
You must have at least one VMware vCenter Connection, Click Finish Setup., or RHEV
Connection to complete the configuration.
VMware vCenter Connection

1 On the Add Connection dialog, click the vCenter tab.
2 Type the IP address or FQDN (fully-qualified domain name) and the credentials for the
system.
For vCenter , credentials should have Read-Only and Browse Datastore permissions for the
entire environment. If you are using the automated feature for implementing
recommendations, the appropriate permissions are required.
The credentials used for the vCenter where the vOPS Server Standard appliance is installed
must also have Virtual Machine State permissions in order for the appliance to be updated
automatically.
3 vOPS Server Standard can be accessed and used from within vCenter using a vKernel plug-
in. Select the Install VKernel vCenter Plug-in check box if you want the vKernel plug-in
installed in vCenter.
Note
If the virtual infrastructure client is open during this process, it must be closed and
reopened in order for the vKernel plug-in to become visible.
23
4 The vOPS Server Standard Performance Analyzer uses vCenter alarms for real-time
monitoring of the state of the virtual environment.

Note
Six specific vKernel utilization alarms must be installed in vCenter in order to provide the
real-time functionality. The vCenter credentials must have Alarm permissions in order to
create the alarms. Leave the Add VKernel Alarms to vCenter box checked if you want
to use the real-time analysis capability of Performance Analyzer. If you leave the box
checked, the alarms are installed automatically.
5 After a connection is established, the overall configuration can be completed.

6 Click Finish Setup.
Microsoft System Center Connection

1 Select the System Center tab on the Add Connection dialog.
2 To establish the Microsoft Hyper-V connection, the Hyper-V Collector must be installed, as
described in Installing and Configuring the vKernel Hyper-V Collector on page 33.
After the Hyper-V Collector is installed and configured, it appears in the connection list and
the overall configuration can be completed.
24
3 Click Proceed.
The appliance collects all the required virtual environment information. Depending on the
size of the virtual environment, this can take anywhere from fifteen minutes to several hours.
RHEV Connection
1 On the Add Connection dialog, click the RHEV tab.
2 Configure the Red Hat connection with the IP address or FQDN of the RHEVM server.
Provide the credentials for an account with SuperUser rights to the RHEVM application.
3 Click Add.
VMware vCloud Connection

1 On the Add Connection dialog, click the VMware vCloud tab.
25
2 Type the IP address or FQDN (fully-qualified domain name) and the credentials for the
system.
For VMware vCloud, credentials should have Read-Only and Browse Datastore permissions
for the entire environment. If you are using the automated feature for implementing
recommendations, the appropriate permissions are required.
The credentials used for the VMware vCloud where the vOPS Server Standard appliance is
installed must also have Virtual Machine State permissions in order for the appliance to be
updated automatically.
3 vOPS Server Standard can be accessed and used from within VMware vCloud using a
vKernel plug-in. Select the Install VKernel vCenter Plug-in check box if you want the
vKernel plug-in installed in VMware vCloud.
Note
If the virtual infrastructure client is open during this process, it must be closed and
reopened in order for the vKernel plug-in to become visible.
4 The vOPS Server Standard Performance Analyzer uses vCloud alarms for real-time
monitoring of the state of the virtual environment.

Note
Six specific vKernel utilization alarms must be installed in vCloud in order to provide the
real-time functionality. The vCenter credentials must have Alarm permissions in order to
create the alarms. Leave the Add VKernel Alarms to vCenter box checked if you want
to use the real-time analysis capability of Performance Analyzer. If you leave the box
checked, the alarms are installed automatically.
5 After a connection is established, the overall configuration can be completed.

6 Click Finish Setup.
Initial Data Collection

After it is configured, the appliance collects all of the required virtual environment information.
26
Click OK and log in to vOPS Server Standard.
Logging in to vOPS Server Standard

To begin using vOPS Server Standard, open a standard browser (Mozilla Firefox, Microsoft
Internet Explorer, or Chrome, with Adobe Flash 10 or later) and type in the IP address of the vOPS
Server Standard virtual machine. Once the website loads, a username and password is requested.
The default username is vkernel and the default password is vkernel.

If the appliance has recently been configured, it may still be collecting the required virtual
environment information. Depending on the size of the virtual environment, this can take
anywhere from fifteen minutes to several hours.
27
After the initial collection is complete, the Get Started dashboard appears.
Managing Licenses
When you click any top level tab other than Dashboard, the Request a License dialog box opens
and prompts you to license the module you are trying to access.
Note
A 30-day free trial of the complete vOPS Server Standard is available.
Select either Trial License or Purchased License and click Next.

For more information, see either Activating a Trial License or Activating a Purchased License.
28
Activating a Trial License

After the initial configuration, when you click any top level tab other than Dashboard, the Request
a License dialog box opens and prompts you to license the module you are trying to access.
To activate a trial license:
1 Click a top level tab other than Dashboard.
The Request a License dialog box opens.
2 Select Trial License and click Next.
The Request a Trial License dialog box opens.
3 Type the required information, and click Request the License.
Your trial license is processed and installed immediately.
29
4 Click Finish to begin using vOPS Server Standard.
To allocate socket licenses, see Allocating Socket Licenses on page 31.
Activating a Purchased License

After the initial configuration, when you click any top level tab other than Dashboard, the Request
a License dialog box opens and prompts you to license the module you are trying to access.
To activate a purchased license:
1 Click a top level tab other than Dashboard.
2 Select Purchased License for vOPS Server Standard or Basic and click Next.
The Customer ID dialog box opens.
30
3 Type the customer ID in the box and click Next.
The License Socket Count dialog box opens.
Review the information provided.

4 If necessary, adjust the value in the Total Sockets Required for This vOPS Server box.
For example, if you have purchased 300 sockets, but the vOPS Server you are installing the
license on only requires 150 sockets, type 150 in the box.
5 Click Request the License to submit the licensing request.
A message box opens while the request is processed, then the results of the license request
are displayed.
31
6 Click Finish.
To allocate socket licenses, see Allocating Socket Licenses on page 31.
Activating a Purchased License after installing a Trial License

Alternately, if you have been using a trial license and want to add a purchased license, you can do
so from the Settings > License tab.
To install a purchased license:
1 On the Settings > License tab, click Request A License.
2 Follow step 2 through step 6 of the procedure To activate a purchased license: on page 29.
Allocating Socket Licenses

To allocate the license sockets:
1 Click the gear icon
at the top-right corner of the browser interface to access the settings.
2 Click the License tab.

3 Click License Assignment.
The vOPS Server License Agreement dialog box opens.
4 Select the host or socket from the Unlicensed Hosts/Sockets list on the left.

5 Click the right arrow

Note
to move them to the Licensed Hosts/Sockets list on the right.
The text that indicates the number of host and socket licenses used updates
automatically.
6 When finished, click OK.
The License tab updates to display the licensed hosts and sockets.
Installing a License Received by E-mail

If you have requested and received a license by e-mail, you can install that license through the
Settings > License tab.
To install an e-mailed license:
1 On the Settings > License tab, click Install License received via E-mail.
The Manual Activation dialog box opens.
32
33
2 Click Browse to navigate to and select the license file you received by e-mail.
Optional if you want to reset the list of assigned hosts when you import the license, select
the Reset assigned host list after activation check box.
3 Click Activate.
Migrating Licenses from another Appliance

If you are upgrading from a previous version of vOPS Server Standard, you can migrate an
existing license to your new appliance.
To migrate a licence:
1 On the Settings > License tab, click Migrate License from another Appliance.
The Migrating License From Previous Version dialog box opens.
2 Provide the required information from the previous version of the appliance.
Optional if you want to update the e-mail address that licenses are sent to, select the
Change the E-mail the licenses will be sent to check box, and type a new e-mail address in
the box.
3 Click Next.
Deactivating All Licenses

To deactivate all commercial licenses that have been installed on the vOPS Server Standard
appliance, click Deactivate all Licenses. A message box opens, prompting you to confirm the
action.
Installing and Configuring the vKernel Hyper-V Collector

To install the vKernel Hyper-V Collector:
1 Select the Microsoft Windows server where the vKernel Hyper-V Collector is to be installed.
2 Locate the .msi file from the Hyper-V Collector folder extracted from the vOPS Server
Standard .exe.
3 Copy the .msi file to the selected server.

4 Double-click on the .msi file to install the vKernel Hyper-V Collector.
To configure the vKernel Hyper-V Collector:

1 After installing the vKernel Hyper-V Collector, navigate to All Programs > VKernel
Hyper-V Collector and start the collector.

The VKernel Hyper-V Collector dialog box opens, with the Service tab selected.
The Service tab shows the status of the vKernel Hyper-V Collector service and the
credentials for the service.
2 Click the Database tab.
34
35
The Database tab shows the vOPS Server Standard database connection information.
a Select the SQL Server Type.
b In the PostgreSQL Server Configuration area, type the appropriate server information and
credentials.
If you are using the Embedded PostgreSQL database, the Server address should be the
address of the vOPS Server Standard virtual machine. For the embedded PostgreSQL
database, the account and password are postgres and postgres.
3 Click Apply.
4 Click the Connections tab.
36
The Connections tab specifies the connection to the Systems Center Operations Manager.
If the connection parameters were specified properly, a new connection appears on the
connection list. The vKernel Hyper-V Collector service starts immediately.
5 Review the connection information and edit if necessary.
6 Click Close.
System Center Integration

The VKernel Hyper-V Collector is required in order to propagate the vOperations alarms into the
Microsoft System Center Virtual Machine Manager. For more information, see Installing as a
Microsoft Hyper-V Virtual Machine on page 15.
2
Dashboard
The dashboard provides an overall summary of the status of the virtual environment. The
Dashboard tab provides five default dashboard views: Get Started, Alarms and Bottlenecks,
Capacity Efficiency and Availability, Infrastructure Overview, and vScope Dashboard, as well as
the ability to add additional custom dashboards, hide the default views, and to re-order dashboard
tabs.
Configurable Dashboards and Dashboard Management

New configurable dashboards can be created and customized with a variety of reports. For
example, the Get Started dashboard is a configurable dashboard that can be easily modified to suit
the user.

Chapter 2Dashboard
To create a new dashboard:

1 Click the plus sign tab
to the right of the other dashboard tabs. The dashboard is

created and opened in editing mode.
2 Click Add Report to add a report to the new dashboard.
3 Select the report you want to add and click OK. The report is added and you can then
position and size it for your particular requirements.
4 Individual reports can be configured (for example, to set a custom timeframe, or to exclude
certain columns) by clicking the Configure Gear icon at the top right corner of the specific
chart or table.

Chapter 2Dashboard
5 You can add multiple reports to a single dashboard.

6 Change the name of the dashboard using the text box in the toolbar.
7 Once you have completed your new dashboard, click Done to save it.
You can edit or delete an existing dashboard by clicking on the appropriate toolbar button. You can
also reorder dashboard tabs by simply dragging them to the right or left.
If you want to provide access to any configurable dashboard directly, without having to access the
rest of the Foglight UI, use the URL option. Select the access permissions to control access to the
URL. The URL can then be copied and shared as appropriate.

Chapter 2Dashboard
Get Started Dashboard

The Get Started dashboard provides an overall environment summary as well as a summary of
things to do for the various aspects of the environment.
Note
The Getting Started dashboard does not react to selections in the navigation tree. It always
shows the information for the entire environment.
Alarms and Bottlenecks

This view highlights the performance related status of the virtual environment.
Capacity Efficiency and Availability

This view highlights the efficiency of resource utilization and the availability of resources for
additional growth.

Chapter 2Dashboard
Infrastructure Overview
This view highlights the historical virtual machine trends.

Chapter 2Dashboard
vScope Dashboards
vScope provides an environment-wide, cross-hypervisor visualization of the status of your
infrastructure from the perspectives of performance, capacity, efficiency and cost. These
dashboards excel at providing high-level views of your environment where a list may not give an
accurate portrayal of its overall health.
Double-clicking any item on a vScope dashboard takes you to a drill-down view with more
detailed information on the selected item. Click Close to return to the main view.
Note
Unlike most views in Foglight, vScope dashboards cannot be exported as PDF. They can,
however, still be exported as CSV/XML.
3
Performance Analyzer
Monitor, diagnose, and resolve real-time performance problems using the vOPS Server Standard
Performance Analyzer. The application analyzes real-time alerts and system metrics to identify
root cause, impact, and resolution of real-time performance problems.
The functionality of the Performance Analyzer application is divided into six major areas: Real
Time Alarms, Trend Alarms, Hypervisor Alarms, Current Bottlenecks, Datastore Performance,
and Performance vScope.
Note
Each view within the Performance Analyzer includes only the objects selected in the navigation
tree.
Real Time Alarms

The Performance Analyzer uses real-time alarms that it sets automatically in vCenter and System
Center, together with a rich set of performance metrics, to identify, analyze, and resolve real-time
performance problems.
The Real Time Alarms tab includes five different views to provide insight into identified
performance issues: Root Cause, Actions History, Alarms By Resource, Alarm History, and Alarm
Configuration.
44
Chapter 3Performance Analyzer
Alarms Set in vCenter

Performance Analyzer automatically sets the following alarms in each vCenter based on the
VMware-specific threshold settings and duration times in vOPS Server Settings > Thresholds:
Host CPU Utilization
Host Memory Utilization
Virtual Machine CPU Utilization
Virtual Machine CPU Ready
Virtual Machine Memory Utilization
Virtual Machine Disk Latency
These alarms are set at the vCenter root level and apply to all objects in the virtual environment.
The alarm names all begin with VKernel for easy identification.
The alarm state of all objects in the virtual environment is clearly indicated in the vOPS Server
Standard navigation tree. Alarm states roll up from child to parent objects in the tree, so that you
are immediately aware of any problems regardless of the state of the navigation tree.
45
Note
Some alarms may not be available in older versions of vCenter. If they are not available, they do
not appear and are not used in Performance Analyzer analysis.
Disabling these alarms causes some real-time functionality to be lost, but Performance Analyzer
continues to use other metrics that it collects to identify and diagnose performance issues.
Alarms Set in System Center

Performance Analyzer automatically sets the following alarms in each SCOM installation:
Virtual Machine CPU Utilization
Virtual Machine Memory Utilization
Virtual Machine Disk Latency
Host CPU Utilization
Host Memory Utilization
These alarms are included in the Quest PRO Management Pack. While the alarms themselves may
not be modified, the Hyper-V-specific threshold settings and duration times in Settings >
Thresholds allow their values to be overridden.
Disabling these alarms causes some real-time functionality to be lost, but Performance Analyzer
continues to use other metrics that it collects to identify and diagnose performance issues.
Root Cause
The Root Cause view of Real Time Alarms identifies all alarms that require action to resolve a
current problem. It does not contain alarms that result from a root cause alarm.
Alarms are listed in a table that includes the virtual object, problem, problem duration, and
recommendation. Where appropriate, a button in the Action column provides an immediate option
to remediate the problem.
46
Double-click on a particular alarm in the Root Cause view to open the Impact Analysis view for
the specific alarm.
Impact Analysis
In addition to the problem, problem duration, and recommendation provided by the Root Cause
View, the Impact Analysis view provides all of the information necessary to fully understand the
problem as well as a possible resolution.
Actions History
The Actions History view shows all of the Root Cause remediations performed by the user.
Alarms by Resource
The Alarms By Resource view shows all currently open alarms and the value of the pertinent
resource metric for all objects selected in the navigation tree.
47
Alarm History
All alarms, both current and resolved, are included in the Alarm History view. As with the other
views, any of the columns can be sorted. This allows a view of all alarms for a particular object or
of a particular type.
Alarm Configuration
This view shows all of the real-time alarms that are currently set. You can add, edit, or delete
alarms in this view.
While the real-time alarms set in vCenter and System Center are always present, these alarms can
be limited to a specific object type (such as a host or virtual machine).
To edit or delete an alarm:
1 Select the specific alarm in the table.
2 Click the appropriate button in the far right column.
48
To add a new alarm.

1 Click New Alarm.
2 To limit real-time alarms to particular objects, folders, or business views, click the Scope tab
and set the scope for the particular alarm.
49
3 To configure notifications, click the Notifications tab.
Notifications of active real-time alarms can be emailed to selected users, sent as traps to an
existing management system, sent as alerts to the System Center Operations Manager /
System Center Virtual Machine Manager, or added to a selected RSS Feed.
4 Click Add.
Trend Alarms
Trend Alarms are used to pinpoint extraordinary changes in resource utilization. You can set a
trend alarm to generate an alarm and notify the user if the utilization of a particular resource
increases (or decreases) significantly in a relatively short period of time.
Alarm History
This view shows the history of all alarms with resolution dates (if the alarms were resolved).
50
Alarm Configuration
This view shows all of the trend alarms that are currently set. You can add, edit, or delete alarms in
this view.
There are two types of trend alarms: trend alarms for virtual objects and trend alarms for
datastores.
Trend alarms can be configured to alert on a significant change in resource utilization, when
resource utilization reaches the warning or alarm threshold, or on an accelerated growth in
resource utilization.
To edit or delete an alarm, select the specific alarm in the table and click the appropriate button.
To add a new alarm, click New Alarm.
51
To set an alarm for a change in resource utilization, select the % Change option and set the period
within which the change must occur.
To set an alarm for a resource threshold, select Threshold, then type the threshold and set the time
period during which the average utilization must meet or exceed the threshold.
52
To set an alarm for accelerated growth, select Accelerated Growth, then set the period to use for
the recent trend and specify the change in time remaining before the resource is exhausted.
In addition to trend alarms for virtual objects, you can also set threshold and accelerated growth
trend alarms for datastores.
53
The trend alarms for virtual objects can be limited to particular objects, folders or business views
by setting the scope for the particular alarm. The trend alarms for datastores can be limited to
particular datastore clusters or datastores.
54
Notifications of the active trend alarms can be emailed to selected users, sent as traps to an existing
management system, sent as alerts to a System Center Virtual Machine Manager, or added to a
selected RSS Feed.
Default Trend Alarms

Several trend alarms are pre-set by default when vOPS Server Standard is installed. You can delete
or modify any of them, as well as add your own. These default alarms are set on VMs or hosts
across your entire infrastructure for the following conditions:
Average CPU utilization doubles over the past week (Host, VM)
Average memory utilization doubles over the past week (Host, VM)
Average disk throughput doubles over the past week (Host, VM)
Average CPU Ready doubles over past day (VM)
Average memory swapped doubles over the past day (Host, VM)
Average memory ballooned doubles over the past day (VM)
Average disk latency doubles over the past day (Host, VM)
Hypervisor Alarms
The Hypervisor Alarms tab shows all monitored vCenter and System Center alarms, not just the
ones specifically set by Performance Analyzer.
Note
Only the vOPS-installed alarms are monitored within System Center.
The Hypervisor Alarms tab provides two different views: Current Alarms and Alarm History.
Current Alarms
This view lists the currently active monitored vCenter and System Center alarms.
55
Alarm History
This view lists all of the monitored vCenter and System Center alarms, both current and resolved.
Current Bottlenecks
The Current Bottlenecks views identify the objects that currently have capacity bottlenecks.
Six different views are available for analysis and resolution of bottleneck problems: Summary,
CPU, Memory, Storage, Throughput, and Latency.
Summary
The Summary view is an overview of the current bottlenecks for all key resources. The average
utilization over the evaluation period (typically the last 24 hours) of the key resource metrics is
shown. The direction of change of the average utilization is shown by arrow icons (up, down or
constant). Other significant metric values (for example, peak, swapping, ballooning) are indicated
by a triangle icon.
56
Double-click a particular alarm in any of the views to open the Root Cause view for the specific
alarm.
Root Cause
This view provides a detailed analysis of the specific bottleneck with specific recommendations
and supporting information.
57
CPU
In addition to the average CPU utilization, the CPU view also displays the other metrics pertinent
to CPU analysis.
58
Memory
In addition to the average memory utilization, the Memory view also displays the other metrics
pertinent to memory analysis.
Storage
In addition to the average storage utilization, the Storage view also displays the average utilization
of the individual partitions within the storage.

Throughput
In addition to the average throughput rate, the Throughput view also displays the other metrics
pertinent to throughput analysis for each individual datastore on the object.
Latency
In addition to the average latency, the Latency view also displays the other metrics pertinent to
latency analysis for each individual datastore on the object.
59
60
Datastore Performance
The Datastore Performance view provides a summary by storage resource of all of the key
VMware datastore and datastore cluster and Hyper-V disk performance metrics.
Performance vScope
infrastructure. The Performance vScope indicates which VMs or hosts are either experiencing or
on the verge of experiencing performance problems. Two different views are provided in the form
of heat maps, one from a VM-focused perspective, and one from a host-focused perspective.
VM Performance View
In the VM Performance view, each colored box represents a single VM, grouped by host, cluster
and data center. The color of each VM indicates the severity of identified performance issues. Red
indicates serious performance problems, while yellow identifies less serious or imminent
performance issues. VMs with no identified issues are green.
To see what specific issues are impacting the performance health of the VM, hover your cursor
over the VM box. A popup opens, listing the details. Double-click on the VM box to drill down to
a detailed view for the selected VM.
Host Performance View

In the Host Performance view, each colored box represents a single host, again grouped by cluster
and data center. The colors of the host boxes have the same meaning as those of the VMs.
To see what specific issues are impacting the performance health of the host, hover your cursor
over the host box. A popup opens, listing the details. Double-click on the host box to drill down to
a detailed view for the selected host.

61
4
Capacity Manager
Forecast and manage virtual environment capacity using the vOPS Server Standard Capacity
Manager. The application uses predictive analysis of system metrics to identify potential future
bottlenecks and models available VM capacity across server and storage resources.
The functionality of the Capacity Manager application is divided into five major areas:
Availability, Current Bottlenecks, Future Bottlenecks, Predictive Alarms, and Capacity vScope.
Availability
The Capacity Manager Availability view identify the availability of the key resources of the virtual
environment.
Capacity Availability
The Capacity Availability view highlights the number of additional virtual machines that can be
added to the clusters, hosts, and resource pools.
CPU, memory, storage and throughput are each analyzed for available capacity. High availability
(HA) and other configuration parameters, as well as reservations are fully considered in the
analysis to ensure the accuracy of the result.
If reservations for future virtual machines have been set, the availability calculation takes the
reservations into account when calculating the number of additional virtual machines that can be
added. The reservations can be excluded from the availability calculation by clearing the Include
Reservations check box.
The assumptions used in making the availability calculation can be modified using the Calculator.
The calculator has two modes of operation: Basic Analysis and Advanced What If Analysis.
In Basic Analysis mode, the availability calculation can be based on current actual utilization of
the virtual machines in the infrastructure or it can be based on the predicted utilization of the
virtual machines at a point in the future.
The availability calculation in the Basic Analysis mode can be based on the following:
The maximum actual utilization of the virtual machines on HA enabled clusters and the
average actual utilization of the virtual machines on individual hosts or clusters that do not
have HA enabled.
63
Chapter 4Capacity Manager
The maximum actual utilization of all virtual machines.

The average actual utilization of all virtual machines.
A custom virtual machine model with specific values for CPU, memory, storage, and
throughput.
Tip
The custom model can be based on an actual virtual machine in the infrastructure. It can
also be named and saved for future use.
In the Advanced What If Analysis, multiple virtual machines of differing sizes can be temporarily
placed in the infrastructure in order to measure the effect of those virtual machines on overall
availability.
Important Placing a virtual machine does not actually create a virtual machine in the infrastructure; it simply
modifies the results of the availability in the Advanced What If Analysis.
The availability calculation in the Advanced What If Analysis mode is based on a custom virtual
machine model with specific values for CPU, memory, storage, and throughput. The custom model
can be based on an actual virtual machine in the infrastructure. It can also be named and saved for
future use.
64
To place a temporary virtual machine in the infrastructure, in the Calculator pane, click Place
VMs.
The quantity, name, container and datastore, disk or datastore cluster for the virtual machine are
required. The values for each of the resources are initialized with the values selected in the
Calculator but can be modified.
65
Click Place to set aside the required resources for the temporary virtual machine(s). The placed
virtual machines are listed in the Calculator pane.
You can place additional virtual machines of varying resource utilization.
The placed virtual machines can be edited, deleted, or converted to a reservation for deployment.
Click Reservation to reserve the virtual machines.
66
Type the Reservation ID, select the deployment date, and click Save. The placed virtual machine is
converted to a reservation and appears in the Reserved VMs column of the Capacity Availability
view. It is also removed as a placed virtual machine.
67
Tip
To learn more about how to reserve capacity for future VM Deployments in vOPS, watch our
learning video. See http://www.vkernel.com/support/learn
VM Reservations
All of the current virtual machine reservations are shown in the VM Reservations view.
If reservations for future virtual machines have been set, the availability calculation in Capacity
Availability takes the reservations into account when calculating the number of additional virtual
machines that can be added. The reservations can be excluded from the availability calculation by
clearing the Include Reservations check box on the Capacity Availability tab.
You can add, edit, delete, or deploy new reservations.

In order to automatically deploy a reservation, a deployment template must be selected. The

allocation values for the template can also be changed for a specific deployment.
68
69
When it is time for deployment, select Deploy Now and click Deploy. The deployment can then be
performed immediately or scheduled.
If the Reporting and Chargeback application is licensed, you can use Match Reservations to check
for deployment of the reserved virtual machine and to delete the reservation.
70
For more information, see Reporting and Chargeback on page 109.
Future Requirements
The Future Requirements tab uses short- and long-term trending analysis to predict resource
requirements at a selected future date.
Select a future date for which future resource requirements are needed. There is no limit on how
far out the projection can be made. Keep in mind, however, that the accuracy of the prediction
degrades with time.
The required resources are computed for the selected date using two different projections, one
based on trending usage over the past thirty days, and one based on longer-term (six month)
trending. In addition, for each of the two projections, the report indicates the number of days
before capacity utilization of any resource will reach warning or alarm thresholds, and indicates
which resource is the primary constraint.
Charts showing usage versus capacity over the past six months are provided to aid in interpreting
the projected results.
71
Datastore Statistics
The current allocation and utilization status of all VMware datastores and datastore clusters and
Hyper-V disks are shown in the Datastore Statistics view.
72
Top Consumers
The Top Consumers view displays the individual resource usage of each virtual machine. By
sorting on a particular resource, you can identify the virtual machines that are using the greatest (or
least) amount of the resource.
73
Current Bottlenecks
The Current Bottlenecks views identify the objects that currently have capacity bottlenecks.
The Current Bottlenecks tab provides six different views for analysis and resolution of bottleneck
problems: Summary, CPU, Memory, Storage, Throughput, and Latency.
Summary
The Summary is an overview of the current bottlenecks for all key resources. The average
utilization over the evaluation period (typically the last 24 hours) of the key resource metrics is
shown. The direction of change of the average utilization is indicated by arrow icons (up, down or
constant). Other significant metric values (for example, peak, swapping, ballooning) are indicated
by triangle icons.
Double-click on a particular alarm in any of the views to open the Root Cause view for the specific
alarm.
Root Cause
The Root Cause view shows a detailed analysis of the specific bottleneck with specific
recommendations and supporting information.
74
CPU
In addition to the average CPU utilization, the CPU view also displays the other metrics pertinent
to CPU analysis.
75
Memory
In addition to the average memory utilization, the Memory view also displays the other metrics
pertinent to memory analysis.
Storage
In addition to the average storage utilization, the Storage view also displays the average utilization
of the individual partitions within the storage.

Throughput
In addition to the average throughput rate, the Throughput view also displays the other metrics
pertinent to throughput analysis for each individual datastore on the object.
76
77
Latency
In addition to the average latency, the Latency view also displays the other metrics pertinent to
latency analysis for each individual datastore on the object.
Future Bottlenecks
The Future Bottlenecks view analyzes the historical utilization of resources to proactively predict
future capacity bottlenecks. The calculations require a minimum of at least seven days of historical
data and preferably thirty days.
Overview
The Overview view of Future Bottlenecks identifies which resources will become problematic in
the future. Double-click on a CPU or Memory constraint to open the Root Cause view for a
particular object.

Root Cause
The Root Cause view provides a detailed analysis of the specific future CPU or memory
bottleneck with specific recommendations and supporting information.
Predictive Alarms
Predictive Alarms are used to identify future resource needs within the virtual environment.
Active Alarms
The Active Alarms view of Predictive Alarms shows all of currently active alarms.
78
79
Alarm Configuration
The Alarm Configuration view shows all of the predictive alarms that are currently set.
To edit or delete an alarm, select the specific alarm in the table and the click the appropriate button.
Click New Alarm to add a new alarm.
80
Predictive alarms can be limited to particular objects, folders or business views by setting the
scope for a particular alarm on the Scope tab.
Notifications of active predictive alarms can be emailed to selected users, sent as traps to an
existing management system, sent as alerts to the System Center, or added to a selected RSS Feed.
You can configure notifications on the Notifications tab.
81
Capacity vScope
infrastructure. The Capacity vScope indicates the capacity state of all hosts and clusters in the
form of a heat map. Each colored box represents a single host. Hosts are further grouped by cluster
and data center.
The color of each host indicates its capacity-related health. Hosts with no factors negatively
impacting their capacity are green, hosts with some minor factors or future/negatively trending
factors are yellow, and hosts with significant factors are red.
To see what specific issues are impacting the capacity health of the host, hover your cursor over
the host box. A popup lists the details. Double-click on the host box to drill down to a detailed
view for the selected host.

82
5
Optimizer
Optimize resource utilization and eliminate resource waste using the vOPS Server Standard
Optimizer. The application analyzes actual utilization and performance metrics to properly size
virtual machine allocations and reclaim unused resources.
The functionality of the Optimizer application is divided into three major areas: Rightsizer,
Wastefinder, and the Efficiency vScope.
Rightsizer
The Optimizer Rightsizer identifies recommended configuration changes for the environment.
Summary
The Summary view of the Rightsizer is an overall summary of all of the recommended
configuration changes for the environment. It includes the value of the resource savings.
84
Chapter 5Optimizer
The CPU and Memory changes can be implemented automatically or scheduled for
implementation at a particular time in the future (for example, during a maintenance window).
Click Automate to implement the recommendations.
CPU
The CPU view displays additional information about the CPU recommendations and allows you to
implement the recommendations immediately.
85
Chapter 5Optimizer
Memory
The Memory view displays additional information about the memory recommendations and
allows you to implement the recommendations immediately.
Storage
The Storage view displays additional information about the storage recommendations including
the recommendations for individual drives within the virtual machine.
Rightsizer Constraints
Rightsizer recommendations are based on actual peak and average utilization values and are
designed to set allocations appropriately to the actual needs of the VMs. However, vendor
recommendations or IT policies may dictate limitations on minimum or maximum allocations for
86
Chapter 5Optimizer
numbers of vCPUs, or allocated memory or storage. Rightsizer constraints allow you to impose
these limitations within vOPS Server.
To set Rightsizer constraints, you first need to create a Configuration Group containing the VMs to
which the constraints apply. You can create and manage Configuration Groups from the Settings >
Configuration Groups menu, or you can create them directly within the Rightsizer Constraints
view.
Configuration Groups are similar to Business Views. You can create free-form groups and
manually add VMs or VM containers (for example, resource pools, clusters, folders, or business
views) to them, or you can create smart configuration groups that automatically select VMs and
VM containers based on filters that you set. For more information, see Smart Business Views on
page 126.
To create a new Configuration Group (in either traditional free-form or smart style):
1 Right-click All Configuration Groups and create it in the same way you would a Business
View (see page 125 for details).

2 Drag the configuration group into Rightsizer Groups (in the left pane) to edit its constraints.
3 Select the configuration group.
4 Set the minimum or maximum values for each type of resource for which Rightsizer
recommendations are generated. You can also turn off recommendations for particular
resources entirely.
For example: if you do not want Rightsizer to recommend reducing memory below 4 GB for
any VMs in your SQL cluster, create a Configuration Group containing your SQL cluster and
set the Minimum constraint for memory to 4 GB. This causes Rightsizer to modify its
recommendations to meet the limitation.
Rightsizer Constraint Conflicts

It is possible for a VM to be a member of more than one configuration group. In this case,
constraint resolution rules must be applied to determine the appropriate constraint to apply. If
recommendations are disabled for a VM in any configuration group, then recommendations are
suppressed. For minimum and maximum constraints, the default behavior is to always take the
largest value found. This can be changed by clicking Conflict Resolution Rules at the top left
(below the Summary tab) and changing the default behavior.
87
Chapter 5Optimizer
Wastefinder
The Optimizer Wastefinder identifies wasted resources within the environment. Some items, such
as Abandoned VM Images and Snapshots, can be deleted automatically.
Abandoned VM Images
The Abandoned VM Images view of Wastefinder shows the virtual machine images in storage that
are not part of the virtual environment inventory. This typically occurs when a virtual machine that
is no longer needed is removed from inventory instead of being deleted.
Click the Options button on the toolbar to view and modify the settings used to identify
abandoned VM images.
88
Chapter 5Optimizer
Powered Off VMs

Virtual machines that have been powered off for an extended period of time are highlighted in the
Powered Off VMs view.
Unused Template Images

The Unused Template Images view highlights templates that have not been accessed in an
extended period of time.
Click Options on the toolbar to view and modify the settings used to identify unused template
images.
Note
Identification of unused templates is supported only for VMware environments. Hyper-V support
for this feature will be available in the next vOPS release.
89
Chapter 5Optimizer
Click Options on the toolbar to view and modify the settings used to identify these snapshots.
Potential Zombie VMs

Potential Zombie VMs are virtual machines that are powered on but appear to be unused. These
virtual machines are identified by analyzing CPU, memory, network, and disk throughput for very
consistent usage over an extended period of time.
Click Options on the toolbar to view and modify the settings used to identify zombie VMs.
90
Chapter 5Optimizer
Efficiency vScope
infrastructure. The Efficiency vScope indicates the efficiency of resource allocation or usage from
either a VM-focused perspective or a datastore-focused perspective in the form of a heat map.
Double-click on any item on the heat map to open a more detailed drill-down view for that item.
VM Efficiency View
In the VM Efficiency view, each colored box represents a single VM, grouped by host, cluster, and
data center. The color of each VM indicates the degree to which it inefficiently uses resources.
Severely oversized VMs are red, moderately oversized VMs, and suspected zombies are yellow.
VMs with no identified issues are green.
To see what specific issues are impacting the efficiency health of the VM, hover your cursor over
the VM box to open a popup with detailed information. Double-click the VM box to open a drilldown detailed view for the selected VM.
Datastore Efficiency View

In the Datastore Efficiency view, each colored box represents a single datastore, grouped by
hypervisor environment. The color of each datastore indicates the extent of wasted storage
identified, where red means very extensive waste, yellow is moderate waste, and green identifies
datastores with little or no wasted storage.
To see what specific issues are impacting the efficiency health of the host, hover your cursor over
the host box to open a popup with detailed information. Double-click the host box to open a drilldown detailed view for the selected host.

Chapter 5Optimizer
91
6
Change Analyzer
Track changes in your virtual environment and understand their potential impact on performance
and capacity using the vOPS Server Standard Change Analyzer. This module captures and reports
on changes to VMs, hosts, clusters, datastores, and disks, and assesses the potential impact on your
environment. Change Analyzer also lets you compare VMs to a gold standard VM or template
and alerts you when changes cause their configurations to drift from the standard.
The functionality of the Change Analyzer application is divided into five major areas: Change
Summary, Infrastructure History, VM Comparison, Change Assessment, and Change and
Comparison Alarms.
Each view within the Change Analyzer includes only the objects selected in the navigation tree.
Common Features in Change Analyzer

Risk Definitions
Common to all the Change Analyzer functions is an assessment of the potential risk that a change
in the environment or a deviation from a standard configuration might impact the performance of
VMs or potentially create or worsen performance bottlenecks.
The risk assessment is based on the type of change or deviation and, in certain cases, on the
direction of the change. For example, creating a new datacenter may be an interesting event, but it
should not show up as high-risk. On the other hand, setting any sort of memory limit on a VM
potentially creates severe performance issues and therefore the impact risk is set to high.
93
Chapter 6Change Analyzer
Allocating more memory to a VM is low-risk, but decreasing the memory allocation can
potentially cause performance problems and therefore defaults to medium-risk.
Click Risk Definitions on any Change Analyzer screen to view the current settings. In some cases
corporate policy or your own experience with your environment may dictate different risk impact
settings for certain events than the default. You can change these settings in the Risk Definitions
dialog.
Filters
Every report in Change Analyzer can be sorted by clicking on the appropriate column header, or
filtered using the standard filter mechanisms in the report-level toolbar just above the report.
There are three common filters:
Name Filter type a name to filter the report by the name of the VM or object.
User Filter type a user name to filter the report by the name of the user who made the
change.
Type Filter this filter offers a set of check boxes that let you select the change or deviation
types to display. You can filter by the type of object on which the change occurred, the type
of change, or the impact risk level.
94
Change Summary
The Change Summary view shows net changes that occurred to VMs, hosts, clusters, and resource
pools within the selected environment over a specified period of time. The time period is set at the
top right area of the report. You can select a standard period, such as the last week or month, or a
custom period.
Each row of the report shows the VM, the total number of differences in the configuration of that
VM between the beginning and end of the period, the total number of changes that occurred to
cause those changes, the highest impact risk of any change that occurred to that VM over the
specified period, and the date when the last change occurred. Entries are ordered by the Max
Impact Risk column by default.
Each row of the report can be expanded to display the specific differences and the degree of
change.
95
Note that the number of differences may not be the same as the number of changes.
To see a detailed list of all the changes that make up the net difference reported here, right-click on
the report row to go directly to the Infrastructure History report for the selected object.
Infrastructure History
The Infrastructure History view lists all changes that occurred to VMs, resource pools, hosts,
clusters, disks, datastores, and data centers within the selected environment over a specified period
of time. The time period is set at the top right area of the report. You can select a standard period
such, as the last week or month, or a custom period.
Each row of the report shows the potential risk of performance impact, the time of the change, the
object on which the change occurred, the change type and brief description, before and after values
when available, the user who made the change, and the full path to the changed object. Entries are
ordered by the time the change occurred by default.
At the bottom of the screen a graph shows the numbers of changes that occurred within each subperiod of the selected time interval, allowing easy identification of periods in which unusual
numbers of changes occurred. Hovering your cursor over a bar in the chart causes a tooltip to
appear showing the total counts of changes at each risk level.

Right-click on any row of the report to access additional actions.
You can quickly pivot to other relevant reports within the same time period, such as:
All changes to the same object
All changes of the same change type
All changes made by this user
All changes with the same impact risk
Reverting Changes
96
97
Resource Graphs include an overlay showing what changes occurred during the interval that is
being charted. A green, yellow, or red star is shown along the top of the chart whenever there are
events that occurred during that time period. The color of the star reflects the maximum impact
risk level of the changes that occurred.
Hovering over the star brings up a summary of all the changes, with detailed listings of the riskiest
changes along with counts for the complete set. Click on the summary to close the resource graph
and instead open a listing of the change events on the Infrastructure History view of the Change
Analyzer.
everting Changes
You can also revert certain changes that may be automated via hypervisor infrastructure APIs.
Right-click on a row in the Infrastructure History to access this option (when available).
98
Type the desired value and revert either immediately, or on a scheduled basis.
Note
This action is not available for all changes and reversion of specific change types may not be
available for all hypervisors.
VM Comparison
As the size and complexity of virtual environments continues to grow, standardization becomes
increasingly important. As a simple example, after testing and tuning of a specific database server
type has been carried out in order to understand the configuration which guarantees optimal
performance, it is important to ensure that all instances of this type of server follow this standard.
The VM Comparison tab enables you to compare all VMs within the selected environment to a
specific gold standard or reference VM or template and, if any do differ, to see a detailed list of
the configuration differences.
Click New Comparison to select a reference VM or template. You can search by name or browse
the virtual topology tree to locate the desired template.
99
The selection appears following the Compare With: label. The VM Comparison view maintains a
history of selected templates so that you can easily switch between frequently used templates.
To compare against the typical configurations used in your environment, select Average (By
Hypervisor). This option is selected by default the first time you open the VM Comparison view.
Each row of the report shows the name of the VM that deviates from the standard, the number of
differences found, the maximum impact risk of all the deviations, and the date that the VM was
last changed.
100
To see a detailed list of recent changes that have occurred on a selected VM, right-click on the
report row to go directly to the Infrastructure History report for the selected object.
Change Assessment
The Change Assessment view allows you to define a sequence of changes, see what impact those
changes have on performance and capacity, and allows you to trigger the execution of these
changes immediately or schedule these changes within vOPS. The entire environment is displayed
in this view. Change assessments made are executed in the order displayed in the table. Review the
impact of a change to all elements in the environment from this view.
To model proposed changes:

1 On the right-hand side of the view, click Make a Model.

2 Select the type of change from the drill down menu.
3 Optionalselect Move a VM.
101
102
a Expand the navigation tree displayed on the left, select a VM.
The name of this VM is displayed in the VM to Move dialog box.

b Expand the navigation tree displayed on the right, under VM Destination, and select a
destination.
The name of this destination is displayed in the VM Destination dialog box.
c Click Save.
The change is added to the Change Assessment table.

4 Optionalselect Power On a VM or Power Off an VM.
103
a Expand the navigation tree and select the VM.
In this example, the name of the VM is displayed in the VM to Power On dialog box.
The Overall Performance and Overall Capacity impact for this change is displayed at
the bottom of the Change to be Assessed dialog box.
b Click Save.

5 Optionalselect Change VM Configuration.

a Expand the navigation tree and select the VM.
The name of the VM is displayed in the VM to Configure dialog box.

A list of the current configurations is displayed.
b In the Change To dialog boxes, enter a new value and select the unit type.
c Click Save.

6 Optionalselect Change RP Configuration.
104

Repeat step a to step c of step 5.

7 Optionalselect Change HA Failure Configuration.
Note
This option is only available for VMware objects.
a Expand the navigation tree and select a cluster to configure.

b Select one of the following options:
105
106
HA Failover Disableddefault value.

Host Failures the Cluster Will Toleratespecify the count.
Percentage of Resources Reserved as Failover Capacityspecify the CPU % and
Memory % values.
Specify Failover Hostsselect an available host and click the arrow
to move the
host to the Failover Hosts list.
8 Click Save.
Change and Comparison Alarms

The Change Analyzer application also provides alarm mechanisms that can proactively alert you
to changes occurring in your environment that pose performance or security risks.
Use of the alarms is similar to all other alarms used in vOPS Server Standard. Each type of alarm
has an Alarms Configuration view for configuring alarms of that type.
Each of the alarm types also has an Alarm History view with a full history of all alarms that have
occurred.
Change Analyzer provides two types of alarms: Change Alarms and Comparison Alarms.
107
Change Alarms
Change alarms are related to the Infrastructure History tab. They allow you to receive proactive
notifications of any changes that exceed a specified impact risk level.
To create a Change Alarm:
Click New Alarm on the Alarms Configuration tab.
You can choose to receive notifications based on the type of object as well as the risk level.
The change alarms can be limited to particular objects, folders, or business views by setting the
scope for the particular alarm on the Scope tab of the alarm dialog.
Notifications of any change alarms that occur can be emailed to selected users, sent as traps to an
existing management system, sent as an alert to the System Center Virtual Machine Manager or
added to a selected RSS feed. These options are configured on the Notifications tab of the alarm
dialog.
Comparison Alarms
Comparison alarms are related to the VM Comparison tab. They allow you to receive proactive
notifications of any deviation of a VM from a specified gold standard VM or template.
To create a Comparison Alarm:
Click New Alarm on the Alarms Configuration tab.
108
As shown in the dialog box, you can choose to receive notifications only for certain types of
changes. As in the VM Comparison view, you must select a specific VM or template to use for
comparison.
The Use most recent configuration of the comparison VM or template check box controls
whether the alarm measures deviations from an unchanging standard defined by the configuration
of the comparison VM or template at the time the alarm was created (the default), or whether it
uses a dynamic standard. In the latter case, any change to a VM within the scope of the alarm
triggers a comparison to the current configuration of the gold standard VM or template.
Note
The comparison VM or template must continue to exist, otherwise an error notification is sent.
The comparison alarms can be limited to particular objects, folders or business views by setting
the scope for the particular alarm on the Scope tab of the alarm dialog.
Notifications of any comparison alarms that occur can be emailed to selected users, sent as traps to
an existing management system, sent as an alert to System Center Virtual Machine Manager or
added to a selected RSS Feed. These options are configured on the Notifications tab of the alarm
dialog.
7
Reporting and Chargeback
Generate virtual environment trend, configuration and chargeback reports using the vOPS Server
Standard Reporting and Chargeback application. The functionality of the Reporting and
Chargeback application is broken into four major areas: Summary Reports, Inventory, Chargeback
and the Cost Index vScope.
Summary Reports
Generate custom reports of infrastructure history, trends, and status for the entire virtual
environment or for select areas of the environment.
Note
All summary reports can be used in configurable dashboards. For more information, see
Configurable Dashboards and Dashboard Management on page 37.
There are five types of reports available: Standard Capacity Reports, Standard Efficiency Reports,
Standard Performance Reports, Efficiency Trend Reports, and Overall Environment Reports.
Select the specific type of report to see a listing of all available reports of that type or select All
Reports to see all possible reports.
Click a report button to access an individual report.
110
Chapter 7Reporting and Chargeback
To view reports on a specific date, set the date and options, then click Build Report. The view
refreshes.
To view reports by period, specify the start date, end date, type and content. Click Build Report to
refresh the view.
111
All of the summary reports can be accessed from any web browser using the link provided by the
URL Copy menu.
Inventory
Create custom reports of virtual machine configuration, utilization, and status, or a complete
inventory of all virtual machines from the Inventory view.
List View
Use the List view of Inventory to create custom reports by selecting the items to be included and
filtering the information for desired content.
112
To create a custom report:

1 On the top right corner, click Custom View to select the items to include in the view.
2 In the Inventory Custom View dialog box, do the following:

a Select the Table check boxes for the items you want to include.
b Select the Tool-Tip check boxes for the items you want to see in the tooltips.
c Click OK when finished.
3 To filter for specific values of each item, select the item in the Table Filters drop-down list.
113
4 Select the filter item, then select the filter criteria from the second drop-down list.
5 Type the value for the specific item and criteria in the box. The filter is applied automatically
and only items that match the specific criteria are included in the table.
You can use multiple filters to pinpoint specific conditions. Click Add Filter to add the filter
item, criteria, and value.
114
Detailed View
The Detailed View of Inventory contains detailed information about each virtual machine. The
information can be used for reference or to archive virtual environment information at regular
intervals.
Note
Because Hyper-V and VMware make different detailed information available on individual VMs,
the specific information listed in the detailed view may differ.
Chargeback
Chargeback allows you to create detailed cost analysis reports for individual groups, organizations
or customers. Reports include both allocation costs based on the virtual machine configuration and
utilization costs based on the actual utilization of the resources.
Base prices must be defined for the hardware resources (CPU, memory, network and storage) that
are used by the customers. These base prices can be overridden for specific business views, as
described in Creating Customized Pricing Models on page 116.
For help in calculating the appropriate prices for your environment, download the Chargeback
Methodology white paper and the Chargeback Calculator from the vKernel website:
http://www.vkernel.com/resources/whitepapers/chargeback-calculator-and-methodology
115
To configure chargeback:
1 In vOPS Server Standard, navigate to Settings > General > Prices.
The prices can be set individually for each host or the hosts can be dragged and dropped into
one of the tiers and the pricing set for the tier. The tiers can be renamed or new tiers added.
Once the hosts are organized appropriately, enter the prices per daily unit.
Note
You can organize datastores and disks and set their prices in the same way.
2 Next you must create the customers. To add a customer, right click on Customers in the
navigation tree and select Add Customer.
3 Type the customer name and click Add.

4 Business Views are used to organize the resources that belong to a customer. Create one or
more business views with the appropriate virtual objects (folders, clusters, hosts, resource
pools or virtual machines). The business view can then be dragged and dropped into the
specific customer folder.
5 Select the customer. The chargeback report is generated.
116
The report period can be changed according to your preference. The specific content of the report
can also be controlled.
Creating Customized Pricing Models

The default pricing model defined in Settings > General > Prices can be overridden within
individual business views, and additional fixed costs can also be defined.
To override prices and add fixed costs:
1 Right-click on a business view in the navigation tree and select Set Pricing Model.
117
2 The Set Pricing Model dialog has two panes. In the first tab, Fixed Costs, you can add fixed
per day costs (power, cooling, licensing) to the business view by clicking Add.
a Right-click on the business view and select Set Fixed Costs.
b Click Add and then type the name of the fixed cost and the amount to add daily.
3 The second tab, Override Resource Prices, allows a new price to be set on individual
resources that overrides the base price. You can set different prices for allocation and for
utilization. The base price is the price set for that resource either in a containing business
view or in Settings > General > Prices.
Within per-business-view price settings, you have three possible ways to determine the price
to be used for utilization or allocation on a specific resource:
Set a specific price by selecting appropriate units and entering a value. This price
overrides any other price.
Set a multiplier by selecting X Base Price and entering a value. This causes the base price
to be multiplied by the value specified. This can be used to provide a discount or tax on
particular resources for particular products or customers.
Leave the field blank. The base price is used.
118
To understand how this works and how the base price is determined, consider the following
example.
The Manufacturing business view contains two sub-views, Division 1 and Division 2, as shown in
the image below. If no pricing model has been created, then any VMs in any of these business
views will use the prices set in Settings > General > Prices.
Create a pricing model on Manufacturing that changes the storage utilization and CPU allocation
prices as shown. If we stop here, then all Manufacturing VMs are charged the default prices for
memory, network, storage allocation, and CPU utilization, but the new prices for storage
utilization and CPU allocation are used.
Next, create a new pricing model in Division 1, as shown in the image below. Here we have
changed the memory utilization price and added a multiplier of 0.9 to the storage utilization price.
The result is that VMs in Division 1 are charged the default prices for network, memory allocation,
storage allocation, and CPU utilization. They are charged the same price as other Manufacturing
VMs for CPU allocation, but now have a different special price for memory utilization. Finally,
VMs in Division 1 receive a 10% discount on the manufacturing price for storage utilization.
119
Fixed costs can also be overridden. If a fixed cost with the same name appears in both a parent
business view and a child one, VMs in the child business view are charged the price set there,
while VMs in the parent and other child business views are charged the price set in the parent.
Cost Index vScope

infrastructure. The Cost Index vScope indicates the relative costs of all VMs in the form of a heat
map. Each colored box represents a single host, and hosts are further grouped by cluster and data
center.
The color of each host reflects its Quest cost index (VCI), a measure of its cost relative to all other
VMs in the environment. For more information, see The vKernel Cost Index (VCI) on page 120.
The map employs a cold (blue for low-cost) to hot (red for high-cost) color scale. You can use the
color slider at the bottom of the view to change the transition from blue to red.
120
Double-click a VM box to drill down to a detailed view for the selected VM.
The vKernel Cost Index (VCI)

A VM's Quest Cost Index (VCI) represents its relative cost rank compared to all other VMs in the
environment. The VCI ranges from a minimum value of 1 (the least expensive VM) to a maximum
value of 100 (the most expensive VM).
To derive the cost index of a VM, vOPS Server computes a base cost from the actual usage of
CPU, memory, storage and network and the prices established in Settings > General > Prices. Then
it computes a corrected cost that factors in the utilization of the host the VM runs on. The reason
121
for this is that IT must bear the full cost of host resources even if they are not fully utilized and the
cost attributed to the VM should account for this.
Finally, vOPS Server derives the relative cost rank of the VM by mapping the corrected costs of all
VMs to a range between 1 and 100, preserving their relative values. Therefore, if one VM is twice
as expensive as another, its cost index will also be twice as large.
The vScope cost index drill-down provides detailed information for the selected VM on the VCI,
base cost and corrected cost, as well as details about the VM and its resource utilization.
8
Common Features
Features of the vOPS Server Standard that are common to all applications include: the Global
Search, the Navigation Tree, Business Views, Settings, Update, Help, and Reports.
Global Search
From the navigation tree, use the Global Search to quickly locate any VM, host, cluster, datastore,
or datacenter.
Product Navigation
You can navigate directly from any part of the appliance to any other part of the appliance by using
the dropdown functionality on the application buttons at the top of the user interface. These menus
reproduce the entire tab structure, so you don't need to wait for each tab to load to navigate around
the user interface.
123
Chapter 8Common Features
Navigation Tree
The Navigation Tree is common to the Dashboard and all applications. It consists of two parts:
Business Views, and the infrastructure views gathered from vCenter and System Center.
Infrastructure node
In a multi-hypervisor environment, the tree displays an Infrastructure node, followed by a
VMware sub-tree, a Hyper-V sub-tree, and a Red Hat sub-tree.
Infrastructure node structure:
VMware
Host and Clusters is kept synchronized with the vCenters connected to the vOPS Server
Standard. It contains the same objects and structures as seen in vCenter.
VMs and Templates is kept synchronized with the vCenters connected to the vOPS
Server Standard. It also contains the same objects and structures as seen in vCenter.
Datastores contains all of the datastores and datastore clusters used in the virtual
environment.
Hyper-V
Host and Clusters is kept synchronized with SCVMM. It contains the same objects and
structures as seen in SCVMM.
Disks contains all of the virtual disks used in the virtual environment.
Red Hat
Clusters is kept synchronized with the Red Hat clusterss connected to the vOPS Server
Standard. It contains the same objects and structures as seen in vCenter.
Storages contains all the data storage locations used in the virtual environment.
In a single-hypervisor environment, the Infrastructure and VMware or Hyper-V nodes do not
appear.
Business Views allow the organization of the infrastructure based on organizational use or
application deployment.
124
Organizing your VMs

There are three main tagging methods provided to assist you in organizing your VMs within
vOPS.
Analysis Period
Analysis Period is a method of tagging the VMs in your environment with specified exclude times.
The Analysis Period options are:
Use Parent Settingsno exclude times set.
Override Parent Settingsset the analysis period for a virtual machine to exclude specific
times.
Application Types
Application types are a method of tagging the VMs in your environment with the application that
runs on them. This allows for more efficient organization of your VMs within vOPS. Application
types can be used in smart business view and configuration group filters using the Application
Type characteristic.
Right-click on an individual VM or container object (such as a resource pool) in the navigation
tree to Set Application Type on the object. The application type is applied to all VMs in the
hierarchy below the current object. You can select either which application type to associate with
these VMs or you can manage the application types themselves under the Manage Application
Types tab.
125
vCloud Director
By default, icons for vApps, catalogs, and virtual machines are displayed in the navigation tree. To
disable, right click in the navigation tree, and clear the check box Display object names and
icons.
Business Views
Business Views allow the organization of the infrastructure based on organization use or
application deployment. Business views are hierarchical and can contain other business views,
vCenter folders or individual objects. The same object can appear in more than one business view,
allowing multiple perspectives on the infrastructure to be maintained.
There are two types of Business Views: Free-Form and Smart.
Note
The functionality of business views is shared by Configuration Groups, as described in Settings

on page 132.
126
Free-Form Business Views

To add a free-form business view:
1 Right-click either Business Views or a previously created business view in the navigation
tree and select Add Free-Form Business View.

2 In the Add A Free Form Business View dialog box, type a name and description for the
business view.
3 Select the inventory objects to be included in the business view and move them to the table
on the right.
4 Click Add to create the business view containing the selected objects.
Tip
You can also select objects in the navigation tree and drag and drop them into an existing
business view.
Smart Business Views

Smart business views work differently from free-form business views in that they are dynamically
populated based on a series of rules instead of by adding specific objects.
To add a smart business view:
1 Right-click on Business Views or a previously created business view in the navigation tree
and select Add Smart Business View.
127
2 Type the name and description of the business view.

3 Click New Rule to add a new rule set. Multiple rule sets can be applied to each smart
business view.
Each rule set can contain multiple rules. For example, a rule set containing VM name
contains SQL and Cluster contains prod creates a business view that contains all VMs within
the prod cluster that also have SQL in their name. If a new VM that matches this criteria is
added to the environment it also shows up within this business view.
Each rule consists of several elements: the type of object to which it applies (such as VM or
host), the property of that object for which the condition is set (for example, name,
application type, or OS), and the condition itself.
4 Click Save to finalize the rule sets and create the new smart business view.
Tip
To learn more about how to create Business Views to organize VMs and other objects in vOPS,
watch our learning video.
Visit http://www.vkernel.com/support/learn
Resource Graphs
Resource Graphs allow you to chart the raw data points collected by vOPS for the various objects
(such as hosts and VMs) in your environment.
Resource Graphs are available throughout the product by clicking Resource Graphs at the right of
the main tab layer. They can also be added to any custom Dashboard. They can be configured to
128
display host (or VM) CPU, memory, storage, and networking data along with datastore and guest
partition data.
Resource graphs include an overlay showing what changes occurred during the interval that is
being charted. A green, yellow, or red star appears along the top of the chart whenever there are
events that occurred during that time period. The color of the star reflects the maximum impact
risk level of the changes that occurred. The color definitions are provided at the top of the graph.
Hovering over the star brings up a summary of all the changes, with detailed listings of the riskiest
changes along with counts for the complete set, as shown in the image below. Clicking on the
summary closes the resource graph and opens a listing of the change events in the Infrastructure
History view of the Change Analyzer.
Reports
All of the views within each application can be saved as an XML file, a PDF, emailed, or
scheduled to be emailed on a regular basis.
Table Reports
Table reports are used throughout vOPS (for example, Current Bottlenecks or Datastore
Performance). The columns shown in these reports can be customized.
To add or remove columns from a given table:
1 Click the drop-down menu arrow in the column header.
Tip
The dropdown menu arrow may not be visible until you hover your cursor over the
column header.
2 Click Columns.
3 Select or clear items from the menu as desired.
129
Scheduled reports use the columns that are selected at the time the report is configured, allowing
you to customize reports sent to different audiences.
Saving Reports
Click XML or PDF to immediately save the current view.
Emailing Reports
Click E-mail to specify the type of report and one or more email addresses to immediately send
the report to.
130
Scheduling Reports
Click Schedule to specify how often the report will be sent, the type of the report, and one or more
email addresses to send the report to.
Diagnose a VM
Click Diagnose a VM to review the status of a virtual machine. From this view you can quickly
see if anything is wrong, what it is, and what to do about it.
To view diagnose information for a VM:
1 From the Performance Analyzer tab, click Diagnose a VM.
2 Type the beginning of the VM name.
A list of VM machines is displayed in the drill down menu.

Tip
Limit the search scope by selecting the environment of interest in the navigation tree at
the left. For more information about how to use the navigation tree menus, see
Navigation Tree on page 123.
131
3 Select aVM to review the diagnostic information.
Alternatively, you can select a VM in the navigation tree and right click to select Diagnose
This VM.
4 Optionalclick Graph Period and select an option. By selecting another Graph Period,
you can quickly see the history for this virtual machine.
132
Settings
The vOPS Server Standard settings apply to all of the applications.
To access the settings, click the gear icon
at the top-right corner of the browser interface.
Settings > General > Environment

Configure the connections to the VMware vCenter(s) or ESX host(s).
Systems Center connections appear here once properly configured, but cannot be added here
directly. Follow the detailed instructions in Installing vOPS Server Standard to add SCOM
connections.
By default, the Display object names and icons as they appear in the vCloud Director option is
enabled. Added support for vCloud Director, a VMware software, enables the consolidation of
virtual infrastructure across multiple clusters, the encapsulation of application services as portable
vApps, and the deployment of those services on-demand with isolation and control. With this
option enabled, the naming convention used by the vCloud Director is captured.
Note
All vCenters that the vCloud Director uses must have added VMware and set credentials.
133
Settings > General > Database (DB) Settings

The vOPS Server Standard requires a database for storage of the information it uses to analyze the
virtual environment. The database may be either an embedded PostgreSQL database or an external
Microsoft SQL or Oracle database. Approximately 30 MB of database storage is required for each
virtual machine. The PostgreSQL database is automatically configured during installation.
To use an external database:
1 Click Change Database.
2 Select either MS SQL or Oracle.
134
MS SQL
To configure a Microsoft SQL 2005 or later database:
1 Select the MS SQL option.
2 Type the server name or IP address of the MS SQL database server.
3 Type the database credentials.
If the database does not already exist, the credentials must have permissions that allow
database creation.
If the database already exists, the credentials need only have database owner permissions.
These credentials are used to create the database (if it does not already exist), the tables, and
the stored procedures. Either Windows authentication or SQL authentication can be selected.
4 Click Check Settings to verify database connectivity.
5 Click Set Database to finish.
135
Oracle
To configure an Oracle 10g or later database:
1 Select the Oracle option.
2 Type the server host and service name of the Oracle database server.
3 Type the database credentials.
If the database does not already exist, the credentials must have permissions that allow
database creation.
If the database already exists, the credentials need only have database owner permissions.
These credentials are used to create the database (if it does not already exist), the tables, and
the stored procedures. Either Windows authentication or SQL authentication can be selected.
4 Click Check Settings to verify database connectivity.
5 Click Set Database to finish.
Settings > General > Savings

Set the costs used in estimating potential savings through reconfiguration or elimination of waste.

Settings > General > Prices

Set the hardware prices used to determine resource allocation and utilization costs.
Settings > General > Scheduled Tasks

Review, edit, or delete the scheduled reports.
136

Settings > General > Deployment Tasks

Review, edit, or deleted the scheduled virtual object deployment changes.
Settings > General > Automated Tasks

Review, edit, or deleted the scheduled virtual object configuration changes.
137

Settings > General > Proxy

Set the proxy connection to the Internet.
138

Settings > General > Miscellaneous

Add the company logo or adjust other general
setting
Settings > Notifications > Alerts

Review, edit, or delete the Trend, Capacity, and Predictive Alerts.
Note
These alarms are deprecated and exist for legacy compatibility. If available, please use
Performance Analyzer for alerting purposes instead.
139

Settings > Notifications > System

Set general system notifications.
Settings > Notifications > Address Book

Review, add, edit, or delete address book entries used for notifications and alarms.
140
141
Settings > Notifications > Email

Set the credentials used to send email.
Settings > Thresholds

Thresholds are a set of configurable values that many components in the application use. Capacity
Availability, for example, does not make any capacity recommendations that would violate a
142
threshold. The alarms in Performance Analyzer are configured to use these thresholds as a basis
for their trigger values. Current Bottlenecks and Future Bottlenecks also use these values as a basis
for identifying current and trending resource bottlenecks.
There are separate tabs for VMware environments and Hyper-V environments due to the differing
metrics between the two hypervisors.
The Peak Analysis Period is the amount of time for which a value has to be sustained before
it is considered a peak. For example, if CPU goes up to 90% for 10 minutes and drops back
down, given a 15 minute peak analysis period, it won't be labeled as a peak. It needs to last
for as long as this value indicates.
The Threshold For Merging Peaks provides the flexibility to turn two separate peaks into
one. For example, if you have a 15 minute, 80% peak followed immediately by a separate 15
minute 82% peak, they are really the same peak. Therefore, if the values are within the
threshold percentage, they are merged into one large peak.
The Real-time Warning/Alarm Durations set the duration on the alerts that go into Virtual
Center. In order for Virtual Center to generate an alert, the warning or alarm value has to be
sustained for the full duration.
Settings > Thresholds > Cluster

Review or edit the thresholds used to analyze cluster performance. There are separate tabs for
VMware, Red Hat, and Hyper-V clusters.
Settings > Thresholds > Host

Review or edit the thresholds used to analyze host performance. There are separate tabs for
VMware, Red Hat, and Hyper-V clusters.

Settings > Thresholds > Resource Pool

Review or edit the thresholds used to analyze resource pool performance.
143
144
Settings > Thresholds > VMware vApp

Review or edit the thresholds used to analyze VMware vApp performance.
Settings > Thresholds > Virtual Machine

Review or edit the thresholds used to analyze virtual machine performance. Please note that there
are separate tabs for VMware VMs and Hyper-V VMs.

145
146
Settings > Users

In User Management you can enable or disable the use of Active Directory (AD) authentication.
When configuring Active Directory, you must specify the following items:
AD Server: Specify the FQDN or IP of a domain controller that manages Active Directory.
DNS Domain: Specify the DNS domain for Active Directory, such as vkernel.com.
AD Admin Group: You may specify any group in Active Directory here. You may create a
new group or use an existing one. Any user that resides within this group or any of its nested
sub-groups will be given full administrative rights within vOPS.
Note
You may specify other groups with which to grant specific permissions levels later on in
the configuration (such as giving business users read-only rights on a specific cluster),
this is only for administrators.
AD Service Account: Specify a service account with which the vOPS appliance can
authenticate against LDAP.
Password: The password for the AD Service account.
147
Important You cannot use local users and Active Directory users at the same time. Enabling Active
Directory disables local users (including the default vkernel account).
If you choose not to use Active Directory, right-click on Users to add a new user. After the
username and password have been specified, they appear in the list. The new user does not have
any permissions by default. You must modify the permissions to suit your preference. Any user
granted the Add, edit and delete users permission is added to the User Administrators list at the
top of the User Management tree.
When using Active Directory, users logging in receive, by default, access rights according to their
permissions in vCenter in a VMware environment. By default, in a Hyper-V environment, they
have no access permissions. Administrators can choose to add permissions directly in order to
override the default permissions.
Note
Overriding the permissions in vOPS Server does not modify any permissions in vCenter.
Another feature of Active Directory is the use of AD User Groups. Right-click on this item in the
menu on the left of the User Management screen and add a new AD user group. Specify any group
within Active Directory. You can then set permissions for this group as a whole. These rights
propagate to every user that is a member of this group. This allows you to grant an entire group of
non-administrative vOPS Server users specific permissions without having to grant them on an
individual basis.
Settings > License

Request, change, install, migrate, review, or assign socket licenses to the hosts.
148
For more information, see Managing Licenses on page 27.
Settings > Configuration Groups

Configuration Groups are used to customize different settings in different parts of the
environment. They function similarly to Business Views (both free-form and smart), but are used
for configuration rather than reporting.
Configuration Groups are designed to be used across multiple types of settings, but currently are
used only within Rightsizer. For more information, see Rightsizer Constraints on page 85.
To create a new Configuration Group (either free-form or smart), right-click All Configuration
Groups and create them in the same way you do a Business Views. With free-form groups, you
can drag any item from the inventory tree at the bottom into the group. The contents of smart
configuration groups are determined by the filters used to create them, just as with smart business
views.
For information on how to use Configuration Groups to create constraints on Rightsizer

recommendations, see Rightsizer Constraints on page 85.

Settings > Dashboard URLs

Delete custom created dashboards from the list of URLs.
149
150
Index
A
abandoned VM images 87
Actions History 46
activating
purchased license 29
trial license 28
Active Directory (AD) 146
address book notification settings 140
Alarm Configuration
Real Time Alarms 47
Trend Alarms 50
Alarm History
Hypervisor Alarms 55
Real Time Alarms 47
Trend Alarms 49
alarms 40
real time 43
set in System Center 45
set in vCenter 44
Alarms and Bottlenecks 40
Alarms by Resource 46
alert notification settings 139
allocating
socket licenses 31
analyzing performance 43
application
license settings 147
types 124
automated tasks general settings 137
Availability
Capacity Availability 62
Capacity Manager 62
Datastore Statistics 71
Future Requirements 70
Top Consumers 72
VM Reservations 67
B
bottlenecks 40
Business Views 125

Free-Form 126
Smart 126
C
Capacity Availability 62
Capacity Efficiency and Availability 40
Capacity Manager 62
Availability 62
Current Bottlenecks 73
CPU 74
Latency 77
Memory 75
Root Cause 73
Storage 75
Summary 73
Throughput 76
Future Bottlenecks 77
Overview 77
Root Cause 78
Predictive Alarms 78
Active Alarms 78
Alarm Configuration 79
Capacity vScope 81
Change Alarms 106, 107
Change Analyzer 92
Change Alarms 106
common features 92
Comparison Alarms 106
Filters 93
Infrastructure History 95
risk definitions 92
VM Changes 94
VM Comparison 98
Chargeback 109, 114
creating customized pricing models 116
cluster threshold settings 142
common features 122
Comparison Alarms 106, 107
151
Index
configuration groups 85
settings 148
configuring
RHEVM history database 19
vKernel Hyper-V collector 33
vOPS Server Standard 21
connecting
Microsoft System Center 23
RHEV 24
connecting VMware vCenter 22, 24
connection management 22
constraints
Rightsizer 85
Rightsizer conflicts 86
Cost Index 120
vScope 119
creating customized pricing models 116
Current Bottlenecks
Capacity Manager 73
CPU 74
Latency 77
Memory 75
Root Cause 73
Storage 75
Summary 73
Throughput 76
Performance Analysis 55
CPU 57
Latency 59
Memory 58
Root Cause 56
Storage 58
Summary 55
Throughput 59
Current Hypervisor Alarms 54
customized pricing models 116
D
dashboards
configurable 37
Get Started 40
managing 37
vScope 42
data collection, initial 25
database
Microsoft SQL settings 134
Oracle settings 135
settings 133
Datastore Performance Analysis 60
Datastore Statistics, Availability 71
deactivating licenses 33
default
Trend Alarms 54
E
Efficiency vScope 90
email notification settings 141
emailing reports 129
environment general settings 132
export domain 20
F
Filters 93
free-form business views 126
Future Bottlenecks
Capacity Manager 77
Overview 77
Root Cause 78
Future Requirements, Availability 70
G
general settings
automated tasks 137
database 133
environment 132
miscellaneous 139
prices 136
proxy 138
savings 135
scheduled tasks 136
Get Started dashboard 40
graphs of resources 127
guidelines for installation 10
H
history database, configuring 19
host threshold settings 142
how to install 10
Hyper-V
collector 33
virtual machine, installing as 15
Hyper-V software requirements 11
152
Index
Alarm History 55
Current 54
integrating with vOPS alarms 36

migrating a license 33
miscellaneous general settings 139
Impact Analysis 46
Infrastructure History 95
reverting changes 97
Infrastructure Overview 41
initial configuration of vOPS Server Standard 21
initial,data connection 25
initializing virtual machine 14
installation guidelines 10
installing 10
Hyper-V virtual machine 15
license from e-mail 32
required packages for RHEVM reports 19
RHEVM virtual machine 18
vKernel Hyper-V collector 33
VMware virtual machine 11
integrating vOPS alarms with System Center 36
Inventory 111
Detailed View 114
List View 111
navigation 122
tree 123
notification settings
address book 140
alerts 139
email 141
notification settings, system 140
Performance Analysis
Current Bottlenecks 55
CPU 57
Latency 59
Memory 58
Root Cause 56
Storage 58
Summary 55
Throughput 59
Datastore Performance 60
Trend Alarms 49
Performance Analyzer 43
Real Time Alarms 43
Performance vScope 60
postgres remote connection 21
potential zombie VMs 89
powered off VMs 88
powering on virtual machine 14
Predictive Alarms
Capacity Manager 78
Active Alarms 78
license
activating 28
allocating sockets 31
deactivating 33
installing from e-mail 32
managing 27
migrating 33
purchased 29
settings 147
trial 28
license agreement 22
logging in 26
M
managing
licenses 27
managing connections 22
Microsoft Hyper-V 15
Microsoft System Center
connections 23
O
Optimizer 83
Rightsizer 83
CPU 84
Memory 85
Storage 85
Summary 83
Wastefinder 87
Oracle database settings 135
153
Index
prices, general settings 136
proxy, general settings 138
R
Real Time Alarms 43
Actions History 46
Alarm History 47
Alarms by Resource 46
Root Cause 45
Red Hat Enterprise Virtualization Manager reports 19
Red Hat software requirements 11
remote database connection
RHEVM postgres 21
Reporting and Chargeback 109
Inventory 111
Summary Reports 109
Reports 128
emailing 129
saving 129
scheduling 130
Table 128
reports
RHEVM 19
requirements
Hyper-V software 11
Red Hat (RHEVM) software 11
system 10
VMware software 11
Resource Graphs 127
resource pool threshold settings 143
RHEV
connections 24
export domain, selecting 20
RHEVM
configuring history database 19
history database 19
installing required packages 19
Rightsizer 83
Constraint conflicts 86
Constraints 85
CPU 84
Memory 85
Storage 85
Summary 83
Risk Definitions 92
Root Cause
Impact Analysis 46
Real Time Alarms 45
S
saving reports 129
savings, general settings 135
scheduled tasks general settings 136
scheduling reports 130
selecting, RHEV export domain 20
settings 132
configuration groups 148
general
automated tasks 137
database 133
environment 132
miscellaneous 139
prices 136
proxy 138
savings 135
scheduled tasks 136
license 147
notifications
address book 140
alerts 139
email 141
system 140
thresholds 141
cluster 142
host 142
resource pool 143
virtual machine 144
VMware vApp 144
users 146
smart business views 126
support 8
System Center
alarms set 45
integration with 36
system notification settings 140
system requirements 10
T
Table Reports 128
technical support 8
154
Index
threshold settings 141

cluster 142
host 142
resource pool 143
virtual machine 144
VMware vApp 144
Top Consumers, Availability 72
Trend Alarms
default 54
History 49
Performance Analysis 49
U
unused template images 88
upgrading
license 33
user settings 146
V
vCenter, alarms set in 44
virtual machine
Hyper-V 15
initializing 14
powering on 14
RHEVM 18
threshold settings 144
VMware 11
vKernel Cost Index (VCI) 120
vKernel Hyper-V collector
configuring 33
installing 33
VM
Changes 94
Comparison 98
Reservations, Availability 67
VMs
abandoned images 87
potential zombies 89
powered off 88
unused template images 88
VMware
software requirements 11
vApp threshold settings 144
vCenter connections 22, 24
vOPS Server
common features 122
initial configuration 21
logging in 26
settings 132
vScope
Capacity 81
Cost Index 119
dashboards 42
Efficiency 90
Performance 60
W
Wastefinder 87
Abandoned VM Images 87
Potential Zombie VMs 89
Powered Off VMs 88
Unused Template Images 88

VOpsStandard Installation and User Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

VOpsStandard Installation and User Guide

Transféré par

Droits d'auteur :

Formats disponibles

vOPS Server Standard 6.

2012 Quest Software, Inc.

Third Party Contributions

Installation and User Guide

vOPS Server Standard: Installation and User Guide

Installing vOPS Server Standard.....................................................................................................................................10

vOPS Server Standard: Installation and User Guide

Capacity Efficiency and Availability........................................................................................................................................ 40

Performance Analyzer ..................................................................................................................................................... 43

Capacity Manager ............................................................................................................................................................ 62

vOPS Server Standard: Installation and User Guide

Change Analyzer .............................................................................................................................................................. 92

Reporting and Chargeback ........................................................................................................................................... 109

vOPS Server Standard: Installation and User Guide

List View............................................................................................................................................................................... 111

Common Features.......................................................................................................................................................... 122

vOPS Server Standard: Installation and User Guide

Settings > Dashboard URLs ................................................................................................................................................ 149

Introduction to this Guide

About Quest Software, Inc.

Contacting Quest Software

Quest Software, Inc.

Contacting Quest Support

vOPS Server Standard: Installation and User Guide

Retrieve thousands of solutions from our Knowledge Base

vOPS Server Virtual Machine

Less than 90%

Less than 80%

Less than 80%

vOPS Server Database Selection

vOPS Server Standard: Installation and User Guide

Chapter 1Installing vOPS Server Standard

vCenter Database Server

Less than 90%

Less than 80%

Less than 80%

Less than 90%

Less than 80%

Less than 80%

VMware Software Requirements:

Installing as a VMware Virtual Machine

vOPS Server Standard: Installation and User Guide

The Deploy OVF wizard opens.

vOPS Server Standard: Installation and User Guide

vOPS Server Standard: Installation and User Guide

Chapter 1Installing vOPS Server Standard

Powering On and Initializing the Virtual Machine

Setting a Static IP Address or Changing the Network Time Server

vOPS Server Standard: Installation and User Guide

Chapter 1Installing vOPS Server Standard

Installing as a Microsoft Hyper-V Virtual Machine

Import Virtual Machine.

The Import Virtual Machine dialog opens.

vOPS Server Standard: Installation and User Guide

9 In the left pane, select the Network Adapter.

vOPS Server Standard: Installation and User Guide

Chapter 1Installing vOPS Server Standard

Power On and Initialize the Virtual Machine

vOPS Server Standard: Installation and User Guide

Chapter 1Installing vOPS Server Standard

Setting a Static IP Address or Changing the Network Time Server

Installing as an RHEVM Virtual Machine

WinSCP opens to your account's home directory.

vOPS Server Standard: Installation and User Guide