Virtual Connect

113
HP Virtual Connect Enterprise Manager User Guide HP Part Number: 460924-005 Published: September 2009, Fifth Edition

Transcript of Virtual Connect

Page 1: Virtual Connect

HP Virtual Connect Enterprise ManagerUser Guide

HP Part Number: 460924-005Published: September 2009, Fifth Edition

Page 2: Virtual Connect

© Copyright 2007, 2009 Hewlett-Packard Development Company, L.P.

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor'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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

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

Page 3: Virtual Connect

Table of Contents

About this document....................................................................................11Intended audience................................................................................................................................11Publishing history..................................................................................................................................11Related documents................................................................................................................................11HP encourages your comments...............................................................................................................11

1 Introduction.............................................................................................13Key features and benefits.......................................................................................................................13

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

What's new.........................................................................................................................................14Platform support....................................................................................................................................14Architectural overview............................................................................................................................14

HP Virtual Connect technology..........................................................................................................14Managing HP Virtual Connect...........................................................................................................15

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

VCEM operations............................................................................................................................16Setup and configuration summary...........................................................................................................17

2 Installing and configuring VCEM................................................................19Preparing for a VCEM installation...........................................................................................................19VCEM checklist.....................................................................................................................................19Prerequisites for installation....................................................................................................................19

Hardware requirements....................................................................................................................19Software requirements......................................................................................................................19

Supported configurations.............................................................................................................22Installing VCEM....................................................................................................................................23Performing post-installation configuration tasks..........................................................................................23

Post-installation configuration tasks.....................................................................................................23VCEM home page................................................................................................................................24

3 Managing VC Domains............................................................................27VC Domains.........................................................................................................................................27

Requirements for adding a VC Domain to a VC Domain Group.............................................................28Mixed Virtual Connect firmware versions and firmware compatibility in a VC Domain Group................31Virtual Connect 2.3x features that must be disabled in a VC Domain to be part of the VC Domain Groupwith Virtual Connect firmware 2.1x................................................................................................32Virtual Connect 2.1x features that must be disabled in a VC Domain to be part of the VC Domain Groupwith Virtual Connect firmware 2.0x...............................................................................................33

VC Domain tasks.............................................................................................................................34Licensing an enclosure for VCEM.......................................................................................................34Creating a VC Domain Group...........................................................................................................35Adding a VC Domain to a VC Domain Group.....................................................................................36Removing a VC Domain from a VC Domain Group..............................................................................37Working with multienclosure VC Domains...........................................................................................38VC Domain Maintenance..................................................................................................................40

VC Domain Group configuration replicated to other VC Domains during VC Domain Maintenance.......41Performing VC Domain Maintenance.............................................................................................43Backing up and restoring domain configurations through VC Domain Maintenance.............................43Changes in Virtual Connect Manager that might affect completing VC Domain Maintenance...............44Working with HP Virtual Connect 8Gb Fibre Channel Module for c-Class BladeSystem........................45

Table of Contents 3

Page 4: Virtual Connect

Adding or removing remote enclosures from a multienclosure domain in VC Domain Maintenance........45Canceling a VC Domain Maintenance task.........................................................................................45Resynchronizing a VC Domain with Configuration Mismatch..................................................................45

4 Managing VC Domain Groups..................................................................47VC Domain Groups...............................................................................................................................47

Creating a VC Domain Group...........................................................................................................48Maintaining a VC Domain from the VC Domain Group page................................................................49Canceling a VC Domain Group maintenance task...............................................................................50Upgrading VC Domain Group Firmware Mode....................................................................................50Deleting a VC Domain Group...........................................................................................................50Adding or removing VC modules to VC Domain Group configuration.....................................................51Moving Ethernet networks (VLANs tagged) from one shared uplink to another.........................................52Correlating VCEM operations in HP SIM and Virtual Connect logs.........................................................52

5 Managing server profiles...........................................................................53Profiles................................................................................................................................................53

Creating a profile............................................................................................................................55Configuring the target boot LUN........................................................................................................55Configuring multiple networks............................................................................................................56Configuring Network Port Speed........................................................................................................57Deleting a profile.............................................................................................................................58Editing a profile...............................................................................................................................58Verifying the presence of EFI partition data.........................................................................................58Assigning a profile...........................................................................................................................58Unassigning a profile.......................................................................................................................59Copying and assigning a profile to a bay...........................................................................................59Moving a profile..............................................................................................................................59Performing a VC Profile Failover.........................................................................................................59

Preconditions for VC Profile Failover..............................................................................................59Designating spare bays...............................................................................................................59Initiating VC Profile Failover through the VCEM CLI.........................................................................60Initiating VC Profile Failover through the VCEM GUI........................................................................60Initiating VC Profile Failover using HP SIM Automatic Event Handling................................................60

6 Managing bays.......................................................................................63Bays....................................................................................................................................................63

Powering down a bay......................................................................................................................64Assigning a profile to a bay..............................................................................................................65Unassigning a profile from a bay.......................................................................................................65Designating spare bays....................................................................................................................66Performing a VC Profile Failover.........................................................................................................66

Preconditions for VC Profile Failover..............................................................................................66Designating spare bays...............................................................................................................66Initiating VC Profile Failover through the VCEM CLI.........................................................................66Initiating VC Profile Failover through the VCEM GUI........................................................................66Initiating VC Profile Failover using HP SIM Automatic Event Handling................................................67

7 Managing MAC and WWN addresses.......................................................69MAC Addresses....................................................................................................................................69

Tracking individual MAC addresses....................................................................................................69Creating MAC exclusion ranges.........................................................................................................70Deleting MAC exclusion ranges.........................................................................................................70Reclaiming external MAC addresses...................................................................................................70Adding custom MAC address ranges..................................................................................................71Editing custom MAC address ranges..................................................................................................71

4 Table of Contents

Page 5: Virtual Connect

Removing custom MAC address ranges...............................................................................................71WWN Addresses.................................................................................................................................71

Tracking individual WWN addresses.................................................................................................72Creating WWN exclusion ranges......................................................................................................72Deleting WWN exclusion ranges.......................................................................................................73Allocating WWN addresses.............................................................................................................73Reclaiming external WWN addresses................................................................................................74Adding custom WWN address ranges...............................................................................................74Editing custom WWN address ranges................................................................................................75Deleting custom WWN address ranges..............................................................................................75

8 Working with Logical Serial Numbers.........................................................77Logical Serial Numbers..........................................................................................................................77

Identifying logical serial number values...............................................................................................77

9 Tracking VCEM job status..........................................................................79Jobs....................................................................................................................................................79

Job status message window...............................................................................................................79Reviewing job details.......................................................................................................................80Deleting jobs...................................................................................................................................80

10 Upgrading Virtual Connect firmware after VCEM is managing VC Domains...81Preparation checklist..............................................................................................................................81Performing the firmware update using the VC Domain Maintenance capability..............................................81

11 Removing an external manager account.....................................................83

12 Command Line Interface usage in VCEM...................................................85Perform VC profile failover on specified VC Domain bay server...................................................................85List details for specified VCEM job...........................................................................................................85Show CLI usage online help...................................................................................................................86CLI exit and error codes.........................................................................................................................87

13 Troubleshooting VCEM............................................................................89Troubleshooting....................................................................................................................................89

Unauthorized error when trying to access the VCEM home page............................................................89A job appears with Failed status........................................................................................................89Enclosure has two Onboard Administrators, and one fails.....................................................................89VCEM is prompting for Onboard Administrator credentials on a configured VC Domain...........................89Virtual Connect Manager does not accept Onboard Administrator credentials.........................................89Unable to add VC Domain to a VC Domain Group..............................................................................90Unable to add an unconfigured VC Domain to a VC Domain Group......................................................90Cannot manage a VC Domain when VC module failover is taking place.................................................90VC Domain displays Missing External Manager lock status....................................................................91VC Domain displays Configuration Mismatch status..............................................................................91VC Domain displays Connectivity failure status....................................................................................91Operation fails to perform in the VC Domain or VC Domain Group under maintenance status...................92Remove from VC Domain Group job is successful but with errors............................................................93VC Domain displays Expired License status..........................................................................................93Error on database operation occurs....................................................................................................94Errors occur while loading VCEM pages.............................................................................................94Failed to execute VCEM operation because VC firmware not supported..................................................94Creating a server profile or adding a VC Domain to a VC Domain Group fails........................................95Uninstalling VCEM...........................................................................................................................95

Table of Contents 5

Page 6: Virtual Connect

Backing up and restoring VCEM........................................................................................................95Cannot change the MAC/WWN/Serial Number ranges in Virtual Connect Manager when there are serverprofiles...........................................................................................................................................96VCEM database is inaccessible or irretrievable with no backup, or VCEM file systems are corrupt with nobackup...........................................................................................................................................96Enclosure has a hardware failure and must be replaced........................................................................97Replace VC modules in a VC Domain managed by VCEM....................................................................97Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is:java.net.SocketTimeoutException: Read timed out.................................................................................98VC Profile Failover fails during Onboard Administrator replacement.......................................................98VCEM cannot power down ProLiant server model BL465 G1.................................................................98After VC Domain is removed from VC Domain Group in VCEM, profile with external-managed status cannotbe edited through Virtual Connect Manager........................................................................................98Server profile edit operation fails when target server is powered on........................................................98Server profile network connections that use multiple networks are not working.........................................99Server profile network configuration was lost.......................................................................................99VC Domain status is "Mismatch Configuration" after cancel VC Domain Maintenance operation fails.........99Server profile job completed with success but changes have not occurred................................................99VCEM getting started online help screen does not appear automatically at HP SIM login........................100HP SIM customizations for VCEM have not taken place.......................................................................100After a server profile failover, some connections defined in the server profile are not functional................100Server profiles are not displaying physical port mapping and allocated bandwidth information................101VCEM page displays "Communication with the HP SIM server has been lost"........................................101VC Domain not discovered by HP SIM..............................................................................................101Create VC Domain Group or Add VC Domain to VC Domain Group operations fail and the message "Aninvalid boot LUN was entered. Check the storage arrays for the proper LUN number" appears................101Profile move, assign, or failover operations fail and the message "An invalid boot LUN was entered. Checkthe Storage arrays for the proper LUN number" appears.....................................................................102VC Domain Maintenance operation fails when moving Ethernet networks (VLANs tagged) from a deletedshared uplink set to another............................................................................................................102

14 HP services and technical support...........................................................105HP contact information.........................................................................................................................105

Glossary..................................................................................................107

Index.......................................................................................................111

6 Table of Contents

Page 7: Virtual Connect

List of Figures1-1 HP Virtual Connect technology..........................................................................................................151-2 Virtual Connect Enterprise Manager operations...................................................................................162-1 VCEM home page..........................................................................................................................253-1 VC Domains page..........................................................................................................................273-2 Select any value other than 8Gb as uplink and downlink configuration speeds.......................................323-3 Multienclosure VC Domain...............................................................................................................333-4 Virtual Connect 8Gb 24-Port FC Module............................................................................................333-5 Fibre Channel port speed set to 8Gb.................................................................................................343-6 Valid configuration of Ethernet and Fibre Channel Virtual Connect modules............................................393-7 VC Domain Group with VC Domains that have different numbers of enclosures.......................................404-1 VC Domain Groups.........................................................................................................................475-1 Profiles page..................................................................................................................................535-2 Server VLAN tag to vNet Mappings window......................................................................................565-3 Copying a profile using the Copy from button.....................................................................................575-4 Force same VLAN mappings as Shared Uplink Sets checkbox...............................................................575-5 Custom Port Speed window..............................................................................................................576-1 Bays page.....................................................................................................................................636-2 Window displaying the power status of a bay....................................................................................646-3 Bay status with tab and hold.............................................................................................................657-1 MAC Ranges List page....................................................................................................................697-2 WWN Ranges List page..................................................................................................................727-3 WWN Ranges List page..................................................................................................................748-1 Logical serial number page..............................................................................................................779-1 Jobs list..........................................................................................................................................7913-1 Backing up and restoring VCEM.....................................................................................................96

7

Page 8: Virtual Connect

8

Page 9: Virtual Connect

List of Tables2-1 Hardware requirements....................................................................................................................192-2 Operating system naming convention................................................................................................202-3 Component Abbreviations................................................................................................................202-4 HP Insight software ICE CMS requirements.........................................................................................202-5 Supported Windows CMS operating systems in Insight software ICE components ...................................212-6 Supported Virtual Servers for Insight software ICE components .............................................................212-7 HP Insight software ICE supported CMS databases..............................................................................22

9

Page 10: Virtual Connect

10

Page 11: Virtual Connect

About this documentIntended audience

This document is intended to be used by technical professionals who manage multiple HP BladeSystemenclosures and use HP Virtual Connect Manager to control network connectivity. HP assumes that you haveinstalled Virtual Connect Manager and have read the HP Virtual Connect for c-Class BladeSystem User Guideand understand its concepts.

Publishing historyPublication dateSoftware versionManufacturing part number

September 20091.40460924-005

April 20091.30460924-004

January 20091.20460924-003

April 20081.10460924-002

November 20071.00460924-001

Related documentsIn addition to this guide, the following resources are available:

• VCEM website at http://www.hp.com/go/vcem

• HP Insight Software Quick Setup Poster

• HP Insight Software Support Matrix

• HP Virtual Connect Enterprise Manager Release NotesFor more information about Virtual Connect Manager, see:

• BladeSystem c-Class Solution Overview

• HP Virtual Connect for c-Class BladeSystem User Guide

• HP Virtual Connect Manager Release Notes

HP encourages your commentsYour comments and suggestions regarding product features will help us develop future editions of VCEM.For contact information, see chapter 14.

Intended audience 11

Page 12: Virtual Connect

12

Page 13: Virtual Connect

1 IntroductionHP Virtual Connect Enterprise Manager (VCEM) simplifies the management of multiple HP BladeSystemenclosures that use HP Virtual Connect to control LAN and Storage Area Network (SAN) connectivity (VirtualConnect [VC] Domains), helping organizations to increase productivity, respond faster to changing workloaddemands, and reduce operating costs.Built on the Virtual Connect and Onboard Administrator architecture integrated into every HP BladeSystemc-Class enclosure, VCEM provides a central console to perform efficient administration of LAN and SANaddresses, group-based configuration management, plus the rapid assignment, movement and failover ofserver-to-network connections and their workloads for up to 200 VC Domains (up to 800 BladeSystemenclosures).Use VCEM in HP BladeSystem environments to complete key data center tasks quickly, reliably, and withoutdisrupting production LANs and SANs. VCEM enables you to:

• Deploy new BladeSystem enclosures, server blades, and Virtual Connect (VC) Domains

• Perform fast and cost-effective server recovery

• Complete planned systems maintenance with minimal downtime

• Rapidly migrate and repurpose server blades to meet workload and application priorities

Together, Virtual Connect and VCEM create a change-ready infrastructure that enables system administratorsto add, replace, and recover blade servers across the data center in minutes without impacting LAN andSAN availability. Virtual Connect and VCEM help organizations work smarter, respond faster to change,and reduce typical server deployment and maintenance costs.For more information on VCEM, see http://www.hp.com/go/vcem.

Key features and benefitsVCEM delivers the following key features and benefits.

Key features• Single intuitive console to control up to 200 VC Domains (800 BladeSystem enclosures and 12,800

servers when used with Virtual Connect Ethernet multienclosure domains)

• Central repository supports 128,000 address ranges for MAC and World Wide Name (WWN)assignments, for a total of 256,000 supported network addresses per VCEM console.

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

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

• Scripted and manual movement of server connection profiles and associated workloads betweenBladeSystem enclosures

• Automated failover of server connection profiles and workloads to designated spare servers

• Embedded maintenance tools that enable VC Domain settings and network connection changes to bemade once, and then pushed automatically to multiple BladeSystem enclosures.

• Seamless integration with Virtual Connect infrastructures—discovers and aggregates existing VirtualConnect resources into a central console

• Licensed for each c-Class enclosure—simplifies deployment and enables support for current and futureBladeSystem and Virtual Connect hardware

Key benefits• Centrally manage individual and groups of VC Domains.

• Enable more efficient LAN and SAN address management and eliminate the risk of address conflicts.

• Increase infrastructure consistency and enables rapid change management across multiple enclosures.

Key features and benefits 13

Page 14: Virtual Connect

• Add, change, and replace servers across the data center in minutes when your business needs to withoutimpacting production LAN and SAN availability.

• 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.

• Scale across small and large data centers.

What's newVCEM 1.40 introduces support for new hardware and functionality delivered with VC firmware 2.30, whichincludes:

• Support for the HP Virtual Connect 8Gb 20-Port Fibre Channel module for BladeSystem c-Class.

• Updated SNMP events for Virtual Connect.

• Introduces new VCEM 128,000 address ranges for MAC and World Wide Name (WWN) assignments,for a total of 256,000 supported network addresses per VCEM console.

• Removes support for Virtual Connect firmware 1.2x and 1.3x. The minumum supported Virtual Connectfirmware version is 2.00.

NOTE: VCEM 1.40 update requires an existing VCEM 1.20 or 1.30 installation and is available only asa web download at http://www.hp.com/go/vcem.

Platform supportVCEM is supported on most HP BladeSystem c-Class hardware, storage, software, and third-party operatingplatforms. For a full list of supported platforms and components, see the HP Insight Software Support Matrix.

Architectural overviewThis section provides an overview of the architecture, functionality, and operations of Virtual Connecttechnology and VCEM.

HP Virtual Connect technologyHP Virtual Connect is an interconnect option for HP BladeSystem c-Class enclosure that simplifies serverconnectivity by reducing physical cabling and virtualizing network assignments. It puts an abstraction layerbetween the servers and their external networks so that LANs and SANs see a pool of servers instead ofindividual servers, providing real benefits over traditional managed switch and pass-thru network solutions.The Virtual Connect architecture is built into every HP BladeSystem c-Class enclosure and extended throughstandards-based Ethernet and Fibre Channel modules that plug into the enclosure interconnect bays. VirtualConnect uses pools of unique media access control (MAC) addresses, World Wide Names (WWNs), andserver profiles to establish reliable server-to-network connections. The server connection profiles containMAC, WWN, and boot-from-SAN definitions that are assigned to the enclosure bays and not the physicalservers. The physical servers use network assignments and the server profiles instead of any default NIC orHBA addresses. Even if a server is replaced, the MAC and WWN assignments for the enclosure will remainconstant, and changes are invisible to the network. Virtual Connect provides the following benefits:

• Significantly reduce cabling and server connection complexity.

• Maintain constant end-to-end connections to preferred networks and fabrics.

• Separate server administration from LAN and SAN administration.

• Enable system administrators to be more self-sufficient, so they can add, replace, or modify servers inminutes without impacting production LANs and SANs.

• Relieve LAN and SAN administrators from server-centric maintenance.

14 Introduction

Page 15: Virtual Connect

Figure 1-1 HP Virtual Connect technology

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

Managing HP Virtual ConnectA Virtual Connect server profile is a logical grouping of server connection attributes that can be assignedto 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 preconfigure, modify, anddynamically assign Virtual Connect server profiles to BladeSystem enclosures and bays.

HP Virtual Connect ManagerVirtual Connect Manager is a web-based console integrated into Virtual Connect Ethernet module firmware,providing local management for individual VC Domains.Typical environmentSmall environments with HP BladeSystem c-Class and Virtual Connect contained in a local data center.

HP Virtual Connect Enterprise ManagerHP Virtual Connect Enterprise Manager (VCEM) is a software application that provides a centralized consolefor managing multiple BladeSystem enclosures configured with Virtual Connect. VCEM also provides acentral database for simplified LAN and SAN address information, group-based management capabilities,and the rapid deployment, movement, and failover of server connection profiles between BladeSystemenclosures.Typical Environment

• Medium to large HP BladeSystem environments that use Virtual Connect.

• BladeSystem environments that extend to multiple locations.

• Organizations that require centralized control of server-to-network connectivity.

• Organizations that require rapid server movement between enclosures.

Architectural overview 15

Page 16: Virtual Connect

For more information about Virtual Connect and Virtual Connect Manager, see the HP Virtual Connect forc-Class BladeSystem User Guide.

VCEM operationsVCEM extends Virtual Connect technology with a single console that aggregates the management andcontrol of multiple BladeSystem infrastructures. This intuitive solution delivers advanced Virtual Connectmanagement that leverages and integrates with other HP management tools, including HP SIM, VirtualConnect 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.3.1 or later, and as a virtual machine.VCEM presents 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 centrallyadministered VCEM address database.

• Create VC Domain Groups.

• Assign and unassign VC Domains to VC Domain Groups.

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

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

• Change, reassign, and automatically failover server profiles to alternative or spare enclosures andenclosure bays. Use this capability to quickly perform server recovery, planned maintenance, and serverrepurposing across the data center.

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

Figure 1-2 Virtual Connect Enterprise Manager operations

VCEM centralizes Virtual Connect infrastructure management and increases productivity.

16 Introduction

Page 17: Virtual Connect

Setup and configuration summaryTo set up and 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. For a complete list of hardware, firmware, and software requirements, see“Prerequisites for installation”.

2. Install the VCEM software on a designated host system running a supported operating system using theHP Insight Software DVD.Insight Software media can be downloaded from http://www.hp.com/go/insightcontrol.

3. Open the VCEM console, and then 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 allsubsequent group members.

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

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

Setup and configuration summary 17

Page 18: Virtual Connect

18

Page 19: Virtual Connect

2 Installing and configuring VCEMThis chapter describes how to install and configure VCEM.

IMPORTANT: HP assumes that you have installed Virtual Connect Manager, have read the HP VirtualConnect for c-Class BladeSystem User Guide, and understand its concepts.

Preparing for a VCEM installationIf you have VCEM 1.10 or earlier, you must first upgrade to VCEM 1.20 using the HP Insight Software 3.10DVDs before you upgrade to VCEM 1.30 or 1.40.VCEM 1.30 and 1.40 are web-only deliverables which can be used to update VCEM 1.20 and higher withno loss of information.

IMPORTANT: HP recommends that you install and upgrade VCEM using the HP Insight Software DVDs. Ifyou manually upgrade HP SIM 5.2 to 5.3 or 5.3.1, you must also upgrade VCEM 1.10 or 1.10 SP1 to1.20. Otherwise, HP SIM might use VCEM license seats without your consent.

VCEM checklistYou must have the following information before performing a VCEM installation.

Prerequisites for installationThis section describes the server prerequisites for installing VCEM, including the hardware and softwareprerequisites.

Hardware requirementsThe following table lists the Insight software ICE CMS hardware installation requirements.Table 2-1 Hardware requirements

SpecificationComponent

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

Server

At least 2 GB RAM (3 GB RAM recommended). If you are installing HP Insight Dynamics – VSE, 4 - 6 GB isrecommended.1

Memory

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

At least 15 GB for HP Insight software. More space is needed for storing deployment operating systems (for HP InsightRapid Deployment software) and patches (for Vulnerability and Patch Management Pack). 3

Disk space

New Technology File System (NTFS)Filestructure

Local or mapped DVD drive requiredDVD drive

1 Construction of a system meeting the minimum memory requirements for Virtual Server Environment (VSE) operation is problematicon 32-bit versions of the Windows Server family due to the maximum addressable memory space of a 32-bit operating system of4 GB. This memory space is also shared by some hardware elements, such as video memory, reducing the maximum availablememory below the minimum recommended by HP. To overcome this limitation, the /PAE switch can be added to the boot.ini fileto enable the Physical Address Extension feature. This allows access to memory above 4 GB on 32-bit operating system editionsrunning on hardware that supports PAE.

2 For HP Insight Dynamics – VSE, two or more processing cores are required.3 For information about HP Insight Dynamics requirements, see the HP Insight Dynamics - VSE and HP VSE Management Software

Version 4.1 Support Matrix or HP Insight Dynamics - VSE & VSE Management Software Version 4.1 Getting Started Guide.

Software requirementsThe following naming conventions are used in Table 2-4 “ HP Insight software ICE CMS requirements”.

