Hp Virtual Connect Enterprise Manager User Guide

HP Virtual Connect Enterprise Manager

User Guide

HP Part Number: 460924-002 Published: April 2008, second edition

Legal Notices

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

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 is a U.S. trademark of Microsoft Corporation. Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

About this document....................................................................................11

Intended audience................................................................................................................................11

Publishing history..................................................................................................................................11

Document organization..........................................................................................................................11

Typographic conventions........................................................................................................................11

Related documents................................................................................................................................12

HP encourages your comments...............................................................................................................12

1 Introduction.............................................................................................13

Key features and benefits.......................................................................................................................13

Key features....................................................................................................................................13

Key benefits....................................................................................................................................14

Platform support....................................................................................................................................14

Architectural overview............................................................................................................................14

HP Virtual Connect technology..........................................................................................................14

Managing HP Virtual Connect...........................................................................................................15

HP Virtual Connect Manager.......................................................................................................15

HP Virtual Connect Enterprise Manager.........................................................................................15

Virtual Connect Enterprise Manager operations...................................................................................16

Setup summary.....................................................................................................................................17

2 Installing and configuring Virtual Connect Enterprise Manager.......................19

Preparing for a VCEM installation...........................................................................................................19

VCEM checklist.....................................................................................................................................19

Prerequisites for installation....................................................................................................................19

Hardware installation requirements....................................................................................................20

Insight Control Management hardware installation requirements.......................................................20

Software installation requirements......................................................................................................20

Insight Control Management software installation requirements.........................................................20

Performing an installation.......................................................................................................................21

Performing an Insight Control Management integrated installation..........................................................21

Performing post-installation configuration tasks..........................................................................................34

Post-installation configuration tasks.....................................................................................................34

3 Managing VC Domains............................................................................37

VC Domains.........................................................................................................................................37

Requirements for adding a VC Domain to a VC Domain Group.............................................................38

VC Domain actions..........................................................................................................................39

Licensing an enclosure for VCEM.......................................................................................................40

Creating a VC Domain Group...........................................................................................................40

Adding a VC Domain to a VC Domain Group.....................................................................................40

Removing a VC Domain from a VC Domain Group..............................................................................41

Making changes to a VC Domain in VC Domain Maintenance..............................................................42

Changes in Virtual Connect Manager that might affect completing VC Domain Maintenance...............43

4 Managing VC Domain Groups..................................................................45

VC Domain Groups...............................................................................................................................45

Creating a VC Domain Group...........................................................................................................46

Updating a VC Domain Group configuration.......................................................................................46

Canceling a VC Domain Group configuration.....................................................................................48

Removing a VC Domain from a VC Domain Group..............................................................................48

Table of Contents 3

Removing a VC Domain Group.........................................................................................................49

5 Managing server profiles...........................................................................51

Profiles................................................................................................................................................51

Creating a profile............................................................................................................................52

Deleting a profile.............................................................................................................................53

Editing a profile...............................................................................................................................53

Assigning a profile...........................................................................................................................53

Unassigning a profile.......................................................................................................................53

Copying and assigning a profile to a bay...........................................................................................53

Moving a profile..............................................................................................................................54

Performing a VC Profile Failover.........................................................................................................54

Preconditions for VC Profile Failover..............................................................................................54

Designating spare bays...............................................................................................................54

Initiating VC Profile Failover through the VCEM CLI.........................................................................54

Initiating VC Profile Failover through the VCEM GUI........................................................................55

Initiating VC Profile Failover using HP SIM Automatic Event Handling................................................55

6 Managing bays.......................................................................................57

Bays....................................................................................................................................................57

Powering down a bay......................................................................................................................58

Assigning a profile to a bay..............................................................................................................58

Unassigning a profile from a bay.......................................................................................................59

Performing a VC Profile Failover.........................................................................................................59

Preconditions for VC Profile Failover..............................................................................................59

Designating spare bays...............................................................................................................59

Initiating VC Profile Failover through the VCEM CLI.........................................................................59

Initiating VC Profile Failover through the VCEM GUI........................................................................60

Initiating VC Profile Failover using HP SIM Automatic Event Handling................................................60

7 Managing MAC and WWN addresses......................................................63

MAC Addresses....................................................................................................................................63

Tracking individual MAC addresses....................................................................................................63

Creating MAC exclusion ranges........................................................................................................64

Deleting MAC exclusion ranges.........................................................................................................64

Reclaiming external MAC addresses...................................................................................................64

Adding custom MAC address ranges..................................................................................................65

Editing custom MAC address ranges..................................................................................................65

