HP Virtual Connect Enterprise Manager 7.5 User Guide

HP Virtual Connect Enterprise Manager 7.
5
User Guide
Abstract
This document is intended to be used by technical professionals who manage multiple HP BladeSystem enclosures and use HP
Virtual Connect Manager to control network connectivity. HP assumes that you have installed Virtual Connect, are familiar with
the embedded VCM web console, and have read the HP Virtual Connect for c-Class BladeSystem User Guide and understand
its concepts.
HP Part Number: 778004-004

Published: August 2015
Edition: 1
© Copyright 2007, 2015 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Links to third-party websites take you outside the HP website. HP has no control over and is not responsible for information outside HP.com.
Acknowledgments
Microsoft® and Windows® are trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.

Warranty
HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management
products.
Contents
1 Introduction...............................................................................................9
Key features and benefits...........................................................................................................9
Key features........................................................................................................................9
Key benefits........................................................................................................................9
What's new......................................................................................................................10
Platform support.....................................................................................................................10
Product licensing....................................................................................................................10
Architectural overview.............................................................................................................11
HP Virtual Connect technology............................................................................................11
Managing HP Virtual Connect..................................................................................................13
HP Virtual Connect Manager...............................................................................................13
HP Virtual Connect Enterprise Manager................................................................................13
Understanding VCEM operations..............................................................................................13
2 Installing and configuring VCEM................................................................16
Understanding VCEM and VC firmware version compatibility.......................................................16
Preparing for a VCEM installation.............................................................................................19
Installation prerequisites..........................................................................................................20
VC firmware browser support..............................................................................................20
Mixed VC firmware versions and compatibility in a VC Domain Group ....................................20
Backward compatibility for VC firmware ..........................................................................20
Forward compatibility for VC firmware.............................................................................21
Selecting HP Virtual Connect Enterprise Manager ports ..........................................................21
Installing VCEM......................................................................................................................22
Updating VC firmware............................................................................................................22
Updating to VC firmware 3.7x or later..................................................................................24
Updating to VC firmware 4.1x.............................................................................................24
Removing VCEM....................................................................................................................25
Performing post-installation configuration tasks............................................................................25
Post-installation configuration tasks.......................................................................................25
Upgrading incompatible firmware modes and versions...........................................................27
Installing VCEM in an HA-clustered CMS configuration in a Microsoft Cluster Server cluster..............28
3 Managing VC Domains............................................................................29
Requirements for adding a VC Domain to a VC Domain Group....................................................30
VC 4.4x features that must be disabled in a VC Domain to be part of a VC Domain Group with
VC firmware 4.3x..............................................................................................................34
VC firmware 4.2x..............................................................................................................35
VC firmware 4.1x...............................................................................................................35
VC firmware 4.0x..............................................................................................................36
VC firmware 3.7................................................................................................................36
VC firmware 3.5x and 3.6x................................................................................................40
VC 3.7x, 3.6x and 3.5x features that must be disabled in a VC Domain to be part of a VC Domain
Group with VC firmware 3.3x..............................................................................................41
VC 3.5x feature that must be disabled in a VC Domain to be part of a VC Domain Group with
VC firmware 3.3x..............................................................................................................41
VC Domain tasks....................................................................................................................42
Contents 3
VCEM licensing......................................................................................................................42
Preparing to create a VC Domain Group...................................................................................43
Creating a VC Domain Group..................................................................................................43
Defining Roles-Based Access Control (RBAC)..............................................................................45
Adding a VC Domain to a VC Domain Group............................................................................50
Moving a VC Domain containing server profiles to a different VC Domain Group...........................52
Removing a VC Domain from a VC Domain Group.....................................................................52
Working with multienclosure VC Domains..................................................................................53
VC Domain Maintenance........................................................................................................56
Replicating VC Domain Group configurations to other VC Domains during VC Domain
Maintenance.....................................................................................................................58
Performing VC Domain Maintenance....................................................................................61
Backing up and restoring domain configurations through VC Domain Maintenance....................62
Changes in VCM that might affect completing VC Domain Maintenance...................................63
Viewing VC Domain details ................................................................................................63
Viewing the Custom Speed value....................................................................................64
Viewing VC Domain QoS details....................................................................................64
Viewing VC Domain and VC Domain Group roles.............................................................66
Viewing VC Domain multicast details ..............................................................................66
Statistical throughput attributes........................................................................................67
Viewing Allocated Bandwidth attributes.......................................................................67
Displaying Converged Uplink sets and FCoE networks...................................................68
Viewing LACP timer attributes for VC Domains.............................................................68
SNMP Access...............................................................................................................69
Viewing IPv6 addresses of managed VC Domains ............................................................70
Using VLAN capacity.........................................................................................................70
Working with HP Virtual Connect 8 Gb Fibre Channel Module for c-Class BladeSystem...............71
Adding or removing remote enclosures from a multienclosure domain in VC Domain
Maintenance.....................................................................................................................71
Canceling a VC Domain Maintenance task................................................................................71
Resynchronizing a VC Domain with Configuration Mismatch........................................................72
Replacing the HP 1/10 Gb VC-Enet or the HP 1/10 Gb-Enet modules ..........................................72
Using FlexFabric modules........................................................................................................73
Adding FlexFabric modules to an existing VCEM managed VC Domain....................................73
Replacing VC Ethernet modules with FlexFabric modules in an existing VCEM managed VC
Domain............................................................................................................................73
Replacing VC Ethernet in interconnect bays three to eight with FlexFabric in an existing VCEM
managed VC Domain........................................................................................................74
Replacing FC modules with FlexFabric modules in an existing VCEM managed VC Domain.........74
Replacing VC Ethernet and FC modules with FlexFabric modules in an existing VCEM managed
VC Domain.......................................................................................................................75
Upgrading to an HP Virtual Connect 8 Gb, 24-port FC module or an HP VC 8 Gb 20-port FC
module ............................................................................................................................76
Upgrading or removing an HP Virtual Connect Flex-10 module or an HP Virtual Connect FlexFabric
module.............................................................................................................................76
Upgrading to an HP Virtual Connect FlexFabric module from a VC-FC module...........................78
Support of the CMS Reconfigure Tool........................................................................................79
4 Managing VC Domain groups...................................................................80
Creating a VC Domain Group..................................................................................................81
Maintaining a VC Domain from the VC Domain Groups page .....................................................83
Canceling a VC Domain Group maintenance task......................................................................84
Upgrading VC Domain Group firmware mode............................................................................84
Deleting a VC Domain Group..................................................................................................85
Displaying VC Domain Group detail tabs..................................................................................87
4 Contents
Viewing VC Domain Group QoS details...............................................................................87
Viewing VC Domain Group roles.........................................................................................89
Viewing VC Domain Group multicast details .........................................................................89
Statistical throughput attributes.............................................................................................90
Displaying Converged Uplink sets and FCoE networks in VC Domain Groups............................90
Viewing LACP timer attributes for VC Domain Groups.............................................................90
Adding or removing VC modules in a VC Domain Group ...........................................................91
Moving Ethernet networks (VLANs tagged) from one shared uplink to another................................91
Correlating VCEM operations in Systems Insight Manager and VC logs.........................................92
5 Managing server profiles...........................................................................93
Creating a server profile..........................................................................................................98
Concealing unused FlexNICS ................................................................................................104
Configuring the target boot LUN.............................................................................................104
Configuring multiple networks ...............................................................................................105
Configuring Network Port Speed............................................................................................106
Deleting a server profile........................................................................................................106
Editing a server profile..........................................................................................................107
Viewing server profile attributes and status...............................................................................108
Using flexible server profile listings .........................................................................................111
Extending mapped networks..................................................................................................111
Selecting a single network................................................................................................111
Selecting multiple networks...............................................................................................111
Selecting multiple networks with the Force same VLAN mappings as Shared Uplink Set option
checked..........................................................................................................................112
Verifying the presence of EFI partition data..............................................................................112
Assigning a server profile......................................................................................................112
Unassigning a server profile...................................................................................................113
Copying a server profile........................................................................................................113
Moving a server profile.........................................................................................................114
Moving a server profile to another bay in the same VC Domain Group...................................114
Moving a server profile to another bay in a different VC Domain Group.................................114
Performing a VC Server Profile Failover....................................................................................119
Preconditions for VC Server Profile Failover.........................................................................120
Using spare bays.............................................................................................................120
Initiating VC Server Profile Failover through the VCEM CLI.....................................................120
Initiating VC Server Profile Failover through the VCEM GUI...................................................121
Initiating VC Server Profile Failover using Systems Insight Manager Automatic Event Handling....121
6 Managing enclosure bay assignments.......................................................123
Powering down a bay...........................................................................................................124
Assigning a server profile to a bay.........................................................................................126
Unassigning a server profile from a bay..................................................................................126
Designating spare bays.........................................................................................................126
Performing a Server Profile Failover.........................................................................................126
7 Managing MAC and WWN addresses.....................................................128
MAC Addresses...................................................................................................................128
Tracking individual MAC addresses........................................................................................128
Creating MAC exclusion ranges.............................................................................................129
Deleting MAC exclusion ranges..............................................................................................129
Reclaiming external MAC addresses.......................................................................................130
Adding a custom MAC address range.....................................................................................130
Editing a custom MAC address range......................................................................................130
Removing a custom MAC address range..................................................................................130
WWN Addresses.................................................................................................................131
Contents 5
Tracking individual WWN addresses......................................................................................131
Creating WWN exclusion ranges...........................................................................................132
Address management tasks....................................................................................................132
Using VCEM subranges in a federated CMS environment......................................................133
Managing exclusion ranges with multiple central management systems..............................133
Extending VCEM in use ranges................................................................................133
Transferring all managed VC Domains from one VCEM instance to another.............................134
Transferring one managed VC Domain from one VCEM instance to another............................134
Consolidating multiple VCEM instances into a single VCEM instance .....................................136
Displaying factory default MAC and WWN addresses.........................................................136
Deleting WWN exclusion ranges...........................................................................................137
Reclaiming external WWN addresses.....................................................................................137
Adding a custom WWN address range..................................................................................138
Editing a custom WWN address range...................................................................................138
Deleting a custom WWN address range.................................................................................138
8 Working with Logical Serial Numbers.......................................................139
Identifying logical serial number values...................................................................................139
9 Tracking VCEM job status........................................................................140
Jobs....................................................................................................................................140
Job status message window...................................................................................................140
Reviewing job details............................................................................................................141
Deleting jobs.......................................................................................................................141
10 Upgrading VC firmware after VCEM is managing VC Domains..................142
Preparation checklist.............................................................................................................142
Performing the firmware update using the VC Domain Maintenance capability.............................143
Performing firmware update without the VC Domain Maintenance capability................................143
11 Removing an external manager account...................................................144
12 Failover Command Line Interface Usage in VCEM.....................................146
Perform VC Server Profile failover on specified VC Domain bay server.........................................146
List details for specified VCEM job..........................................................................................147
Show CLI usage online help...................................................................................................148
CLI exit and error codes........................................................................................................148
13 Troubleshooting VCEM..........................................................................149
VC Domain configuration mismatch after FW upgrade from 4.20 to 4.40....................................149
VCEM will present an unexpected error for profile operations on a blade that is in EV-CORRUPTION
state...................................................................................................................................149
Deleting a large number of assigned profiles results in a timeout.................................................149
Managing VC domains with Expanded VLAN capacity enabled................................................149
Using Expanded VLAN capacity .......................................................................................149
Adding a VC 3.70 or later Domain with IGMP No Flood enabled into a VC Domain Group with
group firmware mode 3.3x or 3.5x....................................................................................150
Adding a 3.70 or later VC Domain to a VC Domain Group in compatibility mode (3.30 or
3.50).........................................................................................................................150
Canceling Domain Maintenance...................................................................................151
Completing Domain Maintenance.................................................................................151
Using Expanded VLAN capacity with the Cancel VC domain Maintenance operation...............152
Using iSCSI boot configuration with IE10 in compatibility view...................................................152
Using boot configuration with Internet Explorer browser in compatibility view...............................152
Cannot resynchronize VC Domain that has a configuration mismatch state due to an enabled VC
feature................................................................................................................................152
Updating VC firmware versions in a VC Domain to be compatible with VC 3.7x or later................153
Performance issues while using IE 8 or 9 with a large number of networks...................................154
6 Contents
General..............................................................................................................................154
VCEM performance..............................................................................................................155
VC Domain Groups and VC Domain Management...................................................................155
Jobs....................................................................................................................................156
Server power management....................................................................................................156
Server profile operations........................................................................................................156
VC Profile Failover................................................................................................................156
Profile operations fail, and the error message "An invalid boot LUN was entered. Check the storage
arrays for the proper LUN number" appears.............................................................................156
Error popup appears when you select HP predefined ranges during remove VC Domain from group
or delete VC Domain Group operations...................................................................................157
VCM shows an incorrect address for VCEM.............................................................................157
Communicating with the enclosure OA....................................................................................157
MAC, WWN, and Serial Number management.......................................................................158
Duplicate MAC and WWN address assignments.....................................................................158
Unauthorized error when trying to access the VCEM home page................................................158
A job appears with Failed status.............................................................................................158
Enclosure has two Onboard Administrators, and one fails..........................................................158
VCEM is prompting for Onboard Administrator credentials on a configured VC Domain................159
VCM does not accept Onboard Administrator credentials..........................................................159
Unable to add VC Domain to a VC Domain Group...................................................................159
Unable to add an unconfigured VC Domain to a VC Domain Group...........................................160
Cannot manage a VC Domain when VC module failover is taking place.....................................160
VC Domain displays Missing External Manager lock status........................................................160
VC Domain displays Configuration Mismatch status..................................................................161
VC Domain displays Connectivity failure status.........................................................................161
Cannot resynchronize VC Domain that is in Configuration Mismatch state....................................162
Operations fail in a VC Domain or VC Domain Group under maintenance status..........................163
Remove from VC Domain Group job is successful but with errors.................................................163
Resolving an expired license status..........................................................................................164
Resolving database operation errors........................................................................................164
Errors occur while loading VCEM pages..................................................................................164
Failed to execute VCEM operation because VC firmware not supported.......................................165
Creating a server profile or adding a VC Domain with a server profile to a VC Domain Group
fails....................................................................................................................................165
Removing VCEM..................................................................................................................165
Backing up and restoring VCEM.............................................................................................166
Cannot change the MAC/WWN/Serial Number ranges in VCM when there are server profiles.....166
VCEM database is inaccessible or irretrievable with no backup, or VCEM file systems are corrupt
with no backup....................................................................................................................166
Enclosure has a hardware failure and must be replaced.............................................................167
Replacing VC modules..........................................................................................................168
Replacing VC modules in a VC Domain managed by VCEM.................................................168
Replacing VC modules in interconnect bays three to eight in a VC Domain Managed by VCEM
without removing the VC Domain from the VC Domain Group................................................168
Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is:
java.net.SocketTimeoutException: Read timed out......................................................................169
VC Profile Failover fails during Onboard Administrator replacement............................................169
After a VC Domain is removed from a VC Domain Group in VCEM, a profile with external-managed
status cannot be edited through VCM......................................................................................169
Server profile edit operation fails when target server is powered on.............................................169
VC Domain status is "Mismatch Configuration" after cancel a VC Domain Maintenance operation
fails....................................................................................................................................170
Server profile job completed successfully but changes have not occurred......................................170
Systems Insight Manager customizations for VCEM have not taken place.....................................171
Contents 7
After a server profile failover, some connections defined in the server profile are not functional.......171
VCEM page displays "Communication with the Systems Insight Manager server has been lost"......171
VC Domain not discovered by Systems Insight Manager............................................................171
Create VC Domain Group or Add VC Domain to VC Domain Group operations fail and the message
"An invalid boot LUN was entered. Check the storage arrays for the proper LUN number"
appears..............................................................................................................................172
Profile move, assign, or failover operations fail and the message "An invalid boot LUN was entered.
Check the Storage arrays for the proper LUN number" appears..................................................172
Profiles fail to boot from Direct Attached SAN Fabric after relocation to another enclosure..............173
14 Support and other resources...................................................................174
Information to collect before contacting HP...............................................................................174
How to contact HP................................................................................................................174
Security bulletin and alert policy for non-HP owned software components....................................174
Subscription service..............................................................................................................174
Registering for software technical support and update service.....................................................174
How to use your software technical support and update service.............................................175
HP authorized resellers..........................................................................................................175
Related information...............................................................................................................175
Documents......................................................................................................................175
Websites........................................................................................................................175
Typographic conventions.......................................................................................................175
15 Documentation feedback.......................................................................177
A VCEM subranges...................................................................................178
Glossary..................................................................................................182
Index.......................................................................................................186
8 Contents
1 Introduction
HP Virtual Connect Enterprise Manager (VCEM) centralizes network connection management and
workload mobility for HP BladeSystem servers that use Virtual Connect to access LANs, SANs, and
converged network environments. VCEM helps organizations increase productivity, respond faster
to workload and infrastructure changes, and reduce operating costs.
Built on the Virtual Connect architecture integrated into every HP BladeSystem c-Class enclosure,
VCEM provides a central console to administer network address assignments, perform group-based
configuration management, and to rapidly deploy, move, and failover server connections and
workloads for 250 VC Domains (designed to support up to 1,000 enclosures and 16,000 server
blades when used with Virtual Connect multi-enclosure domain configurations).
Use VCEM to complete key data center tasks quickly and reliably, without impacting the
configuration and availability of production networks. VCEM enables you to:
• Deploy new BladeSystem enclosures, server blades, and VC Domains
• Perform fast and cost-effective server recovery
• Complete planned systems maintenance with minimal downtime
• Rapidly migrate and repurpose server blades to meet changing workload and application
priorities
Together, Virtual Connect and VCEM create a change-ready infrastructure that enables system
administrators to add, replace, and recover blade servers and their workloads across the data
center in minutes without impacting production networks. This flexible infrastructure also provides
the foundation for logical server deployment and orchestration delivered with Matrix Operating
Environment software.
Key features and benefits

VCEM delivers the following key features and benefits.
Key features
• Single intuitive console to manage up to 250 VC Domains. VCEM is designed to support up
to 1,000 BladeSystem enclosures and 16,000 servers when used with Virtual Connect Ethernet
multienclosure domains.
• Central repository administers a total of 256K MAC addresses and WWNs per VCEM console.
• Group-based management of multiple VC Domains using master configurations.
• Automated failover of server connection profiles and workloads to customer-defined spare
servers.
• Seamless integration with existing Virtual Connect infrastructures—discovers and aggregates
Virtual Connect resources into a central console.
• Licensed per c-Class enclosure—simplifies deployment and enables support for current and
future BladeSystem and Virtual Connect hardware.
Key benefits
• Centrally manage connectivity and workloads for hundreds of VC Domains and thousands of
HP BladeSystem server blades.
• The VCEM address repository enables more efficient administration of data and storage
network assignments (MAC and WWN) and eliminates the risk of address conflicts.
Key features and benefits 9

• Group-based management of Virtual Connect Domains increases infrastructure consistency,
simplifies system deployment and enables rapid change management across hundreds of HP
BladeSystem enclosures.
• Add, change, and failover servers and their workloads across the data center in minutes
without impacting production networks.
• Increase productivity and server-to-administrator ratios.
• Release LAN and SAN administrators from routine server-centric tasks.
• Scalable across small and large data centers.
What's new
HP VCEM 7.5 adds the following new feature:
• Supports HP Virtual Connect 4.45
Platform support
VCEM is supported on most HP BladeSystem c-Class hardware, storage, software, and third-party
operating platforms. For a full list of supported platforms and components, see Installing and
configuring VCEM.
Product licensing
VCEM is licensed per BladeSystem c-Class enclosure, with separate options for HP BladeSystem
c3000 and HP BladeSystem c7000 enclosures.
A single VCEM license is required for each enclosure to be managed in both single and
multi-enclosure domain configurations, and is valid for the life of the associated
enclosure.
10 Introduction
Table 1 (page 11) lists all available VCEM licenses, including Virtual Connect hardware and VCEM
packaged options.
Table 1 VCEM license options
License type Part number Description
VCEM software licenses 459864-B21 HP VCEM BL-c7000 Single enclosure

license
459865-B21 HP VCEM BLc7000 Single flexible

quantity license—covers multiple
enclosures
459866-B21 HP VCEM BLc7000 Tracking license –

quantity license used only with a current
AKA
T9094AAE HP VCEM BLc7000 E-LTU—

Electronically delivered license (email)
that can cover single or multiple c7000
enclosures
459867-B21 HP VCEM BLc3000 Single enclosure

license
459868-B21 HP VCEM BLc3000 Single flexible

quantity license—covers multiple
enclosures
459869-B21 HP VCEM BLc3000 Tracking

license—Quantity license used only with
a current AKA
T9095AAE HP VCEM BLc3000 Encl E-LTU single

or multiple licenses
605865-B21 HP Virtual Connect FlexFabric 10/24

Enterprise Edition BLc7000 1
662048–B21 HP Virtual Connect Flex-10/10D

Enterprise Edition for BLc7000 Option2
1
Includes 2 x Virtual Connect FlexFabric modules and 1 x VCEM license for c7000
2
Includes 2 x HP Virtual Connect Flex-10/10D Ethernet modules plus 1 x VCEM BL-c7000 enclosure license
For more information, see “VCEM licensing” (page 42).
Architectural overview
This section provides an overview of the architecture, functionality, and operations of Virtual
Connect technology and VCEM.
HP Virtual Connect technology

VC is the preferred interconnect technology for HP BladeSystem environments. Virtual Connect is
used in place of traditional pass-through and managed switches to reduce costs and simplify blade
server connectivity to production LANs, SANs, and converged networks. VC virtualizes I/O
connections by putting an abstraction layer between the servers and their external networks, so
that LANs and SANs see NIC or HBA addresses presented by the VC modules instead of the default
burned-in interface addresses. VC provides several key advantages:
• Reduces physical server-to-network cabling, complexity, and leased network ports.
• Maintains constant end-to-end connections to preferred networks and fabrics.
• Enables administrators to wire LAN and SAN connections once and limit changes.
Architectural overview 11
• Allows network assignments to be preprovisioned even to empty server bay—enables rapid
server deployment and limits configuration errors.
• Separates server administration from LAN and SAN administration.
• Enables system administrators to be self-sufficient—Add, replace, or modify servers in minutes
to meet changing workload and business requirements without impacting production networks.
• Relieves LAN and SAN administrators from server-centric maintenance.
Figure 1 shows a comparison between tradition networks and VC networks.
Figure 1 Traditional network and Virtual Connect comparison
The VC architecture is integrated into every BladeSystem c-Class enclosure and built on industry
standards, allowing operations with a broad range of switch brands that includes Cisco, Brocade,
Juniper, BNT, and HP ProCurve. VC functionality is delivered using high performance VC Ethernet
and Fibre Channel modules that plug into the standard BladeSystem c-Class enclosure interconnect
bays. Each VC module provides dense port aggregation that turns multiple physical network
connections to each server into a few simple high-speed uplinks that greatly reduce infrastructure
complexity and costs. To the external networks, VC modules appear as regular pass-through
devices, but provide the benefits of integrated switching. HP BladeSystem enclosures configured
with VC Ethernet and Fiber Channel modules are referred to as VC Domains. A VC Domain is a
logical group that can be a single enclosure with up to 16 servers, or up to four physically linked
enclosures running up to 64 servers.
To establish server connections to LANs and SANs, VC uses server connection profiles in
combination with dynamic pools of unique media access control (MAC) addresses and world wide
names (WWN). A VC server profile is a logical grouping of server connection attributes that can
be assigned to any bay in a BladeSystem enclosure. When assigned to an enclosure bay, the
server in that bay assumes the attributes of the server profile which can include:
• MAC addresses for all NICs
• WWNs for all HBAs
12 Introduction
• Fibre Channel boot from SAN parameters
• Logical serial numbers
An important benefit of VC is that server connection profiles and associated attributes are assigned
to BladeSystem enclosure bays and not hard wired to individual servers. The physical server in
each bay uses the MAC and WWN assignments in the associated server connection profile instead
of its default burned-in NIC or HBA addresses. Using this model, even if a server is replaced, the
MAC and WWN assignments for the enclosure bay remain constant, and the change is invisible
to the network.
During VC installation, the LAN and SAN administrators are still responsible for defining the
networks, subnets, and storage LUNs the servers will use, but they no longer must be involved in
every server-centric change. Once implemented, VC allows system administrators to be more
self-sufficient, so they can add, replace, and modify servers in minutes without affecting LAN and
SAN availability or burdening network administration staff.
Managing HP Virtual Connect

To configure and manage VC resources, HP provides options for both small and large VC
environments.
HP Virtual Connect Manager

VCM is a simple web console built into the firmware of each VC Ethernet module, and is designed
to configure and manage a single VC Domain. A typical environment is up to 4 VC enclosures
that you do not plan to expand further.
HP Virtual Connect Enterprise Manager

VCEM is HP’s primary application that centrally manages server connections and provides workload
mobility for up to 250 VC Domains and thousands of servers across the datacenter.
A typical environment involves BladeSystems with more than one rack of enclosures. VCEM is
designed to scale as the infrastructure grows and simplifies the addition of new and bare metal
enclosures. Small configurations with goals to expand beyond a single server rack should use
VCEM from the beginning to get the most benefit. VCEM is designed for the following environments:
• Medium to large HP BladeSystem configurations using VC CMS
• HP BladeSystem environments extending to multiple locations
• Organizations requiring centralized control of server-to-network connectivity
• Organizations requiring rapid server workload assignment and recovery across enclosures.
Understanding VCEM operations

VCEM aggregates network connection management and workload mobility for hundreds of VC
Domains and thousands of blade servers into a single console. This scalable solution delivers
advanced VC management that builds on and integrates with other HP management tools, including
HP Systems Insight Manager, VC hardware, 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-in to Systems Insight Manager, and as a virtual server
guest.
The majority of VCEM operations are accessed through a dedicated home page which includes
the following core tasks:
• Discover and import existing VC Domains without system downtime.
• Aggregates individual VC address information for LAN and SAN connectivity into a centrally
administered VCEM address repository.
Managing HP Virtual Connect 13

• Create VC Domain Groups.
• Assign and unassign VC Domains to VC Domain Groups.
• Define server profiles and link to available LAN and SAN network resources.
• Assign server profiles to BladeSystem enclosures, enclosure bays, and VC Domain Groups.
• Change, move, or automatically failover server profiles to spare servers.
• Rapidly install new bare-metal HP BladeSystem enclosures by assigning it to a VC Domain
Group.
Figure 2 Virtual Connect Enterprise Manager home page
Figure 3 VCEM architecture overview
Using VCEM, system administrators can quickly deploy, replace and recover servers and their
associated workloads by assigning or reassigning the VC server connection profile to an enclosure
bay. The example in Figure 4 illustrates a server profile movement operation from “Server A” to
“Server C” using VCEM.
14 Introduction
NOTE: The LANs associated with each uplink port and the attributes of the VC server profile
remain exactly the same; only the location of the server profile has changed.
When a VC server connection profile is moved, the associated MAC, WWN, boot from SAN
parameters, and related workload always move with the server profile.
From the VCEM GUI, server profiles can be moved to a user-defined spare server. A server profile
can be moved manually from one VC Domain to any other VC Domain in the same VC Domain
Group, or to a different VC Domain Group, whether it is in the same rack, across the datacenter,
or at another location. A server profile move can be scripted within the same VC Domain only,
using the profile failover capability. The profile movement and failover functionality provided by
VCEM can be used to provide cost-effective server blade recovery, perform proactive hardware
maintenance with reduced downtimes, and control rapid server repurposing to meet changing
workload and application priorities. When moving VC server profiles, the fastest completion times
are achieved when the corresponding source and target servers are configured to boot-from-SAN.
The automated profile failover functionality delivered in VCEM requires a boot-from-SAN
environment.
Figure 4 VC server profile movement example
Understanding VCEM operations 15

2 Installing and configuring VCEM
This chapter describes how to install and configure VCEM.
IMPORTANT: This guide assumes that you have previously configured VC using the integrated
VCM, have read the HP Virtual Connect for c-Class BladeSystem User Guide, and understand its
concepts.
Understanding VCEM and VC firmware version compatibility

When planning an upgrade of VCEM software or VC firmware, it is important to consider which
versions of VC are supported by the version of VCEM in use as well as which versions of VC
firmware are compatible together in a VC Domain Group.
VCEM provides two types of support for VC, “Full” support and “Compatibility” support. Full
support means that the version of VCEM supports the features in the version of VC. An example
of full support is the enhanced VLAN capacity feature that was introduced in VC 3.30 and VCEM
6.3.1. Another example is the direct connect fabric type introduced in VC 3.7x and VCEM 7.1.1.
Table 2 shows which versions of VC firmware are fully supported by recent versions of VCEM. The
items in bold indicate support added in the release of VCEM. The items struck through indicate
where support for older versions of VC firmware was removed.
Table 2 Fully supported VC Firmware versions
VCEM version Fully supported VC firmware versions
6.3 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, and 3.18
6.3u1 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, 3.18, and 3.3x
7.0 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, 3.18, and 3.3x
7.1 3.15, 3.17, 3.18, 3.3x, 3.5x, and 3.6x
7.1.1 3.3x, 3.5x, 3.6x, and 3.7x
7.2 3.3x, 3.5x, 3.6x, 3.7x, and 4.0x
7.2.2 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, and 4.1x
7.3 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, and 4.1x
7.3.2 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.10, 4.2x
7.4 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.10, 4.2x, 4.3x
7.4.1 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.10, 4.2x, 4.3x, 4.4x
7.5 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.10, 4.2x, 4.3x, 4.4x
Compatibility support allows a newer version of VC firmware to behave like an older version by
the features it exposes. VC domains running a newer version of VC firmware can belong to the
same domain group as domains running older versions of VC firmware through compatibility
support. The VC domains in the group behave like the oldest version of VC firmware on any domain
in the group. As domains in the group are updated with new VC firmware, the “group firmware
mode” can be updated through the VCEM UI to take advantage of features delivered in the new
VC firmware.
Figure 5 shows how compatibility support allows VC Domains running different VC firmware
versions belong to the same VC Domain Group.

Figure 5 VC Domain compatibility support
In each case, the newer versions of VC will behave functionally like the oldest version of firmware
running on any VC Domain in the VC Domain Group. No features beyond those that are supported
by the oldest version of VC firmware in the VC Domain Group can be enabled on any of the VC
Domains in the VC Domain Group even if they are running a newer version of VC firmware. A
benefit of compatibility support is that installing the newer version of VC firmware makes available
any bug fixes that it contains.
Table 3 shows the versions of VC firmware that can be managed by recent versions of VCEM
whether using full support or compatibility support.
Table 3 VCEM VC firmware version full or compatibility support
VCEM Version Fully supported VC versions Compatibility supported VC versions
6.3 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, 3.3x, 3.5x, 3.6x
3.18
6.3u1 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, 3.5x, 3.6x, 3.7x1, 2, 4.0x, 4.1x, 4.2x,
3.18, 3.3x 4.3x, and 4.4x
7.0 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, 3.5x, 3.6x, 3.7x1, 2, 4.0x, 4.1x, 4.2x,
3.18, 3.3x 4.3x, and 4.4x
7.1 3.15, 3.17, 3.18, 3.3x, 3.5x, 3.6x 3.7x1, 2, 4.0x, 4.1x, 4.2x, 4.3x, and
4.4x
7.1.1 3.3x, 3.5x, 3.6x, 3.7x 4.0x, 4.1x, 4.2x, 4.3x, and 4.4x
7.2 3.3x, 3.5x, 3.6x, 3.7x and 4.0x 4.1x, 4.2x, 4.3x, and 4.4x
7.2.23 3.3x, 3.5x, 3.6x, 3.7x, 4.0x and 4.2x, 4.3x, and 4.4x
4.1x
7.3 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x 4.3x, and 4.4x
and 4.2x
7.3.2 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x, 4.4x

4.2x, and 4.3x4
7.4 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x, 4.4x

4.2x, and 4.3x
7.4.1 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x, Will be determined based on the future
4.2x, 4.3x, and 4.4x releases of VC firmware.
7.5 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x, Will be determined based on the future
4.2x, 4.3x, and 4.4x releases of VC firmware.
Understanding VCEM and VC firmware version compatibility 17

1
VC 3.7x enforces expanded VLAN capacity and requires that expanded VLAN capacity is enabled for a VC Domain
Group before the 3.7x VC Domain can be brought into VC Domain Groups configured for legacy VLAN support. The
Group Firmware mode must be 3.30 or higher before expanded VLAN capacity can be enabled.
2
3.7x or later will work in compatibility mode for VCEM 6.3u1, 7.0 and 7.1 (see Table 3 above) only if the group
firmware mode is greater than 3.3x.
3
VCEM 7.2.2 and SIM 7.2.2 require IPv4 connectivity
4
VCEM 7.3.2 supports VC 4.3x with the exception of UEFI boot support
The ability to run a mix of VC firmware versions in a VC Domain Group is based on the "group
firmware mode". This designates the functional level at which all the VC Domains in the VC Domain
Group behave. The group firmware mode is dictated by the oldest version of firmware of any VC
domain in the VC Domain Group. After upgrading the VC firmware, the administrator can decide
when to upgrade the group firmware mode. Once the group firmware mode has been updated,
the administrator can enable new features for the VC domains in the VC Domain Group. VC
Domains join the VC Domain Group at the group firmware level. A VC Domain is not allowed to
join the VC Domain Group if it has any features enabled beyond the features supported by the
group firmware mode.
Table 4 illustrates how the group firmware mode is determined based on the versions of VC firmware
installed on the VC Domains in the VC Domain Group.
Table 4 Determining group firmware mode
VC Domain Group firmware
Group name Domain A Domain B Domain C Domain D mode
GroupOne 3.18 3.30 3.30 3.60 3.15
GroupTwo 3.30 3.5x 3.60 3.7x 3.3x
GroupThree 3.60 3.7x 4.0x 4.1x 3.5x
GroupX 4.0x 4.1x 4.2x 4.3x 4.0x
GroupOne contains four domains running 3.18, 3.30, and 3.60 VC firmware. The group firmware
mode is 3.15 because of the 3.18 VC Domain in the VC Domain Group.
GroupTwo contains four VC Domains running 3.30, 3.5x, 3.60, and 3.7x. The group firmware
mode is 3.3x because 3.30 is the lowest version in the group.
GroupThree contains four VC Domains running 3.60, 3.7x, 4.0x, and 4.1x. The group firmware
mode is 3.50 because 3.60 is the lowest version in the group and 3.60 shares group firmware
mode with VC 3.5x.
GroupX contains four VC Domains running 4.0x, 4.1x, 4.2x, and 4.3x. The group firmware mode
is 4.0x because 4.0x is the lowest version in the group.
The group firmware mode also is a factor when creating a VC Domain Group based on a VC
Domain running a newer version of VC firmware than what is fully supported by the version of
VCEM managing the VC Domain Group. In this case, VCEM automatically sets the group firmware
mode when creating the VC Domain Group. VCEM sets the group firmware mode to the highest
firmware version that is fully supported by the version of VCEM being used to create the VC Domain
Group.
Table 5 shows the group firmware mode that will be set by recent versions of VCEM when the VC
Domain Group is created using a more recent version of VC firmware.
Table 5 Group firmware mode with recent versions of VC firmware
VCEM version Later firmware versions Resulting group firmware mode
6.3 3.3x, 3.5x, 3.6x 3.15
6.3u1 3.5x, 3.6x, 3.7x 3.3x

Table 5 Group firmware mode with recent versions of VC firmware (continued)
VCEM version Later firmware versions Resulting group firmware mode
7.0 3.5x, 3.6x, 3.7x 3.3x
7.1 3.7x 3.5x
7.1.1 4.0x 3.7x
7.2 and 7.2.2 4.1x, 4.2x 4.0x
7.3 4.3x 4.2x
7.3.2 4.3x 4.2x
7.4 4.4x 4.3x
7.4.1 and 7.5 Will be determined based on the 4.4x

future releases of VC firmware.
Creating a VC Domain Group based on a VC Domain running a newer version of VC firmware

requires that no features are enabled in the VC Domain that are beyond those supported by the
version of VCEM managing the VC Domain Group. For example, attempting to create a VC Domain
Group with VCEM 6.3 based on a domain with 3.30 installed and enhanced VLAN capacity
enabled will not succeed.
Preparing for a VCEM installation

IMPORTANT: Starting with Insight Management 7.2, you must run VCEM on a 64-bit operating
system.
If you are upgrading your CMS and have VCEM 7.3 to 7.5 running on a 64-bit operating system,
you can directly update installations with the HP Insight Management DVD. Figure 6 shows the
32-bit to 64-bit operating system update path.
Figure 6 Update path
IMPORTANT: VCEM 7.5 does not support VC firmware versions prior to VC 3.30. If you have
versions of VC firmware before 3.30 installed, an incompatible firmware icon is displayed, and
VCEM prevents most VC Domain, VC Domain Group, and server profile operations. You must
upgrade to VC firmware 3.3x. See “Upgrading incompatible firmware modes and versions” (page
27) for more information. While VCEM does not support older firmware versions, both VCEM and
the Insight Managed System Setup Wizard will not prevent you from licensing these firmware
versions.
For a list of VCEM and Insight Management requirements see the HP Insight Management Support
Matrix at http://www.hp.com/go/insightsoftware/docs.
Preparing for a VCEM installation 19

Installation prerequisites
VC firmware browser support
Ensure that you have the right browser before installing VCEM. Table 6 lists browser support by
VC firmware version.
Table 6 VC firmware browser support
VC firmware
version Internet Explorer version Firefox Version Google Chrome
3.30 7.x and 8.x 3.x NA
3.5x 8.x and 9.x 6.x and 7.x NA
3.60 8.x and 9.x 9 and 10ESR NA
3.7x 8.x and 9.x 9, 10ESR and 11 NA

1
4.0x 8.x, 9.x and 10 9, 10ESR and 17ESR NA
4.1x 9.x, 10 and 11 17, 22 NA
4.2x 9.x, 10 and 11 17, 22 NA
4.3x 8.x, 9.x, 10 and 11 17, 22 NA
4.4x 8.x, 9.x, 10 and 11 17, 22, 31.x, 33.x, and NA

35.x
1
The iSCSI boot configuration web GUI is not supported in IE compatibility mode.
IMPORTANT: The use of VCEM web GUI in browser compatibility mode is not recommended as
some configurations are not supported in this mode. It is strongly recommended to disable
compatibility view to have a better experience during navigation.
Mixed VC firmware versions and compatibility in a VC Domain Group

VCEM enables firmware compatibility using current and future versions of VC firmware. This feature
provides both backward and forward VC firmware compatibility.
Backward compatibility for VC firmware

You can install VCEM 7.5 and run the latest VC firmware in a VC Domain Group that has an
earlier but supported firmware mode.
IMPORTANT: The minimum supported firmware version in VCEM 7.5 is VC firmware 3.3x. If
you are upgrading from an earlier VCEM version managing VC Domains that have a VC firmware
version older than 3.3x, VCEM will mark those VC Domains and VC Domain Groups with an
incompatible firmware status.
You must upgrade the VC Domain firmware and the VC Domain Group firmware mode to 3.3x
or later before you can manage those VC Domains and VC Domain Groups with VCEM 7.5.
Table 7 displays VC Domain Group firmware compatibility.
Table 7 VC Domain Group firmware compatibility
VC Domain VC Domain VC Domain VC Domain VC Domain VC Domain VC Domain VC Domain
Group Group Group Group Group Group Group Group
VC firmware firmware firmware firmware firmware firmware firmware firmware
firmware mode 4.4x mode 4.3x mode 4.2x mode 4.10 mode 4.0x mode 3.7x mode 3.5x mode 3.3x
4.4x Yes Yes Yes Yes Yes Yes Yes Yes
4.3x Yes Yes Yes Yes Yes Yes Yes Yes