Preparing for a VCEM installation 19

Page 20: Virtual Connect

Table 2-2 Operating system naming convention

Operating SystemTerm

Microsoft Windows Server® 2008, Standard and Enterprise Edition 32-bitWindows Server 2008 (32-bit)

Microsoft Windows Server 2008, Standard and Enterprise Edition 64-bit (32-bit mode) 1Windows Server 2008 (64-bit)

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

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

1 ID – VSE, VCEM, IO, and HP IR do not support CMS installation to 64-bit Windows Server 2008. For more information, see thecomponent's support matrix.

The following abbreviations are used in the tables.Table 2-3 Component Abbreviations

ComponentAbbreviation

HP Integrated InstallerHP II

HP Insight RecoveryHP IR

HP Systems Insight ManagerHP SIM

HP Insight Power ManagerIPM

HP Insight Orchestration softwareIO

HP Performance Management PackPMP

HP Insight Rapid Deployment softwareRDP

HP Insight Server Migration software for ProLiant1SMP

HP Virtual Machine Management PackVMM

HP Vulnerability and Patch ManagementVPM

Virtual Server Environment2VSE

1 See the HP Insight Server Migration software for ProLiant Support Matrix information about differences between migrations.2 See the HP Insight Dynamics - VSE and HP VSE Management Software Version 4.1 Support Matrix.

Table 2-4 HP Insight software ICE CMS requirements

Windows Server 2003 R2Windows Server 2003Windows Server 2008

Specification 64-bit32-bit64-bit32-bit64-bit32-bit

✓✓✓✓.NET 1.1 Framework1

✓✓✓✓.NET 2.0 Framework2

✓✓✓✓.NET 3.0 Framework3

✓✓✓✓Acrobat® Reader

✓✓✓✓Adobe Flash Player 9.03

✓✓Microsoft iSCSI Software Initiator 2.06, 2.07 or2.084

✓✓iSCSI 6.0.6001.180005

✓✓✓✓SNMP

✓✓✓✓TCP/IP with DNS installed so that system names mustresolve to an IP addresses. It is necessary that IPaddresses must resolve to system names.

✓✓✓✓Windows Automated Installation Kit (WAIK) 2.16

1 This requirement applies to HP Insight Rapid Deployment software.2 If .NET 2.0 is not installed, it is installed during the Integrated Installation.3 This requirement applies to HP Insight Orchestration software.4 This requirement applies to HP Insight Server Migration software for ProLiant.

20 Installing and configuring VCEM

Page 21: Virtual Connect

5 This requirement applies to HP Insight Server Migration software for ProLiant and is already installed by default.6 This requirement applies to HP Insight Rapid Deployment software. If you are installing or upgrading HP Insight Rapid Deployment

software, you must first install Microsoft WAIK 2.1, also known as the Automated Installation Kit (AIK) for Windows Vista SP1 andWindows Server 2008 It is available at the Microsoft website), or search for 936330AIK on http://www.microsoft.com (thefilename is 6001.18000.080118-1840-kb3aikl_en.iso).

NOTE: HP Performance Management Pack (PMP) 5.2 requires Java Runtime Environment (JRE) 5.0 tocomplete the installation successfully if JRE 1.4.2 or earlier is installed on the system.If JRE is not installed on the system, the PMP 5.2 installation continues without an issue.

Table 2-5 Supported Windows CMS operating systems in Insight software ICE components

VCEMHP IRIOID-VSESMPVMMIPMVPMPMPRDPHP SIMHP IIOperating system

✓✓✓✓✓✓✓✓✓✓✓✓Windows Server 2008,Standard and Enterprise Edition32-bit

✓✓✓✓✓✓✓✓Windows Server 2008,Standard and Enterprise Edition64-bit (32-bit mode)

✓✓✓✓✓✓✓✓✓✓✓✓Windows Server 2003,Standard and Enterprise EditionSP2 32-bit

✓✓✓✓✓✓✓✓✓✓✓✓Windows Server 2003 R2,Standard and Enterprise EditionSP2 32-bit

Table 2-6 Supported Virtual Servers for Insight software ICE components

VCEMHP IRIOID-VSESMPVMMIPMVPMPMPRDPHP SIMHP IIOperating system

✓✓✓✓✓✓✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.0.1

✓✓✓✓✓✓✓✓✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.0.2

✓✓✓✓✓✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.0.3

✓✓✓✓✓✓✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.5Update 1

✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.5Update 2

✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.5Update 3

✓✓✓✓✓✓✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESX 3.5Update 4

✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESXi 3.5Update 1

✓✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESXi 3.5Update 2

Prerequisites for installation 21

Page 22: Virtual Connect

VCEMHP IRIOID-VSESMPVMMIPMVPMPMPRDPHP SIMHP IIOperating system

✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESXi 3.5Update 3

✓✓✓Supported 32-bit Windowsoperating system running as aguest on VMware ESXi 3.5Update 4

✓✓✓Integrity VM HP-UX running asguest on an HP-UX 11i v2operating system

✓✓✓Integrity VM HP-UX running asguest on an HP-UX 11i v3operating system

✓✓✓✓Microsoft Hyper-V1

1 The CMS is supported running on this operating system which is a guest on the hypervisor.

The following table lists the minimum support for installation of HP Insight software ICE. Installations withMicrosoft Data Engine (MSDE) 2000 Service Pack 3a are migrated to Microsoft SQL 2005 Express EditionService Pack 2.Table 2-7 HP Insight software ICE supported CMS databases

Remotedatabase

Localdatabase

Database

✓✓Microsoft SQL Server 20081

✓✓Microsoft SQL Server 2005 SP21

✓Microsoft SQL Server 2005 Express Edition SP22

1 SQL Server 2005 and 2008 supports up to 5,000 systems and 50,000 events.2 SQL Server 2005 Express Edition supports up to 500 systems and 5,000 events.

NOTE: When VPM is installed on a CMS with a remote connection to the HP SIM database, VPM installsa local copy of Microsoft SQL Express and creates a database instance to store and manage vulnerabilitydefinitions and scan results.

Supported configurationsThe following configurations are supported both in a Windows domain and a workgroup:

• If one server is in a Windows domain, ensure that all servers are in that Windows domain. Servers indifferent Windows domains are not supported.

• If one server is in a Windows domain, ensure that the domain server is a separate server from theservers shown in the following figure. Installation of HP Insight software is not supported on domainservers.

• If one server is in a workgroup, ensure that each server has a local account with the same name andpassword (both for services and database credentials).

The following figure shows the supported configurations for the CMS with HP Insight software installed.

22 Installing and configuring VCEM

Page 23: Virtual Connect

NOTE: HP does not recommend the installation of both Insight Rapid Deployment and an HP Ignite-UXserver on the same subnet.

For a complete list and diagram of supported configurations, see the HP Insight Software Installation andConfiguration Guide.

Installing VCEMTo install VCEM, follow the steps provided in the installation wizard. To access online help, click the ? iconin the upper right-hand corner of the window.

Performing post-installation configuration tasksPost-installation configuration tasks

If you are installing VCEM for the first time, perform the following tasks:1. To access VCEM, select either of the following:

• Start→All Programs→HP Virtual Connect Enterprise Manager→HP Virtual ConnectEnterprise Manager

• HP SIM→Tools→Integrated Consoles→Virtual Connect Enterprise Manager (VCEM)

If VCEM is a stand-alone installation, click the VCEM desktop icon. The VCEM Home page appears.

2. Enter the credentials that you entered when performing the installation. The VCEM home page appears.

• If an HP SIM discovery has been performed, all Virtual Connect modules appear.

• If an HP SIM discovery has not been previously performed, and no Virtual Connect modules appear,perform an HP SIM discovery before continuing.1. Make sure to discover the Onboard Administrator IP addresses with enclosures that have VC

Ethernet modules.2. To verify whether any VC Domains have been discovered, click the VC Domains tab.

For more information about performing an HP SIM discovery, see the HP SIM User Guide.

Installing VCEM 23

Page 24: Virtual Connect

3. (Optional) Configure the MAC addresses to match the needs in the data center.a. From the VCEM Home page, click the Home tab. In a stand-alone VCEM installation, to return to

the Home page, click the Home link on the upper right-hand corner of the screen.b. Click the MAC Addresses hyperlink.c. To create a custom range, click Add custom.

The MAC address range used by the VCEM domain must be unique within the environment. HPprovides a set of predefined ranges that are reserved for use by Virtual Connect and VCEM, anddoes not conflict with server factory-default MAC addresses.When using the HP-predefined MAC address ranges, be sure that each range is used only oncewithin the environment.

For more information, see Adding custom MAC address ranges.

4. (Optional) Create MAC exclusion ranges. For more information, see Creating MAC exclusion ranges.5. (Optional) Configure the World Wide Names ranges to meet your requirements.

a. From the VCEM Home page, click the Home tab. In a stand-alone VCEM installation, to return tothe Home page, click the Home link on the upper right-hand corner of the screen.

b. Click the World Wide Names hyperlink.c. To create a custom range, click Add custom.

The WWN range used by the VCEM domain must be unique within the environment. HP providesa set of predefined ranges that are reserved for use by Virtual Connect and VCEM, and does notconflict with server factory-default WWNs.When using the HP-predefined WWN ranges, be sure that each range is used only once withinthe environment.For more information, see Adding custom WWN address ranges.

6. (Optional) Create WWN exclusion ranges. For more information, see Creating WWN exclusion ranges.

7. Click the VC Domains tab. VC Domains appear as the following:

• Unconfigured VC Domains—Appear as VCD_name, where name is the temporary nameautomatically given to the VC Domain.

• Configured VC Domains—Appear with the VC Domain name.

8. Select a VC Domain, and then click License to license the domain. For more information on licensing,see Licensing an enclosure for VCEM.

9. Create a new VC Domain Group, and then add one or more already licensed VC Domains to it. Formore information on creating a new VC Domain Group, see Creating a VC Domain Group.

You can continue using VCEM and its additional functions such as creating profiles and assigning them tobays.VCEM uses a Secure Sockets Layer (SSL) connection provided by HP SIM. For more information about theavailable cipher suites and how to enable or disable them, see the Understanding HP SIM security whitepaper at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.VCEM uses the same TCP ports as HP SIM. VCEM does not open any other TCP ports.

VCEM home pageThe following screenshot shows the VCEM home page.

24 Installing and configuring VCEM

Page 25: Virtual Connect

Figure 2-1 VCEM home page

VCEM home page 25

Page 26: Virtual Connect

26

Page 27: Virtual Connect

3 Managing VC DomainsVC Domains

This section describes how to use VCEM to manage VC Domains.On the VC Domains page, you can filter the VC Domain list by VC Domain Group. The default filter showsall VC Domains.

Figure 3-1 VC Domains page

The following table lists and describes the columns on the VC Domains page.

DescriptionItem

Describes VC Domain statusStatus

Identifies the VC Domain nameVC Domain Name

Identifies the domain IP address for the primary VC Ethernetmodule

VC Manager

Identifies the enclosure nameEnclosure

Identifies the VC Domain Group name, if anyVC Domain Group

The following table lists and describes VC Domain status icons and descriptions.

DescriptionIconStatus

The VC Domain enclosure has not beenlicensed.

(no icon)Not licensed

The VC Domain enclosure has been licensedto VCEM.

Licensed

VC Domains 27

Page 28: Virtual Connect

DescriptionIconStatus

Failed to connect to the VC Domain. Possiblecauses include:• Connection times out.

• Ethernet VC Module is physically notavailable.

• Virtual Connect Manager is failing.

• VC Domain firmware is updating.

• HP Virtual Connect Ethernet IP addresshas changed (through DHCP or EBIPAconfiguration).

VCEM checks the VC Domain connectivitybefore executing any operation that involvesVirtual Connect Manager. VCEM omits theVC Domains with connection failurestatus message when executing anoperation.

Connectivity failure

VCEM is unable to obtain the necessarypermissions for External Manager user.VCEM might have lost the External Managerlock at the VC Domain.

Missing external manager lock

The VC Domain enclosure has an expiredlicense.

Expired license

The VC Domain is part of a VC DomainGroup and operating normally.

Managed by VCEM

The VC Domain configuration has changedand does not match the VC Domain Groupconfiguration.

Configuration mismatch

VC Domain is unlocked for domain, network,and storage changes through VirtualConnect Manager. After completing thedomain, network, and storage changes,confirm the new VC Domain configurationin VCEM. VCEM operations related to thisVC Domain or its VC Domain Group, suchas create profile, move profile, profilefailover, and so on, are blocked while theVC Domain is under maintenance.

Under maintenance

NOTE: For information on how to resolve status issues, see "Troubleshooting."

To display the properties of a particular VC Domain, click the VC Domain name. Properties include theprimary IP address, status, Virtual Connect firmware version, Ethernet networks, Shared Uplink sets, FibreChannel SAN fabrics, Ethernet and Fibre Channel common settings, and SMP Ethernet and Fibre Channelalert destinations.

Requirements for adding a VC Domain to a VC Domain GroupTo add a configured VC Domain to a VC Domain Group, the following requirements must be met:

• The VC Domain must have the minimum number of enclosures required by the VC Domain Group. Formore information, see Working with multienclosure VC Domains.

• VC Domain names must not already exist in VCEM.

• Profile names must not already exist in VCEM.

28 Managing VC Domains

Page 29: Virtual Connect

• MAC or WWN addresses or serial numbers that are assigned to a profile must not be in use by VCEMor in a VCEM exclusion list. If the MAC or WWN addresses or serial numbers are user-defined, thenyou must define an address range in VCEM.

• If the VC Domain contains server profiles, the MAC addresses, WWNs, and serial numbers allocatedmust be compatible with the MAC, WWN, and serial number range types of the VC Domain Group:

• A VC Domain containing server profiles with factory-default addresses can be added to a VCDomain Group with VCEM-defined range types, and user-defined range types. To add a VCDomain to a VC Domain Group with factory-default range types, all profiles of the VC Domainmust be configured with factory-default addresses.

• A VC Domain containing server profiles with addresses allocated as user-defined range type canbe added to a VC Domain Group with a user-defined or HP-predefined range type. A user-defined(custom) MAC and WWN range that includes all addresses allocated to server profiles within theVC Domain must be defined in VCEM before adding the domain to the VC Domain Group.

• A VC Domain containing server profiles with addresses allocated as HP-predefined range typecan be added to a VC Domain Group with an HP-predefined or a user-defined range type.

• An unconfigured VC Domain without server profiles has no range type restrictions when addingin a VC Domain to a VC Domain Group.

The following table summarizes MAC address, WWN address, and serial number range type compatibilitywhen adding a VC Domain to a VC Domain Group.

VCEM-supportedMAC or WWN or serial number in VCDomain Group

VC Domain has profiles with MAC orWWNaddresses or serial number allocated as

YesVCEM-defined or user-definedVCEM-defined

YesVCEM-defined or user-definedUser-defined

YesFactoryFactory (MAC address or WWN address)

YesVCEM-defined or user-definedFactory

YesVCEM-defined or user-definedVCEM-defined, HP-predefined, oruser-defined

VC Domain configuration must be identical to the VC Domain Group configuration. Verify that the followingitems are identical:

• Interconnect bays location and model

• Enclosure model

• Domain settings:

Configuration for double density servers (for example, BL2x220c)•

• Configuration for full-height and half-height single density servers (for example, BL460c, BL480c)

• Ethernet settings:

MAC Cache Failover:•

• Enable Fast MAC Cache Failover

• MAC Refresh Interval

• IGMP Snooping:

Enable IGMP Snooping•

• IGMP Idle Timeout Interval

• Server VLAN Tagging support:

Tunnel VLAN Taggings or Map VLAN Taggings•

• Force Server connection setting

VC Domains 29

Page 30: Virtual Connect

• Multiple Network Speeding Settings:

Preferred Link Connections•

• Preferred Link Connection Speed

• Maximum Link Connection

• Maximum Link Connection Speed

• Network SNMP settings:

• Read Community

• System Contact

• IP addresses

• Fibre Channel SAN Fabric settings:

Enables SMI-S•

• Fibre Channel SNMP settings: Read Community, System Contact, and IP addresses

• Network and Fibre Channel SAN Fabrics uplinks

• For each single network uplink:

Network name•

• Smart link

• Private Network

• Enable VLAN Tunneling

• State

• Network port location

• Speed/duplex mode

• Connection mode

• Preferred Link Connection

• Preferred Link Connection Speed

• Maximum Link Connection

• Maximum Link Connection Speed

• Number of networks configured in the VC Domain

• For each shared network uplink:

Uplink set name•

• Network port location

• Speed/duplex mode

• Connection mode

• Number of VLANs tagged associated to the shared network uplinks

• Number of shared networks configured in the VC Domain

• For each VLAN-tagged associated to the shared network uplink:

Network name•

• Network state

• VLAN ID

• Native

• Smart Link

• Private network

30 Managing VC Domains

Page 31: Virtual Connect

• Preferred Link Connection

• Preferred Link Connection Speed

• Maximum Link Connection

• Maximum Link Connection Speed

• For each Fibre Channel SAN Fabric:

Fabric name•

• If VC Domain has firmware 2.0x and later:

• Configuration speed

• Login distribution

• Fabric port location

• Number of Fibre Channel SAN Fabrics configured in the VC Domain

To add an unconfigured VC Module to a VC Domain Group, the following items must be identical:

• Interconnect bays location and model

• Enclosure model

• Uplinks of the network and Fibre Channel SAN Fabric

• Power state of the VC Modules

Mixed Virtual Connect firmware versions and firmware compatibility in a VC Domain GroupVCEM enables firmware compatibility using current and future versions of Virtual Connect firmware. Thisfeature provides these benefits:

• A single VC Domain Group can contain VC Domains running different firmware versions. The followingtable shows the supported combinations of Virtual Connect firmware within a single VC Domain Group.

VC firmware 2.0xVC firmware 2.1xVC firmware 2.3xVC Domain Group

YesYesYesVC Domain firmware 2.3x

YesYesNoVC Domain firmware 2.1x

YesNoNoVC Domain firmware 2.0x

* Virtual Connect 2.3x features must be disabled for it to be in the same group as Virtual Connect 2.1xor 2.0x.* Virtual Connect 2.1x features must be disabled for it to be in the same group as Virtual Connect2.0x.

NOTE: If you have a VC Domain Group 2.0x or 2.1x and all the VC Domains have been upgradedto Virtual Connect 2.1x or 2.3x, the group will not function as a VC Domain Group 2.0x or 2.1x.To enable Virtual Connect 2.1x or 2.3x functionality, migrate the VC Domains from the existing 2.0xor 2.1x to a new VC Domain Group 2.1x or 2.3x. For more information, see Upgrading VC DomainGroup Firmware Mode.

• VCEM 1.40 might be able to support future versions of Virtual Connect firmware in a compatibilitymode.

This compatibility mode enables a new Virtual Connect firmware version to be used immediately with aVCEM 1.40 installation. For example, if Virtual Connect released a 2.2x version of its firmware, a domainwithin a 2.1x VC Domain Group could be upgraded to the 2.2x version of the firmware while preservingthe 2.1x level of functionality. The VC Domain Group will operate at the firmware version with which it wascreated. A subsequent VCEM release would support the new functionality.

VC Domains 31

Page 32: Virtual Connect

Virtual Connect 2.3x features that must be disabled in a VC Domain to be part of the VC DomainGroup with Virtual Connect firmware 2.1x

IMPORTANT: If you plan to add Virtual Connect 2.3x to a VC Domain Group with Virtual Connect firmware2.0, you must disable the Virtual Connect 2.3x features in this section and the Virtual Connect 2.1x featuresin the following section.

• Enhanced SNMP configuration is not supported

You cannot have more than five VC Ethernet or VC Fibre Channel SNMP traps.•

• You cannot modify the SNMP configuration for VC Domain level. The default VC Domain level isenabled with community string equals to public. This is only available through the Virtual ConnectManager command line interface.

• To disable this feature, set the following SNMP trap settings as follows:1. Verify that the destination name is in the following format:

<IP Address of the SNMP Trap Destination*gt _<Community String>_<0if a VC-Ethernet Module and 1 if a VC-Fibre Channel Module>>

(that is, 192.168.1.1_public_1)

2. Select ipv4.3. Verify that the SNMP format is “SNMPv1."4. Disable SNMP trap severities by verifying that the right side must be empty.5. Verify that the trap categories equal either:

• other VC-Enet Traps

• other VC-FC Traps

6. Disable the Virtual Connect Manager trap by verifying that the right side is empty.

• Fibre Channel Port Speed cannot be set to 8Gb for a HP Virtual Connect 8-Gb 20-Port Fibre ChannelModule.Select any value other than 8Gb as the uplink configuration speed when defining a SAN Fabric for aHP Virtual Connect 8-Gb 20-Port Fibre Channel Module.

Figure 3-2 Select any value other than 8Gb as uplink and downlink configuration speeds

Select any value other than 8Gb as the downlink configuration speed when assigning a SAN Fabricfor a HP Virtual Connect 8-Gb 20-Port Fibre Channel Module.

32 Managing VC Domains

Page 33: Virtual Connect

Virtual Connect 2.1x features that must be disabled in a VC Domain to be part of the VC DomainGroup with Virtual Connect firmware 2.0x

• Multienclosure VC Domain is not supported.Do not configure remote enclosures in the VC Domain or remove the VC Domains that are configured.

Figure 3-3 Multienclosure VC Domain

• The HP Virtual Connect 8Gb 24-Port FC Module is not supported.Do not insert the HP Virtual Connect 8Gb 24-Port FC Module in the VC Domain.

Figure 3-4 Virtual Connect 8Gb 24-Port FC Module

• Fibre Channel Port Speed cannot be set to 8Gb for HP Virtual Connect 8Gb 24-Port FC Module.Select any value other than 8Gb as the configuration speed for HP Virtual Connect 8Gb 24-Port FCModule.

VC Domains 33

Page 34: Virtual Connect

Figure 3-5 Fibre Channel port speed set to 8Gb

VC Domain tasksFrom the VC Domains page, you can perform the following tasks:

• License an enclosure for VCEM

• Create a VC Domain Group

• Add a VC Domain to a VC Domain Group

• Remove a VC Domain from a VC Domain Group

• VC Domain Maintenance

• Cancel VC Domain Maintenance

• Resynchronize a VC Domain with Configuration Mismatch Status

Licensing an enclosure for VCEMYou must purchase a license for each enclosure to be managed. For licensing information, see the VCEMQuickSpecs at http://www.hp.com/go/vcem.To enable a VC Domain license:1. From VC Domain page, select the VC Domain, and then click License. The License Enclosure page

appears.2. Click Add Key.3. Enter the license key string, and then click OK. If the license key is valid, then it is added to HP SIM.4. The License Enclosure page reappears displaying the number of available licenses.5. Select the VC Domain to which you want to apply the VCEM license.6. Click Apply License.7. The VC Domain list page reappears, displaying the updated status of VC Domains.8. The VC Domain appears with Informational status.

34 Managing VC Domains

Page 35: Virtual Connect

Creating a VC Domain GroupYou can create a VC Domain Group by selecting the VC Domains that you want to incorporate into a newVC Domain Group.

IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from HP SIM. To accessthis reference, you must correlate the HP SIM and Virtual Connect logs. For more information, see CorrelatingVCEM operations in HP SIM and Virtual Connect logs.

VCEM supports multienclosure VC Domains. A multienclosure VC Domain is a VC Domain with one localenclosure and up to three remote enclosures.To manage multienclosure VC Domains in VCEM, you must perform the following steps before you createa VC Domain Group:1. Log in to Virtual Connect Manager.2. Find and import a local enclosure, and then select the appropriate Double-dense option.3. Skip the Network and Fibre Channel configuration wizards, and then navigate directly to the VC Domain

user interface.4. Find and import the necessary remote enclosures in the correct order through Virtual Connect Manager.5. Go to HP SIM and perform a manual discovery for the Onboard Administrator IP address of all released