Removing custom MAC address ranges..............................................................................................65

WWN Addresses.................................................................................................................................65

Tracking individual WWN addresses.................................................................................................66

Creating WWN exclusion ranges......................................................................................................66

Deleting WWN exclusion ranges.......................................................................................................67

Allocating WWN addresses.............................................................................................................67

Reclaiming external WWN addresses................................................................................................67

Adding custom WWN address ranges...............................................................................................68

Editing custom WWN address ranges................................................................................................68

Deleting custom WWN address ranges..............................................................................................68

8 Tracking VCEM job status..........................................................................69

Jobs....................................................................................................................................................69

Job status message window...............................................................................................................69

Reviewing job details.......................................................................................................................70

Deleting jobs...................................................................................................................................70

4 Table of Contents

9 Upgrading Virtual Connect firmware after VCEM is managing VC Domains.....71

Preparation checklist..............................................................................................................................71

Performing the firmware update using the VC Domain Maintenance capability..............................................71

10 External manager account.......................................................................73

11 Command Line Interface usage in Virtual Connect Enterprise Manager..........75

Perform VC Profile Failover on specified VC Domain Bay Server..................................................................75

List details for specified VCEM job...........................................................................................................76

Show CLI Usage online help...................................................................................................................76

CLI Exit/Error codes..............................................................................................................................77

12 Troubleshooting Virtual Connect Enterprise Manager...................................79

Troubleshooting....................................................................................................................................79

A Job appears with Failed status........................................................................................................79

Enclosure has two Onboard Administrators, and one fails.....................................................................79

WWN exclusion range displays a conflict message even when there is no conflict...................................79

Missing enclosure model...................................................................................................................79

VCEM is prompting for Onboard Administrator credentials on a configured VC Domain...........................79

Unable to add VC Domain to a VC Domain Group..............................................................................79

Unable to add an unconfigured VC Domain to a VC Domain Group......................................................80

VC Domain displays Missing External Manager lock status...................................................................80

VC Domain displays Configuration Mismatch status..............................................................................80

VC Domain displays Connectivity failure status....................................................................................81

Operation fails to perform in the group and VC Domain Group is under updating process error message

appears.........................................................................................................................................82

Operation fails to perform in the VC Domain Group under Maintenance status........................................82

Remove from VC Domain Group job is successful but with errors............................................................82

VC Domain displays Expired License status..........................................................................................83

Error on database operation occurs....................................................................................................83

Errors occur while loading VCEM pages.............................................................................................83

Failed to execute VCEM operation because VC firmware not supported..................................................84

Creating a profile or adding a VC Domain to a VC Domain Group fails.................................................84

Uninstalling VCEM...........................................................................................................................84

Backing up and restoring VCEM........................................................................................................85

Edit profile does not display all the Fibre Channel SAN connections.......................................................85

Unable to change the MAC/WWN range in Virtual Connect Manager..................................................85

VCEM database is inaccessible or unretrievable with no backup, or VCEM file systems are corrupt with no

backup...........................................................................................................................................86

Enclosure has a hardware failure and must be replaced........................................................................86

VCEM is inaccessible because HP SIM was uninstalled.........................................................................87

An HP SIM-initiated custom tool calling the VCEM Failover CLI completed with an error stating The system

cannot find the path specified............................................................................................................87

Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is:

java.net.SocketTimeoutException: Read timed out.................................................................................87

VC Profile Failover fails during Onboard Administrator replacement.......................................................87

VCEM cannot power down ProLiant server model BL465 G1.................................................................88

VC Profile Failover CLI fails with Internal VCEM Error Message: VCEM failed to resolve the note [{0}]

message.........................................................................................................................................88

Cannot upgrade VCEM because one or more VC Domains are under VCEM control................................88

13 Appendix HP services and technical support..............................................89

HP contact information...........................................................................................................................89

Table of Contents 5

Glossary....................................................................................................91

Index.........................................................................................................95

6 Table of Contents

List of Figures

1-1 HP Virtual Connect technology..........................................................................................................15

1-2 Virtual Connect Enterprise Manager operations..................................................................................17

3-1 VC Domains page..........................................................................................................................37

4-1 VC Domain Groups.........................................................................................................................45

5-1 Profiles page..................................................................................................................................51

6-1 Bays page.....................................................................................................................................57

6-2 Window displaying the power status of a bay....................................................................................58

6-3 Bay status with tab and hold.............................................................................................................58

7-1 MAC Ranges List page....................................................................................................................63

7-2 WWN Ranges List page..................................................................................................................66