Table 7 VC Domain Group firmware compatibility (continued)
VC Domain VC Domain VC Domain VC Domain VC Domain VC Domain VC Domain VC Domain
Group Group Group Group Group Group Group Group
VC firmware firmware firmware firmware firmware firmware firmware firmware
firmware mode 4.4x mode 4.3x mode 4.2x mode 4.10 mode 4.0x mode 3.7x mode 3.5x mode 3.3x
4.2x No No Yes Yes Yes Yes Yes Yes
4.1x No No No Yes Yes Yes Yes yes
4.0x No No No No Yes Yes Yes Yes
3.7x No No No No No Yes Yes Yes
3.5x/3.6x No No No No No No Yes Yes1
3.30 No No No No No No No Yes1
1
If enhanced VLAN capacity is enabled for the VC Domain being added to a VC Domain Group, the VC Domain group
must also have enhanced VLAN capacity enabled.
Forward compatibility for VC firmware

VCEM enables firmware compatibility using current and future versions of VC firmware. For
example, VCEM 7.5 can support future VC firmware versions (when available) in compatibility
mode. This depends on the firmware mode of the VC Domain Group you are trying to add the VC
Domain with the newer VC firmware version into. See Section for more information.
Selecting HP Virtual Connect Enterprise Manager ports

Before you install VCEM, check Table 8 to ensure you have the correct ports open to allow
communication.
NOTE: Table 8 is based on the assumption that HP Virtual Connect Enterprise Manager is behind
the firewall of the CMS.
Table 8 VCEM ports
CMS Managed System Port Protocol1 Description
In2 Out In Out
Y Y 443 SSL Communication

with VCEM
Y Y 22 SSH This port is

needed to
establish a
connection
through SSH
using CLI
Y Y 161 SNMP (UDP) SNMP

Agent/Poll
Y 162 SNMP Trap Trap listener

(UDP)
Y 69 UDP TFTP—Used for

upload and
configuration
backup from CLI
Y 20, 21 TCP FTP—Used for

upload and
configuration
backup from CLI
Installation prerequisites 21
Table 8 VCEM ports (continued)
CMS Managed System Port Protocol1 Description
Y 636 TCP LDAP

Authentication
Y 514 UDP SYSLOG
Y 1812, 1813 UDP RADIUS server if

configured
Y 49 TCP TACACS server

if configured
1
All ports are used for TCP and UDP.
2
The CMS normally has all managed system ports open, as the CMS is a managed system itself. Firewalls can be configured
to block these ports if the CMS is not to be managed from another system.
Installing VCEM
When you are upgrading to a new and different CMS, or are moving to a 64-bit CMS, you might
need to migrate your data by using the Systems Insight Manager data migration tool. If you are
upgrading to a new version of VCEM on the same CMS, data migration with the Systems Insight
Manager data migration tool is not necessary. For more information, see the HP Insight Management
Installation and Configuration Guide.
To install VCEM, follow the steps provided in the HP Insight Management Installer. To access HP
Insight Management online help, click the ? icon in the upper right-hand corner of the window.
Updating VC firmware
VCEM allows you to update VC firmware simultaneously across multiple VCEM managed VC
Domains using VC Domain Firmware Update.
CAUTION: VC Domains with a status of Fail to communicate with VC domain/Disabled enclosure

or Missing external manager lock/Communication established with disabled enclosure can be
selected because they have a transient status. The VC Domain can restore communication with
VCEM or restore the lock before Enable Firmware Update is allowed. If the Fail to communicate
or Missing external manager lock statuses still occur, enabling the firmware update is still allowed
and fails as a consequence.
CAUTION: Firmware Update mode does not allow changes using the VCM user interface. If
changes to VCM are desired, use VCEM Domain Maintenance mode. When using Firmware
Update mode on a VC Domain, do not use VCM CLIs to remove or suspend external manager
locks.
To update VC Firmware:

1. Select the VC Domains that are targeted for firmware updates.
NOTE: Using the firmware update workflow requires VCSU 1.8.0 or later and the VC
Domains being updated must be running VC 3.50 or later. Otherwise, enable maintenance
mode on the VC Domain in preparation for updating the VC firmware with VCSU.
Figure 7 VC Domain tab page
2. Select VC Domain Firmware Update... and all the VC Domains selected are displayed.
3. Select Enable Firmware Update... (Figure 8).
NOTE: VC Domain Firmware update will stay enabled until all VC Domains selected display
the Firmware update status.
Figure 8 Enabling firmware updates
A message similar to the following is displayed:
Figure 9 Firmware update message
Updating VC firmware 23
After the job completes, use the VCSU to perform the firmware update and then proceed to
Step 4.
4. Check mark the targeted VC Domains on the VC Domain tab and select VC Domain Firmware
Update... again.
NOTE: If another VC Domain with a status other than Firmware update is selected, the VC
Domain Firmware update button is disabled.
5. Select Complete Firmware update to finish the firmware update process (Figure 10).
Figure 10 Completing the Firmware Update process
You may want to upgrade the VC Domain Group firmware after updating the VC firmware. See
“Upgrading VC Domain Group firmware mode” for more information.
Updating to VC firmware 3.7x or later

CAUTION: Do not update to VC firmware 3.7x or later if the VC Domain Group firmware mode
is 3.15. This is because VC firmware 3.7x or later is not compatible with VC firmware 3.15. If
you update to VC firmware 3.7x or later, your only options are to either remove the updated VC
Domain from the VC Domain Group, or to use VCSU to downgrade the VC Domain firmware to
the previous version.
HP recommends that you update to the VC Domain Group firmware version to VC firmware 3.30
or later before attempting to update a VC Domain in the VC Domain Group to VC firmware 3.7x
or later. For more information, see “Updating VC firmware versions in a VC Domain to be
compatible with VC 3.7x or later”.
If you are running firmware with the HP 1/10Gb VC-Enet module or the HP 1/10Gb-F VC-Enet
module you will need to replace those with one of the following modules to update to VC firmware
3.7x or later:
• HP VC Flex-10 Enet Module
• HP VC FlexFabric 10Gb/24-Port Module
• HP VC Flex-10/10D Module
For information on replacing modules, see “Replacing VC modules”.
Updating to VC firmware 4.1x

The HP 4Gb VC-FC module is not supported by VC firmware versions 4.1x and later. You must
replace these modules with HP Virtual Connect 4Gb FC Modules to update to VC firmware 4.1x
or later.
For information on replacing modules, see the “Replacing VC modules”.

Removing VCEM
WARNING! Removing VCEM could have significant implications. Before removing VCEM, verify
that no other upper-level management products, such as HP Matrix Operating Environment, are
using VCEM capabilities. Uninstallation of VCEM requires a release of all VC Domains. Removing
VCEM also removes all VCEM-centric historical tracking of individual WWNs and MAC addresses.
IMPORTANT: Before you remove VCEM, ensure that you have removed all VC Domains from
the VC Domain Groups that are under VCEM control. Otherwise, VCEM removal will not be
successful. For more information, see “Removing a VC Domain from a VC Domain Group”.
To remove VCEM:
1. Choose from one of the following options:
• Select Start→All Programs→HP Insight Management→Uninstall HP Insight Management,
and then select HP Virtual Connect Enterprise Manager.
• From the Control Panel, click Add or Remove Programs, select HP Insight Management,
and then click HP Virtual Connect Enterprise Manager.
2. Confirm the removal.
After removing VCEM, some files might not be removed. Manually removing such files might
cause an access denied error message. If this occurs, reboot the server where VCEM is
installed, and then remove the files.
3. The removal logs are located in the %systemdrive%\HPIC\logs\timestamp folder. The
%systemdrive% is the drive where the operating system is installed (such as C:) and the
timestamp identifies the system clock time stamp.
Performing post-installation configuration tasks

Post-installation configuration tasks
If you are installing VCEM for the first time, perform the following post-installation tasks.
1. Verify that the VC module and HP Onboard Administrator firmware for all VC Domains to be
managed by VCEM meets the minimum requirements. For a complete list of hardware, firmware,
and software requirements, see “Preparing for a VCEM installation” (page 19).
2. Choose one of the following options:
• Select Start→ All Programs→HP Virtual Connect Enterprise Manager→HP Virtual Connect
Enterprise Manager
• Select 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.
3. Enter the credentials that you entered when performing the installation. The VCEM home page
appears.
• If an HP SIM discovery of Onboard Administrators has been performed, all VC modules
appear.
• If an HP SIM discovery has not been previously performed, and no VC modules appear,
perform an HP SIM discovery before continuing.
1. Discover the Onboard Administrator IP addresses with enclosures that have VC
Ethernet modules.
2. Click VC Domains to verify whether any VC Domains have been discovered.
For more information about performing an Systems Insight Manager discovery, see
the HP Systems Insight Manager User Guide
Removing VCEM 25
4. (Optional) If you are installing VCEM as part of the HP Insight Management suite, access the
Insight managed system setup wizard after performing an Systems Insight Manager discovery
and complete the steps in the wizard. You can also run the Insight Managed System Setup
Wizard as part of the HP Insight Management suite to set up systems such as applying VCEM
licenses to systems you want to manage. For more information about the wizard, see the HP
Insight Management Installation and Configuration Guide.
5. (Optional) Configure the MAC addresses to match the needs in the data center.
NOTE: It is optional to set up a user-defined range in VCEM. This is only required if you are
managing VC Domains which use special user-defined MACs.
a. Click Home from the VCEM home page. In a stand-alone VCEM installation, click Home
on the upper right-hand corner of the window to return to the home page.
b. Click the MAC Addresses hyperlink.
c. Click Add custom to create a custom range.
The MAC address range used by the VCEM Domain must be unique within the
environment. HP provides a set of predefined ranges that are reserved for use by VC and
VCEM, and does not conflict with server factory-default MAC addresses.
When using the HP-predefined MAC address ranges, ensure that each range is used only
once within the environment.
For more information, see “Managing MAC and WWN addresses” (page 128).
6. (Optional) Create MAC exclusion ranges. For more information, see “Creating MAC exclusion
ranges” (page 129).
NOTE: Creating exclusion ranges is optional but highly recommended to avoid MAC/WWN
address conflicts in the same network.
HP recommends using exclusion ranges in the following scenarios:
• When VC Domains are not VCEM controlled and are using other user-defined MAC or
WWN addresses that overlap with VCEM user-defined MAC or WWN ranges. For
example:
VCEM exclusion ranges need to be created for MAC or WWN addresses used by other
VC Domains.
• When installing multiple instances of VCEM in the same network. For example:
Exclusion ranges need to be created for VCEM-defined MAC and WWN addresses.
7. (Optional) Use the following procedure to configure the WWN ranges to meet your
requirements.
NOTE: It is optional to set up a user-defined range in VCEM. This is only required if you are
managing VC Domains which use special user-defined WWNs.
a. Click Home from the VCEM home page. To return to the home page in a stand-alone
VCEM installation, click the Home link on the upper right-hand corner of the window.
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
provides a set of predefined ranges that are reserved for use by VC and VCEM, and
does not conflict with server factory-default WWNs.
When using the HP-predefined WWN ranges, ensure that each range is used only once
within the environment.
For more information, see “Adding a custom WWN address range” (page 138).

8. (Optional) Create WWN exclusion ranges. For more information, see “Creating WWN
exclusion ranges” (page 132).
NOTE: HP recommends using exclusion ranges in the following scenarios:

• When VC Domains are not VCEM-controlled and are using other user-defined MAC or
WWN addresses that overlap with VCEM user-defined MAC or WWN ranges. For
example:
VCEM exclusion ranges need to be created for MAC or WWN addresses used by other
VC Domains.
• When installing multiple instances of VCEM in the same network. For example:
Exclusion ranges need to be created for VCEM-defined MAC or WWN addresses.
9. Click the VC Domains tab. VC Domains appear as the following:

• Unconfigured VC Domains—Appear as VCD_name, where name is the temporary name
automatically given to the VC Domain.
• Configured VC Domains—Appear with the VC Domain name.
10. Select a VC Domain, and then click License to license the domain. For more information on
licensing, see “VCEM licensing” (page 42).
11. Create a new VC Domain Group, and then add one or more already-licensed VC Domains
to it. For more information on creating a new VC Domain Group, see “Creating a VC Domain
Group” (page 43).
IMPORTANT: In a new environment, when adding VC Domains to into the VC Domain

Group, you must have one configured VC Domain. Any additional VC Domains can remain
nonconfigured as they are automatically configured by VCEM. For an environment with
existing, already configured VC Domains, create a VC Domain Group for the VC Domains.
You can continue using VCEM and its additional functions such as creating server profiles and
assigning them to bays.
VCEM uses a SSL connection provided by Systems Insight Manager. For more information about
the available cipher suites and how to enable or disable them, see the Understanding HP SIM
security white paper at http://h18013.www1.hp.com/products/servers/management/hpsim/
infolibrary.html.
VCEM uses the same TCP ports as Systems Insight Manager. VCEM does not open any other TCP
ports.
Upgrading incompatible firmware modes and versions

If unsupported VC Domain firmware versions are detected at the end of a VCEM 7.5 upgrade, a
warning message similar to the following is displayed:
VCEM detected unsupported VC firmware. For information on how to upgrade
your firmware, run the Insight Software Advisor or refer to the VCEM
User Guide troubleshooting section.
Upgrade to a supported VC firmware by performing the following steps:
1. Select the VC Domain with an incompatible status and click VC Domain Maintenance.
2. Click Make Changes via VC Manager.
3. Upgrade the managed VC Domains to the minimum VCEM supported VC firmware version.
See the “Mixed VC firmware versions and compatibility in a VC Domain Group ” for the
VCEM-supported VC firmware versions.
4. Click Complete VC Domain Maintenance to close the operation.
Performing post-installation configuration tasks 27

5. Upgrade the VC Domain Group firmware mode to the minimum VCEM-supported VC firmware.
For more information, see “Upgrading VC Domain Group firmware mode” (page 84).
Installing VCEM in an HA-clustered CMS configuration in a Microsoft

Cluster Server cluster
VCEM can be installed in an HA clustered CMS configuration on an MSCS cluster. This installation
is described in Installing and Upgrading HP Insight Management 7.0 on Windows Server 2008
R2 Failover Clusters. This white paper is accessible in the HP Insight Management documentation
library at HP Enterprise Information Library
By installing in a failover cluster configuration, the CMS can fail over to a backup cluster node if
the primary node needs maintenance or experiences a failure.
In preparation for a planned failover, ensure that no Insight Management jobs, tasks, requests, or
migration processes are running at the time of the failover. The configuration of the managed
environment should not be changed between powering off the CMS on the primary node and
resuming operations on the backup cluster node.
In the event of an unplanned failover, it is possible that manual intervention may be required to
restore full operations. If a VC Domain reports configuration mismatch or an out-of-sync occurrence
after recovering from an unplanned failover, the following actions are recommended.
• Execute Mxsync in analysis mode (mysync) to determine the nature of the failure on the VC
Domain during the CMS recovery phase.
• Execute Mxsync in execute mode (mxsync-e) during the CMS recovery phase, and follow
the Mxsync instructions until the VC Domains are synchronized.
• If Mxsync detects and reports out-of-sync scenarios in additional subsystems, resolve them
according to instructions displayed, otherwise exit Mxsync.
NOTE: Executing mxsync –e will help resolve VC Domain synchronization issues across multiple
VC domains.

3 Managing VC Domains
This chapter 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 shows all VC Domains.
Figure 11 VC Domains window
Table 9 (page 29) lists the columns on the VC Domains page.

Table 9 VC Domains page
Item Description
VCEM Status Describes VCEM status for the VC Domain
VC Domain Name Identifies the VC Domain name
VC Manager Identifies the domain IP address for the primary VC Ethernet

module
Enclosure Identifies the enclosure name for each enclosure in the VC

Domain
VC Domain Group If the domain is a member of a VC domain group, this

column identifies the VC Domain Group name.
Table 10 (page 29) describes VC Domain status icons and descriptions.

Table 10 VCEM status icons
Status Icon Description
Not licensed (no icon) The VC Domain enclosures have not

been licensed.
Licensed The VC Domain enclosures have been

licensed to VCEM.
Fail to communicate to VC Failed to connect to the VC Domain.

Domain/Disabled enclosure Possible causes include:
• Connection times out.
• Ethernet VC Module is physically not
available.
• VCM failed.
• When firmware update is taking
place.
• VC Ethernet IP address has changed
(through DHCP or EBIPA
configuration).
29
Table 10 VCEM status icons (continued)
Missing external manager VCEM is unable to obtain the necessary

lock/Communication established with permissions for External Manager user.
disabled enclosure VCEM might have lost the External
Manager lock at the VC Domain.
Expired license The VC Domain enclosure has an

expired license.
Managed by VCEM The VC Domain is part of a VC Domain

Group and operating normally.
Configuration mismatch The VC Domain configuration has

changed and does not match the VC
Domain Group configuration.
Under maintenance VC Domain is unlocked for domain,

network, and storage changes through
VCM. After completing the domain,
network, and storage changes, confirm
the new VC Domain configuration in
VCEM by exiting maintenance mode.
VCEM operations related to this VC
Domain or its VC Domain Group, such
as create server profile, move server
profile, server profile failover, and so
on, are blocked while the VC Domain
is under maintenance.
Incompatible firmware This status is displayed after a VCEM

upgrade and indicates that an
incompatible firmware mode and
version was detected. Only the
following VCEM VC Domain operations
are permitted for resources with an
incompatible status:
• Remove VC Domain from Group
• Delete VC Domain Group
• Perform VC Domain Maintenance
• Upgrade VC Group firmware Mode
See “Upgrading incompatible firmware
modes and versions” to upgrade to a
supported firmware.
Firmware Update The managed VC Domain is in

firmware update mode.
For information on how to resolve status issues, see “Troubleshooting VCEM” (page 149).
To display the properties of a particular VC Domain, click the VC Domain name. Properties include
the primary IP address, status, VC firmware version, Ethernet networks, Shared Uplink sets, Fibre
Channel SAN fabrics, Ethernet and Fibre Channel common settings, and SNMP Ethernet and Fibre
Channel alert destinations.
Requirements for adding a VC Domain to a VC Domain Group

To add a configured VC Domain to a VC Domain Group, the following requirements must be met:
• Multienclosure VC Domains must be configured and match the minimum number of enclosures
required by the VC Domain Group. The Ethernet uplinks used by each enclosure define the
minimum number of enclosures. For more information about multienclosure VC Domains, see
“Working with multienclosure VC Domains”.
• VC Domain names must not already exist in VCEM.
• Server profile names must not already exist in VCEM.
• MAC or WWN addresses or serial numbers that are assigned to a server profile must not be
in use by VCEM or in a VCEM exclusion list. If the MAC or WWN addresses or serial numbers
are user-defined, then you must also identify a user-defined address range in VCEM.
• If the VC Domain contains server profiles, the MAC addresses, WWNs, and the serial numbers
allocated must 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 VC Domain Group with VCEM-defined range types, and user-defined range types. To
add a VC Domain to a VC Domain Group with factory-default range types, all server
profiles of the VC Domain must be configured with factory-default addresses.
NOTE: If the VC Domain or VC Domain Group screen is displaying an incompatible

firmware status after upgrading from an older VCEM version, upgrade the VC firmware
for the affected VC Domains to make changes. See “Upgrading incompatible firmware
modes and versions” for more information.
◦ A VC Domain containing server profiles with addresses allocated as user-defined range

type can be added to a VC Domain Group with a user-defined or VCEM-predefined
range type. A user-defined (custom) MAC and WWN range that includes all addresses
allocated to server profiles within the VC 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
type can be added to a VC Domain Group with an VCEM-predefined or a user-defined
range type.
◦ An unconfigured VC Domain without server profiles has no range type restrictions when
adding in a VC Domain to a VC Domain Group.
Table 11 (page 31) summarizes MAC or WWN addresses, and serial number range type
compatibility when adding a VC Domain to a VC Domain Group.
Table 11 MAC or WWN address and serial number range compatibility
VC Domain server profiles with MAC
or WWN addresses or serial number MAC or WWN or serial number in VC
allocated as: Domain Group VCEM-supported
VCEM-defined VCEM-defined or user-defined Yes
User-defined User-defined Yes, as long as it belongs to the same

User-defined range
User-defined VCEM-defined Yes, if a User-defined range is created

on VCEM
Factory (MAC or WWN address) Factory, VCEM-defined or Yes

User-defined
HP-predefined VCEM-defined Yes
HP-predefined User-defined Yes, if a User-defined range is created

on VCEM
VCEM-Defined, HP-predefined, or Factory No

User-defined
Requirements for adding a VC Domain to a VC Domain Group 31

VCEM validates the following components when adding a VC Domain to a VC Domain group,
therefore the VC Domain configuration must be identical to the VC Domain Group configuration.
Verify that the following components 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)
• Network Access Groups
◦ Name(s) and networks
• Ethernet and iSCSI Flex-10 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
◦ 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
◦ Port Throughput Statistics
◦ VLAN Capacity
– Legacy VLAN capacity or Expanded VLAN capacity
• 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
◦ Network Access Groups (associated with this network)

• Number of networks configured in the VC Domain
• For each shared network uplink:
◦ Uplink set name
◦ Connection mode
◦ Number of VLANs tagged associated with the shared network uplinks

• Number of shared networks configured in the VC Domain
• For each VLAN-tagged associated with the shared network uplink:
◦ Network name
◦ Network state
◦ VLAN ID
◦ Native
◦ Smart Link
◦ Private network
◦ Preferred Link Connection
◦ Preferred Link Connection Speed
◦ Maximum Link Connection

◦ Maximum Link Connection Speed

• For each Fibre Channel SAN Fabric:
◦ Fabric name
◦ Fabric port location
◦ Configuration speed
• 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
VC 4.4x features that must be disabled in a VC Domain to be part of a VC Domain

Group with VC firmware 4.3x
The following are the list of VC 4.4x features that must be disabled in a VC Domain to be part of
a VC Domain Group with VC firmware 4.3x:
• Non default SR-IOV setting.
• Tagged LLDP — This feature enables LLDP daemon to send LLDP frames with a VLAN tag to
the configured FlexNIC server ports.
• Virtual Connect 16Gb 24 Port fiber channel modules are not supported in a VC Domain
Group with group firmware mode 4.3x.
• UEFI Boot order is not supported. Do not configure profiles with UEFI boot order checked on
VC Domain.
Figure 12 UEFI Boot order

• The FlexFabric-20/40 F8 modules are not supported in a VC Domain Group with group
firmware mode 4.1x.
• The SNMPv3 is not supported. Do not configure SNMP Access items or Trap destination to
use SNMPv3.
Figure 13 SNMPv3
• FIPS Mode is not supported. The VC GUI will include an icon to indicate FIPS mode. The VCM
CLI alters the prompt to indicate when the domain is in FIPS mode.
• 4k VLAN is not supported. Do not add a VC Domain containing more than 1000 networks
to a VC Domain Group whose group firmware mode is 4.1x.
• The Hide Unused FlexNICs check box is not supported. Do not configure server profiles with
the Hide Unused FlexNICs option checked. (See Figure 14).
Figure 14 Hide unused FlexNICs option
To disable this feature, edit the server profile and uncheck the Hide Unused FlexNICs check
box. If the server profile is assigned to a server that is powered on, ensure that the server is
powered off before editing the server profile.
• IPv6 SNMP is not supported. Do not configure any SNMP Access items or trap destination
using IPv6 (see Figure 15).
Figure 15 SNMP access and trap destinations
To disable this feature, delete all the items in the SNMP access and trap destinations tables
that are configured to use IPv6 addresses.

Group with VC firmware 3.7
The following features are not supported:
• Dual-Hop FCoE
Do not configure VC Domains with FCoE networks or server profiles with FCoE connections
linked to Flex-10/10D modules. Each FCoE network is associated to one FCoE Uplink Set.
“Removing FCoE networks” displays FCoE networks with associated Uplink Set.
Figure 16 Removing FCoE networks
To disable Dual Hop FCoE, delete all existing FCoE networks. However, do not delete the
FCoE Uplink Set. After removing a FCoE network, the Uplink Set is automatically switched
from FCoE to Ethernet. Also update the server profiles by removing the FCoE connections that
are linked to Flex-10/10D modules.
• LACP timers
Do not configure LACP timers in VC Domains, Uplink Sets, or networks with a Long (30 sec)
value. For VC Domain configurations (see Figure 17) there are two possible values:
◦ Short (1 second)
◦ Long (30 second)

For network (see Figure 18) and Uplink Set (see Figure 19) there are three possible values:
◦ Domain-Default which is either Short (1 second) or Long (30 second)
◦ Short (1 second)
◦ Long (30 second)

When the LACP timer configuration is set to long in VC Domains, all Uplink Sets and networks
with a default are automatically using Long (30 sec).
Figure 17 VC Domain LACP timer configuration

Figure 18 Ethernet Network LACP timer configuration
Figure 19 Uplink Set LACP timer configuration
To disable this feature:

1. Change the VC Domain LACP timers from Long (30 sec) to Short (1 sec).
2. Change each network and uplink set configuration from Long (30 sec) to Domain
Default,Short (1 sec) or Short (1 sec)
• IGMP Multicast Filter Sets or Multicast filters
Do not configure IGMP Multicast Filter Sets or Multicast filters in VC Domains. Server profiles
must not have Ethernet connections assigned to IGMP Multicast Filter Sets or Multicast filters
(see Figure 20, Figure 21, and Figure 22).
Figure 20 Server profile configured with IGMP Multicast Filter Set or Multicast filter
Figure 21 VC Domain configured with a IGMP Multicast Filter Set
Figure 22 VC Domain configured with IGMP Multicast filter
To disable this feature, it is necessary to first remove the Multicast Filter Sets and then remove
the Multicast filters.
1. Remove the association between server profile Ethernet connections and Multicast Filter
Sets or Multicast filters by selecting None in the Multicast Filter column (see Figure 20) .

2. Remove the Multicast Filter Sets and then remove the Multicast filters (see Figure 21, and
Figure 22).
• Customized QoS configuration
Do not configure “QoS Configuration Type” with Custom (with FCoE Lossless) or Custom
(without FCoE). Those options are displayed in Figure 23.
Figure 23 VC Domain customized QoS configuration types
To disable this feature, select Passthrough as the QoS Configuration Type

• VC user role permissions
With VC 4.0x, you can provide permissions to grant access to operations for specific roles.
To disable this feature in a VC Domain to be part of a VC Domain Group with VC firmware
3.7 or earlier, do not customize user roles in the targeted VC Domain. Figure 24 displays
customizing user role operations.
Figure 24 VC domain with customized role operations
To disable this feature, click Select Factory Default Role Operations and the default permissions
are restored.

Group with VC firmware 3.5x and 3.6x
The following features are not supported:
• HP Virtual Connect Flex-10/10D Modules
• Direct Attach storage
Figure 25 SAN fabrics with direct attach fabric type
To disable this feature delete all direct attach SAN fabrics.

• The SNMP access feature is not supported. To disable this feature delete all the items on the
SNMP access table. See Figure 26 for more information.
Figure 26 SNMP access configuration
VC 3.7x, 3.6x and 3.5x features that must be disabled in a VC Domain to be part
of a VC Domain Group with VC firmware 3.3x
All VC 3.5x, 3.6x, and 3.7x features must be disabled for VC Domain Groups with firmware mode
3.3x to add 3.7x back into the 3.3x VC Domain Group.
VC 3.5x feature that must be disabled in a VC Domain to be part of a VC Domain

Extra FC or FCoE connections are not supported.
Do not configure server profiles with more FC SAN Connections or FCoE Connections than
redundant connections per Virtual Connect Fibre Channel or Virtual Connect Flex Fabric modules
available in the VC Domain. The extra FC SAN or FCoE connections display additional connections
pointing to bays 1 and 2 (in the FCoE connection list) and bays 3 and 4 (in the FC connection list,
for C3000 enclosures only) in the “Connected To” column. See Figure 27 (page 42) for more
information.

Figure 27 Removing FC and FCoE connections in 3.5x
To disable this feature, delete the additional FC SAN connections or FCoE connections (that exceeds
the 4 redundant connections to each Virtual Connect Fibre Channel/Virtual Connect FlexFabric
Module) from the server profile.
VC Domain tasks
From the VC Domains page, you can perform the following tasks:
• License an enclosure.
• Create a VC Domain Group.
• Add a VC Domain to a VC Domain Group.
• Remove a VC Domain from a VC Domain Group.
• Work with multienclosure VC Domains
• Perform VC Domain maintenance.
• Cancel VC Domain maintenance.
• Resynchronize a VC Domain with a Configuration Mismatch status.
• Recover server profiles
• Update VC firmware
• Delete a VC Domain Group
• View VC Domain details
VCEM licensing
You must purchase a license for each enclosure you want to manage. For licensing information,
see the VCEM QuickSpecs at http://www.hp.com/go/vcem.
To enable a VC Domain license, perform one of the following procedures:
• For new VC Domain Groups:
1. Click New VC Domain Group on the VC Domains page.
Both licensed and unlicensed VC domains are displayed.
2. Click Add Key and enter the key string.
3. Select one or more unlicensed VC Domains.
4. Click Apply License.
5. Click OK to validate the key string.
NOTE: License key fields are case-sensitive

If the key string is valid, the key is added to HP Insight Management.
6. Click Next to provide VC Domain credentials.
• For existing VC Domain Groups:
1. Select the VC Domain from the VC Domains page, 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, it is added to Systems Insight Manager. The License Enclosure
page reappears, displaying the number of available licenses.
4. Select the VC Domain to which you want to apply the VCEM license.
The VC Domains page reappears, displaying an updated informational status of the VC
Domains.
For more information, see “Product licensing” (page 10).
Preparing to create a VC Domain Group

In defining a VC Domain Group, consider hardware and firmware update paths. Smaller VC
Domain Groups allow smaller units to update while larger VC Domain Groups have less
management touch points. Larger VC Domain groups take longer to propagate configuration
changes when completing maintenance mode. More fully configured VC Domains take longer to
propagate than those with fewer network and storage connections.
If there are collections of VC Domains which are managed by different teams, it may be useful to
place them in separate VC Domain Groups and use VCEM RBAC settings to control administrative
access to the various VC Domains. Since all the VC Domains in a VC Domain Group share identical
uplink, SAN fabric, and VLAN definitions this can also place constraints on the size of VC Domain
Groups
Creating a VC Domain Group

You can create a VC Domain Group by selecting the VC Domains that you want to include in the
new VC Domain Group.
IMPORTANT: This VCEM operation does not provide a reference to the VC Domain from Systems
Insight Manager. To access this reference, you must correlate the Systems Insight Manager and
VC logs. For more information, see Correlating VCEM operations in Systems Insight Manager and
VC logs.
VCEM supports multienclosure VC Domains. A multienclosure VC Domain has one local enclosure
and up to three remote enclosures.
To manage multienclosure VC Domains in VCEM, you must perform the following steps before you
create a VC Domain Group:
Preparing to create a VC Domain Group 43

1. Log in to VCM.
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. From VCM, find and import the necessary remote enclosures in the correct order. For more
information on remote enclosures, see the HP Virtual Connect for c-Class BladeSystem Setup
and Installation Guide.
5. From Systems Insight Manager, perform a manual discovery of the Onboard Administrator IP
address for all related VC Domain enclosures.
If you are using an HP VC FlexFabric 10 Gb 24-port module, ensure that the module status is
compatible. See “Upgrading incompatible firmware modes and versions” (page 27) for more
information.
VCEM cannot manage a VC Domain that has one or more FC modules with an Incompatible status.
The FC module can become incompatible in the following situations:
• An HP Virtual Connect 4 Gb FC module replaces an HP Virtual Connect 8 Gb 24-port FC
module.
• An HP Virtual Connect 8 Gb 24-port FC module replaces a HP Virtual Connect 4 Gb FC
module.
• If two VC modules from different models (like a Flex-10 or a FlexFabric module or an FC 4
Gb and an FC 8 Gb) share the same I/O bay slice.
• If there are mixed VC FC 4 Gb and 8 Gb modules in the same I/O bay from different
enclosures in a multienclosure VC Domain.
To create a VC Domain Group from the VC Domains page, select the VC Domains:
NOTE: At a minimum, the first VC Domain must have at least one network defined before it can
be used to create a VC Domain Group. It is easier to define networks and storage fabrics in the
VC Domain first before using it to create a VC Domain Group.
1. Click New VC Domain Group.
(Optional) If the enclosures for the selected VC Domains are not licensed for VCEM, then the
License page appears below the VC Domains list. (For more information, see VCEM licensing.)
Otherwise, New VC Domain Group... appears below the VC Domains list.
(Optional) Provide a new group name for the unconfigured VC Domains. Valid VC Domain
Group names can contain alphanumeric characters, hyphens (-), dot (.), and underscores (_),
and cannot exceed 64 characters.
2. Enter the user name and password for each VC Domain. Provide VC Domain credentials with
full privileges. VC Domains appear as:
• Unconfigured domains, which are listed in the System Name column with the unassigned
name, VCD_name
• Configured domains, which are listed in the System Name column with their previously
assigned names
3. Enter the user name and password for the Onboard Administrator of each unconfigured VC
Domain. Ensure you provide the Onboard Administrator credentials with full privileges if the
VC module is not configured.
(Optional) In some cases you might want to overwrite the existing VC Domain configuration
for selected VC Domains. To enable this action, select Existing VC Domain configuration
settings for selected VC Domain(s) without server profiles will be overwritten by selected base
VC Domain configuration defined for the VC Domain Group. VCEM confirms that the selected
VC Domain configurations match the VC Domain Group configuration. VC Domains that are
already configured and have server profiles are not affected.
4. Enter the VC Domain Group name in the VC Domain Group Name field.
Valid VC Domain Group names can contain alphanumeric characters, hyphens (-), dot (.),
and underscores (_), and cannot exceed 64 characters.
5. From the Configuration based on VC Domain list, select the VC Domain configuration on
which the new VC Domain Group will be based.
The Configuration VC Domain list contains only configured VC Domains.
6. Select the MAC address range type from the following options:
• VCEM-defined
• User-defined
• Factory-default
NOTE: You cannot change any of the range types after creating the VC Domain Group.
You can only select the User-Defined option for the MAC range type if a MAC custom range
is defined.
7. Select the WWN address range type from the following options:
• VCEM-defined
• User-defined
• Factory-default
You can only select the User-Defined option for the WWN range type if a WWN custom
range is defined.
8. Select the Serial Number address range type from the following options:
• Logical serial number
• Factory-default
9. Click OK. The message Virtual Connect Enterprise Manager is executing
the request appears.
10. Click OK to go to the Jobs page and monitor job progress.
11. (Optional) After creating a VC Domain Group from the Systems Insight Manager User and
Authorization page, configure the user authorization privileges for that VC Domain Group.
“Defining Roles-Based Access Control (RBAC)” defines role-based authorization privileges.
Defining Roles-Based Access Control (RBAC)

VCEM allows you to define role-based access control to VCEM resources. VCEM will restrict
operations based on the Systems Insight Manager user and their defined role within specific VC
Domain Groups.
Defining Roles-Based Access Control (RBAC) 45

NOTE:
• Create the VC Domain Groups, then define VCEM access to authorized users.
• By default the OS administrator user account has VCEM administrator rights to all VCEM VC
Domain Groups.
• A user account can be associated with different VC Domain Groups and have different
privileges for each of the groups. Likewise, a VC Domain Group can have different users
associated with it who have different privilege levels. For example, user JohnSmith can have
“VCEM Domain Group Administrator” privileges for the “HP-UX” VC Domain Group but be
limited to “VCEM Group Limited Operator” privileges in the “Linux-Servers” VC Domain Group.
It is also possible to assign other users with different privileges to conduct operations on the
“HP-UX” VC Domain Group. This way user RachelGreen could be assigned “VCEM Domain
Group Operator” privileges and user AdamWood could be assigned “VCEM Group Limited
Operator” privileges allowing them to perform only subsets of management operations on the
“HP-UX” VC Domain Group.
Table 12 Role-based privileges
Privileges Type Description
VCEM User (read-only) CMS Provides read-only access to VCEM

pages.
VCEM Group Limited Operator Group Enables you to perform some of the
tasks of the VC Domain Group
Operator role except for creating,
editing, or deleting a server profile.
VCEM Domain Group Operator Group Allows you to manage server profiles
in one or more specified VC Domain
Groups. Only server profile operations
in the specified VC Domain Group are
permitted.
VCEM Domain Group Administrator Group Enables you to manage VC Domains

and server profiles in one or more
specified VC Domain Groups. All
operations in the specified VC Domain
Group are permitted.
VCEM Administrator Group Provides access to all VCEM

operations.
To define RBAC to a specific VCEM VC Domain Group:
NOTE: You must have operating system administrator privileges to perform these steps
1. Create an Operating System account (for example, "JohnSmith").
2. Browse to Systems Insight Manager Options→Security→User and Authorizations screen.
3. Select the Users tab and click New.
4. Enter the same OS account name you created in Step 1 (JohnSmith).
5. Select the Authorizations tab and click New.
6. Under Select Users select the user account you created in Step 1 (JohnSmith). See Figure 28
for more information.
Figure 28 Systems Insight Manager Users and Authorizations page
7. Under Select Toolbox(es) select the VCEM role you want to use to restrict access (for example,
"VCEM Domain Group Administrator"). See Figure 28 for more information.

8. Under Select Systems:
a. CMS type roles: If you want these roles to apply to all VCEM pages, then select CMS.
b. Group type roles: Select Add, the select the VCEM VC Domain Group for which you want
to restrict access (for example, "vcdg-1") and click Apply. The selected VCEM VC Domain
Group will appear automatically in Select Toolbox(es). See Figure 29 for more information.
IMPORTANT: VCEM roles of type "Group" can only be applied to VCEM VC Domain
Groups as selected systems and VCEM roles of type "CMS" can only be applied to
"CMS" as selected systems. Otherwise the VCEM roles take no effect.
Figure 29 Add systems page
9. Click Apply.
When you log in to HP SIM using this OS user account VCEM applies RBAC based on the HP SIM
logged user and blocks some operations for the specific VC Domain Group resources based on
the VCEM RBAC rules. Table 13 summarizes all VCEM operations and RBAC privileges:
NOTE: In Table 13 (page 49) the “x” means that VCEM allows that role to perform the operation.
The “N” means that VCEM does not allow that role to perform the operation
Table 13 VCEM operations and RBAC privileges
VCEM operations VCEM VCEM group VCEM group VCEM group VCEM user
or VCEM roles administrator administrator operator limited operator (Read-only)
List bays x x x x x
List profiles x x x x x
List jobs x x x x x
List VC Domains x x x x x
List VC Domain x x x x x
Groups
Display profile x x x x x
details
Display bay x x x x x
details
Display job x x x x x
details
Display VC x x x x x
Domain Group
details
Display VC x x x x x
Domain details
Delete job x N N N N
Failover profile x x x x N
Create profile x x x N N
(single, multiple
assigned/unassigned)
Edit profile x x x N N
Move profile x x x x N
Copy server x x x x N
profile
Delete server x x x N N
profile
Assign server x x x x N
profile
Unassign server x x x x N
profile
Recover server x x x x N
profiles (disable
enclosure)
Create VC x N N N N
Domain Group
Remove VC x x N N N
Domain from VC
Domain Group
Add VC Domain x x N N N
to a VC Domain
Group