VC Domain enclosures.VCEM cannot manage a VC Domain that has one or more FC modules in an Incompatible state.The FC module can become incompatible in the following situations:

• An HP Virtual Connect 4Gb FC module replaces an HP Virtual Connect 8Gb 24-port FC module.

• An HP Virtual Connect 8Gb 24-port FC module replaces a HP Virtual Connect 4Gb FC module.

• If HP Virtual Connect 8Gb 24-port FC modules and HP Virtual Connect 4Gb FC modules share thesame IO bay slice. (For example, a HP Virtual Connect 4Gb FC module in IO Bay 3 and a HP VirtualConnect 8Gb 24-port FC module in IO Bay 4).

• IIn a multienclosure VC Domain, if there are mixed HP Virtual Connect 4Gb FC modules and HP VirtualConnect 8Gb 24-port FC modules in the same IO bay from different enclosures. (For example, 4GbFC modules in the local enclosure, but 8Gb FC modules in the remote enclosures.)

To create a VC Domain Group from the VC Domains page, select the VC Domains:1. Click New VC Domain Group.

(Optional) If the enclosures related to the selected VC Domains are not licensed to VCEM, then theLicense page appears below the VC Domains list. For more information, see Licensing an enclosure forVCEM. Otherwise, the Create VC Domain Group appears below the VC Domains list.(Optional) You can provide a new name for the unconfigured VC Domains. Valid VC Domain Groupnames are alphanumeric, hyphens (-), underscore (_), and cannot exceed 64 characters.

2. Enter the username and password for each VC Domain. Ensure you provide VC Domain credentialswill full privileges. VC Domains appear as:

• Unconfigured domains, which appear in the System Name column with the unassigned name,VCD_name

• Configured domains, which appear in the System Name column with their previously assignedname

3. Enter the username and password for the Onboard Administrator of each unconfigured VC Domain.Ensure you provide the Onboard Administrator credentials with full privileges if the Virtual ConnectModule is not configured.(Optional) In some cases you might want to overwrite the existing VC Domain configuration for selectedVC Domains. To enable this action, select Existing VC Domain configuration settings for selectedVC Domain(s) without server profiles will be overwritten by selected base VC Domainconfiguration defined for the VC Domain Group. In this case, VCEM validates that the selected VCDomain configurations match the VC Domain Group configuration. VC Domains that are alreadyconfigured and have server profiles are not affected.

VC Domains 35

Page 36: Virtual Connect

4. Enter the VC Domain Group name in the VC Domain Group Name field. Valid VC Domain Groupnames are alphanumeric, hyphens (-), underscore (_), and cannot exceed 64 characters.

5. From the Configuration based on VC Domain list, select the VC Domain configuration upon which thenew VC Domain Group is to be based. The Configuration VC Domain list contains only configured VCDomains.

6. From the Select MAC range type list, select whether the MAC address range type is VCEM-defined,user-defined, or factory-default. You can only select the User-Defined option for MAC range type if aMAC custom range is defined.

7. From the Select WWN range type list, select whether the WWN address range type is VCEM-defined, user-defined, or factory-default. You can only select the User-Defined option for WWN range type ifa WWN custom range is defined.

8. From the Select Serial Number range type list, select whether the Serial Number address range type islogical serial number, or factory-default.

9. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessageappears.

10. Click OK to go to the Jobs page and monitor job progress.

Adding a VC Domain to a VC Domain GroupYou can select the Add to VCD Group button if there is at least one VC Domain Group created, and thecurrent selection contains VC Domains that do not belong to VC Domain Groups, and that have a validlicense.Before adding a VC Domain to a VC Domain Group, verify the VC Domain meets the minimum requirementsas well as the VC Domain Group configuration for the configured VC Domains. For the complete list ofconfiguration checks, see Requirements for adding a VC Domain to a VC Domain Group.To manage multienclosure VC Domains in VCEM, you must perform the following steps before you add aVC Domain to a VC Domain Group:1. Log in to Virtual Connect Manager.2. Find and import a local enclosure, and then select the appropriate Double-dense option.3. Skip the Network and Fibre Channel configuration wizards, and then navigate directly to the VC Domain

user interface.4. Find and import the necessary remote enclosures in the correct order through Virtual Connect Manager.5. Go to HP SIM and perform a manual discovery for the Onboard Administrator IP address of all released

VC Domain enclosures.VCEM cannot manage a VC Domain having one or more FC modules in an Incompatible state.The FC module can become incompatible in the following situations:

• An HP Virtual Connect 4Gb FC module replaces an HP Virtual Connect 8Gb 24-port FC module.

• An HP Virtual Connect 8Gb 24-port FC module replaces a HP Virtual Connect 4Gb FC module.

• If HP Virtual Connect 8Gb 24-port FC modules and HP Virtual Connect 4Gb FC modules share thesame IO bay slice. (For example, a HP Virtual Connect 4Gb FC module in IO Bay 3 and a HP VirtualConnect 8Gb 24-port FC module in IO Bay 4).

• IIn a multienclosure VC Domain, if there are mixed HP Virtual Connect 4Gb FC modules and HP VirtualConnect 8Gb 24-port FC modules in the same IO bay from different enclosures. (For example, 4GbFC modules in the local enclosure, but 8Gb FC modules in the remote enclosures.)

To add a VC Domain to a VC Domain Group:1. From the VC Domains page, select one or more VC Domains you want to add to the VC Domain Group.2. Click Add to VC Domain Group.

(Optional) If the enclosures related to the selected VC Domains are not licensed to VCEM, then theLicense page appears below the VC Domains list. For more information, see Licensing an enclosure forVCEM. Otherwise, the Add VC Domain to VCD Group appears below the VC Domains list.

3. (Optional) You can provide a new name for the unconfigured VC Domains. Valid VC Domain Groupnames are alphanumeric, hyphens (-), underscore (_), and cannot exceed 64 characters.

36 Managing VC Domains

Page 37: Virtual Connect

4. Enter the username and password for each unconfigured VC Domain. Ensure you provide VC Domaincredentials with full privileges. VC Domains appear as:

• Unconfigured domains, which appear in the System Name column with the unassigned name,VCD_name

• Configured domains, which appear in the System Name column with their previously assignedname

5. Enter the username and password for the Onboard Administrator of each unconfigured VC Domain.Ensure you provide the Onboard Administrator credentials with full privileges if the Virtual ConnectModule is not configured.

6. (Optional) In some cases you might want to overwrite the existing VC Domain configuration for selectedVC Domains. To enable this action, select Existing VC Domain configuration settings for selectedVC Domain(s) without server profiles will be overwritten by selected base VC Domainconfiguration defined for the VC Domain Group. In this case, VCEM validates that the selected VCDomain configurations match the VC Domain Group configuration. VC Domains that are alreadyconfigured and have server profiles are not affected.

7. Select the VC Domain Group name to which you want to add the selected VC Domains.8. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.9. Click OK to go to the Jobs page and monitor job progress.

Removing a VC Domain from a VC Domain Group

IMPORTANT: If you remove the last VC Domain from a VC Domain Group, the unassigned server profileswill be located at this VC Domain.

MAC, WWN, and serial number ranges enable Virtual Connect Manager to manage the allocation of newaddresses when you are releasing the VC Domain control back to Virtual Connect Manager, such as whendeleting the VC Domain Group or removing the VC Domain from a VC Domain Group. HP recommendsthat you provide MAC, WWN, and serial number ranges that are:

• Not in use by VCEM.

• Not in use by any other VC Domain in your network

You can click Remove from VCD Group only if the current selection contains VC Domains that belong to VCDomain Groups.After removing a VC Domain from a VC Domain Group, you can edit or change the existing profiles fromthe Virtual Connect Manager user interface.To remove a VC Domain or VC Domains from a VC Domain Group:1. From the VC Domains page, select the VC Domains to be removed.2. Click Remove from VC Domain Group. The Remove VC Domains Group information from VC Domain

Group appears below the table.

VC Domains 37

Page 38: Virtual Connect

3. Perform the following actions for each VC Domain that uses HP-predefined or user-defined ranges thatyou want to remove from the VC Domain Group. Factory-default MAC, WWN, and serial numberranges are released back to Virtual Connect Manager as Factory-default.If factory-default MAC or WWN addresses or Serial Numbers are not being used, address ranges mustbe specified for each removed VC Domain. These address ranges must be unique and distinct to avoidassignment of duplicate addresses. Each selected MAC and WWN address range must also be recordedas an exclusion range to prevent assignment by VCEM. VCEM manages a proprietary Serial Numberrange so you do not need to define an external range for serial number.The selected HP-predefined ranges are identified as user-defined ranges by Virtual Connect Managerafter the VC Domain is removed from VCEM.a. Enter the MAC address range. To use an HP-predefined MAC range, from the MAC Range section,

select the Use HP Pre-Defined range box, and then select a range from the list. You can alsoclear the Use HP Pre-Defined range box and then enter the start and end addresses for the MACrange. Valid MAC address range is NN-NN-NN-NN-NN-NN where N is a hexadecimal digit(0-F) and cannot exceed 14 characters. The VC Domain configuration applies this MAC addressrange after being removed from VCEM control.

b. Enter the WWN address range. To use an HP-predefined WWN range, from the WWN Rangesection, select the Use HP Pre-Defined range box, and then select a range from the list. You canalso unselect the Use HP Pre-Defined range box and then enter the start and end addresses for theWWN range. Valid WWN address range is NN:NN:NN:NN:NN:NN:NN:NN where N is ahexadecimal digit (0-F) and cannot exceed 23 characters. The VC Domain configuration appliesthis WWN address range after being removed from VCEM control.

c. Enter the Serial Number range. To use an HP-predefined Serial Number range, from the SerialNumber Range section, select the Use HP Pre-Defined range box, and then select a range formthe list. You can also unselect the User range box and then enter the start and end values for theSerial Number Range. Valid Serial Number range is VXC01NNNNN for User-defined orVCXNNNNNNN for HP-predefined, where N is a hexadecimal digit (0-F) and cannot exceed 10characters. The VC Domain configuration applies this Serial Number address range after beingremoved from VCEM control.

4. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessageappears.

5. Click OK to go to the Jobs page and monitor job progress.

Working with multienclosure VC DomainsVCEM supports multienclosure VC Domains. A multienclosure VC Domain is a VC Domain with one localenclosure and up to three remote enclosures. VCEM supports VC Domains with up to four BladeSystemc7000 enclosures.Within each enclosure of a multienclosure domain, the Virtual Connect Ethernet Modules must follow thesame configuration rules as VC Domains with single enclosures. However, each enclosure within the VCDomain might have a different configuration of Ethernet modules. Stacking links must enable Ethernet packetsto reach all Ethernet modules within the VC Domain. All enclosures in a multienclosure VC Domain musthave the same Virtual Connect Fibre Channel Module configuration.The following figure illustrates a valid configuration of Ethernet and Fibre Channel Virtual Connect modulesin a VC Domain with multiple enclosures. The black lines linking the Ethernet modules illustrate the stackinglinks.VCEM supports VC Domain Groups containing VC Domains with multiple enclosures, and enables the VCDomains to contain different numbers of enclosures, as long as each VC Domain contains the minimumnumber of enclosures. The Ethernet uplinks define the minimum number of enclosures. The enclosure with adefined Ethernet uplink port defines the minimum number of enclosures.In this example, the minimum number of enclosures is two. The second enclosure is the last enclosure thatcontains Ethernet uplink ports.

38 Managing VC Domains

Page 39: Virtual Connect

Figure 3-6 Valid configuration of Ethernet and Fibre Channel Virtual Connect modules

As in earlier versions of VCEM, all VC Domains within a VC Domain Group must have the same hardwareconfiguration. VCEM enables each enclosure within a VC Domain with multiple enclosures to have a differentVirtual Connect Ethernet module configuration, but it requires the same Virtual Connect Ethernet Moduleconfiguration across the VC Domain Group members. The base enclosure of every VC Domain within oneVC Domain Group must have the same VC Ethernet module configuration. Similarly, every VC Domain thathas more than one enclosure must have the same VC Ethernet module configuration in the second enclosure.The same rules apply to the third and fourth enclosures.The following figure illustrates a VC Domain Group containing VC Domains with different numbers ofenclosures.

VC Domains 39

Page 40: Virtual Connect

Figure 3-7 VC Domain Group with VC Domains that have different numbers of enclosures

A multienclosure domain can only be configured as follows:

• The enclosure must be a c7000 enclosure.

• Primary and secondary Virtual Connect Ethernet modules must be either the HP 1/10Gb-F VirtualConnect Ethernet Module or the HP Virtual Connect Flex-10 10Gb Ethernet Module running VC firmware2.1x or later.

• FC modules in every enclosure must match the model and disposition.

To manage multienclosure domains in VCEM you would proceed in the same way as with single enclosuredomains:1. License all enclosures. For more information, see “Licensing an enclosure for VCEM”.2. Provide credentials as needed.3. Configure the VC Domain Group. For more information, see Creating a VC Domain Group.VCEM supports multienclosure domains with a different number of enclosures in the same VC Domain Group.For example, you can configure a group with two VC Domains if one VC Domain has two enclosures, andthe other VC Domain has four enclosures. You can perform this configuration provided that the baseconfigurations of both VC domains are equal.

IMPORTANT: When configuring the VC Domain, you must add the remote enclosures in the correct order.Virtual Connect Manager tracks the order of the enclosures that are added. If you add the remote enclosuresand one VC Domain follows a different order than the others, VCEM fails to manage that VC Domain.

The VC module disposition between two VC Domains must match for them to be included in the same VCDomain Group.For more information, see the HP Virtual Connect Manager documentation.

VC Domain MaintenanceVC Domain Maintenance is a useful way to perform updates on a particular VC Domain without removingit from a VC Domain Group, and apply the common domain, network and storage configuration changes

40 Managing VC Domains

Page 41: Virtual Connect

automatically to all other VC Domains that belong to the same VC Domain Group. VCEM accomplishes thistask by temporarily enabling domain, network, and storage changes through the local Virtual ConnectManager for the selected domain.Some of the useful domain-level operations enabled during VC Domain Maintenance include:

• Upgrading firmware

• Backing up VC Domain configuration

• Administering local user accounts

• Setting LDAP directory settings

• Changing VC Domain configuration

Domain name•

• Static IP address

• Setting SSH

• Setting SSL Certificate

• Resetting Virtual Connect Module (soft reset)

• Monitoring network ports

• Configuring networks

• Configuring storage

Some of the useful network-level operations enabled during VC Domain Maintenance include:

• Monitoring network ports

• Changing network configurations

Some of the useful storage level operations enabled during VC Domain Maintenance include changingstorage configuration.

VC Domain Group configuration replicated to other VC Domains during VC Domain Maintenance

IMPORTANT: The VC Domain, network, and storage configuration changes performed during VC DomainMaintenance are automatically replicated to all other VC Domains that belong to the same VC DomainGroup when the VC Domain that maintenance operation is confirmed or discarded.

The following information is replicated to all VC Domains in the VC Domain Group during VC DomainMaintenance:

• Domain settings

Configuration for double density servers (for example, BL2x220c)•

• Configuration for full-height and half-height single density servers (for example, BL460c, BL480c)

• Ethernet settings

MAC Cache Failover:•

• Enable Fast MAC Cache Failover

• MAC Refresh Interval

• IGMP (Internet Group Management Protocol) Snooping:

Enable IGMP Snooping•

• IGMP Idle Timeout Interval

• Server VLAN Tagging Support:

Tunnel VLAN Taggings or Map VLAN Taggings•

• Force server connection setting

VC Domains 41

Page 42: Virtual Connect

• Multiple Network Speed Settings:

Preferred Link Connection•

• Preferred Link Connection Speed

• Maximum Link Connection

• Maximum Link Connection Speed

• Network SNMP settings:

• Enable SNMP

• Read Community

• System Contact

• Each SNMP trap defined community and IP address

• Fibre Channel SAN fabric settings:

Enable SMI-S•

• Fibre Channel SNMP settings:

• Enable SNMP

• Read Community

• System Contact

• Each SNMP trap Community and IP address

• For each Fibre Channel fabric:

Fabric name•

• Configuration speed, log and distribution, and fabric port location

• For each network uplink:

Name•

• State

• Connection mode

• Smart link

• Private network

• Enable VLAN tunneling

• States

• Network port location

• Speed/duplex mode

• Connection mode

• Preferred link connection

• Preferred link connection speed

• Maximum link connection

• Maximum link connection speed

• For each shared network:

Uplink Set Name•

• State

• Smart Link

• External VLAN ID

42 Managing VC Domains

Page 43: Virtual Connect

• Native VLAN

• Number of VLANs tagged associated to the shared network uplinks

• For each uplink set name:

Connection Mode•

• Network Port Location

Performing VC Domain MaintenanceThe VC Domain that maintenance operation comprises these steps:1. Initiate the VC Domain Maintenance.2. Perform changes through the Virtual Connect Manager Web interface.3. Confirmed the VC Domain changes through VCEM.To perform VC Domain Maintenance from the VC Domains page:1. Select the VC Domain upon which you want to perform VC Domain Maintenance.2. Click VC Domain Maintenance. The VC Domain Maintenance page appears.3. To unlock Virtual Connect Manager for domain, network, and storage changes, click Make changes

via VC Manager. Virtual Connect Manager web interface appears in a separate browser window. TheUnder Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network,and storage changes.

4. Using Virtual Connect Manager, log in with full user rights at Virtual Connect Manager, perform thenecessary changes, and save the changes. VCEM blocks all operations related to the VC Domain andto its respective VC Domain Group while VC Domain is under VC Domain Maintenance.

5. Close the Virtual Connect Manager web browser and return to the VC Domain Maintenance page inVCEM. Repeat steps 1 and 2 to confirm the changes in VCEM.

6. To apply the changes, click Complete VC Domain Maintenance. Optionally, to cancel VC Domainchanges, click Cancel. The Restore configuration checkbox enables VCEM to automatically restore theoriginal VC Domain configuration in case the new VC Domain configuration is not able to be replicatedto other VC Domains in the VC Domain Group. The Virtual Connect Enterprise Manageris executing the request message appears with a job ID code.

7. Click OK to go to the Jobs page and monitor job progress.

IMPORTANT: When a VC Domain is put in VC Domain Maintenance, operations such as backup andrestore Virtual Connect configurations are allowed. Restoring Virtual Connect configurations require additionalcare. If an old configuration is restored, verify that the configuration of this specific VC Domain remaincompatible with VC Domain Group, otherwise the VC Domain will be incompatible with VCEM. (For example,actual server profiles in the VC Domain after the restore may not match the previous state registered byVCEM.)

While VC Domain Maintenance enables the following actions to be performed on this VC Domain, theactions might cause side effects in VCEM. Therefore, HP does not recommend performing these actions.Domain-level operations (not recommended through VC Domain Maintenance):

• Configuration restoration for backup configurations performed out of VCEM control

• Domain deletion

To perform these domain-level operations, remove the VC Domain from VCEM, make the needed changes,and then reimport the VC Domain to VC Domain Group.

Backing up and restoring domain configurations through VC Domain Maintenance1. Go to the VC Domains tab.2. Select the VC Domain upon which you want to back up the configuration.3. Click VC Domain Maintenance. The VC Domain Maintenance page appears.4. To unlock Virtual Connect Manager for domain, network, and storage changes, click Make changes

via VC Manager. The Virtual Connect Manager web interface appears in a separate browser window.

VC Domains 43

Page 44: Virtual Connect

The Under Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network,and storage changes.

5. Using Virtual Connect Manager:a. Log in with full user rights at Virtual Connect Manager.b. Perform the domain backup by selecting Domain Settings→Domain Configuration, selecting

the Backup/Restore tab.c. Click Backup configuration. Wait until backup process completes.

6. Close the Virtual Connect Manager web browser and return to the VC Domain Maintenance page.7. Click Complete VC Domain Maintenance. The Virtual Connect Enterprise Manager is

executing the request message appears with a job ID code.8. Click OK to go to the Jobs page and monitor job progress.To perform VC Domain configuration restoration through VC Domain Maintenance:1. Select the VC Domains tab.2. Select the VC Domain upon which you want to restore the configuration.3. Click VC Domain Maintenance. The VC Domain Maintenance page appears.4. Click Make changes via VC Manager to unlock Virtual Connect Manager for domain, network, and

storage changes. Virtual Connect Manager web interface appears in a separate browser window. TheUnder Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network,and storage changes.

5. Using Virtual Connect Manager:a. Log in with full user rights at Virtual Connect Manager.b. Perform the domain backup by selecting Domain Settings→Domain Configuration, selecting

the Backup/Restore tab.c. Enter the file name for domain configuration.d. Click Restore configuration. Wait until backup process completes.

6. Close the Virtual Connect Manager web browser and return to the VC Domain Maintenance page.7. Click Complete VC Domain Maintenance. The Virtual Connect Enterprise Manager is

executing the request message appears with a job ID code.8. Click OK to go to the Jobs page and monitor job progress.

IMPORTANT: The domain configuration backup file created during VC Domain Maintenance and is validfor restoration while the VC Domain is in VC Domain Group. The domain configuration file is not valid afterthe VC Domain is removed from VC Domain Group.

Changes in Virtual Connect Manager that might affect completing VC Domain MaintenanceWhen you enable VC Domain Maintenance and make changes to a VC Domain base configuration, attemptsto complete VC Domain Maintenance might result in VCEM creating a failed job and the VC Domain remainsunder VC Domain Maintenance.Changes in Virtual Connect Manager that might cause problems in completing VC Domain Maintenanceinclude:

• Updating the Virtual Connect firmware to an incompatible version, (Domain Settings→FirmwareManagement). To resolve this issue, update the Virtual Connect firmware version to a compatibleversion and complete VC Domain Maintenance again.

• Deleting the domain (Domain Settings→Domain Configuration). To resolve this issue, restore theVirtual Connect configuration from a backup, or remove the VC Domain from the VC Domain Group.

• Breaking the Virtual Connect lock using VC command line. To resolve this issue, remove the VC Domainfrom the VC Domain Group.

• Virtual Connect fails to respond. To resolve this issue, even if the VC Domain Maintenance job failsbecause of poor or failed VC communication, fix the communication and complete VC DomainMaintenance again.

44 Managing VC Domains

Page 45: Virtual Connect

Working with HP Virtual Connect 8Gb Fibre Channel Module for c-Class BladeSystemVCEM cannot manage a VC Domain having one or more FC modules in an Incompatible state.The FC module can become incompatible in the following situations:

• An HP Virtual Connect 4Gb FC module replaces an HP Virtual Connect 8Gb 24-port FC module.

• An HP Virtual Connect 8Gb 24-port FC module replaces a HP Virtual Connect 4Gb FC module.

• If HP Virtual Connect 8Gb 24-port FC modules and HP Virtual Connect 4Gb FC modules share thesame IO bay slice. (For example, a HP Virtual Connect 4Gb FC module in IO Bay 3 and a HP VirtualConnect 8Gb 24-port FC module in IO Bay 4).

• IIn a multienclosure VC Domain, if there are mixed HP Virtual Connect 4Gb FC modules and HP VirtualConnect 8Gb 24-port FC modules in the same IO bay from different enclosures. (For example, 4GbFC modules in the local enclosure, but 8Gb FC modules in the remote enclosures.)

Adding or removing remote enclosures from a multienclosure domain in VC Domain Maintenance

NOTE: Adding enclosures that are not yet licensed in VCEM causes that VC Domain to be put in NotLicensed status. You must either license or remove the newly added enclosure.

To add or remove remote enclosures:1. Select the VC Domain that must be changed, and put it into maintenance mode.2. Access Virtual Connect Manager.3. Click Domain Settings→Domain Enclosures.4. Find and import the enclosures to be added, or delete the enclosures to be deleted.5. From VCEM, confirm VC Domain Maintenance.

Canceling a VC Domain Maintenance taskCanceling a VC Domain Maintenance discards domain, network, and storage configuration changes thatyou have performed until now, and returns the VC Domain to the configuration that is shared by all VCDomains within a VC Domain Group.