7-3 WWN Ranges List page..................................................................................................................67

8-1 Jobs list..........................................................................................................................................69

12-1 Backing up and restoring VCEM.....................................................................................................85

List of Tables

2-1 Insight Control Management hardware installation requirements............................................................20

2-2 Insight Control Management software installation requirements.............................................................20

About this document

Intended audience

This document is intended to be used by technical professionals who manage multiple HP BladeSystem enclosures and use HP Virtual Connect Manager to control network connectivity. This documentation assumes that you have installed Virtual Connect Manager, have read the

User Guide

Publishing history

Document organization

• Chapter 1, Introduction, provides an overview of Virtual Connect Enterprise Manager, its key features

• Chapter 2, Installing and configuring Virtual Connect Enterprise Manager, provides an installation

• Chapter 3, Managing VC Domains, provides requirements for adding a VC Domain to a VC Domain

• Chapter 4, Managing VC Domain Groups, provides information on creating a VC Domain Group,

• Chapter 5, Managing server profiles, provides information on creating and managing server profiles

• Chapter 6, Managing bays, provides information on powering down a bay, assigning a profile to a

• Chapter 7, Managing MAC and WWN addresses, provides information on managing MAC and

• Chapter 8, Tracking VCEM job status, provides information on Job status message windows, reviewing

• Chapter 9, Upgrading Virtual Connect firmware after VCEM is managing VC Domains, describes the

• Chapter 10, External manager account, describes how to remove an external manager account from

• Chapter 11, Command Line Interface usage in Virtual Connect Enterprise Manager, describes command

• Chapter 12, Troubleshooting Virtual Connect Enterprise Manager, identifies and provides solutions for

• Chapter 13, HP services and technical support, provides information for HP software support services.

, and understand its concepts.

and benefits, platform support, an architectural overview, and setup summary.

checklist, prerequisites for installation, and the procedures for installation and post-installation configuration.

Group and describes VC Domain actions.

updating and canceling a VC Domain Group configuration, removing a VC Domain from a VC Domain Group, and removing a VC Domain Group.

for use with VCEM.

bay, unassigning a profile from a bay, and performing VC Profile Failovers.

WWN addresses using VCEM.

job details, and deleting jobs.

additional steps required when for upgrading Virtual Connect firmware when VCEM is managing the VC Domain.

a Virtual Connect Manager. Removing the external the external manager account results in Virtual Connect Manager being removed from VCEM control.

line usage in VCEM for VC Failover operations.

commonly encountered issues, as well as answers to frequently asked questions.

HP Virtual Connect for c-Class BladeSystem

Publication dateEdition numberManufacturing part number

April 20081.10460924-002

November 20071.0460924-001

Typographic conventions

find

(1) HP-UX manpage. In this example, “find” is the manpage name and “1” is the

manpage section.

Book Title

Title of a book or other document.

Intended audience 11

Linked Title

http://www.hp.com A Web site 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

term Defined use of an important word or phrase.

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

<element> An element used in a markup language. attrib= An attribute used in a markup language.

HP encourages your comments

Your comments and suggestions regarding product features will help us develop future editions of VCEM. For contact information, see chapter 13.

12 About this document

1 Introduction

HP Virtual Connect Enterprise Manager (VCEM) simplifies the management of multiple HP BladeSystem enclosures that use HP Virtual Connect to control LAN and Storage Area Network (SAN) connectivity, helping organizations increase productivity, respond more quickly to business demands, and significantly reduce operating costs.

Built on the Virtual Connect architecture integrated into every BladeSystem c-Class enclosure, VCEM provides a central console to manage and control server-to-network connections for up to 100 BladeSystem enclosures, a single resource pool for LAN and SAN address administration, group-based configuration management, plus the rapid assignment and movement of server connection profiles and workloads across the data center.

Use VCEM in environments with multiple HP BladeSystem enclosures to complete key data center tasks quickly, reliably, and without disruption to production LANs and SANs. VCEM enables you to:

• Install new blade servers and enclosures

• Perform fast and cost-effective server recovery

• Complete planned systems maintenance with minimal downtime

• Deploy large Virtual Connect installations

• Rapidly migrate and repurpose blade servers

Together, Virtual Connect and VCEM create a change-ready data center environment that enables administrators to add, replace, and recover blade servers in minutes without impacting LAN and SAN availability, significantly reducing typical deployment and maintenance costs.

For more information on VCEM, see http://www.hp.com/go/vcem.

Key features and benefits

VCEM delivers the following key features and benefits.

Key features

The key features of VCEM include:

• Single intuitive console to control multiple HP BladeSystem infrastructures that use Virtual Connect to

control LAN and SAN connectivity

• Central database administers over 65,000 Media Access Control (MAC) and World Wide Names

(WWNs)

• Group-based management of multiple Virtual Connect domains using common baseline configuration

profiles

• Embedded maintenance tools to configure and modified Virtual Connect network settings

• Scripted and manual movement of server connection profiles and associated workloads between

BladeSystem enclosures

• Automated failover of server connection profiles and workloads to spare server pools

• Flexible options enable VCEM to be installed as a physical stand-alone server, as a plug-in to HP

Systems Insight Manager (HP SIM) 5.2 and later, and as a VMware ESX virtual machine

• Integrates seamlessly and extends Virtual Connect infrastructures—Discovers existing VC Domains and

aggregates resources into a central VCEM console

• Licensed per c-Class enclosure—Simplifies deployment and enables VCEM support for current and

future blade server hardware

Key features and benefits 13

Key benefits

The key benefits of VCEM include:

• Centrally manage individual and groups of BladeSystem enclosures that use Virtual Connect to control

LAN and SAN connectivity

• VCEM database enables more efficient LAN and SAN address management and eliminates conflicts

• Group-based management of Virtual Connect domains increases infrastructure consistency and enables

rapid change management across multiple enclosures using a single task

• Add, change, and replace servers across the data center in minutes when your business needs it without

impacting production LAN and SAN availability

• Significantly reduce the costs and time to deploy and maintain BladeSystem infrastructures

• Increase productivity and server-to-administrator ratios

• Release LAN and SAN administrators from routine server administration tasks

• Scalable across small and large data center environments

Platform support

VCEM is supported on a defined set of HP BladeSystem c-Class hardware, storage, software, and third-party operating platforms.

For a full list of supported platforms and components, see the

HP Insight Control Management Support Matrix.

Architectural overview

This section provides an overview of the architecture, functionality, and operations of Virtual Connect technology and VCEM.

HP Virtual Connect technology

HP Virtual Connect is a virtual I/O technology for HP BladeSystem that simplifies the setup and administration of server connections to LANs and SANs. Virtual Connect is also a key building block in the HP Adaptive Infrastructure strategy, which is designed to help organizations build next-generation data centers.

The Virtual Connect architecture is built into every HP BladeSystem c-Class enclosure, and extended through standard Ethernet and Fibre Channel hardware module options that plug into the interconnect bays of the enclosure. Virtual Connect uses pools of MAC address and World Wide Names in combination with server profiles to establish dynamic connections between HP BladeSystem servers and production networks. Virtual Connect enables IT organizations to wire LAN and SAN connections once, then add, replace, or recover servers in minutes, rather than hours, days, or weeks. With Virtual Connect you can:

• Significantly reduce cabling and server connection complexity

• Maintain constant end-to-end connections to preferred fabric brands

• Separate server enclosure administration from LAN and SAN administration

• Enable system administrators to make server changes more optimally without impacting LAN or SAN

operations and administrators

• Relieve LAN and SAN administrators from server-centric maintenance

The following figure illustrates Virtual Connect technology.

14 Introduction

Figure 1-1 HP Virtual Connect technology

Virtualized server connectivity to LAN and SAN increases productivity and reduces complexity and costs.

Managing HP Virtual Connect

A Virtual Connect server profile is a logical grouping of server connection attributes that can be assigned to any bay in a BladeSystem enclosure—also called a VC Domain. When assigned to an enclosure bay, the server in that bay assumes the attributes of the profile which can include:

• MAC addresses for all NICs

• WWNs for all Host Bus Adapters (HBAs)

• Fibre Channel SAN boot parameters

HP provides a choice of management tools that enable administrators to quickly pre-configure and modify Virtual Connect server profiles and assign them dynamically to BladeSystem enclosures and bays. Associating LAN and SAN connections to enclosure bays means that even if the server environment changes the network connections remain constant.

HP Virtual Connect Manager

Virtual Connect Manager is a web-based console integrated into Virtual Connect Ethernet module firmware, providing local management for individual VC Domains.

Typical Environment—Small environments with HP BladeSystem c-Class and Virtual Connect contained in a local data center.

HP Virtual Connect Enterprise Manager

Virtual Connect Enterprise Manager (VCEM) is an advanced software application that provides centralized management for multiple BladeSystem enclosures configured with Virtual Connect. VCEM uses a single console to manage many BladeSystem enclosures, a central resource pool for LAN and SAN address administration, and grouping capabilities that enable rapid, reliable deployment and movement of server connection profiles between blade enclosures and across the data center.