Table 13 VCEM operations and RBAC privileges (continued)
VCEM operations VCEM VCEM group VCEM group VCEM group VCEM user
or VCEM roles administrator administrator operator limited operator (Read-only)
Resynchronize x x N N N
VC Domain
Maintenance x x N N N
Mode
Delete VC x x N N N
Domain Group
Upgrade VC x x N N N
Domain Group
firmware mode
Update VC x x N N N
Domain firmware
License Enclosure x N N N N
Change server x x x x N
power state
Adding a VC Domain to a VC Domain Group

Select Add to VCD Group to add a VC Domain to a VC Domain Group. Verify that the following
prerequisites are met:
• At least one VC Domain Group is created
• Your current selection contains VC Domains that do not belong to a VC Domain Group
• VC Domains have a valid license
• Ensure that the version of VC firmware and the features enabled in the VC Domain are
compatible with the group firmware mode of the VC Domain Group to which it is being added.
For more information, see “Mixed VC firmware versions and compatibility in a VC Domain
Group ” (page 20).
• The VC Domains you select have a supported VC firmware version
If the VC firmware is unsupported, the following error message is displayed:
The operation cannot be performed because the VC firmware version
for the selected VC Domain(s) is not supported by VCEM. Refer to
the VCEM User Guide to verify the supported VC firmware versions,
and then update the VC Domain(s) firmware to a supported version.
• The VC Domain as well as the VC Domain Group configuration for the configured VC Domains
meet the minimum requirements . For the complete list of configuration checks, see
“Requirements for adding a VC Domain to a VC Domain Group” (page 30).
To manage multi-enclosure VC Domains in VCEM, you must perform the following steps before
adding a VC Domain to a VC Domain Group:
1. Log in to VCM.
and Installation Guide at http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/
c01732252/c01732252.pdf.
5. From Systems Insight Manager, perform a manual discovery of the Onboard Administrator IP
address for all remote VC Domain enclosures.
VCEM cannot manage a VC Domain which has one or more FC modules in an Incompatible state.
module.
module.
• HP Virtual Connect 8 Gb 24-port FC modules and HP Virtual Connect 4 Gb FC modules share
the same I/O bay slice (for example, an HP Virtual Connect 4 Gb FC module in I/O Bay 3,
and an HP Virtual Connect 8 Gb 24-port FC module in I/O Bay 4.).
• In a multienclosure VC Domain, if there are both HP Virtual Connect 4 Gb FC modules and
HP Virtual Connect 8 Gb 24-port FC modules in the same I/O bay from different enclosures,
(for example, 4 FC modules in the local enclosures, and 8 Gb FC modules in the remote
enclosures).
If the FIPS mode is enabled for the VC domain, the VC-FC module becomes incompatible.
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 for VCEM,
then the License page appears below the VC Domains list. For more information, see “VCEM
licensing” (page 42). 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
System names can contain alphanumeric characters, hyphens (-), dot (.), underscores (_), and
cannot exceed 31 characters.
4. Enter the user name and password for each unconfigured VC Domain. Ensure you provide
VC Domain credentials 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
assigned name
Domain. Ensure you provide the Onboard Administrator credentials with full privileges if the
VC module is not configured.
6. (Optional) In some cases you might want to overwrite the existing VC Domain configuration
for selected VC Domains. To do this, select Existing VC Domain configuration settings for
selected VC Domain(s) without server profiles will be overwritten by selected base VC Domain
configuration defined for the VC Domain Group. In this case, VCEM validates that the selected
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 request
message appears.
Adding a VC Domain to a VC Domain Group 51

Moving a VC Domain containing server profiles to a different VC Domain
Group
To move a VC Domain containing server profiles to a different VC Domain Group:
1. Export the server profiles from the VC Domain to the target VC Domain Group (and leave the
server profiles unassigned). The VCEM export operation will match all resources in use by
server profile and change the necessary elements to allow the migration to complete.
2. Select Overwrite Configuration to add the VC Domain to the target VC Domain Group. VCEM
overwrites the VC Domain with the VC Domain’s configuration.
3. Edit the server profiles exported in the first step, and select the available resources such as
networks, fabrics, network access groups, IGMP filters and so on.
4. Assign the server profile to the server bay.
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 profiles
will be located in this VC Domain.
• VC firmware supports no more than 256 server profiles within the VC Domain. If this number
is exceeded, VCM can reset.
VCEM detects the presence of logical server managers or upper-level managers. When performing
a specific task, a dialog box appears explaining the impact of performing the task from outside
the logical server manager or upper-level manager.
IMPORTANT: VCEM has detected you may be using other products, such as
HP Matrix Operating Environment. Removing this VC Domain from its VC
Domain Group will make it and any Server Profiles in this VC Domain
unmanageable by this upper level manager. Type YES to proceed with this
operation.
To proceed, enter YES, and then click OK. (VCEM will not proceed if you cut and paste YES into
the field.)
MAC, WWN, and serial number ranges enable VCM to manage the allocation of new addresses
when you release VC Domain control back to VCM (such as when you delete a VC Domain Group
or remove the VC Domain from a VC Domain Group). HP recommends that you provide MAC,
WWN, and serial number ranges that are not being used by VCEM or 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 VC Domain Groups.
After removing a VC Domain from a VC Domain Group, you can edit or change the existing server
profiles from the VCM user interface. If you re-import the VC Domain into a different VC Domain
Group, perform the import operation in VCEM and also make any further changes through VCEM.
NOTE: Removing the VC Domain out of the VC Domain Group does not cause any changes to
the MACs or WWNs currently in use in the VC Domain. Any new MACs or WWNs assigned
through VCM after the VC Domain has been removed from the VC Domain Group will be assigned
from the ranges designated when the VC Domain was removed from the VC Domain Group. See
“Managing MAC and WWN addresses” (page 128) for more information.
To remove one or more 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 the VC Domain Group appears.
3. Perform the following steps for each VC Domain that uses HP-predefined or user-defined ranges
that you want to remove from the VC Domain Group.
NOTE: Factory-default MAC, WWN, and serial number ranges are released to VCM as
factory-default.
If factory-default MAC or WWN addresses or serial numbers are not being used, you must
specify address ranges for each removed VC Domain. These address ranges must be unique
to avoid assignment of duplicate addresses.
NOTE: It is only necessary to record each selected MAC and WWN address range when
specifying a subset of a user-defined range also in use by VCEM. Since VCEM 1.40, VCEM
uses a proprietary 128k range so specifying HP pre-defined ranges when releasing VC
Domains does not require recording HP pre-defined ranges as exclusion ranges.
VCEM manages a proprietary serial number range so you do not need to define an external
range for the serial number.
The selected HP-predefined ranges are identified as user-defined ranges by VCM after 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 Use HP Pre-Defined range and then select a range from the list. You
can also clear Use HP Pre-Defined range and then enter the start and end addresses for
the MAC range. The MAC address range is NN-NN-NN-NN-NN-NN, where N is a
hexadecimal digit (0-F) and cannot exceed 12 characters. The VC Domain configuration
applies this MAC address range after the VC Domain is removed from VCEM control.
b. Enter the WWN address range. To use an HP-predefined WWN range, from the WWN
Range section, select Use HP Pre-Defined range and then select a range from the list. You
can also clear Use HP Pre-Defined range and then enter the start and end addresses for
the WWN range. The WWN address range is NN:NN:NN:NN:NN:NN:NN:NN where
N is a hexadecimal digit (0-F) and cannot exceed 16 characters. The VC Domain
configuration applies this WWN address range after the VC Domain is 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 Use HP Pre-Defined range and then select a range
from the list. You can also clear Use HP Pre-Defined range and then enter the start and
end values for the serial number range. The serial number range is VXC01NNNNN for
user-defined or VCXNNNNNNN for HP-predefined, where N is a hexadecimal digit
(0-F) and cannot exceed 10 characters. The VC Domain configuration applies this serial
number address range after the VC Domain is removed from VCEM control.
4. Click OK.
The message Virtual Connect Enterprise Manager is executing the request
appears.
Working with multienclosure VC Domains

VCEM supports multienclosure VC Domains. A multienclosure VC Domain is a VC Domain with
one local enclosure and up to three remote enclosures. VCEM supports VC Domains with up to
four BladeSystem c7000 enclosures.
Within each enclosure of a multienclosure domain, the VC Ethernet Modules must follow the same
configuration rules as VC Domains with single enclosures. However, each enclosure within the VC
Domain might have a different configuration of Ethernet modules. Stacking links must enable
Ethernet packets to reach all Ethernet modules within the VC Domain. All enclosures in a
multienclosure VC Domain must have the same Virtual Connect Fibre Channel Module configuration.
Working with multienclosure VC Domains 53

See “Related information” (page 175) for documents that can have more information on “stacking
links.”
Figure 30 (page 54) illustrates a valid configuration of Ethernet and Fibre Channel Virtual Connect
modules in a VC Domain with multiple enclosures. The black lines linking the Ethernet modules
illustrate the stacking links.
VCEM supports VC Domain Groups containing VC Domains with multiple enclosures, and enables
the VC Domains to contain different numbers of enclosures, as long as each VC Domain contains
the minimum number of enclosures. The Ethernet uplinks define the minimum number of enclosures.
The enclosure with a defined 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
that contains Ethernet uplink ports.
Figure 30 Valid configuration of Ethernet and Fibre Channel VC modules
As in earlier versions of VCEM, all VC Domains within a VC Domain Group must have the same
hardware configuration. VCEM enables each enclosure within a VC Domain with multiple enclosures
to have a different Virtual Connect Ethernet module configuration as described in the Virtual Connect
documentation, but it requires the same Virtual Connect Ethernet Module configuration across the
VC Domain Group members. The base enclosure of every VC Domain within one VC Domain
Group must have the same VC Ethernet module configuration. Similarly, every VC Domain that
has more than one enclosure must have the same VC Ethernet module configuration in all the
enclosures.
Figure 31 illustrates a VC Domain Group containing VC Domains with different numbers of
enclosures.
Figure 31 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.
• See the VC documentation available at: http://www.hp.com/go/vc for details on which
Virtual Connect Ethernet modules are supported for primary and secondary roles for the VC
firmware revision in your environment.
• FC modules in every enclosure must match the model and disposition.
To manage multienclosure domains in VCEM, proceed in the same way as with single-enclosure
domains:
1. License all enclosures. For more information, see “VCEM licensing” (page 42).
2. Provide credentials as needed.
3. Configure the VC Domain Group. For more information, see “Creating a VC Domain Group”
(page 43).
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, and the other VC Domain has four enclosures. You can create this configuration
provided that the base configurations of both VC domains are equal. For more information about
base configurations, see the “Replicating VC Domain Group configurations to other VC Domains
during VC Domain Maintenance”.
IMPORTANT: When configuring the VC Domain, you must add the remote enclosures in the
correct order. VCM tracks the order of the enclosures that are added. If you add the remote
enclosures and 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 VC Domain Group.
Working with multienclosure VC Domains 55

For more information, see the HP Virtual Connect Manager documentation.
VC Domain Maintenance
VC Domain Maintenance is a useful way to perform updates on a particular VC Domain without
removing it from a VC Domain Group, and apply the common domain, network and storage
configuration changes automatically to all other VC Domains that belong to the same VC Domain
Group. VCEM accomplishes this task by temporarily enabling domain, network, and storage
changes through the local VCM for the selected domain. VCEM retains control of the server
permissions while in maintenance mode. This means that operation permissions must be delegated
to the VC Domain, network, or storage roles in VCM if they are to be performed while in
maintenance mode.
NOTE: Adding the first FCoE network to an existing Shared Uplink Set whose associated networks
are currently in use will cause a momentary traffic interruption on those networks. If the domain is
part of a VC domain group, each domain in the group will have a brief traffic interruption.
Figure 32 displays VC Domain Maintenance functions.
Figure 32 VC domain maintenance
Some of the useful domain-level operations enabled during VC Domain Maintenance include:
• Updating firmware
• Backing up VC Domain configuration
• Administering local user accounts
• Directory Server settings:
◦ LDAP
◦ RADIUS
◦ TACACS+
◦ Role Authentication Order
• Changing VC Domain configuration
◦ Domain name
◦ Static IP address
• Setting SSH
• Setting SSL Certificate
• Ethernet Settings:
◦ MAC Cache failover
◦ IGMP Snooping
◦ Multiple Networks Link Speed Settings
◦ Server VLAN Tagging Support

• Shared Uplink Set
• Resetting VC module (soft reset)
• Monitoring network ports
• Configuring networks
• Configuring storage
• Login Banner Configuration
• Enclosures Configuration:
◦ Find
◦ Import
◦ Delete
• Storage Management Credentials
• SNMP Configuration
• Link Stability Redistribution
• Support Log Configuration
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
changing storage configuration.
VCEM detects the presence of logical server managers or upper level managers. When performing
selected tasks, a prompt dialog message appears and explains the impact of performing that task
from outside the logical server manager or upper level manager. The following message appears:
HP Matrix Operating Environment. While a VC Domain is in VC Domain
Maintenance, the VC Domain and any Server Profiles in the VC Domain
will be unmanageable by this upper level manager. Type YES to proceed
with this operation.
VC Domain Maintenance 57
To proceed, you must type YES, and then click OK. VCEM does not proceed if you cut and paste
YES into the field.
Replicating VC Domain Group configurations to other VC Domains during VC Domain

Maintenance
IMPORTANT: The VC Domain, network, and storage configuration changes performed during
VC Domain Maintenance are automatically replicated to all other VC Domains that belong to the
same VC Domain Group when the VC Domain maintenance operation is completed. The
configuration changes are rolled back for the domain and not replicated to other domains if the
maintenance operation is cancelled instead of completed. Cancelling maintenance accepts the
new firmware version if the VC firmware is updated during VC Domain Maintenance.
The following information is replicated to all VC Domains in the VC Domain Group during VC
Domain Maintenance:
NOTE: The following information is sample base VC Domain configuration data that is replicated
to all VC Domains in the VC Domain Group.
• Domain settings
NOTE: If the group firmware mode is 3.7x or later, the Password Preference setting and
the Require Strong Passwords setting are also propagated.
NOTE: When a domain is in maintenance mode, adding the first FCoE network to an existing
Shared Uplink Set whose associated networks are currently in use causes a momentary traffic
interruption on those networks. Each domain in the domain group experiences a brief traffic
interruption during the “complete maintenance” operation as the new settings are propagated.
◦ Configuration for double density servers (for example, BL2x220c)
◦ Configuration for full-height and half-height single density servers (for example, BL460c,
BL480c)
◦ Login Banner Configuration
◦ LACP timer
◦ Multicast filters and Multicast Filter Sets
IMPORTANT: Multicast Filter Set and multicast filter configurations can be changed in
VCM during the VCEM maintenance operation. However, you must have VCM
administrator or network role privileges to perform any change on these elements.
◦ QoS settings
◦ Name(s) and networks
• 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
◦ 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
– SNMP Security Enhancements
◦ Port Throughput statistics
◦ Port throughput statistics configuration information
◦ Network Loop Protection
◦ VLAN Capacity
– Expanded VLAN capacity
• 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
• For each network uplink:
◦ Name
◦ State
◦ Connection mode
◦ Smart link
◦ Private network
◦ Enable VLAN tunneling
◦ States
◦ Connection mode
◦ Preferred link connection
◦ Preferred link connection speed
◦ Maximum link connection
◦ Maximum link connection speed
◦ Colors
◦ Labels
• For each shared network:
◦ Uplink Set Name
◦ State
◦ Smart Link
◦ External VLAN ID
◦ Native VLAN
◦ Number of VLANs tagged associated with the shared network uplinks
◦ Colors
◦ Labels
• For each uplink set name:
◦ Connection Mode
◦ Network Port Location
Performing VC Domain Maintenance

IMPORTANT: You must select VC Domain Maintenance... to update VC firmware for VC Domains
with VC firmware earlier than 3.5x. If you are only updating the firmware, select Cancel VC Domain
Maintenance instead of Complete VC Domain Maintenance because there is no need to propagate
the configuration changes from the VC Domain configuration to the other VC Domains in the same
VC Domain Group. However, if you use maintenance mode to upgrade VC firmware and want
to save time by cancelling rather than completing VC Domain Maintenance in order to avoid
propagating the base configuration, ensure that you do not to make any other changes while in
maintenance mode. Cancelling maintenance will roll back any configuration changes except for
the updated firmware in addition to skipping propagation.
For VC firmware 3.5x and later, you can use maintenance mode or firmware update mode. See
“Updating VC firmware” for more information.
The VC Domain maintenance operation is comprised of these steps:

1. Initiate the VC Domain Maintenance.
2. Perform changes through the VCM Web interface.
NOTE: When a VC Domain has a status of Under maintenance, VCEM does not allow you
to perform server profile operations in any VC Domains which belong to that VC Domain
Group. This restriction also precludes any operation permissions delegated to the server role
as a result of VCM role operation configuration customizations. You can have a maximum of
one VC Domain in the VC Domain Group that has a status of Under maintenance.
3. Confirm the VC Domain changes through VCEM.

To perform VC Domain Maintenance from the VC Domains page:
1. Select the VC Domain on which you want to perform VC Domain Maintenance.
2. Click VC Domain Maintenance. The VC Domain Maintenance page appears.
3. To unlock VCM for domain, network, and storage changes, click Make changes via VC
Manager. The VCM web interface appears in a separate browser window. The Under
Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network,
and storage changes.
4. Using VCM, log in with the required user rights at Virtual Connect Manager, perform the
necessary changes, and save the changes. VCEM blocks all operations related to the VC
Domain and to its respective VC Domain Group while the VC Domain is under VC Domain
Maintenance.
5. Close the VCM web browser and return to the VC Domain Maintenance page in VCEM.
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
Domain changes, click Cancel. The Restore configuration check box enables VCEM to
automatically restore the original VC Domain configuration in case the new VC Domain
configuration is not able to be replicated to other VC Domains in the VC Domain Group. The
Virtual Connect Enterprise Manager is executing the request message
appears with a job ID code.
IMPORTANT: When a VC Domain is put in VC Domain Maintenance, operations such as backup

and restore VC configurations are allowed. Restoring VC configurations requires additional care.
If an old configuration is restored, verify that the configuration of this specific VC Domain remains
compatible with the 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 by VCEM.)
While VC Domain Maintenance enables the following actions to be performed on this VC Domain,
the actions 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 re-import the VC Domain to the VC Domain Group.
Backing up and restoring domain configurations through VC Domain Maintenance

NOTE: For VC Domains running VC 3.7x or later is not necessary to use VC Domain Maintenance
to perform the backup
1. Go to the VC Domains tab.
2. Select the VC Domain configuration that you want to back up.
Manager. The VCM web interface appears in a separate browser window. The Under
5. Using VCM:
a. Log in to VCM with the required user rights.
b. Perform the domain restoration by selecting Domain Settings→Domain Configuration,
and selecting the Backup/Restore tab.
c. Click Backup configuration. Wait until the backup process completes.
6. Close the VCM 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.
NOTE: If there are no additional changes to the configuration, HP recommends that you
cancel maintenance after the backup is completed. Cancelling maintenance avoids the
unnecessary propagation of unchanged VC Domain information to other member VC Domains
in the VC Domain Group.
To perform VC Domain configuration restoration through VC Domain Maintenance:
1. Select the VC Domains tab.
2. Select the VC Domain on which you want to restore the configuration.
4. Click Make changes via VC Manager to unlock VCM for domain, network, and storage
changes. The VCM web interface appears in a separate browser window. The Under
5. Using VCM:
a. Log in to VCM with the required user rights.
b. Perform the domain backup by selecting Domain Settings→Domain Configuration, and
selecting the Backup/Restore tab.
c. Enter the file name for the VC Domain configuration.
d. Click Restore configuration. Wait until the restoration process completes.
6. Close the VCM 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.
IMPORTANT: The domain configuration backup file created during VC Domain Maintenance is
valid for restoration while the VC Domain is in the VC Domain Group. The domain configuration
file is not valid after the VC Domain is removed from the VC Domain Group.
Changes in VCM that might affect completing VC Domain Maintenance

When you enable VC Domain Maintenance and make changes to a VC Domain base configuration,
attempts to complete VC Domain Maintenance might result in VCEM creating a failed job and the
VC Domain remaining under VC Domain Maintenance.
Changes in VCM that might cause problems in completing VC Domain Maintenance include:
• Updating the VC firmware to an incompatible version, (Domain Settings→Firmware
Management). To resolve this issue, update the VC firmware version to a compatible version
and complete VC Domain Maintenance again.
• Deleting the domain (Domain Settings→Domain Configuration). To resolve this issue, restore
the VC configuration from a backup, or remove the VC Domain from the VC Domain Group.
• Breaking the VC lock by using the VC command line. To resolve this issue, remove the VC
Domain from the VC Domain Group.
• VC fails to respond. If the VC Domain Maintenance job fails due to poor or failed VC
communication, fix the communication issue and complete VC Domain Maintenance again.
Viewing VC Domain details

NOTE: For QoS, operation permissions and multicast filters, details are only available if the VC
Firmware is 4.0x or later.
VCEM has enhanced how VC Domain details are displayed. VCEM provides a tab for each VC
Domain component such as Ethernet networks, shared uplink sets, and FC SAN fabrics. You can
also view new tabs such as quality of service (QoS), operation permissions, and multicast filters.
To access VC Domain details and component detail tabs, click the VC Domain you want to view
and depending on your configuration, VC Domain details similar to Figure 33 appear.
Figure 33 VC Domain details
Viewing the Custom Speed value

Virtual Connect 4.2x firmware supports 20Gb FlexFabric Adapters (HP FlexFabric 20Gb 2-port
630M Adapter and HP FlexFabric 20Gb 2-port 630FLB Adapter) which allows you to choose
Custom Speed values for Ethernet, iSCSI, FCoE, Associated networks, and multiple networks up
to 20Gb combined with the HP VC FlexFabric-20/40 F8 module. VCEM supports the Custom
Speed values for all these connections mentioned above. See Figure 34.
Figure 34 Custom speed value display for associated Ethernet, iSCSI, FCoE networks combined with
the HP VC FlexFabric-20/40 F8 module
Viewing VC Domain QoS details

To view QoS information on the VC Domain details page, select the QoS tab and the appropriate
OoS is displayed. Figure 35, Figure 36 and Figure 37 displays each QoS type.
NOTE: QoS settings are only displayed in both the VC Domain and VC Domain Group details
in VCEM. For more information on configuring QoS see the
HP Virtual Connect for c-Class BladeSystem User Guide at http://h18004.www1.hp.com/products/
blades/components/c-class-tech-installing.html
Figure 35 VC Domain QoS passthrough information
Figure 36 QoS custom with FCoE lossless configuration type
Figure 37 QoS custom without FCoE lossless configuration type
Figure 38 QoS custom without FCoE lossless (DOT1P mapping) configuration type
Viewing VC Domain and VC Domain Group roles

To view allowed VC Domain role permissions perform the following steps:
1. Select the VC Domain tab from the home page.
2. Click the target VC Domain.
3. Select the Operation Permissions tab to view VC Domain roles. Figure 39 displays an example.
Figure 39 VC Domain operation permissions tab
NOTE: Operation permissions are only displayed in VCEM. For more information on VCM
customizing role permissions see the HP Virtual Connect for c-Class BladeSystem User Guide
at http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html.
Viewing VC Domain multicast details
NOTE: the Multicast Filters tab is only displayed in VC Domain versions 4.0x or later.
When you create a VC Domain Group, add a new VC Domain to an existing VC Domain Group,
create or edit server profiles containing Ethernet connections using a MulticastFilterSet or a
MulticastFilter, you can view the current Multicast settings using the Multicast Filters tab.
Figure 40 VC Domain Multicast Filters tab
Statistical throughput attributes

VCEM displays statistical-throughput configuration information in the VC Domain Properties and
the VC Domain Group properties windows including:
• Add to Group—When a VC Domain is added to a VC Domain Group, the statistics-throughput
configuration setting from the VC Domain Group is applied to the VC Domain.
• VC Domain Maintenance—If the statistics-throughput setting is changed while the VC Domain
is in maintenance mode, the new setting will be propagated to the other VC Domains in the
VC Domain Group when maintenance is completed.
NOTE: For VC Domains that are in compatibility mode, this attribute will not be returned for VC
firmware versions earlier than 3.7x.
Figure 41 displays statistics-throughput configuration information.
Figure 41 VC Domain statistics-throughput configuration information
Viewing Allocated Bandwidth attributes

You can see the preferred or maximum allocated bandwidth speed and bandwidth type for each
fabric on VC Domain and VC Domain Group properties page. Optimized bandwidth attributes
are only applicable to fabrics that have uplink ports from FlexFabric interconnect modules. The
following list identifies the minimum and maximum allocated bandwidth attribute types:
• Minimum allocated bandwidth types:
◦ AUTO—No set value
◦ CUSTOM—Value between 100 Mb and 8 Gb

• Maximum allocated bandwidth types:
◦ UNRESTRICTED—No set speed limit
◦ CUSTOM—Value between 100 Mb and 8 Gb

Optimized bandwidth types are displayed in the VC Domain properties page and Allocated port
speed (min-max) entry has been added to the Ethernet, Flex -10 iSCSI and FCoE connections
screens. Figure 42 displays an FCoE connections screen example.
Figure 42 FCoE allocated port speed example
You can also view or select a new value for the FCoE connections table preferred port speed on
the edit server profile page. Figure 43 displays an example of preferred port speed (default port
speed when adding a new connection) in the FCoE connections table.
Figure 43 FCoE preferred port speed example
Displaying Converged Uplink sets and FCoE networks

Figure 44 displays Converged Uplink Sets and FCoE networks in the VC Domain details.
Figure 44 VC Domain details for Converged Uplink sets and FCoE networks
Viewing LACP timer attributes for VC Domains

VCM offers you the option of configuring the timeout for LACP which changes the frequency of
control messages (LACPDU). The feature can be either a short duration (1 second) or a long duration
(30 seconds). VCEM displays that information in the VC Domain network details. Figure 45 displays
VC Domain network details with the LACP timer attribute.
Figure 45 VC Domain network details LACP timer attributes
SNMP Access
VCEM displays VC Domain and VC Domain Group Ethernet SNMP access information by clicking
More Details ... at the bottom of the properties window. Figure 46 and Figure 47 displays SNMP
access.
NOTE: This feature is only available for Ethernet modules and not available on VC firmware
earlier than 3.7x.
Figure 46 Displaying Ethernet SNMP access
Figure 47 Displaying Ethernet SNMP access for IPv6
Viewing IPv6 addresses of managed VC Domains

Figure 48 displays a managed VC Domain IPv6 address.
NOTE: This feature is only available with VC firmware 4.1x or later.
Figure 48 IPv6 IP address
Using VLAN capacity