IMPORTANT: For more information on the domain, network, and storage configurations that VCEM canreplicate during completion of VC Domain Maintenance, or discard in case of a failure or cancellation ofthe VC Domain Maintenance operation, see VC Domain Group configuration replicated to other VC Domainsduring VC Domain Maintenance.

To cancel a VC Domain Maintenance from the VC Domain page:1. Select the VC Domain with status under maintenance.2. Click VC Domain Maintenance. The VC Domain Maintenance page appears.3. Click Cancel. The Virtual Connect Enterprise Manager is executing the request

message is appears with a job ID code.4. Click OK to go to the Jobs page and monitor job progress.

Resynchronizing a VC Domain with Configuration MismatchResynchronize a VC Domain is a useful way to force VCEM to verify that the VC Domain is still compatiblewith VC Domain Group configuration without removing and adding that VC Domain to a VC Domain Group.The VC Domain configuration must comply with the same requirements when you add a VC Domain into aVC Domain Group for the first time.To resynchronize a VC Domain:1. Go to the VC Domains tab.2. Select the VC Domain with Configuration Mismatch status.3. Click VC Domain Maintenance. A dialog box showing the VC Domain to be resynchronized appears.

VC Domains 45

Page 46: Virtual Connect

4. Click OK to confirm. The Virtual Connect Enterprise Manager is executing therequest message appears with a job ID code.

5. Click OK to go to the Jobs page and monitor job progress.

46 Managing VC Domains

Page 47: Virtual Connect

4 Managing VC Domain GroupsVC Domain Groups

This section describes the management of Virtual Connect (VC) Domain Groups using VCEM.A VC Domain consists of an HP BladeSystem enclosure, a set of associated Virtual Connect Ethernet andFibre Channel interconnect modules, and server blades that are managed together by a single instance ofVirtual Connect Manager. The VC Domain contains specified networks, server profiles, and user accountsthat simplify the setup and administration of server connections. Establishing a VC Domain Group enablesadministrators to upgrade, replace, or move servers within their enclosures without changes to the externalLAN/SAN environments.VCEM keeps unassigned server profiles at the VC Domain Group level.With VCEM you can move and copy profiles within a single VC Domain or between any VC Domains withina VC Domain Group.

IMPORTANT: When a VC Domain is imported into VCEM and managed as part of a VC Domain Group,all unassigned server profiles associated with the VC Domain become part of the VC Domain Group. Anyunassigned server profiles created through VCEM become part of the VC Domain Group.

To access the VC Domain Group page in VCEM, click the VC Domain Group tab. The VC Domain Grouppage appears.

Figure 4-1 VC Domain Groups

The following table lists and describes the columns on the VC Domain Groups page.

DescriptionItem

Describes Virtual Connect Domain Group statusStatus

Lists Virtual Connect Domain Group nameName

Identifies the number of domains in the group# of Domains

The following table lists and describes VC Domain Group icons and status.

DescriptionIconStatus

All VC Domains that belong to this VCDomain Group share the same domainconfiguration.

Configuration in synch

VC Domain Groups 47

Page 48: Virtual Connect

DescriptionIconStatus

VC Domain is unlocked for domain, network,and storage changes through the VirtualConnect Manager. After completing thedomain network and storage changes, youmust confirm the new VC Domainconfiguration in VCEM. VCEM operationsrelated to this VC domain or to VC DomainGroup, such as create profile, move profile,profile failover, and so on, are blocked whilethe VC Domain is under maintenance.

Under maintenance

To display the properties for a particular VC Domain Group, such as status, MAC range type, WWN rangetype, domain names, and server profiles, click the group name.From the VC Domain Groups page, you can perform the following actions:

• Create a VC Domain Group

• Maintaining a VC Domain

• Cancel VC Domain Maintenance task

• Upgrade Firmware Mode

• Delete a VC Domain Group

Creating a VC Domain Group

IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from HP SIM. To accessthis reference, you must correlate the HP SIM and Virtual Connect logs. For more information, see CorrelatingVCEM operations in HP SIM and Virtual Connect logs.

To manage multienclosure VC Domains in VCEM, you must perform the following steps before you createa VC Domain Group or add a VC Domain to a VC Domain Group:1. Log in to Virtual Connect Manager.2. Find and import a local enclosure, and then select the appropriate Double-dense option.3. Skip the Network and Fibre Channel configuration wizards, and then navigate directly to the VC Domain

user interface.4. Find and import the necessary remote enclosures in the correct order through Virtual Connect Manager.5. Go to HP SIM and perform a manual discovery on Onboard Administrator IP address of all released

VC Domain enclosures.VCEM cannot manage a VC Domain that has one or more FC modules in an Incompatible state.The FC module can become incompatible in the following situations:

• An HP Virtual Connect 4Gb FC module replaces an HP Virtual Connect 8Gb 24-port FC module.

• An HP Virtual Connect 8Gb 24-port FC module replaces a HP Virtual Connect 4Gb FC module.

• If HP Virtual Connect 8Gb 24-port FC modules and HP Virtual Connect 4Gb FC modules share thesame IO bay slice. (For example, a HP Virtual Connect 4Gb FC module in IO Bay 3 and a HP VirtualConnect 8Gb 24-port FC module in IO Bay 4).

• IIn a multienclosure VC Domain, if there are mixed HP Virtual Connect 4Gb FC modules and HP VirtualConnect 8Gb 24-port FC modules in the same IO bay from different enclosures. (For example, 4GbFC modules in the local enclosure, but 8Gb FC modules in the remote enclosures.)

To create a VC Domain Group:1. Click New....

(Optional) If the enclosures related to the selected VC Domains are not licensed to VCEM, then theLicense page appears below the VC Domain Group list. (For more information, see Licensing an enclosurefor VCEM.) Otherwise, the Create VC Domain Group appears below the VC Domain Group list.

2. (Optional) You can provide a new name for the unconfigured VC Domains. Valid VC Domain Groupnames are alphanumeric, hyphens (-), underscore (_), and cannot exceed 64 characters.

48 Managing VC Domain Groups

Page 49: Virtual Connect

3. Enter the username and password for each VC Domain. Ensure you provide VC Domain credentialswill full privileges. VC Domains appear as:

• Unconfigured domains, which appear in the System Name column with the unassigned name,VCD_name

• Configured domains, which appear in the System Name column with their previously assignedname.

4. Enter the username and password for the Onboard Administrator of each unconfigured VC Domain.Ensure that you provide the Onboard Administrator credentials with full privileges if the Virtual ConnectModule is not configured.(Optional) In some cases you might wish to overwrite the existing VC Domain configuration for selectedVC Domains. To enable this action, select Existing VC Domain configuration settings for selectedVC Domain(s) without server profiles will be overridden by selected base VC Domainconfiguration defined for the VC Domain Group. VCEM validates that the selected VC Domainconfigurations match the VC Domain Group configuration. VC Domains that are already configuredand have server profiles are not affected.

5. Enter the VC Domain Group name in the VC Domain Group Name field. Valid VC Domain Groupnames are alphanumeric, hyphens (-), underscore (_), and cannot exceed 64 characters.

6. From the Configuration based on VC Domain list, select the VC Domain configuration upon which thenew VC Domain Group is to be based. The Configuration VC Domain list contains only configured VCDomains.

7. From the Select Serial Number type list, select whether the serial number type is a logical serial numberor factory default.

8. From the Select MAC range type list, select whether the MAC address range type is VCEM-defined,user-defined, or factory-default. You can only select the user-defined option for MAC range type if aMAC custom range is defined.

9. From the Select WWN range type list, select whether the WWN address range type is VCEM-defined,user-defined, or factory-default. You can only select the User-Defined option for WWN range type if aWWN custom range is defined.

10. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessageappears.

11. Click OK to go to the Jobs page and monitor job progress.

Maintaining a VC Domain from the VC Domain Group pageTo perform VC Domain maintenance from the VC Domain Group page:1. Select the VC Domain Group on which you want to perform maintenance.2. Click VC Domain Maintenance.3. Select the target VC Domain within the selected VC Domain Group which will be enabled for

maintenance, and click Next. The VC Domain Maintenance page appears.4. To unlock Virtual Connect Manager for domain, network, and storage changes, click Make changes

via VC Manager. Virtual Connect Manager web interface appears in a separate browser window. Theunder maintenance status indicates that the VC Domain Group is temporarily unlocked for domainnetwork and storage.

5. Using Virtual Connect Manager, log in with full user rights at VC Manager, perform the necessarychanges, and save the changes. VCEM blocks all operations related to the VC Domain and to itsrespective VC Domain Group while VC Domain is under VC Domain Maintenance. Close the VCManager web browser and return to the VC Domain Group page in VCEM. To confirm changes inVCEM, repeat steps 1 and 2.

6. To apply the changes, click Complete VC Domain Maintenance. Optionally, you can cancel VCDomain changes by clicking Cancel. The Restore configuration checkbox enables VCEM toautomatically restore the original VC Domain configuration in case changes cannot be applied to theVC Domain Group. The Virtual Connect Enterprise Manager is executing the requestmessage appears with a job ID code.

7. Click OK to go to the Jobs page and monitor job progress.

VC Domain Groups 49

Page 50: Virtual Connect

Canceling a VC Domain Group maintenance task1. From the VC Domain Group page, select the VC Domain Group with status Under Maintenance.2. Click VC Domain Maintenance. The VC Domain Group Maintenance page appears.3. Click Cancel. The Virtual Connect Enterprise manager is executing the request

message appears with a job ID code.4. Click OK to go to the Jobs page and monitor job progress.

Upgrading VC Domain Group Firmware Mode

IMPORTANT: VCEM upgrade firmware mode does not allow a downgrade of a VC Domain Group firmwareversion. You must verify that the VC firmware versions for VC Domains within the VC Domain Group arelater than the current VC Domain Group firmware version. Otherwise, the upgrade firmware mode for theVC Domain Group will not be allowed.

Upgrade VC Domain Group Firmware Mode enables you to upgrade the VC firmware mode of VC DomainGroup according to the VC firmware versions of VC Domains that belong to the VC Domain Group. Toupgrade the VC Domain Group firmware mode to a later version:1. Select to the VC Domain Group to be upgraded.2. From the VC Domain Group page, click Upgrade Firmware Mode.3. Select a firmware version from Upgrade Firmware Mode to.4. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears with a job ID code.5. Click OK to go to the Jobs page and monitor job progress.

Deleting a VC Domain Group

IMPORTANT: If you delete a VC Domain Group, then all unassigned server profiles within that VC DomainGroup will be posted to one of the VC Domains that were part of the deleted VC Domain Group. To verifywhich VC Domain contains the unassigned server profiles after the VC Domain Group deletion job iscompleted, look at the report generated by the related job in the VCEM event. To access this report fromthe HP SIM left navigation panel, select Events→Shared→VCEM Events.

IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from HP SIM. To accessthis reference, you must correlate the HP SIM and Virtual Connect logs. For more information, see CorrelatingVCEM operations in HP SIM and Virtual Connect logs.

IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from HP SIM. To accessthis reference, you must correlate the HP SIM and Virtual Connect logs. For more information, see CorrelatingVCEM operations in HP SIM and Virtual Connect logs.

To delete a VC Domain Group:1. Click the VC Domain Groups tab. The VC Domain Groups page appears.2. Select the VC Domain Groups to be deleted.3. Click Delete. The Delete VC Domain Group page appears.

50 Managing VC Domain Groups

Page 51: Virtual Connect

4. Perform the following actions for each VC Domain that uses HP-predefined or user-defined ranges withinthe VC Domain Group that you want to remove. Factory-default MAC and WWN ranges are releasedback to VC Manager as Factory-default.If factory-default MAC or WWN addresses or serial numbers are not being used, address ranges mustbe specified for each removed VC Domain. These address ranges must be unique and distinct to preventassignment of duplicate addresses. Each selected MAC and WWN address range must also be recordedas an exclusion range to prevent assignment by VCEM. VCEM manages a proprietary serial numberrange, so there is no need to define an external range or serial number. The selected HP-predefinedranges are identified as a user-defined ranges by the VC Manager after the VC Domain is removedfrom VCEM.The selected HP-predefined ranges are identified as a user-defined range for the Virtual Connect Managerafter the VCEM Domain is removed from VCEM.a. Enter the MAC address range.

To use an HP-predefined MAC range, from the MAC range section, select the Use HP Pre-Definedrange box, and then select a range from the list.You can also clear the Use HP Pre-Defined range box and then enter the start and end addressesfor the MAC range. Valid MAC address range is NN-NN-NN-NN-NN-NN where N is ahexadecimal digit (0-F) and cannot exceed 14 characters. The VC Domain configuration appliesthis MAC address range after being removed from VCEM control.

b. Enter the WWN address range.To use an HP-predefined WWN range, from the WWN Range section, select the Use HPPre-Defined range box, and then select a range from the list.You can also clear the Use Pre-Defined range box and then enter the start and end addressesfor the WWN range. Valid WWN address range is NN:NN:NN:NN:NN:NN:NN:NN whereN is a hexadecimal digit (0-F) and cannot exceed 23 characters. The VC Domain configurationapplies this WWN address range after being removed from VCEM control.

c. Enter the serial number range.To use an HP-predefined serial number range, from the serial number range section, select the UsePre-Defined range box, and then select a range from the list.You can also clear the User Pre-Defined range box and then enter the start and end values forthe serial number range. Valid serial number range VCX01NNNNN for user-defined orVCXNNNNNNN for HP-predefined where N is a hexadecimal digit (0-F) and cannot exceed 10characters. The VC Domain configuration applies this serial number address change after beingremoved from VCEM control.

5. Click OK. You are prompted to confirm the deletion.6. Click OK. If you click Cancel, you continue in the Delete VC Domain Group page. The Virtual

Connect Enterprise Manager is executing the request message appears.7. Click OK, to go to the Jobs page and monitor job progress.VCEM generates an HP SIM event that describes in detail about the released VC Domain, such as domainname, MAC range type, WWN range type, serial number range type, server profiles and related MACaddresses, addresses, serial numbers, network connections, and Fibre Channel SAN connection range types.

Adding or removing VC modules to VC Domain Group configurationTo add or remove VC modules to all VC Domains managed by a VC Domain Group:1. Click the VC Domain Groups tab.2. Select the desired VC Domain Group where you want to add or remove VC modules, and then click

Delete.For more information, see Deleting a VC Domain Group.

VC Domain Groups 51

Page 52: Virtual Connect

3. For each VC Domain released from the VC Domain Group, insert or remove VC modules in thecorresponding enclosure, and perform the necessary domain, network, and storage configurationchanges in the Virtual Connect Manager user interface.Before VC module removal, remove the VC module uplink ports from all existing Network or SharedUplink settings from VC Domain configuration.For VC module removal, from the VC Manager user interface, click HardwareOverview→Enclosure_Name→Interconnect Bays, select the VC module at the bay you want toremove, then click Remove from Domain.

4. Return to VCEM, click the VC Domain Groups tab, and click New. For more information about creatinga VC Domain Group, see Creating a VC Domain Group. At step 1, select the VC Domains to add tothe new VC Domain Group. Wait until the job operation completes. As a result, the new VC DomainGroup created contains an updated configuration reflecting the new VC modules.

NOTE: Existing profiles cannot see new Fibre Channel SAN connections added using these steps. However,if the fabrics were created on Virtual Connect Manager, you can see the Fibre Channel SAN connections.For more information, see Editing a profile.

Moving Ethernet networks (VLANs tagged) from one shared uplink to another1. Click the VC Domains tab, and select a VC Domain.2. Click VC Domain Maintenance, and enable VC Domain Maintenance by clicking Make changes via

VC Manager.3. In Virtual Connect Manager user interface, delete the desired shared uplink sets or delete desired

Ethernet networks (VLANs tagged) from the shared uplink sets.4. Go back to VCEM and complete VC Domain Maintenance by clicking Complete VC Domain

Maintenance.5. Repeat steps 1 and 2.6. In Virtual Connect Manager user interface, create Ethernet networks (VLANs tagged) to any shared

uplink set.7. Go back to VCEM, and complete VC Domain Maintenance by clicking Complete VC Domain

Maintenance.

Correlating VCEM operations in HP SIM and Virtual Connect logsAll VCEM operations are logged in HP SIM Audit log and provide a reference to the VC Domain beingmanaged. The VCEM operations related to a managed VC Domain are also logged by Virtual ConnectManager in its system log. In an audit process for VCEM operations, you must correlate HP SIM in VirtualConnect Manager logs. To perform this task:1. Look for VCEM entries in HP SIM Audit Log by clicking Tasks & Logs→View HP Systems Insight

Manager Audit log.2. Search for a VCEM operation that is starting: “Virtual Connect Enterprise Manager (VCEM) - Starting