Typical Environment

• Medium to large HP BladeSystem environments that use Virtual Connect

• BladeSystem environments that extend to multiple locations, such as remote sites or across data centers

Architectural overview 15

• Organizations that require centralized administration of Virtual Connect infrastructures to control

server-to-network connectivity.

• Organizations that require rapid server movement between enclosures—can be used for cost effective

server recovery, planned maintenance, and server repurposing.

For more information about Virtual Connect and Virtual Connect Manager, see the

c-Class BladeSystem User Guide.

Virtual Connect Enterprise Manager operations

VCEM extends Virtual Connect technology with a single console that aggregates the management and control of multiple BladeSystem infrastructures. This intuitive solution delivers advanced Virtual Connect management that leverages and integrates with other HP management tools, including HP SIM, Virtual Connect firmware, and the Onboard Administrator integrated into HP BladeSystem c-Class enclosures.

VCEM can be installed in a variety of configurations that include a physical stand-alone console, as a plug into HP SIM 5.2 or later, and as a VMware ESX Server virtual machine.

VCEM uses its own dedicated homepage to perform the following core tasks:

• Discover and import existing VC Domains

• Aggregate individual Virtual Connect address pools for LAN and SAN connectivity into a centrally

administered VCEM address database

• Create VC Domain Groups

• Assign and un-assign VC Domains to domain groups

• Define server profiles and link to available LAN and SAN resources

HP Virtual Connect for

• Assign server profiles to BladeSystem enclosures, enclosure bays and VC Domain Groups

• Change and re-assign server profiles to alternative enclosures and enclosure bays. Use this capability

to quickly perform server recovery, planned maintenance, and multiple server repurposing across the data center.

• Rapidly install new bare-metal HP BladeSystem enclosures by assigning to a VC Domain Group

The following figure identifies the main elements associated with the implementation and operations of VCEM.

16 Introduction

Figure 1-2 Virtual Connect Enterprise Manager operations

VCEM centralizes Virtual Connect infrastructure management and aggregates LAN and SAN address pools.

NOTE: VCEM does not support profile failover for Integrity server blades or profile moves of Integrity

blades in a 'boot from SAN' configuration. Profile moves for Integrity blades with local boot storage are supported by VCEM.

Setup summary

To configure VCEM into an existing HP BladeSystem environment running Virtual Connect:

1. Verify that existing Virtual Connect module firmware and HP Onboard Administrator firmware meets the minimum requirements.

2. Install the VCEM software on a designated host system running Microsoft Windows Server 2003 SP2 or later using the HP Insight Control Management (ICM) DVD.

ICM media can be downloaded from http://www.hp.com/go/insightcontrol.

NOTE: For a complete list of hardware, firmware, and software requirements, see “Prerequisites for

installation”.

3. Open the VCEM console, and discover all existing VC Domains.

4. From the list of discovered domains, select which ones you want to manage using VCEM.

5. Apply a single VCEM license to the BladeSystem enclosure of each domain to be managed. A VCEM license enables operations across all bays in an enclosure for the life of the enclosure.

6. From the VCEM console, create a VC Domain Group, and assign an available VC Domain to the group.

• The configuration of the first domain in a VC Domain Group defines the characteristics for all

subsequent group members.

• All domains in a group have the same Virtual Connect uplink connections to LAN and SAN.

Setup summary 17

After you complete these steps, VCEM is now ready to be used to centrally manage your HP BladeSystem and Virtual Connect infrastructures. You can now add, change, and move blade servers across the data center in minutes.

18 Introduction

2 Installing and configuring Virtual Connect Enterprise

Manager

This chapter describes how to install and configure VCEM.

IMPORTANT: This guide assumes that you have installed Virtual Connect Manager, have read the

Virtual Connect for c-Class BladeSystem User Guide

Preparing for a VCEM installation

To prepare for a VCEM installation, decide which type of installation is best for your environment. VCEM

1.10 can be installed or upgraded as a stand-alone product. VCEM can also be installed as part of a full

HP SIM installation that enables administrators to take advantage of other HP SIM-based plug-in tools. Possible installation scenarios include:

• Upgrade a standalone VCEM 1.00 installation to a VCEM 1.10 standalone installation.

This installation uses the ICM DVD VCEM Standalone option.•

• This installation upgrades VCEM 1.00 to a 1.10 standalone version with no loss of information.

• This installation offers no HP SIM plug-in support.

• Perform a new VCEM 1.10 standalone installation.

This installation uses the ICM DVD VCEM Standalone option.•

