HP Virtual Connect Enterprise Manager 7.5 User Guide
HP Virtual Connect Enterprise Manager 7.5 User Guide
HP Virtual Connect Enterprise Manager 7.5 User Guide
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.
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.
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
• 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.
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
Architectural overview
This section provides an overview of the architecture, functionality, and operations of Virtual
Connect technology and VCEM.
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.
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.
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.
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.
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.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.
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.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.
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 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
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.
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.
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
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.
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
Installation prerequisites 21
Table 8 VCEM ports (continued)
CMS Managed System Port Protocol1 Description
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.
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.
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.
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).
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.
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”.
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.
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).
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.
NOTE: Executing mxsync –e will help resolve VC Domain synchronization issues across multiple
VC domains.
29
Table 10 VCEM status icons (continued)
Status Icon Description
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.
30 Managing VC Domains
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.
◦ 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
◦ VLAN Capacity
– Legacy VLAN capacity or Expanded VLAN capacity
◦ Fibre Channel SNMP settings: Read Community, System Contact, and IP addresses
• Network and Fibre Channel SAN Fabrics uplinks
32 Managing VC Domains
• For each single network uplink:
◦ Network name
◦ Smart link
◦ Private Network
◦ State
◦ Speed/duplex mode
◦ Connection mode
◦ Speed/duplex mode
◦ Connection mode
◦ Network state
◦ VLAN ID
◦ Native
◦ Smart Link
◦ Private network
◦ 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
• 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.
34 Managing VC Domains
VC 4.3x features that must be disabled in a VC Domain to be part of a VC Domain
Group with VC firmware 4.2x
• UEFI Boot order is not supported. Do not configure profiles with UEFI boot order checked on
VC Domain.
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.
Requirements for adding a VC Domain to a VC Domain Group 35
VC 4.1x features that must be disabled in a VC Domain to be part of a VC Domain
Group with VC firmware 4.0x
• The Hide Unused FlexNICs check box is not supported. Do not configure server profiles with
the Hide Unused FlexNICs option checked. (See Figure 14).
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).
To disable this feature, delete all the items in the SNMP access and trap destinations tables
that are configured to use IPv6 addresses.
36 Managing VC Domains
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)
◦ Short (1 second)
38 Managing VC Domains
Figure 20 Server profile configured with IGMP Multicast Filter Set or 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) .
To disable this feature, click Select Factory Default Role Operations and the default permissions
are restored.
40 Managing VC Domains
Figure 25 SAN fabrics with direct attach fabric type
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.
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:
42 Managing VC Domains
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.
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:
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.
44 Managing VC Domains
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.
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.
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.
46 Managing VC Domains
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.
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.
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
48 Managing VC Domains
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
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
50 Managing VC Domains
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.
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.
• 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
5. 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.
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
VC Domain configurations match the VC Domain Group configuration. VC Domains that are
already configured and have server profiles are not affected.
7. Select the VC Domain Group name to which you want to add the selected VC Domains.
8. Click OK. The Virtual Connect Enterprise Manager is executing the request
message appears.
9. Click OK to go to the Jobs page and monitor job progress.
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.
52 Managing VC Domains
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.
5. Click OK to go to the Jobs page and monitor job progress.
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.
54 Managing VC Domains
Figure 31 VC Domain Group with VC Domains that have different numbers of enclosures
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.
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.
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+
56 Managing VC Domains
• Changing VC Domain configuration
◦ Domain name
◦ Static IP address
• Setting SSH
• Setting SSL Certificate
• Ethernet Settings:
◦ MAC Cache failover
◦ IGMP Snooping
◦ Import
◦ Delete
• Storage Management Credentials
• SNMP Configuration
• Network Access Groups
• 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:
IMPORTANT: VCEM has detected you may be using other products, such as
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.
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 full-height and half-height single density servers (for example, BL460c,
BL480c)
◦ Login Banner Configuration
◦ LACP timer
58 Managing VC Domains
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
• Network Access Groups
◦ Name(s) and networks
• Ethernet settings
◦ MAC Cache Failover:
– Enable Fast MAC Cache Failover
– MAC Refresh Interval
VC Domain Maintenance 59
◦ Network Loop Protection
◦ VLAN Capacity
– Expanded VLAN capacity
◦ State
◦ Connection mode
◦ Smart link
◦ Private network
◦ States
◦ Speed/duplex mode
◦ Connection mode
◦ Colors
◦ Labels
• For each shared network:
◦ Uplink Set Name
◦ State
60 Managing VC Domains
◦ Smart Link
◦ External VLAN ID
◦ Native VLAN
◦ Colors
◦ Labels
• For each uplink set name:
◦ Connection Mode
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.
VC Domain Maintenance 61
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.
7. Click OK to go to the Jobs page and monitor job progress.
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.
62 Managing VC Domains
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.
3. Click VC Domain Maintenance. The VC Domain Maintenance page appears.
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
Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network,
and storage changes.
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.
8. Click OK to go to the Jobs page and monitor job progress.
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.
VC Domain Maintenance 63
Figure 33 VC Domain details
Figure 34 Custom speed value display for associated Ethernet, iSCSI, FCoE networks combined with
the HP VC FlexFabric-20/40 F8 module
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
64 Managing VC Domains
Figure 35 VC Domain QoS passthrough information
VC Domain Maintenance 65
Figure 38 QoS custom without FCoE lossless (DOT1P mapping) configuration type
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.
NOTE: the Multicast Filters tab is only displayed in VC Domain versions 4.0x or later.
66 Managing VC Domains
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.
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.
VC Domain Maintenance 67
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
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 44 VC Domain details for Converged Uplink sets and FCoE networks
68 Managing VC Domains
(30 seconds). VCEM displays that information in the VC Domain network details. Figure 45 displays
VC Domain network details with the LACP timer attribute.
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.
VC Domain Maintenance 69
Figure 47 Displaying Ethernet SNMP access for IPv6
70 Managing VC Domains
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.
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 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.)
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.
72 Managing VC Domains
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).
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.
74 Managing VC Domains
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.
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.
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.
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.
76 Managing VC Domains
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.
3. Click Remove from VC Domain Group. Wait for the job to complete successfully.
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.
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
78 Managing VC Domains
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.
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
modules) in the second filter.
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.
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.
Table 15 (page 81) describes VC Domain Group icons and status on the page.
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
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.
5. Enter the user name and password for the Onboard Administrator of each unconfigured VC
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
VC Domain configurations match the VC Domain Group configuration. VC Domains that are
already configured and have server profiles are not affected.
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.
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.
4. 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 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.
8. Click OK to go to the Jobs page and monitor job progress.
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.
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.
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
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.
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 59 VC Domain Group details for Converged Uplink sets and FCoE networks
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).
The following table lists the columns in the managing server profile table.
Item Description
93
Item Description
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
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
Table 16 VCEM supported VC features (continued)
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
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
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.
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.
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.
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.
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
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.
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.
Port 2 (required if an alternate target IP address is TCP port associated with the alternate IP address. The
specified) default value is 3260
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 (‘ ‘ , ‘-‘, ‘.’,
‘:’, ‘,’ ).
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.
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.
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."
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.
14. Click OK. The Virtual Connect Enterprise Manager is executing the request
message appears.
15. Click OK to go to the Jobs page and monitor job progress.
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.
Figure 69 displays the operating system device listings after enabling the Hide Unused FlexNICs
check box.
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.
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.
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.
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.
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
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.
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.
4. Click OK. The Virtual Connect Enterprise Manager is executing the request
message appears.
5. Click OK to go to the Jobs page and monitor job progress.
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: 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.
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.
NOTE: When moving a server profile to another bay in the same or different VC Domain group,
VCEM detects the presence of logical server managers or upper level managers. When performing
this task, the following message appears and explains the impact of performing that 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. 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.
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:
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.
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.
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
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.
◦ 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
◦ 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.
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.
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”.
VCEM detects the presence of logical server managers or upper level managers. When performing
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:
IMPORTANT: VCEM has detected you may be using other products, such as
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.
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.
Item Description
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
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
UID Icon that indicates the Unit Identifier (UID) state: on, off, or
not available
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)
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
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.
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.
Item Description
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.
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.
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.
Item Description
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
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 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.
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.
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
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
for the HP Matrix Operating Environment Federated CMS Overview White Paper.
NOTE: Factory default address information is only available for mapped connections.
Connections which are unmapped will continue to display as Factory-Default.
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.
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.
Item Description
The following table lists describes the job item columns or drop-down menu in the Jobs list.
Item Description
User Name Identifies the user that performed the function and created
the job
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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).
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
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.
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 -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.
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.
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.
To resolve this issue:
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.
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.
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.
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.
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.
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.
NOTE: The option “-quiet” is available to suppress user confirmation prompts. This option is useful
for scripting operations.
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.
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.
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.
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.
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.
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:
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.
7. From the VCEM home page, click the VC Domains tab.
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”.
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.
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.
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:
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.
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.
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.
To resolve this issue:
1. Click the Profiles tab.
2. Select the server profile that is presenting the problem.
3. Click Edit.
4. In the boot target configurations table, change all the target LUN fields to be within the allowed
ranges (either a three-digit decimal between 0–255, or a 16-digit hexadecimal between 0
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 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
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.
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
179
Table 22 MAC and WWN subranges (continued)
VCEM MAC WWN
Subrange
Start End Start End
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.
See also enclosure, racks.
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
your data center. Excluded address ranges are not assigned for use by VCEM.
external Address in use by server profiles in a VC Domain that was released back to 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.
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.
See also enclosure, racks.
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