job.”3. You can find timestamp, VCEM operation (Job number#, Job details, Job title, VC Domain name), and

username. For most VCEM operations you can find the related name of VC Domain.4. Look for VC Domain system log in Virtual Connect Manager by clicking Tools→System Log.5. Search for the log entries based on timestamp. Be sure to take the time difference between the CMS

and VC Domain into account.There is no specific marker for VCEM operations. VCEM operations usually are encompassed by “VCMuser login” and “VCM user logout” entries for the username “A<CMS_IP>@<CMS_IP>.” For example,CMS IP 16.84.195.136 appears in the VC log entry as a reference to“([email protected])” because VCEM runs on the CMS system.

52 Managing VC Domain Groups

Page 53: Virtual Connect

5 Managing server profilesProfiles

This section describes how to create and manage profiles for use with VCEM.A Virtual Connect server profile is a logical grouping of attributes related to server connectivity that can beassigned to a server bay. A server profile can be assigned to any server bay within the VC Domain Group.VCEM requires the server to power down for any profile operations such as create, delete, unassign, copy,move, and edit. For more information on this procedure, see "Bays."To access the Profiles page, click the Profiles tab. Information on the Profiles pages can be filtered byselecting one of the following entries in the Filter list.

• All—Select this option to display all profiles being managed by VCEM.

• VC Domain—Select this option to display all profiles that exist in a specified VC Domain. The secondlist can be used to select a specific VC Domain to use as a filter.

• VC Domain Group—Select this option to show all profiles that exist in a VC Domain Group. The secondlist can be used to select a specific VC Domain Group to use as a filter.

After selecting the options in the filter, click Filter.

Figure 5-1 Profiles page

The following table lists the columns in the managing profile table.

DescriptionItem

Profile status (assigned or not assigned)Status

Profile nameName

VC Domain Group nameVC Domain Group

VC Domain nameVC Domain

Enclosure nameEnclosure

Bay numberBay

Profiles 53

Page 54: Virtual Connect

A server profile defines connections for a blade server. Server profiles can include the following information:

• Profile name

• Logical serial number and logical UUID

• Ethernet network connections and PXE settings

• MAC addresses

• Fibre Channel fabric connections

• WWN addresses

• Server boot configuration

• BIOS settings

Newer VC Domain versions provide a broader set of configuration in the server profile. The following tablelists the features that are configurable depending on the VC Domain versions.

Virtual Connect 2.0xVirtual Connect 2.1xVirtual Connect 2.3xFeature

•••Server VLAN tagging

•••Add/Remove Fibre ChannelSAN connections

•••Integrity blade support (EFIpartition data)

•••Ethernet connection port speedconfiguration

•••Double-density blade support

From the managing profiles screen, you can perform the following tasks:

• Create a profile

• Delete one or more profiles

• Edit a profile

• Assign a profile

• Unassign a profile

• Copy a profile to a bay

• Move a profile

• View network and Fibre Channel information for a profile

• Perform a VC Profile Failover operation

NOTE: If the server profile has Flex-10 connections enabled, and server blade NICs (onboard or mezzaninecard) are connected to HP 10/10Gb-F Virtual Connect Ethernet Module, Virtual Connect requires you to

54 Managing server profiles

Page 55: Virtual Connect

power off the server blade to perform server profile operations with VC firmware 2.0x or 2.1x. However,in VC firmware 2.3x, you can perform these operations with the server blade powered on.

Creating a profile

NOTE: Depending on the VC Domain version, the create profile page displays a different set ofconfigurations. To verify the available features for each VC Domain version, see the feature set table earlierin this section.

NOTE: In a VC Domain Group with VC firmware 2.1x, the 8Gb FC module appears only if VCEM detectsit. If VCEM detects the 4Gb FC module, then the maximum port speed will be 4Gb.

1. From the Profiles page, click New.2. From the Member of VC Domain Group menu, select the VC Domain Group to which the profile will

belong.The Create New Profile information appears below the profiles list.

3. In the Profile name box, enter a unique profile name.4. (Optional) To use factory-assigned MAC addresses and WWNs, and override the VCEM-provided

settings, select Show advanced settings.If you choose to use factory-assigned MAC addresses, WWNs, and serial numbers, these changesapply to every Ethernet and Fibre Channel connection in a server profile.

• To use server factory defaults for Ethernet MAC addresses, select Use Server Factory Defaultsfor Ethernet MAC addresses.

• To use server factory defaults for Fibre Channel WWNs, select Server Factory Defaults for FibreChannel WWNs.

• To use server factory defaults for Serial Number, select Server Factory Defaults for SerialNumber.

5. In the Ethernet network connections table, select at least two Ethernet networks. Network names areoptional. In VC Domain , it is possible to select Multiple Networks. To add more connections, click AddNetwork Connection. To remove a connection, click the X icon at the right side of the table.

6. In the Fibre Channel SAN connections table, set the Fibre Channel SAN connections. To add moreconnections in VC Domain , click Add FC SAN Connection. To remove a connection, click the X iconat the right side of the table.

7. (Optional) In the Fibre Channel Boot Parameters table, enter the boot parameters for defined FibreChannel SAN connections. The default boot parameter is Use Bios. The World Wide Part Number(WWPN) and Logical Unit Number (LUN) are required only for the primary and secondary SAN boot.

8. (Optional) To create the bay assignment, select VC Domain, and then select an available target serverbay. If a profile is not assigned to a server bay or fails to assign to a server bay, then that profilebecomes unassigned to a VC Domain Group.

9. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessageappears.

10. Click OK to go to the Jobs page and monitor job progress.

NOTE: To create profiles for Integrity Blades that boot from SAN, you must manually configure the SANboot entries in the blade server EFI console.

Configuring the target boot LUNWhen creating or editing server profiles, you can specify a target boot LUN for the FC SAN connectionsdesignated as Primary and Secondary in the boot priority column.

Profiles 55

Page 56: Virtual Connect

Target boot LUN values must be compliant with proper ranges.

▲ VC Domains—You can provide the target boot LUN in either of the possible formats:

When using LUN values from 0–255, you can specify the LUN and either decimal or in 16-digithexadecimal number format.

• When using LUN values greater than 255, you must specify the LUN in 16-digit hexadecimalnumber format.

To specify the LUN and a 16-digit hexadecimal number format, place the desired hexadecimal numberpreceded by leading zeros as shown in the following examples:

• 1023 can be represented in 16-digit hexadecimal format as 00000000000003ff or00000000000003FF (not case-sensitive).

• 18446744073709551615 is represented in 16-digit hexadecimal format as ffffffffffffffff orFFFFFFFFFFFFFFFF.

Configuring multiple networksWhen creating or editing a profile in VC Domains, you can configure multiple networks to use as a sameEthernet connection port.1. In the Ethernet connections table expand the network name menu and select Multiple Networks. The

Server VLAN tag to vNet Mappings window appears.

Figure 5-2 Server VLAN tag to vNet Mappings window

2. Select the vNet name server VLAN ID.3. To add a vNet mapping, click Add Mapping. To remove a mapping, click the Delete icon.

You can select one mapping to be untagged, meaning the VLAN ID is applied to that mapping.

4. (Optional) Instead of deleting mappings manually, the Copy from button enables you to copy themappings from an existing profile or from a Shared Uplink Set.

56 Managing server profiles

Page 57: Virtual Connect

Figure 5-3 Copying a profile using the Copy from button

5. (Optional) You can create vNet mappings based on a shared uplink set. To perform this task, selectForce same VLAN mappings as shared uplink sets.

Figure 5-4 Force same VLAN mappings as Shared Uplink Sets checkbox

Configuring Network Port SpeedWhen creating or editing a profile, you can configure the network speed of an Ethernet network connection.You can select network speeds of 1Gb, 2Gb, 4Gb, and 8Gb, or Auto.1. In the Ethernet connections table, select the desired port speed from the Port Speed Setting menu.2. (Optional) To select the desired port speed for the connection, select Custom. The Custom Port Speed

windows appears. Enter the desired port speed.

Figure 5-5 Custom Port Speed window

Profiles 57

Page 58: Virtual Connect

Deleting a profile1. From the Profiles page, select the profiles to be deleted.2. Click Delete. You are prompted to confirm the deletion.3. Click OK to go to the Jobs page and monitor job progress.

Editing a profile

NOTE: In a VC Domain Group with VC firmware 2.1x, the 8Gb FC module appears only if VCEM detectsit. If VCEM detects the 4Gb FC module, then the maximum port speed will be 4Gb.

When editing server profiles, VC Domain Group memberships and server bay assignments are read only.To edit a server profile:1. From the Profiles page, select the profile to be edited.2. Click Edit. The Edit Profile information appears below the profile table.3. Enter changes to the Profile name as needed.4. Enter changes to the Ethernet network connections (physical ports) as needed, and then click Add

Network Connection.5. Enter changes to Fibre Channel SAN connections, and Fibre Channel boot parameters as necessary.

Depending on the physical changes to the Fibre Channel Virtual Connect modules, the Add FC Connectionbutton or the Remove FC Connection button appears.

6. (Optional) To erase the current EFI partition information in the profile for profiles assigned to Integrityblades, select Cleanup the EFI partition data.

7. (Optional) To inform the bay assignment, select VC Domain, and then select an available target serverbay. If a profile is not assigned to a server bay or fails to assign to a server bay, then that profile issaved as unassigned in the VC Domain Group. The Assign to bay button is available only if the selectedserver profile being edited is unassigned.

8. Verify the server bay assignment.9. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.10. Click OK to go to the Jobs page and monitor job progress.

Verifying the presence of EFI partition dataWhen editing profiles that are assigned to Integrity server blades, you can verify the presence of the EFIpartition data that controls the Integrity server blade boot.To verify the presence if the EFI partition data:1. From the Profiles page, select the profile to be verified.2. Click Edit. The Edit Profile information appears below the profile table.3. In the Profile Information table, click the question mark icon.4. If EFI partition data is present in the profile, the EFI icon appears as well as the option to clean up the

data.5. (Optional) To clean up the partition data, check the Remove EFI partition attached to profile checkbox

and click OK. The Virtual Connect Enterprise Manager is executing the requestmessage appears.

6. Click OK to go to the Jobs page and monitor job progress.

Assigning a profile1. From the Profiles page, filter the profiles by the VC Domain Group that has the unassigned profiles.2. In the profiles list, click the Assign link, or select a profile to assign, and then click Assign. The Profile

Assignment page appears.3. Select an available server bay to which the profile is assigned.4. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.5. Click OK to go to the Jobs page and monitor job progress.

58 Managing server profiles

Page 59: Virtual Connect

Unassigning a profile1. From the Profiles page, select the assigned profile to unassign.2. Click Unassign. You are prompted to confirm the unassignment.3. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.4. Click OK to go to the Jobs page and monitor job progress.

Copying and assigning a profile to a bay1. From the Profiles page, select the profile that must be copied and assigned.2. Click Copy.3. Enter a unique name for the new profile.4. Select an available bay to which the new profile is assigned.5. Set the port information.6. Enter a unique name for the new profile.7. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.8. Click OK to go to the Jobs page and monitor job progress.

Moving a profile1. From the Profiles page, select a profile.2. Click Move. The Move Profile page appears.3. In the Move to Bay list, select an available bay to which the new profile is to be moved.4. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.5. Click OK to go to the Jobs page and monitor job progress.

Performing a VC Profile FailoverVC Profile Failover is a feature that enables a server hardware failure to be recoverable, either manually orautomatically, by restarting the failed server boot drive on a designated replacement (or spare) server.VC Profile Failover functionality enables you to designate spare servers and perform one-button VC ProfileFailover operations. Also, when full HP SIM server discovery is enabled, you can enable trigger-initiated VCProfile Failovers using action-on-events functionality in HP SIM.

IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from HP SIM. To accessthis reference, you must correlate the HP SIM and Virtual Connect logs. For more information, see CorrelatingVCEM operations in HP SIM and Virtual Connect logs.

Preconditions for VC Profile Failover

• The failed server is a server that is configured as SAN-boot.

• The failed server has no dependency on a local drive.

• A spare server within the same VC Domain Group has been designated and is powered off.

• The spare server is the same model as the failed server.

Designating spare bays1. Select one or more bays that do not have a profile applied.2. Click Apply Spares.You can initiate VC Profile Failover either through the command line interface (CLI) or through the VCEMgraphical user interface (GUI).

Profiles 59

Page 60: Virtual Connect

Designate spares according to the service level needs and the server blade models being used. For example,if a data center is using three blade models in the environment, designate a spare for each. These designatedspares can be any system that does not already have a profile assigned within the same VC Domain Group.

Initiating VC Profile Failover through the VCEM CLIYou must have HP SIM administrative privileges to perform VC Profile Failover tasks using the CLI.To initiate VC Profile Failover through the VCEM CLI, enter C:\>VCEM -failover arguments, thenenter the appropriate argument as follows:

• For a bay, enter -bay enclosure_name:bay_number.

• For a host, enter -host hostname.

• For an IP address, enter -ip IP_address.

The host and IP address are valid arguments only when HP SIM runs on the same system as VCEM and fullserver discovery is in operation in HP SIM.Single-density server bays are specified by their number. Double-density server bays must be specified withthe bay number followed by the A or B letter such as 12A or 12B.For more information about CLI usage in VCEM, see the "Command Line Interface usage in Virtual ConnectEnterprise Manager" chapter in the HP Virtual Connect Enterprise Manager User Guide.

Initiating VC Profile Failover through the VCEM GUI1. Select an assigned profile with an acceptable spare server.2. Click VC Profile Failover. The Virtual Connect Enterprise Manager is executing the

request message appears.3. Click OK to go to the Jobs page and monitor job progress.

Initiating VC Profile Failover using HP SIM Automatic Event HandlingThe VCEM CLI can be used to automatically trigger VC Profile Failovers using HP SIM automatic eventhandling. A collection of sample failover SNMP traps exists in the "Profile Failover Trigger Events” collectionunder “VCEM Events” in the VCEM user interface. VCEM has also created two custom tools to facilitateautomated VC Profile Failover.For automatic event handling to work, the following prerequisites must be met:

• VCEM 1.40 has been installed as part of a HP SIM installation.

• DNS is properly configured in the environment.

• The Administrator account is usable on the system in which VCEM and HP SIM reside.

The custom tools enable an administrator to initiate a VC Profile Failover. Any administrator that can run allthe tools on HP SIM or VCEM installation can perform a failover. The two custom tools can be deleted fromthe HP SIM or VCEM installation with no impact other than the inability to configure automatic event handling.

IMPORTANT: Enabling automated failover actions can have implications in a data center. Before completingthis task, review any automatic event handlers. Unintended failovers can result in the loss of data andunnecessary system downtime.

To set up automated VC Profile Failover:1. Enable HP SIM automatic discovery by selecting Options→Discovery. Discovery must be enabled to

discover servers within the environment.2. Enable active event handling by selecting Options→Events→Automatic Event Handling→New

Task. This step launches a wizard to aid in the creation of a task.3. Use the wizard to select a name for the event handler.4. To monitor the selected CPU and memory-related failures, select the Profile Failover Trigger Events

event collection.5. Select the systems that the event handler must monitor. You can select specific systems or a collection

of systems.6. Select Run custom CMS tool, and then select VCEM Profile Failover by Hostname.

60 Managing server profiles

Page 61: Virtual Connect

7. If there is a specific time the event handler must be active, choose a time filter.8. Review the selected events, systems, and actions for the automatic event handler.VC Profile Failovers now occur whenever any designated system generates one of the events within the eventcollection. When an event triggers a VC Profile Failover, a VCEM Failover job appears to have originatedfrom the administrator user account and fail over the system that generated the event.For more information about VC Profile Failover, see the failover white paper at http://www.hp.com/go/vcem.For more information about Automatic Event Handling, see the HP SIM User Guide athttp://www.hp.com/go/hpsim.

Profiles 61

Page 62: Virtual Connect

62

Page 63: Virtual Connect

6 Managing baysBays

Only the bays that are inside a VC Domain Group appear on the Bays page.Bays can be filtered by selecting one of the following entries in the Filter list:

• All—Select this option to display all bays.

• VC Domain—Select this option to display all bays that exist in a specified VC Domain. The second listcan be used to select a specific VC Domain to use as a filter.

• VC Domain Group—Select this option to display all bays that exist in a specific VC Domain Group.The second list can be used to select a specific VC Domain Group to use as a filter.

The Show more details checkbox enables you to see physical information such as power state, UID LEDstate, and the blade model inside each bay in the list. The option is enabled and selected by default onlywhen filtering devices bays by VC Domain.After selecting the options in the filter, click Filter.

Figure 6-1 Bays page

The following table lists the columns in the bays list table.

DescriptionItem

Enclosure nameEnclosure

Bay numberBay #

Select spares to apply as VC Profile FailoverSpare

Profile nameProfile

To see more information about bays, select the Show more info checkbox. The following table lists theadditional information that appears on the screen.

Bays 63

Page 64: Virtual Connect

DescriptionItem

Model of blade serverBlade model

Enclosure is powered-up or powered-downPower

Unique identifier that tells if the light on the device is powered-upor powered-down

UID

To see server bay status and blade server information in case there is a server in a selected bay, click thebay number, then a status window appears. The following table lists the additional information that appears.

DescriptionItem

Server profile name assigned to the bayAssigned Server Profile

Enclosure name where the bay is locatedEnclosure Name

Icon that indicates the Unite Identifier (UID) state: on, off, or notavailable

UID

Icon that indicates the server power statusPower Status/Control

Factory serial number for physical serverLogical Serial Number designated by server profile

Serial NumberSerial Number (Logical)

Factory UUID for physical serverLogical UUID designated by server profile

UUIDUUID (Logical)

Model of server bladeProduct Name

Powering down a bayTo view a window displaying the power status of a bay, click the number in the Bay# column. You canpower down and power up the server inside that bay by clicking the buttons.

Figure 6-2 Window displaying the power status of a bay

To remotely power down a bay:

64 Managing bays

Page 65: Virtual Connect

1. Click the Bays tab.2. To determine the power status of the bay, click the bay number. A status window appears.3. Depending on the power status of the bay, perform one of the following steps:

• If the bay is currently powered down, then proceed to the Assigning a profile to a bay proceduresection.

• If the bay is currently powered up, then click Momentary Press, which automatically powersdown the bay.

• If the bay is currently powered up and clicking Momentary Press does not power down the bay,then click Press and Hold.

CAUTION: Only use the Press and Hold option when other attempts to powering down the bay havefailed, such as attempting to shut down physical bay instead of remotely.

Figure 6-3 Bay status with tab and hold

Assigning a profile to a bayYou can assign a profile to a bay only if the bay is not associated with a server or if the server is powereddown. To assign a profile to a bay:1. Click the Bays tab.2. (Optional) From the Filter list, select VC Domain or VC Domain Group, and click Filter.3. Select the bay.4. Click Assign profile. The Assign Profile page appears.5. Select an unassigned profile.6. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.7. Click OK to go to the Jobs page and monitor job progress.

Unassigning a profile from a bayYou can only unassign a profile from a bay if the bay is not associated with a server of if the server ispowered down. To unassign a profile from a bay:1. Click the Bays tab.2. (Optional) From the Filter list, select VC Domain or VC Domain Group.3. Select the bay for which you want to unassign a profile.4. Click Unassign profile. You are prompted to confirm the unassignment.5. Click OK. The Virtual Connect Enterprise Manager is executing the requestmessage

appears.6. Click OK to go to the Jobs page and monitor job progress.

Bays 65

Page 66: Virtual Connect

Designating spare bays1. Select one or more Spares checkboxes for bays that do not have a profile applied.2. Click Apply Spares.You can initiate VC Profile Failover either through the command line interpreter (CLI) or through the VCEMgraphical user interface (GUI).Designate spares according to the service level needs and the blade models being used. For example, if adata center is using three blade models in the environment, designate a spare for each of the three blademodel types. These designated spares can be any systems that do not already have a profile assigned withinthe same VC Domain Group.

Performing a VC Profile FailoverVC Profile Failover is a feature whereby a server hardware failure may be recoverable, either manually orautomatically, by restarting the failed server boot drive on a designated replacement (or spare) server.VC Profile Failover functionality enables you to designate spare servers and perform one-button VC ProfileFailover operations. Also, when full HP SIM server discovery is enabled, you can enable trigger-initiated VCProfile Failovers using action-on-events functionality in HP SIM.

IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from HP SIM. To accessthis reference, you must correlate the HP SIM and Virtual Connect logs. For more information, see CorrelatingVCEM operations in HP SIM and Virtual Connect logs.

Preconditions for VC Profile Failover

• The failed server is configured as SAN-boot.

• The failed server has no dependency on a local drive.

• A spare server within the same VC Domain Group has been designated and is powered off.

• The spare server is the same model as the failed server.

Designating spare baysFor more information about designating spare bays, see Designating spare bays.

Initiating VC Profile Failover through the VCEM CLIYou must have HP SIM administrative privileges to perform VC Profile Failover tasks using the CLI.To initiate VC Profile Failover using the CLI, enter C:\>VCEM -failover arguments, then enter theappropriate argument as follows:

• For a bay, enter -bay enclosure_name:bay_number

• For a host, enter -host hostname

• For an IP address, enter -ip IP_address

The host and IP address are valid arguments only when HP SIM runs on the same system as VCEM and fullserver discovery is in operation in HP SIM.For more information about CLI usage in VCEM, see the "Command Line Usage in Virtual Connect EnterpriseManager" chapter in the HP Virtual Connect Enterprise Manager User Guide.

Initiating VC Profile Failover through the VCEM GUI1. Select an assigned profile with an acceptable spare server.2. Select a bay with an assigned profile.3. Click Profile Failover. The Virtual Connect Enterprise Manager is executing the

request message appears.4. Click OK to go to the Jobs page and monitor job progress.

66 Managing bays

Page 67: Virtual Connect

Initiating VC Profile Failover using HP SIM Automatic Event HandlingThe VCEM CLI can be used to automatically trigger VC Profile Failovers using HP SIM automatic eventhandling. A collection of sample failover SNMP traps exists in the "Profile Failover Trigger Events” collectionunder “VCEM Events” in the VCEM user interface. VCEM has also created two custom tools to facilitateautomated VC Profile Failover.For automatic event handling to work, the following prerequisites must be met:

• VCEM 1.40 has been installed as part of a HP SIM installation

• DNS is properly configured in the environment

• The Administrator account is usable on the system in which VCEM and SIM reside

The custom tools enable an administrator to initiate a VC Profile Failover. Any administrator that can run allthe tools on HP SIM or VCEM installation can perform a failover. The two custom tools can be deleted fromthe HP SIM or VCEM installation with no impact other than the inability to configure automatic event handling.

IMPORTANT: Enabling automated failover actions can have implications in a data center. Before completingthis task, review any automatic event handlers. Unintended failovers can result in the loss of data andunnecessary system downtime.

To set up automated VC Profile Failover, complete the following steps:1. Enable HP SIM automatic discovery by selecting Options→Discovery. Discovery must be enabled to

discover servers within the environment.2. Enable active event handling by selecting Options→Events→Automatic Event Handling→New

Task. This step launches a wizard to aid in the creation of a task.3. Use the wizard to select a name for the event handler.4. To monitor the selected CPU and memory-related failures, select the Profile Failover Trigger Events

event collection.5. Select the systems that the event handler must monitor. You can select specific systems or a collection

of systems.6. Step 4 of the wizard enables you to choose what actions the event handler must if one of the selected

systems generates an event. Select Run custom CMS tool, and then select VCEM Profile Failoverby Hostname.

7. If there is a specific time the event handler must be active, choose a time filter.8. Review the selected events, systems, and actions for the automatic event handler.VC Profile Failovers will now occur whenever any of the designated systems generate one of the eventswithin the event collection. When an event triggers a VC Profile Failover, a VCEM Failover job appears tohave originated from the administrator user account and will failover the system which generated the event.For more information about VC Profile Failover, see the failover white paper at http://www.hp.com/go/vcem.For more information about Automatic Event Handling, see the HP SIM User Guide athttp://www.hp.com/go/hpsim.

Bays 67

Page 68: Virtual Connect

68

Page 69: Virtual Connect

7 Managing MAC and WWN addressesThis section describes how to manage MAC and WWN addresses using VCEM.

MAC Addresses

NOTE: In VCEM 1.40 and later, a new “VCEM-defined” range has been reserved, from which VCEMallocates MAC addresses. VCEM no longer uses the “HP Pre-defined” range for MAC address allocation.However, profiles created before VCEM 1.40 will continue to use the HP Pre-defined addresses alreadyassigned to them.

When using VCEM-assigned MAC addresses, you can choose between VCEM-defined MAC address rangesor user-defined MAC address ranges. You can use the HP pre-defined MAC address range only for importprofiles or profiles created on previous versions of VCEM.

• VCEM-defined MAC address ranges—HP recommends this range. This predefined range is reservedand never appears as factory-default on any hardware. There are 131,072 unique addresses fromwhich VCEM automatically assigns to profiles on demand.

• User-defined MAC address range—To prevent potential conflict with other hardware MAC addressesin the environment, you can use a subrange of MAC addresses reserved by the IEEE for locallyadministered MAC addresses. Ensure that the range does not conflict with any Ethernet device alreadydeployed within the enterprise.

To access the MAC addresses from the VCEM home page, click the MAC addresses hyperlink. The MACRanges List page appears.

Figure 7-1 MAC Ranges List page

Tracking individual MAC addressesIndividual addresses in a MAC range (HP-predefined, VCEM-defined, or user-defined) can be monitored byclicking the Individual addresses secondary tab within the MAC Ranges List page.

MAC Addresses 69

Page 70: Virtual Connect

The following table lists and describes the MAC address status at Individual address page.

DescriptionItem

Address available to use in VCEM.Free

Address currently used by a server profile in VCEM.In use

Addresses used by server profiles in a VC Domain that have beenreleased back to Virtual Connect Manager and no longermanaged by VCEM.

External Address

Addresses that reside in a VCEM Exclusion range list. VCEM willnot allocate any address that is marked as excluded.

Excluded Addresses

Creating MAC exclusion rangesVCEM requires that you define exclusion ranges for both MAC and WWN address ranges that are in useby VC Domains outside VCEM management. Exclusion ranges are used to set aside addresses that mightbe in use for other purposes within your data center. Excluded address ranges are not assigned for use byVCEM.1. From the VCEM home page, under the Administration heading, click the MAC addresses hyperlink.2. From the Select ranges to configure list, select MAC.3. Select a MAC address range. The exclusion range must be contained within the address range to which

the exclusion range belongs.4. Select the Exclusion ranges tab.5. To create the exclusion range, click New.

IMPORTANT: External addresses that are included in a MAC exclusion range remain external addresses.The status of an external address does not change if it is included in a MAC exclusion range.

6. Select a HP-predefined address range, or manually enter the address range to exclude.

Deleting MAC exclusion ranges1. From the VCEM home page, under the Administration heading, click the MAC addresses hyperlink.2. From the Select ranges to configure list, select MAC.3. Select a MAC address range. The exclusion range must be contained within the address range to which

the exclusion range belongs.4. Select a MAC exclusion range.5. Click Delete. You are prompted to confirm your choice.6. Click OK.

IMPORTANT: If the exclusion range includes external addresses, these external addresses remain external,even if the exclusion range is removed.To avoid conflicts, make sure all addresses within this range are not being used by any other Ethernet deviceon your network.

Reclaiming external MAC addressesExternal MAC addresses are generated when a VC Domain containing server profiles is removed from aVC Domain Group. Since every profile contains one or more MAC addresses associated with it, VCEMidentifies these addresses as external. Addresses identified as external are reserved for VC Domains outsideof VCEM and will not be used by VCEM.To change the status of an address from External to Free, use the Reclaim External button. Before freeing anaddress, verify that the address is no longer used by a VC Domain outside of VCEM.To reclaim MAC addresses:1. From the VCEM home page, under the Administration heading, click the MAC addresses hyperlink.2. From the Select ranges to configure list, select MAC.

70 Managing MAC and WWN addresses

Page 71: Virtual Connect

3. Select a MAC address range.4. Select the Individual addresses tab.5. From the Filter list, select External.6. Select the external addresses to be reclaimed.7. Click Reclaim External. You are prompted to confirm your choices.8. Click OK.

Adding custom MAC address rangesBecause the maximum range size is 131,072, a large range might take a few minutes to create. You cancreate one custom range.To add custom MAC address ranges:1. From the VCEM home page, under the Administration heading, click the MAC addresses hyperlink.2. From the Select ranges to configure list, select MAC.3. Click Add custom. The Add Custom MAC Address Range information appears.4. Enter custom MAC address range.5. Click OK.

Editing custom MAC address rangesBecause the maximum range size is 131,072, a large range might take a few minutes to edit. If you arereducing the size of a custom range, verify that any addresses or exclusion ranges already in use are notoutside the edited range.To edit custom MAC address ranges:1. From the VCEM home page, under the Administration heading, click the MAC addresses hyperlink

under the Administration heading.2. From the Select ranges to configure list, select MAC.3. Select the custom MAC address range.4. Click Edit.5. Edit the custom MAC address range as necessary.6. Click OK.

Removing custom MAC address ranges

NOTE: Removing a custom MAC address range also removes its defined exclusion ranges.

You must verify there are no addresses already in use for this range. To remove custom MAC address ranges:1. From the Virtual Connect Enterprise Manager home page, under the Administration heading, click the

MAC addresses hyperlink.2. From the Select ranges to configure list, select MAC.3. Select the custom MAC address range.4. Click Delete. You are prompted to confirm your choice.5. Click OK.

WWN Addresses

NOTE: In VCEM 1.40 and later, a new “VCEM-defined” range has been reserved, from which VCEMallocates WWN addresses. VCEM no longer uses the “HP Pre-defined” range for WWN address allocation.However, profiles created before VCEM 1.40 will continue to use the HP Pre-defined addresses alreadyassigned to them.

The WWN range used by the VCEM domain must be unique within the environment. HP provides a set ofpredefined addresses that is reserved for Virtual Connect and VCEM and does not conflict with serverfactory-default WWNs.

WWN Addresses 71

Page 72: Virtual Connect

Overall, WWN range management in VCEM is very similar to MAC ranges. VCEM allocates WWNsautomatically according to VC Domain Group configuration using HP-predefined, VCEM-defined, oruser-defined WWNs. You can use the HP-predefined range only for import profiles or profiles created onprevious versions of VCEM.To access WWN addresses from the VCEM home page, click the World Wide Names hyperlink. The WWNRanges List page appears.

Figure 7-2 WWN Ranges List page

Tracking individual WWN addressesIndividual addresses in a WWN range (HP-predefined, VCEM-defined, or user-defined) can be monitoredby clicking on the Individual addresses secondary tab within the WWN Ranges List page.The following table lists and describes the WWN address status at Individual address page.

DescriptionItem

Address available to use in VCEM.Free

Address currently used by a server profile in VCEM.In use

Addresses used by server profiles in a VC Domain that has beenreleased back to Virtual Connect Manager and no longermanaged by VCEM.

External Address

Addresses that reside in a VCEM Exclusion range list. VCEM willnot allocate any address that is marked as excluded.

Excluded Addresses

Creating WWN exclusion rangesVCEM requires that you define exclusion ranges for both MAC and WWN address ranges that are in useby VC Domains outside VCEM management. Exclusion ranges are used to set aside addresses that mightbe in use for other purposes within your data center. Excluded address ranges are not assigned for use byVCEM.

72 Managing MAC and WWN addresses

Page 73: Virtual Connect

1. From the VCEM home page, under the Administration heading, click the World Wide Names hyperlink.2. From the Select ranges to configure list, select WWN.3. Select a WWN address range. The exclusion range must be contained within the address range to

which the exclusion range belongs.4. Select the Exclusion ranges tab.5. To create the exclusion range, click New.

IMPORTANT: External addresses that are included in a WWN exclusion range remain externaladdresses. The status of an external address does not change if it is included in a WWN exclusionrange.

6. Select a HP-predefined address range, or manually enter the address range to exclude.

Deleting WWN exclusion ranges1. From the VCEM home page, under the Administration heading, click the World Wide Names hyperlink.2. From the Select ranges to configure list, select WWN.3. Select a WWN address range. The exclusion range must be contained within the address range to

which the exclusion range belongs.4. Click Delete. You are prompted to confirm your choice.

IMPORTANT: If the exclusion range includes external addresses, these external addresses remainexternal, even if the exclusion range is removed.To avoid conflicts, ensure all addresses within this range are not being used by any other Fibre Channeldevice on your network.

Allocating WWN addressesExclusion ranges are used to set aside addresses that might be in use for other purposes within your datacenter. Excluded address ranges are not assigned for use by VCEM.To allocate WWN addresses:1. From the VCEM home page, under the Administration heading, click the World Wide Names hyperlink.2. From the Select ranges to configure list, select WWN. The WWN Ranges List page appears.

WWN Addresses 73

Page 74: Virtual Connect

Figure 7-3 WWN Ranges List page

3. Select a WWN address range. The exclusion range must be contained within the address range towhich the exclusion range belongs. Valid WWN ranges cannot contain all 0s or all Fs and cannot havean F within either of the first two octets.

4. Click the Exclusion ranges tab.5. To create the exclusion range, click New.

Reclaiming external WWN addressesExternal WWN addresses are generated when a VC Domain containing server profiles is removed from aVC Domain Group. Because every profile contains one or more WWN addresses associated with it, VCEMidentifies these addresses as external. Addresses identified as external are reserved for VC Domains outsideof VCEM and will not be used by VCEM.To change the status of an address from External to Free, use the Reclaim External button. Before freeing anaddress, verify that the address is no longer used by a VC Domain outside of VCEM.To reclaim WWN addresses:1. From the Virtual Connect Enterprise Manager home page, under the Administration heading, click the

World Wide Names hyperlink.2. From the Select ranges to configure link, select WWN. The WWN Ranges List page appears.3. Select a WWN address range.4. Click the Individual addresses tab.5. From the Filter link, select External.6. Select the external addresses.7. Click Reclaim External. You are prompted to confirm your choices.8. Click OK.

Adding custom WWN address rangesBecause the maximum range size is 131,072, a large range might take a few minutes to create. You cancreate one custom range.

74 Managing MAC and WWN addresses

Page 75: Virtual Connect

To add WWN custom address ranges:1. From the Virtual Connect Enterprise Manager home page, under the Administration heading, click the

World Wide Names hyperlink.2. From the Select ranges to configure link, select WWN.3. Click Add custom. The Add Custom WWN Address Range information appears.4. Enter the custom WWN address range.5. Click OK.

Editing custom WWN address rangesBecause the maximum range size is 131,072, a large range might take a few minutes to edit. You cancreate one custom range.1. From the VCEM home page, under the Administration heading, click the World Wide Names hyperlink.2. From the Select ranges to configure link, select WWN.3. Select a WWN address range.4. Click Edit.5. Edit the WWN address range as necessary. Valid WWN ranges cannot contain all 0s or all Fs and

cannot have an F within either of the first two octets.6. Click OK.

Deleting custom WWN address ranges

NOTE: Removing a custom WWN address range also removes its defined exclusion ranges.

1. From the Select ranges to configure link, select WWN.2. Select the custom WWN range.3. Click Delete. You are prompted to confirm your choice.4. Click OK.

WWN Addresses 75

Page 76: Virtual Connect

76

Page 77: Virtual Connect

8 Working with Logical Serial NumbersLogical Serial Numbers

This section describes how to view logical serial numbers that exist in server profiles being managed byVCEM. These numbers are displayed for informational purposes.Logical serial numbers move with a server profile. The virtual serial number is a 10-character string.

NOTE: For informational purposes, logical serial numbers start with three characters of eitherVCXNNNNNNN or VCYNNNNNNN where VCX indicates that the logical serial number was created byVirtual Connect Manager before having a VC Domain imported into VCEM. A logical serial number prefacedby VCY indicates that the logical serial number was created by VCEM when it created a server profile.

From the VCEM home page, click the Logical Serial Numbers hyperlink. The logical serial number pageappears.

Figure 8-1 Logical serial number page

Identifying logical serial number valuesThe following table lists and describes the logical serial number status values.

DescriptionItem

Logical serial number is currently used by a server profile in VCEM.In use

Logical serial numbers used by server profiles in a VC Domainthat has been released back to Virtual Connect Manager and isno longer managed by VCEM.

External

Logical Serial Numbers 77

Page 78: Virtual Connect

78

Page 79: Virtual Connect

9 Tracking VCEM job statusJobs

The Jobs list provides detailed information about jobs that have occurred and are related to VCEM. To viewthese jobs, click the Jobs tab. The Jobs list appears. From this list, you can perform the following tasks:

• Review a summary of jobs

• Select and review details of jobs

• Select and delete jobs

Figure 9-1 Jobs list

The following table lists and describes the job item columns in the Jobs list.

DescriptionItem

Identifies the job number with the task performedJob ID

Describes the job performed or to be performedTask

Provides job statusStatus

Describes the progress of the current jobProgress

Identifies the person who performed the function that created thejob

User Name

Identifies job start timeStart Time

Identifies the time when the job was completed (if the job is notcomplete, this field is blank)

End Time

Job status message windowWhen a function is performed, a job is created. A message window appears displaying the Job ID.Details of the job can be viewed in the Jobs tab. When jobs are created, events might also be created inHP SIM.

Jobs 79

Page 80: Virtual Connect

VCEM limits the number of jobs that it displays to 65,000. If the limit is reached, then only the most recent65,000 jobs are viewable. To keep the list smaller, you can select the jobs to be deleted, and then clickDelete.

Reviewing job detailsTo review the details of a particular job, click the hyperlink of the appropriate job name. The Job Detailswindow appears.

Deleting jobsTo delete a particular job or multiple jobs, click Delete. Only pending, failed, or completed jobs can bedeleted. You cannot delete a running job.

80 Tracking VCEM job status

Page 81: Virtual Connect

10 Upgrading Virtual Connect firmware after VCEM ismanaging VC Domains

The process for upgrading Virtual Connect (VC) firmware requires extra steps when VCEM is managing theVC Domain. VCEM gains exclusive access to managed domains. However, using the VC Domain Maintenancecapability, the Virtual Connect Manager can be used to upgrade VC firmware while the VC Domain is beingmanaged by VCEM.

Preparation checklistBefore upgrading VC firmware, you must ensure that the installed version of VCEM supports the VC firmwareupgrade. See the HP Insight Control Environment Support Matrix at http://www.hp.com/go/vcem.The VC firmware version might require installation of a VCEM Firmware Support Update or new version ofVCEM. Ensure the following requirements have been met:1. Download and install the VCEM Firmware Support Update or a new VCEM version that supports

VC firmware.2. Acquire the HP BladeSystem c-Class Virtual Connect Firmware. You can download the firmware from

http://www.hp.com. Firmware installation instructions are included with the download.3. Determine whether any other components must be updated before upgrading the VC firmware by

reviewing the Virtual Connect firmware documentation and. The VC firmware might have dependencieson specific versions of the following items:

• HP BladeSystem c-Class Onboard Administrator

• HP ProLiant c-Class Server BIOS – System ROM

• HP Integrity c-Class Server EFI

• HP c-Class Embedded NICs

• HP c-Class Server Mezzanine Cards

• HP Integrated Lights-Out 2 (iLO 2)

Performing the firmware update using the VC Domain Maintenancecapability

1. From the VC Domains screen, select a VC Domain.2. Click VC Domain Maintenance.3. Click Make changes via VC Domain. Virtual Connect Manager appears in a separate browser window.

The VC Domain Maintenance information indicates that the VC Domain is unlocked for domain, network,and storage changes.

4. Using Virtual Connect Manager, log in with full user rights at VC Manager and upgrade the firmware.When the firmware upgrade is complete, close the VC Manager browser.

5. Return to the VC Domain Maintenance page in VCEM.6. To apply the changes, click Complete VC Domain Maintenance. The Virtual Connect

Enterprise Manager is executing the request message appears with a job ID code.7. Click OK to go to the Jobs page and monitor job progress.

Preparation checklist 81

Page 82: Virtual Connect

82

Page 83: Virtual Connect

11 Removing an external manager accountFor VCEM to manage VC Domains (using the Virtual Connect Manager, the embedded software in a VirtualConnect Ethernet module) VCEM uses programmatic interfaces with each Virtual Connect Manager. VCEMautomatically creates an external manager account in each Virtual Connect Manager for subsequentauthentication.

NOTE: VCEM uses a Secure Sockets Layer (SSL) connection provided by HP SIM. For more informationabout the available cipher suites and how to enable or disable them, see the Understanding HP SIM securitywhite paper at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.

VCEM creates a local account on each Virtual Connect Manager it manages. To prevent inadvertentmodification, this account is not visible from the user-interface on the Virtual Connect Manager associatedwith the VC Domain being managed by VCEM. This account has full privileges to the Virtual ConnectManager and the credentials are used for SOAP interfaces with the Virtual Connect Manager, using aconnection over Secure Sockets Layer (SSL). These credentials are securely stored on the Central ManagementServer (CMS) used to run VCEM. Each Virtual Connect Manager managed by VCEM has a unique, randomlygenerated password.Removing the external manager account removes Virtual Connect Manager from VCEM control. Removethe account using the following methods:

• Preferred method—Uses the VCEM user-interface and removes the account from the Virtual ConnectManager and the credential store from VCEM.

• Remove the VC Domain from the VC Domain Group

• Secondary method—Uses the Virtual Connect Manager command line interface to remove the accountfrom the Virtual Connect Manager.If the preferred method is not possible, then the Virtual Connect Manager supports command lineinterfaces that allow the external manager account to be deleted from the Virtual Connect Managerand allow a Virtual Connect Manager to be removed from VCEM control.To remove the external manager account:1. Telnet in to the Virtual Connect Manager using an SSH connection such as SSH

[email protected], where xxx is the VC Domain IP address.2. To determine the username of the external manager account, from the Virtual Connect Manager

command prompt, enter show external-manager. For this example, assume the usernamereturned was xyz.

3. To disable the account, from the Virtual Connect Manager command prompt, enterset external-manager Username=xyz Enabled=false

If VC Domain firmware is 2.0x, perform the following:

• To remove the account and release the VC Domain from VCEM control, from the VirtualConnect Manager command prompt, enterremove external-manager Username=xyzmactype=<Factory-Default/User-Defined> MacStart=<> MacEnd=<>wwnType=<Factory-Default/User-Defined> WwnStart=<> WwnEnd=<>serverIdType=<Factory-Default/User-Defined> serverIdStart=<>serverIdEnd=<>

NOTE: "-quiet" is an option to suppress user confirmation prompts. This option is useful for scriptingoperations. This option is available for VC firmware 2.0x for the disable account, remove the account,and release ranges commands.

For more information, see the HP Virtual Connect Manager Command Line Interface User Guide.

83

Page 84: Virtual Connect

84

Page 85: Virtual Connect

12 Command Line Interface usage in VCEMVCEM provides support for a command line interface (CLI) to perform several failover-related functions. Thesesame functions are also available in the VCEM GUI.

Perform VC profile failover on specified VC Domain bay serverThis CLI command initiates a VC profile failover operation. Options for specifying the source server as theVC profile failover target are:

• Specifying a VC Domain enclosure name and bay number as the source server>vcem –failover –bay “EnclosureName:BayNumber”

• Specifying a VC Domain bay server host name as the source server>vcem –failover –host “BayServerHostname”

• Specifying a VC Domain bay server IP address as the source server>vcem –failover –ip “BayServerIPAddress”

If the CLI Failover command for any of these three options is successful, the exit code from the CLI iszero, and the following example output displays (through stdout) on the screen. The CLI also displaysthe job number of the VCEM Failover job (represented by N below) that has just been initiated.

Performing VC Profile Failover on the specified VC Domain Bay Server...VC Profile Failover has been initiated: "EnclosureName:BayNumber"VCEM Failover Job Number is: NPerforming VC Profile Failover on the specified VC Domain Bay Server...VC Profile Failover has been initiated: "BayServerHostname"VC Profile Failover Job Number is: N

Performing VC Profile Failover on the specified VC Domain Bay Server...VC Profile Failover has been initiated: "BayServerIPAddress"VC Profile Failover Job Number is: N

If the CLI Failover command for any of these three options has failed, the exit code is some value greaterthan zero and the associated error message appears. The following shows some output examples.

Performing VC Profile Failover on the specified VC Domain Bay Server...ERROR (30) - Could not initiate VC Profile FailoverInternal VCEM Error Code: 5013Internal VCEM Error Message: Specified server bay number is out of range, it must be between 1 – 16.

Performing VC Profile Failover on the specified VC Domain Bay Server...ERROR (30) - Could not initiate VC Profile FailoverInternal VCEM Error Code: 5058Internal VCEM Error Message: Enclosure name contains too many characters - limit is 32Performing VC Profile Failover on the specified VC Domain Bay Server...ERROR (30) - Could not initiate VC Profile FailoverInternal VCEM Error Code: 5009Internal VCEM Error Message: Invalid format for IP address - it must be: [0-255].[0-255].[0-255].[0-255]

List details for specified VCEM jobThis CLI command can be used to list the details and status for a particular VCEM job and can be used todetermine the status of a CLI failover job.

Perform VC profile failover on specified VC Domain bay server 85

Page 86: Virtual Connect

>vcem –list –details –job JobNumber

If the CLI List Job Details command is successful, the exit code from the CLI is zero, and the followingexample output appears (through stdout) on the screen.

>vcem –list –details –job 1Listing details for specified VCEM Job...

Job Number: 1Job Type: MDMJob State: COMPLETED

Job Progress: % Complete, Time, Possible Error Msg, Possible Detailed Error MsgJob Priority: 5Job User Name: “MachineUserNameHere”

Job Create Time: 1:58:34 PMJob Start Time: 1:58:34 PMJob End Time: 1:58:42 PM

In the preceding example, the job dtate status shows as completed. Valid values for this status are:

• Unknown

• Pending

• Running

• Completed

• Failed

• Canceled

If the CLI List Job Details command has failed, the exit code is some value greater than zero and theassociated error message appears. The following shows some output examples.

Listing details for specified VCEM Job...ERROR (63) - Specified VCEM Job Number is not an integer

Listing details for specified VCEM Job...ERROR (64) - Could not list details for jobInternal VCEM Error Code: 5014Internal VCEM Error Message: No Job is found. Verify that the specified Job ID must be bigger than 0 and valid.

Show CLI usage online helpThis CLI command can be used to display brief usage help on the screen.>vcem -help

Several CLI option keywords provide for abbreviated alternatives – that is, {-failover | -fo}.

VCEM (Virtual Connect Enterprise Manager) CLI Usage:- Perform VC Profile Failover on specified VC Domain Bay Server>vcem {-failover | -fo} {-bay "EnclosureName:BayNumber" | -host "BayServerHostName" | -ip "BayServerIPAddress"}

- Listing details for specified VCEM Job>vcem {-list | -ls} {-details | -dt} -job "jobNumber"

- Show CLI Help>vcem {-help | -h}

86 Command Line Interface usage in VCEM

Page 87: Virtual Connect

CLI exit and error codesThe CLI returns a numeric value that either indicates success or a particular error or failure. The CLI alsodisplays an associated error message (through stdout). A zero numerical returned value indicates success.Some returned value greater than zero indicates an error or failure. The following list shows all possible exitand error codes and messages that might be returned by the VCEM CLI.VCEM CLI syntax error codes/messages

Error messageCode

ERROR–Invalid command line syntax1

ERROR–Invalid command line option2

ERROR–Argument not allowed for this option3

ERROR–Only one required argument allowed for this option4

ERROR–Missing a required argument for this option5

ERROR–Missing operational option6

ERROR–Missing command line option(s)7

ERROR–Invalid command line argument8

ERROR–Duplicate options not allowed9

ERROR–Option not allowed10

VCEM CLI User Authorization and Login error codes/messages

Error MessageCode

ERROR–Could not locate VCEM SOAP Service15

ERROR–Could not login to VCEM- SIM must be running- VCEM must be installed- User must be in OS Administrator group- User must be valid SIM user- User must have adequate VCEM authorization

16

CLI exit and error codes 87

Page 88: Virtual Connect

88

Page 89: Virtual Connect

13 Troubleshooting VCEMTroubleshootingUnauthorized error when trying to access the VCEM home page

VCEM requires the CMS to be correctly registered in the DNS. Make sure HP SIM can correctly discoverthe CMS. You might experience an unauthorized error page when trying to access the VCEM home pageif the CMS is incorrectly registered in the DNS.To correct this issue, register the CMS in DNS or add the CMS hostname to the Windows hosts file.

A job appears with Failed statusA job might fail for several reasons. For more information about the reason of job failure and how to correctthe issue, see the job details:1. From the VCEM home page, click the Jobs tab.2. Locate the job, either by its ID or its name.3. For detailed information about the job and how you can resolve the issue, click the task name of this

job.4. (Optional) Job details might appear to be truncated when the appended exceeds 256 characters. If

this occurs, to view the full job details, go to HP SIM left navigation panel→Events→Shared→VCEMEvents.

Enclosure has two Onboard Administrators, and one failsIf an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant OnboardAdministrator might take several minutes to take over. Before performing any operations to the VC Domain,wait until the Onboard Administrator has failed over. Perform an HP SIM discovery to rediscover the newOnboard Administrator IP address. If it is not rediscovered then see the HP BladeSystem c-Class OnboardAdministrator User Guide.

VCEM is prompting for Onboard Administrator credentials on a configured VCDomain

VCEM might prompt for Onboard Administrator credentials on a VC Domain that has already been configuredwhere the Onboard Administrator has been imported and discovered. This issue occurs when a backup VCis discovered or if a failover of a VC Module occurred in a redundancy environment. To correct this issue,perform a rediscovery on the Onboard Administrator IP address associated with the VC Module.

Virtual Connect Manager does not accept Onboard Administrator credentialsIf a VC Domain is being managed by VCEM, and the Onboard Administrator is brought out of VirtualConnect Mode, the following error message appears the next time you log into Virtual Connect Manager:The HP Virtual Connect has lost its login credentials for the HP Onboardadministrator (OA). The OA may have been replaced or reset to factory defaults.To ensure proper operation, these credentials must be reestablished.

When Onboard Administrator credentials are provided, an error message appears stating that the credentialsare not valid. This situation can occur when:

• Onboard Administrator is replaced or reset to factory default settings.

• The clear vcmmode command was executed in the Onboard Administrator CLI.

• The VC Ethernet modules were temporarily replaced by another BladeSystem c-Class interconnectmodule.

To resolve this issue:1. Select the affected VC Domain, and put it into VC Domain Maintenance.2. Log in to Virtual Connect Manager. Wait to be prompted for new Onboard Administrator credentials.

Troubleshooting 89

Page 90: Virtual Connect

NOTE: You must have domain privileges to log in to Virtual Connect Manager.

3. Provide the Onboard Administrator credentials, and then follow the Virtual Connect Manager instructions.4. In Virtual Connect Manager, restart all servers with server profiles that present a Pending status.5. Verify that the servers are operating correctly.6. Access VCEM, and complete VC Domain Maintenance.

Unable to add VC Domain to a VC Domain GroupIf the VC Domain is not the same as the VC Domain configuration group, then you might not be able to addthe VC Domain to the VC Domain Group. To correct this issue, verify that the VC Domain meets therequirements for adding a VC Domain to a VC Domain Group. For more information, see Requirements foradding a VC Domain to a VC Domain Group.Also, a VC Domain might fail to add to the VC Domain Group for the following reasons:

• Network issues

• Invalid IP address

• Insufficient credentials permission

• Another VCEM external manager exists

To correct this issue:

• Verify that you can ping from the command line of the VCEM server and log in the Virtual ConnectManager using the browser.

• In a redundant environment, verify if the failover between an active and standby VC module occurs. Ifso, wait until the failover completes and then perform rediscovery of Onboard Administrator associatedto the VC module.

• VCEM requires Virtual Connect Manager credentials with full privileges to communicate to VirtualConnect Module.

• Access the Virtual Connect Manager CLI:Telnet in to the Virtual Connect Manager using an SSH connection such as [email protected], where xxx.xxx.xxx.xxx is the VC Domain IP address.

1.

2. To determine the username of the external manager account, enter show external-managerin the Virtual Connect Manager Command User Interface. The status of the external manager nameappears.

For more information, see the HP Virtual Connect Command Line Interface User Guide.

Unable to add an unconfigured VC Domain to a VC Domain GroupIf you are unable to add an unconfigured server to a VC Domain Group, verify that the VC Domain meetsthe requirements for adding a VC Domain to a VC Domain Group. For more information, see Requirementsfor adding a VC Domain to a VC Domain Group.

Cannot manage a VC Domain when VC module failover is taking placeVCEM cannot create a VC Domain Group or add a VC Domain to a VC Domain Group when a backupVC module is discovered or if a failover of a VC module occurred in a redundancy environment. The followingerror message appears:"The VC Domain [VC Domain Name] cannot be managed by VCEM. A possible causeis that the current state of the VC Domain is unknown. Verify HP Systems InsightManager (HP SIM) is referencing the primary VC Module. If not, run HP SIMdiscovery to update the reference."

To correct this issue, perform an HP SIM discovery on the Onboard Administrator IP address associated withthe VC module and perform the VCEM operation again.

90 Troubleshooting VCEM

Page 91: Virtual Connect

VC Domain displays Missing External Manager lock statusIf the VC Domain displays a status of Missing External Manager lock icon, the external manager lock haseither been suspended or removed.To correct this issue with a VC Domain, remove the VC Domain from VC Domain Group, break the externalmanager lock and release these MAC, WWN, and serial number address ranges as follows:1. Telnet in to the Virtual Connect Manager using an SSH connection such as SSH

[email protected], where xxx.xxx.xxx.xxx is the VC Domain IP address.2. To determine the username of the external manager account, from the Virtual Connect Manager command

prompt, enter show external-manager. For this example, assume the user name returned was xyz.3. To disable the account, from the Virtual Connect Manager command prompt, enter

set external-manager Username=xyz Enabled=false.

If VC Domain firmware is 2.0x or later, perform the following:• To remove the account and release the VC Domain from VCEM control, from the Virtual Connect Manager

command prompt, enterremove external-manager Username=xyz mactype=<Factory-Default/User-Defined>MacStart=<> MacEnd=<> wwnType=<Factory-Default/User-Defined> WwnStart=<>WwnEnd=<> serverIdType=<Factory-Default/User-Defined> serverIdStart=<>serverIdEnd=<>

NOTE: “-quiet” is an option to suppress user confirmation prompts. This option is useful for scriptingoperations. This option is available for VC firmware 2.0x or later for the disable account, remove theaccount, and release ranges commands.

For more information, see the HP Virtual Connect Manager Command Line Interface User Guide.

VC Domain displays Configuration Mismatch statusIf the VCEM data does not match the data from the VC Domain, then the Configuration Mismatch iconappears. This might happen when either the user suspends the external manager lock and then modifies theVC Domain, or adds or removes VC Modules from rear-enclosure interconnect bays.To correct this issue, see Resynchronizing a VC Domain with Configuration Mismatch.

VC Domain displays Connectivity failure statusThe Connectivity failure icon might appear if any of the following occur:

• Connection timeout, network problems, Virtual Connect Ethernet Modules physically not available, orenclosure problem

• Virtual Connect Manager failover

• VC Domain firmware update

• Virtual Connect Ethernet Module IP address change.

To correct this issue, perform any of the following:

• Ethernet VC modules are not physically available anymore or there is a connection timeout or networkproblems between VCEM and VC Ethernet modules.To correct this issue, verify the Ethernet VC Modules are still available and that there are nonetwork-related issues with the Virtual Connect Manager. From the command line at the VCEM server,ping the VC Domain IP.For information on enclosure problems, see Enclosure has a hardware failure and must be replaced.

• In a redundant environment, the failover between active and standby Virtual Connect module is takingplace.To correct this issue:

Troubleshooting 91

Page 92: Virtual Connect

1. Verify that the failover between the active and standby Virtual Connect module is taking place.2. Wait a few minutes until the failover completes, and then try again.3. Log into the Virtual Connect Manager (https://<VCDomain_IP>). A status of Active Virtual Connect

Manager not at this IP address might appear.4. You must also rediscover the Onboard Administrator related to this VC Domain again by selecting

HP SIM menu Options→Identify System or Options→Discovery.

• Verify firmware update is in progress and wait a few minutes until update is completed.Log into the Virtual Connect Manager (https://<VCDomain_IP>), and then to verify the VC Domainfirmware status, click Domain Settings→Firmware Management.

• Run an HP SIM discovery to idenfity the new VC Domain IP address and perform the operation again.If you perform an operation that changes the VC Domain status to Connectivity failure, VCEM will checkthe connectivity using the information from HP SIM nodes after the operation completes.

• Remove the VC Domain from VC Domain Group, and run the HP SIM discovery task to identify the newVC Domain IP address.Break the external manager lock, and then release these MAC and WWN address ranges as follows:1. Telnet in to the Virtual Connect Manager using an SSH connection such as SSH

[email protected], where xxx.xxx.xxx.xxx is the VC Domain IP address.2. To determine the username of the external manager account, from the Virtual Connect Manager

command prompt, enter show external-manager. For this example, assume the usernamereturned was xyz.

3. To disable the account, from the Virtual Connect Manager command prompt, enter setexternal-manager Username=xyz Enabled=false.

If VC Domain firmware is 2.0x or later, perform the following:• To remove the account and release the VC Domain from VCEM control, from the Virtual Connect

Manager command prompt, enter:remove external-manager Username=xyzmactype=<Factory-Default/User-Defined> MacStart=<> MacEnd=<>wwnType=<Factory-Default/User-Defined> WwnStart=<> WwnEnd=<>serverIdType=<Factory-Default/User-Defined> serverIdStart=<>serverIdEnd=<>

NOTE: “-quiet” is an option to suppress user confirmation prompts. This option is useful forscripting operations. This option is available for VC firmware 2.0x or later for the disable account,remove the account, and release ranges commands.

Operation fails to perform in the VC Domain or VC Domain Group under maintenancestatus

VCEM cannot perform any operations related to VC Domains in a VC Domain Group that have the UnderMaintenance icon because of any of the following:

• Maintenance process has not completed by clicking Complete VC Domain Maintenance or Cancel

• Maintenance job is still running.

• Maintenance job fails.

To resolve this issue:

92 Troubleshooting VCEM

Page 93: Virtual Connect

1. Click the VC Domains or VC Domain Groups tab.a. Select the VC Domain or VC Domain Groupb. Click VC Domain Maintenance.c. Click Complete VC Domain Maintenance or Cancel.

2. Verify the VC Domain Maintenance job is running. If so, wait until the job completes.3. Review the job error details and fix the problem with the VC Domain.

a. To complete VC Domain Maintenance, click VC Domain Maintenance, or to revert back to theoriginal VC Domain configuration, click Cancel.

b. Wait until the VC Domain Maintenance job has completed successfully. If the Cancel VC DomainMaintenance job fails, then remove the VC Domain from the VC Domain Group.

For more information, see Removing a VC Domain from a VC Domain Group

Remove from VC Domain Group job is successful but with errorsOccasionally, when successfully performing a remove from VC Domain Group job, an error might appearin the job detail. The error is related to VCEM being unable to:

• Release control over the MAC and WWN address pools, or serial number range.

• Remove external manager.

To correct the issue related to removal of external manager or unable to release control of MAC, WWN,and serial number ranges, perform the following:1. Telnet in to the Virtual Connect Manager using an SSH connection such as

SSH [email protected], where xxx.xxx.xxx.xxx is the VC Domain IP address.2. To determine the username of the external manager account, from the Virtual Connect Manager command

prompt, enter show external-manager. For this example, assume the username returned was xyz.3. To disable the account, from the Virtual Connect Manager command prompt, enter

set external-manager Username=xyz Enabled=false.

If VC firmware is 2.0x, perform the following:• To remove the account and release the VC Domain from VCEM control, from the Virtual Connect Manager

command prompt, enterremove external-manager Username=xyz mactype=<Factory-Default/User-Defined>MacStart=<> MacEnd=<> wwnType=<Factory-Default/User-Defined> WwnStart=<>WwnEnd=<> serverIdType=<Factory-Default/User-Defined> serverIdStart=<>serverIdEnd=<>

NOTE: “-quiet” is an option to suppress user confirmation prompts. This option is useful for scriptingoperations. This option is available for VC firmware 2.0x for the disable account, remove the account,and release ranges commands.

VC Domain displays Expired License statusIf a VC Domain has an Expired License icon, perform the following:1. License the enclosure with a Flexible Quantity License (FQL) VCEM license. For information on purchasing

licenses, see the VCEM QuickSpecs at http://www.hp.com/go/vcem.2. Click the VC Domain tab.3. Select the VC Domain, and then click License.4. Click Add Key.5. Enter a valid FQL license key, and then click OK.6. Click Apply License.7. Perform the failed operation again.

Troubleshooting 93

Page 94: Virtual Connect

Error on database operation occursErrors might occur during database operations if:

• VCEM tables are missing; that is, Database Administrator deleted some VCEM tables.

• HP SIM database is not running.

To resolve this issue:1. If VCEM tables are missing, then you must restore the VCEM database backup. For more information,

see Backing up and restoring VCEM.2. Check the HP SIM database server status:

• If the database server is remote, then log in to the database server.

• In Windows taskbar, check if the Microsoft SQL or MSDE service is running. A red status meansthey are not running.

• Right-click the status, and then select Start.

3. If this issue still occurs, then uninstall and install VCEM again.

Errors occur while loading VCEM pagesIf errors occur while loading VCEM pages, then the HP SIM service is most likely down. To resolve this issue:1. Check if HP SIM service is up and running.2. Select Start→Control Panel→Administrative Tools→Services.3. Check the HP SIM service status.4. If the service is not running, right-click, and then select Start.

Failed to execute VCEM operation because VC firmware not supportedIf the VC firmware version you have is not supported, then VCEM operations might fail to execute. For moreinformation about supported Virtual Connect firmware, see http://www.hp.com/go/vcem.To correct this issue, related to the VC firmware version not supported, perform the following steps andexecute the VCEM operation again:• Update VC firmware according VC firmware versions supported by VCEM using the Virtual Connect

Manager user interface.a. Access the Virtual Connect Manager user interface.b. Using the VC Domain account with full credentials, log in to the VC Domain.c. From the left panel, click Managing Firmware, click Upload, and then enter the firmware file.d. Click Activate.

To correct this issue, if VC Domain is under VCEM management, you can either:

• Remove the VC Domain from VC Domain group. For more information, see Removing a VC Domainfrom a VC Domain Group

• If VC Domain is not under maintenance status, then enable VC Domain Maintenance and update theVC firmware version according VC firmware supported by VCEM.1. Access the Virtual Connect Manager user interface.2. Using the VC Domain account with full credentials, log in to the VC Domain.3. From the left panel, click Managing Firmware, click Upload, and then enter the firmware file.4. Click Activate.5. In VCEM, add the VC Domain to the VC Domain Group. If the VC Domain is already under VCEM

management then return to VC Domain Maintenance page and complete VC Domain Maintenance.For more information, see VC Domain Maintenance

94 Troubleshooting VCEM

Page 95: Virtual Connect

Creating a server profile or adding a VC Domain to a VC Domain Group failsAttempting to create a profile or adding a VC Domain to a VC Domain Group might fail if any of the followingoccur:

• VCEM does not have enough free MAC or WWN addresses.

• Some MAC or WWN addresses are already being used by another server profile.

• The MAC or WWN addresses in use by the VC Domain are not defined as custom ranges in VCEM.

To resolve this issue:1. Verify VCEM has enough free MAC and WWN addresses.2. Verify there are no MAC or WWN address conflicts for the VC Domain to be added to the VC Domain

Group.3. Create MAC and WWN custom ranges, and then verify that the ranges contain the MAC and WWN

addresses from the server profiles defined in the VC Domain to be managed by VCEM.4. Perform the operation again.

Uninstalling VCEMIf there is one or more VC Domains that are being managed, then VCEM uninstall does not proceed. In thiscase, the VCEM uninstaller fails and a button appears in HP Insight Software. You can click the button toopen an error log that instructs you of the corrective action to take.To uninstall VCEM:

• Select Start→All Programs→Insight Software→Uninstall HP Insight Software.

NOTE: Depending on your operating system, the following menu options might slightly vary.

• From the Control Panel:Double-click Add or Remove Programs.1.

2. Click Insight Software.3. Click Remove.

IMPORTANT: The uninstall operation does not remove a VCEM folder from installation directory, suchas C:\Program Files\HP\Virtual Connect Enterprise Manager\. The folder is empty and no systemdamage or inability to reinstall or upgrade VCEM again in the future occurs.

Backing up and restoring VCEMIn the event of catastrophic and complete VCEM failure, all server blades continue to operate, and theintegrity of the server application and data are not compromised.VCEM can be restored to an operational state after complete loss of the VCEM Application or Database.While it is possible to restore VCEM to its state before the loss, minor or major configuration loss mightoccur, depending on the availability of a database backup. If no database backup is available, then a largeamount of information can be reconstructed from the contents of the Virtual Connect modules.It is important that you understand what information is stored in the database, and can be lost without properbackup practices.

Troubleshooting 95

Page 96: Virtual Connect

Figure 13-1 Backing up and restoring VCEM

The Domain Network and SAN Configuration and assigned Server Profiles can be recovered from the VirtualConnect modules. The VC Domain Group definitions, MAC and WWN custom ranges, and MAC andWWN address exclusions are stored only on the Management Server.For more information on performing backups and restoring VCEM, see “Backing up and restoring HP SystemsInsight Manager 5.3 data files in a Windows environment” at the HP SIM Information Library at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.

Cannot change the MAC/WWN/Serial Number ranges in Virtual Connect Managerwhen there are server profiles

After removing the VC Domain from a VC Domain Group, you might not be able to modify the MAC, WWN,or Serial Number ranges in Virtual Connect Manager even after removing all server profiles from the VCDomain. This situation occurs because the MAC, WWN, and Serial Number ranges you entered whenreleasing the VC Domain from VCEM have addresses externally in use by server profiles under VCEM control.To correct the issue, reset the Virtual Connect Module, and make sure you enter MAC and WWN rangesdefined as exclusion ranges in VCEM. From the Virtual Connect Manager user interface, select Tools→ResetVirtual Connect Manager.

VCEM database is inaccessible or irretrievable with no backup, or VCEM file systemsare corrupt with no backup

Without a backup, the VCEM cannot restore to the original point. But the network and SAN configurationand assigned server profiles can be recovered from the Virtual Connect modules. Reinstall the VCEM to afresh system, ensuring that the backup is well prepared on VCEM and its database on the new VCEM. Formore information, see Backing up and restoring VCEM.To resolve this issue:1. Install VCEM 1.20 in a fresh machine.2. Break the external manager lock in all VC Domains that were previously managed by VCEM 1.20. To

remove the external manager account:a. Telnet in to the Virtual Connect Manager using an SSH connection such as

SSH [email protected], where xxx.xxx.xxx.xxx is the VC Domain IP address.b. To determine the username of the external manager account, from the Virtual Connect Manager

command prompt, enter show external-manager. For this example, assume the user namereturned was xyz.

c. To disable the account, from the Virtual Connect Manager command prompt, enterset external-manager Username=xyz Enabled=false.

1. To remove the account and release the VC Domain from VCEM control, from the Virtual Connect Managercommand prompt, enterremove external-manager Username=xyz mactype=<Factory-Default/User-Defined>MacStart=<> MacEnd=<> wwnType=<Factory-Default/User-Defined> WwnStart=<>

96 Troubleshooting VCEM

Page 97: Virtual Connect

WwnEnd=<> serverIdType=<Factory-Default/User-Defined> serverIdStart=<>serverIdEnd=<>

NOTE: “-quiet” is an option to suppress user confirmation prompts. This option is useful for scriptingoperations. This option is available for VC firmware 1.3x and later for the disable account, remove theaccount, and release ranges commands.

2. In HP SIM, perform a new discovery.3. Add the same VCEM license keys you were using previously and license the VC Domains with the same

key.

NOTE: If the previous configuration used custom MAC, WWN, and Serial Number ranges, then addthe same ranges to the new setup before proceeding.

4. Create new VC Domain Groups mirroring the prefail configuration informing the currently workingcredentials.

NOTE: Unassigned server profiles, external MAC and WWN addresses, and serial numbers are notrecovered with this procedure.

Enclosure has a hardware failure and must be replacedAn enclosure that is being managed by VCEM indicates a hardware failure that requires replacement.When a Virtual Connect Ethernet Module is removed from an enclosure and placed in another, its settingsare automatically cleared and all domain configuration is lost, including any existing server profiles.To resolve this issue:1. From the VCEM home page, click the VC Domains tab.2. Select the VC Domain that has an enclosure problem.3. Click Remove from VC Domain Group. Wait for the job to complete successfully.4. Connect the new enclosure in the network. Verify the network and SAN connections wired to the new

enclosure are the same as the failed one.5. From the interconnect bays of the failed enclosure, remove the VC/FC modules and place them in the

same rear-panel positions of the Interconnect Bays in the new enclosure.6. From the failed enclosure, remove all blades and place them in the same front-panel positions in the

new enclosure.7. To configure the VC Domain, see the HP Virtual Connect for c-Class BladeSystem User Guide.8. Access the Onboard Administrator web interface for the enclosure to verify that the VC Domain link in

the bottom left correctly points to the VC Domain Manager IP address.9. To find the new enclosure, run an HP SIM discovery against the Onboard Administrator IP address.10. From the VCEM home page, click the VC Domains tab.11. Select the newly discovered VC Domain, and then click Add to VC Domain Group. Wait for the job

to complete successfully.

Replace VC modules in a VC Domain managed by VCEMTo replace a VC Ethernet module or a VC Fibre Channel module of a VC Domain managed by VCEM,perform the following:1. From the VCEM home page, click the VC Domains tab.2. Select the VC Domain with the VC modules to be replaced.3. Click Remove from VC Domain Group. Wait for the job to complete successfully.4. Replace the VC modules from the enclosure reader interconnect bays. Verify that the network and SAN

connections that are wired to the new VC modules are the same as the old connections.5. If the primary VC Ethernet module was replaced, then you must configure the VC Domain again through

virtual Connect. For more information about configuring the VC Domain, see the HP virtual connect forc-Class BladeSystem User Guide.

Troubleshooting 97

Page 98: Virtual Connect

6. Access the Onboard Administrator web interface for the enclosure to verify that the VC Domain link inthe bottom left portion of the screen correctly points to the VC Domain Manager IP address.

7. Perform an HP SIM discovery against the Onboard Administrator IP address.8. From the VCEM home page, click the VC Domains tab.9. Select the same VC Domain, and then click Add to VC Domain Group. Wait for the job to complete

successfully.Verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group.For more information, see Requirements for adding a VC Domain to a VC Domain Group.

Failover fails to initiate with an ERROR (30) - Could not initiate failover; nestedexception is: java.net.SocketTimeoutException: Read timed out

This error can occur when the CLI cannot communicate to the VCEM SOAP interface. This communicationissue can occur when an IP address or hostname lookup takes more than a few minutes to return or whenthere is a networking issue on the VCEM server. To resolve this issue, verify that the HP SIM system is runningproperly by logging in and that the IP address or hostname for the source system exists. If the IP address orhostname does not exist, perform an HP SIM discovery.

VC Profile Failover fails during Onboard Administrator replacementIf an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant OnboardAdministrator might take several minutes to take over. The VC Profile Failover operation fails when sourceor spare bays are associated to an enclosure while the redundant Onboard Administrator is taking place.To resolve this issue:1. Wait until Onboard Administrator has failed over. Perform an HP SIM discovery to rediscover the new

Onboard Administrator IP address. If the address is not rediscovered, see the HP BladeSystem c-ClassOnboard Administrator User Guide.

2. If you initiated VC Profile Failover through the VCEM GUI:a. From the VCEM home page, click the Profiles tab.b. Select the server profile to failover and click Failover. The Virtual Connect Enterprise

Manager is executing the request message appears.c. Click OK to go to the Jobs page and monitor job progress.

VCEM cannot power down ProLiant server model BL465 G1All VCEM operations that explicitly power down the server (such as VC Profile Failover, Momentary Pressor Press and Hold) might not work well for ProLiant server model BL465c G1 unless the Onboard Administratorfirmware version is 2.25. If you are managing enclosures that contain ProLiant server model BL465c G1,verify that you use Onboard Administrator firmware version 2.25.

After VC Domain is removed from VC Domain Group in VCEM, profile withexternal-managed status cannot be edited through Virtual Connect Manager

This situation occurs when the profile address are not in the released range selected during the remove VCDomain from VC Domain Group or delete entire VC Domain Group operations. To make changes to suchserver profiles, you must bring the VC Domain again to VCEM control and then update the server profilethrough the VCEM profile editor.

Server profile edit operation fails when target server is powered onIf you edit a server profile in VCEM and add, remove, or change an Ethernet network connection, add,remove, or change Fibre Channel SAN connections or change the server profile name, the edit server profilejob might fail with the following message in the job details:Error during Edit server profile [Profile Name]. Details: This action couldnot be performed because the server is powered on. Power down the serverassociated with the Server Bay and retry the operation.

98 Troubleshooting VCEM

Page 99: Virtual Connect

VCEM server profile editor does not prevent profile edit operations in case the target server is powered off.However, the VCEM server profile edit job might fail depending on what profile changes each VC Domainfirmware version allows in case the target server is powered on.

Server profile network connections that use multiple networks are not workingIf a VC Domain has a network connection from a server profile configured to use multiple networks, and theVC Domain is not working as expected, the network that was selcted to the untagged network might not becorrectly reflected in the VC Domain.To resolve this issue:1. Power down the server blade.2. Select the server profile that is presenting the problems, and then click Edit.3. Verify that the multiple networks configuration for that server profile is correct. Verify that the Untagged

network is correctly selected.4. Click OK.5. Power on the server blade.6. From VC Domain Maintenance, upgrade the VC Domain Firmware to the latest version.

Server profile network configuration was lostIf a VC Domain has server profiles configured to use multiple networks and there is a network selected tobe untagged, the network configurations can be lost.To resolve this issue:1. From VC Domain Maintenance, upgrade the VC Domain firmware to the latest version.2. Edit the server profile, and then set the multiple networks configuration.

VC Domain status is "Mismatch Configuration" after cancel VC Domain Maintenanceoperation fails

This situation occurs when the server profiles from a VC Domain managed by VCEM have changed and donot match the existing server profiles in the VCEM database. For example, restoring an old VC Domainbackup that has a different server profile form the current VC Domain in the VCEM database.In such cases, VCEM changes the VC Domain status to "Mismatch Configuration," and the VC DomainGroup to, "Configuration in sync." To continue managing this VC Domain with VCEM, click VC DomainMaintenance to resynchronize the VC Domain configuration and server profiles.

Server profile job completed with success but changes have not occurredIf a VC Domain is managed by VCEM, and Onboard Administrator is brought out of Virtual Connect Mode,the following error message appears the next time you log in to Virtual Connect Manager:The HP virtual connect has lost its login credentials for the HP OnboardAdministrator (OA). OA may have been replaced or reset to factory defaults.To ensure proper operation, these credentials must be reestablished.

When the Onboard Administrator credentials are provided, an error message appears stating that thecredentials are not valid. This situation can occur when:

• Onboard Administrator is replaced or reset to factory default settings.

• The clear vcmmode command was executed in the Onboard Administrator command line interface.

• The VC Ethernet modules were temporarily replaced by another BladeSystem c-Class interconnectmodule.

As a result, VCEM might display false job results such as, "Completed with success," even though the serverprofile changes have not taken effect. The ability of VCEM to manage server profiles might also be affectedfor:

• Creating an unsigned server profile

• Editing of an assigned server profile

Troubleshooting 99

Page 100: Virtual Connect

• Assigning a server profile

• Deleting a server profile

• Unassigning a server profile

The following bay operations might also be affected:

• False information might be displayed for power status, the server model, and serial number

• Power buttons might not perform the expected operations

In addition, after logging in to the Virtual Connect Manager user interface, the following warning messagemight appear:The HP Virtual Connect has lost its login credentials for HP OnboardAdministrator (OA). OA may have been replaced or reset to factory defaults.To ensure proper operation, these credentials must be reestablished.

This situation occurs because VCEM relies on proper communication from the Virtual Connect Manager tothe Onboard Administrator to retrieve and change configurations, statuses of the physical devices inside theenclosure, and perform server power all on and off operations.To correct this issue, restore communication between the Onboard Administrator and Virtual Connect Managerby performing the following:1. Select the affected VC Domain, and start VC Domain Maintenance.2. Log in to Virtual Connect Manager. Wait to be prompted for new Onboard Administrator credentials.

NOTE: You must have domain privileges to log in to Virtual Connect Manager.

3. Provide the Onboard Administrator credentials, and then follow the Virtual Connect Manager instructions.4. In Virtual Connect Manager, restart all servers with server profiles that present a Pending status.5. Verify that the servers are operating correctly.6. Access VCEM, and complete VC Domain Maintenance.

VCEM getting started online help screen does not appear automatically at HP SIMlogin

HP SIM cannot present VCEM getting started online help content during the HP SIM login if there are nosystems discovered.To correct this issue, perform either of the following:

• Access the VCEM from the click Help→Getting Started→Virtual Connect Enterprise Manager help.

• Run HP SIM discovery in order to enable VCEM Getting Started online help at the next HP SIM login.If you entered information at Discovery settings for HP SIM page during VCEM installation, thenaccess the HP SIM menu by selecting Options→Discovery

1.

2. Select either Virtual Connect Enterprise Manager Network Discovery or Insight SoftwareNetwork Discovery.

3. Click Run Now.

HP SIM customizations for VCEM have not taken placeVCEM customizations for both HP SIM menu and HP SIM System and Events collections might not take placewhen installing VCEM standalone mode.To correct this issue from the HP SIM menu, access Options→Managed Environment, and click OK toapply VCEM customization to HP SIM menu and HP SIM System and Events collections.

After a server profile failover, some connections defined in the server profile are notfunctional

VCEM cannot identify if all Fibre Channel and Ethernet connections configured in a server profile can bephysically mapped to the physical ports of a server blade, due to that it is possible to have Ethernet or Fibre

100 Troubleshooting VCEM

Page 101: Virtual Connect

Channel connections in the server profile that cannot be configured in the server blade where it is assigned,causing those servers to not function.To correct this issue, perform either of the following:

• Manually move the affected server profile to a spare server blade that contains all the necessary physicalports to receive the server profile.

• Install the necessary mezzanine cards in the server blade to provide the physical port mappings requiredby the server profile connections.

Server profiles are not displaying physical port mapping and allocated bandwidthinformation

VCEM does not display physical port mapping and allocated bandwidth information for the Ethernet networkconnection in a server profile.To correct this information, perform the following:1. Go to Virtual Connect Manager user interface.2. Expand the Server Profiles Assigned Server Profiles left navigation panel and click the desired

server profile.3. The Physical Port Mapping and Allocated Bandwith information is presented inside the Ethernet Network

Connection table.

VCEM page displays "Communication with the HP SIM server has been lost"When VCEM performs a task that requires some time to be completed, HP SIM server might detect that thetask is taking too long and the Communication with the HP SIM server has been lostmessageappears.This behavior is intermittent, but can occur in the following situations:

• When navigating through VCEM pages and requesting multiple operations at the same time

• When VC Domains that are being managed by VCEM are having a communication outage

To solve this issue, press Refresh to reload the VCEM page, and then perform the desired operation again.To prevent the issue from happening again, perform either of the following:

• Verify that the Central Management Server has the minimum hardware requirements to run VCEM.

• Verify that all VC Domains are correctly communicating with the Central Management Server.

VC Domain not discovered by HP SIMIf SNMP protocol is not correctly configured, then HP SIM cannot correctly discover the unconfigured VCDomains, and then you might not be able to see such VC Domains or the VC Domains list.To correct this issue, perform one of the following:

• Access the HP SIM menu, select Options→Discovery→Configure Global Credentials, and verifythe first SNMP read community string is public.

• Access the HP SIM menu, Select Options→Discovery→Configure Global Protocol Settings, andverify that the Enable SNMP option is selected.

• Run HP SIM discovery on the Onboard Administrator IP address related to the VC Domain by accessingthe HP SIM menu and selecting Options→Identify System or Options→Discovery.

Create VC Domain Group or Add VC Domain to VC Domain Group operations failand the message "An invalid boot LUN was entered. Check the storage arrays forthe proper LUN number" appears

VCEM requires the boot target LUN configuration and server profiles to be either a three-digit decimalbetween 0–255, or a 16-digit hexadecimal value between 0 and FFFFFFFFFFFFFFFF.

Troubleshooting 101

Page 102: Virtual Connect

This message appears whenever a Create VC Domain Group or an Add VC Domain to VC Domain Groupoperation is performed and there is one or more server profiles inside the VC Domains that have a bootLUN that does not comply with the required conditions.To resolve this issue, use the Virtual Connect Manager to correct the Boot LUN value in the server profiles.A valid value is either a three–digit decimal between 0–255 or a 16-digit hexadecimal between 0 andFFFFFFFFFFFFFFFF. To determine the correct value, access the storage management software or ask thestorage administrator. After entering the correct value, try the operation again.

Profile move, assign, or failover operations fail and the message "An invalid bootLUN was entered. Check the Storage arrays for the proper LUN number" appears

VCEM requires the boot target LUN configuration and server profiles to be either a three-digit decimalbetween 0–255, or a 16-digit hexadecimal value between 0 and FFFFFFFFFFFFFFFF.This message appears whenever a profile move or failover operation is performed with a server profile thathas a boot LUN that fails to comply with the conditions stated here. This situation can happen when a serverprofile is created in virtual connect manager, and then you try to manage it with VCEM.To resolve this issue:1. Click the Profiles tab.2. Select the server profile that is presenting the problem.3. Click Edit.4. In the boot target configurations table, change all the target LUN fields to be within the allowed ranges

(either a three-digit decimal between 0–255, or a 16-digit hexadecimal between 0 andFFFFFFFFFFFFFFFF).

5. Click OK.6. Monitor the job progress until it is complete.After the operation completes, you can perform move, assign, and failover operations with the server profile.

VC Domain Maintenance operation fails when moving Ethernet networks (VLANstagged) from a deleted shared uplink set to another

When managing VC Domains with a firmware version later than 2.10, if you enable VC Domain Maintenanceand deleted a shared uplink set, and then added one or more Ethernet networks (VLANs tagged) with thesame name of the deleted ones to another existing shared uplink set, the VC Domain Maintenance serverprofile job completes, but other VC Domain Group members might be changed to "Mismatch Configuration"status. When trying to resynchronize such mismatched VC Domains, the VC Domain Maintenance job failsand the following message appears in the job details:"Virtual Connect Manager cannot perform the requested operation. Possiblereason is the user deleted a shared uplink set and its Ethernet Networks (VLANstagged), then added one or more Ethernet Networks (VLANs tagged) with the samename of the deleted ones to another existing Shared Uplink Set."

To resolve this issue:1. Click the VC domains tab, and select the VC Domain where the changes were made during the VC

Domain Maintenance operation.2. Click VC Domain Maintenance, and enable VC Domain Maintenance again by clicking Make changes

via VC Manager.3. In the Virtual Connect Manager user interface, delete the Ethernet networks (VLANs tagged) that were

moved from the deleted shared uplink set to another shared uplink set.4. Go back to VCEM, and complete VC Domain Maintenance by clicking Complete VC Domain

Maintenance.5. Click the VC Domains tab, for each VC Domain with "Configuration Mismatch" status, click VC Domain

Maintenance. To confirm the resynchronization of the selected VC Domain with the VC Domain Groupconfiguration, click OK.

6. Repeat steps 1 and 2 for the VC Domain where the changes were made.

102 Troubleshooting VCEM

Page 103: Virtual Connect

7. In the Virtual Connect Manager user interface, create the Ethernet networks (VLANs tagged) in thedesired shared uplink set.

8. Go back to VCEM and complete VC Domain Maintenance by clicking Complete VC DomainMaintenance.

Troubleshooting 103

Page 104: Virtual Connect

104

Page 105: Virtual Connect

14 HP services and technical supportHP offers a number of software support services, many of which are provided to our customers at no additionalcharge.

• Software Technical Support and Update Service—VCEM includes one year of 24 x 7 HP SoftwareTechnical Support and Update Service. This service provides access to HP technical resources forassistance in resolving software implementation or operations problems. The service also providesaccess to software updates and reference manuals either in electronic form or on physical media asthey are made available from HP. (Customers who purchase an electronic license to use are eligiblefor electronic updates only.) With this service, customers benefit from expedited problem resolution aswell as proactive notification and delivery of software updates. For more information about this service,see http://www.hp.com/services/insight.Registration for Software Technical Support and Update Service:There are two methods for registering:

• If you received a license entitlement certificate, automated registration for this service will takeplace upon online redemption of the license certificate/key.

• If the license information you received for your product instructs you to register for SoftwareTechnical Support and Update Service, follow the instructions so that you will be eligible fortelephone support and product updates.

How to Use Your Software Technical Support and Update Service:Once registered, you will receive a service contract in the mail containing the Customer Service phonenumber and your Service Agreement Identifier (SAID). You will need your SAID when calling for technicalsupport. Using your SAID, you can also go to the Software Update Manager (SUM) web page to viewyour contract online and elect electronic delivery for product updates.

• Warranty—HP will replace defective delivery media for a period of 90 days from the date of purchase.This warranty applies to VCEM and all Insight Control Management, HP Systems Insight Manager, andProLiant Essentials products.

• Join the discussion—The HP Support Forum is a community-based, user-supported tool for HP customersto participate in discussions amongst the customer community about HP products. See the “ManagementSoftware and System Tools” area.

• Software and Drivers download pages—These pages provide the latest software and drivers for yourHP products.

• Management Security (http://www.hp.com/servers/manage/security)—HP is proactive in its approachto the quality and security of all its management software. Be sure to check this website often for thelatest down loadable security updates.

HP Worldwide Customer Service contact numbers are available at http://www.hp.com/country/us/en/wwcontact.html.

HP contact informationFor the name of the nearest HP authorized reseller:

• In the United States, see the HP U.S. service locator at http://www.hp.com/service_locator.

• In other locations, see Contact HP Worldwide at http://welcome.hp.com/country/us/en/wwcontact.html.

For HP technical support:

• In the United States, for contact options see Contact HP United States at http://welcome.hp.com/country/us/en/contact_us.html.

• To contact HP by phone, call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hoursa day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored.

• In other locations, see Contact HP Worldwide at http://welcome.hp.com/country/us/en/wwcontact.html.

HP contact information 105

Page 106: Virtual Connect

106

Page 107: Virtual Connect

Glossarybays A device bay where the server blade is connected. HP BladeSystem c7000 Enclosure has a total

of 16 device bays and HP BladeSystem c3000 Enclosure has a total of 8 device bays.blade server A server that is located in a rack or enclosure.

See also enclosure, racks.centralmanagementserver (CMS)

A system in the management domain that executes the HP Systems Insight Manager software. Allcentral operations within HP Systems Insight Manager are initiated from this system.

collections The method for grouping system or event searches.container A rack or an enclosure is considered a container.

See also enclosure, racks.critical status A state generated when HP Systems Insight Manager can no longer communicate to a managed

system.DesktopManagementInterface (DMI)

An industry standard protocol, primarily used in client management, established by the DMTF.DMI provides an efficient means of reporting client system problems. DMI-compliant computerscan send status information to a central management system over a network.

discovery A feature within a management application that finds and identifies network objects. In HPmanagement applications, discovery finds and identifies all the HP systems within a specifiednetwork range.

domain groups Logical collection of domains with the same network and storage configuration.Domain NameService (DNS)

A service that translates domain names into IP addresses.

domains A VC Domain includes a single HP c-Class BladeSystem enclosure.enclosure A physical container for a set of blades servers. It consists of a backplane that routes power and

communication signals and additional hardware for cabling and thermal issues. It also hosts theCPU or server power supplies.

event Information sent to certain users that something in the managed environment has changed. Eventsare generated from SNMP traps and are preconfigured in this release. HP Systems Insight Managerreceives a trap when an important event occurs. Events are defined as:

• Informational. Events of this type require no attention and are provided as usefulinformation.

• Normal. Events of this type indicate that this event is not a problem.

• Minor. Events of this type indicate a warning condition that can escalate into a moreserious problem.

• Major. Events of this type indicate an impending failure.

• Critical. Events of this type indicate a failure and signal the need for immediate attention.

exclusion range Exclusion ranges are used to set aside addresses that might be in use for other purposes withinyour data center. Excluded address ranges are not assigned for use by VCEM.

external Address in use by server profiles in a VC Domain that was released back to VC Manager controland are no longer managed by VCEM.

external manageror externalmanager lock

A Virtual Connect user account created and exclusively used by Virtual Connect EnterpriseManager.

external port The Ethernet connectors (10GBASE-CX4 and RJ45) on the faceplate of the VC-Enet module labeledas ports 1-8, X1, and X2.

free Address available for VCEM allocation.

107

Page 108: Virtual Connect

full configurationrights user

A user who is automatically authorized for the All Tools toolbox on all systems, including theCMS. This type of user has been given special privileges to administer the HP Systems InsightManager software.

hardware status The operating state of SNMP-based systems. A hardware status is determined by polling SNMPinformation from the system. Status is defined as:

• Critical. HP Systems Insight Manager can no longer communicate with the system. Thesystem was previously discovered, but cannot be pinged. The system might be down, poweredoff, or no longer accessible on the network because of network problems.

• Major. A problem exists.

• Minor. The system is functioning but with errors.

• Normal. The system is functioning correctly.

• Unknown. HP Systems Insight Manager cannot obtain management information aboutthe system.

• Disabled HP Systems Insight Manager is disabled.

HP Systems InsightManager database(database)

The database that stores vital information about HP Systems Insight Manager, including users,systems, and toolboxes.

identification An aspect of the discovery process that identifies the management protocol and type of system.in use Address currently allocated by a server profile managed by VCEM.Internet Protocol(IP)

Specifies the format of datagrams (packets) and the addressing scheme on a network. Mostnetworks combine IP with Transmission Control Protocol (TCP), which establishes a virtualconnection between a destination and a source.

Major status Aggregate status information collected from the system that indicates one or more of the monitoredsubsystems are not operating properly which is impacting the system. Action should be takenimmediately.

Minor status Aggregate status information collected from the system that indicates one or more of the monitoredsubsystems are not operating properly which is impacting the system. Action should be taken assoon as possible to prevent further failure.

OnboardAdministrator

The Onboard Administrator is the central point for controlling an entire c-Class rack. It offersconfiguration, power, and administrative control over the rack, and its associated blades (ComputeServers), blade management processors (iLOs), network switches (depending on the models ofswitches used) and storage components (such as SAN or SATA). The Onboard Administrator isa single management processor, with shared resources to an optional backup twin processor forfailover.

profiles Virtual Connect server profile is a logical grouping of attributes related to server connectivity thatcan be assigned to a server blade.

racks A set of components cabled together to communicate between themselves. A rack is a containerfor an enclosure.

reclaim external Returns the external address to VCEM allocation.server blade Typically a very dense server system containing microprocessors, memory, and network connections

that can be easily inserted into a rack-mountable enclosure to share power supplies, fans, switches,and other components with other server blades. Server blades tend to be more cost-efficient,faster to deploy, and easier to adapt to growth and change than traditional rack-mounted ortower servers.See also enclosure, racks.

shared uplink port An Ethernet uplink port that carries the traffic for multiple Virtual Connect networks. Each associatedVirtual Connect network is mapped to a specific Virtual Local Area Network (VLAN) on theexternal connection, and appropriate VLAN tags are removed or added as Ethernet packets enteror leave the VC Domain.

108 Glossary

Page 109: Virtual Connect

shared uplink portset

A set of Ethernet uplinks that are used together to provide improved throughput and availabilityto a group of associated Virtual Connect networks. Each associated Virtual Connect network ismapped to a specific VLAN on the external connection and appropriate VLAN tags are removedor added as Ethernet packets enter or leave the VC Domain.

Simple NetworkManagementProtocol (SNMP)

One of the management protocols supported by HP Systems Insight Manager. Traditionalmanagement protocol used extensively by networking systems and most servers. MIB-2 is thestandard information available consistently across all vendors.

Smart Link A feature that, when enabled, configures a Virtual Connect network so that if all external uplinkslose link to external switches, Virtual Connect will drop the Ethernet link on all local server bladeEthernet ports connected to that network.

stacking port A VC-Enet module external port used to connect to other VC-Enet modules within an active VCDomain. Stacking ports are automatically identified by the VC-Enet modules. The port number(port ID) is illuminated amber.

system Nodes on the network that communicate through TCP/IP or IPX. To manage a system, some typeof 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.

uncleared eventstatus

Events that have a Critical, Major, Minor, Normal, or Informational severity.

Critical. A failure has occurred, and immediate attention is required.•

• Major. A failure is impending.

• Minor. A warning condition exists that can escalate into a more serious problem.

• Normal. These events are not a problem.

• Informational. No attention required. This status is provided as useful information

unknown status HP Systems Insight Manager cannot obtain management information about the system usingSNMP or DMI. Although no management instrumentation information is available, the systemcan be pinged. It might have an invalid community string or security setting.

uplink port An external port that is configured within Virtual Connect for use as a connection to externalnetworking equipment. Uplink ports are defined within Virtual Connect by the enclosure name,interconnect bay containing the module, and the part number. The port number (port ID) for uplinkports is lit green.

uplink port set A set of uplinks that are used together to provide improved throughput and availability for asingle Virtual Connect network connection to external networking equipment.

user A network user with a valid login on the CMS that has been added to HP Systems Insight Manager.VC Domain Groupconfiguration

A Virtual Connect domain configuration (including network definition, storage definition, MACaddress setting, and WWN address setting) applied to all the Virtual Connect modules in oneVC Domain group. It requires these Virtual Connect modules managed by the VC Domain Groupto have identical hardware configuration.

Version ControlAgent (VCA)

An agent that is installed on a server to enable you to see the HP software installed on that server.The VCA can be configured to point to a VCRM agent, enabling easy version comparison andsoftware update from the repository.

Virtual ConnectEnterpriseManager (VCEM)

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

Virtual ConnectManager (VCM)

The firmware embedded software provided with each Virtual Connect module.

Virtual Connectserver profile

A logical grouping of attributes related to server connectivity that can be assigned to a serverblade. A server profile can be assigned to any server blade within the VC Domain.

109

Page 110: Virtual Connect

110

Page 111: Virtual Connect

Index

Aadding a VC Domain to a VC Domain Group, 36adding custom MAC address ranges, 71adding custom WWN address range, 74adding or removing VC modules to VC Domain Group

configuration, 51allocating WWN addresses, 73assigning a profile, 58, 59assigning a profile from a key, 65

Bbays

assigning a profile from a key, 65performing a VC Profile Failover, 66powering down a bay, 64unassigning a profile from a key, 65

Ccanceling a VC Domain Group maintenance task, 50cancelling a VC Domain Maintenance task, 45Command Line Interface usage in VCEM, 85configuring multiple networks, 56configuring network port speed, 57configuring the target boot LUN, 55copying and assigning a profile to a bay, 59correlating VCEM operations in HP SIM and Virtual

Connect logs, 52creating a profile, 55creating a VC Domain Group, 35, 48creating MAC exclusion ranges, 70creating WWN exclusion ranges, 72

Ddeleting a profile, 58deleting a VC Domain Group, 50deleting custom WWN address ranges, 75deleting jobs, 80deleting MAC exclusion ranges, 70deleting WWN exclusion ranges, 73

Eediting a profile, 58editing custom MAC address ranges, 71editing custom WWN address ranges, 75external manager account, 83

HHP Virtual Connect

managing, 15technology, 14

HP Virtual Connect Enterprise Managerarchitectural overview, 14features and benefits, 13installation and configuration, 19installing, 23

key benefits, 13key features, 13Logical Serial Numbers, 77managing bays, 63managing MAC and WWN addresses, 69managing server profiles, 53managing VC Domain Groups, 47managing VC Domains, 27operations overview, 16performing post-installation configuration tasks, 23platform support, 14post-installation configuration tasks, 23preparing for installation, 19prerequisites for installation, 19product introduction, 13setup and configuration summary, 17tracking VCEM job status, 79troubleshooting, 89upgrading Virtual Connect firmware after VCEM is

managing VC Domains, 81VCEM home page, 24VCEM operations, 15

HP Virtual Connect Manageroverview, 15

JJob status message window, 79jobs

deleting jobs, 80Job status message window, 79reviewing job details, 80

Llicensing an enclosure for VCEM, 34logical serial numbers

identifying logical serial number values, 77

MMAC address

adding custom MAC address ranges, 71creating MAC exclusion ranges, 70deleting MAC exclusion ranges, 70editing custom MAC address ranges, 71reclaiming external MAC addresses, 70removing custom MAC address ranges, 71tracking individual MAC addresses, 69

maintaining a VC Domain from the VC Domain Grouppage, 49

moving a profile, 59moving Ethernet networks (VLANs tagged) from one shared

uplink to another, 52

Pperforming a VC Profile Failover, 59, 66powering down a bay, 64profiles

111

Page 112: Virtual Connect

assigning a profile, 58configuring multiple networks, 56configuring network port speed, 57configuring the target boot LUN, 55copying and assigning a profile to a bay, 59creating a profile, 55deleting a profile, 58editing a profile, 58moving a profile, 59performing a VC Profile Failover, 59unassigning a profile, 59verifying the presence of EFI partition data, 58

Rreclaiming external MAC addresses, 70reclaiming external WWN addresses, 74removing a VC Domain from a VC Domain Group, 37removing custom MAC address ranges, 71requirements for adding a VC Domain to a VC Domain

Group, 28reviewing job details, 80

Ssupported Insight software configurations, 22

Ttracking indivdual MAC addresses, 69tracking individual WWN addresses, 72troubleshooting

After a server profile failover, some connections definedin the server profile are not functional, 100

after VC Domain is removed from VC Domain Groupin VCEM, profile with external-managed status cannotbe edited through Virtual Connect Manager, 98

backing up and restoring VCEM, 95cannot change the MAC/WWN/Serial Number ranges

in Virtual Connect Manager when there are serverprofiles, 96

cannot manage a VC Domain when VC module failoveris taking place, 90

Create VC Domain Group or Add VC Domain to VCDomain Group operations fail and the message "Aninvalid boot LUN was entered. Check the storagearrays for the proper LUN number" appears, 101

creating a server profile or adding a VC Domain to aVC Domain Group fails, 95

enclosure has a hardware failure and must be replaced,97

enclosure has two Onboard Administrators, and onefails, 89

error on database operation occurs, 94errors occur while loading VCEM pages, 94failed to execute VCEM operation because VC firmware

not supported, 94failover fails to initiate with an ERROR (30) - Could not

initiate failover; nested exception is:java.net.SocketTimeoutException: Read timed out, 98

HP SIM customizations for VCEM have not taken place,100

job appears with Failed status, 89operation fails to perform in the VC Domain or VC

Domain Group under maintenance status, 92profile move, assign, or failover operations fail and the

message "An invalid boot LUN was entered. Checkthe Storage arrays for the proper LUN number"appears, 102

Remove from VC Domain Group job is successful butwith errors, 93

Replace VC modules in a VC Domain managed byVCEM, 97

server profile edit operation fails when target server ispowered on, 98

server profile network configuration was lost, 99Server profiles are not displaying physical port mapping

and allocated bandwidth information, 101unable to add an unconfigured VC Domain to a VC

Domain Group, 90unable to add VC Domain to a VC Domain Group, 90unauthorized error when trying to access the VCEM

home page, 89uninstalling VCEM, 95VC Domain displays Configuration Mismatch status, 91VC Domain displays Connectivity failure status, 91VC Domain displays Expired License status, 93VC Domain displays Missing External Manager lock

status, 91VC Domain Maintenance operation fails when moving

Ethernet networks (VLANs tagged) from a deletedshared uplink set to another, 102

VC Domain not discovered by HP SIM, 101VC Domain status is "Mismatch Configuration" after

cancel VC Domain Maintenance operation fails, 99VC Profile Failover fails during Onboard Administrator

replacement, 98VCEM cannot power down ProLiant server model BL465

G1, 98VCEM database is inaccessible or irretrievable with no

backup, or VCEM file systems are corrupt with nobackup, 96

VCEM getting started online help screen does notappear automatically at HP SIM login, 100

VCEM is prompting for Onboard Administratorcredentials on a configured VC Domain, 89

VCEM page displays "Communication with the HP SIMserver has been lost", 101

Uunassigning a profile from a bay, 65upgrading VC Domain Group firmware mode, 50upgrading Virtual Connect firmware after VCEM is

managing VC Domains, 81performing firmware update using the VC Domain

Maintenance capability, 81preparation checklist, 81

VVC Domain Group

canceling a VC Domain Group maintenance task, 50

112 Index

Page 113: Virtual Connect

creating a VC Domain Group, 48deleting a VC Domain Group, 50maintaining a VC Domain from the VC Domain Group

page, 49upgrading VC Domain Group firmware mode, 50

VC Domain Groupsadding or removing VC modules to VC Domain Group

configuration, 51correlating VCEM operations in HP SIM and Virtual

Connect logs, 52moving Ethernet networks (VLANs tagged) from one

shared uplink to another, 52VC Domain in VC Domain Maintenance, 40VC Domain tasks, 34VC Domains

adding a VC Domain to a VC Domain Group, 36cancelling a VC Domain Maintenance task, 45creating a VC Domain Group, 35licensing an enclosure for VCEM, 34removing a VC Domain from a VC Domain Group, 37requirements for adding a VC Domain to a VC Domain

Group, 28VC Domain in VC Domain Maintenance, 40VC Domain tasks, 34

VC Profile FailoverCLI exit and error codes, 87list details for specified VCEM job, 85performing VC profile failover on specified VC Domain

bay server, 85show CLI usage online help, 86

VCEM home page, 24verifying the presence of EFI partition data, 58

WWWN address

adding custom WWN address ranges, 74allocating WWN addresses, 73creating WWN exclusion ranges, 72deleting custom WWN address ranges, 75deleting WWN exclusion ranges, 73editing custom WWN address ranges, 75reclaiming external WWN addresses, 74tracking individual WWN addresses, 72

113