• This installation installs a new 1.10 standalone version of VCEM.

• This installation offers no HP SIM plug-in support.

• Perform a new VCEM 1.10 installation along with HP SIM.

This installation uses the Insight Control Management suite customized List option.•

, and understand its concepts.

• This installation installs HP SIM as well as VCEM 1.10.

• This installation can be made on a system already running HP SIM.

• This installation upgrades a previous version of HP SIM to the current version.

• This installation fully supports SIM plug-in installations.

• Perform a new VCEM 1.10 installation as part of a HP Insight Dynamics - VSE installation.

VCEM 1.10 is installed as part of the suite but is licensed separately.•

• Will upgrade a previous version of SIM to the current version.

• Fully supports HP SIM plug-in installations.

• Perform a new VCEM 1.10 installation and migrate a VCEM 1.00 installation.

1. Install VCEM 1.10 as a new standalone installation or as part of a new HP SIM installation as described previously.

2. Migrate the VCEM 1.00 data to VCEM 1.10.

For more information about VCEM 1.0 migration, see http://www.hp.com/go/vcem.

VCEM checklist

You must have the following information before performing a VCEM installation:

Prerequisites for installation

This section describes the server prerequisites for installing VCEM, including the hardware and software prerequisites.

Preparing for a VCEM installation 19

Hardware installation requirements

Insight Control Management hardware installation requirements

The "Insight Control Management hardware installation requirements" lists the hardware installation requirements for Insight Control Management.

Table 2-1 Insight Control Management hardware installation requirements

SpecificationComponent

Server

Disk space

HP ProLiant BladeSystem c-Class or p-Class server blades, or HP ProLiant 300, 500, and 700 series ML or DL servers

At least 2 GB RAM (4 GB RAM recommended)Memory

At least 1.6 GHz (2 GHz or faster recommended)Processor

At least 5 GB for Insight Control Management software. However, the actual amount of disk space may vary according to the number of Insight Control Management components selected to install.

New Technology File System (NTFS)File structure

Local or mapped DVD drive requiredDVD drive

Insight Control Management suites support installation on VMware ESX 3.0.1 and 3.0.2 virtual servers.

IMPORTANT: Insight Control Environment licenses all ProLiant ML and DL 300, 500, and 700 servers.

Insight Control Environment for BladeSystem licenses all ProLiant BladeSystem servers and select BladeSystem workstations. See the appropriate component support matrixes to understand the server hardware and operating system support for each particular component.

Insight Control Environment supports the new HP ProLiant ML785 server, but Insight Power Manager does not support this server.

Software installation requirements

Insight Control Management software installation requirements

The "Insight Control Management software installation requirements" table lists the software installation requirements for Insight Control Management. Installations with Microsoft Data Engine (MSDE) 2000 SP3a will be migrated to Microsoft SQL 2005 Express Edition SP2.

Table 2-2 Insight Control Management software installation requirements

SpecificationComponent

Operating system

Services

Database

Microsoft Windows Server® 2003, Standard Edition SP2 (32-bit only)

Windows Server 2003, Enterprise Edition SP2 (32-bit only) Windows Server 2003 R2, Standard Edition SP2 (32-bit only) Windows Server 2003 R2, Enterprise Edition SP2 (32-bit only)

.NET 2.0 Framework SNMP TCP/IP with DNS installed so that system names must resolve to

an IP addresses. It is necessary that IP addresses must resolve to system names.

Microsoft SQL Server 2005 Express Edition SP2 * Microsoft SQL Server 2000 Standard Edition, SP3 or SP4 (for

Standard Server operating system) Microsoft SQL Server 2000 Enterprise Edition, SP3 or SP4 (for

Advanced Server operating system) Microsoft SQL Server 2005 running on Windows Server 2003

20 Installing and configuring Virtual Connect Enterprise Manager

SpecificationComponent

Applications

* SQL Server 2005 Express Edition supports 500 systems and 5,000 events.

IMPORTANT: If you are upgrading previous ICM installations with a local version of Rapid Deployment Pack, you must first install

Microsoft WAIK 2.1, also known as the "Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008". It is available at http://www.microsoft.com/downloads/details.aspx?familyid=94bb6e34-d890-4932-81a5-5b50c657de08.

NOTE: The CMS supports Windows 2000 and 2003 International Server - French, German, Italian, Spanish, and Japanese (latest

service pack available for each language).

Microsoft Internet Explorer 6.0 SP1 or 7.0

Adobe® Acrobat® Reader

Mozilla Firefox 1.5.0.12 (not supported by all components) Mozilla Firefox 2.0.0.4 (not supported by all components)