CAUTION: VCM firmware versions 3.3x through 3.6x or later does not allow you to easily revert
back from Expanded VLAN capacity mode to Legacy capacity mode. To revert back to Legacy
capacity mode, you must delete the VC Domain in VCM.
VC firmware 3.7x removes support for legacy VLAN capacity. All VC domains with VC 3.7x
installed support "Expanded VLAN Capacity". When adding a VC 3.7x or later Domain into a
VC Domain Group, you must ensure that the VC Domain Group is configured for "Expanded VLAN
Capacity". This can be done by putting one of the VC Domains in the VC Domain Group into
maintenance mode and configuring "Expanded VLAN Capacity" in VCM. Complete maintenance
mode to propagate this change to all the member VC Domains.
If a VC firmware earlier than 3.7x is running in Legacy mode and it is updated to VC firmware
3.7x, VLAN capacity will continue in Legacy mode.
Before applying Expanded VLAN capacity to a VC Domain 3.3x or later during Maintenance
Mode, make sure the VC Domain Group that the VC Domain belongs to is running firmware mode
3.3x or higher (this is a VCEM rule). If you change a VC Domain 3.3x to Expanded VLAN Capacity
and the VC Domain Group firmware mode is lower than 3.3x, the Complete Maintenance Mode
operation will fail, because VCEM will detect an enabled feature (Expanded VLAN capacity) not
supported by the other VC Domains (with older firmware). The VC Domain will remain in
Maintenance Mode status and VCEM will not be able to complete or cancel the maintenance
operation. To complete or cancel the maintenance operation, you must first remove the VC Domain
with Expanded VLAN capacity from the Domain Group.
Working with HP Virtual Connect 8 Gb Fibre Channel Module for c-Class BladeSystem
VCEM cannot manage a VC Domain having one or more FC modules in an Incompatible state.
module.
module.
• If HP Virtual Connect 8 Gb 24-port FC modules and HP Virtual Connect 4 Gb FC modules
share the same I/O bay slice. (For example, a HP Virtual Connect 4 Gb FC module in I/O
Bay 3 and a HP Virtual Connect 8 Gb 24-port FC module in I/O Bay 4).
• In a multienclosure VC Domain, if there are mixed HP Virtual Connect 4 Gb FC modules and
HP Virtual Connect 8 Gb 24-port FC modules in the same I/O bay from different enclosures.
(For example, 4 Gb FC modules in the local enclosure, but 8 Gb 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 Not Licensed 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 VCM.
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, complete VC Domain Maintenance.
Canceling a VC Domain Maintenance task

Canceling a VC Domain Maintenance discards domain, network, and storage configuration
changes that you have performed while in maintenance mode, and returns the VC Domain to the
configuration that is shared by all VC Domains within a VC Domain Group. If the VC firmware on
the VC Domain is updated while the domain is in maintenance mode, the updated firmware is not
rolled back if maintenance is canceled.
IMPORTANT: For more information on the domain, network, and storage configurations that
VCEM can replicate during completion of VC Domain Maintenance, or discard in case of a failure
or cancellation of the VC Domain Maintenance operation, see “Replicating VC Domain Group
configurations to other VC Domains during VC Domain Maintenance” (page 58).
To cancel a VC Domain Maintenance from the VC Domain page:
1. Select the VC Domain with status under maintenance.
Canceling a VC Domain Maintenance task 71

3. Click Cancel. The following message appears with a job ID code:
Virtual Connect Enterprise Manager is executing the request
Resynchronizing a VC Domain with Configuration Mismatch

Resynchronizing a VC Domain forces VCEM to verify that the VC Domain is still compatible with
the VC Domain Group configuration without removing and adding that VC Domain to a VC Domain
Group. The VC Domain configuration conforms to the same requirements when you add a VC
Domain into a VC Domain Group for the first time.
There are two ways a VC Domain with a configuration mismatch is resynchronized:
• Manually resynchronizing:
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.
4. Click OK to confirm. The Virtual Connect Enterprise Manager is executing
the request message appears with a job ID code.
• Automatically resynchronizing:
If VCEM detects a configuration mismatch, it starts auto resynchronization when you perform
a server profile operation. Figure 49 displays restoring the VC Domain configuration in the
job details.
Figure 49 Job details
Replacing the HP 1/10 Gb VC-Enet or the HP 1/10 Gb-Enet modules

To upgrade the HP 1/10 Gb VC-Enet module or the HP 1/10 Gb-Enet module to use the HP VC
Flex-10/10D module see sections “Replacing VC Ethernet modules with FlexFabric modules in an
existing VCEM managed VC Domain” (page 73) or “Replacing VC Ethernet in interconnect bays
three to eight with FlexFabric in an existing VCEM managed VC Domain” (page 74).
For more details on Migration from HP Virtual Connect 1/10 Ethernet Modules to HP Virtual
Connect Flex-10/10D Modules, see the HP Virtual Connect Migration Guide white paper.
Using FlexFabric modules
This section describes scenarios to add or replace existing Ethernet and FC modules with FlexFabric
modules.
NOTE: For general information about replacing VC modules with or without removing the VC
Domain, see “Replacing VC modules” (page 168).
Adding FlexFabric modules to an existing VCEM managed VC Domain

This scenario describes how to add two extra FlexFabric modules in an existing VC Domain with
Ethernet and FC modules. It also describes how to start using FlexFabric functionality in existing
or new server profiles.
1. Remove the VC Domain from the existing VC Domain Group "A".
2. Upgrade the VC Domain firmware to the latest version for FlexFabric support.
3. Add the two FlexFabric modules in both horizontally adjacent bays with appropriate FC SFP+
transceivers.
4. Create new Ethernet networks and new FC SAN fabrics linked to the new FlexFabric module
uplink ports.
5. Create a new VC Domain Group using the latest version of VC firmware in VCEM with the
VC Domain HP Virtual Connect FlexFabric 10 Gb/24port module.
6. Perform the first four steps again for each managed VC Domain that you want to add the HP
Virtual Connect FlexFabric 10 Gb/24port module to and add the VC Domain to the new VC
Domain Group.
After performing all the steps in “Adding FlexFabric modules to an existing VCEM managed VC
Domain” (page 73), you can create or edit any existing server profiles and use the available
networks or SAN Fabrics from the FlexFabric module to create FCoE or iSCSI connections.
Replacing VC Ethernet modules with FlexFabric modules in an existing VCEM

managed VC Domain
To replace a VC Ethernet module with a FlexFabric module in a VC Domain managed by VCEM,
perform the following steps:
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. Follow the steps in the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide
at http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
to replace the module based on the module model and disposition.
5. Access the Onboard Administrator web interface for the enclosure to verify that the VC Domain
link in the bottom left portion of the screen correctly points to the VC Domain Manager IP
address.
6. Perform an Systems Insight Manager discovery against the Onboard Administrator IP address.
8. Select the same VC Domain, and then click New VC Domain Group or Add to VC Domain
Group. Wait for the job to complete successfully.
Verify that the VC Domain meets the requirements for creating a new VC Domain Group or
adding a VC Domain to a VC Domain Group.
For more information, see “Requirements for adding a VC Domain to a VC Domain Group”
(page 30).
After performing all the steps in “Replacing VC Ethernet modules with FlexFabric modules in an
existing VCEM managed VC Domain” (page 73) you can create, or edit any existing server profiles
Using FlexFabric modules 73

and use the available networks or SAN Fabrics from the FlexFabric module to create FCoE or iSCSI
connections.
Replacing VC Ethernet in interconnect bays three to eight with FlexFabric in an existing

VCEM managed VC Domain
This scenario describes how to replace existing VC-Ethernet 10/10 Gb-F modules in interconnect
bays three to eight with FlexFabric modules in an existing VC Domain. It also describes how to
start using FlexFabric functionality in existing or new server profiles.
1. Remove the VC Domain from the existing VC Domain Group.
2. Upgrade the VC Domain firmware to the latest version of VC firmware for FlexFabric support.
3. Save the configuration.
IMPORTANT: HP recommends that you save the configuration so that if there is a problem
with the VC firmware upgrade you can restore the system to the last configuration snapshot.
4. Unassign any Flex-10 NICs with profile connections that are attached to the interconnect bays
being replaced. This can be done by unassigning the Ethernet connection in the server profile.
HP recommends that you do this in order so you do not lose the MAC addresses.
5. Delete any existing Ethernet network connections that were created using uplinks from the
interconnect bays that are to be replaced.
6. Remove the existing Ethernet modules from bays three, four, five and six.
7. Add the two FlexFabric modules in both horizontally adjacent bays three and four.
8. Create new Ethernet network connections and FC SAN Fabrics connections linked to the
FlexFabric module uplink ports.
9. Create a new VC Domain Group with the latest version of firmware in VCEM using this VC
Domain (with the HP Virtual Connect FlexFabric 10 Gb/24port module).
10. Reassign the existing Ethernet connections in the server profiles or add new connections to
the server profiles, depending on what was selected in Step 4.
11. Edit an existing server profile and add a network connection that uses the FlexFabric uplink
port.
12. Edit an existing server profile and an iSCSI connection and boot option that uses the FlexFabric
uplink port.
13. Create a new server profile and add a network connection that uses the FlexFabric uplink
port.
14. Create a new server profile and add a iSCSI connection and iSCSI boot that uses the FlexFabric
uplink port.
Replacing FC modules with FlexFabric modules in an existing VCEM managed VC

Domain
This scenario describes how to replace existing FC modules in bays three and four with VC-FC 4
Gb or VC-FC 8 Gb 24 port modules in an existing VC Domain. It also describes how to start using
FCoE functionality in existing or new server profiles.
2. Upgrade the VC Domain firmware to the latest version of VC firmware.
3. Replace the blade server FC HBA mezzanine cards with FlexFabric Adapter mezzanine cards.
4. Unassign any FC profile connections that are attached to the interconnect bays being replaced.
This can be done by unassigning the FC connections in the server profile. HP recommends
that you do this in order so you do not lose the MAC addresses.
5. Delete any FC SAN fabric connections that were created using uplinks from the interconnect
bays that are to be replaced.
6. Physically remove the FC modules from both horizontally adjacent bays three and four.
7. Add the two FlexFabric modules in both horizontally adjacent bays three and four with
appropriate FC FP transceivers.
8. Recreate previously deleted FC SAN fabrics using FlexFabric uplink ports (X1 to X4) .
9. Create a new VC Domain Group with the latest version of VC firmware in VCEM and using
this VC Domain (with the HP Virtual Connect FlexFabric 10 Gb/24port module).
After performing all the steps in “Replacing FC modules with FlexFabric modules in an existing
VCEM managed VC Domain” (page 74) you can create, or edit any existing server profiles and
use the available networks or SAN Fabrics from the FlexFabric module to create FCoE or iSCSI
connections.
Replacing VC Ethernet and FC modules with FlexFabric modules in an existing VCEM

managed VC Domain
This scenario describes how to replace existing VC-Ethernet 10/10 Gb-F modules in bays one and
two and VC-FC 4 Gb or VC-FC 8 Gb 24 port modules in bays three, four, five and six . It also
describes how to start using FlexFabric functionality in existing or new server profiles.
2. Upgrade the VC Domain firmware to the latest version of VC firmware.
3. Save the configuration.
4. Unassign any Flex-10 NICs with profile connections that are attached to the interconnect bays
being upgraded. This can be done by unassigning the Ethernet connections in the server
profile. HP recommends that you do this in order so you do not lose the MAC addresses.
5. Delete any existing Ethernet network connections that were created using uplinks from the
interconnect bays that are to be replaced.
6. Replace the blade server FC HBA mezzanine cards with FlexFabric Adapter mezzanine cards.
7. Unassign any FC profile connections that are attached to the interconnect bays being replaced.
This can be done by unassigning the FC connections in the server profile. HP recommends
that you do this in order so you do not lose the WWN addresses.
8. Delete any FC SAN fabric connections that were created using uplinks from the interconnect
bays that are to be replaced.
9. Remove the existing modules that are not FlexFabric from both horizontally adjacent bays
three to eight.
10. Add the two existing VC modules in both horizontally adjacent bays three and four with
appropriate FC SFP+ transceivers.
11. Create new networks with FC SAN fabrics linked to the new FlexFabric module uplink ports.
12. Reassign the Ethernet connections in server profiles or add new connections to the server
profiles, depending on what was selected in Step 4 and Step 7.
13. Save the configuration again.
IMPORTANT: HP recommends that you save the configuration so that if there is a problem
with the VC firmware upgrade you can restore the system to the last configuration snapshot.
14. Remove the Ethernet modules from bays one and two.
15. Add the two existing VC Ethernet modules in both horizontally adjacent bays one and two.
16. Follow the Virtual Connect Domain Setup Wizard, and select the option to restore the domain
for the saved configuration file in “Replacing VC Ethernet and FC modules with FlexFabric
modules in an existing VCEM managed VC Domain” (page 75).
After performing all the steps in “Replacing VC Ethernet and FC modules with FlexFabric modules
in an existing VCEM managed VC Domain” (page 75) you can create, or edit any existing server
profiles and use the available networks or SAN Fabrics from the FlexFabric module to create iSCSI
connections.

Upgrading to an HP Virtual Connect 8 Gb, 24-port FC module or an HP VC 8 Gb
20-port FC module
Upgrading to an HP Virtual Connect 8 Gb 24-port FC module or an HP VC 8 GB FC module in a
VC Domain managed by VCEM requires performing several important steps in both VC Manager
and VCEM depending on the starting configuration.
To replace a VC FC module with a different type of module in a VCEM managed VC Domain:
1. Click the VC Domains tab from the VCEM home page.
2. Select the VC Domain containing the VC modules to be replaced.
4. Follow the steps described in the HP Virtual Connect for c-Class BladeSystem User Guide at
http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html for
your specific replacement scenario, The following replacement modules are examples of the
current replacement scenarios:
• Replacing an HP 4Gb VC-FC Module, HP VC 4Gb FC Module, or HP 8Gb 20-Port FC
Module with an HP VC 8Gb 24-Port FC Module
• Replacing an HP 4Gb VC-FC Module or HP VC 4Gb FC Module with an HP VC 8Gb
20-Port FC Module.
• Replacing an HP 8Gb 24-Port FC Module with an HP VC 8Gb 20 Port FC Module
IMPORTANT: After installing the new VC FC modules, omit any VC steps to recreate FC
connections. You must use VCEM to recreate and reassign server profile connections.

6. Select the same VC Domain and click Add to VC Domain Group if there is an existing VC
Domain Group that meets the minimum requirements. Otherwise, click New VC Domain Group.
Wait for the job to complete successfully.
7. Reassign the server profiles and then add the FC Connections to the profiles (if necessary).
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”.
Upgrading or removing an HP Virtual Connect Flex-10 module or an HP Virtual

Connect FlexFabric module
Upgrading an enclosure to Flex-10 or FlexFabric support or removing Flex-10 support in a VCEM
managed VC Domain requires several steps in both VC Manager and VCEM, depending upon
the starting configuration.
To replace a VC Ethernet module with a different type of module in a VCEM managed VC Domain
and for configurations upgrading horizontally adjacent bay pairs hosting VC Manager (the
horizontal bays housing primary or backup modules), perform the following steps:
IMPORTANT: These steps guarantee that current VC/VCEM managed identifiers such as MACs,
WWNs, and serial numbers, assigned to existing server profiles from the original VC Domain,
are preserved after the creation of the new VC Domain during the process of replacing the primary
or backup VC modules.
These steps require that you have a VC Domain Group that will temporarily hold the server profiles
while replacing the VC modules
1. Click the Server Profiles tab from the VCEM home page.
2. Select VC Domain in the first filter and select the VC Domain name (with the primary or backup
VC modules to be replaced) in the second filter.
3. For the server profiles in the selected VC domain:
IMPORTANT: Use the VCEMCLI, to export the server profiles to a CSV file as a record of
the server profile names, bay assignments and profile connections. For more information on
the export command, see the HP Virtual Connect Enterprise Manager Command Line Interface
User Guide at HP Enterprise Information Library
a. Ensure that the server is powered off.
b. Click Edit and unassign all existing connections. Wait for the job to complete successfully.
c. Click Unassign. Wait for the job to complete successfully.
d. Click Move if the current VC Domain Group that contains the VC Domain with the primary
or backup VC modules that need to be replaced has no other members, select another
VC Domain Group that with a compatible minimum configuration and leave the server
profile unassigned. Wait for the job to complete successfully. For more details about
moving a server profile to a different VC Domain Group, see “Moving a server profile
to another bay in a different VC Domain Group”
These server profiles remain unassigned in the selected VC Domain Group in VCEM while upgrading
the VC Domain modules. The server profiles can be assigned back to the original VC Domain after
the VC module replacement is complete. To complete the VC module replacement:
1. Click the VC Domains tab from the home page.
2. Select the VC Domain with the VC Ethernet modules to be replaced.
http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html for
your specific replacement scenario.
CAUTION: If a VC firmware update is required for the scenarios below then make sure that
you select a VC firmware version supported by the VCEM version. See “Understanding VCEM
and VC firmware version compatibility” for more details regarding supported VC firmware
versions.
IMPORTANT: If you already have a VC Domain Group that meets minimum requirements
to add the VC Domain with replaced VC modules, you can omit the VC Domain recreation
steps described in the HP Virtual Connect for c-Class BladeSystem User Guide at http://
h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html.
IMPORTANT: Omit the server profile and connections reassignment steps described in the
HP Virtual Connect for c-Class BladeSystem User Guide. Instead, use VCEM to reassign the
server profiles, then reassign the networks and fabrics to the connections using the information
in the CSV export created earlier in the process as a reference.
The following are examples of the current replacement scenarios:
• Replacing a VC Ethernet module with an HP VC Flex-10 module or HP FlexFabric module
in a horizontally adjacent bay pair hosting VC Manager (the horizontal bays housing
primary and/or backup modules)
• Replacing a VC Ethernet module with an HP VC Flex-10 module or HP FlexFabric module
in a horizontally adjacent bay pair not hosting VC Manager
• Replacing an HP VC Flex-10 module or HP FlexFabric module with a VC Ethernet module
in a horizontally adjacent bay pair hosting VC Manager (the horizontal bays housing
primary and/or backup modules)
• Replacing an HP VC Flex-10 module or HP FlexFabric module with a VC Ethernet module
in a horizontally adjacent bay pair not hosting VC Manager

5. Perform the following steps if the scenario is to replace a VC module in a horizontally adjacent
bay pair hosting VC Manager:
a. Access the Onboard Administrator web interface for the enclosure to verify that the VC
Domain link in the bottom left portion of the screen correctly points to the VC Domain
Manager IP address.
b. Perform a Systems Insight Manager discovery against the Onboard Administrator IP
address.
7. Select the same VC Domain, and click Add to VC Domain Group if there is an existing VC
Domain Group which meets minimum requirements. For more information, see “Adding a VC
Domain to a VC Domain Group”. Otherwise, click New VC Domain Group. Wait for the job
to complete successfully.
8. If you kept the server profiles (step 1) unassigned in the VC Domain Group then perform the
following steps to assign the server profiles back to the original VC Domain with replaced VC
modules:
a. Click the Server Profiles tab from the VCEM home page.
b. Select VC Domain in the first filter and select the VC Domain name (with the replaced VC
modules) in the second filter.
c. For each server profile that was in the VC Domain (now with replaced VC modules)
perform the following steps:
i. Ensure that the server is powered off.
ii. Click Move and select the VC Domain Group where the original VC Domain is and
select the original server bay to assign it. For more information, see “Moving a server
profile”. Wait for the job to complete successfully.
iii. Click Edit and recreate the necessary connections, or assign the existing connections
to the new fabrics and networks, depending on what was done in your replacement
scenario. Wait for the job to complete successfully.
iv. Power up the server.
Upgrading to an HP Virtual Connect FlexFabric module from a VC-FC module

Upgrading an enclosure to FlexFabric from a VC FC module in a VCEM managed VC Domain
requires several steps in both VC Manager and VCEM. To replace a VC-FC module with an HP
VC FlexFabric module:
1. Release any server profile FC connections using WWN identifiers from the VCEM pool (if
any).
a. Click the Server Profiles tab from the VCEM home page.
b. Select VC Domain in the first filter and select the VC Domain name (with the replaced VC
c. For each server profile in the selected VC Domain do the following:
i. Ensure the server profile is powered off.
ii. Click Edit and remove any FC profile connections that are associated to the
interconnect bays being upgraded. Wait for the job to complete successfully.
3. Select the VC Domain with the VC FC modules that you want to replace.
http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
according to the current replacement scenarios, such as "Upgrading to an HP Virtual Connect
FlexFabric module from a VC-FC module" for example.
IMPORTANT: Omit the server profile and connections reassignment steps described in HP
Virtual Connect for c-Class BladeSystem User Guide. Instead, use VCEM to reassign the server
profiles, then reassign the networks and fabrics to the connections.

7. Select the same VC Domain and click Add to VC Domain Group if there is an existing VC
Domain Group that meets the minimum requirements. Otherwise, click New VC Domain Group.
Wait for the job to complete successfully. For more information, see “Adding a VC Domain
to a VC Domain Group” or “Creating a VC Domain Group”.
8. Recreate the server profile SAN connections in VCEM.
CAUTION: The VC and VCEM identifiers (WWNs) associated with the removed server profiles’
FC connections can be assigned to different server ports or slots in the recreated server profile
SAN connections using FCoE Connections. Recreating the SAN connections in the server profile
means that the newly created connections will be assigned new WWNs.
1. Select VC Domain in the first filter and select the VC Domain name (with the replaced VC
2. For each server profile that belongs to the VC Domain (with replaced VC FC modules) do the
following:
a. Ensure that the server is powered off.
b. Click Edit and recreate the necessary SAN connections, or assign the existing connections
to the new fabrics depending on your replacement scenario. Wait for the job to complete
successfully.
c. Power up the server.
Support of the CMS Reconfigure Tool

VCEM only supports the CMS reconfigure password tool included in the CMS reconfigure tool set.
For information on the CMS Reconfigure Tool, see the HP Systems Insight Manager User Guide
available at HP Enterprise Information Library.
Support of the CMS Reconfigure Tool 79

4 Managing VC Domain groups
This section describes the management of VC Domain Groups using VCEM.
A VC Domain consists of an HP BladeSystem enclosure, a set of associated Virtual Connect Ethernet
and Fibre Channel interconnect modules, and server blades that are managed together by a single
instance of VCM. The VC Domain contains specified networks, server profiles, and user accounts
that simplify the setup and administration of server connections. Establishing a VC Domain Group
enables administrators to upgrade, replace, or move servers within their enclosures without changes
to the external LAN/SAN environments.
VCEM keeps unassigned server profiles at the VC Domain Group level.
With VCEM you can move and copy server profiles within a single VC Domain or between any
VC Domains within a VC Domain Group. You can also export or move profiles to a different 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. Any unassigned server profiles created through VCEM also become part of the
VC Domain Group.
To access the VC Domain Groups page in VCEM, click the VC Domain Group tab. The VC Domain
Groups page appears.
Figure 50 VC Domain Groups
Table 14 (page 80) describes the columns on the page.

Table 14 VC Domain Groups page
Item Description
Status Describes VC Domain Group status
Name Lists VC Domain Group name
Number of domains Identifies the number of domains in the group
Table 15 (page 81) describes VC Domain Group icons and status on the page.

Table 15 Group icons and status
Configuration in synch All VC Domains that belong to this VC

Domain Group share the same domain
configuration
Under maintenance VC Domain is unlocked for domain,

network, and storage changes through
the VCM. After completing the domain,
network and storage changes, you must
confirm the new VC Domain
configuration in VCEM. VCEM
operations related to this VC domain
or to VC Domain Group, such as create
server profile, move server profile,
server profile failover, and so on, are
blocked while the VC Domain is under
maintenance.
Incompatible firmware This status is displayed after a VCEM

upgrade and indicates that an
incompatible firmware mode and
version was detected. Only the
following VCEM VC domain operations
are permitted for resources with an
incompatible status:
• Remove VC Domain from Group
• Delete VC Domain Group
• Perform VC Domain Maintenance
• Upgrade VC Domain Group
firmware mode
To display the properties for a particular VC Domain Group, such as status, MAC range type,
WWN range type, 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

the VC logs. For more information, see “Correlating VCEM operations in Systems Insight Manager
and VC logs”.
To manage multienclosure VC Domains in VCEM, you must perform the following steps before you
create a VC Domain Group or add a VC Domain to a VC Domain Group:
1. Log in to VCM.
Creating a VC Domain Group 81

and Installation Guide.
5. Go to Systems Insight Manager and perform a manual discovery on Onboard Administrator
IP address of all related VC Domain enclosures.
If you are using the HP VC FlexFabric 10 Gb 24-port module, ensure that the module status is
compatible. If the module is incompatible, an error message appears.
VCEM cannot manage a VC Domain that has one or more FC modules in an incompatible state.
See “Working with HP Virtual Connect 8 Gb Fibre Channel Module for c-Class BladeSystem” for
incompatibility information.
To create a VC Domain Group:
NOTE: At a minimum, the first VC Domain must have at least one network defined before it can
be used to create a VC Domain Group. It is easier to define networks and storage fabrics in the
VC Domain first before using it to create a VC Domain Group.
1. Select the VC Domain Groups tab.
2. Click New....
(Optional) If the enclosures related to the selected VC Domains are not licensed for VCEM,
then the License page appears below the VC Domain Group list. (For more information, see
“VCEM licensing” Otherwise, the Create VC Domain Group frame appears below the VC
Domain Group list.
3. (Optional) You can provide a new name for the unconfigured VC Domains. Valid VC Domain
Group names are alphanumeric, hyphens (-), dot (.), underscores (_), and cannot exceed 64
characters.
4. Enter the user name and password for each VC Domain. Ensure you provide VC Domain
credentials will 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
assigned name.
Domain. Ensure that you provide the Onboard Administrator credentials with full privileges if
the VC module is not configured.
(Optional) In some cases you might wish to overwrite the existing VC Domain configuration
for selected VC Domains. To enable this action, select Existing VC Domain configuration
settings for selected VC Domain(s) without server profiles will be overridden by selected base
VC Domain configuration defined for the VC Domain Group. VCEM validates that the selected
6. Enter the VC Domain Group name in the VC Domain Group Name field. Valid VC Domain
Group names are alphanumeric, hyphens (-), dot (.), underscores (_), and cannot exceed 64
characters.
7. From the Configuration based on VC Domain list, select the VC Domain configuration upon
which the new VC Domain Group is to be based. The Configuration VC Domain list contains
only configured VC Domains.
8. From the Select Serial Number type list, select whether the serial number type is a logical
serial number or factory default.
9. 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 a MAC custom range is defined.

10. 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 a WWN custom range is defined.
message appears.
13. (Optional) After creating a VC Domain Group, from the Systems Insight Manager User and
Authorization page, select the user authorization privileges for that VC Domain Group. See
“Creating a VC Domain Group” for more information.
Maintaining a VC Domain from the VC Domain Groups page

IMPORTANT: VCM 3.3x to 3.6x does not allow you to easily revert back from Expanded VLAN
capacity mode to Legacy capacity mode. To revert back to Legacy capacity mode, you must delete
the VC Domain in VCM and then recreate it.
VC firmware 3.7x supports legacy VLAN capacity for VC Domains upgraded to VC 3.7x from
older versions of VC firmware. New domains being created with VC 3.7x or later will automatically
be set to expanded VLAN capacity. When adding a VC 3.7x or later Domain into a VC Domain
Group, you must ensure that the VC Domain Group is configured for "Expanded VLAN Capacity".
This can be done by putting one of the VC Domains in the VC Domain Group into maintenance
mode and configuring "Expanded VLAN Capacity" in VCM. Complete maintenance mode to
propagate this change to all the member VC Domains.
If a VC firmware earlier than 3.7x is running in Legacy mode and it is updated to VC firmware
3.7x, the VLAN Capacity will continue in Legacy mode.
To perform VC Domain maintenance from the VC Domain Groups page:

1. Select the VC Domain Group on which you want to perform maintenance.
2. Click VC Domain Maintenance.
NOTE: When a VC Domain has a status of Under maintenance, VCEM does not allow you
to perform server profile operations in any VC Domains which belong to that VC Domain
Group. You can have a maximum of one VC Domain in the VC Domain Group that has a
status of Under 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.
Manager. The VCM web interface appears in a separate browser window. The under
maintenance status indicates that the VC Domain Group is temporarily unlocked for domain
network and storage.
5. Using VCM, log in with full user rights at the Virtual Connect Manager prompt and perform
and save the necessary changes. VCEM blocks all operations related to the VC Domain and
to its respective VC Domain Group while the VC Domain is under VC Domain Maintenance.
Close the VCM web browser and return to the VC Domain Groups page in VCEM. To confirm
changes in VCEM, repeat steps 1 and 2.
6. Click the Restore configuration check box to enable VCEM to automatically restore the original
VC Domain configuration in case changes cannot be applied to the VC Domain Group.
7. Select from one of the following options:
• Click Complete VC Domain Maintenance to apply the changes.
If VCEM detects that all VC Domains in the group have higher firmware versions than the
VC Domain Group, a warning similar to the following is displayed:
VCEM detected that in addition to completing the VC Domain
Maintenance process, the VC Domain Group firmware mode [{0}] can
Maintaining a VC Domain from the VC Domain Groups page 83
be upgraded to [{1}]. Do you want to upgrade the VC Domain Group
firmware mode? Click 'Yes' to upgrade the VC Domain Group firmware
mode in addition to completing the VC Domain Maintenance
operation. Or click 'No' if you want to complete VC Domain
Maintenance operation at this time. You can manually upgrade the
VC Domain Group firmware mode at a later time by selecting
'Upgrade Firmware Mode' on the VC Domain Groups page.
• Click Cancel to discard the VC Domain configuration changes. If the VC Domain is not
under maintenance, clicking Cancel closes the user interface pages. The message Virtual
Connect Enterprise Manager is executing the request appears with a
job ID code.
Canceling a VC Domain Group maintenance task

To cancel a VC Domain Group maintenance task:
1. From the VC Domain Groups page, select VC Domain Group with status Under Maintenance.
3. Click Cancel. The Virtual Connect Enterprise manager is executing the
request message appears with a job ID code.
Upgrading VC Domain Group firmware mode

IMPORTANT: VC Domain Group firmware mode does not allow a downgrade of a VC Domain
Group firmware version. You must verify that the VC firmware versions for the VC Domains within
the VC Domain Group are later than the current VC Domain Group firmware version. Otherwise,
the upgrade firmware mode for the VC Domain Group will not be allowed.
Upgrading the VC Domain Group firmware mode enables you to upgrade the VC firmware mode
of the VC Domain Group according to the VC firmware versions of the VC Domains contained in
the VC Domain Group. To upgrade the VC Domain Group firmware mode to a later version:
NOTE: Not every release of VC Firmware will provide a new "Group Firmware Mode" option.
The features introduced in the release determine whether a new "Group Firmware Mode" is needed.
1. Select to the VC Domain Group to be upgraded.
2. From the VC Domain Groups page, click Upgrade Firmware Mode.

IMPORTANT: The Upgrade Firmware Mode feature is used to control what firmware level
will be used for the VC Domain Group as a whole. For example, if the FW mode of the VC
Domain Group is 3.30, then the base VC Domain configuration data and profile operations
will all behave as though they contain VC FW 3.30. This allows you to gradually upgrade
the individual VC Domain firmware levels to a later version, and then when the last VC Domain
firmware is upgraded, clicking the Upgrade Firmware Mode button signals the VC Domain
Group as a whole to start operating at the later firmware version.
Not all VC firmware upgrades provide a new group firmware mode option. For example, VC
firmware releases 3.5x through 3.60 all use 3.5x group firmware mode. New VC Domain
Group firmware options typically correlate to significant new features in the VC firmware
The base VC Domain configuration data is the foundational information that defines the
capabilities of a VC Domain. For more information on base VC Domain configuration data,
see “Replicating VC Domain Group configurations to other VC Domains during VC Domain
Maintenance”.
The Upgrade Firmware Mode feature allows you to set the minimum acceptable VC firmware
version for any VC domain in this VC domain group.
In VCEM 7.3, the FW mode of the VC Domain is 4.10 and in 7.3, the FW mode of the VC
Domain Group is 4.1x.
3. Select a firmware version from Upgrade Firmware Mode to.

message appears with a job ID code.
Deleting a VC Domain Group

IMPORTANT: If you delete a VC Domain Group, then all unassigned server profiles within that
VC Domain Group will be posted to one of the VC Domains that were part of the deleted VC
Domain Group. To verify which VC Domain contains the unassigned server profiles after the VC
Domain Group deletion job is completed, look at the report generated by the related job in the
VCEM event. To access this report from the Systems Insight Manager left navigation panel, select
Events→Shared→VCEM Events.
VC firmware supports no more than 256 profiles within the VC Domain. If this number is exceeded,
the VCM can reset.
VC logs. For more information, see “Correlating VCEM operations in Systems Insight Manager
and VC logs”.
this task, a prompt dialog message appears and explains the impact of performing that task from
outside the logical server manager or upper level manager. The following message appears:
HP Matrix Operating Environment. Deleting this VC Domain Group will
make it and any Server Profiles in this VC Domain Group unmanageable
by this upper level manager. Type YES to proceed with this operation.
YES into the field.
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.
Deleting a VC Domain Group 85

3. Click Delete. The Delete VC Domain Groups page appears.
4. Perform the following actions for each VC Domain that uses HP-predefined or user-defined
ranges within the VC Domain Group that you want to remove. Factory-default MAC and
WWN ranges are released back to VCM as Factory-default.
If factory-default MAC or WWN addresses or serial numbers are not being used, address
ranges must be specified for each removed VC Domain. These address ranges must be unique
and distinct to prevent assignment of duplicate addresses. If you are specifying a subset of a
user-defined range which is also in use by VCEM, each selected MAC and WWN address
range must be recorded as an exclusion to prevent VCEM assignment. VCEM manages a
proprietary serial number range, so there is no need to define an external range or serial
number. The selected HP-predefined ranges are identified as a user-defined ranges by the
VCM after the VC Domain is removed from VCEM.
The selected HP-predefined ranges are identified as a user-defined range for the VCM after
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 also clear the Use HP Pre-Defined range box and then enter the start and end
addresses for the MAC range. Valid MAC address range is NN-NN-NN-NN-NN-NN
where N is a hexadecimal digit (0-F) and cannot exceed 12 characters. The VC Domain
configuration applies this 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
HP Pre-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
addresses for the WWN range. Valid WWN address range is
NN:NN:NN:NN:NN:NN:NN:NN where N is a hexadecimal digit (0-F) and cannot
exceed 16 characters. The VC Domain configuration applies 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 Use Pre-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
for the serial number range. Valid serial number range VCX01NNNNN for user-defined
or VCXNNNNNNN for HP-predefined where N is a hexadecimal digit (0-F) and cannot
exceed 10 characters. The VC Domain configuration applies this serial number address
range after being removed 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 Groups 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 Systems Insight Manager event that describes in detail about the released VC
Domain, such as domain name, MAC range type, WWN range type, serial number range type,
server profiles and related MAC addresses, WWN addresses, serial numbers, network connections,
and Fibre Channel SAN connection range types.

Displaying VC Domain Group detail tabs
Select or hover over a VC Domain Groups and detail tabs such as VC Domain Group, Ethernet
networks, Shared Uplink sets, FC San fabrics, QoS, Operation Permissions, Multicast Filters, and
Server Profiles are displayed.
NOTE: For QoS, Operation Permissions and multicast filters, details are only available if the VC
Firmware is 4.0x or later.
View all properties about that tab. Figure 51 displays the VC Domain Group properties tab.
Figure 51 VC Domain Group properties tab
Viewing VC Domain Group QoS details

To view QoS information on the VC Domain Group details page, select the QoS tab and the
appropriate OoS is displayed. Figure 52, Figure 36 and Figure 37 displays each QoS type.
NOTE: QoS settings are only displayed in VCEM. For more information on configuring QoS see
the
HP Virtual Connect for c-Class BladeSystem User Guide at http://h18004.www1.hp.com/products/
blades/components/c-class-tech-installing.html
Figure 52 VC Domain Group QoS passthrough information
Figure 53 QoS custom with FCoE lossless configuration type
Displaying VC Domain Group detail tabs 87

Figure 54 QoS custom without FCoE lossless configuration type

Figure 55 QoS custom without FCoE lossless (DOT1P mapping) configuration type
Viewing VC Domain Group roles

To view allowed VC Domain Group role permissions, perform the following steps:
1. Select the VC Domain Group tab from the home page.
2. Click on the target VC Domain Group.
3. Select the Operation Permissions tab to view VC Domain Group roles. Figure 56 (page 89)
displays an example.
NOTE: Operation permissions are only displayed in VCEM and do not affect the VCEM
GUI. For more information on VCM customizing role permissions see the HP Virtual Connect
for c-Class BladeSystem User Guide at http://h18004.www1.hp.com/products/blades/
components/c-class-tech-installing.html.
Figure 56 VC Domain Group Operation Permissions tab
Viewing VC Domain Group multicast details

When you create a VC Domain Group, add a new VC Domain to an existing VC Domain Group,
create or edit server profiles containing Ethernet connections using MulticastFilterSet or MulticastFilter
filters, you can view the current Multicast settings using the Multicast Filters tab.
Displaying VC Domain Group detail tabs 89

Figure 57 VC Domain Group multicast filters
Statistical throughput attributes

VCEM displays statistical throughput configuration information in the VC Domain Properties and
the VC Domain Group properties windows including:
• Add to Group—When a VC Domain is added to a VC Domain Group, the statistics-throughput
configuration setting from the VC Domain Group is applied to the VC Domain.
• VC Domain Maintenance—If the statistics-throughput setting is changed while the VC Domain
is in maintenance mode, the new setting will be propagated to the other VC Domains in the
VC Domain Group when maintenance is completed.
NOTE: For VC Domains that are in compatibility mode, this attribute will not be returned for VC
firmware versions earlier than 3.7x.
Figure 58 displays statistics-throughput configuration information.
Figure 58 VC Domain Group statistics-throughput configuration information
Displaying Converged Uplink sets and FCoE networks in VC Domain Groups

Figure 59 displays Converged Uplink Sets and FCoE networks in the VC Domain Group details.
Figure 59 VC Domain Group details for Converged Uplink sets and FCoE networks
Viewing LACP timer attributes for VC Domain Groups

VCM offers you the option of configuring the timeout for LACP which changes the frequency of
control messages (LACPDU). The feature allows you to change the frequency, which can be either
a short duration (1 second) or a long duration (30 seconds). Figure 60 displays default LACP timer
duration information in the VC Domain Group properties.

Figure 60 LACP timer duration
Adding or removing VC modules in a VC Domain Group

To 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” (page 85).
3. For each VC Domain released from the VC Domain Group, insert or remove VC modules in
the corresponding enclosure, and perform the necessary domain, network, and storage
configuration changes in the VCM user interface.
Before VC module removal, remove the VC module uplink ports from all existing Network or
Shared Uplink settings from VC Domain configuration.
4. Return to VCEM, click the VC Domain Groups tab, and click New. For more information about
creating a VC Domain Group, see “Creating a VC Domain Group” (page 43). At step 1,
select the VC Domains to add to the new VC Domain Group. Wait until the job operation
completes. As a result, the new VC Domain Group created contains an updated configuration
reflecting the new VC modules.
NOTE: Existing server profiles cannot see new Fibre Channel SAN connections added using
these steps. However, if the fabrics were created on VCM, you can see the Fibre Channel SAN
connections. For more information, see “Editing a server profile” (page 107).
Moving Ethernet networks (VLANs tagged) from one shared uplink to

another
1. 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 the VCM 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.
Adding or removing VC modules in a VC Domain Group 91

5. Repeat steps 1 and 2.
6. In the VCM 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 Systems Insight Manager and VC logs

All VCEM operations are logged in the Systems Insight Manager Audit log and provide a reference
to the VC Domain being managed. The VCEM operations related to a managed VC Domain are
also logged by VCM in its system log. In an audit process for VCEM operations, you must correlate
Systems Insight Manager in VCM logs. To perform this task:
1. Look for VCEM entries in Systems Insight Manager Audit Log by clicking Tasks & Logs→View
Systems Insight Manager Audit log.
2. Search for a VCEM operation that begins with: “Virtual Connect Enterprise Manager (VCEM)
- Starting job.”
3. You can find timestamp, VCEM operation (Job number#, Job details, Job title, VC Domain
name), and user name. For most VCEM operations you can find the name of the VC Domain.
4. You can view the VC Domain system log in VCM 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 bracketed by
“VCM user login” and “VCM user logout” entries for the user name “A<CMS_IP>@<CMS_IP>.”
For example, CMS IP 16.84.195.136 appears in the VC log entry as a reference to
“(A1684195136@16.84.195.136)” because VCEM runs on the CMS system.

5 Managing server profiles
This section describes how to create and manage server profiles with VCEM.
A VC server profile is a logical grouping of attributes related to server connectivity that can be
assigned 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 server profile operations such as create, delete,
unassign, copy, move, and edit. For more information on this procedure, see “Managing enclosure
bay assignments” (page 123)
To access the server profiles page, click the Server Profiles tab. Information on the Server Profiles
pages can be filtered by selecting one of the following entries in the Filter list.
• All—Select this option to display all server profiles being managed by VCEM.
• VC Domain—Select this option to display all server profiles that exist in a specified VC Domain.
The second list can be used to select a specific VC Domain to use as a filter.
• VC Domain Group—Select this option to show all server profiles that exist in a VC Domain
Group. The second list 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 61 Server Profiles page
The following table lists the columns in the managing server profile table.
Item Description
Status Server profile status (assigned or not assigned)
Name Server profile name
93
Item Description
VC Domain Group VC Domain Group name
VC Domain VC Domain name
Enclosure Identifies the enclosure name
Bay Bay number
A server profile defines connections for a blade server. Server profiles can include the following
information:
• Server profile name
• Logical serial number and logical UUID
• Ethernet network connections and PXE settings
• MAC addresses
• Fibre Channel fabric connections
• Flex-10 iSCSI Connections
• FCoE Connections
• WWN addresses
• Server boot configuration
• BIOS settings
Newer VC Domain versions provide a broader configuration set in the server profile. Table 16
lists the features that are configurable depending on the VC Domain versions.
Table 16 VCEM supported VC features
VC
3.5x-VC
Feature VC 4.4x VC 4.3x VC 4.2x VC 4.1x VC 4.0x VC 3.7x 3.60 VC 3.3x
Server • • • • • • • •
VLAN
tagging
Add/Remove • • • • • • • •
Fibre
Channel
SAN
connections
Integrity • • • • • • • •
blade
support (EFI
partition
data)
Ethernet • • • • • • • •
connection
port speed
configuration
Double-density • • • • • • • •
blade
support
Enhanced • • • • • • • •
SNMP
configuration

Table 16 VCEM supported VC features (continued)
VC
3.5x-VC
Multienclosure • • • • • • • •
VC Domain
Assign • • • • • • • •
server
profiles to
multi-blade
servers
BL850 I2,
BL870 I2,
BL890 I2 in
c7000 and
c3000
enclosures
Add up to • • • • • • • •
128
Ethernet
connections
Add • • • • • • • •
extended
FC
connections
for
multi-blade
systems
Add or • • • • • • • •
remove
Flex-10
iSCSI
connections
iSCSI boot • • • • • • • •
for Flex-10
Add or • • • • • • • •
remove
FCoE
connections
Storage • • • • • • • •
Management
Targets
Expanded • • • • • • •
VLAN
Capacity
Add • • • • • • • •
Network
Access
Groups
iSCSI Boot • • • • • • • •
Assistant
(IBA)
Server • • • • • • • •
profile GUI
enhancements
(Network
selection
95
VC
3.5x-VC
and
Network/VLAN
filtering)
Integrity • • • • • • •
multiblade
servers:
• BL860c
i4—single
blade
server
• BL870c
i4—2-blade
server
• BL890c
i4—4-blade
server
VC Flex • • • • • •
10/10D
Ethernet
module
FlexNIC • • • • • •
port
statistics,
stacking
link
information
Connect to • • • • • •
field to
show how
server
logons are
distributed
among the
uplinks on
VC SAN
Fabrics
VCEM Edit • • • • • •
Profile
displays
the
hexadecimal
factory
MAC
address for
Ethernet
connections
if the MAC
Address
type is
“Factory-Default”.
SNMP • • • • • •
access
configuration
Direct • • • • • •
Attached

VC
3.5x-VC
FC Fabrics
with 3PAR
storage.
Duplicate • • • • • • •
and Excess
Network
restrictions
Configurable • • • • •
role
operations
LACP timer • • • • •
settings
Quality of • • • • •
Service
(QoS and
Classes of
Service
(CoS)
Preferred • • • • •
port speed
(QoS)
Selecting a • • • • •
Multicast
Filter
Selecting a • • • • •
FCoE
Network
Hide • • • •
unused
FlexNICs
Multi-FCOE • • • •
network
per Uplink
Set
From the managing server profiles screen, you can perform the following tasks:
• Create a server profile
• Delete one or more server profiles
• Edit a server profile
• Assign a server profile
• Unassign a server profile
• Copy a server profile to a bay
• Move a server profile to the same VC Domain Group or a different VC Domain Group
• View network and Fibre Channel information for a server profile
• Perform a VC Server Profile Failover operation
• Recover server profiles from an unreachable enclosure
97
Creating a server profile
NOTE:
Keep the following server profile dependencies in mind:
• Depending on the VC Domain version, the create server profile page displays a different set
of configurations. To verify the available features for each VC Domain version, see “VCEM
supported VC features”.
• The server profile can have at most one FC, iSCSI, or FCoE boot option configured.
1. From the Server Profiles page, click New.
NOTE: An enable or disable Hide Unused FlexNICS check box has been added to the server
profile editor. The check box is only visible if the VC Domain Group firmware mode is 4.1x
or later. The default for newly-created server profiles is to hide unused FlexNICs. See
“Concealing unused FlexNICS ” for more information on the Hide Unused FlexNICS check
box option.
2. From the Member of VC Domain Group menu, select the VC Domain Group to which the
server profile will belong.
The Create New Server Profile information appears below the server profiles list.
3. In the server profile name box, enter a unique server profile name.
4. (Optional) Choose the network access group selection box.
NOTE: Network access groups can be changed while creating or editing a server profile.
The connections using networks that do not belong to the newly selected network access group
are set back to unassigned.
A network access group associates a server profile with a subset of networks in the VC Domain
and ensures that the server profile is not connected to networks outside the subset. Therefore,
only the networks that belong to the selected network access group are displayed in the
selection box. The other networks are filtered out. If a network access group option is not
selected, the Default option is used.
All networks are part of the default network access group. You can create other network access
groups through VCM and decide which networks will be associated with each network access
group.
5. (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
changes apply to every Ethernet and Fibre Channel connection in a server profile.
• To use server factory defaults for Ethernet MAC addresses, select Use Server Factory
Defaults for Ethernet MAC addresses.
• To use server factory defaults for Fibre Channel WWNs, select Server Factory Defaults
for Fibre Channel WWNs.
• To use server factory defaults for Serial Number, select Server Factory Defaults for Serial
Number.
6. In the Ethernet network connections table, two Ethernet networks are created. Network names
are optional, however if you do not select a network name, the blade server NICs are not
able to access connectivity You can select multiple networks using Ethernet network connections.
To add more connections, click Add Network Connection. To remove a connection, click the
X icon at the right side of the table.
The Ethernet network connections can vary depending on the VC Domain Group firmware
mode. For example, if the firmware mode is 4.0x or later, the IGMP filter selection is displayed.

Figure 62 (page 99) and Figure 63 (page 99) displays network selections.
Figure 62 Network selections
Figure 63 Selecting a Network window
To make the search easier, you can apply filters by Name, Shared Uplink Set, VLAN ID, label
or color. If you choose Name, Shared Uplink Set, VLAN or label, the second drop-down box
defaults to Contains and you can enter part of a filter such as Name or Shared Uplink Set. If
you choose Color, the drop-down box defaults to Is. Filters are helpful in situations where a
VC Domain Group has a large amount of VLAN networks (up to 1000) configured. Label and
color filters are only available in VC Domain Groups running VC firmware version 3.3x or
later.
IMPORTANT: The Select a network window will display a maximum of 8192 VLANs but we
can select only 1000.
NOTE: You also have the option to change the network after you have assigned it. The
following figure displays changing the network.
Figure 64 Change network connection
Creating a server profile 99

NOTE: For VC firmware versions 3.7x and later, you cannot select the same network for
more than one mapped physical port such as LOM1 and LOM2 for example. VCEM returns
an error similar to the following:
Ethernet connections 2, 4 are mapped to the same physical port (LOM:2). These connections are configured
with duplicate networks. Please ensure there are no duplicate networks on connections mapped to the same
physical port.
7. Select Add iSCSI Connection in the Flex-10 iSCSI connections table to add network names,
port speed and boot settings.
Figure 65 displays iSCSI boot settings.
Figure 65 iSCSI boot settings
If you enter an incorrect field format, an error message with the appropriate format is displayed.
The following table describes iSCSI boot setting attributes and field formatting.
Setting Description
iSCSI Boot Configuration
Initiator Name (required) Name used for the iSCSI initiator boot system. The
initiator name length is maximum of 256 characters. If
the initiator name contains nonalphanumeric characters,
it must be enclosed in double quotes. The value must be
in the following format:
iqn.yyyy-mm.{domain.name} See http://
docs.hp.com/en/T1452-90011/ch04s01.html for more
information.
Target Name (required) Boot target. The target name length is a maximum of
256 characters. If the name contains nonalphanumeric
characters, it must be enclosed in double quotes. The
value must be in the following format:
iqn.yyyy-mm.{domain.name} See http://
docs.hp.com/en/T1452-90011/ch04s01.html for more
information.

Setting Description
Primary IP Address (required) Primary IP address of the iSCSI target. This value is in
dotted-decimal format. For example:
111.222.333.444
Primary Port (required) TCP port associated with the primary target IP address.
The Default value is 3260.
IP Address 2 Alternate target IP address used if the primary address

is unavailable.
Port 2 (required if an alternate target IP address is TCP port associated with the alternate IP address. The
specified) default value is 3260
Use DHCP (optional) Click Use DHCP to enable the following:

• iSCSIParamDHCP—Allows the iSCSI ROM option to
retrieve iSCSI boot parameters. This attribute default
is set to disable to allow for static configurations.
• DHCP Vendor ID—Required if iSCSIParamDHCP is
set to enable. Used to match the value in the Vendor
Class ID field in the DHCP packet with retrieving
either iSCSI Boot or network parameters. The Vendor
ID field is restricted to 32 characters.
Authentication Method
None Default selection for the authentication method.
CHAP or CHAPM user names and passwords Click CHAP or CHAPM to enable the following:
• CHAP or CHAPM user name—Required if the
authentication method is CHAP or CHAPM. This is
the user name for authentication. The user name
length is a maximum of 223 characters. If the user
name contains nonalphanumeric characters, it must
be enclosed in double quotes.
• CHAP or CHAPM Secret—Required if the
authentication method is CHAP or CHAPM. This is
the password for authentication and is specified as
a string or a long hexadecimal value starting with
0x. This value must be at least 96 bits (12 bytes, 24
hexadecimal digits) long and at most 16 bytes (32
hexadecimal digits) excluding separators (‘ ‘ , ‘-‘, ‘.’,
‘:’, ‘,’ ).
Initiator Network Configuration
VLAN ID (optional) VLAN number used by the iSCSI initiator for all sent and
received packets. Valid VLAN number values are
between 1 and 4094.
IP Address (required) Address used by the iSCSI initiator. This value is in

dotted-decimal format.
Netmask (required) IP network mask used by the iSCSI initiator. This value
is in dotted-decimal format.
Gateway (optional) Default IP route used by the iSCSI initiator. This value is
in dotted-decimal format.
8. (Optional) Select Use Boot Assistant... and the iSCSI Boot Assistant window opens. Figure 66
displays the iSCSI Boot Assistant window.
NOTE: The Use Boot Assistant option is only available for HP 4000 SAN solutions.

Figure 66 iSCSI Boot Assistant
HP recommends that you use the iSCSI Boot Assistant rather than populating the iSCSI fields
manually. The main goal of the iSCSI Boot Assistant is to save time. If you run the iSCSI Boot
Assistant after manually populating the iSCSI fields, the values previously entered manually
will be overwritten.
1. Choose a VC Domain and the Management Targets: selection box is enabled. The list of
available management targets is dependent on the storage management credentials
configured in each VC Domain. Each VC Domain can have a list of different iSCSI targets
in its storage management credential configuration area.
2. Choose a management target, and the Boot Volume: selection box is enabled. Select a
boot volume and then click OK.
9. In the Fibre Channel SAN connections table, set the Fibre Channel SAN connections. To add
more connections in a VC Domain, click Add FC SAN Connection. You can add up to 8
connections per slice, for a maximum of 4 slices and 32 connections. If you enter the maximum
connections allowed, Add is disabled and an error message is displayed. To remove a
connection, click the X icon at the right side of the table.
10. (Optional) In the Fibre Channel Boot Parameters table, enter the boot parameters for defined
Fibre Channel SAN connections. The default boot parameter is Use Bios. The World Wide
Port Number (WWPN) and Logical Unit Number (LUN) are required only for the primary and
secondary SAN boot.
NOTE: For a profile booting from the remote volume, you need an operating system previously
configured on the volume.
11. (Optional) Select FCoE Connections. The server profile editor displays the default FCoE
connections based on the VC modules present in the VC Domain. For example, Figure 67
shows how to set the FC SAN Name for the connection on port 2. You can select an FCoE
network or a SAN fabric. If you select an FCoE network the Type column displays "FCOE."

FCoE networks are only available when the group firmware mode of the VC Domain Group
is 4.0x or later.
Figure 67 FCoE network or SAN fabric selection
IMPORTANT: Custom port speeds differ between FCOE and SAN fabric networks as follows:
• FCOE network range—0.1 to 20 Gb.
• SAN fabric network range—0.1 to 8Gb.
You must add a minimum port speed, if the value is greater than the maximum port speed.
New FCoE connections can be added at the end of this list. Connections can be removed in
the reverse order from which they were added. An error message is displayed if the maximum
number of FCoE connections is reached.
NOTE: If there are no SAN fabrics using the uplink ports, the FCoE connections can be
configured as unassigned.
12. You can create a single server profile, or multiple server profiles. To create a single server
profile, select Single Profile.
You can either leave the profile unassigned or click Select Location to assign the profile to a
server bay. A table is displayed allowing you to select a domain and enclosure and also select
the bays you want associated with the profile. Click OK to create the profiles and a profile
list is displayed. Click OK to accept the assignments.
13. In addition to creating a single server profile, you can create multiple profiles at the same time
and decide to leave a number of profiles with an unassigned status, or assign those server
profiles to bays. Choose from one of the multiple server profile options:
1. Select Assign server profiles to specific server bays and click Select Location to make the
assignments. A window opens allowing you to select a domain and enclosure and all
the bays associated with the enclosure. Click OK to create the profile and a profile list is
displayed. Click OK to accept the assignments.
2. Select Leave server profiles unassigned for now and pick the number of profiles you want
to create (up to 50). The server profile names are automatically generated based on the
server profile prefix. Click Select Location to select more bays or delete bays. Click OK
to create the profiles.
NOTE: When creating multiple server profiles, boot parameters are ignored. Edit each server
profile to specify the boot parameters.
message appears.
NOTE: To create server profiles for Integrity Blades that boot from SAN, you must manually
configure the SAN boot entries in the blade server EFI console.

Concealing unused FlexNICS
NOTE: The ability to hide unused FlexNICs is only supported in VC Domain Groups whose group
firmware mode is 4.1x or later.
VCEM provides administrators with control over whether or not unused FlexNICs are listed in the
host operating system running on the blade where the profile is assigned. Displaying unused
FlexNICs consumes additional resources and can prevent using all 10GB of the port on one physical
function.
For example, Figure 68 displays the operating system device listings before disabling unused
FlexNICs
Figure 68 Before removing unused FlexNICS
Figure 69 displays the operating system device listings after enabling the Hide Unused FlexNICs
check box.
Figure 69 After removing FlexNICs
Server profiles upgraded from VC firmware versions prior to 4.1x are unchanged and all FlexNICs
will be listed in the operating system. You can change the FlexNICs setting on server profiles after
upgrading to VC 4.1x by powering off the server, setting the Hide Unused FlexNICs check box,
and powering on the server.
IMPORTANT: Changing whether or not unused FlexNICs are listed in the operating system can
change the ordering of network interfaces in the operating system. This can interrupt server network
connectivity until the operating system is reconfigured to match the new NIC ordering structure.
Configuring the target boot LUN

When creating or editing server profiles, you can specify a target boot LUN for the FC SAN, iSCSI
or FCoE connections designated as Primary and Secondary in the boot priority column.
Target boot LUN values must be compliant with proper ranges.

For VC Domains, you can provide the target boot LUN in either of the following possible formats:
• When using LUN values from 0–255, you can specify the LUN in either decimal or in a 13
to 16-digit hexadecimal number format.
• When using LUN values greater than 255, you must specify the LUN in 16-digit hexadecimal
number format.
To specify the LUN and a 13 to 16-digit hexadecimal number format, place the desired hexadecimal
number preceded by leading zeros as shown in the following examples:
• 1023 can be represented in 16-digit hexadecimal format as 00000000000003ff or
00000000000003FF (not case-sensitive).
• 18446744073709551615 is represented in 16-digit hexadecimal format as ffffffffffffffff or
FFFFFFFFFFFFFFFF.
• 4503599627370495 is represented in 13-digit hexadecimal format as fffffffffffff or
FFFFFFFFFFFFF
• 72057594037927935 is represented in 14-digit hexadecimal format as ffffffffffffff or
FFFFFFFFFFFFFF
• 1152921504606846975 is represented in 15-digit hexadecimal format as fffffffffffffff or
FFFFFFFFFFFFFFF
Configuring multiple networks

To configure multiple networks
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 70 displays multiple networks.
Figure 70 Server VLAN tag to vNet Mappings window
2. You can filter also networks by the following attributes:

• Name
• VLAN Id
• Color
• Label
The second drop-down box defaults to Contains and you can enter part of a filter such as
Name or Shared Uplink Set. If you choose Color, the drop-down box defaults to Is.
3. Click the Force same VLAN mappings as Shared Uplink Set check box to enable or disable it
depending on your base configuration. Figure 71 displays the options.
Configuring multiple networks 105

Figure 71 Force same VLAN mappings as Shared Uplink Set options
4. Click the right-arrow to add the network to your configuration. To remove networks press the
left-arrow. You can select all the VLAN networks available, but only 162 VLAN networks are
accepted. The following message is displayed warning you about this limit.
The provided configuration for multiple networks exceeds the maximum allowed number of VNet mappings. The
maximum number of VNet mappings is [].
The 162 VLAN networks feature is made available with Extended Mapped VLAN capability
and is contained in VC Domains with VC firmware 3.30 or later.
5. Click OK to save the configuration.
NOTE: For VC firmware versions 3.5x and later, you cannot configure more than 162 VLANs
per physical function such as LOM1 or LOM2 for example. VCEM will return an error.
Configuring Network Port Speed

When creating or editing a server profile, you can configure the network speed of an Ethernet
network connection. You can select network speed parameters using the Preferred, Custom, or
Disabled options.
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 window appears. Enter the desired port speed.
Deleting a server profile

such as HP Matrix Operating Environment. Deleting this VC Domain Group
will make it and any Server Profiles in this VC Domain Group unmanageable
by this upper level manager. Type YES to proceed with this operation.
YES into the field.
1. From the Server Profiles page, select the server profiles to be deleted.
2. Click Delete. You are prompted to confirm the deletion.

Editing a server profile

HP Matrix Operating Environment. Editing this Server Profile can make
it inconsistent with the upper level manager. It is recommended to use
the upper level manager to edit this Server Profile. Type YES to proceed
with this operation.
YES into the field.
When editing server profiles, VC Domain Group memberships and server bay assignments are
read only. To edit a server profile:
1. From the Server Profiles page, select the server profile to be edited.
2. Click Edit. The Edit Server Profile information appears below the server profile table.
3. Enter changes to the Server Profile name as needed.
4. (Optional) To change the network access group:
1. Choose the Network Access Group selection box.
2. Choose another network access group. A warning message similar to the following can
appear if Ethernet networks, multiple, or iSCSI connections are not associated with this
network access group: VCEM will unassign all Ethernet/iSCSI connections
in this server profile that are assigned to a Network with no
association to the selected Network Access Group [nag1]. Do you
want proceed with the Network Access Group change? Click "OK" to
proceed with the Network Access Group change or click "Cancel"
to keep the current connections.
5. Enter changes to the Ethernet network connections (physical ports) as needed, and then click
Add Network Connection.
6. Enter changes to Fibre Channel SAN connections, and Fibre Channel boot parameters as
necessary. Depending on the physical changes to the Fibre Channel VC modules, the Add
FC Connection button or the Remove FC Connection button appears.
7. (Optional) To erase the current EFI partition information in the integrity blades assigned server
profiles, select Cleanup the EFI partition data.
8. (Optional) Edit the Flex-10 iSCSI Connections table and the iSCSI Boot Setting column as
necessary.
9. (Optional) Edit the FCoE Connections column and the FCoE Boot parameters table as necessary.
For example, Figure 72 shows how to set the FC SAN Name for the connection on port 2.
You can select an FCoE network or a SAN fabric. If you select an FCoE network the Type
column displays "FCOE." FCoE networks are only available when the group firmware mode
of the VC Domain Group is 4.0x or later.
Figure 72 FCoE network or SAN fabric selection
Editing a server profile 107

10. (Optional) To inform the bay assignment, select VC Domain, and then select an available
target server bay. If a server profile is not assigned to a server bay or fails to assign to a server
bay, then that server profile is saved as unassigned in the VC Domain Group. The Assign to
bay button is available only if the selected server profile being edited is unassigned.
11. Verify the server bay assignment.
message appears.
Viewing server profile attributes and status

VCEM ensures that you can determine the difference between the VCEM server profile status and
the VC Manager status. Figure 73 displays VCEM and VC status.
Figure 73 VCEM and VC statuses
If a degraded status icon is displayed in the Status column, you can view the statuses of the iSCSI,
FC, and FCoE network connections in the VCEM server profile GUI. Figure 74 displays some
network status icons. “Connection type and status definition” displays and defines connection type,
status icons, and status definitions.

Figure 74 Network status icons
Viewing server profile attributes and status 109

Table 17 Connection type and status definition
Connection type Status icon Status definition
Server profile The blue icon with an “i” in the middle

indicates that the iSCSI or most of the
connections are not mapped.
(Not shown) The blue question marks

indicate an unknown status.
(Not shown) Degraded—If a degraded

status icon is displayed in the Status
row, you can view the statuses of the
iSCSI, FC, and FCoE network
connections in the VCEM server profile
GUI.
Ethernet Network Connections The green check marks indicate a

normal status.
Flex-10 iSCSI Connections The blue icon with an “i” in the middle
indicates that the iSCSI or most of the
connections are not mapped.
FC SAN Connections (Physical Ports) Normal
FCoE Connections (not shown) Normal
VCEM also displays network connection port mapping and the minimum-maximum allocated port
speed so that you can the view the allocated port speed of a physical port and the server hardware
mapping assignment. Figure 75 displays Ethernet and iSCSI port mapping and allocated port
speed.
NOTE: If the server profile is not assigned, the value of allocated port speed is displayed as Not
Allocated.
Figure 75 Ethernet and iSCSI port mapping and allocated port speed

Using flexible server profile listings
VCEM allows you to dynamically customize the number of server profiles displayed on the server
profile page. Figure 76 displays the page ranges.
Figure 76 Flexible page ranges
You can select pages by choosing them in groups or you can enter a page into the Go to page:
dialog box . You can also use the browser's search and find features for quick access to a particular
server profile.
Extending mapped networks

Recent VC firmware releases increase the maximum number of multiple networks to 1000. As the
number of networks available to a VC Domain Group server profile increases significantly, a filter
for networks is available. You can find networks by labels and colors too.
There are two options available when selecting an Ethernet network:
• Select a Network
• Multiple Networks
For iSCSI networks, only Select a Network is available.
When a network is already selected, click Change Network to edit it.
Selecting a single network

When selecting a single network, you can filter with the following options:
• Name
• VLAN Id
• Label
• Color
Use the Is/Contains combination box to search by part of a word or phrase. Click on the column
heading to sort the results. Label and color filters are available only in VC Domain Group firmware
mode 3.3x or later.
Selecting multiple networks

You can filter multiple networks the same way you filter single networks. See “Selecting a single
network” (page 111) for more information. Two tables are displayed. To select the networks, click
the networks in the left table and transfer them to the right table. When changing a network, all
the previously selected networks are displayed in the right table. When the Force option is not
checked you can edit network VLAN IDs. The maximum number of networks you can select are
retrieved from the VC Domain Group.
Using flexible server profile listings 111

Selecting multiple networks with the Force same VLAN mappings as Shared Uplink
Set option checked
When selecting multiple networks and the option Force same VLAN mappings as Shared Uplink
Set is checked, a combination box is display. Select Shared Uplink Set and only the networks
related to this Shared Uplink Set will be displayed in the left table. You can filter these networks
but the Shared Uplink Set option will not be available.
Verifying the presence of EFI partition data

When editing server profiles that are assigned to Integrity server blades, you can verify the presence
of the EFI partition data that controls the Integrity server blade boot.
To verify the presence if the EFI partition data:
1. From the Server Profiles page, select the server profile to be verified.
2. Click Edit. The Edit Server Profile information appears below the server profile table.
3. In the Server Profile Information table, click the question mark icon.
4. If EFI partition data is present in the server 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 server
profile check box and click OK. The Virtual Connect Enterprise Manager is
executing the request message appears.
Assigning a server profile

such as HP Matrix Operating Environment. Assigning this Server Profile
can make it inconsistent with the upper level manager. It is recommended
to use the upper level manager to assign this Server Profile. Type YES
to proceed with this operation.
YES into the field.
1. From the Server Profiles page, filter the server profiles by the VC Domain Group that has the
unassigned server profiles.
2. In the server profiles list, click the Assign link, or select a server to assign, and then click Assign.
The Server Profile Assignment page appears.
3. Select an available server bay to which the server profile is assigned.
IMPORTANT: You cannot assign a server profile to a covered bay. An error message similar
to the following is displayed:
Cannot assign server profile because the selected bay is covered.
See “VC Domain Group firmware compatibility” (page 20) for the latest firmware versions.
message appears.
IMPORTANT: If a profile is assigned to a server with two FlexNIC ports on the same physical
NIC, VCEM indicates the problem in the profile status icon.

NOTE: When assigning profiles which SAN-boot from a Direct Attached fabric to a different
c-Class enclosure, you must edit the boot parameters to reflect the appropriate address which the
3PAR array presents to the new enclosure.
Unassigning a server profile

outside the logical server manager or upper level manager. The following message appears.
HP Matrix Operating Environment. Unassigning this Server Profile can
make it inconsistent with the upper level manager. It is recommended
to use the upper level manager to Unassign this Server Profile. Type
YES to proceed with this operation.
YES into the field.
1. From the Server Profiles page, select the assigned server profile to unassign.
2. Click Unassign. You are prompted to confirm the unassignment.
message appears.
Copying a server profile

1. From the Server Profiles page, select the server profile that must be copied and assigned.
NOTE: Profiles with NPIV settings edited by upper level managers such as Matrix OE cannot
be copied directly in VCEM. These profiles must be managed through the upper level software
that created them.
2. Click Copy.
3. Enter a unique name for the new server profile.
4. (Optional) Select an available bay to which the new server profile is assigned.
NOTE: If a VC Domain already contains server profiles assigned to covered bays and is
upgraded to VC firmware 3.3x or later, and you unassign an existing server profile from a
covered bay, it is not possible to assign it to a covered bay again.
This situation can exist a if a VC Domain already contains server profiles assigned to covered
bays and is upgraded to VC firmware 3.3x or later.
5. Select from one of the following boot parameter options:

• Fibre Channel Boot Parameters
• Flex-10 iSCSI Connections
NOTE: Boot Settings for Flex-10 iSCSI Connections or FCoE Boot Parameters are
displayed if the VC Domain Group contains VC Domains with the required firmware
version (3.3x or later) and VC interconnect modules with enabled FCoE and iSCSI features.
• FCoE Boot Parameters

6. (Optional) For Flex-10 iSCSI connections, select Use Boot Assistant and the iSCSI Boot Assistant
window opens.
7. Click OK. The message Virtual Connect Enterprise Manager (VCEM) is
executing the request appears.
Unassigning a server profile 113

Moving a server profile

IMPORTANT: Profiles can fail to boot from Direct Attached SAN fabric after relocation to another
enclosure. To correct this, see “Profiles fail to boot from Direct Attached SAN Fabric after relocation
to another enclosure”.
You can move a server profile to the same VC Domain Group or to a different VC Domain Group.
“Moving a server profile to another bay in the same VC Domain Group” and “Moving a server
profile to another bay in a different VC Domain Group” (page 114) describes each scenario.
NOTE: When moving a server profile to another bay in the same or different VC Domain group,
this task, the following message appears and explains the impact of performing that task from
outside the logical server manager or upper level manager:
HP Matrix Operating Environment. Moving this Server Profile to another
Server Bay can make it inconsistent with the upper level manager. It
is recommended to use the upper level manager to move this Server Profile
to another Server Bay. Type YES to proceed with this operation.
Moving a server profile to another bay in the same VC Domain Group

To proceed, you must enter YES, and then click OK.
NOTE: VCEM does not respond if you cut and paste YES into the field.
1. Select a server profile from the Server Profiles page.
2. Click Move. The Move Server Profile page appears.
3. Select the same VC Domain Group as the target VC Domain Group, VCDG315 for example,
from the Select Target VC Domain Group as displayed in Figure 77:
Figure 77 Moving a server profile
4. In the Move to Bay list, select an available bay in which to move the new server profile.
5. Click OK. The message Virtual Connect Enterprise Manager is executing
the request appears.
6. Click OK to go to the Jobs page and monitor progress.
Moving a server profile to another bay in a different VC Domain Group

This feature allows you to move profiles across VC Domain Groups. VCEM ensures that moved
server profiles are compatible with the target VC Domain Group. To access the move option you
must have either Administrator or Group Administrator privileges. See “Managing VC Domains”
for more information.
To move a server profile to another bay in a different VC Domain Group:

1. Select Server Profiles from the menu.
2. Select a server profile and click Move.
NOTE: You can move either assigned or unassigned profiles.
3. Select the VC Domain Group that you want as a target.

4. Select the VC Domain and optionally select a target bay from the VC Domain Group target
in which to move the server profile and click OK. The following message is displayed:
The Virtual Connect Enterprise Manager is executing the request.
5. Click OK and browse to the Jobs page to monitor the progress.
If VCEM detects any errors during the move or requires post-configuration steps, the Move Profile
Prevalidation window opens and displays step status and further actions to take. Figure 78 displays
the Move Profile Prevalidation table.
Figure 78 Move profile prevalidation table
VCEM performs five validation steps during the export process as displayed in Figure 78. These
five steps validate source and target resources associated with the export operation. These steps
also validate feature compatibility between the server profile and the target VC Domain Group as
well as certifying feature compatibility specific to network and fabric features.
Table 18 describes the status for each prevalidation step.
Moving a server profile 115

Table 18 Prevalidation status
Status Description
Done Step has successfully completed.
Configuration VCEM will perform some changes on the server profile in

order to export it to the target VC Domain Group. If a
configuration status is displayed, the export can proceed
but some post-export actions need to be performed such
as editing the server profile at the target VC Domain Group
and assigning existing networks or fabrics so that the server
profile network and storage connectivity continues to work
properly.
Error VCEM has detected some situation where the validation

failed. If any steps show an error status, the export cannot
proceed until the problem is fixed.
Warning VCEM detects that changes need to be made to the source

server profile such as removing an FC or FCoE connection
or adding or removing VLANS in a multiple network
defined connection. If any step shows a warning status,
then the export cannot proceed until the problem is fixed.
The following list is a full description, including validations and post-configuration actions required
for each step.
1. Source resource validations—VCEM performs the following source resource validations:
• Ensures that if the source server profile is assigned to a server, that the server is powered
off before the export operation.
NOTE: If the source server is not powered off, you must power it off and perform the
export operation again.
• Confirms that the source VC Domain Group that the server profile belongs to has a status
of Configuration in synch. Server profiles belonging to a VC Domain Group with other
statuses such as the following list cannot be exported:
◦ Under maintenance
◦ Expired license
◦ Incompatible firmware mode

If any of the Step 1 conditions are not met, the prevalidation window (Move profile
prevalidation table (page 115)) displays an error for this step.
2. Target resource validations—VCEM performs the following target resource validations:
• If the target device bay selected contains a server then the server must be powered off
before the export operation can be performed.
NOTE: If the target server is not powered off, you must power it off and perform the
export operation again.
• Ensures that the target bay device does not have a server profile assignment.

• Confirms that the target VC Domain Group that the server profile will be exported to has
a status of Configuration in synch. VC Domain Groups with other statuses such as the
following list cannot receive exported server profiles:
◦ Under maintenance
◦ Incompatible firmware
• Ensures that the target VC Domain Group virtual MAC, WWN and Serial Number range
types are compatible with addresses allocated in the selected server profile. See
Table 11 (page 31)) for more information.
If any of the Step 2 conditions are not met, the prevalidation window (Move profile
prevalidation table (page 115)) displays an error for this step.
3. Feature compatibility validations—The target VC Domain Group must support all the connections
and features defined by the selected server profile. VCEM performs the following validations
in this step:
• Ensures that the target VC Domain Group firmware mode supports iSCSI if the server
profile contains iSCSI connections
• Ensures that the target VC Domain Group supports FC connections if the server profile
contains them.
• Confirms that the target VC Domain Group firmware mode supports FCoE if the server
profile contains FCoE connections.
If any Step 3 condition is not attained, the prevalidation window (Move profile prevalidation
table (page 115)) displays an error status for this step.
4. Feature Validations related to Network—VCEM performs the following validations related to
the Ethernet connections data export:
• Confirms that the target VC Domain Group supports server profiles with Ethernet
connections defined as Multiple Networks. If the server profile has an Ethernet connection
using Multiple Networks, then the target VC Domain Group firmware mode must support
the server VLAN mapping feature, otherwise Step 4 displays an error status in the
prevalidation window (Move profile prevalidation table (page 115)).
• Ensures that the Ethernet networks used in the selected server profile exist in the target
VC Domain Group. If any network used in the profile does not exist in the target VC
Domain Group, VCEM automatically removes the reference to that network from the server
profile in order to allow it to be exported to the target VC Domain Group. Network names
used by the server profile Ethernet or iSCSI connections should match the network names
defined in the target VC Domain Group. Otherwise, the network name will be
disassociated from the specific server profile connection (Ethernet or iSCSI) and Step 4
displays a configuration status in the prevalidation window (Move profile prevalidation
table (page 115)). In this case after the export server profile operation is completed , you
must edit the server profile in the target VC Domain Group and assign an existing network
to the Ethernet or iSCSI connection so that the server profile network connectivity works
properly.
• Confirms that the network port speed defined in the server profile is less than or equal to
the maximum port speed defined for the target VC Domain Group network, otherwise
Step 4 displays an error status in the prevalidation window.
• Ensures that all VLAN network names for the Ethernet connections defined as multiple
connections exist in the target VC Domain Group. VLAN network names used by a server
profile connection that is defined as Multiple Networks must match the network names
Moving a server profile 117

defined in the target VC Domain Group. Otherwise Step 4 will show a warning status at
the prevalidation window.
• Confirms that all VLAN network names and their associated Shared Uplink Set exist in
the target VC Domain Group with the following conditions:
◦ Ethernet connections are defined as Multiple Networks.
◦ Multiple networks have the Force same VLAN mapping as Shared Uplink Sets option
selected.
If the server profile has an Ethernet connection defined using Multiple Networks configured
with the Force same VLAN mappings as Shared Uplink Sets option, then all the VLAN
networks names used by this Ethernet connection and its associated Shared Uplink Set
must match in the target VC Domain Group. The Shared Uplink Set defined in the target
VC Domain Group can contain different VLAN network associations other than the source
VC Domain Group, however, they must match the VLAN network associations used by
the server profile that is being exported. Otherwise Step 4 displays a warning status icon
in the prevalidation window.

5. Validating Fabric data—VCEM performs the following validations for fabric connections during
the export process:
• Ensures that the fabric names and I/O bays exist in the target VC Domain Group. Fabric
names and I/O bays used by the server profile FC and FCoE connections must match
the fabric names and I/O bay positions defined in the target VC Domain Group.
These two conditions are mandatory for the server profile FC/FCoE connection be exported
successfully. If the fabric name exists in the target VC Domain Group and if the I/O port
in use by the fabric matches between the source and the target VC Domain Groups then
Step 5 is successful.
• Confirms that the related I/O bay slice (horizontal adjacent pair of I/O bays containing
at least one VC FC or FlexFabric module) in use by the server profile connections exists
in the target VC Domain Group.
For example, consider server profile A with an FCoE connection defined as fabric
“FCoE_A” using I/O bay 3 in the source VC Domain Group which contains a VC
FlexFabric module, and you want to export this server profile to a target VC Domain
Group. In the target VC Domain Group, there is no fabric named “FCoE_A” and there
is no VC FlexFabric module in I/O bay 3. However the target VC Domain Group has
FCoE_B fabric using I/O bay 4 which contains a VC FlexFabric module that is the same
I/O bay slice the fabric “FCoE_A” was using in the source VC Domain Group.
If one of the fabrics from the I/O bay slice in use by the server profile connection does
not exist or is named differently in the target VC Domain Group, then the specific fabric
name is disassociated from the server profile FC or FCoE connection and Step 5 displays
a Configuration status in the prevalidation window. In this case, after the export server
profile operation is completed you must edit the server profile in the target VC Domain
Group and assign an existing fabric to the FC or FCoE connections. You will also need
to configure boot options for any of these connections, if necessary, so that the server
profile storage data or boot connectivity continues to work properly.
NOTE: There is no loss of WWNs. The FC or FCoE connection will remain in the server
profile (and related WWNs as well) and only the fabric is dissociated from the connection.
• Ensures that the source VC Domain Group I/O slice in use by server profile FC or FCoE
connections exists in the target VC Domain Group. If the I/O bay slice is not defined in
the target VC Domain Group, then Step 5 displays a Warning status in the prevalidation
window. In this case, HP recommends that you edit the VC Server Profile and remove the
FC or FCoE connections from the source server profile that is related to the nonexistent
I/O bays in the target VC Domain Group.
NOTE: The WWNs are removed and after exporting the server profile, you need to
create new FC or FCoE connections which will allocate new WWNs address.
If there are no errors or post-installation tasks, the server profile move completes without intervention.
NOTE: When moving profiles that SAN-boot from a Direct Attached fabric to a different c-Class
enclosure, you must edit the boot parameters to reflect the appropriate address which the 3PAR
array presents to the new enclosure.
Performing a VC Server Profile Failover

Virtual Connect Server Profile Failover is a VCEM feature that enables the automated movement
of VC server profiles and associated network connections to customer-defined spare servers in a
VC Domain Group. The manual movement of a VC server profile requires the following steps to
complete the operation, but VC Server Profile Failover combines these separate steps into one
seamless task:
Performing a VC Server Profile Failover 119

1. Power down the original or source server.
2. Select a new target server from the VC Domain Group spare pool.
3. Move the VC server profile to the target server.
4. Power up the new server.
VC Server Profile Failover operations require the source and target servers to be configured to
boot-from-SAN, and can be initiated from the VCEM graphical user interface (GUI) as a one-button
operation or from a command line interface (CLI). When used with the automatic event handling
functionality in Systems Insight Manager, VC Server Profile Failover operations can be automatically
triggered based user-defined events.
When selecting a target server from a pool of defined spare systems, VC Server Profile Failover
automatically chooses the same server model as the source server.
System administrators can use VC Server Profile Failover to perform the rapid and cost effective
recovery of physical servers within the same VC Domain Group with minimal administrator
intervention.
IMPORTANT: When you perform a VC Server Profile Failover, no reference is provided to the
VC Domain from Systems Insight Manager. To access this reference, you must correlate the Systems
Insight Manager and VC logs. For more information, see “Correlating VCEM operations in Systems
Insight Manager and VC logs”.
such as HP Matrix Operating Environment. Performing a failover of a
Server Profile to a designated spare blade may make it inconsistent
with the upper level manager. It is recommended to use the upper level
manager to edit this Server Profile. Type YES to proceed with this
operation.
NOTE: When failing over profiles that SAN-boot from a Direct Attached fabric to a different
c-Class enclosure, you must edit the boot parameters to reflect the appropriate address that the
3PAR array presents to the new enclosure.
Preconditions for VC Server Profile Failover

• Source and designated spare servers must be part of the same VC Domain Group.
• Designated spare servers are powered off.
• A spare server must be the same model as the source server.
Using spare bays

For information about designating spare bays, see “Designating spare bays” (page 126).
Initiating VC Server Profile Failover through the VCEM CLI

You can initiate VC Server Profile Failover through the VCEM CLI or GUI.
To perform VC Server Profile Failover tasks using the CLI, you must have Systems Insight Manager
administrative privileges.

To initiate VC Server Profile Failover using the CLI, enter C:\>VCEM -failover arguments,
then enter 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 Systems Insight Manager runs on the same
system as VCEM and full server discovery is operating in Systems Insight Manager.
For more information about using the CLI in VCEM, see the “Failover Command Line Interface
Usage in VCEM” (page 146).
Initiating VC Server Profile Failover through the VCEM GUI

1. Select an assigned server profile with an acceptable spare server.
2. (Optional) from the Filter list, select VC Domain or VC Domain Group, and click Filter.
3. Click VC Server Profile Failover. The Virtual Connect Enterprise Manager is
executing the request message appears.
Initiating VC Server Profile Failover using Systems Insight Manager Automatic Event
Handling
The VCEM CLI can be used to automatically trigger VC Server Profile Failovers using Systems
Insight Manager automatic event handling. A collection of sample failover SNMP traps exists in
the "Profile Failover Trigger Events” collection under “VCEM Events” in the VCEM user interface.
VCEM also provides two custom tools to facilitate automated VC Server Profile Failover.
To use automatic event handling in VCEM, the following prerequisites must be met:
• VCEM has been installed as part of a Systems Insight Manager installation.
• DNS is properly configured in the environment.
• The Administrator account is usable on the system in which VCEM and Systems Insight Manager
reside.
The VCEM custom tools enable an administrator to initiate a VC Server Profile Failover using
automatic event handling. Any administrator with full permissions within Systems Insight Manager
or VCEM can perform VC Server Profile Failover operations. The VCEM custom tools can be deleted
from the Systems Insight Manager or VCEM installation with no impact to other operations.
IMPORTANT: Enabling automated failover actions can impact other operations in a data center.
Before using this feature, you must fully review potential implications to other system resources and
data center services, and ensure compatibility with any other applications designed to perform
automatic event handling. Unintended failovers can result in the loss of data and unnecessary
system downtime.
To set up automated VC Server Profile Failover:
1. Enable Systems Insight Manager 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 Server 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.
Performing a VC Server Profile Failover 121

6. Select Run custom CMS tool, and then select VCEM Server Profile Failover by 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 Server Profile Failovers now occur whenever any designated system generates one of the events
within the event collection. When an event triggers a VC Server Profile Failover, a VCEM Failover
job appears to have originated from the administrator user account and fail over the system that
generated the event.
For more information about VC Server Profile Failover, see the failover white paper at http://
www.hp.com/go/vcem. For more information about Automatic Event Handling, see the HP Systems
Insight Manager User Guide at HP Enterprise Information Library.

6 Managing enclosure bay assignments
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 list can 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 check box enables you to see physical information such as power state,
UID LED state, blade model, and Auxiliary blades inside each bay in the list. The option is enabled
and selected by default only when filtering devices bays by VC Domain.
After selecting the options in the filter, click Filter.
Figure 79 Bays page
The following table describes the columns in the Bays page.
Item Description
Enclosure Enclosure name
Bay # Bay number
Spare Select spares to fail over a VC server profile to another

blade server.
Server Profile Server profile name
123
To see more information about bays, select the Show more details check box. The following table
describes the additional information that will be displayed.
Item Description
Server model Model of server
Power Server is powered-up or powered-down
UID Reports if the identification light on the device is

powered-up or powered-down
To see server bay status and blade server information (if there is a server in a selected bay), click
the bay number, then a status window appears. The following table lists the additional information
that appears.
Item Description
Assigned Server Profile Server profile name assigned to the bay
Enclosure Name Enclosure name where the bay is located.
UID Icon that indicates the Unit Identifier (UID) state: on, off, or
not available
Power Status/Control Icon that indicates the server power status
Serial Number Factory serial number for physical server

Serial Number (Logical) Logical Serial Number designated by server profile
UUID Factory UUID for physical server

UUID (Logical) Logical UUID designated by server profile
Product Name Model of server
Multiblade System Devices The multiblade system contains information regarding the
device bays which compose the multiblade system. The
information describes which bay contains the monarch
server and which bays contain auxiliary servers. The
following is an example of a four blade multiblade system:
Multiblade system size-4 Bay 1 - Monarch Bay 2 -
(Auxiliary Blade) Bay 3 - (Auxiliary Blade) Bay
4 - (Auxiliary Blade)
The following is an example of two blades in a multiblade

system:
Multiblade system size-2 Bay 3 - Monarch
Bay 4 - (Auxiliary Blade)
From the Bay screen, you can perform the following tasks:
• Power down a bay
• Assign a server profile to a bay
• Unassign a server profile from a bay
• Designate spare bays
• Perform a Server Profile Failover from the Bays page
Powering down a bay

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

Figure 80 Window displaying the power status of a bay
To remotely power down a bay:

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 server profile to
a bay procedure section.
• If the bay is currently powered up, then click Momentary Press, which automatically
powers down 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 at powering down the
bay have failed, such as attempting to shut down from the physical bay instead of remotely.
Figure 81 Bay status with press and hold
Powering down a bay 125

Assigning a server profile to a bay
You can assign a server profile to a bay only if the bay is not already associated with a server
profile and if the server is powered down. To assign a server profile to a bay:
2. (Optional) From the Filter list, select VC Domain or VC Domain Group, and click Filter.
3. Select the bay.
4. Click Assign Server Profile. The Assign Server Profile page appears.
5. Select an unassigned server profile.
message appears.
NOTE: You cannot assign a server profile to a covered bay. An error message similar to the
following is displayed:
Cannot assign server profile because the selected bay is covered.
Unassigning a server profile from a bay

You can only unassign a server profile from a bay if the bay is associated with a server profile
and if the server is powered down. To unassign a server profile from a bay:
2. (Optional) From the Filter list, select VC Domain or VC Domain Group.
3. Select the bay for which you want to unassign a server profile.
4. Click Unassign server profile. You are prompted to confirm the unassignment.
message appears.
Designating spare bays

1. Select one or more Spares check box for bays that do not have a server profile applied. A
asterisk symbol is displayed to indicate that the spares marked with a symbol must be
confirmed.
2. To confirm the spare, click Apply Spares.
You can initiate VC Server Profile Failover either through the command line interpreter (CLI) or
through the VCEM graphical user interface (GUI).
Designate spares according to the service level needs and the blade models being used. For
example, if a data center is using three blade models in the environment, designate a spare for
each of the three blade model types. These designated spares can be any systems that do not
already have a server profile assigned within the same VC Domain Group.
Performing a Server Profile Failover

To initiate a Server Profile failover:
2. (Optional) from the Filter list, select VC Domain or VC Domain Group, and click Filter.
3. Select a bay with an assigned server profile and with a spare server.
4. Click Failover. The message The Virtual Connect enterprise Manager is
executing the request appears.
5. Click OK to go to the Jobs page and monitor progress.

For more information about failover pre-requirements, see “Preconditions for VC Server Profile
Failover” (page 120)
Performing a Server Profile Failover 127

7 Managing MAC and WWN addresses
MAC Addresses
NOTE: A "VCEM-defined” range has been reserved, from which VCEM allocates MAC addresses.
VCEM no longer uses the “HP pre-defined” range for MAC address allocation. However, server
profiles created before VCEM 1.40 will continue to use the HP pre-defined addresses already
assigned to them.
When using VCEM-assigned MAC addresses, you can choose between VCEM-defined MAC
address ranges or user-defined MAC address ranges. You can use the HP predefined MAC address
range only to import server profiles or server profiles created on previous versions of VCEM.
• VCEM-defined MAC address ranges—HP recommends this range. This predefined range is
reserved and never appears as factory-default on any hardware. There are 131,072 unique
addresses from which VCEM automatically assigns to server profiles on demand.
• User-defined MAC address range—To prevent potential conflict with other hardware MAC
addresses in the environment, you can use a subrange of MAC addresses reserved by the
IEEE for locally administered MAC addresses. Ensure that the range does not conflict with any
Ethernet device already deployed within the enterprise.
To access the MAC addresses from the VCEM home page, click the MAC addresses hyperlink.
The MAC Ranges List page appears.
Figure 82 MAC Ranges List page
Tracking individual MAC addresses

Individual addresses in a MAC range (HP-predefined, VCEM-defined, or user-defined) can be
monitored by clicking the Individual addresses secondary tab within the MAC Ranges List page.
The following table lists and describes the MAC address status at Individual address page.
Item Description
Free Address available to use in VCEM.
In use Address currently used by a server profile in VCEM.

Item Description
External Address Addresses used by server profiles in a VC Domain that

have been released back to VCM and no longer managed
by VCEM.
Excluded Addresses Addresses that reside in a VCEM Exclusion range list.

VCEM will not allocate any address that is marked as
excluded.
Creating MAC exclusion ranges

VCEM requires that you define exclusion ranges for both MAC and WWN addresses if:
• VCEM and VC Domains outside of VCEM management are sharing the same user-defined
MAC and WWN ranges.
• VCEM is running in a federated CMS environment where multiple instances of the VCEM
application are operating on the same network.
NOTE: In the case of federated CMS environments, you can select from a pre-defined VCEM
MAC subrange during a new HP Insight Management DVD installation.
Exclusion ranges are used to set aside addresses that might be in use for other purposes within
your data center. Excluded address ranges are not assigned for use by VCEM.
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 from the MAC ranges list. You can also look at Range Usage
to determine the percentage of free exclusion ranges. The exclusion range must be contained
within the address range to which the exclusion range belongs.
4. Select the Exclusion ranges tab and choose from the list of ranges.
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. Manually enter the address range to exclude it.
Deleting MAC exclusion ranges

hyperlink.
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.
Before deleting the exclusion range, ensure all addresses within this range are not being used by
any other VC Domain or VCEM instance on your network.
Creating MAC exclusion ranges 129

Reclaiming external MAC addresses
When a VC Domain containing server profiles is removed from a VC Domain Group configured
to use user-defined MAC address ranges, VCEM reclassifies the addresses in the removed VC
Domain as external. This does not change the actual addresses for server profiles in the VC Domain.
Addresses identified as external are reserved for VC Domains outside of 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 an address, verify that the address is no longer used by a VC Domain outside of VCEM.
To reclaim MAC addresses:
hyperlink.
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 a custom MAC address range

Because the maximum range size is 131,072, a large range might take a few minutes to create.
You can create one custom range.
To add a custom MAC address range:
hyperlink.
3. Click Add custom. The Add Custom MAC Address Range information appears.
4. Enter custom MAC address range.
5. Click OK.
Editing a custom MAC address range

Because the maximum range size is 131,072, a large range might take a few minutes to edit. If
you are reducing the size of a custom range, verify that any addresses or exclusion ranges already
in use are not outside the edited range.
To edit a custom MAC address range:
hyperlink.
3. Select the custom MAC address range.
4. Click Edit.
5. Edit the custom MAC address range as necessary.
6. Click OK.
Removing a custom MAC address range

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 a custom MAC
address range:

1. From the Virtual Connect Enterprise Manager home page, under the Administration heading,
click the MAC addresses hyperlink.
3. Select the custom MAC address range.
5. Click OK.
WWN Addresses
NOTE: In VCEM 1.40 and later, a new “VCEM-defined” range has been reserved, from which
VCEM allocates WWN addresses. VCEM no longer uses the “HP pre-defined” range for WWN
address allocation. However, server profiles created before VCEM 1.40 will continue to use the
HP pre-defined addresses already assigned to them.
The WWN range used by the VCEM domain must be unique within the environment. HP provides
a set of predefined addresses that is reserved for VC and VCEM and does not conflict with server
factory-default WWNs.
Overall, WWN range management in VCEM is very similar to MAC ranges. VCEM allocates
WWNs automatically according to VC Domain Group configuration using HP-predefined,
VCEM-defined, or user-defined WWNs. You can use the HP-predefined range only to import server
profiles or server profiles created on previous versions of VCEM.
To access WWN addresses from the VCEM home page, click the World Wide Names hyperlink.
The WWN Ranges List page appears.
Figure 83 WWN Ranges List page
Tracking individual WWN addresses

Individual addresses in a WWN range (HP-predefined, VCEM-defined, or user-defined) can be
monitored by clicking on the Individual addresses secondary tab within the WWN Ranges List
page.
WWN Addresses 131

The following table lists and describes the WWN address status at Individual address page.
Item Description
Free Address available to use in VCEM.
In use Address currently used by a server profile in VCEM.
External Address Addresses used by server profiles in a VC Domain that has

been released back to VCM and no longer managed by
VCEM.
Excluded Addresses Addresses that reside in a VCEM Exclusion range list.

VCEM will not allocate any address that is marked as
excluded.
Creating WWN exclusion ranges

VCEM requires that you define exclusion ranges for both MAC and WWN addresses if:
• VCEM and VC Domains outside of VCEM management are sharing the same user-defined
MAC and WWN ranges.
• VCEM is running in a federated CMS environment where multiple instances of the VCEM
application are operating on the same network.
NOTE: In the case of federated CMS environments, you can select from a pre-defined VCEM
WWN subrange during a new HP Insight Management DVD installation.
Exclusion ranges are used to set aside addresses that might be in use for other purposes within
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 from the WWN Ranges list. The exclusion range must be
contained within the address range to which the exclusion range belongs.
4. Select the Exclusion ranges tab and choose from the list of ranges.
5. To create the exclusion range, click New.
IMPORTANT: External addresses that are included in a WWN exclusion range remain
external addresses. The status of an external address does not change if it is included in a
WWN exclusion range.
6. Manually enter the address range to exclude it.
Address management tasks

There is no longer a need to plan and create the exclusion ranges manually. The HP Insight
Management DVD installation automatically creates the necessary MAC and WWN exclusion
ranges in VCEM for subrange selection. Figure 84 and Figure 85 display MAC and WWN
exclusion ranges.

Figure 84 MAC exclusion ranges
Figure 85 WWN exclusion ranges
Using VCEM subranges in a federated CMS environment

In a federated CMS environment, it is critical to select unique pre-defined VCEM subranges during
HP Insight Management DVD installation for each CMS in the federation. This prevents the different
VCEM instances from using MAC or WWNs which belong to other instances. This also results in
an automatic creation of VCEM exclusion ranges for MAC or WWNs which do not belong to a
particular VCEM instance.
Managing exclusion ranges with multiple central management systems

The Insight Management installer provides 128 subranges for VCEM-Defined MAC address and
WWN ranges (size 1024) for user selection. The 128 subranges allows you to manage 128 CMSs
and the VCEM-defined range size (1024) in use by each CMS is enough to manage up to 16
enclosures in each CMS.
For a complete list of VCEM-defined MAC and WWN subranges, see “VCEM subranges”.
Extending VCEM in use ranges

If you selected the Multiple CMS checkbox on the VCEM Range selection screen at install time,
VCEM automatically creates 127 exclusion ranges after installation. If you need to manually
manage the WWN and MAC exclusion ranges to extend the current VCEM-defined range in use
by the VCEM instance:
1. From the CMS, go to the VCEM home page by selecting Tools→Integrated Consoles→Virtual
Connect Enterprise Manager (VCEM).
2. In the Administration section, click the MAC addresses link.
The VCEM-defined MAC address exclusion ranges will be displayed in groups of 10. Each
range defaults to a size of 1024 addresses. If a larger range is required, exclusion ranges
Address management tasks 133

may be deleted to increase the size of the remaining in use VCEM-defined range. To delete
an exclusion range, select the checkbox next to the name for those ranges, and click Delete.
Be sure the range deleted from exclusion range is not in use in any other VCEM instances (this
means, it must be part of the exclusion range in the other VCEM instances).
3. In the Administration section, click the World Wide Names link.
The VCEM-defined WWN exclusion ranges will be displayed in groups of 10. Each range
defaults to a size of 1024 addresses. If a larger range is required, exclusion ranges may be
deleted to increase the size of the remaining in use VCEM-defined range. To delete an exclusion
range, select the checkbox next to the name for those ranges, and click Delete. Be sure the
range deleted from the exclusion range is not in use in any other VCEM instances (this means,
it must be part of the exclusion range in the other VCEM instances).
If you had manually configured the exclusion ranges for VCEM-defined MAC and WWN
ranges you need to edit the exclusion ranges to reduce their size appropriately. Be sure the
addresses removed from the exclusion range are not in use in any other VCEM instances (this
means, they must be part of the exclusion range defined in the other VCEM instances).
Transferring all managed VC Domains from one VCEM instance to another

Use the procedure in the following example to transfer all managed VC Domains from one VCEM
instance to another VCEM instance. This example assumes that the source CMS is the VCEM
instance using subrange 1 which will be deactivated and all its managed VC Domains will be
transferred to the other VCEM instance (called target CMS) using subrange 2.
1. Remove all VC Domains (for example Domain_A, Domain_B, Domain_C) from the VCEM VC
Domain Group which resides in the source CMS.
2. Power off the source CMS. This guarantees that no more than one VCEM instance is using
that same subrange.
NOTE: The source CMS cannot be powered on again unless you provide a new VCEM
subrange. If you want to use the source CMS for other purposes, you must uninstall it along
with the whole Insight Management stack or guarantee that the CMS will be cleaned by either
installing a new operating system or reformatting the hard disk.
3. At the target CMS, browse to the MAC address management page and remove MAC exclusion
range1 from the VCEM-defined exclusion ranges.
4. At the target CMS, browse to the WWN management page and remove the WWN exclusion
range 1 from the VCEM-defined exclusion ranges.
5. At the target CMS, import all VC Domains which were removed from the source CMS into the
VCEM VC Domain Group. If the VC Domains configuration is not identical on the source and
target VCEM instances then create a new VC Domain Group on the target CMS with the
imported VC Domains.
For more information, go to: HP Enterprise Information Library, look in the White Papers section
for the HP Matrix Operating Environment Federated CMS Overview White Paper.
Transferring one managed VC Domain from one VCEM instance to another

Use the procedure in the following example to transfer a managed VC Domain from one VCEM
instance to another VCEM instance. This example assumes that the source CMS is the VCEM
instance using subrange 1 and the target CMS is the VCEM instance using subrange 2. In this
example one VC Domain (VC Domain A) is transferred from the source to the target VCEM instance
and both VCEM instances will continue to operate.

1. Identify which MAC and WWN addresses are used in the server profiles assigned to VC
Domain A. There are two options to do this:
• Manually inspect each server profile MAC and WWN address in use and take notes.
• Run the VCEM CLI Export Server Profile command which will export all server profile
information to a CSV file. For more information about the VCEM CLI, see the HP Virtual
Connect Enterprise Manager Command Line Interface User Guide.
2. Remove VC Domain A from the VC Domain Group which is managed by the source CMS.
3. Ensure that all VCEM MAC and WWN addresses in use by server profiles assigned to VC
Domain A are marked as “External” within the VCEM source CMS.
4. (Optional) Before other users reclaim those external MAC or WWN addresses, create a VCEM
exclusion range with those MAC and WWN addresses within the source CMS. This excludes
other users from reclaiming those external MAC or WWN addresses in use by VC Domain
A (which will be managed by another VCEM instance in the target CMS).
5. In the target CMS, browse to the MAC address management page and ensure that the specific
MAC addresses in use by each server profile in Domain A are removed from the VCEM
exclusion range. This can result in splitting an existing VCEM exclusion range into two or more
ranges. For example if VCEM MAC exclusion range for subrange 1 is defined as
00-21-5A-9B-00-00 to 00-21-5A-9B-03-FF and if MAC addresses in use by server profiles are
00-21-5A-9B-00-02, 00-21-5A-9B-00-03, 00-21-5A-9B-00-04, and 00-21-5A-9B-00-05 then
you must redefine the VCEM MAC subrange 1 as displayed in Table 19:
Table 19 Redefining VCEM MAC subrange 1
MAC Exclusion ranges Start End
ExclusionSubrange1-part1 00-21-5A-9B-00-00 00-21-5A-9B-00-01
ExclusionSubrange1-part2 00-21-5A-9B-00-06 00-21-5A-9B-03-FF
6. At the target CMS, browse to the WWN management page and make sure the specific
WWNs in use by each server profile in Domain A are removed from the VCEM exclusion
range. This can result in splitting an existing VCEM WWN exclusion range into two or more
ranges.
For example if VCEM WWN exclusion range for subrange 1 is defined as
50:01:43:80:02:A3:00:00 to 50:01:43:80:02:A3:03:FF, and if WWNs in use by server
profiles are 50:01:43:80:02:A3:00:02, 00-21-5A-9B-00-03, 00-21-5A-9B-00-06, and
00-21-5A-9B-00-07 then you must redefine the VCEM WWN subrange 1 as displayed in
Table 20:
Table 20 Redefining VCEM WWN subrange 1
MAC Exclusion ranges Start End
Subrange1-part1 50:01:43:80:02:A3:00:00 50:01:43:80:02:A3:00:01
ExclusionSubrange1-part2 50:01:43:80:02:A3:00:04 50:01:43:80:02:A3:00:05
ExclusionSubrange1-part3 50:01:43:80:02:A3:00:08 50:01:43:80:02:A3:03:FF
7. In the target CMS, import VC Domain A into the VC Domain Group. If the VC Domain A
configuration is not identical on the source and target VCEM instances then create a new VC
Domain Group with imported VC Domain A.
For more information, go to: HP Enterprise Information Library, then look in the White Papers section
Address management tasks 135

Consolidating multiple VCEM instances into a single VCEM instance
Use the following example scenario to transform multiple VCEM standalone instances (VCEM
subranges) into a single VCEM instance (big pool):
Consider that you have 3 central management systems (CMS), CMS#1 is using subrange #1,
CMS#2 is using subrange #2 and CMS#3 is using subrange #3, in a multi-CMS system or in the
Federated HP IO environment. You want CMS#2 to be the only CMS in a single VCEM instance.
1. At CMS#1, remove the VC Domain A from the VCEM VC Domain Group.
2. Power off CMS#1. This guarantees that no more than one VCEM instance is using that same
#01 subrange.
3. At the CMS#2 target, browse to the MAC address management page and remove the MAC
exclusion range #01.
4. At CMS#2, browse to the WWN management page and remove the exclusion range #01.
5. At CMS#2, import VC Domain A into the VCEM VC Domain Group.
6. At CMS#3, remove VC Domain C from VCEM VC Domain Group.
7. Power off CMS#3. This guarantees that no more than one VCEM instance is using the same
#03 subrange.
8. At the CMS#2 target, browse to the MAC address management page and remove the MAC
exclusion range #03.
9. At CMS#2, browse to the WWN management page and remove exclusion range #03.
10. At CMS#2, import VC Domain C into the VCEM VC Domain Group.
11. At CMS#2, remove all other VCEM pre-defined subranges from the exclusion list. This returns
the available addresses into a single large pool.
For more information, go to: HP Enterprise Information Library, look in the White Papers section
Displaying factory default MAC and WWN addresses

NOTE: There is not any label or attribute indicating that the MAC or WWN addresses displayed
are factory defaults, it is up to you to identify that.
For VC firmware 3.7x and later, you can view factory default MAC and WWN addresses for:
• The server profile edit page for assigned server profiles
• The server profile edit page for unassigned server profiles
• Each server profile edit page with Advanced Settings
• Imported server profiles from VCM with mixed connections (user-defined and factory default).
• The Server Profile Information details link
Figure 86 (page 137) shows the Server Profile Information details link

Figure 86 Server Profile Information details
NOTE: Factory default address information is only available for mapped connections.
Connections which are unmapped will continue to display as Factory-Default.
Deleting WWN exclusion ranges

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.
IMPORTANT: If the exclusion range includes external addresses, these external addresses
remain external, even if the exclusion range is removed.
To avoid conflicts, ensure all addresses within this range are not being used by any other
Fibre Channel device on your network.
Reclaiming external WWN addresses

When a VC Domain containing server profiles is removed from a VC Domain Group configured
to use User-Defined WWN address ranges, VCEM reclassifies the WWN addresses in the removed
VC Domain as external. This does not change the actual addresses for server profiles in the VC
Domain. Addresses identified as external are reserved for VC Domains outside of 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 an address, verify that the address is no longer used by a VC Domain outside of VCEM.
To reclaim WWN addresses:
click the World Wide Names hyperlink.
2. From the Select ranges to configure list, select WWN. The WWN Ranges List page appears.
3. Select a WWN address range.
Deleting WWN exclusion ranges 137

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

Because the maximum range size is 131,072, a large range might take a few minutes to create.
You can create one custom range.
To add WWN a custom address ranges:
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 a custom WWN address range

Because the maximum range size is 131,072, a large range might take a few minutes to edit. You
can create one custom range.
hyperlink.
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 a custom WWN address range

NOTE: Removing a custom WWN address range also removes its defined exclusion ranges.
2. Select the custom WWN range.
4. Click OK.

8 Working with Logical Serial Numbers
This section describes how to view logical serial numbers that exist in server profiles being managed
by VCEM. These numbers are displayed for informational purposes.
Logical serial numbers move with a server profile. The logical serial number is a 10-character
string.
NOTE: For informational purposes, logical serial numbers start with three characters of either
VCXNNNNNNN or VCYNNNNNNN where VCX indicates that the logical serial number was
created by VCM before having a VC Domain imported into VCEM. A logical serial number prefaced
by 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
page appears.
Figure 87 Logical serial number page
Identifying logical serial number values

The following table lists and describes the logical serial number status values.
Item Description
In use Logical serial number is currently used by a server profile

in VCEM.
External Logical serial numbers used by server profiles in a VC

Domain that has been released back to VCM and is no
longer managed by VCEM.
Identifying logical serial number values 139

9 Tracking VCEM job status
Jobs
The Jobs list provides detailed information about jobs that have occurred and are related to VCEM.
To view these 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 88 Jobs list
The following table lists describes the job item columns or drop-down menu in the Jobs list.
Item Description
Job ID Identifies the job number with the task performed
Task Describes the job performed or to be performed
Status Provides job status
Progress Describes the progress of the current job
User Name Identifies the user that performed the function and created
the job
Start Time Identifies job start time
End Time Identifies the time when the job was completed (if the job
is not complete, this field is blank).
Show Jobs by State and Filter drop-down menu Displays jobs by state and filters jobs by a specific state.
Job status message window

When 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 in Systems Insight Manager.
140 Tracking VCEM job status

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

To review the details of a particular job, click the hyperlink of the appropriate job name. The Job
Details window appears.
Deleting jobs
To delete a particular job or multiple jobs, click Delete. Only pending, failed, or completed jobs
can be deleted. You cannot delete a running job.
Reviewing job details 141

10 Upgrading VC firmware after VCEM is managing VC
Domains
The process for upgrading VC firmware requires extra steps when VCEM is managing the VC
Domain. VCEM gains exclusive access to managed domains. However, using the VC Domain
Maintenance capability, the VCM can be used to upgrade VC firmware while the VC Domain is
being managed by VCEM.
IMPORTANT: Starting with VCEM 7.1.1 or later versions of VC firmware prior to VC 3.30 are
not supported. If you have versions of VC firmware before 3.30 installed, an incompatible firmware
icon is displayed, and VCEM prevents most VC Domain, VC Domain group, and server profile
operations. You must upgrade to at least VC firmware 3.3x. See “Upgrading incompatible firmware
modes and versions” (page 27) for more information. While VCEM does not support these older
firmware versions, both VCEM and the Insight Managed System Setup Wizard will not prevent
you from licensing these older firmware versions.
Preparation checklist
Before upgrading VC firmware, you must ensure that the installed version of VCEM supports the
VC firmware upgrade. For more information, see the “VC Domain Group firmware compatibility”,
and the “VCEM supported VC features”.
The VC firmware version might require installation of a VCEM Firmware Support Update or new
version of VCEM. Ensure the following requirements have been met:
1. Download and install the VCEM Firmware Support Update or a new VCEM version that
supports the VC firmware.
2. Acquire the HP BladeSystem c-Class VC 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 VC firmware documentation. The VC firmware might have dependencies on
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 (iLO )
See the HP Insight Management Support Matrix at HP Enterprise Information Library for support
such as operating system and system type.
142 Upgrading VC firmware after VCEM is managing VC Domains

Performing the firmware update using the VC Domain Maintenance
capability
CAUTION: Do not update to VC firmware 3.7x or later if the VC Domain Group firmware mode
is 3.15. This is because VC firmware 3.7x and later are not compatible with VC firmware 3.15.
If you update to VC firmware 3.7x or later, your only options are to either remove the updated
VC Domain from the VC Domain Group, or to use VCSU to downgrade the VC Domain firmware
to the previous version.
HP recommends that you update to the VC Domain Group firmware version to VC firmware 3.30
or later before attempting to update a VC Domain in the VC Domain Group to VC firmware 3.7x
or later. See “Updating to VC firmware 3.7x or later” for more information.
1. From the VC Domains screen, select a VC Domain.

2. Click VC Domain Maintenance.
3. Click Make changes via VC Manager. VCM 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. Upgrade the firmware with the HP Virtual Connect Support Utility. See the HP BladeSystem
c-Class Virtual Connect Support Utility User Guide at http://www.hp.com/go/virtualconnect
for more information. Attempting to upgrade 3.0x or later through the VCM web interface
will fail due to the increased size of the firmware image.
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.
Performing firmware update without the VC Domain Maintenance capability

For VC firmware versions 3.5x and later use the VCSU in your environment. For update information,
see “Updating VC firmware”.
Performing the firmware update using the VC Domain Maintenance capability 143
11 Removing an external manager account
For VCEM to manage VC Domains (using VCM), the embedded software in a Virtual Connect
Ethernet module) VCEM uses programmatic interfaces with each VCM. VCEM automatically creates
an external manager account in each VCM for subsequent authentication.
NOTE: VCEM uses a Secure Sockets Layer (SSL) connection provided by Systems Insight Manager.
For more information about the available cipher suites and how to enable or disable them, see
the Understanding Systems Insight Manager security white paper at http://h18013.www1.hp.com/
products/servers/management/hpsim/infolibrary.html.
VCEM creates a local account on each VCM it manages. To prevent inadvertent modification, this
account is not visible from the user-interface on the VCM associated with the VC Domain being
managed by VCEM. This account has full privileges to the VCM and the credentials are used for
SOAP interfaces with the VCM, using a connection over Secure Sockets Layer (SSL). These
credentials are securely stored on the Central Management Server (CMS) used to run VCEM. Each
VCM managed by VCEM has a unique, randomly generated password.
Removing the external manager account removes VCM from VCEM control. Remove the account
using the following methods:
• Preferred method—Uses the VCEM user-interface and removes the account from VCM and
the credential store from VCEM.
◦ Remove the VC Domain from the VC Domain Group
• Alternate method—Uses the VCM command line interface to remove the account from the
VCM.
If the preferred method is not possible (for example, if the CMS where VCEM is installed is
inoperable or unreachable from the VC Domain), the VCM supports command line interfaces
that allow the external manager account to be deleted from the VCM and also allow a VCM
to be removed from VCEM control.
To remove the external manager account:
1. Telnet in to the VCM using an SSH connection such as SSH Administrator@xxx.xxx.xxx.xxx,
where xxx is the VC Domain IP address.
2. To determine the user name of the external manager account, from the VCM command
prompt, enter show external-manager. For this example, assume the user name
returned was xyz.
3. To disable the account, from the VCM command prompt, enter
set external-manager Username=xyz Enabled=false
Perform the following:
◦ To remove the account and release the VC Domain from VCEM control, from the
VCM command prompt, enter
remove 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: The "-quiet" option is used to suppress user confirmation prompts. This option is useful
for scripting operations. This option is available for the disable account, remove the account,
and release ranges commands.
144 Removing an external manager account

For more information, see the HP Virtual Connect Manager Command Line Interface User Guide
at http://www.hp.com/go/virtualconnect.
145
12 Failover Command Line Interface Usage in VCEM
VCEM provides support for two types of command line interfaces:
• Failover Command Line Interface—Performs several failover-related functions and is addressed
in this chapter. These same functions are also available in the VCEM GUI.
• The HP Virtual Connect Enterprise Manager Command Line Interface (VCEMCLI)—Can be
used as an alternate method for managing common VC operations. The VCEMCLI is also
useful when scripting bulk operations on multiple VC profiles. See the HP Virtual Connect
Enterprise Manager Command Line Interface User Guide for more information.
Perform VC Server Profile failover on specified VC Domain bay server

This CLI command initiates a VC server profile failover operation. Options for specifying the source
server as the VC server 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 is zero, and the following example output displays (through stdout) on the screen. The CLI
also displays the job number of the VCEM Failover job (represented by N below) that has just
been initiated.
Performing VC Server Profile Failover on the specified VC Domain Bay Server...

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

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 greater than zero and the associated error message appears. The following shows some
output examples.

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


Internal VCEM Error Message: Enclosure name contains too many characters - limit is 32
Internal VCEM Error Message: Invalid format for IP address - it must be: [0-255].[0-255].[0-255].[0-255]
List details for specified VCEM job

This CLI command can be used to list the details and status for a particular VCEM job and can be
used to determine the status of a CLI failover job.
>vcem –list –details –job JobNumber
If the CLI List Job Details command is successful, the exit code from the CLI is zero, and the
following example output appears (through stdout) on the screen.
>vcem –list –details –job 1

Listing details for specified VCEM Job...
Job Number: 1
Job Type: MDM
Job State: COMPLETED
Job Progress: % Complete, Time, Possible Error Msg, Possible Detailed Error Msg
Job Priority: 5
Job User Name: “MachineUserNameHere”
Job Create Time: 1:58:34 PM
Job Start Time: 1:58:34 PM
Job End Time: 1:58:42 PM
In the preceding example, the job state shows as completed. Valid values for this job state 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 the associated error message appears. The following shows some output examples.

ERROR (63) - Specified VCEM Job Number is not an integer

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

Show CLI usage online help
This 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 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}
CLI exit and error codes

The CLI returns a numeric value that either indicates success or a particular error or failure. The
CLI also displays an associated error message (through stdout). A zero returned value indicates
success. A return value greater than zero indicates an error or failure. The following list shows all
possible exit and error codes and messages that might be returned by the VCEM CLI.
VCEM CLI syntax error codes/messages
Code Error message
1 ERROR–Invalid command line syntax
2 ERROR–Invalid command line option
3 ERROR–Argument not allowed for this option
4 ERROR–Only one required argument allowed for this option
5 ERROR–Missing a required argument for this option
6 ERROR–Missing operational option
7 ERROR–Missing command line option(s)
8 ERROR–Invalid command line argument
9 ERROR–Duplicate options not allowed
10 ERROR–Option not allowed
VCEM CLI User Authorization and Login error codes/messages
Code Error Message
15 ERROR–Could not locate VCEM SOAP Service
16 ERROR–Could not login to VCEM

- Systems Insight Manager 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

13 Troubleshooting VCEM
When you are upgrading to a new and different CMS, or are moving to a 64-bit CMS, you might
need to migrate your data by using the Systems Insight Manager data migration tool. If you are
upgrading to a new version of VCEM on the same CMS, data migration with the Systems Insight
Manager data migration tool is not necessary. For more information, see the Data Migration of
an Existing Microsoft Windows CMS to a new Insight Management 7.2 system white paper on
the Systems Insight Manager Information Library at HP Enterprise Information Library.
NOTE: There are no updates for this release in this regard.
VC Domain configuration mismatch after FW upgrade from 4.20 to 4.40

Upgrading a VC domain that is running on FW 4.20 and has QoS (Quality of Service) configured
to FW 4.40 or newer results in a configuration mismatch on VCEM.
Suggested action
Open maintenance mode or edit a profile that is assigned to the domain to resynchronize the
domains in configuration mismatch status.
VCEM will present an unexpected error for profile operations on a blade

that is in EV-CORRUPTION state
In some rare scenarios the server blade may have its EV corrupted, due to a forced power off.
When trying to perform any operation to a server profile that is in this state via VCEM, the job
operation fails and an unexpected error is shown on job details.
Suggested action
To correct this issue, reset the server physically or issue the OA CLI command reset server
#. Then, reapply the profile. If issue still persists, clear the server BIOS settings, and reapply the
profile.
Deleting a large number of assigned profiles results in a timeout

If you are trying to delete 1000 or more assigned profiles, the deletion can either take a long time
to complete or can result in a timeout. HP recommends that you only delete less than 1000 assigned
profiles at a time.
Managing VC domains with Expanded VLAN capacity enabled

VCEM 7.1.1 or later is able to manage VC domains with Expanded VLAN capacity enabled.
CAUTION: Virtual Connect Manager 3.30 or later does not allow you to easily revert back from
Expanded VLAN capacity mode to Legacy capacity mode. To revert to Legacy capacity mode,
you must delete the VC domain in Virtual Connect Manager and then recreate it.
Using Expanded VLAN capacity

Virtual Connect Manager 3.7x or later has Expanded VLAN capacity mode enabled by default.
To add a VC Domain with VC FW 3.7x to a VC Domain Group prior to VC firmware 3.7x or
later, the VC Domain Group must have Expanded VLAN Capacity enabled.
NOTE: If the VC Domain Group was created with all VC Domains in Legacy VLAN Capacity
and the VC firmware is prior to 3.7x (3.30/3.51/3.60), when you update the VC firmware to
3.7x (3.70/3.75) or later, all VC Domains will continue in Legacy VLAN capacity.
VC Domain configuration mismatch after FW upgrade from 4.20 to 4.40 149

Adding a VC 3.70 or later Domain with IGMP No Flood enabled into a VC Domain
Group with group firmware mode 3.3x or 3.5x
IMPORTANT: IGMP behavior is configured by using Advanced Settings in the VCM GUI. VCM
3.70 allows administrators to select whether IGMP Snooping is enabled and whether to prevent
flooding of unregistered multicast traffic. These settings can be viewed in the Ethernet Common
Settings section of the VC Domain Group Properties or the VC Domain Properties displayed in
VCEM.
VCEM is unable to communicate to a VC Domain running VC firmware 3.70 after VCEM attempts
to configure the VC Domain using Prevent flooding of unregistered multicast traffic with a VC
Domain Group that disables the IGMP Snooping feature.
NOTE: This does not impact server blade I/O connectivity in the managed enclosures.
After the situation occurs, the VCEM job reports the failure immediately following the entry “Validated
VC Domain.” It contains the following message:
Error during Add VC Domain [xxxxx_vc_domain] to VC Domain Group.
Details: Virtual Connect is not responding. To resolve this issue:
1. Verify if the IP address is active (try to log to the Virtual Connect Manager via Onboard Administrator).
2. Verify that there are no network related issues between Virtual Connect Manager and VCEM (try to ping from
the command line of the Virtual Connect Enterprise Manager server to the Virtual Connect Manager. 3. Verify if
Virtual Connect is in the process of updating firmware. If so, wait for a few minutes and try again. 4. Verify
if Virtual Connect is in the process of failover. If so, wait for a few minutes and try again. 5. Check if the
Virtual Connect Manager user-interface is reporting a status of “Loading, please wait”. If so, wait for a few
minutes and try again.
VCM 3.70 stops responding for a short time period after receiving a VC Domain configuration
with IGMP Snooping disabled and IGMP NoFlood enabled. The IGMP NoFlood feature is only
available in VC 3.70 and later, so VCEM does not set IGMP NoFlood when propagating a pre-3.70
VC Domain configuration to a VC 3.70 Domain running in compatibility mode.
The following scenarios reproduce this issue for a VC Domain running VC firmware version 3.70
with IGMP NoFlood enabled in a VC Domain Group running Domain Group firmware mode prior
to 3.7x:
Adding a 3.70 or later VC Domain to a VC Domain Group in compatibility mode (3.30 or 3.50)
If a VC 3.70 Domain with IGMP NoFlood enabled is added to a VC Domain Group running
Domain Group Firmware Mode prior to 3.70 with IGMP Snooping disabled and the administrator
selects the VCEM option to overwrite the VC Domain 3.70 configuration. This is an uncommon
scenario because this option is only available for VC Domains without any server profiles.
If this occurs, use the following workaround:
1. Wait until the VC Domain restores communication with VCEM. The communication is restored
when you are able to login to the VCM web interface.
2. Use the VCM CLI to remove the external manager account (if present) from the VC Domain
that failed to be added to the VC Domain group. To remove the external manager account:
a. Telnet to the Virtual Connect Manager using an SSH connection such as SSH
Administrator@xxx.xxx.xxx.xxx, where xxx is the VC Domain IP address.
b. Determine the user name of the external manager account, from the VCM command
prompt and enter show external-manager. For this example, assume the user name
returned was xyz.
c. From the VCM command prompt, disable the account by entering set
external-manager Username=xyz Enabled=false.
d. If present, remove the external-manager account by entering the following at the VCM
command prompt:
remove external-manager Username=xyz mactype=Factory-Default
wwnType=Factory-Default serverIdType=Factory-Default

3. You can resolve this by either modifying the configuration and disabling IGMP No Flood on
the VC Domain that is being added into the VC Domain Group or by modifying the
configuration and enabling IGMP Snooping on the VC Domain Group using VC Domain
Maintenance.
a. Use one of the following options to disable IGMP No Flood on the VC Domain that is
being added to the VC Domain Group:
• From the VCM command line—Telnet into the VCM using an SSH connection such
as SSH Administrator@xxx.xxx.xxx.xxx, where xxx is the VC Domain IP address.
Enter set igmp NoFlood=false .
• From the VCM GUI—Clear the Prevent flooding of unregistered multicast traffic check
box.
b. Use one of the following options to enable IGMP Snooping on the VC Domain Group to
which the VC Domain will be added:
• From the VCEM GUI:
a. Start a VC Domain Maintenance operation on any VC Domain in the VC Domain
Group
b. Enable IGMP Snooping from the VCM CLI by telneting into VCM using an SSH
connection such as SSH Administrator@xxx.xxx.xxx.xxx, where xxx is the VC
Domain IP address of the VC Domain under maintenance
c. Enter set igmp Enabled=true.
• From the VCM GUI:
a. Enable IGMP Snooping by clicking the Enable IGMP Snooping check box
b. Browse to the VCEM GUI and complete VC Domain Maintenance.
4. Add the VC Domain to the VC Domain Group again.
Canceling Domain Maintenance

If the VC Domain Group currently has IGMP Snooping disabled and the administrator changes
the VC Domain 3.70 running in compatibility mode to enable both IGMP Snooping and IGMP
NoFlood, and then cancels the maintenance operation use the following workaround:
1. Wait until VCM restores communication with VCEM. The communication is restored when you
are able to log into the VCM web interface.
2. Access the VCM GUI or CLI for the VC Domain that failed to cancel maintenance.
3. Select one of the following options to disable IGMP No Flood
• From the VCM command line, telnet into VCM using an SSH connection such as SSH
Administrator@xxx.xxx.xxx.xxx, where xxx is the VC Domain IP address and enter set
igmp NoFlood=false.
• From VCM GUI, clear the Prevent flooding of unregistered multicast traffic check box.
4. Browse to the VCEM GUI and cancel the VC Domain Maintenance again.
Completing Domain Maintenance

If the VC Domain Group currently has IGMP Snooping enabled and the VC Domain 3.70 running
in compatibility mode has both IGMP Snooping and IGMP No Flood enabled and the administrator
disables IGMP Snooping in another VC Domain in the VC Domain Group and tries to complete
maintenance the 3.70 VC Domain is marked as a “configuration mismatch”. If the administrator
proceeds with the resynchronization process when prompted by VCEM, the failure will occur. Use
the following workaround if this situation occurs:
1. Wait until VCM restores communication with VCEM. The communication is restored when you
are able to log into the VCM web interface.
2. Access the VCM GUI or CLI for the VC Domain that failed to complete maintenance.
Managing VC domains with Expanded VLAN capacity enabled 151

3. Select one of the following options to disable IGMP No Flood:
• From the VCM CLI—Telnet into VCM using an SSH connection such as SSH
Administrator@xxx.xxx.xxx.xxx, where xxx is the VC Domain IP address and enter set
igmp NoFlood=false .
• From the VCM GUI—Clear the Prevent flooding of unregistered multicast traffic check
box.
4. Browse to the VCEM GUI and complete VC Domain Maintenance for the VC Domain.
For more information, see Customer Advisory PI51599 entitled “VCEM is unable to manage VC
3.70 Domains in compatibility mode with IGMP NoFlood enabled.”
Using Expanded VLAN capacity with the Cancel VC domain Maintenance operation
Cancelling maintenance mode in VCEM will not revert the Expanded VLAN capacity configuration
back to Legacy capacity mode.
If you enable Maintenance Mode, change Legacy capacity to Expanded VLAN capacity, and then
click Cancel VC domain Maintenance, VCEM cannot revert back to Legacy capacity mode in the
VC domain. Instead, the VC domain displays the “Under maintenance” icon and VCEM fails to
complete or cancel the maintenance operation. To resolve this, see the procedure to delete the
domain in “Using Expanded VLAN capacity ” (page 149).
Using iSCSI boot configuration with IE10 in compatibility view

The iSCSI boot configuration web GUI is not supported in IE10 compatibility view. Use IE10 without
compatibility view to make changes to the iSCSI boot configuration.
Using boot configuration with Internet Explorer browser in compatibility

view
The compatibility view of the Internet Explorer does not allow VCM to support the iSCSI or any
boot configuration web GUI.
Suggested action
Use Internet Explorer without compatibility view enabled to make changes to the boot configuration.
Cannot resynchronize VC Domain that has a configuration mismatch state

due to an enabled VC feature
If VCEM failed to resynchronize a VC Domain that is in a configuration mismatch state because
there are one or more VC features enabled (see Figure 89) you will need to perform the following
steps to correct the VC Domain:

Figure 89 Configuration mismatch details
1. Telnet into VCM using an SSH connection such as SSH

Administrator@xxx.xxx.xxx.xxx, where xxx is the VC Domain IP address to access
the VCM CLI.
2. Enter show external-manager at the VCM command prompt to determine the user name
of the external manager account. For this example, assume that the user name that is returned
is xyz.
3. Enter set external-manager Username=xyz Enabled=false to temporarily disable
the account.
4. Identify the features that are enabled and disable them. See “Requirements for adding a VC
Domain to a VC Domain Group” for more information on enabled features.
5. Enter set external-manager Username=xyz Enabled=true from the VCM command
prompt to enable the account.
6. Perform the VC Domain resynchronization operation again. For more information, see
“Resynchronizing a VC Domain with Configuration Mismatch”.
Updating VC firmware versions in a VC Domain to be compatible with

VC 3.7x or later
Since the release of VCEM 7.1.1 or later, VC firmware versions 3.7x and later are not compatible
with VC firmware versions prior to 3.3x.
NOTE: VC firmware 3.7x or later does not support HP 1/10 Gb VC-Enet and HP 1/10 Gb-Enet
modules. VCSU detects the old modules and will not proceed with the firmware update.
Suggested actions
Virtual Connect firmware compatibility mode allows administrators to update each VC Domain in
a VC Domain Group incrementally, rather than requiring that all VC Domains be updated at the
Updating VC firmware versions in a VC Domain to be compatible with VC 3.7x or later 153

same time. VC Domain Group firmware mode is the firmware level in which a VC Domain Group
operates.
NOTE: For GUI screens and buttons to perform the VC firmware updates described in the following
procedures, see “Updating VC firmware”.
To update a VC Domain to VC 3.7x or later from VC 3.18 or earlier:
1. Use VC Domain Maintenance to perform a firmware update to an intermediary version that
is supported by the new firmware first. For example, if the current VC Domain Group firmware
mode is 3.15 and the new firmware is 3.7x, update the firmware on all VC Domains from
the VC Domain Group to 3.5x or 3.6x.
2. After the firmware for all VC Domains has been updated to 3.5x or 3.6x, upgrade the VC
Domain Group firmware mode to 3.5x.
NOTE: VC 3.5x and VC 3.6x share the 3.5x VC Domain Group firmware mode. There is
no separate 3.6x VC Domain Group firmware mode.
3. From the VC Domains page in the VCEM GUI, select all VC Domains (which have just been
updated to 3.5x or 3.6x) from the VC Domain Group and the VC Domain Firmware Update...
GUI button. Then use the VCSU to update the VC firmware for each of the selected VC Domains.
4. Optional—Update the VC Domain Group firmware mode to 3.7x or later after the VC firmware
on all the VC Domains in the VC Domain Group has been updated to VC firmware 3.7x or
later.
The following steps are an alternate procedure to update from VC firmware 3.15-3.18 to VC
firmware 3.7x or the latest firmware version:
1. Remove the entire VC Domain Group from VCEM.
2. Update the VC firmware for all VC Domains directly to 3.7x or later.
3. Recreate the VC Domain Group using the updated VC Domains.
For more information, see “Creating a VC Domain Group”, “Updating VC firmware” or “Deleting
a VC Domain Group”.
If you are using HP Matrix Operating Environment infrastructure orchestration to manage logical
servers attached to server profiles, some additional steps may be necessary after removing and
recreating the VC Domain Group. See the HP Matrix Operating Environment Infrastructure
Orchestration User Guide at HP Enterprise Information Library.
Performance issues while using IE 8 or 9 with a large number of networks

There are performance issues observed after some extended amount of usage in the single and
multiple network selection windows on the Create Server Profile or Edit Server Profile screen. This
is observed while using IE 8 or IE 9 browsers. HP recommends that you use Google Chrome with
a large number of networks.
General
If you are logged into HP SIM using an account with insufficient access privileges and attempt to
execute the “VCEM Profile Failover by Hostname”, or “VCEM Profile Failover by IP address” custom
tools, the following message appears:
SSH public key authentication failed for user
To resolve this issue, log in to HP SIM with an account created with VCEM Domain Group Limited
Operator or higher permissions for the resource being managed and execute the VCEM Profile
Failover by Hostname or VCEM Profile Failover by IP address custom tools again.

VCEM performance
VCEM can be temporarily unresponsive if the CMS is under heavy load operation due to other
products such as Matrix OE. If this occurs the following message is displayed:
This action cannot be performed because the current user does not have
the required privileges.
To resolve this situation, wait until the CMS load is lighter and perform the operation again.
VC Domain Groups and VC Domain Management

• At times the network port speed configured as 10 Gb on a VC Domain that supports 10 Gb
incorrectly displays as Auto on a VC Domain that does not support 10 Gb.
This situation occurs when the Virtual Connect Manager user interface on the VC Domain
without the SFP-SR connector displays the network speed as Auto.
The Auto value appears only on the Virtual Connect Manager user interface. When VCEM
attempts to capture the network configuration from VCM, the information returned is 10Gb
and not Auto.
To resolve this issue:
1. Access the VCM user interface on the VC Domain that does not have the SFP-SR connector.
2. Edit the network with the incorrectly labeled Auto port speed to use another port speed
value (for example, 1 Gb).
3. Save the edits.
4. Edit the network again, and set the port speed to Auto.
• If, after performing data migration, you are running Virtual Connect Manager and try to access
a VCEM-managed VC Domain, the following error message appears:
VC Domain locked by Virtual Connect Enterprise Manager <CMS IP
address>.
1. Go to the CMS and invoke the MS-DOS command box.
2. Change the directory to the <DRIVE>\<VCEM INSTALLATION FOLDER>.
3. Run either of the following CLI commands:
◦ >vcem -updatevcmdesc
◦ >vcem -uvcm
To validate that the problem has been corrected, browse to the VCMs that showed the incorrect
message to ensure that the correct message is displayed.
• VCEM cannot manage a VC Domain that configures a Shared Uplink Set or Ethernet Network
with the following:
◦ Connection mode set to Failover
◦ More than one port with Port Role value set to Primary or no Port Role set to Primary
To resolve the issue, access VCM and set one port to be the primary.
• VCEM cannot manage a VC Domain that configures an Ethernet Uplink Port with a
Speed/Duplex value as Disabled. VCEM always replicates the VC Domain configuration
with Speed/Duplex set to Auto.
However, VCEM does not prevent you from adding a VC Domain that configures an Ethernet
Uplink Port with a Speed/Duplex value as Disabled to a VC Domain Group.
VCEM performance 155

• VCEM fails to add a VC Domain that configures an Ethernet Uplink Port with a Speed/Duplex
value as Disabled to the same VC Domain Group to which it previously belonged.
To resolve the issue, perform the following steps after the Add to VC Domain Group job failure:
1. Go to the VCM user interface.
2. Select values for the Speed/Duplex of Ethernet Uplink Ports according to VC Domain
Group Ethernet Uplink Port values.
3. Go to VCEM and re-add the VC Domain to the same VC Domain Group.
• VCEM cannot create a VC Domain Group or add a VC Domain to a VC Domain Group when
a backup VC module is discovered or if a failover of a VC module occurred in a redundancy
environment. The following error message appears:
The VC Domain [<VC Domain Name>] cannot be managed by VCEM. A
possible cause is that the current state of the VC Domain is unknown.
Verify HP Systems Insight Manager (HP SIM) is referencing the primary
VC Module. If not, run HP SIM discovery to update the reference.
To resolve this issue, perform a rediscovery on the Onboard Administrator IP address associated
with the VC Module and perform the VCEM operation again.
Jobs
System performance can slow down on the Jobs page when the number of jobs exceeds 20,000.
To maximize system performance, delete old jobs before the total number reaches this limit.
Server power management

VCEM might not correctly present the power state of a server when the server is powered off using
VCM.
Server profile operations

• To create profiles for Integrity server blades that boot from SAN, you must manually configure
the SAN boot entries in the blade server EFI console.
• If the server profile has Flex-10 connections enabled, and server blade NICs (onboard or
mezzanine card) are connected to HP 10/10 Gb-F Virtual Connect Ethernet Module, VC
requires you to power off the server blade to perform any server profile operation.
VC Profile Failover
• When you initiate a VC Profile Failover operation, VCEM does not check the compatibility of
the physical connections of the target server. The VC Profile Failover operation automatically
selects an available spare server of the same type and assigns the profile, but assumes that
the correct physical connections are already in place.
• When a Failover is executed, HP SIM may not update the servers information. To resolve this
issue, run a manual HP SIM discovery of the affected systems.
Profile operations fail, and the error message "An invalid boot LUN 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 3-digit decimal
between 0-255, or a 16-digit hexadecimal between 0 and FFFFFFFFFFFFFFFF.
This message appears whenever a profile move or failover operation is performed with a server
profile that has a boot LUN that fails to comply with the conditions stated here. This situation can
happen when you create a server profile in VCM, and then try to manage it with VCEM.

1. Select the VCEM Server 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 3-digit decimal between 0-255, or a 16-digit hexadecimal between 0 and
FFFFFFFFFFFFFFFF).
5. Click OK.
6. Monitor the job progress until it is complete.
After the operation completes, you can perform move and failover operations on the server profile.
Error popup appears when you select HP predefined ranges during remove
VC Domain from group or delete VC Domain Group operations
Using the web browser in the Japanese language causes an error popup to appear when you
select a HP pre-defined range to be used by a VC Domain that is being removed from a VC Domain
Group.
To resolve the issue:
1. Clear the Use Pre-defined range check box.
2. Enter the From and To values for the desired range in the text boxes.
3. Click OK. Wait until the process completes.
VCM shows an incorrect address for VCEM

When you log into the VCM while under VCEM control, the following message is displayed:
VC Domain locked by Virtual Connect Enterprise Manager [x.x.x.x]
The x.x.x.x in the message is an incorrect IP address for VCEM.
NOTE: The incorrect IP address does not have any impact on VCEM management of VCM.
Leaving the incorrect IP address in place does not break any VCEM operations. The IP address is
only displayed to inform you that VCM is managed by VCEM from that IP address.
To correct the IP address in VCM, complete the following steps:
1. Verify that the Windows host where VCEM is installed has its network adapters bound in the
correct order. The network adaptor handling communications with VCM should be first in the
list. If not, re-order the network adaptors so the network adaptor handling communications
with VCM is the first one in the list.
2. Open a Windows command prompt on the VCEM host and run the following command: >
Vcem –uvcm This command will get the IP address from the system and update all of the VC
Domains that VCEM is managing with the correct IP address.
Communicating with the enclosure OA

Although VCEM may report the VC Domain status as Managed by VCEM (green status) on the VC
Domains tab, the VC Domain might be indicating a different overall status which is not displayed
in the VCEM GUI. If the VC Domain has lost communication with the enclosure OA, VCM reports
this problem by modifying the VC Domain status. However, the VCEM GUI does not directly report
it and the only indicator for the communication issue will be one of the following error messages
displayed when VCEM is trying to communicate with VCM.
• Error message A
The operation cannot be performed because the VC Manager has lost communication with the enclosure's
[enclosure name] Onboard Administrator (OA). This communication issue could be intermittent. Go to VC
Manager to check the status of all the enclosures associated with that VC Domain. See the Virtual Connect
user guide for more information if there is a lost communication.
Error popup appears when you select HP predefined ranges during remove VC Domain from group or delete VC Domain 157
Group operations
• Error message B
The operation cannot be performed because the VC Manager has lost communication with the enclosure Onboard
Administrator (OA). This communication issue could be intermittent. Go to the VC Manager to check the
status of all the enclosures associated to that VC Domain. If there is a lost communication, go to Virtual
Connect user guide to get information on how to resolve this issue.
Once VCEM returns one of the error messages above, you must go to the VCM GUI and check
the VC Domain overall status to see if it is still reporting the communication problem with the
enclosure OA and then see the HP Virtual Connect Manager User Guide to resolve the situation.
MAC, WWN, and Serial Number management

You must verify that VC Domains within a network have unique MAC addresses, WWN addresses,
and serial numbers. Adding a VC Domain to a VC Domain Group or creating a VC Domain Group
does not verify that the profiles in a VC Domain use MAC or WWN addresses allocated in the
VCEM external address pool. You can overwrite the external addresses to become in use status.
To prevent external addresses from use in VCEM, add the addresses to the exclusion addresses
pool. If you plan to add the VC Domain back to VCEM, then you must also remove these addresses
from the exclusion addresses pool.
Duplicate MAC and WWN address assignments

Using VCEM 6.2 or 6.2.1 may result in duplicate MAC and WWN address assignments. This will
occur if a VC profile edit fails when removing iSCSI or FCoE connections via the VCEM Graphical
User Interface (GUI). The VCEM 6.2.2 or later upgrade contains a critical fix and is strongly
recommended to prevent this issue.
For more information, see the Support Communication - Customer Advisory, Document ID:
c02805558, available at: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?
objectID=c02805558&lang=en&cc=us&taskId=101&prodSeriesId=4194735&
prodTypeId=3709945
Unauthorized error when trying to access the VCEM home page

VCEM requires the CMS to be correctly registered in the DNS. Make sure Systems Insight Manager
can correctly discover the CMS. You might experience an unauthorized error page when trying
to access the VCEM home page if 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 status

A job might fail for several reasons. For more information about the reason of job failure and how
to correct the 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 text exceeds 256 characters.
If this occurs, to view the full job details, go to Systems Insight Manager left navigation
panel→Events→Shared→VCEM Events.
Enclosure has two Onboard Administrators, and one fails

If an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant
Onboard Administrator 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 Systems Insight
Manager discovery to rediscover the new Onboard Administrator IP address. If it is not rediscovered
then see the HP BladeSystem c-Class Onboard Administrator User Guide.

VCEM is prompting for Onboard Administrator credentials on a configured
VC Domain
VCEM might prompt for Onboard Administrator credentials on a VC Domain that has already
been configured where the Onboard Administrator has been imported and discovered. This issue
occurs when a backup VC is discovered or if a failover of a VC Module occurred in a redundant
environment. To correct this issue, perform a rediscovery on the Onboard Administrator IP address
associated with the VC Module.
VCM does not accept Onboard Administrator credentials

If a VC Domain is being managed by VCEM, and the Onboard Administrator is brought out of
VC mode, the following error message appears the next time you log into VCM:
The HP VC has lost its login credentials for the HP Onboard administrator
(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 credentials are not valid. This situation can occur when:
• Onboard Administrator is replaced or reset to factory default settings.
• The clear vcmode command was executed in the Onboard Administrator CLI.
• The VC Ethernet modules were temporarily replaced by another BladeSystem c-Class
interconnect module.
1. Select the affected VC Domain, and put it into VC Domain Maintenance.
2. Log in to VCM. Wait to be prompted for new Onboard Administrator credentials.
NOTE: You must have domain privileges to log in to VCM.
3. Provide the Onboard Administrator credentials, and then follow the VCM instructions.
4. In VCM, restart all servers with server profiles that report 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 Group

If the VC Domain is not the same as the VC Domain configuration group, then you might not be
able to add the VC Domain to the VC Domain Group. To correct this issue, 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”.
Also, a VC Domain might fail to add to the VC Domain Group for the following reasons:
• Network issues, specifically:
◦ Configuration mismatches between VC Domains and VC Domain Groups
◦ VC Domain Group with the latest version of firmware

• Invalid IP address
• Insufficient credentials permission
• Another VCEM external manager exists
• The models of VC modules installed in the VC Domain are different from those in the VC
Domain Group.
VCEM is prompting for Onboard Administrator credentials on a configured VC Domain 159

To correct this issue:
• Verify that you can ping from the command line of the VCEM server and log on to the VCM
using the browser.
• In a redundant environment, verify if the failover between an active and standby VC module
occurs. If so, wait until the failover completes and then perform Systems Insight Manager
rediscovery of Onboard Administrator associated with the VC module.
• VCEM requires VCM credentials with full privileges to communicate to Virtual Connect Module.
• Access the VCM CLI:
where xxx.xxx.xxx.xxx is the VC Domain IP address.
2. To determine the user name of the external manager account, enter show
external-manager in the VCM Command User Interface. The status of the external
manager name appears.
• When models of VC modules differ between the VC Domain Group and the VC Domain, you
can create a new VC Domain Group instead of adding to an existing VC Domain Group.
For more information, see the HP Virtual Connect Command Line Interface User Guide.
Unable to add an unconfigured VC Domain to a VC Domain Group

If you are unable to add an unconfigured server to a VC Domain Group, 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”.
Cannot manage a VC Domain when VC module failover is taking place

VCEM cannot create a VC Domain Group or add a VC Domain to a VC Domain Group when a
backup VC module is discovered or if a failover of a VC module occurred in a redundancy
environment. The following error message appears:
"The VC Domain [VC Domain Name] cannot be managed by VCEM. A possible
cause is that the current state of the VC Domain is unknown. Verify HP
Systems Insight Manager (Systems Insight Manager) is referencing the
primary VC Module. If not, run Systems Insight Manager discovery to
update the reference."
To correct this issue, perform an Systems Insight Manager discovery on the Onboard Administrator
IP address associated with the VC module and perform the VCEM operation again.
VC Domain displays Missing External Manager lock status

If the VC Domain displays a status of Missing External Manager lock icon, the external manager
lock has either been suspended or removed.
To correct this issue with a VC Domain, remove the VC Domain from VC Domain Group, break
the external manager lock and release these MAC, WWN, and serial number address ranges as
follows:
2. To determine the user name of the external manager account, from the VCM command prompt,
enter show external-manager. For this example, assume the user name returned was
xyz.
set external-manager Username=xyz Enabled=false.

• To remove the account and release the VC Domain from VCEM control, from the VCM
command prompt, enter
serverIdEnd=<>
NOTE: The “-quiet” option is used to suppress user confirmation prompts. This option is useful
for scripting operations. This option is available or later 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.
VC Domain displays Configuration Mismatch status

If the VCEM data does not match the data from the VC Domain, then the Configuration Mismatch
icon appears. This might happen when either the user suspends the external manager lock and
then modifies the VC 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 status

The Connectivity failure icon might appear if any of the following occur:
• Connection timeout, network problems, Virtual Connect Ethernet Modules physically not
available, or enclosure problem
• VCM 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 or there is a connection timeout or a network
problems between VCEM and VC Ethernet modules.
To correct this issue, verify the Ethernet VC Modules are still available and that there are no
network-related issues with the VCM. 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 VC module is taking
place.
To correct this issue:
1. Verify that the failover between the active and standby VC module is taking place.
2. Wait a few minutes until the failover completes, and then try again.
3. Log into VCM (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 Systems Insight Manager menu Options→Identify System or Options→Discovery.
• Verify firmware update is in progress and wait a few minutes until the update is completed.
Log into the VCM (https://<VCDomain_IP>), and verify the VC Domain firmware status, click
Domain Settings→Firmware Management.
VC Domain displays Configuration Mismatch status 161

• Run an Systems Insight Manager discovery to identify 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 check the connectivity using the information from Systems Insight Manager nodes after
the operation completes.
• Remove the VC Domain from the VC Domain Group, and run the Systems Insight Manager
discovery task to identify the new VC Domain IP address.
Break the external manager lock, and then release these MAC and WWN address ranges
as follows:
1. Telnet in to VCM using an SSH connection such as SSH Administrator@xxx.xxx.xxx.xxx,
2. To determine the user name of the external manager account, from the VCM command
returned was xyz.
3. To disable the account, from the VCM command prompt, enter set external-manager
Username=xyz Enabled=false.
• To remove the account and release the VC Domain from VCEM control, from the VCM
command prompt, enter:
serverIdEnd=<>
NOTE: The option “-quiet” is available to suppress user confirmation prompts. This
option is useful for scripting operations. This option is available for VC firmware for the
disable account, remove the account, and release ranges commands.
Cannot resynchronize VC Domain that is in Configuration Mismatch state

Attempting to resynchronize a VC Domain that is in Configuration Mismatch results in a failed job,
and the following message appears:
Unable to import the MAC, WWN or VSN addresses. Possible reasons include
1) Address is being used in VCEM.
2) Address conflicts with an existing Exclusion Range.
3) Address does not fall within the defined VCEM Global Range.
To identify why the issue occurred, consider that both VC and VCEM use two MAC addresses for
each Ethernet network connection and two WWN addresses for each Fibre Channel connection.
However, only one of these addresses appears in the user interface. When checking if a server
profile is using an address, you must consider both the displayed address and the hidden address.
When considering the hidden addresses, add 1 to the addresses that are being displayed. For
example, if a profile is using two Ethernet connections with MAC addresses 00-21-5A-9B-00-00
and 00-21-5A-9B-00-02 then the hidden addresses will be 00-21-5A-9B-00-01 and
00-21-5A-9B-00-03. In this example, the profile will be using four MAC addresses from
00-21-5A-9B-00-00 to 00-21-5A-9B-00-03.
1. Access VCM for the VC Domain that is in Mismatch Configuration state.

2. Verify the server profiles inside the VC Domain searching for MAC, WWN, or VSN (Virtual
Server Number) addresses that are:
• Already in use by VCEM—In this case, delete the server profiles that have addresses that
are reported as in use by VCEM.
• Inside an existing exclusion range in VCEM—In this case, remove the exclusion range or
adjust it so it does not contain the conflicting addresses.
• Outside any range known to VCEM—In this case, create a user defined address range
that contains all the addresses in use by the profiles.
After completing these steps, perform the VC Domain resynchronization operation again.
Operations fail in a VC Domain or VC Domain Group under maintenance

status
VCEM cannot perform any operations related to VC Domains in a VC Domain Group displaying
the Under Maintenance 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.
1. Click the VC Domains or VC Domain Groups tab.
a. Select the VC Domain or VC Domain Group
b. 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 the original VC Domain configuration, click Cancel.
b. Wait until the VC Domain Maintenance job has completed successfully. If the Cancel VC
Domain Maintenance 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 errors

Occasionally, when successfully performing a remove from VC Domain Group job, an error might
appear in 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 VCM using an SSH connection such as SSH Administrator@xxx.xxx.xxx.xxx, where
xxx.xxx.xxx.xxx is the VC Domain IP address.
2. To determine the user name of the external manager account, from the VCM command prompt,
enter show external-manager. For this example, assume the user name returned was
xyz.
Operations fail in a VC Domain or VC Domain Group under maintenance status 163

Remove the account and release the VC Domain from VCEM control by entering the following from
the VCM command prompt:
mactype=<Factory-Default/User-Defined>MacStart=<> MacEnt=<>
serverIDType=<Factory-Default/User-Defined> serverIDStart=<>
serverIdEnd=<>
NOTE: The option “-quiet” is available to suppress user confirmation prompts. This option is useful
for scripting operations.
Resolving an expired license status

If 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.
7. Perform the failed operation again.
Resolving database operation errors

Errors might occur during database operations if:
• VCEM tables are missing.
• Systems Insight Manager database is not running.
1. Check the mxdomainmgr.0.log file for errors related to the database. This log file may
indicate that the transaction log has filled up or that the database is experiencing some other
error.
2. If VCEM tables are missing, restore the VCEM database backup. For more information, see
“Backing up and restoring VCEM”.
3. Check the Systems Insight Manager database server status:
a. If the database server is remote, then log in to the database server.
b. In the Windows taskbar, check if the Microsoft SQL Server, Express or MSDE service is
running. A red status means they are not running.
c. Right-click the status, and then select Start.
4. If this issue still occurs, then uninstall and reinstall VCEM.
Errors occur while loading VCEM pages

Errors or hangs can be caused by problems with the Systems Insight Manager service or with the
web browser on the client system.
Action
To verify that Systems Insight Manager service is running:
1. Select Start→Control Panel→Administrative Tools→Services.
2. Check the Systems Insight Manager service status.
3. Right-click and select Start If the service is not running.

Choose one or try both of the following options to resolve issues with the web browser:
• Restart the browser
• Retry the operation with another browser supported by VCEM and Systems Insight Manager.
Failed to execute VCEM operation because VC firmware not supported

If the VC firmware version you have is not supported, then VCEM operations might fail to execute.
For more information about supported VC firmware, see http://www.hp.com/go/vcem.
To correct this issue if the VC firmware version is not supported, perform the following steps and
execute the VCEM operation again:
• Update VC firmware according VC firmware versions supported by VCEM using the VCSU.
To correct this issue if the VC Domain is under VCEM management, you can either:
• Remove the VC Domain from the VC Domain group. For more information, see“Removing a
VC Domain from a VC Domain Group”.
• If the VC Domain is not under maintenance , then enable VC Domain Maintenance and update
the VC firmware version to a VC firmware version supported by VCEM.
1. Use the VCSU to update VC firmware installed on the VC Domain.
2. 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.
Creating a server profile or adding a VC Domain with a server profile to

a VC Domain Group fails
Attempting to create a profile or adding a VC Domain to a VC Domain Group might fail if any of
the following occur:
• 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.
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.
Removing VCEM
IMPORTANT: You must remove VC Domains from VCEM management before removing VCEM.
If there are VC Domains being managed by VCEM during removal, the uninstaller fails and a
button appears in HP Insight Management. You can click on the button to get corrective action
instructions.
To remove VCEM:
• Select Start→All Programs→Insight Management→Uninstall HP Insight Management.
Failed to execute VCEM operation because VC firmware not supported 165

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

1. Double-click Add or Remove Programs.
2. Click Insight Management.
3. Click Remove.
Backing up and restoring VCEM

In the event of catastrophic and complete VCEM failure, all server blades continue to operate, and
the integrity 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 might occur, depending on the availability of a database backup. If no database
backup is available, then a large amount of information can be reconstructed from the contents of
the VC modules.
It is important that you understand what information is stored in the database, and can be lost
without proper backup practices. Table 21 (page 166) describes what components are recovered
if there is not backup strategy in place.
Table 21 Components restored without a backup strategy
Restored components Management server stored components
Local user accounts Unassigned server profiles
Network and SAN configurations VC Domain Groups
Assigned server profiles MAC and WWN exclusions
The Domain Network and SAN Configuration and assigned Server Profiles can be recovered from
the VC modules. The VC Domain Group definitions, MAC and WWN custom ranges, and MAC
and WWN address exclusions are stored only on the Management Server.
For more information on performing backups and restoring VCEM, see Backing up and restoring
HP Insight Management Central Management Server (Windows) available from the HP Enterprise
Information Library at HP Enterprise Information Library.
Cannot change the MAC/WWN/Serial Number ranges in VCM when

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 VCM even after removing all server profiles from the
VC Domain. This situation occurs because the MAC, WWN, and Serial Number ranges you
entered when releasing the VC Domain from VCEM have addresses externally in use by server
profiles under VCEM control.
To correct the issue, reset the VC module, and make sure you enter MAC and WWN ranges
defined as exclusion ranges in VCEM. From the VCM user interface, select Tools→Reset Virtual
Connect Manager.
VCEM database is inaccessible or irretrievable with no backup, or VCEM

file systems are corrupt with no backup
Without a backup, the VCEM cannot restore to the original point. But the network and SAN
configuration and assigned server profiles can be recovered from the VC modules. Reinstall the
VCEM to a fresh system, ensuring that the backup is well prepared on VCEM and its database on
the new VCEM. For more information, see “Backing up and restoring VCEM”.

1. Install VCEM 7.5 on a fresh machine.
2. Break the external manager lock in all VC Domains. To remove the external manager account:
a. Telnet in to VCM using an SSH connection such as SSH Administrator@xxx.xxx.xxx.xxx,
b. To determine the user name of the external manager account, from the VCM command
returned was xyz.
c. To disable the account, from the VCM command prompt, enter
d. To remove the account and release the VC Domain from VCEM control, from the VCM
command prompt, enter
serverIdEnd=<>
NOTE: “-quiet” is an option to suppress user confirmation prompts. This option is useful
for scripting operations. This option is available for VC firmware 1.3x and later for the
disable account, remove the account, and release ranges commands.
3. In Systems Insight Manager, perform a new discovery.

4. 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 add the same ranges to the new setup before proceeding.
5. Create new VC Domain Groups mirroring the prefail configuration specifying the currently
working credentials.
NOTE: Unassigned server profiles, external MAC and WWN addresses, and serial numbers
are not recovered with this procedure.
Enclosure has a hardware failure and must be replaced

An 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 settings are automatically cleared and all domain configuration is lost, including any existing
server profiles.
2. Select the VC Domain that has an enclosure problem.
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.
Enclosure has a hardware failure and must be replaced 167

7. To configure the VC Domain, see the HP Virtual Connect for c-Class BladeSystem User Guide.
link in the bottom left correctly points to the VC Domain Manager IP address.
9. To find the new enclosure, run an Systems Insight Manager discovery against the Onboard
Administrator IP address.
11. Select the newly discovered VC Domain, and then click Add to VC Domain Group. Wait for
the job to complete successfully. If the newly discovered VC Domain is in an unlicensed
enclosure, you will be prompted to provide licensing information.
Replacing VC modules
Replacing VC modules in a VC Domain managed by VCEM
To replace a VC Ethernet module or a VC Fibre Channel module of a VC Domain managed by
VCEM, perform the following steps:
4. Follow the steps in the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide
at http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
to replace the module based on the module model and disposition.
link in the bottom left portion of the screen correctly points to the VC Domain Manager IP
address.
6. Perform an Systems Insight Manager discovery against the Onboard Administrator IP address.
8. Select the same VC Domain, and then click New VC Domain Group or Add to VC Domain
Group. Wait for the job to complete successfully.
Verify that the VC Domain meets the requirements for creating a new VC Domain Group or
adding a VC Domain to a VC Domain Group.
For more information, see “Requirements for adding a VC Domain to a VC Domain Group”.
Replacing VC modules in interconnect bays three to eight in a VC Domain Managed

by VCEM without removing the VC Domain from the VC Domain Group
Perform the following steps to replace a VC Ethernet module or a VC Fibre Channel module in
interconnect bays three to eight of a VC Domain managed by VCEM without removing the VC
Domain from the VC Domain Group:
1. Ensure that the VC Domain Group has only one VC Domain.
2. Click VC Domains from the VCEM home page
NOTE: The modules to be replaced cannot be primary or secondary modules (usually

interconnect bays one and two) and the modules must have the same model.
4. Click VC Domain Maintenance... and then click Make Changes via VC Manager….
5. Replace the VC modules in the enclosure rear interconnect bays. Verify that the network and
SAN connections wired to the new VC modules are the same as the old connections.
6. Use the VCSU to update the Virtual Connect firmware using the same firmware version that
was previous installed on the replaced modules to make sure the new modules have the same
firmware version.

7. In the VCEM GUI click Complete VC Domain Maintenance. Wait for the job to complete
successfully
For specific information on how to use FlexFabric modules, see “Using FlexFabric modules”.
Failover fails to initiate with an ERROR (30) - Could not initiate failover;
nested exception is: java.net.SocketTimeoutException: Read timed out
This error can occur when the CLI cannot communicate to the VCEM SOAP interface. This
communication issue can occur when an IP address or hostname lookup takes more than a few
minutes to return or when there is a networking issue on the VCEM server. To resolve this issue,
verify that the Systems Insight Manager system is running properly by logging in and that the IP
address or hostname for the source system exists. If the IP address or hostname does not exist,
perform an Systems Insight Manager discovery.
VC Profile Failover fails during Onboard Administrator replacement

If an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant
Onboard Administrator might take several minutes to take over. The VC Profile Failover operation
fails when source or spare bays are associated with an enclosure while the redundant Onboard
Administrator is still in the process of taking over.
1. Wait until Onboard Administrator has failed over. Perform an Systems Insight Manager
discovery to rediscover the new Onboard Administrator IP address. If the address is not
rediscovered, see the HP BladeSystem c-Class Onboard 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.
After a VC Domain is removed from a VC Domain Group in VCEM, a

profile with external-managed status cannot be edited through VCM
This situation occurs when the profile address is not in the released range selected during the
remove VC Domain from VC Domain Group or delete entire VC Domain Group operations. To
make changes to such server profiles, you must bring the VC Domain under VCEM control and
then update the server profile through the VCEM profile editor.
Server profile edit operation fails when target server is powered on

If 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 profile job might fail with the following message in the job details:
Error during Edit server profile [Profile Name]. Details: This action
could not be performed because the server is powered on. Power down the
server associated with the Server Bay and retry the operation.
VCEM server profile editor allows 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
Domain firmware version allows if the target server is powered on.
Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is: java.net.SocketTimeoutException: 169
Read timed out
VC Domain status is "Mismatch Configuration" after cancel a VC Domain
Maintenance operation fails
This situation occurs when the server profiles from a VC Domain managed by VCEM have changed
and do not match the existing server profiles in the VCEM database. For example, restoring an
old VC Domain backup that has a different server profile from the current VC Domain in the VCEM
database.
In such cases, VCEM changes the VC Domain status to "Mismatch Configuration," and the VC
Domain Group to, "Configuration in sync." To continue managing this VC Domain with VCEM,
click VC Domain Maintenance to resynchronize the VC Domain configuration and server profiles.
Server profile job completed successfully but changes have not occurred
If a VC Domain is managed by VCEM, and Onboard Administrator is brought out of VC mode,
the following error message appears the next time you log in to VCM:
The HP Virtual Connect has lost its login credentials for the HP Onboard
Administrator (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
the credentials are not valid. This situation can occur when:
• Onboard Administrator is replaced or reset to factory default settings.
• The clear vcmode command was executed in the Onboard Administrator command line
interface.
• The VC Ethernet modules were temporarily replaced by another BladeSystem c-Class
interconnect module.
As a result, VCEM might display incorrect job results such as, "Completed with success," even
though the server profile changes have not taken effect. The ability of VCEM to manage server
profiles might also be affected for:
• Creating an unassigned server profile
• Editing of an assigned server profile
• Assigning a server profile
• Deleting a server profile
• Unassigning a server profile
The following bay operations might also be affected:
• Incorrect 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 VCM user interface, the following warning message might
appear:
The HP Virtual Connect has lost its login credentials for HP Onboard
Administrator (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 VCM to the Onboard
Administrator to retrieve and change configurations, statuses of the physical devices inside the
enclosure, and perform server power all on and off operations.
To correct this issue, restore communication between the Onboard Administrator and VCM by
performing the following:

1. Select the affected VC Domain, and start VC Domain Maintenance.
2. Log in to VCM. Wait to be prompted for new Onboard Administrator credentials.
NOTE: You must have domain privileges to log in to VCM.
3. Provide the Onboard Administrator credentials, and then follow the VCM instructions.
4. In VCM, 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.
Systems Insight Manager customizations for VCEM have not taken place
VCEM customizations for both Systems Insight Manager menu and Systems Insight Manager System
and Events collections might not take place when installing VCEM in standalone mode.
To correct this issue from the Systems Insight Manager menu, access Options→Managed
Environment, and click OK to apply VCEM customization to Systems Insight Manager menu and
Systems Insight Manager System and Events collections.
After a server profile failover, some connections defined in the server profile
are not functional
VCEM cannot identify if all Fibre Channel and Ethernet connections configured in a server profile
can be physically mapped to the physical ports of a server blade, because it is possible to have
Ethernet or Fibre 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
physical ports to receive the server profile.
• Install the necessary mezzanine cards in the server blade to provide the physical port mappings
required by the server profile connections.
VCEM page displays "Communication with the Systems Insight Manager

server has been lost"
When VCEM performs a task that requires some time to be completed, Systems Insight Manager
server might detect that the task is taking too long and the Communication with the Systems
Insight Manager server has been lost message appears.
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 Systems Insight Manager

If SNMP protocol is not correctly configured, then Systems Insight Manager cannot correctly discover
the unconfigured VC Domains, and then you might not be able to see such VC Domains or the VC
Domains list.
Systems Insight Manager customizations for VCEM have not taken place 171
To correct this issue, perform one of the following:
• Access the Systems Insight Manager menu, select Options→Discovery→Configure Global
Credentials, and verify the first SNMP read community string is public.
• Access the Systems Insight Manager menu, Select Options→Discovery→Configure Global
Protocol Settings, and verify that the Enable SNMP option is selected.
• Run Systems Insight Manager discovery on the Onboard Administrator IP address related to
the VC Domain by accessing the Systems Insight Manager menu and selecting Options→Identify
System or Options→Discovery.
Create VC Domain Group or Add VC Domain to VC Domain Group

operations fail and the message "An invalid boot LUN 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
decimal between 0–255, or a 16-digit hexadecimal value between 0 and FFFFFFFFFFFFFFFF.
This message appears whenever a Create VC Domain Group or an Add VC Domain to VC Domain
Group operation is performed and there is one or more server profiles inside the VC Domains that
have a boot LUN that does not comply with the required conditions.
To resolve this issue, use VCM 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 and
FFFFFFFFFFFFFFFF. To determine the correct value, access the storage management software or
ask the storage administrator. After entering the correct value, try the operation again.
NOTE: VCEM validates the format of the target LUN but does not verify that it is actually bootable.
Profile move, assign, or failover operations fail and the message "An
invalid boot LUN 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
decimal between 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 that has a boot LUN that fails to comply with the conditions stated here. This situation can
happen when a server profile is created in VCM, and then you try to manage it with VCEM.
VCEM validates the format of the target LUN but does not verify that it is actually bootable.
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
and FFFFFFFFFFFFFFFF).
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.

Profiles fail to boot from Direct Attached SAN Fabric after relocation to
another enclosure
Profiles can fail to boot because the 3PAR port WWN information differs with each c-Class
enclosure. To resolve this, edit the boot LUN parameters in the profile and ensure that it contains
the appropriate port WWN for the new enclosure that is hosting the profile.
Profiles fail to boot from Direct Attached SAN Fabric after relocation to another enclosure 173
14 Support and other resources
Information to collect before contacting HP
Be sure to have the following information available before you contact HP:
• Software product name
• Hardware product model number
• Operating system type and version
• Applicable error message
• Third-party hardware or software
• Technical support registration number (if applicable)
How to contact HP
Use the following methods to contact HP technical support:
• In the United States, see the Customer Service / Contact HP United States website for contact
options
http://welcome.hp.com/country/us/en/contact_us.html
• In the United States, call 1-800-HP-INVENT (1-800-474-6836) to contact HP by telephone.
This service is available 24 hours a day, 7 days a week. For continuous quality improvement,
conversations might be recorded or monitored.
• In other locations, see the Contact HP Worldwide website for contact options:
http://welcome.hp.com/country/us/en/wwcontact.html
Security bulletin and alert policy for non-HP owned software components
Open source software (such as OpenSSL) or third-party software (such as Java) are sometimes
included in HP products. HP discloses that the non-HP owned software components listed in the
Insight Management end user license agreement (EULA) are included with Insight Management.
The EULA is included with the Insight Management Installer on Insight Management DVD #1.
HP addresses security bulletins for the software components listed in the EULA with the same level
of support afforded HP products. HP is committed to reducing security defects and helping you
mitigate the risks associated with security defects when they do occur.
When a security defect is found, HP has a well defined process that culminates with the publication
of a security bulletin. The security bulletin provides you with a high level description of the problem
and explains how to mitigate the security defect.
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/country/us/en/contact_us.html
Registering for software technical support and update service

Insight Management includes one year of 24 x 7 HP Software Technical Support and Update
Service. This service provides access to HP technical resources for assistance in resolving software
implementation or operations problems.
The service also provides access to software updates and reference manuals in electronic form as
they are made available from HP. Customers who purchase an electronic license are eligible for
electronic updates.

With this service, Insight Management customers benefit from expedited problem resolution as
well as proactive notification and delivery of software updates. For more information about this
service, see the following website:
http://www.hp.com/services/insight
Registration for this service takes place following online redemption of the license certificate.
How to use your software technical support and update service

As HP releases updates to software, the latest versions of the software and documentation are
made available to you. The Software Updates and Licensing portal gives you access to software,
documentation and license updates for products on your HP software support agreement.
You can access this portal from the HP Support Center:
HP Support Center
After creating your profile and linking your support agreements to your profile, see the Software
Updates and Licensing portal at http://www.hp.com/go/hpsoftwareupdatesupport to obtain
software, documentation, and license updates.
HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources:
• In the United States, see the HP U.S. service locator website:
http://www.hp.com/service_locator
• In other locations, see the Contact HP worldwide website:
http://www.hp.com/go/assistance
Related information
The following documents and websites provide related information.
Documents
• HP Insight Management Installation and Upgrade Release Notes
• HP Insight Management Support Matrix
• HP Virtual Connect Enterprise Manager Release Notes
• HP Virtual Connect Enterprise Manager Command Line Interface User Guide
For more information about VCM see:
• BladeSystem c-Class Solution Overview
• HP Virtual Connect for c-Class BladeSystem User Guide
• HP Virtual Connect Manager Release Notes
Websites
For more VCEM resources see:
http://www.hp.com/go/vcem
Typographic conventions
This document uses the following typographical conventions:
Book title The title of a book. On the web, this can be a hyperlink to the
book itself.
Command A command name or qualified command phrase.
HP authorized resellers 175

Computer output Text displayed by the computer.
Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you
must hold down the key labeled Ctrl while you press another key
or mouse button.
ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH.
ERROR NAME The name of an error, usually returned in the errno variable.
Key The name of a keyboard key. Return and Enter both refer to the
same key.
Term The defined use of an important word or phrase.
User input Commands and other text that you type.
Replaceable The name of a placeholder in a command, function, or other
syntax display that you replace with an actual value.
[] The contents are optional in syntax. If the contents are a list
separated by |, you must choose one of the items.
{} The contents are required in syntax. If the contents are a list
separated by |, you must choose one of the items.
... The preceding element can be repeated an arbitrary number of
times.
Indicates the continuation of a code example.
| Separates items in a list of choices.
WARNING A warning calls attention to important information that if not
understood or followed will result in personal injury or
nonrecoverable system problems.
CAUTION A caution calls attention to important information that if not
understood or followed will result in data loss, data corruption,
or damage to hardware or software.
IMPORTANT This alert provides essential information to explain a concept or
to complete a task
NOTE A note contains additional information to emphasize or supplement
important points of the main text.

15 Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation,
send a message to:
docsfeedback@hp.com
Include the document title and part number in your message. All submissions become the property
of HP.
177
A VCEM subranges
The 128 MAC and WWN default subranges available to VCEM are listed in the following table.
Each subrange has a default size of 1024. Use the values in this table if you have to manually
edit the VCEM subranges to change the size of a subrange or create exclusion ranges.
Table 22 MAC and WWN subranges
VCEM MAC WWN
Subrange
Start End Start End
1 00-21-5A-9B-00-00 00-21-5A-9B-03-FF 50:01:43:80:02:A3:00:00 50:01:43:80:02:A3:03:FF
2 00-21-5A-9B-04-00 00-21-5A-9B-07-FF 50:01:43:80:02:A3:04:00 50:01:43:80:02:A3:07:FF
3 00-21-5A-9B-08-00 00-21-5A-9B-0B-FF 50:01:43:80:02:A3:08:00 50:01:43:80:02:A3:0B:FF
4 00-21-5A-9B-0C-00 00-21-5A-9B-0F-FF 50:01:43:80:02:A3:0C:00 50:01:43:80:02:A3:0F:FF
5 00-21-5A-9B-10-00 00-21-5A-9B-13-FF 50:01:43:80:02:A3:10:00 50:01:43:80:02:A3:13:FF
6 00-21-5A-9B-14-00 00-21-5A-9B-17-FF 50:01:43:80:02:A3:14:00 50:01:43:80:02:A3:17:FF
7 00-21-5A-9B-18-00 00-21-5A-9B-1B-FF 50:01:43:80:02:A3:18:00 50:01:43:80:02:A3:1B:FF
8 00-21-5A-9B-1C-00 00-21-5A-9B-1F-FF 50:01:43:80:02:A3:1C:00 50:01:43:80:02:A3:1F:FF
9 00-21-5A-9B-20-00 00-21-5A-9B-23-FF 50:01:43:80:02:A3:20:00 50:01:43:80:02:A3:23:FF
10 00-21-5A-9B-24-00 00-21-5A-9B-27-FF 50:01:43:80:02:A3:24:00 50:01:43:80:02:A3:27:FF
11 00-21-5A-9B-28-00 00-21-5A-9B-2B-FF 50:01:43:80:02:A3:28:00 50:01:43:80:02:A3:2B:FF
12 00-21-5A-9B-2C-00 00-21-5A-9B-2F-FF 50:01:43:80:02:A3:2C:00 50:01:43:80:02:A3:2F:FF
13 00-21-5A-9B-30-00 00-21-5A-9B-33-FF 50:01:43:80:02:A3:30:00 50:01:43:80:02:A3:33:FF
14 00-21-5A-9B-34-00 00-21-5A-9B-37-FF 50:01:43:80:02:A3:34:00 50:01:43:80:02:A3:37:FF
15 00-21-5A-9B-38-00 00-21-5A-9B-3B-FF 50:01:43:80:02:A3:38:00 50:01:43:80:02:A3:3B:FF
16 00-21-5A-9B-3C-00 00-21-5A-9B-3F-FF 50:01:43:80:02:A3:3C:00 50:01:43:80:02:A3:3F:FF
17 00-21-5A-9B-40-00 00-21-5A-9B-43-FF 50:01:43:80:02:A3:40:00 50:01:43:80:02:A3:43:FF
18 00-21-5A-9B-44-00 00-21-5A-9B-47-FF 50:01:43:80:02:A3:44:00 50:01:43:80:02:A3:47:FF
19 00-21-5A-9B-48-00 00-21-5A-9B-4B-FF 50:01:43:80:02:A3:48:00 50:01:43:80:02:A3:4B:FF
20 00-21-5A-9B-4C-00 00-21-5A-9B-4F-FF 50:01:43:80:02:A3:4C:00 50:01:43:80:02:A3:4F:FF
21 00-21-5A-9B-50-00 00-21-5A-9B-53-FF 50:01:43:80:02:A3:50:00 50:01:43:80:02:A3:53:FF
22 00-21-5A-9B-54-00 00-21-5A-9B-57-FF 50:01:43:80:02:A3:54:00 50:01:43:80:02:A3:57:FF
23 00-21-5A-9B-58-00 00-21-5A-9B-5B-FF 50:01:43:80:02:A3:58:00 50:01:43:80:02:A3:5B:FF
24 00-21-5A-9B-5C-00 00-21-5A-9B-5F-FF 50:01:43:80:02:A3:5C:00 50:01:43:80:02:A3:5F:FF
25 00-21-5A-9B-60-00 00-21-5A-9B-63-FF 50:01:43:80:02:A3:60:00 50:01:43:80:02:A3:63:FF
26 00-21-5A-9B-64-00 00-21-5A-9B-67-FF 50:01:43:80:02:A3:64:00 50:01:43:80:02:A3:67:FF
27 00-21-5A-9B-68-00 00-21-5A-9B-6B-FF 50:01:43:80:02:A3:68:00 50:01:43:80:02:A3:6B:FF
28 00-21-5A-9B-6C-00 00-21-5A-9B-6F-FF 50:01:43:80:02:A3:6C:00 50:01:43:80:02:A3:6F:FF
29 00-21-5A-9B-70-00 00-21-5A-9B-73-FF 50:01:43:80:02:A3:70:00 50:01:43:80:02:A3:73:FF
30 00-21-5A-9B-74-00 00-21-5A-9B-77-FF 50:01:43:80:02:A3:74:00 50:01:43:80:02:A3:77:FF
178 VCEM subranges

Table 22 MAC and WWN subranges (continued)
VCEM MAC WWN
Subrange
Start End Start End
31 00-21-5A-9B-78-00 00-21-5A-9B-7B-FF 50:01:43:80:02:A3:78:00 50:01:43:80:02:A3:7B:FF
32 00-21-5A-9B-7C-00 00-21-5A-9B-7F-FF 50:01:43:80:02:A3:7C:00 50:01:43:80:02:A3:7F:FF
33 00-21-5A-9B-80-00 00-21-5A-9B-83-FF 50:01:43:80:02:A3:80:00 50:01:43:80:02:A3:83:FF
34 00-21-5A-9B-84-00 00-21-5A-9B-87-FF 50:01:43:80:02:A3:84:00 50:01:43:80:02:A3:87:FF
35 00-21-5A-9B-88-00 00-21-5A-9B-8B-FF 50:01:43:80:02:A3:88:00 50:01:43:80:02:A3:8B:FF
36 00-21-5A-9B-8C-00 00-21-5A-9B-8F-FF 50:01:43:80:02:A3:8C:00 50:01:43:80:02:A3:8F:FF
37 00-21-5A-9B-90-00 00-21-5A-9B-93-FF 50:01:43:80:02:A3:90:00 50:01:43:80:02:A3:93:FF
38 00-21-5A-9B-94-00 00-21-5A-9B-97-FF 50:01:43:80:02:A3:94:00 50:01:43:80:02:A3:97:FF
39 00-21-5A-9B-98-00 00-21-5A-9B-9B-FF 50:01:43:80:02:A3:98:00 50:01:43:80:02:A3:9B:FF
40 00-21-5A-9B-9C-00 00-21-5A-9B-9F-FF 50:01:43:80:02:A3:9C:00 50:01:43:80:02:A3:9F:FF
41 00-21-5A-9B-A0-00 00-21-5A-9B-A3-FF 50:01:43:80:02:A3:A0:00 50:01:43:80:02:A3:A3:FF
42 00-21-5A-9B-A4-00 00-21-5A-9B-A7-FF 50:01:43:80:02:A3:A4:00 50:01:43:80:02:A3:A7:FF
43 00-21-5A-9B-A8-00 00-21-5A-9B-AB-FF 50:01:43:80:02:A3:A8:00 50:01:43:80:02:A3:AB:FF
44 00-21-5A-9B-AC-00 00-21-5A-9B-AF-FF 50:01:43:80:02:A3:AC:00 50:01:43:80:02:A3:AF:FF
45 00-21-5A-9B-B0-00 00-21-5A-9B-B3-FF 50:01:43:80:02:A3:B0:00 50:01:43:80:02:A3:B3:FF
46 00-21-5A-9B-B4-00 00-21-5A-9B-B7-FF 50:01:43:80:02:A3:B4:00 50:01:43:80:02:A3:B7:FF
47 00-21-5A-9B-B8-00 00-21-5A-9B-BB-FF 50:01:43:80:02:A3:B8:00 50:01:43:80:02:A3:BB:FF
48 00-21-5A-9B-BC-00 00-21-5A-9B-BF-FF 50:01:43:80:02:A3:BC:00 50:01:43:80:02:A3:BF:FF
49 00-21-5A-9B-C0-00 00-21-5A-9B-C3-FF 50:01:43:80:02:A3:C0:00 50:01:43:80:02:A3:C3:FF
50 00-21-5A-9B-C4-00 00-21-5A-9B-C7-FF 50:01:43:80:02:A3:C4:00 50:01:43:80:02:A3:C7:FF
51 00-21-5A-9B-C8-00 00-21-5A-9B-CB-FF 50:01:43:80:02:A3:C8:00 50:01:43:80:02:A3:CB:FF
52 00-21-5A-9B-CC-00 00-21-5A-9B-CF-FF 50:01:43:80:02:A3:CC:00 50:01:43:80:02:A3:CF:FF
53 00-21-5A-9B-D0-00 00-21-5A-9B-D3-FF 50:01:43:80:02:A3:D0:00 50:01:43:80:02:A3:D3:FF
54 00-21-5A-9B-D4-00 00-21-5A-9B-D7-FF 50:01:43:80:02:A3:D4:00 50:01:43:80:02:A3:D7:FF
55 00-21-5A-9B-D8-00 00-21-5A-9B-DB-FF 50:01:43:80:02:A3:D8:00 50:01:43:80:02:A3:DB:FF
56 00-21-5A-9B-DC-00 00-21-5A-9B-DF-FF 50:01:43:80:02:A3:DC:00 50:01:43:80:02:A3:DF:FF
57 00-21-5A-9B-E0-00 00-21-5A-9B-E3-FF 50:01:43:80:02:A3:E0:00 50:01:43:80:02:A3:E3:FF
58 00-21-5A-9B-E4-00 00-21-5A-9B-E7-FF 50:01:43:80:02:A3:E4:00 50:01:43:80:02:A3:E7:FF
59 00-21-5A-9B-E8-00 00-21-5A-9B-EB-FF 50:01:43:80:02:A3:E8:00 50:01:43:80:02:A3:EB:FF
60 00-21-5A-9B-EC-00 00-21-5A-9B-EF-FF 50:01:43:80:02:A3:EC:00 50:01:43:80:02:A3:EF:FF
61 00-21-5A-9B-F0-00 00-21-5A-9B-F3-FF 50:01:43:80:02:A3:F0:00 50:01:43:80:02:A3:F3:FF
62 00-21-5A-9B-F4-00 00-21-5A-9B-F7-FF 50:01:43:80:02:A3:F4:00 50:01:43:80:02:A3:F7:FF
63 00-21-5A-9B-F8-00 00-21-5A-9B-FB-FF 50:01:43:80:02:A3:F8:00 50:01:43:80:02:A3:FB:FF
64 00-21-5A-9B-FC-00 00-21-5A-9B-FF-FF 50:01:43:80:02:A3:FC:00 50:01:43:80:02:A3:FF:FF
65 00-21-5A-9C-00-00 00-21-5A-9C-03-FF 50:01:43:80:02:A4:00:00 50:01:43:80:02:A4:03:FF
179
VCEM MAC WWN
Subrange
Start End Start End
66 00-21-5A-9C-04-00 00-21-5A-9C-07-FF 50:01:43:80:02:A4:04:00 50:01:43:80:02:A4:07:FF
67 00-21-5A-9C-08-00 00-21-5A-9C-0B-FF 50:01:43:80:02:A4:08:00 50:01:43:80:02:A4:0B:FF
68 00-21-5A-9C-0C-00 00-21-5A-9C-0F-FF 50:01:43:80:02:A4:0C:00 50:01:43:80:02:A4:0F:FF
69 00-21-5A-9C-10-00 00-21-5A-9C-13-FF 50:01:43:80:02:A4:10:00 50:01:43:80:02:A4:13:FF
70 00-21-5A-9C-14-00 00-21-5A-9C-17-FF 50:01:43:80:02:A4:14:00 50:01:43:80:02:A4:17:FF
71 00-21-5A-9C-18-00 00-21-5A-9C-1B-FF 50:01:43:80:02:A4:18:00 50:01:43:80:02:A4:1B:FF
72 00-21-5A-9C-1C-00 00-21-5A-9C-1F-FF 50:01:43:80:02:A4:1C:00 50:01:43:80:02:A4:1F:FF
73 00-21-5A-9C-20-00 00-21-5A-9C-23-FF 50:01:43:80:02:A4:20:00 50:01:43:80:02:A4:23:FF
74 00-21-5A-9C-24-00 00-21-5A-9C-27-FF 50:01:43:80:02:A4:24:00 50:01:43:80:02:A4:27:FF
75 00-21-5A-9C-28-00 00-21-5A-9C-2B-FF 50:01:43:80:02:A4:28:00 50:01:43:80:02:A4:2B:FF
76 00-21-5A-9C-2C-00 00-21-5A-9C-2F-FF 50:01:43:80:02:A4:2C:00 50:01:43:80:02:A4:2F:FF
77 00-21-5A-9C-30-00 00-21-5A-9C-33-FF 50:01:43:80:02:A4:30:00 50:01:43:80:02:A4:33:FF
78 00-21-5A-9C-34-00 00-21-5A-9C-37-FF 50:01:43:80:02:A4:34:00 50:01:43:80:02:A4:37:FF
79 00-21-5A-9C-38-00 00-21-5A-9C-3B-FF 50:01:43:80:02:A4:38:00 50:01:43:80:02:A4:3B:FF
80 00-21-5A-9C-3C-00 00-21-5A-9C-3F-FF 50:01:43:80:02:A4:3C:00 50:01:43:80:02:A4:3F:FF
81 00-21-5A-9C-40-00 00-21-5A-9C-43-FF 50:01:43:80:02:A4:40:00 50:01:43:80:02:A4:43:FF
82 00-21-5A-9C-44-00 00-21-5A-9C-47-FF 50:01:43:80:02:A4:44:00 50:01:43:80:02:A4:47:FF
83 00-21-5A-9C-48-00 00-21-5A-9C-4B-FF 50:01:43:80:02:A4:48:00 50:01:43:80:02:A4:4B:FF
84 00-21-5A-9C-4C-00 00-21-5A-9C-4F-FF 50:01:43:80:02:A4:4C:00 50:01:43:80:02:A4:4F:FF
85 00-21-5A-9C-50-00 00-21-5A-9C-53-FF 50:01:43:80:02:A4:50:00 50:01:43:80:02:A4:53:FF
86 00-21-5A-9C-54-00 00-21-5A-9C-57-FF 50:01:43:80:02:A4:54:00 50:01:43:80:02:A4:57:FF
87 00-21-5A-9C-58-00 00-21-5A-9C-5B-FF 50:01:43:80:02:A4:58:00 50:01:43:80:02:A4:5B:FF
88 00-21-5A-9C-5C-00 00-21-5A-9C-5F-FF 50:01:43:80:02:A4:5C:00 50:01:43:80:02:A4:5F:FF
89 00-21-5A-9C-60-00 00-21-5A-9C-63-FF 50:01:43:80:02:A4:60:00 50:01:43:80:02:A4:63:FF
90 00-21-5A-9C-64-00 00-21-5A-9C-67-FF 50:01:43:80:02:A4:64:00 50:01:43:80:02:A4:67:FF
91 00-21-5A-9C-68-00 00-21-5A-9C-6B-FF 50:01:43:80:02:A4:68:00 50:01:43:80:02:A4:6B:FF
92 00-21-5A-9C-6C-00 00-21-5A-9C-6F-FF 50:01:43:80:02:A4:6C:00 50:01:43:80:02:A4:6F:FF
93 00-21-5A-9C-70-00 00-21-5A-9C-73-FF 50:01:43:80:02:A4:70:00 50:01:43:80:02:A4:73:FF
94 00-21-5A-9C-74-00 00-21-5A-9C-77-FF 50:01:43:80:02:A4:74:00 50:01:43:80:02:A4:77:FF
95 00-21-5A-9C-78-00 00-21-5A-9C-7B-FF 50:01:43:80:02:A4:78:00 50:01:43:80:02:A4:7B:FF
96 00-21-5A-9C-7C-00 00-21-5A-9C-7F-FF 50:01:43:80:02:A4:7C:00 50:01:43:80:02:A4:7F:FF
97 00-21-5A-9C-80-00 00-21-5A-9C-83-FF 50:01:43:80:02:A4:80:00 50:01:43:80:02:A4:83:FF
98 00-21-5A-9C-84-00 00-21-5A-9C-87-FF 50:01:43:80:02:A4:84:00 50:01:43:80:02:A4:87:FF
99 00-21-5A-9C-88-00 00-21-5A-9C-8B-FF 50:01:43:80:02:A4:88:00 50:01:43:80:02:A4:8B:FF
100 00-21-5A-9C-8C-00 00-21-5A-9C-8F-FF 50:01:43:80:02:A4:8C:00 50:01:43:80:02:A4:8F:FF
180 VCEM subranges

VCEM MAC WWN
Subrange
Start End Start End
101 00-21-5A-9C-90-00 00-21-5A-9C-93-FF 50:01:43:80:02:A4:90:00 50:01:43:80:02:A4:93:FF
102 00-21-5A-9C-94-00 00-21-5A-9C-97-FF 50:01:43:80:02:A4:94:00 50:01:43:80:02:A4:97:FF
103 00-21-5A-9C-98-00 00-21-5A-9C-9B-FF 50:01:43:80:02:A4:98:00 50:01:43:80:02:A4:9B:FF
104 00-21-5A-9C-9C-00 00-21-5A-9C-9F-FF 50:01:43:80:02:A4:9C:00 50:01:43:80:02:A4:9F:FF
105 00-21-5A-9C-A0-00 00-21-5A-9C-A3-FF 50:01:43:80:02:A4:A0:00 50:01:43:80:02:A4:A3:FF
106 00-21-5A-9C-A4-00 00-21-5A-9C-A7-FF 50:01:43:80:02:A4:A4:00 50:01:43:80:02:A4:A7:FF
107 00-21-5A-9C-A8-00 00-21-5A-9C-AB-FF 50:01:43:80:02:A4:A8:00 50:01:43:80:02:A4:AB:FF
108 00-21-5A-9C-AC-00 00-21-5A-9C-AF-FF 50:01:43:80:02:A4:AC:00 50:01:43:80:02:A4:AF:FF
109 00-21-5A-9C-B0-00 00-21-5A-9C-B3-FF 50:01:43:80:02:A4:B0:00 50:01:43:80:02:A4:B3:FF
110 00-21-5A-9C-B4-00 00-21-5A-9C-B7-FF 50:01:43:80:02:A4:B4:00 50:01:43:80:02:A4:B7:FF
111 00-21-5A-9C-B8-00 00-21-5A-9C-BB-FF 50:01:43:80:02:A4:B8:00 50:01:43:80:02:A4:BB:FF
112 00-21-5A-9C-BC-00 00-21-5A-9C-BF-FF 50:01:43:80:02:A4:BC:00 50:01:43:80:02:A4:BF:FF
113 00-21-5A-9C-C0-00 00-21-5A-9C-C3-FF 50:01:43:80:02:A4:C0:00 50:01:43:80:02:A4:C3:FF
114 00-21-5A-9C-C4-00 00-21-5A-9C-C7-FF 50:01:43:80:02:A4:C4:00 50:01:43:80:02:A4:C7:FF
115 00-21-5A-9C-C8-00 00-21-5A-9C-CB-FF 50:01:43:80:02:A4:C8:00 50:01:43:80:02:A4:CB:FF
116 00-21-5A-9C-CC-00 00-21-5A-9C-CF-FF 50:01:43:80:02:A4:CC:00 50:01:43:80:02:A4:CF:FF
117 00-21-5A-9C-D0-00 00-21-5A-9C-D3-FF 50:01:43:80:02:A4:D0:00 50:01:43:80:02:A4:D3:FF
118 00-21-5A-9C-D4-00 00-21-5A-9C-D7-FF 50:01:43:80:02:A4:D4:00 50:01:43:80:02:A4:D7:FF
119 00-21-5A-9C-D8-00 00-21-5A-9C-DB-FF 50:01:43:80:02:A4:D8:00 50:01:43:80:02:A4:DB:FF
120 00-21-5A-9C-DC-00 00-21-5A-9C-DF-FF 50:01:43:80:02:A4:DC:00 50:01:43:80:02:A4:DF:FF
121 00-21-5A-9C-E0-00 00-21-5A-9C-E3-FF 50:01:43:80:02:A4:E0:00 50:01:43:80:02:A4:E3:FF
122 00-21-5A-9C-E4-00 00-21-5A-9C-E7-FF 50:01:43:80:02:A4:E4:00 50:01:43:80:02:A4:E7:FF
123 00-21-5A-9C-E8-00 00-21-5A-9C-EB-FF 50:01:43:80:02:A4:E8:00 50:01:43:80:02:A4:EB:FF
124 00-21-5A-9C-EC-00 00-21-5A-9C-EF-FF 50:01:43:80:02:A4:EC:00 50:01:43:80:02:A4:EF:FF
125 00-21-5A-9C-F0-00 00-21-5A-9C-F3-FF 50:01:43:80:02:A4:F0:00 50:01:43:80:02:A4:F3:FF
126 00-21-5A-9C-F4-00 00-21-5A-9C-F7-FF 50:01:43:80:02:A4:F4:00 50:01:43:80:02:A4:F7:FF
127 00-21-5A-9C-F8-00 00-21-5A-9C-FB-FF 50:01:43:80:02:A4:F8:00 50:01:43:80:02:A4:FB:FF
128 00-21-5A-9C-FC-00 00-21-5A-9C-FF-FF 50:01:43:80:02:A4:FC:00 50:01:43:80:02:A4:FF:FF
181
Glossary
AKA Activation key agreement
bays 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.
central A system in the management domain that executes the Systems Insight Manager software. All
management central operations within HP Insight Control are initiated from this system.
server
collections The method for grouping system or event searches.
container A rack or an enclosure is considered a container.
critical status A state generated when HP Insight Control can no longer communicate to a managed system.
Desktop An industry standard protocol, primarily used in client management, established by the DMTF.
Management DMI provides an efficient means of reporting client system problems. DMI-compliant computers
Interface can 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 HP
management applications, discovery finds and identifies all the HP systems within a specified
network range.
Domain Name A service that translates domain names into IP addresses.
Service
domains A VC Domain can include between one and four HP c-Class BladeSystem 7000 enclosures or
one HP c-Class BladeSystem 3000 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 the
CPU or server power supplies.
event Information sent to certain users that something in the managed environment has changed. Events
are generated from SNMP traps and are preconfigured in this release. HP Insight Control receives
a trap when an important event occurs. Events are defined as:
• Informational.
Events of this type require no attention and are provided as useful information.
• 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 more serious 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 within
external Address in use by server profiles in a VC Domain that was released back to VCM control and
are no longer managed by VCEM.
external manager A Virtual Connect user account created and exclusively used by Virtual Connect Enterprise
or external Manager.
manager lock
external port The Ethernet connectors on the faceplate of the VC-Enet module.
182 Glossary
firmware upgrade Upgrading VC firmware to a later version.
free Address available for VCEM allocation.
full configuration A user who is automatically authorized for the All Tools toolbox on all systems, including the
rights user CMS. This type of user has been given special privileges to administer the HP Insight Control
software.
hardware status The operating state of SNMP-based systems. A hardware status is determined by polling SNMP
information from the system. Status is defined as:
• Critical.
HP Insight Control can no longer communicate with the system. The system was previously
discovered, but cannot be pinged. The system might be down, powered off, 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 Insight Control cannot obtain management information about the system.
• Disabled
HP Insight Control is disabled.
HBA Host bus adapter

HP Systems Insight The database that stores vital information about HP Insight Control, including users, systems, and
Manager database 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 Specifies the format of datagrams (packets) and the addressing scheme on a network. Most
networks combine IP with Transmission Control Protocol (TCP), which establishes a virtual
connection between a destination and a source.
LUN Logical unit number
MAC Media Access Control
maintenance mode VC Domain is unlocked for domain, network, and storage changes through Under maintenance
in Virtual Connect Manager. VCEM operations related to this VC domain or to VC Domain Group,
such as create server profile, move server profile, server profile failover, and so on, are blocked
while the VC Domain is under maintenance.
Major status Aggregate status information collected from the system that indicates one or more of the monitored
subsystems are not operating properly which is impacting the system. Action should be taken
immediately.
Minor status Aggregate status information collected from the system that indicates one or more of the monitored
subsystems are not operating properly which is impacting the system. Action should be taken as
soon as possible to prevent further failure.
MSCS Microsoft Cluster Server cluster
Onboard The Onboard Administrator is the central point for controlling an entire c-Class rack. It offers
Administrator configuration, power, and administrative control over the rack, and its associated blades (Compute
Servers), blade management processors (iLOs), network switches (depending on the models of
switches used) and storage components (such as SAN or SATA). The Onboard Administrator is
a single management processor, with shared resources to an optional backup twin processor for
failover.
183
profiles Virtual Connect server profile is a logical grouping of attributes related to server connectivity that
can be assigned to a server blade.
racks A set of components cabled together to communicate between themselves. A rack is a container
for an enclosure.
RADIUS Remote Authentication Dial-In User Service. An authentication and accounting system used by
many ISPs. When you dial in to the ISP you must enter your username and password. This
information is passed to a RADIUS server, which checks that the information is correct, and then
authorizes access to the ISP system.
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 or
tower servers.
shared uplink port An Ethernet uplink port that carries the traffic for multiple Virtual Connect networks. Each associated
Virtual Connect network is mapped to a specific Virtual Local Area Network (VLAN) on the
external connection, and appropriate VLAN tags are removed or added as Ethernet packets enter
or leave the VC Domain.
shared uplink port A set of Ethernet uplinks that are used together to provide improved throughput and availability
set to a group of associated Virtual Connect networks. Each associated Virtual Connect network is
mapped to a specific VLAN on the external connection and appropriate VLAN tags are removed
or added as Ethernet packets enter or leave the VC Domain.
Simple Network One of the management protocols supported by HP Insight Control. Traditional management
Management protocol used extensively by networking systems and most servers. MIB-2 is the standard
Protocol information available consistently across all vendors.
slice Two virtual connect modules placed in horizontally adjacent interconnected bays.
Smart Link A feature that, when enabled, configures a Virtual Connect network so that if all external uplinks
lose link to external switches, Virtual Connect will drop the Ethernet link on all local server blade
Ethernet ports connected to that network.
SSL Secure Sockets Layer
stacking port A VC-Enet module external port used to connect to other VC-Enet modules within an active VC
Domain. 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. To manage a system, some type of
management protocol (for example, SNMP, DMI, or WBEM) must be present on the system.
Examples of systems include servers, workstations, desktops, portables, routers, switches, hubs,
and gateways.
TACACS+ Terminal access controller access-control system. Allows a remote access server to communicate
with an authentication server in order to determine if the user has access to the network.
uncleared event Events that have a Critical, Major, Minor, Normal, or Informational severity.
status • 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
184 Glossary
unknown status HP Insight Control cannot obtain management information about the system using SNMP or DMI.
Although no management instrumentation information is available, the system can 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 external
networking 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 uplink
ports is lit green.
uplink port set A set of uplinks that are used together to provide improved throughput and availability for a
single 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 Insight Control.
VC Virtual connect. A logical connection or path through a network.
VC Domain Group A Virtual Connect domain configuration (including network definition, storage definition, MAC
configuration address setting, and WWN address setting) applied to all the Virtual Connect modules in one
VC Domain group. It requires these Virtual Connect modules managed by the VC Domain Group
to have identical hardware configuration.
VC Domain Groups Logical collection of VC domains with the same network and storage configuration.
VC firmware The ability for versions of VC firmware to behave functionally like some number of earlier firmware
compatibility mode versions. This allows domains running newer versions of VC firmware to belong to VC Domain
Groups where some domains are running older versions of firmware. The VC firmware for domains
in a group can be upgraded incrementally.
Version Control An agent that is installed on a server to enable you to see the HP software installed on that server.
Agent The VCA can be configured to point to a VCRM agent, enabling easy version comparison and
software update from the repository.
Virtual Connect VCEM simplifies the management of multiple HP BladeSystem enclosures that use Virtual Connect
Enterprise to control LAN and Storage Area Network (SAN) connectivity, helping organizations increase
Manager (VCEM) productivity, respond more quickly to business demands, and significantly reduce operating costs.
Virtual Connect The firmware embedded software provided with each Virtual Connect module.
Manager (VCM)
Virtual Connect A logical grouping of attributes related to server connectivity that can be assigned to a server
server profile blade. A server profile can be assigned to any server blade within the VC Domain.
VLAN Virtual local area network
WWN World wide name
185
Index
A H
adding a VC Domain to a VC Domain Group, 50 HP Virtual Connect Enterprise Manager
adding custom MAC address ranges, 130 key features and benefits, 9
adding custom WWN address range, 138 product introduction, 9
adding or removing VC modules to VC Domain Group upgrading VC firmware after VCEM is managing VC
configuration, 91 Domains, 142
assigning a profile, 113
assigning a server profile, 112 J
assigning a server profile to a bay, 126 Job status message window, 140
jobs
B deleting jobs, 141
bays Job status message window, 140
assigning a server profile to a bay, 126 reviewing job details, 141
powering down a bay, 124
unassigning a server profile from a bay, 126 L
benefits licensing an enclosure for VCEM, 42
key, 9 logical serial numbers
identifying logical serial number values, 139
C
canceling a VC Domain Group maintenance task, 84 M
cancelling a VC Domain Maintenance task, 71 MAC address
Command Line Interface usage in VCEM, 146 adding custom MAC address ranges, 130
configuring multiple networks, 105 creating MAC exclusion ranges, 129
configuring network port speed, 106 deleting MAC exclusion ranges, 129
configuring the target boot LUN, 104 editing custom MAC address ranges, 130
copying and assigning a server profile to a bay, 113 reclaiming external MAC addresses, 130
correlating VCEM operations in Systems Insight Manager removing custom MAC address ranges, 130
and VC logs, 92 tracking individual MAC addresses, 128
creating a server profile, 98 maintaining a VC Domain from the VC Domain Groups
creating a VC Domain Group, 43, 81 page, 83
creating MAC exclusion ranges, 129 moving a server profile, 114
creating WWN exclusion ranges, 132 moving Ethernet networks (VLANs tagged) from one shared
uplink to another, 91
D
deleting a server profile, 106 P
deleting a VC Domain Group, 85 performing a VC Server Profile Failover, 119
deleting custom WWN address ranges, 138 powering down a bay, 124
deleting jobs, 141 profile
deleting MAC exclusion ranges, 129 moving to another VC Domain Group, 114
deleting WWN exclusion ranges, 137
document R
related documentation, 175 reclaiming external MAC addresses, 130
documentation reclaiming external WWN addresses, 137
VCEM website, 175 related documentation, 175
removing a VC Domain from a VC Domain Group, 52
E removing custom MAC address ranges, 130
editing a server profile, 107 requirements for adding a VC Domain to a VC Domain
editing custom MAC address ranges, 130 Group, 30
editing custom WWN address ranges, 138 reviewing job details, 141
external manager account, 144
S
F server profiles
features assigning a server profile, 112
key, 9 configuring multiple networks, 105
configuring network port speed, 106
186 Index
configuring the target boot LUN, 104 unable to add an unconfigured VC Domain to a VC
copying and assigning a server profile to a bay, 113 Domain Group, 160
creating a server profile, 98 unable to add VC Domain to a VC Domain Group, 159
deleting a server profile, 106 unauthorized error when trying to access the VCEM
editing a server profile, 107 home page, 158
moving a server profile, 114 VC Domain displays Configuration Mismatch status,
performing a VC server Profile Failover, 119 161
unassigning a server profile, 113 VC Domain displays Connectivity failure status, 161
verifying the presence of EFI partition data, 112 VC Domain displays Expired License status, 164
VC Domain displays Missing External Manager lock
T status, 160
tracking individual MAC addresses, 128 VC Domain not discovered by Systems Insight Manager,
tracking individual WWN addresses, 131 171
troubleshooting VC Domain status is "Mismatch Configuration" after
After a server profile failover, some connections defined cancel VC Domain Maintenance operation fails, 170
in the server profile are not functional, 171 VC Profile Failover fails during Onboard Administrator
after VC Domain is removed from VC Domain Group replacement, 169
in VCEM, profile with external-managed status cannot VCEM database is inaccessible or irretrievable with no
be edited through VCM, 169 backup, or VCEM file systems are corrupt with no
backing up and restoring VCEM, 166 backup, 166
cannot change the MAC/WWN/Serial Number ranges VCEM is prompting for Onboard Administrator
in VCM when there are server profiles, 166 credentials on a configured VC Domain, 159
cannot manage a VC Domain when VC module failover VCEM page displays "Communication with the Systems
is taking place, 160 Insight Manager server has been lost", 171
cannot resynchronize VC Domain that is in VCM does not accept Onboard Administrator
Configuration Mismatch state, 162 credentials, 159
Create VC Domain Group or Add VC Domain to VC
Domain Group operations fail and the message "An U
invalid boot LUN was entered. Check the storage unassigning a server profile from a bay, 126
arrays for the proper LUN number" appears, 172 updating VC firmware, 22
creating a server profile or adding a VC Domain to a upgrading VC Domain Group firmware mode, 84
VC Domain Group fails, 165 upgrading VC firmware after VCEM is managing VC
enclosure has a hardware failure and must be replaced, Domains, 142
167 performing firmware update using the VC Domain
enclosure has two Onboard Administrators, and one Maintenance capability, 143
fails, 158 preparation checklist, 142
error on database operation occurs, 164
errors or hangs occur while loading VCEM pages, 164 V
failed to execute VCEM operation because VC firmware VC Domain Group
not supported, 165 canceling a VC Domain Group maintenance task, 84
failover fails to initiate with an ERROR (30) - Could not creating a VC Domain Group, 81
initiate failover; nested exception is: deleting a VC Domain Group, 85
java.net.SocketTimeoutException: Read timed out, 169 maintaining a VC Domain from the VC Domain Groups
job appears with Failed status, 158 page, 83
operation fails to perform in the VC Domain or VC upgrading VC Domain Group firmware mode, 84
Domain Group under maintenance status, 163 VC Domain Groups
profile move, assign, or failover operations fail and the adding or removing VC modules to VC Domain Group
message "An invalid boot LUN was entered. Check configuration, 91
the Storage arrays for the proper LUN number" correlating VCEM operations in Systems Insight
appears, 172 Manager and VC logs, 92
Remove from VC Domain Group job is successful but moving Ethernet networks (VLANs tagged) from one
with errors, 163 shared uplink to another, 91
removing VCEM, 165 VC Domain in VC Domain Maintenance, 56
Replace VC modules in a VC Domain managed by VC Domain tasks, 42
VCEM, 168 VC Domains
server profile edit operation fails when target server is adding a VC Domain to a VC Domain Group, 50
powered on, 169 cancelling a VC Domain Maintenance task, 71
Systems Insight Manager customizations for VCEM have creating a VC Domain Group, 43
not taken place, 171 licensing an enclosure for VCEM, 42
187
multienclosure, 53
removing a VC Domain from a VC Domain Group, 52
requirements for adding a VC Domain to a VC Domain
Group, 30
VC Domain in VC Domain Maintenance, 56
VC Domain tasks, 42
VC firmware
updating, 22
VC Profile Failover
CLI exit and error codes, 148
list details for specified VCEM job, 147
show CLI usage online help, 148
VC Server Profile Failover
performing VC Server profile failover on specified VC
Domain bay server, 146
verifying the presence of EFI partition data, 112
W
websites
product manuals, 175
WWN address
adding custom WWN address ranges, 138
creating WWN exclusion ranges, 132
deleting custom WWN address ranges, 138
deleting WWN exclusion ranges, 137
editing custom WWN address ranges, 138
reclaiming external WWN addresses, 137
tracking individual WWN addresses, 131
188 Index

HP Virtual Connect Enterprise Manager 7.5 User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP Virtual Connect Enterprise Manager 7.5 User Guide

Uploaded by

Copyright:

Available Formats

HP Virtual Connect Enterprise Manager 7.

HP Part Number: 778004-004

UNIX® is a registered trademark of The Open Group.

Key features and benefits

Key features and benefits 9

VCEM software licenses 459864-B21 HP VCEM BL-c7000 Single enclosure

459865-B21 HP VCEM BLc7000 Single flexible

459866-B21 HP VCEM BLc7000 Tracking license –

T9094AAE HP VCEM BLc7000 E-LTU—

459867-B21 HP VCEM BLc3000 Single enclosure

459868-B21 HP VCEM BLc3000 Single flexible

459869-B21 HP VCEM BLc3000 Tracking

T9095AAE HP VCEM BLc3000 Encl E-LTU single

605865-B21 HP Virtual Connect FlexFabric 10/24

662048–B21 HP Virtual Connect Flex-10/10D

For more information, see “VCEM licensing” (page 42).

HP Virtual Connect technology

Figure 1 Traditional network and Virtual Connect comparison

Managing HP Virtual Connect

HP Virtual Connect Manager

HP Virtual Connect Enterprise Manager

Understanding VCEM operations

Managing HP Virtual Connect 13

Figure 2 Virtual Connect Enterprise Manager home page

Figure 3 VCEM architecture overview

Figure 4 VC server profile movement example

Understanding VCEM operations 15

Understanding VCEM and VC firmware version compatibility

6.3 2.1x, 2.3x, 3.0x, 3.10, 3.15, 3.17, and 3.18

7.1 3.15, 3.17, 3.18, 3.3x, 3.5x, and 3.6x

7.1.1 3.3x, 3.5x, 3.6x, and 3.7x

7.2 3.3x, 3.5x, 3.6x, 3.7x, and 4.0x

7.2.2 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, and 4.1x

7.3 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, and 4.1x

7.3.2 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.10, 4.2x

7.4 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.10, 4.2x, 4.3x

16 Installing and configuring VCEM

7.3.2 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x, 4.4x

7.4 3.3x, 3.5x, 3.6x, 3.7x, 4.0x, 4.1x, 4.4x

Understanding VCEM and VC firmware version compatibility 17

GroupOne 3.18 3.30 3.30 3.60 3.15

GroupTwo 3.30 3.5x 3.60 3.7x 3.3x

GroupThree 3.60 3.7x 4.0x 4.1x 3.5x

GroupX 4.0x 4.1x 4.2x 4.3x 4.0x

6.3 3.3x, 3.5x, 3.6x 3.15

6.3u1 3.5x, 3.6x, 3.7x 3.3x

18 Installing and configuring VCEM

7.0 3.5x, 3.6x, 3.7x 3.3x

7.1 3.7x 3.5x

7.1.1 4.0x 3.7x

7.2 and 7.2.2 4.1x, 4.2x 4.0x

7.3 4.3x 4.2x

7.3.2 4.3x 4.2x

7.4 4.4x 4.3x

7.4.1 and 7.5 Will be determined based on the 4.4x

Creating a VC Domain Group based on a VC Domain running a newer version of VC firmware

Preparing for a VCEM installation

Figure 6 Update path

Preparing for a VCEM installation 19

3.30 7.x and 8.x 3.x NA

3.5x 8.x and 9.x 6.x and 7.x NA

3.60 8.x and 9.x 9 and 10ESR NA

3.7x 8.x and 9.x 9, 10ESR and 11 NA