HP Matrix Operating Environment 7.3 Update1 Getting Started Guide

HP Matrix Operating Environment 7.3
Update1 Getting Started Guide
Abstract
This document provides an overview of the HP Matrix Operating Environment. It is intended to be used by system administrators
and other technical professionals involved with data center operations, administration, and planning.
HP Part Number: T8671-91101
Published: March 2014
Edition: 1
© Copyright 2006-2014 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
UNIX® is a registered trademark of The Open Group. Java® is a registered trademark of Oracle and/or its affiliates.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open
Group UNIX 95 branded products.
Contents
1 Introduction to the HP Matrix Operating Environment.......................................7
Components of Matrix OE.........................................................................................................7
HP Matrix OE visualization....................................................................................................8
HP Matrix OE logical server management...............................................................................8
HP Capacity Advisor............................................................................................................9
HP Capacity Advisor Consolidation software...........................................................................9
HP Matrix Operating Environment infrastructure orchestration...................................................10
HP Matrix Operating Environment recovery management........................................................11
HP Storage Provisioning Manager........................................................................................11
Application Discovery.........................................................................................................11
HP Global Workload Manager (gWLM)...............................................................................12
HP Instant Capacity software...............................................................................................12
Partition Manager..............................................................................................................12
HP Integrity Virtual Server Manager.....................................................................................13
HP Matrix KVM Private Cloud..............................................................................................13
Product configurations ............................................................................................................13
Matrix OE features..................................................................................................................14
2 License management.................................................................................19
End-user license agreement......................................................................................................19
Matrix OE managed system licenses.........................................................................................19
Matrix OE managed system licensing model.........................................................................19
Licensed Matrix OE products on managed systems.................................................................20
HP ProLiant servers and ProLiant server blades..................................................................20
HP Integrity and HP 9000 servers and Integrity server blades.............................................20
Non-HP servers.............................................................................................................21
HP Capacity Advisor Consolidation software license..........................................................21
HP Operations Orchestration limited license.....................................................................22
License requirements for managed systems with Instant Capacity products ............................22
Managed system trial licenses.........................................................................................22
Adding and applying managed system licenses ....................................................................23
Recommended process: Use the managed system setup wizard...........................................23
Alternative process: Use HP SIM License Manager.............................................................23
Setting authorizations................................................................................................23
Starting the License Manager.....................................................................................23
Order for applying licenses—Windows CMS managed systems.....................................23
Scan for HP-UX licenses ............................................................................................24
Using the CMS password reconfigure tool.............................................................................24
Matrix OE public cloud managed instance licenses.....................................................................24
Bursting to external clouds...................................................................................................24
Managing Public Cloud instances with Matrix OE .................................................................25
3 Getting started.........................................................................................27
Installing the software..............................................................................................................27
Configuring privilege elevation.................................................................................................27
Using the HP Insight managed system setup wizard.....................................................................27
Configuring user authorizations................................................................................................28
Configuring data collection credentials......................................................................................28
About the HP Capacity Advisor Data Collection Service...............................................................28
Contents
3
Configuring data metrics to better reflect your environment......................................................29
Solving utilization data collection problems...........................................................................29
Removing unneeded agent software..........................................................................................30
Using Matrix OE visualization..................................................................................................30
Starting Matrix OE visualization from HP SIM .......................................................................31
Matrix OE tabs..................................................................................................................32
Matrix OE menu bar .........................................................................................................32
Matrix OE tool bar ............................................................................................................35
Customizing collections and home page ..............................................................................36
Creating custom collections............................................................................................36
Automatically displaying Matrix OE visualization ..............................................................37
4 Troubleshooting .......................................................................................39
Memory and other system requirements.....................................................................................39
Insight managed system setup wizard........................................................................................39
Diagnose menu actions...........................................................................................................39
Check CMS configuration...................................................................................................39
Check CMS to managed node communication......................................................................40
Check managed node configuration.....................................................................................41
vseassist command.................................................................................................................42
5 Support and other resources......................................................................43
Information to collect before contacting HP.................................................................................43
How to contact HP..................................................................................................................43
Security bulletin and alert policy for non-HP owned software components......................................43
Subscription service................................................................................................................43
Registering for software technical support and update service.......................................................43
How to use your software technical support and update service...............................................44
HP authorized resellers............................................................................................................44
Related information.................................................................................................................44
Manuals and white papers..................................................................................................44
Installation and configuration: Microsoft Windows CMS.....................................................45
Installation and configuration: HP-UX CMS.......................................................................45
Using Matrix OE and related environments.......................................................................45
Websites..........................................................................................................................46
Information and solutions...............................................................................................46
Products.......................................................................................................................46
Command references (manpages) .......................................................................................46
Reference pages installed on the CMS.............................................................................46
Reference pages installed with agent software on managed systems....................................47
Reference page installed on cell-based complexes.............................................................47
Reference pages installed on systems running Integrity VM.................................................47
Selected HP Systems Insight Manager reference pages.......................................................48
Typographic conventions.........................................................................................................48
6 Documentation feedback...........................................................................49
Command reference....................................................................................51
vseassist(1M)..........................................................................................................................52
vselicense(1M)........................................................................................................................57
4
Contents
Glossary....................................................................................................63
Index.........................................................................................................67
Contents
5
6
1 Introduction to the HP Matrix Operating Environment
This document provides an overview of HP Matrix Operating Environment (Matrix OE).
•
Chapter 1 describes the product features and the available configurations.
•
Chapter 2 (page 19) describes the licensing model and license management procedures.
•
Chapter 3 (page 27) describes initial setup steps to get started with Matrix OE.
•
Chapter 4 (page 39) describes the tools available to set up managed systems correctly and
diagnose and correct common configuration problems.
•
Chapter 5 (page 43) provides a list of support resources and a comprehensive list of Matrix
OE documentation.
•
The Command reference (page 51) provides command reference pages for the vseassist(1M)
and vselicense(1M) commands that are mentioned elsewhere in this document.
•
The Glossary (page 63) provides definitions of key terms used in this document. If you are
viewing this document in electronic form, click the term to jump to the glossary definition.
Matrix OE is an integrated command center that enables you to continuously analyze and optimize
your cloud and converged infrastructure. It builds on the HP infrastructure management portfolio,
including HP Systems Insight Manager (HP SIM) and HP Insight Management.
Matrix OE provides an integrated graphical environment for managing physical servers, logical
servers, virtual machines, server blades, nPartitions, virtual partitions, applications, and workloads.
You can dynamically resize virtual servers and migrate resources where they are needed, based
on service-level objectives and business requirements.
For information about the changes in this release of Matrix OE, see the HP Matrix Operating
Environment Release Notes. For a complete list of Matrix OE documentation and the websites
where these documents can be found, see “Related information” (page 44).
IMPORTANT: The information in the following sections is a summary. Specific supported hardware
and software configurations are provided in the HP Insight Management Support Matrix, available
at http://www.hp.com/go/matrixoe/docs.
Components of Matrix OE
The Matrix OE software is installed on a Central Management Server (CMS) running HP SIM,
which provides a browser-based user interface. A single CMS can be used to manage different
types of systems or instances. The Matrix OE components include Capacity Advisor, Matrix OE
visualization, Matrix infrastructure orchestration, Matrix recovery management, Global Workload
Manager, Matrix KVM Private Cloud and all HP Insight Control components. The software is
installed on the CMS once, regardless of how many or what types of managed system or managed
instance licenses are purchased. The following CMS installations are supported:
•
Matrix OE can be installed on the following types of CMS running Microsoft Windows:
◦
HP ProLiant server
◦
HP BladeSystem c-Class ProLiant server blade
◦
Virtual machine running under VMware ESX or Microsoft Hyper-V on HP ProLiant or
supported non-HP server
On a CMS running Microsoft Windows, Matrix OE is installed as part of the Insight
Management software family of products. For installation and configuration information, see
the HP Insight Management Preinstallation Worksheet, HP Insight Management Quick
Installation Guide, and HP Insight Management Installation and Configuration Guide. For an
introduction to Insight Management software, including security recommendations, a summary
Components of Matrix OE
7
of included products, and a documentation roadmap, see the HP Insight Management Getting
Started Guide.
Table 2 (page 15) provides information on the Matrix OE features that are available on a
CMS running Microsoft Windows.
•
Matrix OE can be installed on the following types of CMS running HP-UX:
◦
HP Integrity server
◦
HP Integrity server blade
◦
Virtual machine running under HP-UX vPars and Integrity VM
For installation on a CMS running HP-UX, see HP Matrix Operating Environment Integrity CMS
Installation and Configuration Guide.
Table 3 (page 17) provides information on the Matrix OE features that are available on a
CMS running HP-UX.
The following sections summarize the major software components of Matrix OE. For more
information, see the user guides and other documents listed in “Related information” (page 44).
Help is also available within the software by clicking the button in the upper right corner of most
screens.
HP Matrix OE visualization
Matrix OE visualization provides the framework for visualizing your virtual server environment. All
the systems and workloads that you are authorized to view are displayed in graphical views. The
hierarchical relationships between systems is displayed in the Visualization view. Different
perspectives can be selected to customize this view. The Workload view shows the workloads
running under servers. Both views show current utilization metrics, allowing you to easily monitor
the operational status of the resources managed by Matrix OE.
With Matrix OE visualization, you can perform the following tasks:
•
Customize the level of detail that you want to see.
•
Easily access additional Matrix OE capabilities to manage and configure systems and
workloads.
•
Inventory your virtual and physical servers.
•
Centrally configure your server resources for optimum utilization.
Launch Matrix OE visualization from HP SIM in any of the following ways:
•
From the top (HP SIM) menu bar, select Tools→HP Matrix OE visualization...
•
From the Systems and Event Collections list in the left navigation area, select
Systems→Shared→Systems by Type→All Matrix OE Resources, or expand the All Matrix OE
Resources collection by clicking its icon, then selecting a subset such as nPartitions
•
Create a custom collection whose default view is set to “HP Matrix OE visualization”,
and select that collection in the left navigation area
For more information about Matrix OE visualization, see “Using Matrix OE visualization” (page 30).
HP Matrix OE logical server management
A logical server is a set of configuration information that you create, activate and move across
physical and virtual machines. It contains the logical server definition and description, including
the server compute resources (for example, number of CPU cores and amount of memory), and
the server connections to storage fabric and networks.
8
Introduction to the HP Matrix Operating Environment
A logical server is managed within Matrix OE and, when activated, is applied to the creation of
a virtual machine using hypervisor-based software or to a bare-metal server blade using HP Virtual
Connect Enterprise Manager. Logical servers can be defined using the Create Logical Server
wizard, or created and activated via the import of an existing server blade or virtual machine.
Logical server management allows you to perform tasks such as the following:
•
Populate an enclosure.
•
Load-balance servers.
•
Evacuate servers, for routine maintenance or in case of disaster.
Logical server management is only supported on a CMS running Microsoft Windows.
For more information about managing logical servers, see the HP Matrix Operating Environment
Logical Server Management User Guide, available at http://www.hp.com/go/matrixoe/docs.
HP Capacity Advisor
Capacity Advisor helps you to analyze and optimize workloads across your management domain
to maximize utilization of computing resources.
It consists of two tools, Capacity Planning and Capacity Analysis:
•
Capacity Planning provides scenario analysis to help manage your current server resources
and plan for changes to your workloads and computing environment (system CPU and memory,
network and disk I/O bandwidth, and power use). It lets you quickly and safely test proposed
configuration changes in your data center before you actually make them.
•
Capacity Analysis combs through utilization data to help you locate both immediate and
impending problems in the data center.
Predefined queries allow you to monitor resource utilization on network systems over a period
of time. You can also define new, custom queries. When creating or editing queries, you can
define the information to be listed in a query's results, thereby creating a customized report.
With Capacity Advisor, you can find answers to questions such as the following:
•
Is there room on this system for an additional workload?
•
Will this workload fit on this system?
•
Can I consolidate these servers as virtual machines on a single server?
•
What might my resource demand be in six months or a year?
•
What are the estimated power costs for cooling a real or simulated system configuration?
•
What does a comparison of several what-if scenarios reveal about the analyzed alternatives?
You can launch Capacity Advisor in any of the following ways:
•
Select Tools from the top menu bar, and then select Capacity Analysis... or Capacity Planning....
•
Select Optimize from the top menu bar, and then select Capacity Analysis... or Capacity
Planning....
•
Select Tools→HP Matrix OE visualization from the top menu bar, and then click the Analysis
tab or the Planning tab.
For more information about Capacity Advisor, see the HP Capacity Advisor User Guide, available
at http://www.hp.com/go/matrixoe/docs.
HP Capacity Advisor Consolidation software
Capacity Advisor is also available through a limited-duration license for systems that are intended
to be consolidated. Using this software, you can collect data to help plan the consolidation of
existing systems without requiring a permanent Matrix OE license for the systems.
Components of Matrix OE
9
The Capacity Advisor Consolidation software license includes the following restrictions:
•
This license does not include Matrix OE visualization or any other Matrix OE components.
•
Systems with this license are not included in the analysis performed by the Capacity Analysis
tool.
For more information, see “Data collection and the HP Capacity Advisor Consolidation software”
in the HP Capacity Advisor User Guide.
HP Matrix Operating Environment infrastructure orchestration
Matrix infrastructure orchestration extends Matrix OE to provide rapid provisioning and repurposing
of infrastructure services from shared resource pools using a self-service portal. Infrastructure
orchestration delivers advanced template-driven design, provisioning, and ongoing operations for
multi-node, multi-tier infrastructure services. It is only supported on a CMS running Microsoft
Windows.
Matrix infrastructure orchestration supports four main activities to automate the deployment of
infrastructure services:
Design
An architect uses the graphical designer to create simple and complex infrastructure templates
that, when tested, can be published for users to create infrastructure services.
Provision
A self-service user selects an existing template and then requests infrastructure provisioning from
it, against an assigned pool of resources. The administrator can approve or deny this request and
monitor its progress.
Operate
The administrator manages server, network, and storage pools, defines virtual machine images
and software deployment jobs, performs manual provisioning tasks as part of the fulfillment of
self-service requests, and uses Insight Management software to monitor the health and utilization
of the managed environment.
Integrate
Matrix infrastructure orchestration comes with a limited version of HP Operations Orchestration.
This version is launched from within the IO user interface, and is used to trigger workflows that
can be performed before or after IO operations.
For example, architects and administrators can:
•
•
•
10
Create a service or add a server:
◦
Add new servers to a cluster or add servers for load balancing.
◦
Add a server to a backup service.
◦
Send approval notices.
Remove a server or service:
◦
Gracefully shut down applications and the operating system.
◦
Remove a server from a cluster or load balancing.
◦
Suspend server monitoring.
Resume a server or service:
◦
Add a server to a cluster or load balancing.
◦
Resume server monitoring.
Introduction to the HP Matrix Operating Environment
For information about what is covered in the limited operations orchestration license, see “HP
Operations Orchestration limited license” (page 22).
For more information about Matrix infrastructure orchestration, see the list of documents under
“Related information” (page 44).
For information on provisioning resources to a public cloud service in Matrix infrastructure
orchestration and the managed instance license that is required, see “Matrix OE public cloud
managed instance licenses” (page 24).
HP Matrix Operating Environment recovery management
Matrix recovery management provides simplified disaster recovery of logical servers and Matrix
infrastructure orchestration services. With a mouse click, you can transfer application environments
running on HP BladeSystems or on virtual machines to a remote recovery site. Logical servers and
Matrix infrastructure orchestration services (IO services) that are included in a Matrix recovery
management configuration are referred to as DR Protected logical servers and IO services.
A Matrix recovery management configuration consists of two sites, each managed by the HP Matrix
Operating Environment The site where the CMS you are logged into is located is referred to as
the Local Site, and the other site in the Matrix recovery management configuration is referred to
as the Remote Site . Matrix recovery management pairs symmetrically configured logical servers
or IO services across the two sites. One logical server or IO service in the pair is activated at one
site, while the other ( peer logical server or IO service) is deactivated at the other site. The boot
images of these DR Protected logical servers and IO services, including applications code and
data, reside on disk array volumes. The source volumes at the site where one of the logical servers
or IO services in the pair is activated are replicated at the other site where its peer logical server
or IO service is deactivated.
These volumes are part of a Storage Replication Group that uses storage array supported replication.
One or more logical servers or IO services can be associated with a single Storage Replication
Group – this is referred to as a Recovery Group
Recovery Groups can be failed over from one site to the other site in a Matrix recovery management
configuration. For example, if a disaster occurs at the Local Site, the administrator at the Remote
site can trigger a failover for all the Recovery Groups that were activated at the Local Site by
activating them at the Remote site. This prepares the storage associated with the deactivated DR
Protected logical servers and IO services at the Remote site for read-write access, and activates
those logical servers and IO services.
Matrix recovery management is only supported on a CMS running Microsoft Windows.
For more information, see the HP Matrix Operating Environment Recovery Management User Guide
available at http://www.hp.com/go/matrixoe/docs.
HP Storage Provisioning Manager
HP Storage Provisioning Manager (SPM) is a software tool that provides a service-centric
management interface to storage, allowing storage requests to be fulfilled with available storage
services from a storage catalog. It securely automates storage management tasks alongside the
Matrix OE visualization software. After storage policies and storage resources are input to the
storage catalog using the SPM user interface, you can use the Matrix OE logical server management
to request and have storage set up to meet server needs.
For more information, see the HP Storage Provisioning Manager (SPM) User Guide, and the Faster
storage provisioning in an HP BladeSystem Matrix and Insight Dynamics environment white paper
available at http://www.hp.com/go/matrixoe/docs.
Application Discovery
Application Discovery helps you identify and learn about the applications and processes running
in your data center or computing network.
Components of Matrix OE
11
With Application Discovery, you can do the following:
•
Discover the location and number of recognized, running, and installed applications in your
network or data center.
•
Monitor the activity and resource usage of running processes and applications.
•
Define and adapt application templates to your environment for better discovery of your
third-party and custom applications, and to make them available for adding to monitored
workloads.
•
Select the event types for which you want to receive notifications and set their level of
importance.
For more information about Application Discovery, see the Application Discovery User Guide,
available at http://www.hp.com/go/matrixoe/docs.
HP Global Workload Manager (gWLM)
This application improves both workload performance and resource utilization in a shared computing
environment. For servers partitioned with nPartitions, virtual partitions, virtual machines, PSETS, or
FSS groups, gWLM can do the following:
•
Monitor each application.
•
Determine the CPU resources needed by each application.
•
Automatically migrate CPU resources between partitions to where they are needed most. This
migration improves application performance by making more resources available to the
application at times of peak demand. In addition, migrating idle resources to the applications
that are busy increases processor utilization.
To access gWLM from the Matrix OE visualization screen, click the Shared Resource Domain tab
or select one of the items under Tools→Global Workload Manager from the Matrix OE visualization
menu bar.
For more information about gWLM, see the HP Global Workload Manager User Guide, available
at http://www.hp.com/go/matrixoe/docs.
HP Instant Capacity software
The Instant Capacity Manager (iCAP Manager) is a web-based interface that can be used to
monitor your Instant Capacity environment. There are several screens available in iCAP Manager,
including an overview of the Instant Capacity resources available, a Global Instant Capacity
(GiCAP) group manager screen to provide more insight into the group managers, and detail screens
for GiCAP groups and Instant Capacity complexes and hosts.
You can get to iCAP Manager in either of the following ways:
•
From the Matrix OE Visualization tab, click the Instant Capacity technology link associated
with any managed system that has Instant Capacity components, TiCAP capacity, or is a
member of a GiCAP group.
•
Select Tools→Instant Capacity Manager from the Matrix OE visualization menu bar.
For more information about Instant Capacity software, see the iCAP Manager help.
Partition Manager
Partition Manager provides system administrators with a convenient graphical user interface to
configure and manage nPartitions on HP servers. Using Partition Manager, you can perform
configuration tasks without having to remember commands and parameters. You select nPartitions,
cells, I/O chassis or other components from the graphical display, then select an action from a
menu.
You can use Partition Manager to perform the following tasks:
12
Introduction to the HP Matrix Operating Environment
•
Create, modify and delete nPartitions.
•
Examine the nPartition configuration of a complex.
•
Check the complex for potential configuration and hardware problems.
•
Manage hardware resources on the complex.
For more information about Partition Manager, see the Partition Manager help.
HP Integrity Virtual Server Manager
Integrity Virtual Server Manager is the GUI that you can use from your browser to manage Integrity
VM resources. Integrity Virtual Server Manager allows you to create, configure, and evaluate
virtual machines, and monitor and evaluate data and resources at the level of the VM Host. You
can view all the VM Host's virtual machines and their assigned resources, and you can view all
resources assigned to a specific virtual machine or virtual switch. For example, Integrity Virtual
Server Manager provides graphical views of virtual-to-physical network and storage devices so
that you can view I/O data, including resource utilization information. Integrity Virtual Server
Manager obtains information about Integrity VM resources through Web-Based Enterprise
Management (WBEM) providers installed on the VM Host.
For more information about Integrity Virtual Server Manager, see the HP Integrity Virtual Server
Manager User Guide, available at http://www.hp.com/go/matrixoe/docs.
HP Matrix KVM Private Cloud
HP Matrix KVM Private Cloud enables the provisioning of virtual machine instances on KVM (Linux
kernel-based virtual machine) hosts in a virtual data center (a cloud) using Matrix infrastructure
orchestration templates and self-service portal processes. It provides automatic detection and
accelerated integration of KVM hosts, and includes a health monitoring subsystem to provide
up-to-date information about KVM hosts.
Matrix KVM Private Cloud has adopted OpenStack, an open-source technology for cloud computing
software to build private, public, and hybrid cloud solutions deployed by enterprises and service
providers.
The Matrix KVM Private Cloud environment consists of:
•
A management appliance running the HP Matrix KVM Admin Console. The appliance is
hosted on a single KVM management host or a two-node failover KVM management cluster
in a High Availability design.
•
A set of compute nodes under the exclusive control of the management appliance. The compute
nodes run on physical Red Hat Enterprise Linux 6.3 KVM hosts.
For more information, see the HP Matrix KVM Private Cloud Getting Started Guide, available at
http://www.hp.com/go/matrixoe/docs.
Product configurations
The software is installed on a CMS running HP SIM, which provides a browser-based user interface.
A single CMS can be used to manage different types of systems. The software is installed on the
CMS once, regardless of how many or what types of managed system licenses are purchased.
Licenses for the managed systems are maintained on the CMS.
For additional information about licensing, see “License management” (page 19).
IMPORTANT: This table is a summary. Specific supported hardware and software configurations
are provided in the HP Insight Management Support Matrix, which is available at http://
www.hp.com/go/matrixoe/docs.
Product configurations
13
Table 1 Matrix OE software
Matrix OE software
Managed systems supported
CMS platform
• HP ProLiant servers running
Microsoft Windows or Linux
HP Matrix OE for ProLiant
• HP BladeSystem c-Class ProLiant
Server Blades running Microsoft
Windows or Linux
• Virtual machines and VM hosts
running under VMware ESX,
VMware ESXi, or Microsoft
Hyper-V on HP ProLiant hosts
HP Matrix OE for non-HP servers
• Virtual machines and VM hosts
running under VMware ESX,
VMware ESXi, or Microsoft
Hyper-V on selected non-HP hosts
• HP ProLiant server running Microsoft
Windows
• HP BladeSystem c-Class ProLiant
Server Blade running Microsoft
Windows
• Virtual machine running Microsoft
Windows running under VMware
ESX or Microsoft Hyper-V on HP
ProLiant or selected non-HP host
• Selected non-HP servers running
Microsoft Windows or Linux
HP Matrix OE for Integrity
• HP Integrity servers running HP-UX, • HP ProLiant server running Microsoft
Windows
HP OpenVMS, Integrity Linux, or
Microsoft Windows for Integrity
• HP BladeSystem c-Class ProLiant
Server Blade running Microsoft
• HP Integrity Server Blades running
Windows
HP-UX, HP OpenVMS, Integrity
Linux, or Microsoft Windows for
• Microsoft Windows virtual machine
Integrity
running under VMware ESX or
Microsoft Hyper-V on HP ProLiant or
• nPartitions running HP-UX, Integrity
selected non-HP host
Linux, or Microsoft Windows for
Integrity
• HP Integrity server running HP-UX
• Virtual machines running under
• HP Integrity Server Blade running
Integrity VM
HP-UX
• Virtual partitions running under a • HP-UX virtual machine running under
vPars monitor
Integrity Virtual Machines
Matrix OE features
The specific features supported by Matrix OE depend on the type of CMS on which the software
is running.
14
•
Table 2 (page 15) summarizes the features supported for different types of managed systems
using a CMS running Microsoft Windows.
•
Table 3 (page 17) summarizes the features supported for different types of managed systems
using a CMS running HP-UX.
Introduction to the HP Matrix Operating Environment
Table 2 Matrix OE features on Windows CMS
Feature
Managed systems/instances supported
Visualize and monitor physical and virtual resources and
workloads using Matrix OE visualization
• HP ProLiant servers running Microsoft Windows or Linux
• HP BladeSystem c-Class ProLiant Server Blades running
Microsoft Windows or Linux
• Virtual machines and VM Hosts running under VMware
ESX, VMware ESXi, or Microsoft Hyper-V on HP ProLiant
and supported non-HP servers
• Selected non-HP servers running Microsoft Windows or
Linux
• HP Integrity servers running HP-UX, Integrity Linux, or
Microsoft Windows for Integrity
• HP Integrity server blades running HP-UX, Integrity Linux,
or Microsoft Windows for Integrity
• Virtual machines running under Integrity VM
• Virtual partitions running under a vPars monitor
Perform capacity analysis and planning using Capacity
Advisor
• HP ProLiant servers running Microsoft Windows or Linux
• HP BladeSystem c-Class ProLiant Server Blades running
Microsoft Windows or Linux
• Virtual machines and VM Hosts running under VMware
ESX, VMware ESXi, or Microsoft Hyper-V on HP ProLiant
and supported non-HP servers
• Selected non-HP servers running Microsoft Windows or
Linux
• HP Integrity servers running HP-UX, Integrity Linux, or
Microsoft Windows for Integrity
• HP Integrity server blades running HP-UX, Integrity Linux,
or Microsoft Windows for Integrity
• Virtual machines running under Integrity VM
• Virtual partitions running under a vPars monitor
• Servers licensed for HP Capacity Advisor Consolidation
software 1
Visualize and monitor logical servers: server profiles that
can be easily created and freely moved
• HP BladeSystem c-Class ProLiant Server Blade running
Microsoft Windows 2
• Virtual machines running Microsoft Windows under
VMware ESX, VMware ESXi, or Microsoft Hyper-V on
HP ProLiant and supported non-HP servers
• HP Integrity server blades running HP-UX, Integrity Linux,
or Microsoft Windows for Integrity 2
• Virtual machines running under Integrity VM
Provision logical servers using Matrix infrastructure
orchestration3
• HP BladeSystem c-Class ProLiant Server Blades running
Microsoft Windows 2
• Virtual machines running Microsoft Windows under
VMware ESX, VMware ESXi, or Microsoft Hyper-V on
HP ProLiant and supported non-HP servers
• HP Integrity server blades running HP-UX, Integrity Linux,
or Microsoft Windows for Integrity
• Managed instances on public cloud services HP Cloud
Compute Services, Amazon EC2 Web Services, and
Savvis Virtual Private Data Center (VPDC) services
• Matrix KVM Private Cloud
• CloudSystem Foundation
Matrix OE features
15
Table 2 Matrix OE features on Windows CMS (continued)
Feature
Managed systems/instances supported
Enable site-to-site fault recovery of logical servers using HP • HP BladeSystem c-Class ProLiant Server Blades running
Matrix Operating Environment recovery management
Microsoft Windows 2
• Virtual machines running Microsoft Windows under
VMware ESX, VMware ESXi, or Microsoft Hyper-V on
HP ProLiant servers
Identify and monitor running applications and processes
using Application Discovery
• HP Integrity servers running HP-UX or Integrity Linux
4
• HP Integrity server blades running HP-UX or Integrity
Linux 4
• Virtual machines running under Integrity VM
• Virtual partitions running under a vPars monitor
Manage workloads with automated policies using HP
Global Workload Manager (gWLM)
• HP Integrity servers running HP-UX
• HP Integrity server blades running HP-UX
• Virtual machines running under Integrity VM
• Virtual partitions running under a vPars monitor
Manage HP Integrity virtual machines using Integrity Virtual • Virtual machines running under Integrity VM
Server Manager
• Integrity Virtual Machine VM hosts
Manage nPartitions and cell-based servers using Partition
Manager
• HP Integrity cell-based servers and nPartitions
Monitor HP Instant Capacity Manager resources (iCAP,
GiCAP, and TiCAP) using Instant Capacity Manager
• HP Integrity servers with HP Instant Capacity Manager
products installed
Manage HP Serviceguard clusters using Serviceguard
Manager
• HP Integrity servers with HP Serviceguard installed
1
Analysis queries do not work with HP Capacity Advisor Consolidation software.
2
Requires HP Virtual Connect Enterprise Manager on BladeSystem enclosure.
3
If you add custom console links in Matrix infrastructure orchestration, you will need to configure your client machine.
You must define a URI protocol handler and install associated software, depending on the type of console access (such
as SSH, VNC, telnet, ...). These must be in place before executing the custom console links. For more information about
defining custom console links in hpio.properties file, see the HP Matrix Operating Environment Infrastructure
4
16
Orchestration User Guide.
Integrity Linux support limited to Red Hat Enterprise Linux 4.x and 5.x and SUSE Linux Enterprise Server 10.x.
Introduction to the HP Matrix Operating Environment
Table 3 Matrix OE features on an HP-UX CMS
Feature
Managed systems supported
Visualize and monitor physical and virtual resources and
workloads using HP Matrix OE visualization
• HP Integrity servers running HP-UX, Integrity Linux, or
Microsoft Windows for Integrity
• HP Integrity server blades running HP-UX, Integrity Linux,
or Microsoft Windows for Integrity
• Virtual machines running under Integrity Virtual Server
Manager
• Virtual partitions running under a vPars monitor
Perform capacity analysis and planning using HP Capacity • HP Integrity servers running HP-UX, Integrity Linux, or
Advisor
Microsoft Windows for Integrity
• HP Integrity server blades running HP-UX, Integrity Linux,
or Microsoft Windows for Integrity
• Virtual machines running under Integrity Virtual Server
Manager
• Virtual partitions running under a vPars monitor
Identify and monitor running applications and processes
using Application Discovery
• HP Integrity servers running HP-UX or Integrity Linux
1
• HP Integrity server blades running HP-UX or Integrity
Linux 1
• Virtual machines running under Integrity Virtual Server
Manager
• Virtual partitions running under a vPars monitor
Manage workloads with automated policies using HP
Global Workload Manager (gWLM)
• HP Integrity servers running HP-UX
• HP Integrity server blades running HP-UX
• Virtual machines running under Integrity Virtual Server
Manager
• Virtual partitions running under a vPars monitor
Manage HP Integrity virtual machines using HP Integrity
Virtual Server Manager
• Virtual machines running under Integrity Virtual Server
Manager
• HP Integrity hosts running HP Integrity Virtual Machines
Manage nPartitions and cell-based servers using Partition
Manager
• HP Integrity cell-based servers and nPartitions
Monitor HP Instant Capacity Manager resources (iCAP,
GiCAP, and TiCAP) using HP Instant Capacity software
• HP Integrity servers with HP Instant Capacity Manager
products installed
Manage HP Serviceguard clusters using Serviceguard
Manager
• HP Integrity servers with HP Serviceguard installed
1
Integrity Linux support limited to Red Hat Enterprise Linux 4.x and 5.x and SUSE Linux Enterprise Server 10.x
Matrix OE features
17
18
2 License management
This chapter describes the licensing models and types of licenses available for Matrix OE, and
explains how to add and apply licenses.
Two categories of Matrix OE licenses are available: for on-site managed systems and for public
cloud managed instances.
End-user license agreement
Your use of Matrix OE is subject to the terms of the end-user license agreement included with the
software. Read this document at its installed location on the CMS:
HP-UX CMS
/opt/vse/src/README
Microsoft Windows CMS
installation-directory\src\README
The default installation directory is C:\Program Files\HP\
Virtual Server Environment, but this directory can be
changed at installation time.
Matrix OE managed system licenses
Matrix OE is licensed for use on managed systems as shown in Table 4 (page 19). Licenses are
managed from the CMS using the HP SIM License Manager database.
Matrix OE managed system licensing model
Table 4 Matrix OE managed system license requirements
System type
License requirement 1
HP Integrity Server
License per CPU socket or core
2
HP 9000 Server
License per CPU socket or core
2
HP ProLiant ML/DL/SL Server
License per system
HP BladeSystem c-Class enclosure
No enclosure license required or available. Licenses apply
to individual server blades.
HP BladeSystem c-Class ProLiant Server Blade
License per server blade
HP Integrity server blade
License per CPU socket or core
Virtual machines running under any of the following:
Covered by host server license
2
• HP Integrity Virtual Machines
• VMware ESX
• VMware ESXi
• Microsoft Hyper-V
• Matrix KVM Private Cloud
1
2
The HP Insight Capacity Advisor Consolidation software license is always licensed per system, regardless of system type.
See “HP Capacity Advisor Consolidation software license” (page 21).
Trial licenses are licensed per system. See “Managed system trial licenses” (page 22).
NOTE:
Additional product licenses might be required, depending on your installation.
To obtain a permanent License To Use (LTU) for Matrix OE, contact your HP sales representative,
your HP services representative, or your authorized HP reseller. The available licenses are listed
in the sections that follow.
End-user license agreement
19
To use a purchased license, it must be added to the HP SIM License Manager database on the
CMS and then applied to a managed system.
Licensed Matrix OE products on managed systems
The tables in the following sections summarize the licensed Matrix OE products and the platforms
on which they are available.
For detailed hardware and software configurations supported by Matrix OE, see the HP Insight
Management Support Matrix, available at http://www.hp.com/go/insightmanagement/docs.
HP ProLiant servers and ProLiant server blades
Table 5 Licensed Matrix OE products: For ProLiant servers
License name
Licensed products
Supported OS
HP Matrix OE for ProLiant
• HP Matrix OE visualization1, 2
• Microsoft Windows
• HP Capacity Advisor
• Linux
3
• HP Insight Control
• HP Insight Control virtual machine
management
• HP Insight Control server migration
• HP Insight Control power
management
• HP Matrix Operating Environment
infrastructure orchestration1
• HP Matrix Operating Environment
recovery management1
• IC server provisioning
1
2
3
HP Matrix OE logical server management, HP Matrix Operating Environment infrastructure orchestration, and HP Matrix
Operating Environment recovery management are only supported on a CMS running Microsoft Windows.
A license for HP Virtual Connect Enterprise Manager is required for BladeSystem enclosures to manage logical servers
on server blades.
A license for HP Insight Control is required. The Insight Control license includes HP Insight Control virtual machine
management, HP Insight Control server migration, HP Insight Control power management, and HP iLO.
HP Integrity and HP 9000 servers and Integrity server blades
Table 6 Licensed Matrix OE products: For Integrity servers
License name
1
HP Matrix OE for Integrity
Licensed products
Supported OS
• HP Matrix OE visualization
• HP-UX
• HP Capacity Advisor
• HP Global Workload Manager
(gWLM)
• HP Insight Control virtual machine
management
HP Matrix OE visualization2, 3, 4
20
License management
• HP Matrix OE visualization
• HP-UX
• HP Insight Control virtual machine
management
• Microsoft Windows for HP Integrity
• Linux for HP Integrity
Table 6 Licensed Matrix OE products: For Integrity servers (continued)
License name
Licensed products
Supported OS
HP Capacity Advisor5
• HP Matrix OE visualization
• HP-UX
• HP Capacity Advisor
• Microsoft Windows for HP Integrity
• HP Insight Control virtual machine
management
• Linux for HP Integrity
• HP Matrix OE visualization
• HP-UX
HP Global Workload Manager
(gWLM)
• HP Global Workload Manager
(gWLM)
• HP Insight Control virtual machine
management
1
2
3
4
5
A license for HP Matrix Operating Environment infrastructure orchestration for Integrity is included with the HP-UX VSE
and DC Operating Environments.
Includes logical server management, supported on a CMS running Microsoft Windows
Matrix OE logical server management, HP Virtual Connect Enterprise Manager, HP Matrix Operating Environment
recovery management and HP Matrix Operating Environment infrastructure orchestration are only supported on a CMS
running Microsoft Windows.
A license for HP Virtual Connect Enterprise Manager is required for BladeSystem enclosures to manage logical servers
on server blades.
A license for Integrity iLO 3 Advanced is recommended to collect advanced power information for visualization meters
and capacity planning.
Non-HP servers
Table 7 Licensed Matrix OE products: For non-HP servers
License name
Licensed products
Supported OS
HP Matrix OE for non-HP servers
• HP Matrix OE visualization1, 2
• Microsoft Windows
• HP Capacity Advisor
• Linux
• HP Insight Control virtual machine
management
• HP Matrix Operating Environment
infrastructure orchestration3
• HP Matrix Operating Environment
recovery management 4, 5
1
Matrix OE logical server management is only supported on a CMS running Microsoft Windows.
2
Support for logical servers on non-HP hardware is limited to virtual machines.
3
HP Matrix Operating Environment infrastructure orchestration is only supported on a CMS running Microsoft Windows.
4
A license for HP Matrix Operating Environment recovery management is included, but recovery management is not
supported on non-HP servers in this release of Matrix OE.
HP Matrix Operating Environment recovery management is only supported on a CMS running Microsoft Windows.
5
HP Capacity Advisor Consolidation software license
The HP Capacity Advisor Consolidation software license allows you to collect data from systems
that you are planning to consolidate. This license is only needed on managed systems that do not
have a license for Capacity Advisor or Matrix OE. Systems with this license are not included in
the analysis performed by the Capacity Analysis tool.
Matrix OE managed system licenses
21
Table 8 Capacity Advisor Consolidation software license
License name
Licensed products
Supported platforms
HP Capacity Advisor Consolidation
software
HP Capacity Advisor1, 2
Servers running HP-UX 11i, Microsoft
Windows for Integrity, x86-based
Microsoft Windows Server, or Linux
1
License is valid for six months after it is assigned to a system.
2
Does not include license for Matrix OE visualization. Systems with only this license will not be visible in visualization.
HP Operations Orchestration limited license
Matrix OE comes with a version of Operations Orchestration that is licensed for limited uses. It is
launched from Matrix infrastructure orchestration and used to trigger workflows that can be
performed before or after IO operations.
This restricted version of operations orchestration:
•
Is licensed for only one author. An upgrade to the full version of operations orchestration
allows for multiple authors.
•
Can only be used for pre- and post-provisioning workflows and workflow troubleshooting. An
upgrade to the full version of operations orchestration allows you to schedule the launch of
operations orchestration workflows outside of Matrix OE.
•
Provides a subset of the content that is available in the full version of operations orchestration.
This subset is related to Infrastructure-as-a-Service workflows. An upgrade to the full version
of the software provides additional content.
•
Allows Matrix OE to be integrated with other management software. However, this requires
additional services from HP consulting.
License requirements for managed systems with Instant Capacity products
For systems using Instant Capacity products (including iCAP, GiCAP, and TiCAP), the total number
of licenses assigned across all nPartitions within the complex (or across multiple complexes when
using GiCAP) must be equal to or greater than the total number of processors that you have
purchased.
Managed system trial licenses
The following trial licenses are available:
•
When Matrix OE is installed on the CMS, 10 trial licenses for HP Matrix OE for Integrity are
included in the License Manager database. These licenses can be applied to HP Integrity and
HP 9000 systems. Each trial license is valid for 90 days after it is applied to a managed
system. To continue to manage these systems beyond the trial period, you must purchase
permanent licenses.
These trial licenses can be applied to managed systems by the Insight managed system setup
wizard or by the vselicense command. They cannot be applied through HP SIM License
Manager. For information about the managed system setup wizard, see “Recommended
process: Use the managed system setup wizard” (page 23). For information about
vselicense, see “Command reference” (page 51).
•
Matrix OE trial licenses for 10 managed systems can be obtained by registering with HP. To
obtain these trial licenses, contact your HP sales representative, your HP services representative,
or your authorized HP reseller.
You can view the status of your trial licenses using the HP SIM License Manager. For information
about License Manager, see “Alternative process: Use HP SIM License Manager” (page 23).
22
License management
Adding and applying managed system licenses
To use a purchased license, you must first add it to the HP SIM License Manager database on the
CMS, then apply the license to a specific managed system. The CMS keeps track of how many of
each type of license are available to be applied to managed systems. As you apply licenses, the
number of available licenses decreases.
Recommended process: Use the managed system setup wizard
HP recommends using the Insight managed system setup wizard to add and apply licenses for
Matrix OE. To start the managed system setup wizard, select Configure→Managed System Setup
Wizard... from the top menu bar. Help is available in each step of the wizard. For more information
about the managed system setup wizard, see “Using the HP Insight managed system setup wizard”
(page 27), and the Insight Managed System Setup Wizard Getting Started Guide available from
Enterprise Information Library.
Alternative process: Use HP SIM License Manager
If you choose not to use the Insight managed system setup wizard, you can use the HP SIM License
Manager to add and apply most types of licenses. You can also use License Manager to view the
available and applied licenses for all products in the License Manager database. To use the License
Manager, you must have administrative rights on the CMS.
Some licenses cannot be applied through License Manager:
•
Trial licenses can only be applied to managed systems by the Insight managed system setup
wizard or by the vselicense command. For information about vselicense, see “Command
reference” (page 51).
•
LTUs from earlier versions of the VSE Management Software for Integrity or from the HP-UX
VSE or DC operating environments are managed using the vselicense command or the
“Scan for HP-UX Licenses” tool. For more information, see “Scan for HP-UX licenses ” (page 24).
Setting authorizations
To add and apply licenses, you must have administrative rights on the CMS and you must be
authorized for the All Tools toolbox on the managed systems that you want to license. To assign
administrative rights to an HP SIM user, select Options→Security→Users and Authorizations→User.
Select the user and click Edit. In the Edit form, select the check box for User can configure CMS
security access such as creating, modifying or removing other users. To enable the All Tools toolbox
for the user, select Options→Security→Users and Authorizations→Authorizations and click New.
In the New Authorizations form, select the user, the All Tools toolbox, and the system.
Starting the License Manager
To start License Manager, select Deploy→License Manager... from the top menu bar. This menu
selection will only be available if you have administrative rights on the CMS. Online help is available
to guide you through the use of License Manager.
The License Manager lists all the available license types from which you can choose to deploy.
Order for applying licenses—Windows CMS managed systems
For systems that will be managed by a CMS running Microsoft Windows, applying licenses in the
proper order will simplify the process and reduce errors. From the Windows CMS, apply licenses
to each managed system in the order shown for each system type:
HP BladeSystem c-Class ProLiant
1. HP iLO Advanced
Server Blade
2. VCEM (enclosure license required for logical server
management of server blades)
3. Insight Control
4. Matrix OE
Matrix OE managed system licenses
23
HP ProLiant ML/DL/SL server
1.
2.
3.
HP iLO Advanced
Insight Control
Matrix OE
HP BladeSystem c-Class Integrity
Server Blade
1.
VCEM (enclosure license required for logical server
management of server blades)
Matrix OE
2.
Scan for HP-UX licenses
From a CMS, use the Scan for HP-UX Licenses task to perform the following functions:
•
Enable the HP Matrix Operating Environment for HP-UX licenses that are included in the HP-UX
Operating Environments.
•
Migrate unused licenses that were purchased for an earlier release to the HP SIM License
Manager database and apply them to your managed systems (if permitted by your licensing
agreement with HP).
To launch this task from the License Manager, click Scan for HP-UX Licenses... on the last Deploy:
HP Matrix OE for Integrity Licenses screen. On the Task Confirmation screen, click Run Now. Online
help is available to guide you through the operation.
This task scans for licenses for any VSE Management Software or Matrix OE for Integrity LTU that
is installed on the managed systems. It is not restricted to the type of license that was originally
selected in License Manager. It only discovers licenses on HP-UX systems, even if other types of
systems were included in the License Manager system selection. For more information about
scanning for HP-UX licenses and migrating unused licenses from earlier software versions, see
“Command reference” (page 51).
Using the CMS password reconfigure tool
The CMS reconfigure tool provides a command that enables you to quickly change passwords for
many licensed systems at once. For information on the CMS reconfigure tool and how to use the
command with the Matrix OE, see the HP Systems Insight Manager User Guide at http://
www.hp.com/go/insightmanagement/sim/docs.
Matrix OE public cloud managed instance licenses
Public cloud instances, along with on-premise systems, are part of the Matrix OE managed
environment, and must be licensed accordingly. Once licensed, public cloud instances can also
be supported as part of the Matrix OE managed infrastructure.
Bursting to external clouds
Cloud bursting is a feature of HP CloudSystem that enables enterprises to broker service delivery
across multiple clouds from a single, integrated point of control. With CloudSystem bursting
enterprises can design, catalog, provision, control, and monitor infrastructure services uniformly
across complex hybrid cloud environments. As a result, businesses can more easily, safely, and
cost effectively supplement internal resources with public cloud resources to meet extra capacity
demands, to extend geographic reach, or to leverage specialized infrastructure service offerings.
Matrix OE currently supports the following public cloud services:
•
HP Cloud Compute Services
•
Amazon EC2 Web Services
•
HP CloudAgile Certified bursting destinations
CloudSystem can also utilize compute resources of other CloudSystem Matrix systems that are
running the Matrix Bursting Connecter (version 7.2 and later).
24
License management
Resources accessible via these services are represented as Cloud Resources inside Matrix OE.
Cloud Resources can be added to a server pool in the same way as any other VM Host or ESX
Resource Pool.
Two white papers provide more detailed descriptions. They explain how to configure Matrix OE
for bursting and how to provision to an external cloud with Matrix infrastructure orchestration.
•
Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services
or Amazon EC2
•
Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis
Both of these white papers are available in the Matrix OE information library (http://www.hp.com/
go/matrixoe/docs).
Managing Public Cloud instances with Matrix OE
With Matrix OE, every traditional, node-based Matrix OE license includes rights to manage one
public cloud instance at an HP-supported public cloud service provider. Additional public cloud
instances may be managed through the acquisition of Matrix OE public cloud managed instance
licenses.
Each Matrix OE Public Cloud Managed Instance license allows you to manage one public cloud
instance hosted at an HP-supported public cloud service provider. The license term is one year
from the license purchase date. Matrix OE public cloud instance license are not keyed, and are
not managed under the HP SIM License Manager.
Multiple licenses can be used together under a concurrent use model. For example, if you purchase
10 licenses, you can manage up to 10 public cloud instances at any one time.
Public cloud managed instance licenses are not tied to a particular service provider. You can use
the same license to manage an instance at one service provider today and another tomorrow, as
long as the license is not used for both instances at the same time.
For details on licensing, contact your HP sales representative.
Matrix OE public cloud managed instance licenses
25
26
3 Getting started
Installing the software
This document does not cover installation of the software or upgrade from previous versions of the
software. For installation and upgrade on a CMS running Microsoft Windows, see HP Insight
Management Preinstallation Worksheet, HP Insight Management Quick Installation Guide, and
HP Insight Management Installation and Configuration Guide. For installation and upgrade on a
CMS running HP-UX, see the HP Matrix Operating Environment Integrity CMS Installation and
Configuration Guide.
Configuring privilege elevation
Some Matrix OE management functions require privileged (root) access from the CMS to HP-UX,
Linux, and VMware ESX managed systems. Privilege elevation allows you to use your preferred
mechanism for acquiring root permissions as needed (for example, using sudo or PowerBroker),
without having to allow login through the root account.
Procedure 1 Configuring privilege elevation for use with Matrix OE
1.
2.
3.
Select Options→Security→Privilege Elevation... from the top menu.
Select Enable privilege elevation for Linux and HP-UX (or VMware ESX, according to the type
of managed system OS).
Select the elevation tool type from the menu.
IMPORTANT: Matrix OE does not support the option A password is required for this privilege
elevation tool. Make sure this option is not selected.
4.
Select Use this user and enter a user name to be used to access all managed systems with this
type of operating system. You also must enable the selected user login on the managed systems.
Additional configuration might also be needed. For example, you might need to configure SSH
access using Configure→Configure or Repair Agents..., and you might need to configure the
managed system to allow host authentication for non-root users. For more information, see the HP
Systems Insight Manager Help, mxagentconfig(1M), and the Insight Management and Matrix OE
installation and configuration guides. Links to these documents can be found in “Related information”
(page 44).
Using the HP Insight managed system setup wizard
Insight managed system setup wizard configures systems to enable them to be managed by HP
SIM and its plug-in applications, including Matrix OE. Use the managed system setup wizard for
initial configuration or re-configuration of any selected set of systems. After you specify which
management features you want to use on the selected systems, the wizard analyzes the current
configuration of each system and performs the following functions:
•
Installs any agents necessary to enable the selected management features.
•
Applies any required licenses from the set of licenses available in the License Manager
database.
•
Completes additional configuration steps required by the features that you selected.
After initial configuration, you can run the managed system setup wizard again at any time to
modify the selected management features and change the configuration.
For more information about the managed system setup wizard, see the HP Insight Managed System
Setup Wizard Getting Started Guide, available at http://www.hp.com/go/matrixoe/docs.
Installing the software
27
Configuring user authorizations
Users must be authorized in HP SIM to use Matrix OE tools and features. Information about Matrix
OE user authorizations is available in the Matrix Operating Environment online help, with additional
information provided in the Matrix OE component help.
Configuring data collection credentials
Systems that are to be managed using Matrix OE or simulated for capacity planning and analysis
must be configured to allow data collection from the CMS. In general, data collection can be
enabled either through the Utilization Provider (UP) installed on the managed system, or through
native data collection. For a description of the two methods, see the section “Comparison of
agentless and UP data collection” in the HP Capacity Advisor User Guide.
Authentication is required to enable data collection. The required credentials are summarized in
Table 9 (page 28). You can verify or modify the WBEM or SSH credentials for a system that has
been discovered in HP SIM by selecting Options→Security→Credentials→System Credentials...
from the top menu bar.
Table 9 Data collection credentials requirements
Managed system OS / Data Collection
Method
Required access credentials
HP-UX/Utilization Provider
Required access level
WBEM credentials must be configured Non-root or root
(or discovered) in HP SIM for these
systems
Integrity Windows, (physical server or WBEM credentials must be configured Does not require Administrator level
VM), from an HP-UX CMS/Utilization (and discovered or identified) in HP
access
Provider
SIM for these systems
Windows physical server from a
Windows CMS/Agentless
WBEM credentials must be configured WBEM login must be a member of the
(or discovered) in HP SIM for these
Administrators group on these systems
systems
x86 Linux physical server or Integrity
Linux (physical server or
VM)/Agentless
SSH credentials or certificate-based
Non-root or root credentials, or
SSH authentication must be configured certificate-based authentication may be
(or discovered) in HP SIM for these
used
systems
Note
On a Windows CMS, any VMware ESX and Microsoft Hyper-V hosts must be properly registered in Insight Control
virtual machine management to allow data collection from these hosts and their virtual machines. For information about
registering the hosts in Insight Control virtual machine management, see HP Insight Control Virtual Machine Management
User Guide.
About the HP Capacity Advisor Data Collection Service
In Capacity Advisor, collection of resource usage data is managed by a service. The service gathers
data provided by the Utilization Provider and native data collectors and normalizes it into five-minute
data points. The service starts automatically on installation and runs constantly unless
stopped—providing data for visualizing resource use on discovered systems and workloads and
for capacity planning. When needed, the service can be stopped or restarted on the CMS.
Procedure 2 Windows CMS: Stopping the Capacity Advisor Data Collection Service
1.
2.
Select Start→Administrative Tools→Services.
In the Name column, look for “HP Capacity Advisor Data Service.” Right-click on this name
and select Stop.
Procedure 3 Windows CMS: Starting the Capacity Advisor Data Collection Service
1.
28
Select Start→Administrative Tools→Services.
Getting started
2.
In the Name column, look for “HP Capacity Advisor Data Service.” Right-click on this name
and select Start.
Procedure 4 HP-UX CMS: Stopping the Capacity Advisor Data Collection Service
•
From the command line as root, run /sbin/init.d/hp_cpdata_service stop
Procedure 5 HP-UX CMS: Starting the HP Capacity Advisor Data Collection Service
•
From the command line as root, run /sbin/init.d/hp_cpdata_service start
NOTE: The Options→Data Collection menu option (on the top menu bar) allows you to configure
data collection for server inventory only. See “Solving utilization data collection problems” (page 29)
when you suspect resource utilization data is missing or utilization data collection is not working.
Configuring data metrics to better reflect your environment
Capacity Advisor provides tools for making the data metrics displayed in the visualization profile
viewer and in capacity planning scenarios better reflect your computing environment.
•
From the Matrix OE Visualization tab or the Planning tab, select Configure→Global Utilization
Limits to set default limits for utilization of CPU, memory, and disk and network I/O bandwidth
to better reflect your Service Level Agreement.
•
Determine your expected growth rate, then use Configure→Global Forecast... to realistically
project future utilization.
•
Reflect your business cycle(s) by changing the displayed date range in your scenarios and
observing the peak, sustained, 90th percentile, and average data views.
•
On the Visualization tab, use Configure→Calibrate Power (All Selected Systems)... to define
power settings for your systems. You must have full authorization on the managed nodes to
use this function.
Solving utilization data collection problems
Matrix Operating Environment provides a default Events collection called “Utilization Data Collection
Events.”
When you suspect you are experiencing a utilization data collection error, review the event listings
available from this menu. To obtain details about an event, including how to address a problem,
click the event type to open the detail table.
To learn more about how to use event collections, click the
table view page” in the HP Systems Insight Manager Help.
button to read “Navigating the event
To learn more about Capacity Advisor functions, see the HP Capacity Advisor User Guide.
About the HP Capacity Advisor Data Collection Service
29
Removing unneeded agent software
If you have upgraded from a previous version of HP Matrix Operating Environment (formerly known
as HP Insight Dynamics or VSE Management Software), there may be agents installed on some of
your managed systems that are no longer needed. This will occur on managed systems that
previously used the Utilization Provider for data collection and are now configured for agentless
or native data collection. The following types of systems are affected:
•
Integrity Linux or x86 Linux managed systems. In releases prior to version 6.0, these systems
needed the Utilization Provider for data collection. In the current release, these systems will
be configured to use agentless data collection. The Utilization Provider is not supported by
Matrix Operating Environment on Linux managed systems.
•
Microsoft Windows managed systems, but only if you are using a CMS that is also running
Microsoft Windows (agentless data collection from Windows systems is not supported on an
HP-UX CMS).
In these cases, when you use the Insight managed system setup wizard to configure the system,
the following message will be displayed:
Agentless data collection is not configured; it will be configured.
An HP Utilization Provider has been detected; it will not be used
for data collection.
You should remove any sub-OS workloads defined on this system.
NOTE:
Any Windows sub-OS workloads on previous versions where this configuration was supported are
automatically removed during the upgrade of HP Matrix Operating Environment.
You may choose to remove the Utilization Provider from the affected systems after they have been
configured for agentless data collection.
IMPORTANT: Even though Matrix OE will no longer use the Utilization Provider for data collection,
there may be other software installed on the system that still uses it (for example, HP Insight Control
power management). Do not remove the agent if it is still in use.
Procedure 6 Remove the Utilization Provider from a Windows Server 2003 system
1.
2.
3.
From Control Panel, select Add or Remove Programs.
Select “HP WMI Util Provider v1.8.1.1” (or the current installed version).
Click Remove.
Procedure 7 Remove the Utilization Provider from a Windows Server 2008 system
1.
2.
3.
From Control Panel, select Program and Features.
Select “HP WMI Util Provider v1.8.1.1” (or the current installed version).
Click Uninstall.
Procedure 8 Remove the Utilization Provider from a Linux system
1.
2.
Open a command shell with root privileges.
Execute the following command:
rpm -e hp-utilprovider
For more information about agentless data collection, see the section “Comparison of agentless
and UP data collection” in the HP Capacity Advisor User Guide.
Using Matrix OE visualization
Matrix OE visualization provides features that let you visualize and manage physical and virtual
servers discovered and licensed for use within the Matrix Operating Environment. Using
visualization, you can:
30
Getting started
•
Customize the level of detail that you want to see.
•
Easily access additional applications to manage and configure systems and workloads.
•
Centrally configure your server resources for optimum utilization.
•
Manage logical servers.
Starting Matrix OE visualization from HP SIM
Start HP Matrix OE visualization software from HP Systems Insight Manager in any of the following
ways:
•
From the blue HP SIM menu bar, choose Tools→HP Matrix OE visualization...
The first time you start Matrix OE visualization, the Visualization View appears with the default
Physical and Virtual perspective. This perspective shows all physical and virtual systems in
graphical compartments.
When you start Matrix OE visualization subsequent times, the software checks to see if you
had previously set a default view by modifying the user preferences. If you set a collection
(for example, Blade), Matrix OE visualization displays that collection.
If you create a custom collection and set the custom collection to the default collection, and
you later delete that collection and start Matrix OE visualization using the Tools→Matrix OE
visualization menu selection, a blank screen is displayed if you start Matrix OE visualization
quickly (within a minute or two of deleting the collection). If you wait a minute or so, the default
collection is reset to All Matrix OE Resources. Alternatively, you can enter Matrix OE
visualization through the left side menu and change your preference to an existing collection.
•
From the HP Systems Insight Manager Systems and Event Collections list in the left-hand
navigation area, choose Systems→Shared→Systems by Type→All Matrix OE Resources.
•
From the Systems Insight Manager System and Event Collections list in the left-hand navigation
area, expand the All Matrix OE Resources collection by clicking its icon, then choose a
subset such as nPartitions.
•
Create a custom Systems Insight Manager collection whose default view is set to “HP Matrix
OE visualization”. Select this collection to start Matrix OE visualization. This is described
in more detail in “Creating custom collections” (page 36). That section also describes how to
customize Systems Insight Manager to display Matrix OE visualization automatically as soon
as Systems Insight Manager starts.
When you start the Matrix OE visualization from any of the methods listed above, a splash screen
displays as the Matrix OE visualization loads.
Using Matrix OE visualization
31
NOTE: Do not create multiple browser windows in the same session by using Ctrl-N or File→New
Window in Internet Explorer or Firefox. This results in the same session running in both windows
and causes errors in the Matrix OE visualization. Similarly, do not create multiple tabs by using
Ctrl-T or File→New Tab, which also causes problems. You can, however, start multiple browsers
from the desktop icon or the Start button. In this case, a different session can run in each browser,
which will not cause Matrix OE visualization problems.
Matrix OE tabs
Matrix Operating Environment provides five tabs to move among the capabilities offered by Matrix
OE visualization, Capacity Advisor, and Global Workload Manager:
•
Visualization tab – View a visual representation of all managed servers, their relationships to
each other or to an enclosure, and resource usage data for each server. You can easily
navigate to the management application for each server technology. For more information,
see the online help accessible from the Visualization tab.
•
Workload tab – View workloads in association with their servers and their utilization settings,
within a compact table format. See the online help accessible from the Workload tab.
•
Shared Resource Domain tab – View and manage Shared Resource Domains (SRDs) using HP
Global Workload Manager (gWLM). gWLM allows you to centrally define resource-sharing
policies that you can use across multiple HP servers. For more information, see the online help
accessible from the Shared Resource Domain tab and see the HP Global Workload Manager
User Guide.
•
Analysis tab – View built-in Capacity Analysis queries that reflect a current concern or business
interest and create custom analysis queries of collected data. For more information, see the
online help accessible from the Analysis tab and see the HP Capacity Advisor User Guide.
•
Planning tab – View computing resource utilization data and create usage scenarios using
Capacity Advisor. For more information, see the online help accessible from the Planning tab
and see the HP Capacity Advisor User Guide.
Matrix OE menu bar
The Matrix OE menu bar provides convenient access to the Matrix OE tools and actions after
clicking a Matrix OE tab for a given application.
To perform an action on a system or compartment, select its check box, then choose the menu
selection from the Matrix OE menu bar. Some menu selections (such as Create→Workload
Definition...) do not require you to select a system first.
NOTE: Menu selections vary between the Matrix OE visualization tabs (Visualization tab and
Workload tab) and the tabs that take you outside the Matrix OE visualization (the Shared Resource
Domain, Analysis, and Planning tabs). The page title indicates the management application for
the selected tab, for example, Matrix OE visualization or Planning.
Menu selections are disabled if any of the following circumstances exist:
•
A required selection has not been made. For example, Modify→Workload Definition... is
enabled only after you select a workload.
•
Ambiguous selections have been made. For example, if you select more than one workload,
Modify→Workload Definition... is not enabled.
Be sure to select the check box to select the appropriate system or systems before choosing a menu
selection from the Matrix OE menu bar.
The following menu options are available from the Matrix OE menu bar. See the online help for
each menu selection to learn more.
32
Getting started
Table 10 Matrix OE visualization Tools menu
Menu selection
Description
Global Workload Manager
Use the Global Workload Manager task screens to define resource-sharing
policies across multiple HP servers.
→ Getting Started – gWLM Home
→ Manage Systems and Workloads
→ Edit gWLM Policies
→ gWLM Real-time Reports
→ gWLM Historical Reports
→ gWLM Advanced Reports
→ Events
Virtual Connect Enterprise Manager VCEM)
→ VCEM Homepage
Use the Virtual Connect Enterprise Manager task screens to manage Virtual
Connect domains.
→ Add Virtual Connect Domain to Group
→ Remove Virtual Connect Domain from Group
→ Virtual Connect Domain Properties..
→ Virtual Connect Domain Group Properties
Logical Servers
→ Activate...
Manage logical servers in virtualized environments. Logical server actions are
available from a Windows CMS only.
→ Copy...
→ Deactivate...
→ Import...
→ Move...
→ Refresh...
→ Power
HP Matrix OE recovery management...
Provide disaster recovery protection for logical servers configured and managed
by Matrix OE visualization.
HP Matrix OE infrastructure management Service Deploy, manage and monitor the overall behavior of Matrix infrastructure
Details
orchestration and its users, templates, services, resources, and organizations.
Infrastructure orchestration is available on Windows CMS only.
Capacity Planning
→ View Planning Scenarios...
Open profile viewers for visualized systems or to create a capacity planning
scenario using Capacity Advisor.
→ View Capacity Advisor Data...
Process Resource Manager
→ Monitor PRM Groups
Control the amount of computing resources that processes use during peak
system load. Process Resource Manager is available on HP-UX only.
→ Configure PRM Groups
Update System Workloads
Replace all of the monitored workload definitions on the selected managed
system.
Instant Capacity Manager
Monitor all Instant Capacity resources.
Table 11 Matrix OE visualization Create menu
Menu selection
Description
Shared Resource Domain...
Managed systems and workloads defined to be part of a shared resource
domain.
Workload Definition...
Create a monitored workload.
Logical Server...
Create a logical server (Windows CMS only).
Using Matrix OE visualization
33
Table 12 Matrix OE visualization Modify menu
Menu selection
Description
Shared Resource Domain...
Modify the definition of a shared resource domain.
Workload Definition...
Edit properties of a monitored workload.
Logical Server
Edit properties of a logical server (Windows CMS only).
Logical Server Storage Pools...
Edit storage pools for use by logical servers (Windows CMS only).
Logical Server Portability Groups...
Edit properties of portability groups (Windows CMS only).
Logical Server Target Attributes...
Edit target attributes associated with logical servers (Windows CMS only).
→ Manage
→ Copy
Table 13 Matrix OE visualization Delete menu
Menu selection
Description
Shared Resource Domain
Remove an SRD definition from the configuration.
Workload Definition(s)...
Remove an existing workload definition. You will be prompted to confirm the
deletion.
Delete Logical Server...
Remove a logical server (Windows CMS only).
Unmanage Logical Server...
Stop managing a logical server (Windows CMS only).
Table 14 Matrix OE visualization Configure menu
Menu selection
Description
Global Forecast...
Modify parameters in the Capacity Advisor forecast model, which are applied
as the default in resource use trend displays in the profile viewer.
Global Utilization Limits...
Modify utilization limits for CPU and memory use, which are applied by default
to data in resource use displays and data tables in the profile viewer.
Workload Forecast...
Define a forecast model for workloads.
Workload Utilization Limits...
Define utilization limits for workloads.
Calibrate Power (All Selected Systems)...
Calibrate power for selected systems managed by Matrix OE.
Edit Network and Disk I/O Capacity...
Set desired capacity for network and disk I/O bandwidth for selected systems.
Agentless Data Collection...
View systems with agentless data collection or use advanced options.
→ List Agentless Systems
→ Advanced Agentless Options
User Preferences
Modify some aspects of Matrix Operating Environment for personal use.
The following table lists menu selections that you can use to manage policies defined in Global
Workload Manager.
Table 15 Matrix OE visualization Policy menu
Menu selection
Apply gWLM Policy...
Change Associated gWLM Policy...
Edit gWLM Policies...
34
Getting started
Table 15 Matrix OE visualization Policy menu (continued)
Menu selection
Remove Associated gWLM Policy...
Create gWLM Policy...
Table 16 Matrix OE visualization Report menu
Menu Selection
Description
gWLM Real-time Reports...
Monitor current interaction of workload activity and management policies.
gWLM Historical Reports
Create a report of historical workload activity.
gWLM Advanced Reports...
Create a report showing overall workload activity and to help identify workloads
that require more resources.
Capacity Planning
Create reports showing computing resource utilization, trends in usage, cost
allocation, and planning scenario comparisons.
Logical Server Job Status...
Create a report showing job status and messages for logical servers (Windows
CMS only).
View Logical Server Details...
Create a report that provides additional information for logical servers (Windows
CMS only).
Matrix OE tool bar
The Matrix OE visualization tool bar provides a convenient way to adjust the display of compartment
information. Figure 1 shows the Matrix OE visualization toolbar options.
Figure 1 Matrix OE visualization tool bar options
1
2
The drop-down menu allows you to select different ways of visualizing your enterprise. The
default view is the “Physical and Virtual” view, which shows all physical and virtual servers
and the greatest number of nodes. You can select alternate views for server blades, logical
servers, Serviceguard clusters, or virtual machines; or show systems and events. In most cases,
selecting an alternate view limits the number of nodes displayed by restricting the view to a
particular type of node (“Virtual Machine”, for example). You can change the default view
that appears when you access Matrix OE visualization by modifying your user preferences.
For more information, see the online help for user preferences.
Select the Show Workloads check box or Show Workloads button to the left of the check box
to display sub-OS workloads running on a given system. Workload compartments display,
when they exist. Click either tool bar element to clear the workloads from the display.
In the following figure, a workload running on an Integrity VM host is shown in the blue
sub-compartment. By default, this control is turned off; Matrix OE visualization initially filters
out workload information from the compartment. For more information, see the online help
for compartment details.
Using Matrix OE visualization
35
3
4
The tool bar expand and collapse buttons allow you to manage the extent of detail you want
shown in the compartments and sub-compartments. For information about how these buttons
work, see the online help for tool bar buttons.
The Search field allows you to locate a given system by searching for a compartment name.
When you enter the name in the search field, Matrix OE visualization first highlights all
complete or partial matches of the name. When you click the Search button or press Enter,
Matrix OE visualization moves the scroll bar to the first compartment name it matches. For
example, searching for the system citrine moves the scroll bar so the compartment for that
system is at the top:
For more information, see the online help for the tool bar search feature.
5
6
The Refresh button
allows you to update the display to include the latest compartments,
their relationships, and utilization information. Normally, refreshing the display is not necessary
because the view is updated automatically as new data becomes available. However, you
might use the Refresh button to reattempt gathering utilization data for all items to ensure the
view is showing the latest information. Refreshing the view updates all containers and
relationships, resource utilization data, authentication credentials (WBEM) from HP Systems
Insight Manager, and workload information from Global Workload Manager. While the view
refreshes, the Refresh button spins to indicate it is in progress.
Status errors or warnings when receiving data are indicated by an alert button. For example,
a warning will appear if a system lacks a valid license or if a license has expired. Multiple
alerts are indicated by the number displayed. Click the alert button to view detailed information
about the error(s) or warning(s). An alert popup displays. Click the [X] button in the upper
right-hand corner of the popup to close it.
For more information, see the online help for alerts.
Customizing collections and home page
The following sections describe ways to customize Systems Insight Manager to make it more
convenient to start Matrix OE visualization and view the systems that you most frequently manage.
Creating custom collections
In Systems Insight Manager, you can create custom system collections whose default view is set to
any of the following options:
36
•
HP Matrix OE visualization – Makes the Matrix OE visualization the default view for the
collection and opens with the “Physical and Virtual” perspective.
•
gWLM – Makes the Shared Resource Domain tab the default view for the collection.
Getting started
•
HP Matrix OE visualization (Logical Servers) – Makes Matrix OE visualization the default view
for the collection and opens with the “Logical Server” perspective.
•
HP Matrix OE visualization (Blades) – Makes Matrix OE visualization the default view for the
collection and opens with the “Blades” perspective.
•
HP Matrix OE visualization (Virtual Machines) – Makes Matrix OE visualization the default
view for the collection and opens with “Virtual Machines” perspective.
•
HP Matrix OE visualization (Serviceguard) – Makes Matrix OE visualization the default view
for the collection and opens with the “Serviceguard” perspective.
•
HP Matrix OE visualization (collection nodes only) – Makes Matrix OE visualization the default
view and opens with “Physical and Virtual” perspective, but only showing nodes that are in
that collection and that you explicitly have authorizations to view.
NOTE: Other Matrix OE views might pull in authorized parent or child nodes not explicitly
defined in a collection.
Selecting a custom collection starts Matrix OE visualization. Using a custom collection instead of
All Matrix OE Resources can provide significant performance improvements because only the
systems in your custom collection will be displayed.
To create a custom collection, use the following procedure:
1.
2.
3.
4.
5.
From the Systems and Event Collections list in the left-hand navigation area, select the
Customize... link.
Click New... to create a new custom collection.
Use the radio button to choose whether to individually specify the systems in the collection or
select systems based on their attributes.
Specify the systems or the attributes of systems to be included in the collection and click Save
As Collection.
Specify the collection name and its location in the Systems tree, then click OK.
NOTE: Non-administrators can only save collections under the Private collection, whereas
administrators can save them anywhere. Any collections intended for use with the default
collection preference must be saved directly under the All Matrix OE Resources collection.
6.
7.
Select the radio button next to the newly created collection and click Set Properties.
Change the Default View to HP Matrix OE, gWLM , HP Matrix OE (Logical Servers),
HP Matrix OE (Blades), HP Matrix OE (Virtual Machines), HP Matrix OE
(Serviceguard), or HP Matrix OE (Collection Nodes Only), and then click OK.
For more information on Visualization views or perspectives, see the online help for Matrix OE
visualization.
Automatically displaying Matrix OE visualization
You can customize Systems Insight Manager so that your preferred perspective in Matrix OE
visualization is automatically displayed as soon as Systems Insight Manager starts.
Use the following procedure to set your Systems Insight Manager home page.
1.
2.
3.
From the top menu bar, choose Options→Home Page Settings...
Select the option This collection and choose All Matrix OE Resources or another collection from
the menu.
Click OK.
Using Matrix OE visualization
37
38
4 Troubleshooting
This chapter describes some of the tools and procedures that can be used to troubleshoot problems
in Matrix Operating Environment. Additional troubleshooting information can be found in the user
guides listed in “Using Matrix OE and related environments” (page 45). For information about
known issues and workarounds in this release, see the HP Matrix Operating Environment Release
Notes.
Memory and other system requirements
Make sure that your CMS and managed systems meet the requirements specified in the HP Insight
Management Support Matrix. In particular, note the recommended and minimum supported memory
requirements. This document is available at http://www.hp.com/go/matrixoe/docs.
If error messages about exceeding heap space are displayed, you may need to increase the heap
size of the Systems Insight Manager Java Virtual Machine (JVM). On 64–bit systems, Systems
Insight Manager sets the heap size to 4096 MB (4 GB). You can specify a different heap size by
setting the JVMMAXHEAP value (in MB) in the globalsettings.props file. On HP-UX, this file
is at /etc/opt/mx/config/globalsettings.props. On Windows, it is at
installation-directory\config\globalsettings.props. The default installation
directory is C:\Program Files\HP\Virtual Server Environment, but this directory can
be changed at installation time.
Insight managed system setup wizard
Many configuration issues can be avoided by using the managed system setup wizard to configure
managed systems for use with Matrix OE. The wizard automates the installation of required licenses,
agent software, and other configuration settings to support the management capabilities intended
for use on the system.
To start the managed system setup wizard, select Configure→Managed System Setup Wizard...
from the top menu. Help is available in each step of the wizard.
Diagnose menu actions
There are three tasks available from the Diagnose→Troubleshoot Matrix Operating Environment
menu, described in the following sections. These tasks use the vseassist command to perform
configuration checks. For examples of the output from these checks, see vseassist(1M) (page 52).
Check CMS configuration
This task performs a number of configuration checks on the CMS. When troubleshooting your
configuration, perform this task first. Once you have resolved any CMS configuration issues, you
can diagnose issues with specific managed systems using the “Check CMS to managed node
communication” (page 40) and “Check managed node configuration” (page 41) tasks described
below.
Procedure 9 Check the configuration of your CMS
1.
2.
From the top menu bar, select Diagnose→Troubleshoot Matrix Operating Environment→Check
CMS Configuration....
To schedule this task to run periodically or at a set time, click Schedule. The Schedule Task
screen is displayed. Help on scheduling options is available from that screen. After the task
executes, you can view the results by selecting Tasks & Logs→View Task Results... from the
top menu bar.
To run this task immediately, click Run Now. This executes the vseassist command on the
CMS and displays the results in the Stdout tab.
Memory and other system requirements
39
3.
4.
For each check performed by this task, one of the following status indicators is displayed:
PASS
No configuration problem was found
FAIL
A serious configuration problem was found. You must resolve the problem for correct
operation of Matrix Operating Environment.
WARN
A configuration problem was found. The problem will not necessarily prevent correct
operation of Matrix Operating Environment, but it may limit or restrict operation of some
features.
N/A
Not Applicable: the check does not apply to this type of system.
Optional: To print a copy of the output, click View Printable Report, then click Print.
This task writes detailed information to the log file (/var/adm/syslog/vseassist.log on an
HP-UX CMS, installation-directory\logs\vseassist.log on Microsoft Windows
systems). Check the log file for details of any problems encountered.
TIP:
The vseassist command line that was executed by this task is displayed on this screen
above the output box. This command is also displayed in the printable version of the report. You
can use this information to create your own diagnostic scripts that can be run from the command
line.
You can review these results again later by selecting Tasks & Logs→View Task Results... from the
top menu bar.
Check CMS to managed node communication
This task checks the communication between the CMS and selected managed systems. When
troubleshooting your Matrix OE configuration, perform the “Check CMS configuration” (page 39)
task first, to make sure that you do not have any unresolved CMS configuration issues. Then use
this task to resolve communication issues with managed systems where you are having problems.
Some of the problems detected with this option include expired licenses, no open WBEM ports,
and improperly configured SSH authentication. These checks will verify whether the CMS can
communicate with the managed systems in order to perform management functions.
Procedure 10 Check the communication between the CMS and managed systems
1.
2.
3.
4.
Optional: Select the managed systems where you are having problems. You can select systems
by checking the selection box next to each system name in the Matrix OE visualization view.
If you prefer, you can start this task with no systems selected. In that case, you are prompted
to select the systems from the available HP SIM system collections after the next step below.
Select Diagnose→Troubleshoot Matrix Operating Environment→Check CMS to Managed Node
Communication... from the top menu bar.
Optional: If no systems have been selected yet, you are prompted to select from the available
HP SIM system collections. If you have already selected systems, then those systems are
displayed in the Verify targets screen. Systems Insight Manager provides several options for
adding or removing systems on this screen. For help, select Help→For HP Systems Insight
Manager from the top menu bar, then select the “Operations” topic and the “Managing with
tasks” subtopic.
To schedule this task to run periodically or at a set time, click Schedule. The Schedule Task
screen is displayed. Help on scheduling options is available from that screen. After the task
executes, you can view the results by selecting Tasks & Logs→View Task Results... from the
top menu bar.
To run this task immediately, click Run Now. This executes the vseassist command on the
CMS and displays the results in the Stdout tab.
40
Troubleshooting
5.
6.
For each check performed by this task, one of the following status indicators is displayed:
PASS
No configuration problem was found
FAIL
A serious configuration problem was found. You must resolve the problem for correct
operation of Matrix OE.
WARN
A configuration problem was found. The problem will not necessarily prevent correct
operation of Matrix OE, but it may limit or restrict operation of some features.
N/A
Not Applicable: the check does not apply to this type of system.
Optional: To print a copy of the output, click View Printable Report, then click Print.
This task writes detailed information to the log file (/var/adm/syslog/vseassist.log on
HP-UX systems, installation-directory\logs\vseassist.log on Microsoft Windows
systems). Check the log file for details of any problems encountered.
TIP:
The vseassist command line that was executed by this task is displayed on this screen
above the output box. This command is also displayed in the printable version of the report. You
can use this information to create your own diagnostic scripts that can be run from the command
line.
You can review these results again later by selecting Tasks & Logs→View Task Results... from the
top menu bar.
Check managed node configuration
This task checks the configuration of HP-UX, Microsoft Windows or Linux managed systems by
using mxexec to copy the vseassist command to selected managed systems, and remotely
execute it there. When troubleshooting your Matrix OE configuration, perform the “Check CMS
configuration” (page 39) task first, to make sure that you do not have any unresolved CMS
configuration issues. Then use the “Check CMS to managed node communication” (page 40) task
to resolve communication issues with managed systems where you are having problems. Once
you have resolved the communication issues, use this task to resolve configuration issues for any
managed systems where you are still having problems.
Procedure 11 Check the configuration of managed systems
1.
2.
3.
4.
Optional: Select the managed systems where you are having problems. You can select systems
by checking the selection box next to each system name in the Visualization View. If you
prefer, you can start this task with no systems selected. In that case, you are prompted to select
the systems from the available HP SIM system collections after the next step below.
Select Diagnose→Troubleshoot Matrix Operating Environment→Check Managed Node
Configuration... from the top menu bar.
Optional: If no systems have been selected yet, you are prompted to select from the available
HP SIM system collections. If you already selected systems, then those systems are displayed
in the Verify targets screen. Systems Insight Manager provides several options for adding or
removing systems on this screen. For help, select Help→For HP Systems Insight Manager from
the top menu bar, then select the Managing with tasks topic.
To schedule this task to run periodically or at a set time, click Schedule. The Schedule Task
screen is displayed. Help on scheduling options is available from that screen. After the task
executes, you can view the results by selecting Tasks & Logs→View Task Results... from the
top menu bar.
To run this task immediately, click Run Now. This executes the vseassist command on the
CMS and displays the results in the Stdout tab.
Diagnose menu actions
41
5.
6.
For each check performed by this task, one of the following status indicators is displayed:
PASS
No configuration problem was found
FAIL
A serious configuration problem was found. You must resolve the problem for correct
operation of Matrix OE.
WARN
A configuration problem was found. The problem will not necessarily prevent correct
operation of Matrix OE, but it may limit or restrict operation of some features.
N/A
Not Applicable: the check does not apply to this type of system.
Optional: To print a copy of the output, click View Printable Report, then click Print.
This task writes detailed information to the log file (/var/adm/syslog/vseassist.log on
HP-UX systems, installation-directory\logs\vseassist.log on Microsoft Windows
systems). Check the log file for details of any problems encountered.
TIP:
The vseassist command line that was executed by this task is displayed on this screen
above the output box. This command is also displayed in the printable version of the report. You
can use this information to create your own diagnostic scripts that can be run from the command
line.
You can review these results again later by selecting Tasks & Logs→View Task Results... from the
top menu bar.
vseassist command
The vseassist command, which implements the Diagnose menu actions described in the previous
section, can also be executed directly from the command line on the CMS. If you are unable to
resolve communication issues with one of your managed systems, you can install or copy this
command to the managed system and run it from the command line there.
For details of the command line options, suggested diagnostic procedure, and examples, see
vseassist(1M) (page 52). On an HP-UX CMS, this reference page can also be viewed from the
command line using the man command.
42
Troubleshooting
5 Support and other resources
Information to collect before contacting HP
Be sure to have the following information available before you contact HP:
•
Software product name
•
Hardware product model number
•
Operating system type and version
•
Applicable error message
•
Third-party hardware or software
•
Technical support registration number (if applicable)
How to contact HP
Use the following methods to contact HP technical support:
•
In the United States, see the Customer Service / Contact HP United States website for contact
options
http://welcome.hp.com/country/us/en/contact_us.html
•
In the United States, call 1-800-HP-INVENT (1-800-474-6836) to contact HP by telephone.
This service is available 24 hours a day, 7 days a week. For continuous quality improvement,
conversations might be recorded or monitored.
•
In other locations, see the Contact HP Worldwide website for contact options:
http://welcome.hp.com/country/us/en/wwcontact.html
Security bulletin and alert policy for non-HP owned software components
Open source software (such as OpenSSL) or third-party software (such as Java) are sometimes
included in HP products. HP discloses that the non-HP owned software components listed in the
Insight Management end user license agreement (EULA) are included with Insight Management.
The EULA is included with the Insight Management Installer on Insight Management DVD #1.
HP addresses security bulletins for the software components listed in the EULA with the same level
of support afforded HP products. HP is committed to reducing security defects and helping you
mitigate the risks associated with security defects when they do occur.
When a security defect is found, HP has a well defined process that culminates with the publication
of a security bulletin. The security bulletin provides you with a high level description of the problem
and explains how to mitigate the security defect.
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/country/us/en/contact_us.html
Registering for software technical support and update service
Insight Management includes one year of 24 x 7 HP Software Technical Support and Update
Service. This service provides access to HP technical resources for assistance in resolving software
implementation or operations problems.
Information to collect before contacting HP
43
The service also provides access to software updates and reference manuals in electronic form as
they are made available from HP. Customers who purchase an electronic license are eligible for
electronic updates.
With this service, Insight Management customers benefit from expedited problem resolution as
well as proactive notification and delivery of software updates. For more information about this
service, see the following website:
http://www.hp.com/services/insight
Registration for this service takes place following online redemption of the license certificate.
How to use your software technical support and update service
As HP releases updates to software, the latest versions of the software and documentation are
made available to you. The Software Updates and Licensing portal gives you access to software,
documentation and license updates for products on your HP software support agreement.
You can access this portal from the HP Support Center:
HP Support Center
After creating your profile and linking your support agreements to your profile, see the Software
Updates and Licensing portal at http://www.hp.com/go/hpsoftwareupdatesupport to obtain
software, documentation, and license updates.
HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources:
•
In the United States, see the HP U.S. service locator website:
http://www.hp.com/service_locator
•
In other locations, see the Contact HP worldwide website:
http://www.hp.com/go/assistance
Related information
For information about open-source products included with Matrix Operating Environment (including
license constraints, updates, and security information), see the end-user license agreement included
with HP Matrix Operating Environment. This document is installed on the CMS at the following
locations:
HP-UX CMS
/opt/vse/src/README
Microsoft Windows CMS
installation-directory\src\README
The default installation directory is C:\Program Files\HP\
Virtual Server Environment, but this directory can be
changed at installation time.
Manuals and white papers
The latest versions of manuals and white papers for Matrix OE and related products can be
downloaded from the HP Web. The manuals and white papers listed below can be found at these
locations:
•
Enterprise Information Library (http://www.hp.com/go/matrixoe/docs)
•
Enterprise Information Library (http://www.hp.com/go/insightcontrol/docs)
•
Enterprise Information Library (http://www.hp.com/go/insightmanagement/docs)
The following tables list the manuals and white papers that are available. Some documents appear
in multiple tables.
44
Support and other resources
Installation and configuration: Microsoft Windows CMS
Topic
Document
Requirements, feature support,
compatibility
• HP Insight Management Support Matrix
Release notes
• HP Matrix Operating Environment Release Notes
• HP Insight Control Release Notes
• HP Virtual Connect Enterprise Manager Release Notes
Installation and configuration
• HP Insight Management Installation and Configuration Guide
• HP Insight Management Preinstallation Worksheet
• HP Insight Management Quick Installation Guide
Installation and configuration: HP-UX CMS
Topic
Document
Requirements, feature support,
compatibility
• HP Insight Management Support Matrix
Release notes
• HP Matrix Operating Environment Release Notes
Installation and configuration
• HP Matrix Operating Environment Integrity CMS Installation and Configuration
Guide
Using Matrix OE and related environments
Topic
Document
Getting started
• HP Matrix Operating Environment Getting Started Guide (this document)
• HP Insight Management Getting Started Guide
• HP Insight Control Getting Started Guide
User guides
• HP Matrix Operating Environment Logical Server Management User Guide
• HP Capacity Advisor User Guide
• Application Discovery User Guide
• HP Global Workload Manager User Guide
• HP Integrity Virtual Server Manager User Guide
• HP Insight Control Server Migration User Guide
• HP Insight Control Virtual Machine Management User Guide
• HP Insight Control Performance Management User Guide
• HP Storage Provisioning Manager (SPM) User Guide
• HP Matrix Operating Environment Infrastructure Orchestration User Guide
• HP Insight Control Power Management User Guide
• HP Matrix Operating Environment Recovery Management User Guide
• HP Insight Control Server Deployment User Guide
• HP Virtual Connect Enterprise Manager User Guide
White papers
Visit the Enterprise Information Library, the Enterprise Information Library, and the
Enterprise Information Library.
Related information
45
Websites
Information and solutions
Reference Architectures for
Application Deployment in
Virtualized Environments
http://www.hp.com/go/idvsera
HP Support Center
HP Support Center
Large Enterprise Business
http://www.hp.com/go/enterprise
HP Matrix Operating Environment
http://www.hp.com/go/matrixoe
HP Insight Management
http://www.hp.com/go/insightmanagement
HP Insight Control
http://www.hp.com/go/insightcontrol/
HP Virtual Connect Enterprise
Manager
http://www.hp.com/go/vcem/
HP Systems Insight Manager
http://www.hp.com/go/insightmanagement/sim/
HP CloudSystem Matrix
http://www.hp.com/go/matrix
Products
Command references (manpages)
Matrix Operating Environment and related products include manpages for HP-UX and Linux systems
and command reference pages for Microsoft Windows systems. These pages provide details about
commands, file formats, and related information. See “Command reference” (page 51) for command
reference pages included with this document. The following tables list additional reference pages
related to Matrix OE.
Reference pages installed on the CMS
Reference page
Description
capagentlesscfg(1M)
Set advanced options for Capacity Advisor agentless data collection, and view a list of systems
configured for agentless data collection (Windows CMS only)
capcustombenchmark(1M)
Configure Capacity Advisor benchmark CPU scaling to normalize collected data
capcustombenchmark(4)
Format of Capacity Advisor custom benchmark database files
capovpaextract(1M)
Export HP Performance Management Agent (formerly HP OpenView Performance Agent, or
OVPA) system data from managed systems and import into Capacity Advisor
cappmpextract
Export HP Insight Control performance management system data from specified managed systems
and import the data into Capacity Advisor (Windows CMS only)
capprofile(1M)
Import, export, display, invalidate and remove Capacity Advisor data for workloads or systems
capprofile(4)
Format of Capacity Advisor import and export files
capupgrade(1M)
Recomputes the CPU utilization data after a Systems Insight Manager upgrade
gwlm(1M)
Global Workload Manager
gwlm(5)
Overview of Global Workload Manager
gwlmcmsd(1M)
Global Workload Manager daemon
gwlmreport(1M)
Produce advanced textual summary reports for workload resource utilization
gwlmsslconfig(1M)
gwlmimportkey(1M)
gwlmexportkey(1M)
Secure network communications for Global Workload Manager
46
Support and other resources
Reference page
Description
msswinitconfig(1M)
Configure or unconfigure the Insight managed system setup wizard
gwlmxml(4)
Overview of XML file structure for Global Workload Manager
vseassist(1M)
Help resolve Matrix OE configuration problems
vseinitconfig(1M)
Configure or unconfigure the Matrix OE software
vselicense(1M)
Manage licenses to use (LTUs) on HP Integrity and HP 9000 systems
Reference pages installed with agent software on managed systems
Reference page
Description
agent_config(1M)
Control Application Discovery certificates from the managed node
amgrd(1M)
Control or modify the operation of the Application Discovery agent
gwlmagent(1M)
Global Workload Manager (gWLM) agent
gwlmplace(1M)
Place a process in a gWLM workload
gwlmsend(1M)
Send metric data to gWLM for use in a custom policy
gwlmsslconfig(1M)
gwlmimportkey(1M)
gwlmexportkey(1M)
Secure network communications for Global Workload Manager
gwlmstatus(1M)
Display status for the managed node's agent, SRD and license manager
utild(1M)
(HP-UX) system utilization data collection daemon
utild(8)
(Linux) system utilization data collection daemon
UPService.pdf
(Windows) Utilization Provider Service (document installed in \Program Files\
Hewlett-Packard\UtilProvider\doc)
Reference page installed on cell-based complexes
Reference page
Description
parmgr(1M)
Start Partition Manager
Reference pages installed on systems running Integrity VM
Reference page
Description
hpvm(5)
About Integrity VM
hpvmclone(1M)
Create a cloned copy of an Integrity VM virtual machine
hpvmcollect(1M)
Collect crash dumps, logs, system status, and configuration on guests and the Integrity VM Host
hpvmconsole(1M)
Connect to the console of an Integrity VM virtual machine
hpvmcreate(1M)
Create a new Integrity VM virtual machine
hpvmdevmgmt(1M)
Manage the Integrity VM device database
hpvminfo(1M)
Display information about the Integrity VM environment
hpvmmodify(1M)
Rename or modify the attributes of an Integrity VM virtual machine
hpvmmigrate(1M)
Move a virtual machine to another Integrity VM Host system
hpvmnet(1M)
Configure virtual network devices
Related information
47
Reference page
Description
hpvmremove(1M)
Remove an Integrity VM virtual machine
hpvmstart(1M)
Start an Integrity VM virtual machine
hpvmstatus(1M)
Display status of one or more Integrity VM virtual machines
hpvmstop(1M)
Stop an Integrity VM virtual machine
Selected HP Systems Insight Manager reference pages
Reference page
Description
mxagentconfig(1M)
Configure the agent to work with a CMS
mxauth(1M)
Add, remove or list authorizations in Systems Insight Manager
mxglobalsettings(1M)
Manage global settings in Systems Insight Manager
mxinitconfig(1M)
Perform initial configuration of the server
mxnode(1M)
Add, modify, identify, remove or list nodes in Systems Insight Manager
mxstart(1M)
Start Systems Insight Manager and the TomCat webserver
mxstatus(1M)
Display or return (via exit code) the current ready/not-ready state of Systems Insight
Manager
mxstop(1M)
Stop Systems Insight Manager and the TomCat webserver
mxuser(1M)
Add, modify, remove or list users in Systems Insight Manager
Typographic conventions
This document uses the following typographic conventions.
48
Book Title
Title of a book or other document.
Linked Title
Title that is a hyperlink to a book or other document.
http://www.hp.com
A website address that is a hyperlink to the site.
Command
Command name or qualified command phrase.
user input
Commands and other text that you type.
computer output
Text displayed by the computer.
Enter
The name of a keyboard key. Note that Return and Enter both refer
to the same key. A sequence such as Ctrl+A indicates that you must
hold down the key labeled Ctrl while pressing the A key.
term
A term that is defined in the glossary and links to a glossary definition.
variable
The name of an environment variable, for example PATH or errno.
value
A value that you may replace in a command or function, or information
in a display that represents several possible values.
find(1)
HP-UX manpage. In this example, “find” is the manpage name and
“1” is the manpage section.
Support and other resources
6 Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation,
send a message to:
docsfeedback@hp.com
Include the document title and part number in your message. All submissions become the property
of HP.
49
50
Command reference
51
vseassist(1M)
NAME
vseassist -- Help Resolve Matrix OE Configuration Problems
SYNOPSIS
Path (HP-UX): /opt/vse/bin/vseassist
Path (Windows): install-path\bin\vseassist.exe
Usage:
vseassist -a [-q] [ -n nodename | -g collectionname ]...
vseassist -c [-q]
vseassist { -l | -r } [-q] { -n nodename | -g collectionname }...
vseassist -s [-q] -h cmsfqdn
vseassist -v
DESCRIPTION
The vseassist command performs a number of checks to identify configuration problems in your
installation of HP Matrix Operating Environment. This command checks the software configuration
on the HP SIM Central Management Server (CMS), the communication between the CMS and
managed systems, and the configuration of the software on managed systems. A summary of results
is displayed and detailed results are written to a log file, along with recommendations for resolving
any problems found.
You can execute vseassist from the Matrix OE graphical user interface, from the command line
on the CMS, or from the command line on a managed system. HP recommends the following
diagnostic procedure:
1. If you have Administrator (root) access to the CMS, execute the following command from
the command line:
vseassist -a
This will check the configuration of the CMS, communication with all systems in the All
Matrix Resources collection, and the configuration on those systems. Refer to the summary
output and examine the log file for any problems. Follow the resolution steps in the log file to
fix any problems that were found.
Fix problems in the CMS configuration first. You can verify that you have fixed those problems
by executing the following command from the CMS command line:
vseassist -c
You can also run this command directly from the Matrix OE user interface. From the Diagnose
menu, select Troubleshoot Matrix Operating Environment, then select Check
CMS Configuration.
52
2.
After you have resolved all problems with the CMS configuration, check to see if there are
any remaining communication issues with the managed systems. From the CMS command
line, specify the HP SIM nodenames or system collection names of your managed systems
using the following command:
vseassist -l { -n nodename | -g collectionname ...}
Or, from the Matrix OE user interface, select the managed systems, then from the Diagnose
menu, select Troubleshoot Matrix Operating Environment, then select Check
CMS to Managed Node Communication.
3.
After you have resolved the communication issues between the CMS and your managed
systems, check the configuration on those systems. From the CMS command line, specify the
HP SIM nodenames or system collection names of your managed systems using the following
command:
vseassist -r { -n nodename | -g collectionname ...}
Command reference
Or, from the Matrix OE user interface, select the managed systems, then from the Diagnose
menu, select Troubleshoot Matrix Operating Environment, then select Check
Managed Node Configuration.
4.
If you are unable to resolve issues with one of your managed systems, you can install or copy
vseassist to the managed system and run it from the command line there. In the following
command, replace cms with the fully qualified domain name of the CMS:
vseassist -s -h cms
Options
If no options are specified, the command syntax is displayed and the command exits with return
code 3.
The vseassist command recognizes the following options. For each option, a mnemonic is
shown in parentheses to help you remember the option letter.
-a
(All) Perform all checks:
1. Check the configuration of the CMS (as with the -c option).
2. Check the communication between the CMS and the specified
managed systems (as with the -l option). If no managed systems
are specified, then perform this check on all systems in the All
Matrix Resources collection.
3. Check the configuration of the specified managed systems (as
with the -r option). If no managed systems are specified, then
perform this check on all compatible systems in the All Matrix
Resources collection.
-c
(CMS) Check the configuration of the CMS.
Note: For a Windows CMS, if IOAssist is installed, additional IOAssist
resource and CMS configuration checks will be launched.
-l
(Link) From the CMS, check the communication between the CMS and
the managed systems specified by the -n and -g options. Some of
the problems detected with this option include expired licenses, no
open WBEM ports, and improperly configured SSH authentication.
These checks will verify that the CMS can communicate with the
managed systems in order to perform management functions.
This option requires one or more -n or -g options.
Note: On Windows and HP-UX CMS, vseassist will obtain the port
on which to attempt managed node communication from the file
globalsettings.props (see FILES section below). If no port
configuration is present, port 22 will be used.
-r
(Remote) From the CMS, check the configuration of the HP-UX or
Windows managed systems specified by the -n and -g options
(vseassist does not provide configuration checks for Linux managed
systems). This option uses mxexec to copy the vseassist command
to the managed systems, where it is executed with the -s option.
In order for the -r option to succeed, the CMS must be able to
communicate with the managed systems (as checked by the -l option).
This option requires one or more -n or -g options.
-n nodename
(Node) Specifies the name of a managed system using the node name
by which the system is known to the CMS (as reported by mxnode(1M)).
Multiple -n and -g options can be used to specify multiple systems.
Note: This command is only designed to diagnose problems with
systems that are part of the All Matrix Resources collection.
53
Applying this command to other resources using -n or -g options will
not produce useful results.
-g collectionname
(Group) Specifies the name of a collection of systems known to the
CMS. The specified checks will be performed for each of the managed
systems in the collection. Multiple -n and -g options can be used to
specify multiple systems.
Note: System or collection names that include spaces must be enclosed
in quotes.
Refer to mxquery(1M) for more information about collections under HP
SIM.
-q
(Quiet) No output will be generated on stdout or stderr. The results
will still be logged to the vseassist.log file.
(System) This option is used when running vseassist directly on
HP-UX or Windows managed systems (vseassist does not provide
configuration checks for Linux managed systems). Some of the problems
detected with this option include missing WBEM providers, stalled
WBEM process, and missing required patches. On an HP-UX managed
system, WBEM services checks will be performed by wbemassist if
wbemassist version 1.1 or later is installed. Otherwise vseassist
will use its own built-in WBEM checks.
Note: wbemassist checks for problems in HP-UX WBEM Services and
recommends solutions. It does not perform checks on WBEM Providers
or other services that use the CIM server. For more information, see
wbemassist(1M).
When you use vseassist with the -r option on the CMS, mxexec
will remotely execute vseassist on the managed systems using the
-s option.
-s
-h cms
-v
(Host) Specifies the fully qualified domain name of the CMS that is
managing the system. This option is passed to the remote execution
of vseassist when you use the -r option on the CMS.
Displays vseassist version
Installation
The vseassist command is installed on the CMS when Matrix OE is installed.
RETURN VALUES
0
1
2
3
4
The command completed successfully and no FAIL results were found.
The command completed successfully and one or more FAIL results were found.
Warnings, but no FAIL results were found.
Incorrect options were specified; the command syntax is displayed.
An unexpected internal error occurred. Contact your HP Support Representative, your HP
Services Representative, or your authorized HP reseller for assistance.
EXAMPLES
The specific checks performed may vary by operating system and system type of the CMS and
managed systems. The following examples show the kind of output that is produced, but the details
may be different in your environment.
Check the configuration of a CMS named unixsys:
# vseassist -c
Version: 7.2
+-----------------------------------------------------------------------------------------------+
|
Performing CMS configuration verification
|
+-----------------------------------------------------------------------------------------------+
54
Command reference
unixsys:
HP SIM running.........................................................................[PASS]
HP SIM memory configuration............................................................[PASS]
HP Matrix Operating Environment running................................................[PASS]
Localhost name resolution..............................................................[PASS]
Matrix OE manageable systems discovered in HP SIM......................................[PASS]
Application Discovery server running...................................................[PASS]
File system free space.................................................................[PASS]
Java JRE installed.....................................................................[PASS]
Virtual Machine Management runnning....................................................[PASS]
VMM responsive.........................................................................[WARN]
WARNING:
HP SIM has discovered one or more virtual machine hosts
servers, but the VMM plugin is not fully configured to
manage the following servers: palacio .
RESOLUTION: - Verify if the HP Management Agents are installed (for
SNMP and proper HP SIM discovery);
- Verify if VMM agent has been installed; It's possible to
install that via the "Deploy -> Deploy Drivers,
Firmwares and Agents -> Install VMM Agent" menu;
- Verify if the system is licensed for VMM;
- Verify if the system is registered for VMM, if not
register the VM host via the "Configure -> Virtual
Machine Host Registration" menu or register the VM via
the native virtualization console and Identify the
system using "Options->Identify Systems" menu.
Virtual Connect Enterprise Manager responsive.........................................[PASS]
Logical Server Automation installed...................................................[PASS]
Running infrastructure orchestration (IO) Checks......................................[PASS]
Result Summary:
13 verification check(s) performed on 1 system(s)
12 check(s) passed
0 check(s) failed
1 check(s) warned
0 check(s) not applicable
See log for details: C:\Program Files\HP\Virtual Server Environment\logs\vseassist.log
Check the communication from the CMS to the managed system named system:
# vseassist -l -n system
Version: 7.2
+---------------------------------------------------------------------------------------------+
|
Performing link verification of managed system(s) from the CMS
|
+---------------------------------------------------------------------------------------------+
system:
Managed system hostname resolution...................................................[PASS]
WBEM port open.......................................................................[PASS]
WBEM authentication..................................................................[PASS]
SSH port open........................................................................[PASS]
SSH authentication...................................................................[PASS]
SNMP port open.......................................................................[PASS]
Trial or permanent license applied...................................................[PASS]
VMM accessibility....................................................................[N/A ]
Capacity Advisor data collection.....................................................[PASS]
Check VMware ESX version.............................................................[N/A ]
Result Summary:
8 verification check(s) performed on 1 system(s)
8 check(s) passed
0 check(s) failed
0 check(s) warned
2 check(s) not applicable
See log for details: C:\Program Files\HP\Virtual Server Environment\logs\vseassist.log
AUTHORS
vseassist was developed by Hewlett-Packard Company.
DOCUMENT LAST UPDATED
December 2013
55
MESSAGES
The following message may be displayed when running managed system configuration checks on
a 64-bit Windows managed system:
'chcp' is not recognized as an internal or external command,
operable program or batch file.
This is an issue with the remote command execution facility of HP SIM. The message can be ignored.
FILES
Configuration settings, including communication port settings, are read from the following file:
HP-UX:
/etc/opt/mx/config/globalsettings.props
Windows:
install-path\config\globalsettings.props
Detailed results of the checks performed by vseassist are written to the log file. Examine the
log file for recommended steps to resolve any problems found.
Note: The log file is not automatically pruned.
HP-UX:
/var/adm/syslog/vseassist.log
Windows:
install-path\logs\vseassist.log
Linux:
/var/log/vseassist.log
The default install-path on a Windows CMS is C:\Program Files\HP\Virtual Server
Environment, but this directory can be changed at installation time.
SEE ALSO
Matrix OE help
Matrix OE information library (http://www.hp.com/go/matrixoe/docs)
mxexec(1M), mxnode(1M), mxquery(1M), vseinitconfig(1M), vselicense(1M), wbemassist(1M)
56
Command reference
vselicense(1M)
NAME
vselicense -- Manage licenses to use (LTUs) on HP Integrity and HP 9000 Systems
SYNOPSIS
Path (HP-UX): /opt/vse/bin/vselicense
Path (Windows): installation-directory\bin\vselicense
vselicense { -? | --help }
(Show command help)
vselicense --usage
(Show command syntax)
vselicense { -t | --tempLicense } { -n sys | --sys=sys }...
(Apply temporary trial licenses)
vselicense { -l key | --key=key } { -n sys | --sys=sys }... { -p prod |
--prod=prod }
(Migrate and apply Integrity Windows/Linux LTUs)
vselicense { -m | --migrate } [ -g | --gwlm ] { -n sys | --sys=sys }...
(Scan and migrate HP-UX LTUs)
vselicense { -m | --migrate } { -c count | --count=count } { -n sys |
--sys=sys }
(Correct the number of per-core/socket licenses assigned to a system)
vselicense { -m | --migrate } { -c 0 | --count=0 } { -n sys | --sys=sys }
(Remove all the licenses applied to a system)
vselicense { -s | --show }
(List the managed systems with migrated LTUs)
DESCRIPTION
The vselicense command is installed on the Central Management Server (CMS) with Matrix
OE. This command installs and removes Licenses to Use (LTUs) for Matrix Operating Environment
for HP-UX. It can also be used to correct the number of per-core or per-socket licenses that are
applied for LTUs.
This command applies only to HP Integrity systems running HP-UX, Linux, or Microsoft Windows
operating systems, and HP 9000 systems running HP-UX. It is not used for licenses based on “5x5”
keys (introduced with VSE Management Software version 4.0). It is only used for trial licenses
included with Matrix OE and for the LTUs in the following list. You may have these LTUs installed
from a previous version of HP Matrix Operating Environment (formerly known as HP Insight Dynamics
or VSE Management Software), or from the HP-UX VSE or DC Operating Environments.
T2786AC HP VSE Suite for HP-UX 11i LTU
T2784AC HP Capacity Advisor for HP-UX LTU
T2782AC HP Virtualization Manager for HP-UX LTU
T2762AA HP Global Workload Manager Agent LTU
T2807AC HP Capacity Advisor for Integrity Windows
T2806AC HP Virtualization Manager for Integrity Windows
T2785AC HP Capacity Advisor for Integrity Linux
T2783AC HP Virtualization Manager for Integrity Linux
Matrix OE licenses are now managed in the HP Systems Insight Manager License Manager database
on the CMS. These licenses are encoded in a “5x5” key consisting of 5 blocks of 5 numbers or
characters. These licenses are added to the CMS and applied to managed systems through HP
SIM.
57
Licenses from previous versions of the software and licenses included in the HP-UX VSE or DC
Operating Environments are automatically migrated to the License Manager database if they were
previously in use (the license had already been installed and scanned). If these licenses were never
installed or have not yet been scanned, you may be able to migrate them to License Manager
database using vselicense (see “Migrating previously unused licenses” below).
Correcting the number of licensed cores or sockets
Matrix OE for Integrity products are licensed per core or socket on managed HP Integrity and HP
9000 systems. When licenses from a previous release or from the HP-UX Operating Environments
are migrated to the current version, the number of cores or sockets on the managed system is
determined via a WBEM query. The value returned is used as the number of licenses assigned to
that system. If the WBEM query is unsuccessful at determining the correct number, one license is
assigned.
You are responsible for verifying that the correct number of licenses are applied to your managed
systems, based on the number of cores or sockets in use. In order to remain in compliance with
your End User Licensing Agreement, you may need to correct the count assigned during the license
migration process. To correct the count assigned during migration, enter the following command
on the CMS:
vselicense -m -c count -n sys
where count is the correct number of per-core or per-socket licenses to assign for system sys.
Migrating previously unused licenses
If permitted by your licensing agreement with HP, unused licenses that were purchased for an
earlier release but have not yet been installed or scanned can be migrated to the License Manager
database and applied to a managed system by the vselicense command, using the following
procedures. These procedures should also be used to enable the LTUs included with the HP-UX
VSE or DC Operating Environments.
To scan for HP-UX LTUs to migrate and apply, follow the steps below. (This scan can also be
performed by the Insight managed system setup wizard and from the Matrix OE GUI.)
1. Install the HP-UX LTUs that have unused licenses, or install the VSE or DC Operating
Environment, on the managed system.
2. Establish common WBEM credentials for communication between the CMS and the managed
systems, or configure SSH for use in HP SIM. In some previous versions of the software, SSH
was required in order to scan for HP-UX LTUs. This scan is now attempted using WBEM. SSH
will only be used if scanning via WBEM fails. For information about configuring WBEM
credentials and SSH, see the HP Matrix Operating Environment Integrity CMS Installation and
Configuration Guide.
It is also possible to scan for the gWLM LTU (T2762AA) by communicating directly with the
gWLM agent if it is running on the managed system. However, this will provide no information
about the other LTUs. To perform this type of scan, use the -g or --gwlm option.
NOTE: The gWLM scanning option is only supported for gWLM agent versions earlier than
version 4.0.
3.
Execute one of the following commands on the CMS (note that multiple -n sys options can
be specified):
•
Scan for T2786AC, T2784AC, T2782AC, and T2762AA LTUs using WBEM or SSH:
vselicense -m -n sys
•
Scan for T2762AA LTU by communicating with the running gWLM agent:
vselicense -m -g -n sys
58
Command reference
NOTE:
This operation may take a long time to complete.
4.
If necessary, correct the number of per-core or per-socket licenses assigned to the systems
using vselicense with the -m and -c options, as described above.
To migrate and apply unused HP Integrity Linux or HP Integrity Windows LTUs, follow these steps:
1. Execute the following command on the CMS (note that multiple -n sys options can be
specified):
vselicense -l key -n sys -p prod
where key is the license key provided with the LTU product prod.
NOTE:
2.
This operation may take a long time to complete.
If necessary, correct the number of per-core or per-socket licenses assigned to the systems
using vselicense with the -m and -c options, as described above.
NOTE: Changes made by vselicense may not show up in the product's user interface until
you refresh the data (click the Refresh Data link in Capacity Advisor, or the Refresh Data icon in
the Visualization tab).
After migration to the License Manager database, your previously purchased LTUs will appear in
the HP SIM License Manager under the following new license names:
HP Matrix OE for Integrity
Migrated from:
T2786AC HP VSE Suite for HP-UX 11i LTU
HP Matrix OE visualization
Migrated from:
T2782AC HP Virtualization Manager for HP-UX LTU
T2806AC HP Virtualization Manager for Integrity Windows
T2783AC HP Virtualization Manager for Integrity Linux
HP Capacity Advisor
Migrated from:
T2784AC HP Capacity Advisor for HP-UX LTU
T2807AC HP Capacity Advisor for Integrity Windows
T2785AC HP Capacity Advisor for Integrity Linux
HP Global Workload Manager
(gWLM)
Migrated from:
T2762AA HP Global Workload Manager Agent LTU
Use the HP SIM License Manager to view the status of these licenses (select Deploy -> License
Manager... from the HP SIM menu, then select one of the new license names, as shown in the
preceding list).
Options
The vselicense command recognizes the following options:
-t|--tempLicense
Apply a trial license for Matrix OE for Integrity to the systems
identified by the -n options. When Matrix OE is installed on
the CMS, 10 trial licenses for Matrix OE for Integrity are
included in the License Manager database. These licenses can
be applied to HP Integrity and HP 9000 systems. Each trial
license is valid for 90 days after it is applied to a managed
system. To continue to manage these systems beyond the trial
period, permanent licenses must be purchased.
-l key|--key=key
Install the license key for the LTU product identified by the -p
option on the systems identified by the -n options.
-n sys|--sys=sys
The system name, as identified in HP SIM.
59
NOTE: HP Integrity virtual machines are licensed through the
VM Host. You cannot specify a virtual machine as the target
of a vselicense command. Instead, apply the command to
the VM Host system.
-p prod|--prod=prod
-g|--gwlm
-m|--migrate
-c count|--count=count
-s|--show
The product number of the LTU being installed or migrated. For
example, T2783AC is the product number for the Virtualization
Manager LTU for HP Integrity managed systems running Linux.
Communicate directly with the gWLM agent running on the
managed system when scanning for the gWLM LTU. This option
should only be used if WBEM and SSH are not configured for
use. When using this option, the scan can only detect the
gWLM LTU (T2762AA). No information will be returned about
other LTUs. This option is only supported for gWLM agent
versions earlier than version 4.0.
Migrate LTUs to the HP SIM License Manager database.
Set the number of per-core or per-socket licenses to apply to
the system identified by the -n option. This option is only valid
for previously migrated LTUs on the specified system. A count
value of 0 removes all migrated LTUs for that system from the
License Manager database.
List the managed systems that have licenses that have been
migrated from previous software releases.
RETURN VALUES
0
1
2
The command completed successfully; no errors were detected.
An error occurred and the command did not complete successfully.
A warning occurred. See command output for details.
EXAMPLES
Apply licenses for the HP Virtualization Manager for Integrity Linux (product T2783AC) on the
managed system that is identified in HP SIM as linsys1. The key value was obtained from HP
when the LTU was purchased.
vselicense -l key -n linsys1 -p T2783AC
Apply licenses for LTUs installed on an HP-UX managed system named uxsys2. The command
uses WBEM (or SSH if WBEM scan fails) to scan for the LTU(s) installed on the system.
vselicense -m -n uxsys2
Use gWLM to scan and apply T2762AA licenses on an HP-UX managed system.
vselicense -m -g -n uxsys3
Correct the number of per-core or per-socket licenses to 4 for a system with previously migrated
licenses.
vselicense -m -c 4 -n uxsys2
Remove all the licenses that were previously migrated and assigned to the managed system
winsys4.
vselicense -m -c 0 -n winsys4
AUTHORS
vselicense was developed by Hewlett-Packard Company.
60
Command reference
DOCUMENT LAST UPDATED
June 2012
SEE ALSO
Additional information is available in the “License Management” topic of the Matrix OE help, the
“Reference pages installed on the CMS” (page 46) and in the following documents:
vseinitconfig(1M), , HP Matrix Operating Environment Integrity CMS Installation and Configuration
Guide, HP Insight Management Installation and Configuration Guide
61
62
Glossary
active logical
server
A logical server that has been bound to both a managed system in HP Systems Insight Manager
and a workload, and is bound to specific storage. Active logical servers can be in one of two
states: powered on or powered off. An active logical server can be moved from one location to
another and its characteristics can be modified.
agent
A program that regularly gathers information or performs some other service without the user's
immediate presence.
application
A logically related set of processes active on a system (a running application) and/or a logically
related set of files on a machine disk (an installed application).
BladeSystem
The HP product portfolio of blade form factor computing devices that provide versatile computing
configurations, integrated network connectivity, and power management capabilities. BladeSystem
options are available in both the Integrity and ProLiant product lines.
See also BladeSystem enclosure, BladeSystem Integrated Manager.
BladeSystem
enclosure
Hardware solution that provides a flexible selection of half- or full-size server blades and associated
components (such as integrated connectivity to storage and data networks, and shared power
subsystems) into a single unit.
See also BladeSystem Integrated Manager.
BladeSystem
Integrated
Manager
A software component in HP Systems Insight Manager that enables users to navigate the blade
servers, enclosure infrastructures, racks, and integrated switches in their BladeSystem environment
by way of pictorial and hierarchical tree representations.
callout icons
Graphical icons that display in the right-hand corner of compartments or subcompartments.
Information callout icons show the system or workload attributes. Meter callout icons show
expanded information about the utilization meters that appear to the left of the icon. The utilization
meters display the recent utilization metrics for CPU, memory, disk, and LAN. See Matrix OE
visualization online help for explanation of icons appearing on the Visualization tab.
cell
A circuit board that contains processors and memory, all controlled by a cell controller (CC). A
cell is the basic building block of an nPartition in a complex.
cell-based server
A server in which all cores and memory are contained in cells, each of which can be assigned
for exclusive use by an nPartition. Each nPartition runs its own instance of an operating system.
CMS
Central Management Server. A system in a server management domain that runs HP Systems
Insight Manager (HP SIM). All central operations within HP SIM are initiated from this system.
compartment
An nPartition, virtual partition, virtual machine, or resource partition for which resources are
allocated by HP Global Workload Manager (gWLM).
Multiple compartments are grouped to form a shared resource domain (SRD). The compartments
all share the resources of the SRD. A compartment can be in only one SRD. Each compartment
holds a workload. gWLM manages each workload's resource allocation by adjusting the resource
allocation of its compartment.
On the Matrix OE Visualization tab, compartments are represented by color. You can select the
entire compartment or individual members within a compartment, then select a drop-down menu
item to operate on the selected item.
complex
A complex includes one or more cabinets that are cabled together and all of the hardware
resources that they contain. A complex has a single service processor.
core
The actual data-processing engine within a processor. A single processor might have multiple
cores, and a core might support multiple execution threads.
FSS group
Fair-Share Scheduler group. A group of processes that has its CPU allocation managed by the
HP-UX Fair Share Scheduler. FSS groups allow you to allocate fractions of cores, rather than only
whole cores, to the processes in the group.
GiCAP
HP Global Instant Capacity. Software that enables you to move usage rights for Instant Capacity
components within a group of servers.
See also iCAP, TiCAP.
63
iCAP
HP Instant Capacity. The product allows you to purchase and install additional processing power
through the use of a two-step purchase model. Initially, you purchase system components (cores,
cell boards, memory) at a fraction of the regular price because the usage rights are not included.
These Instant Capacity components are inactive but installed and ready for use. When extra
capacity is needed, you pay the remainder of the regular price for the usage rights to activate
the components. If the regular price for the component is reduced by the time the usage rights
are purchased, the remainder price is proportionally reduced, providing additional savings.
See also GiCAP, TiCAP.
logical server
A logical server is the complete software image of a server, including operating system,
applications, configuration data, and metadata that you create and assign to operate on a
physical server or virtual machine. Logical servers simplify the provisioning, management, and
movement of servers; and they allow you to quickly populate an enclosure, load balance servers,
and evacuate servers in case of disaster. Using logical servers, you can provision resources only
when needed, increasing optimal utilization of limited compute resources. Logical servers are a
feature of the HP Matrix Operating Environment.
See also active logical server.
LTU
License to use.
managed instance
A resource that is managed via a public cloud service provider. These resources are represented
as Cloud Resources inside HP CloudSystem Matrix and can be added to a server pool in the
same way as any other VM Host or ESX Resource Pool.
managed system
A server or other system that can be managed and monitored by HP Insight Management software
from an HP Systems Insight Manager CMS. A system can be managed and monitored by more
than one CMS.
managed
workload
A workload that is managed by HP Global Workload Manager.
management
domain
A CMS and its managed systems.
Matrix KVM
Private Cloud
Used to deploy a management Kernel Virtual Machine to a virtual data center (a cloud), and to
manage the VM hosts and deployed KVM instances.
monitored
workload
A workload that can be monitored by the HP Matrix Operating Environment, but has no policy
associated with it. Monitored workloads are not managed by HP Global Workload Manager.
nPartition
A partition in a cell-based server that consists of one or more cells and one or more I/O
components. Each nPartition operates independently of other nPartitions and either runs a single
instance of an operating system or is further divided into virtual partitions.
nPartitions can be used as compartments managed by HP Global Workload Manager (gWLM)
as long as several requirements are met. Refer to the gWLM online help for a description of
nPartition requirements.
See also virtual partition.
parked workload
A workload that is not currently associated with a system. A workload becomes parked if its
system is set to “none” when it is created or later modified. A parked workload that was previously
associated with a system may have historical data associated with it from Capacity Advisor or
HP Global Workload Manager. As with any workload, the historical data is lost if the workload
is deleted.
When migrating a workload from one system to another, it may be useful to park the workload
(removing the association with the original system) until the new system becomes available. This
preserves the historical data for the workload across the migration.
partition
64
Glossary
1.
A subset of server hardware that includes core, memory, and I/O resources on which an
operating system (OS) can be run. This type of partitioning allows a single server to run an
OS independently in each partition with isolation from other partitions.
2. A resource partition, made up of either a Fair-Share Scheduler (FSS) group or a processor
set, that runs within a single OS. This type of partitioning controls resource allocations within
an OS.
See also nPartition, virtual partition.
policy
A collection of rules and settings that control compute resources For example, an HP Global
Workload Manager (gWLM) policy can indicate the minimum and maximum amount of CPU
resources allowed for a workload, and a target to be achieved.
A single policy can be associated with multiple workloads.
provision
A function that makes a component operational. Provisioning might include installing, upgrading,
loading, and configuring a software or hardware component. Provisioning a server includes
loading the appropriate software (operating system and applications), customizing and configuring
the system, and starting the server and its newly-loaded software. This makes the system ready
for operation.
PSET
Processor set. A collection of processors grouped together for exclusive access by applications
assigned to that processor set. Each application runs only on processors in its assigned processor
set.
Public cloud
bursting
A feature of HP CloudSystem that enables enterprises to broker service delivery across multiple
clouds from a single, integrated point of control.
resource partition
A subset of the resources available to an operating system instance, isolated for use by specific
processes. A resource partition has its own process scheduler. CPU resources in the partition may
be allocated using Fair-Share Scheduler groups or processor sets. Policies for controlling the
allocation of resources to the partition can be set using HP Global Workload Manager.
Savvis
A managed hosting and cloud services provider capable of meeting dynamic demand for
outsourced IT and cloud services.
server blades
Thin, modular, self-contained computer servers, containing one or more microprocessors and
memory. Server blades are designed for high density and eliminate many components such as
power cords and network cables that are present in traditional rack-mount systems.
See also BladeSystem enclosure.
service processor
An independent support processor for HP servers that support nPartitions. The service processor
provides a menu of service-level commands, plus commands to reset and reboot nPartitions and
configure various parameters.
The service processor in HP servers is sometimes called the management processor (MP) or the
guardian service processor (GSP).
Serviceguard
cluster
An HP Serviceguard cluster is a networked group of HP 9000 or HP Integrity servers (host systems
known as nodes) having sufficient redundancy of software and hardware that a single point of
failure will not significantly disrupt service.
Serviceguard
package
Packages are the means by which HP Serviceguard starts and halts configured applications. A
package is a collection of services, disk volumes and IP addresses that are managed by
Serviceguard to ensure they are available.
Serviceguard
workload
A monitored workload associated with a Serviceguard cluster and a particular package within
the cluster. The workload (and the utilization data reported) follows the package it is associated
with as it moves between the nodes of the cluster.
SMI-S
Storage Management Initiative Specification. SMI-S delivers open storage network management
interface technology in order to have “all storage managed by the SMI interface” as the unifying
factor between all objects that must be managed in a storage area network and the tools used
to manage them.
socket
(CPU socket). The physical chip carrier on the circuit board that houses a CPU chip. The CPU
may consist of multiple cores.
SPM
HP Storage Provisioning Manager, a service-oriented storage provisioning solution bundled with
Matrix OE.
SRD
Shared resource domain. A collection of compartments that share system resources managed by
HP Global Workload Manager (gWLM). The compartments can be nPartitions, virtual partitions,
virtual machines, processor sets (PSETs) or Fair-Share Scheduler (FSS) groups.
A server containing nPartitions can be an SRD as long as nPartition requirements are met.
A server or an nPartition divided into virtual partitions can be an SRD for its virtual partition
compartments. A VM Host can be an SRD to its virtual machines. Similarly, a server, an nPartition,
or a virtual partition containing PSETs can be an SRD for its PSET compartments. Finally, a server,
65
an nPartition, or a virtual partition containing FSS groups can be an SRD for its FSS-group
compartments.
A complex with nPartitions can hold multiple SRDs. For example, if the complex is divided into
nPartitions named Par1 and Par2, Par1's compartments could be virtual partitions, while Par2's
compartments are PSETs.
SSL
Secure Sockets Layer. Protocol for validating identity and for creating an encrypted connection
between a server and a Web browser.
system
1.
2.
A server, nPartition, virtual partition, or virtual machine that is running an instance of an
operating system.
Entities on the network that communicate through TCP/IP or IPX. To manage a system, some
type of management protocol (for example, SNMP, DMI or WBEM) must be present on the
system. Examples of systems include servers, workstations, desktops, portables, routers,
switches, hubs and gateways.
TiCAP
Temporary Instant Capacity. An HP product that enables customers to purchase prepaid core
activation rights for a specified (temporary) period of time. Temporary capacity is sold in 30
processing-day increments.
See also GiCAP, iCAP.
Utilization Provider
The WBEM services provider for real-time utilization data from managed systems.
VCEM
Virtual Connect Enterprise Manager. A management tool for defining a server connection profile
for each server bay. This profile establishes the media access control (MAC) addresses for all
network interface controllers (NICs), the World Wide Names (WWNs) for all host bus adapters
(HBAs), and the SAN boot parameters. If the server blade in the server bay is replaced, the
configuration and connection profile stays constant.
virtual machine
A software entity provided by HP Integrity Virtual Machines, VMware ESX, VMware ESXi, or
Microsoft Hyper-V. This technology allows a single server or nPartition (with Integrity Virtual
Machines) to act as a VM Host for multiple individual virtual machines, each running its own
instance of an operating system (referred to as a guest OS). Virtual machines are managed
systems in the HP Matrix Operating Environment.
virtual partition
A software partition of a server, or of a single nPartition, where each virtual partition can run its
own instance of an operating system. A virtual partition cannot span an nPartition boundary.
See also nPartition, virtual machine.
VM Host
A server running HP Integrity Virtual Machines, VMware ESX, VMware ESXi, Microsoft Hyper-V
or Matrix KVM Private Cloud, that provides multiple virtual machines, each running its own
instance of an operating system.
vPars
An HP software product that provides virtual partitions.
See also virtual machine.
vPars monitor
The program that manages the assignment of resources to virtual partitions in a vPars-enabled
system. To enable virtual partitions, the vPars monitor must be booted in place of a normal HP-UX
kernel. Each virtual partition running under the monitor then boots its own HP-UX kernel.
See also VM Host.
WBEM
Web-Based Enterprise Management. A set of web-based information services standards developed
by the Distributed Management Task Force, Inc. A WBEM provider offers access to a resource.
WBEM clients send requests to providers to get information about and access to the registered
resources.
See also Utilization Provider.
WMI
Windows Management Instrumentation. HP Matrix Operating Environment uses WMI for data
collection from managed systems running Microsoft Windows. WMI queries and responses are
converted to WBEM through the WMI Mapper.
workload
A collection of processes in a standalone server, nPartition compartment, virtual partition
compartment, or virtual machine compartment. HP Global Workload Manager (gWLM) extends
this concept to include processor set (PSET) compartments and Fair-Share Scheduler (FSS) group
compartments.
See also managed workload, monitored workload, Serviceguard workload.
66
Glossary
Index
A
agent
removing unneeded agents, 30
agentless data collection, 30
configuring credentials, 28
Analysis tab, 32
Application Discovery, 11
authorizations
setting, 23
user, 28
C
Capacity Advisor, 9
scenario, 9
Capacity Advisor Consolidation Software, 9
capacity planning, 9
Central Management Server see CMS
CMS, 7
check CMS configuration, 39
check CMS to managed node configuration, 40
HP-UX CMS installation, 27
memory requirements, 39
troubleshooting, 39
Windows CMS installation, 27
command
reference pages, 46
vseassist, 42, 52
vselicense, 57
communication
troubleshooting, 39
configuration
check CMS configuration, 39
check CMS to managed node configuration, 40
check managed node configuration, 41
managed system setup wizard, 23, 27, 39
D
data collection
Capacity Advisor service, 28
credentials required, 28
solving problems, 29
Diagnose menu, 39
disaster recovery, 11
E
event notification
data collection errors, 29
F
features
HP-UX CMS, 17
Windows CMS, 16
G
Global Workload Manager, 12
glossary, 63
gWLM see Global Workload Manager
H
HP Capacity Advisor, 7
HP Global Workload Manager (gWLM), 7
HP Insight Control, 7
HP Insight Management, 7
HP Instant Capacity Manager, 7
HP Instant Capacity software, 7
HP Integrity Virtual Server Manager, 7
HP Matrix OE visualization, 7, 8
HP Matrix Operating Environment infrastructure
orchestration, 7
HP Matrix Operating Environment recovery management,
7
HP SIM see Systems Insight Manager
HP Virtual Connect Enterprise Manager, 7
HP-UX Operating Environments, 24
I
infrastructure orchestration, 10
Insight Management, 7
installation
HP-UX CMS, 27
Windows CMS, 27
Instant Capacity, 12, 22
Integrity Virtual Server Manager, 13
L
license
adding and applying, 23
and HP Instant Capacity products, 22
applying with License Manager, 23
applying with managed system setup wizard, 23
configuration, 13
EULA, 19
HP-UX Operating Environments, 24
Integrity, 24
License Manager, 23
managed instance model, 24
managed system model, 19
management, 19
migration from earlier release, 24
order to apply on Windows managed systems, 23
scan for HP-UX licenses, 24
trial, 22
License Manager, 23
starting, 23
logical server management, 8
M
managed instance, 24
managed system
check CMS to managed node configuration, 40
check managed node configuration, 41
67
supported configuration, 13
troubleshooting, 39
managed system setup wizard, 23, 27, 39
using to apply licenses, 23
manpage, 46
manuals, 44
Matrix OE
Configure menu, 34
Create menu, 33
Delete menu, 34
Modify menu, 34
Policy menu, 35
Report menu, 35
tabs, 32
Tools menu, 33
Matrix OE licenses
for Capacity Advisor Consolidation software, 21
for HP Integrity servers, 20
for HP ProLiant servers, 20
for Instant Capacity products, 22
for non-HP servers, 21
for public cloud, 24
for trial licenses, 22
limited license for HP Operations Orchestration, 22
Matrix OE menu bar, 32
Matrix OE visualization tool bar
optons, 35
memory requirements, 39
metrics
configuring utilization measures to reflect your
environment, 29
P
Partition Manager, 12
Planning tab, 32
platform, 13
PowerBroker, 27
privilege elevation, 27
provisioning
infrastructure, 10
storage, 11
public cloud bursting, 24
R
recovery management, 11
related information, 44
remote command execution, 27
requirements
memory, 39
root access, 27
S
Shared Resource Domain tab, 12, 32
SIM
starting Matrix OE visualization , 31
SPM see Storage Provisioning Manager
Storage Provisioning Manager, 11
sub-OS workload, 30
sudo, 27
68
Index
Systems Insight Manager
customizing for Matrix OE visualization, 36
T
tabs
in Matrix OE, 32
tool bar options, 35
troubleshooting, 39
typographic conventions, 48
U
upgrade from earlier release, 30
user authorizations, 28
Utilization Provider, 30
V
Virtual Connect Enterprise Manager, 9
virtual machine
managing, 13
visualization
automatic display of favorite collection, 37
Visualization tab, 32
Visualization View
Matrix OE visualization tool bar, 35
vseassist, 42, 52
vselicense, 57
W
websites, 46
white papers, 44
workload
sub-OS workloads removed on upgrade, 30
Workload tab, 32
Download PDF
Similar pages