VMware ESX 3.0.1 or 3.0.2 (supported installation platform)Virtualization platform

Performing an installation

Performing an Insight Control Management integrated installation

IMPORTANT: Be sure that maintenance activities do not reboot the system during installation.

The Insight Control Management integrated installation is completed in a single process, with all Insight Control Management software components installed on a single management server. Variations to this installation process might occur under any of the following scenarios:

• If HP SIM 5.1 or higher is already installed, Insight Control Management and all its components are

installed on the HP SIM Central Management Server (CMS). If necessary, HP SIM and all its components are updated to the latest version.

• If Rapid Deployment Pack 3.10, 3.50, or 3.60 is installed on your HP SIM CMS, Insight Control

Management upgrades Rapid Deployment Pack to version 3.70.

• If Rapid Deployment Pack 3.70 is already installed, you can provide the Insight Control Management

installer with information to incorporate your existing Rapid Deployment Pack installation. In this configuration, the Rapid Deployment Pack 3.70 can reside on the same server or on a different server from the HP SIM CMS.

• If neither HP SIM nor Rapid Deployment Pack is present, both components are installed, along with the

other Insight Control Management components, during the Insight Control Management integrated installation process.

IMPORTANT: Microsoft IIS 6.0 or later must be installed on the target CMS to successfully install and use

the Vulnerability and Patch Management Pack. For more information about configuring HTTPS service in IIS, see http://support.microsoft.com/?kbid=324069.

NOTE: Before beginning the installation process, identify all operating systems to be deployed.

You can install or upgrade an Insight Control Management or HP Insight Dynamics - VSE suite either by management suite or by customized product list, selecting one or more suites or components for installation. Individual components may also be installed or upgraded using the integrated installer. In addition an option to install Virtual Connect Enterprise Manager (VCEM) in Standalone mode, the only mode supported in VCEM 1.0, is available from the main installer screen. The standalone install option can also be used to upgrade a VCEM 1.0 installation to 1.10 in standalone mode. Note this upgrade option only updates a VCEM 1.0 to standalone mode. A migration utility is available at http://www.hp.com/go/vcem to help upgrade VCEM 1.0 standalone data to a VCEM 1.10 SIM plug-in installation. A VCEM standalone installation requires a dedicated physical or virtual server to host the application, and uses a specialized version of HP Systems Insight Manager that does not support the installation of additional Insight Control software plug-ins.

Performing an installation 21

To install Insight Control Management, perform the following procedure. If you need help at any time during the installation process, click the ? icon.

1. Insert the Insight Control Management DVD into the DVD-ROM of the intended management server. The End User License Agreement appears. Read the agreement, and then to continue, click Agree.

2. The Welcome to the Insight Control Management DVD screen appears. To ensure that your environment meets the appropriate installation requirements, click Run Insight Control Advisor.

The Insight Control Environment Advisor screen appears. The Insight Control Environment Advisor is a tool that verifies the target platform for compliance with installation prerequisites.

3. Click Run Now. The Welcome to Insight Control Environment Advisor results screen identifies issues that could affect the installation of the Insight Control Management suite. The following example screen shows three items that could affect the installation of the Insight Control Management suite. For more information on those issues, click the corresponding hyperlinks, and then resolve the issues.

22 Installing and configuring Virtual Connect Enterprise Manager

The Welcome to Insight Control Environment Advisor screen reappears. Resolve any remaining issues or click Close to exit Insight Control Environment Advisor.

After you close Insight Control Management Advisor, the Welcome to the Insight Control Management DVD screen reappears.

4. On the Welcome to the Insight Control Management DVD, click Review Installation Checklist. A PDF of the Insight Control Management Installation Checklist appears. You must identify the configuration parameters or configure the settings as listed in the checklist. The integrated installer uses this information to implement and configure HP SIM and the ProLiant Essentials products.

5. On the Welcome to the Insight Control Management DVD, click Run Integrated Installer. The Welcome to the Insight Control Management Installer screen appears.

Performing an installation 23

Choose either of the following options:

• To install by management suite, select management suite, click Next, and then go to step 6.

• To install by customized product list, select customized list, click Next, and then go to step 7.

• To install Virtual Connect Enterprise Manager (VCEM) in standalone mode or to upgrade a VCEM

1.0 install to 1.10 standalone mode, select HP Virtual Connect Enterprise (Standalone mode), click Next and then go to step 8. A standalone installation does not support installation of other HP SIM

related plug-in tools.

When installing by management suite, the Select installation by management suite screen appears.

6. Select the corresponding checkboxes of suites to install. This action automatically selects the appropriate components for installation. Previously installed components are automatically upgraded to the revisions provided. Components have expandable lists that enable you to see the list of components, as shown in the following figure. You can customize the default component selections in the next step. As previously noted VCEM is automatically installed with the HP Insight Dynamics suite option but is licensed separately.

NOTE: The ProLiant (Windows and Linux) targets checkbox is automatically selected when Insight

Control Environment suites are selected. This checkbox can be cleared if you are not managing ProLiant systems (that is, managing only Integrity blades).

When installing by customized product list or continuing with a management suite installation, the Select components for install or upgrade screen appears.

7. Select the corresponding checkboxes of components to install, and then click Next. Components have expandable lists that enable you to see their descriptions. The installer detects components already installed and uses or upgrades those components if they are the correct version or can be upgraded. Checkboxes for required components and previously installed components cannot be cleared. This option is used to install VCEM in Systems Insight Plug-in manager mode.

24 Installing and configuring Virtual Connect Enterprise Manager

The Warning screen appears, listing the system prerequisites for installation. Your system must meet all these prerequisites. Prerequisites are based on selections from step 7.

8. To use the Insight Control Environment Advisor to verify prerequisite status, click the run the Insight Control Environment Advisor hyperlink provided at the bottom of the Warning screen.

IMPORTANT: The installation server IP address is assigned by Dynamic Host Configuration Protocol

(DHCP). The IP address must not be changed.

IMPORTANT: If you are upgrading previous ICM installations with a local version of Rapid Deployment

Pack, you must first install Microsoft WAIK 2.1, also known as the "Automated Installation Kit (AIK) for

Performing an installation 25

Windows Vista SP1 and Windows Server 2008". It is available at http://www.microsoft.com/

downloads/details.aspx?familyid=94bb6e34-d890-4932-81a5-5b50c657de08.

9. Click Next. The Installation Directory screen appears.

10. Select the installation location by performing either of the following steps:

• To use the default directory location, click Next.

• To select a different directory, click Browse, or enter the path in the Installation Directory box

and click Next. If you previously installed Insight Control Management, then the installation directory remains the

same and cannot be changed. If you have already installed a component outside of Insight Control Management suite, then the integrated installer upgrades that component in the original installation location.

11. If you have selected Rapid Deployment Pack and it is not already installed, the HP Rapid Deployment Pack installation options screen appears where you must choose to install the Rapid Deployment Pack on this server or use Rapid Deployment Pack on an existing remote server.

26 Installing and configuring Virtual Connect Enterprise Manager

Choose either of the following options:

• To install on this server, select Install Rapid Deployment Pack on this server, and then select the

deployment network interface to be used by Preboot eXecution Environment (PXE).

• To use the Rapid Deployment Pack already installed on an existing remote server, select Use

existing remote Rapid Deployment Pack, and then enter the credentials.

IMPORTANT: If you use an existing remote RDP server, then DHCP services must be running on your

network to operate properly.

12. Click Next. If the locally installed Rapid Deployment Pack must be upgraded, the Use existing HP ProLiant Essentials Rapid Deployment Pack screen appears.

Performing an installation 27

13. From the Use existing HP ProLiant Essentials Rapid Deployment Pack enter the service credentials, and then click Next.

14. From the Service account credentials screen, enter the credentials, and then click Next. All Insight Control Management components use these credentials. If HP SIM is already installed, then the Username and Domain box are automatically populated.

28 Installing and configuring Virtual Connect Enterprise Manager

15. From the Database configuration screen, depending on whether the local database is detected, perform either of the following steps:

a. If a local database is detected, enter the credentials for the existing database, and then click Next. b. If no local database server is detected, select the appropriate option to install SQL 2005 Express,

or enter the name of a remote database server: i. To install Microsoft SQL 2005 Express, select Install SQL 2005 Express. ii. To use existing SQL Server 2000, 2005 (Enterprise, Standard or Express Editions), select Use

existing SQL Server 2000, 2005 (Enterprise, Standard or Express Editions).

c. Enter the password. To use an existing database, you must provide the server and database

information. Entering Instance Name is optional. click Next.

16. (Optional) From the Automatic logon configuration screen, to enable automatic logon after the installation reboot, select Enable Automatic Logon, and then provide logon credentials. These credentials are used only for the reboot initiated during the installation process.

The Automatic logon configuration screen appears only if HP SIM or Rapid Deployment Pack is installed or upgraded because the system requires a reboot during the installation process.

Performing an installation 29

+ 67 hidden pages