HP Virtual Connect Enterprise Manager 7.2 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.
© Copyright 2007, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................9 Key features and benefits...........................................................................................................9 Key features........................................................................................................................9 Key benefits................................................................................................................
Replicating VC Domain Group configurations to other VC Domains during VC Domain Maintenance.....................................................................................................................56 Performing VC Domain Maintenance....................................................................................58 Backing up and restoring domain configurations through VC Domain Maintenance....................59 Changes in VCM that might affect completing VC Domain Maintenance..................
Configuring the target boot LUN.............................................................................................104 Configuring multiple networks ...............................................................................................105 Configuring Network Port Speed............................................................................................106 Deleting a server profile........................................................................................................
Adding a custom WWN address range..................................................................................142 Editing a custom WWN address range...................................................................................142 Deleting a custom WWN address range.................................................................................143 8 Working with Logical Serial Numbers.......................................................144 Identifying logical serial number values...............
Operations fail in a VC Domain or VC Domain Group under maintenance status..........................164 Remove from VC Domain Group job is successful but with errors.................................................165 Resolving an expired license status..........................................................................................165 Resolving database operation errors........................................................................................165 Errors occur while loading VCEM pages.
15 Documentation feedback.......................................................................178 A VCEM subranges...................................................................................179 Glossary..................................................................................................183 Index.......................................................................................................
1 Introduction 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.
• Group-based management of Virtual Connect Domains increases infrastructure consistency, simplifies system deployment and enables rapid change management across hundreds of HP BladeSystem enclosures. • Add, change, and failover servers and their workloads across the data center in minutes without impacting production networks. • Increase productivity and server-to-administrator ratios. • Release LAN and SAN administrators from routine server-centric tasks.
Table 1 (page 11) lists all available VCEM licenses, including Virtual Connect hardware and VCEM packaged options.
that LANs and SANs see NIC or HBA addresses presented by the VC modules instead of the default burned-in interface addresses. VC provides several key advantages: • Reduces physical server-to-network cabling, complexity, and leased network ports. • Maintains constant end-to-end connections to preferred networks and fabrics. • Enables administrators to wire LAN and SAN connections once and limit changes.
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.
include a physical stand-alone console, as a plug-in to Systems Insight Manager, and as a virtual server guest. The majority of VCEM operations are accessed through a dedicated homepage which includes the following core tasks: • Discover and import existing VC Domains without system downtime. • Aggregates individual VC address information for LAN and SAN connectivity into a centrally administered VCEM address repository. • Create VC Domain Groups. • Assign and unassign VC Domains to VC Domain Groups.
Figure 3 VCEM architecture overview Using VCEM, system administrators can quickly deploy, replace and recover servers and their associated workloads by simply assigning or reassigning the VC server connection profile to an enclosure bay. The example in Figure 4 (page 16) illustrates a server profile movement operation from “Server A” to “Server C” using VCEM.
Figure 4 VC server profile movement example 16 Introduction
2 Installing and configuring VCEM This chapter describes how to install and configure VCEM. IMPORTANT: This guide assumes that you have previously configured VC using the integrated VCM, have read the HP Virtual Connect for c-Class BladeSystem User Guide, and understand its concepts.
Figure 5 VC Domain compatibility support In each case, the newer versions of VC will behave functionally like the oldest version of firmware running on any VC Domain in the VC Domain Group. No features beyond those that are supported by the oldest version of VC firmware in the VC Domain Group can be enabled on any of the VC Domains in the VC Domain Group even if they are running a newer version of VC firmware.
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 name Domain A Domain B Domain C Domain D Group firmware mode GroupOne 3.18 3.30 3.30 3.60 3.15 GroupTwo 3.30 3.5x 3.60 3.7x 3.3x GroupOne contains three domains running 3.
Figure 6 Update path IMPORTANT: VCEM 7.2 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 28) for more information.
Table 7 VC Domain Group firmware compatibility VC firmware VC Domain Group firmware mode 4.0x VC Domain Group firmware mode 3.7x VC Domain Group VC Domain Group firmware mode 3.5x firmware mode 3.3x 4.0x Yes Yes Yes Yes 3.7x No Yes Yes Yes 3.5x/3.6x No No Yes Yes 3.30 No No No Yes1 1 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.
Table 8 VCEM ports (continued) Port Protocol1 Description Y 514 UDP SYSLOG Y 1812, 1813 UDP RADIUS server if configured Y 49 TCP TACACS server if configured CMS Managed System 1 All ports are used for TCP and UDP. 2 The CMS normally has all managed system ports open, as the CMS is a managed system itself. Firewalls can be configured to block these ports if the CMS is not to be managed from another system.
1. Select the VC Domains that are targeted for firmware updates. NOTE: Using the firmware update workflow requires VCSU 1.8.0 or later and the VC Domains being updated must be running VC 3.50 or later. Otherwise, enable maintenance mode on the VC Domain in preparation for updating the VC firmware with VCSU. Figure 7 VC Domain tab page 2. 3. Select VC Domain Firmware Update... and all the VC Domains selected are displayed. Select Enable Firmware Update... (Figure 8).
Figure 9 Firmware update message 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).
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 in order 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” (page 170). Removing VCEM WARNING! Removing VCEM could have significant implications.
3. Enter the credentials that you entered when performing the installation. The VCEM home page appears. • If an HP SIM discovery of Onboard Administrators has been performed, all VC modules appear. • If an HP SIM discovery has not been previously performed, and no VC modules appear, perform an HP SIM discovery before continuing. 1. Discover the Onboard Administrator IP addresses with enclosures that have VC Ethernet modules. 2. Click VC Domains to verify whether any VC Domains have been discovered.
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. b. c. 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. Click the World Wide Names hyperlink. To create a custom range, click Add custom.
Upgrading incompatible firmware modes and versions If unsupported VC Domain firmware versions are detected at the end of a VCEM 7.2 upgrade, a warning message similar to the following is displayed: VCEM detected unsupported VC firmware. For information on how to upgrade your firmware, run the Insight Software Advisor or refer to the VCEM User Guide troubleshooting section. Upgrade to a supported VC firmware by performing the following steps: 1.
3 Managing VC Domains This chapter describes how to use VCEM to manage VC Domains. On the VC Domains page, you can filter the VC Domain list by VC Domain Group. The default filter shows all VC Domains. Figure 11 VC Domains window Table 9 (page 29) lists the columns on the VC Domains page.
Table 10 VCEM status icons (continued) Status Icon Description Missing external manager lock/Communication established with disabled enclosure VCEM is unable to obtain the necessary permissions for External Manager user. VCEM might have lost the External Manager lock at the VC Domain. Expired license The VC Domain enclosure has an expired license. Managed by VCEM The VC Domain is part of a VC Domain Group and operating normally.
minimum number of enclosures. For more information about multienclosure VC Domains, see “Working with multienclosure VC Domains” (page 51). • 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.
VCEM validates the following components when adding a VC Domain to a VC Domain group, therefore the VC Domain configuration must be identical to the VC Domain Group configuration.
• For each single network uplink: ◦ Network name ◦ Smart link ◦ Private Network ◦ Enable VLAN Tunneling ◦ State ◦ Network port location ◦ Speed/duplex mode ◦ Connection mode ◦ Preferred Link Connection ◦ Preferred Link Connection Speed ◦ Maximum Link Connection ◦ Maximum Link Connection Speed ◦ Network Access Groups (associated with this network) • Number of networks configured in the VC Domain • For each shared network uplink: ◦ Uplink set name ◦ Network port location ◦
• • ◦ Maximum Link Connection Speed ◦ Network Access Groups (associated with this network) For each Fibre Channel SAN Fabric: ◦ Fabric name ◦ Fabric port location ◦ Configuration speed Number of Fibre Channel SAN Fabrics configured in the VC Domain To add an unconfigured VC Module to a VC Domain Group, the following items must be identical: • Interconnect bays location and model • Enclosure model • Uplinks of the network and Fibre Channel SAN Fabric • Power state of the VC Modules VC 4
For network (see Figure 14) and Uplink Set (see Figure 15) there are three possible values: ◦ Domain-Default which is either Short (1 second) or Long (30 second) ◦ Short (1 second) ◦ Long (30 second) When the LACP timer configuration is set to long in VC Domains, all Uplink Sets and networks with a default are automatically using Long (30 sec).
Figure 15 Uplink Set LACP timer configuration To disable this feature: 1. Change the VC Domain LACP timers from Long (30 sec) to Short (1 sec). 2. Change each network and uplink set configuration from Long (30 sec) to Domain Default,Short (1 sec) or Short (1 sec) • IGMP Multicast Filter Sets or Multicast filters Do not configure IGMP Multicast Filter Sets or Multicast filters in VC Domains.
Figure 18 VC Domain configured with IGMP Multicast filter To disable this feature, it is necessary to first remove the Multicast Filter Sets and then remove the Multicast filters. 1. Remove the association between server profile Ethernet connections and Multicast Filter Sets or Multicast filters by selecting None in the Multicast Filter column (see Figure 16) . 2. Remove the Multicast Filter Sets and then remove the Multicast filters (see Figure 17, and Figure 18).
Figure 20 VC domain with customized role operations To disable this feature, click Select Factory Default Role Operations and the default permissions are restored. VC 3.7x features that must be disabled in a VC Domain to be part of a VC Domain Group with VC firmware 3.5x and 3.6x The following features are not supported: • Direct Attach storage is not supported. Figure 21 SAN fabrics with direct attach fabric type To disable this feature delete all direct attach SAN fabrics.
Figure 22 SNMP access configuration VC 3.7x, 3.6x and 3.5x features that must be disabled in a VC Domain to be part of a VC Domain Group with VC firmware 3.3x All VC 3.5x, 3.6x, and 3.7x features must be disabled for VC Domain Groups with firmware mode 3.3x in order to add 3.7x back into the 3.3x VC Domain Group. VC 3.5x feature that must be disabled in a VC Domain to be part of a VC Domain Group with VC firmware 3.3x Extra FC or FCoE connections are not supported.
Figure 23 Removing FC and FCoE connections in 3.5x To disable this feature, delete the additional FC SAN connections or FCoE connections (that exceeds the 4 redundant connections to each Virtual Connect Fibre Channel/Virtual Connect FlexFabric Module) from the server profile. VC Domain tasks From the VC Domains page, you can perform the following tasks: • License an enclosure. • Create a VC Domain Group. • Add a VC Domain to a VC Domain Group. • Remove a VC Domain from a VC Domain Group.
5. Click OK to validate the key string. NOTE: License key fields are case-sensitive If the key string is valid, the key is added to HP Insight Management. 6. • Click Next to provide VC Domain credentials. For existing VC Domain Groups: 1. Select the VC Domain from the VC Domains page, and then click License. The License Enclosure page appears. 2. 3. Click Add Key. Enter the license key string, and then click OK. If the license key is valid, it is added to Systems Insight Manager.
If you are using an HP VC FlexFabric 10 Gb 24-port module, ensure that the module status is compatible. See “Upgrading incompatible firmware modes and versions” (page 28) for more information. VCEM cannot manage a VC Domain that has one or more FC modules with an Incompatible status. The FC module can become incompatible in the following situations: • An HP Virtual Connect 4 Gb FC module replaces an HP Virtual Connect 8 Gb 24-port FC module.
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.
Table 12 Role-based privileges Privileges Type Description VCEM User (read-only) CMS Provides read-only access to VCEM pages. VCEM Group Limited Operator Group Enables you to perform some of the tasks of the VC Domain Group Operator role except for creating, editing, or deleting a server profile. VCEM Domain Group Operator Group Allows you to manage server profiles in one or more specified VC Domain Groups. Only server profile operations in the specified VC Domain Group are permitted.
Figure 24 Systems Insight Manager Users and Authorizations page 7. Under Select Toolbox(es) choose the VCEM role you want to use to restrict access ( for example "VCEM Domain Group Administrator"). See Figure 24 for more information.
8. Under Select Systems: a. CMS type roles: If you want these roles to apply to all VCEM pages, then select CMS. b. Group type roles: Select Add, the select the VCEM VC Domain Group for which you want to restrict access (for example "vcdg-1") and click Apply. The selected VCEM VC Domain Group will appear automatically in Select Toolbox(es). See Figure 25 for more information.
Table 13 VCEM operations and RBAC privileges (continued) VCEM operations VCEM or VCEM roles administrator VCEM group administrator VCEM group operator VCEM group limited operator VCEM user (Read-only) List VC Domains x x x x x List VC Domain Groups x x x x x Display profile details x x x x x Display bay details x x x x x Display job details x x x x x Display VC Domain Group details x x x x x Display VC Domain details x x x x x Delete job x N N N N Failove
Table 13 VCEM operations and RBAC privileges (continued) VCEM operations VCEM or VCEM roles administrator VCEM group administrator VCEM group operator VCEM group limited operator VCEM user (Read-only) Delete VC Domain Group x x N N N Upgrade VC Domain Group firmware mode x x N N N Update VC x Domain firmware x N N N License Enclosure x N N N N Adding a VC Domain to a VC Domain Group Select Add to VCD Group to add a VC Domain to a VC Domain Group.
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.).
1. 2. 3. 4. Export the server profiles from the VC Domain to the target VC Domain Group (and leave the server profiles unassigned). The VCEM export operation will match all resources in use by server profile and change the necessary elements to allow the migration to complete. Select Overwrite Configuration to add the VC Domain to the target VC Domain Group. VCEM overwrites the VC Domain with the VC Domain’s configuration.
3. 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.
See “Related information” (page 176) for documents that can have more information on “stacking links.” Figure 26 (page 52) illustrates a valid configuration of Ethernet and Fibre Channel Virtual Connect modules in a VC Domain with multiple enclosures. The black lines linking the Ethernet modules illustrate the stacking links.
Figure 27 VC Domain Group with VC Domains that have different numbers of enclosures A multienclosure domain can only be configured as follows: • The enclosure must be a c7000 enclosure. • Refer to the VC documentation available at: http://www.hp.com/go/vc for details on which Virtual Connect Ethernet modules are supported for primary and secondary roles for the VC firmware revision in your environment. • FC modules in every enclosure must match the model and disposition.
For more information, see the HP Virtual Connect Manager documentation. VC Domain Maintenance VC Domain Maintenance is a useful way to perform updates on a particular VC Domain without removing it from a VC Domain Group, and apply the common domain, network and storage configuration changes automatically to all other VC Domains that belong to the same VC Domain Group. VCEM accomplishes this task by temporarily enabling domain, network, and storage changes through the local VCM for the selected domain.
• Setting SSL Certificate • Ethernet Settings: ◦ MAC Cache failover ◦ IGMP Snooping ◦ Multiple Networks Link Speed Settings ◦ Server VLAN Tagging Support • Shared Uplink Set • Resetting VC module (soft reset) • Monitoring network ports • Configuring networks • Configuring storage • Login Banner Configuration • Enclosures Configuration: ◦ Find ◦ Import ◦ Delete • Storage Management Credentials • SNMP Configuration • Network Access Groups • Link Stability Redistribution
Replicating VC Domain Group configurations to other VC Domains during VC Domain Maintenance IMPORTANT: The VC Domain, network, and storage configuration changes performed during VC Domain Maintenance are automatically replicated to all other VC Domains that belong to the same VC Domain Group when the VC Domain maintenance operation is completed. The configuration changes are rolled back for the domain and not replicated to other domains if the maintenance operation is cancelled instead of completed.
◦ ◦ Multiple Network Speed Settings: – Preferred Link Connection – Preferred Link Connection Speed – Maximum Link Connection – Maximum Link Connection Speed Network SNMP settings: – Enable SNMP – Read Community – System Contact – Each SNMP trap defined community and IP address – SNMP Security Enhancements ◦ Port Throughput statistics ◦ Port throughput statistics configuration information ◦ Network Loop Protection ◦ VLAN Capacity – • • Fibre Channel SAN fabric settings: ◦ Enab
• • ◦ Connection mode ◦ Preferred link connection ◦ Preferred link connection speed ◦ Maximum link connection ◦ Maximum link connection speed ◦ Network Access Groups (associated with this network) ◦ Colors ◦ Labels For each shared network: ◦ Uplink Set Name ◦ State ◦ Smart Link ◦ External VLAN ID ◦ Native VLAN ◦ Number of VLANs tagged associated with the shared network uplinks ◦ Network Access Groups (associated with this network) ◦ Colors ◦ Labels For each uplink set na
NOTE: When a VC Domain has a status of Under maintenance, VCEM does not allow you to perform server profile operations in any VC Domains which belong to that VC Domain Group. This restriction also precludes any operation permissions delegated to the server role as a result of VCM role operation configuration customizations. You can have a maximum of one VC Domain in the VC Domain Group that has a status of Under maintenance. 3. Confirm the VC Domain changes through VCEM.
4. 5. 6. 7. To unlock VCM for domain, network, and storage changes, click Make changes via VC Manager. The VCM web interface appears in a separate browser window. The Under Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network, and storage changes. Using VCM: a. Log in to VCM with the required user rights. b. Perform the domain restoration by selecting Domain Settings→Domain Configuration, and selecting the Backup/Restore tab. c. Click Backup configuration.
Changes in VCM that might cause problems in completing VC Domain Maintenance include: • Updating the VC firmware to an incompatible version, (Domain Settings→Firmware Management). To resolve this issue, update the VC firmware version to a compatible version and complete VC Domain Maintenance again. • Deleting the domain (Domain Settings→Domain Configuration). To resolve this issue, restore the VC configuration from a backup, or remove the VC Domain from the VC Domain Group.
Figure 30 VC Domain QoS passthrough information Figure 31 QoS custom with FCoE lossless configuration type 62 Managing VC Domains
Figure 32 QoS custom without FCoE lossless configuration type VC Domain Maintenance 63
Figure 33 QoS custom without FCoE lossless (DOT1P mapping) configuration type Viewing VC Domain and VC Domain Group roles To view allowed VC Domain role permissions perform the following steps: 1. Select the VC Domain tab from the home page. 2. Click on the target VC Domain.
3. Select the Operation Permissions tab to view VC Domain roles. Figure 34 displays an example. Figure 34 VC Domain operation permissions tab NOTE: Operation permissions are only displayed in VCEM. For more information on VCM customizing role permissions see the HP Virtual Connect for c-Class BladeSystem User Guide at http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html.
Statistical throughput attributes VCEM displays statistical-throughput configuration information in the VC Domain Properties and the VC Domain Group properties windows including: • Add to Group—When a VC Domain is added to a VC Domain Group, the statistics-throughput configuration setting from the VC Domain Group is applied to the VC Domain.
Figure 37 FCoE allocated port speed example You can also view or select a new value for the FCoE connections table preferred port speed on the edit server profile page. Figure 38 displays an example of preferred port speed (default port speed when adding a new connection) in the FCoE connections table. Figure 38 FCoE preferred port speed example Displaying Converged Uplink sets and FCoE networks Figure 39 displays Converged Uplink Sets and FCoE networks in the VC Domain details.
Figure 40 VC Domain network details LACP timer attributes SNMP Access VCEM displays VC Domain and VC Domain Group Ethernet SNMP access information by clicking More Details ... at the bottom of the properties window. Figure 41 displays SNMP access. NOTE: This feature is only available for Ethernet modules and not available on VC firmware earlier than 3.7x.
Using VLAN capacity CAUTION: VCM firmware versions 3.3x through 3.6x or later does not allow you to easily revert back from Expanded VLAN capacity mode to Legacy capacity mode. To revert back to Legacy capacity mode, you must delete the VC Domain in VCM. VC firmware 3.7x removes support for legacy VLAN capacity. All VC domains with VC 3.7x installed support "Expanded VLAN Capacity". When adding a VC 3.
Canceling a VC Domain Maintenance task Canceling a VC Domain Maintenance discards domain, network, and storage configuration changes that you have performed while in maintenance mode, and returns the VC Domain to the configuration that is shared by all VC Domains within a VC Domain Group. If the VC firmware on the VC Domain is updated while the domain is in maintenance mode, the updated firmware is not rolled back if maintenance is canceled.
Figure 42 Job details Replacing the HP 1/10 Gb VC-Enet or the HP 1/10 Gb-Enet modules To upgrade the HP 1/10 Gb VC-Enet module or the HP 1/10 Gb-Enet module to use the HP VC Flex-10/10D module see sections “Replacing VC Ethernet modules with FlexFabric modules in an existing VCEM managed VC Domain” (page 72) or “Replacing VC Ethernet in interconnect bays three to eight with FlexFabric in an existing VCEM managed VC Domain” (page 72).
After performing all the steps in “Adding FlexFabric modules to an existing VCEM managed VC Domain” (page 71), you can create or edit any existing server profiles and use the available networks or SAN Fabrics from the FlexFabric module to create FCoE or iSCSI connections. Replacing VC Ethernet modules with FlexFabric modules in an existing VCEM managed VC Domain To replace a VC Ethernet module with a FlexFabric module in a VC Domain managed by VCEM, perform the following steps: 1.
9. 10. 11. 12. 13. 14. 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). 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. Edit an existing server profile and add a network connection that uses the FlexFabric uplink port.
6. 7. 8. 9. 10. 11. 12. 13. Replace the blade server FC HBA mezzanine cards with FlexFabric Adapter mezzanine cards. Unassign any FC profile connections that are attached to the interconnect bays being replaced. This can be done by unassigning the FC connections in the server profile. HP recommends that you do this in order so you do not lose the WWN addresses. Delete any FC SAN fabric connections that were created using uplinks from the interconnect bays that are to be replaced.
6. 7. Select the same VC Domain and click Add to VC Domain Group if there is an existing VC Domain Group that meets the minimum requirements. Otherwise, click New VC Domain Group. Wait for the job to complete successfully. Reassign the server profiles and then add the FC Connections to the profiles (if necessary). Verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group. For more information, see “Requirements for adding a VC Domain to a VC Domain Group” (page 30).
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” (page 17) for more details regarding supported VC firmware versions.
8. If you kept the server profiles (step 1) unassigned in the VC Domain Group then perform the following steps to assign the server profiles back to the original VC Domain with replaced VC modules: a. Click the Server Profiles tab from the VCEM home page. b. Select VC Domain in the first filter and select the VC Domain name (with the replaced VC modules) in the second filter. c. For each server profile that was in the VC Domain (now with replaced VC modules) perform the following steps: i.
8. Recreate the server profile SAN connections in VCEM. CAUTION: The VC and VCEM identifiers (WWNs) associated with the removed server profiles’ FC connections can be assigned to different server ports or slots in the recreated server profile SAN connections using FCoE Connections. Recreating the SAN connections in the server profile means that the newly created connections will be assigned new WWNs. 1.
4 Managing VC Domain groups This section describes the management of VC Domain Groups using VCEM. A VC Domain consists of an HP BladeSystem enclosure, a set of associated Virtual Connect Ethernet and Fibre Channel interconnect modules, and server blades that are managed together by a single instance of VCM. The VC Domain contains specified networks, server profiles, and user accounts that simplify the setup and administration of server connections.
Table 15 Group icons and status Status Icon Description Configuration in synch All VC Domains that belong to this VC Domain Group share the same domain configuration Under maintenance VC Domain is unlocked for domain, network, and storage changes through the VCM. After completing the domain, network and storage changes, you must confirm the new VC Domain configuration in VCEM.
5. Go to Systems Insight Manager and perform a manual discovery on Onboard Administrator IP address of all related VC Domain enclosures. If you are using the HP VC FlexFabric 10 Gb 24-port module, ensure that the module status is compatible. If the module is incompatible, an error message appears. VCEM cannot manage a VC Domain that has one or more FC modules in an incompatible state.
12. Click OK to go to the Jobs page and monitor job progress. 13. (Optional) After creating a VC Domain Group, from the Systems Insight Manager User and Authorization page, select the user authorization privileges for that VC Domain Group. See “Creating a VC Domain Group” (page 41) for more information. Maintaining a VC Domain from the VC Domain Groups page IMPORTANT: VCM 3.3x to 3.6x does not allow you to easily revert back from Expanded VLAN capacity mode to Legacy capacity mode.
VC Domain Group firmware mode at a later time by selecting 'Upgrade Firmware Mode' on the VC Domain Groups page. • 8. 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. Click OK to go to the Jobs page and monitor job progress.
5. Click OK to go to the Jobs page and monitor job progress. Deleting a VC Domain Group IMPORTANT: If you delete a VC Domain Group, then all unassigned server profiles within that VC Domain Group will be posted to one of the VC Domains that were part of the deleted VC Domain Group. To verify which VC Domain contains the unassigned server profiles after the VC Domain Group deletion job is completed, look at the report generated by the related job in the VCEM event.
4. Perform the following actions for each VC Domain that uses HP-predefined or user-defined ranges within the VC Domain Group that you want to remove. Factory-default MAC and WWN ranges are released back to VCM as Factory-default. If factory-default MAC or WWN addresses or serial numbers are not being used, address ranges must be specified for each removed VC Domain. These address ranges must be unique and distinct to prevent assignment of duplicate addresses.
NOTE: For QoS, Operation Permissions and multicast filters, details are only available if the VC Firmware is 4.0x or later. Figure 44 VC Domain Group details page Select a detail tab and view all properties about that tab. Figure 45 displays the VC Domain Group tab. Figure 45 VC Domain Group properties tab Viewing VC Domain Group QoS details To view QoS information on the VC Domain Group details page, select the QoS tab and the appropriate OoS is displayed.
Figure 46 VC Domain Group QoS passthrough information Figure 47 QoS custom with FCoE lossless configuration type Displaying VC Domain Group detail tabs 87
Figure 48 QoS custom without FCoE lossless configuration type 88 Managing VC Domain groups
Figure 49 QoS custom without FCoE lossless (DOT1P mapping) configuration type Viewing VC Domain Group roles To view allowed VC Domain Group role permissions, perform the following steps: 1. Select the VC Domain Group tab from the home page. 2. Click on the target VC Domain Group.
3. Select the Operation Permissions tab to view VC Domain Group roles. Figure 50 (page 90) displays an example. NOTE: Operation permissions are only displayed in VCEM and do not affect the VCEM GUI. For more information on VCM customizing role permissions see the HP Virtual Connect for c-Class BladeSystem User Guide at http://h18004.www1.hp.com/products/blades/ components/c-class-tech-installing.html.
Statistical throughput attributes VCEM displays statistical throughput configuration information in the VC Domain Properties and the VC Domain Group properties windows including: • Add to Group—When a VC Domain is added to a VC Domain Group, the statistics-throughput configuration setting from the VC Domain Group is applied to the VC Domain.
Viewing LACP timer attributes for VC Domain Groups VCM offers you the option of configuring the timeout for LACP which changes the frequency of control messages (LACPDU). The feature allows you to change the frequency, which can be either a short duration (1 second) or a long duration (30 seconds). Figure 54 displays default LACP timer duration information in the VC Domain Group properties.
Figure 55 VC Domain Group LACP timer attributes Adding or removing VC modules in a VC Domain Group To add or remove VC modules to all VC Domains managed by a VC Domain Group: 1. Click the VC Domain Groups tab. 2. Select the desired VC Domain Group where you want to add or remove VC modules, and then click Delete. For more information, see “Deleting a VC Domain Group” (page 84). 3.
Moving Ethernet networks (VLANs tagged) from one shared uplink to another 1. 2. 3. 4. 5. 6. 7. Click the VC Domains tab, and select a VC Domain. Click VC Domain Maintenance, and enable VC Domain Maintenance by clicking Make changes via VC Manager. In the VCM user interface, delete the desired shared uplink sets or delete desired Ethernet networks (VLANs tagged) from the shared uplink sets. Go back to VCEM and complete VC Domain Maintenance by clicking Complete VC Domain Maintenance. Repeat steps 1 and 2.
5 Managing server profiles This section describes how to create and manage server profiles with VCEM. A VC server profile is a logical grouping of attributes related to server connectivity that can be assigned to a server bay. A server profile can be assigned to any server bay within the VC Domain Group. VCEM requires the server to power down for any server profile operations such as create, delete, unassign, copy, move, and edit.
Item Description Enclosure Identifies the enclosure name Bay Bay number A server profile defines connections for a blade server.
Table 16 VCEM supported VC features (continued) Feature VC 4.0x VC 3.7x VC 3.5x-VC 3.60 VC 3.
Table 16 VCEM supported VC features (continued) Feature VC 4.0x Configurable role operations • LACP timer settings • VC 3.7x VC 3.5x-VC 3.60 VC 3.
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.
Figure 58 Selecting a Network window To make the search easier, you can apply filters by Name, Shared Uplink Set, VLAN ID, label or color. If you choose Name, Shared Uplink Set, VLAN or label, the second drop-down box defaults to Contains and you can enter part of a filter such as Name or Shared Uplink Set. If you choose Color, the drop-down box defaults to Is. Filters are helpful in situations where a VC Domain Group has a large amount of VLAN networks (up to 1000) configured.
Figure 60 iSCSI boot settings If you enter an incorrect field format, an error message with the appropriate format is displayed. The following table describes iSCSI boot setting attributes and field formatting. Setting Description iSCSI Boot Configuration Initiator Name (required) Name used for the iSCSI initiator boot system. The initiator name length is maximum of 256 characters. If the initiator name contains nonalphanumeric characters, it must be enclosed in double quotes.
Setting Description Use DHCP (optional) Click Use DHCP to enable the following: • iSCSIParamDHCP—Allows the iSCSI ROM option to retrieve iSCSI boot parameters. This attribute default is set to disable to allow for static configurations. • DHCP Vendor ID—Required if iSCSIParamDHCP is set to enable. Used to match the value in the Vendor Class ID field in the DHCP packet with retrieving either iSCSI Boot or network parameters. The Vendor ID field is restricted to 32 characters.
Figure 61 iSCSI Boot Assistant HP recommends that you use the iSCSI Boot Assistant rather than populating the iSCSI fields manually. The main goal of the iSCSI Boot Assistant is to save time. If you run the iSCSI Boot Assistant after manually populating the iSCSI fields, the values previously entered manually will be overwritten. 1. Choose a VC Domain and the Management Targets: selection box is enabled.
FCoE networks are only available when the group firmware mode of the VC Domain Group is 4.0x or later. Figure 62 FCoE network or SAN fabric selection 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.
To specify the LUN and a 16-digit hexadecimal number format, place the desired hexadecimal number preceded by leading zeros as shown in the following examples: • 1023 can be represented in 16-digit hexadecimal format as 00000000000003ff or 00000000000003FF (not case-sensitive). • 18446744073709551615 is represented in 16-digit hexadecimal format as ffffffffffffffff or FFFFFFFFFFFFFFFF. Configuring multiple networks To configure multiple networks 1.
Figure 64 Force same VLAN mappings as Shared Uplink Set options 4. Click the right-arrow to add the network to your configuration. To remove networks press the left-arrow. You can select all the VLAN networks available, but only 162 VLAN networks are accepted. The following message is displayed warning you about this limit. The provided configuration for multiple networks exceeds the maximum allowed number of VNet mappings. The maximum number of VNet mappings is [].
2. (Optional) To select the desired port speed for the connection, select Custom. The Custom Port Speed windows appears. Enter the desired port speed. Figure 65 Custom Port Speed window Deleting a server profile 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.
1. 2. 5. 6. 7. 8. 9. Choose the Network Access Group selection box. Choose another network access group. A warning message similar to the following can appear if Ethernet networks, multiple, or iSCSI connections are not associated with this network access group: VCEM will unassign all Ethernet/iSCSI connections in this server profile that are assigned to a Network with no association to the selected Network Access Group [nag1].
Figure 67 VCEM and VC statuses If a degraded status icon is displayed in the Status column, you can view the statuses of the iSCSI, FC, and FCoE network connections in the VCEM server profile GUI. Figure 68 displays some network status icons. “Connection type and status definition” (page 110) displays and defines connection type, status icons, and status definitions.
Table 17 Connection type and status definition Connection type Status icon Server profile Status definition The blue icon with an “i” in the middle indicates that the iSCSI connections are not mapped. (Not shown) The blue question marks indicate an unknown status. (Not shown) Degraded—If a degraded status icon is displayed in the Status row, you can view the statuses of the iSCSI, FC, and FCoE network connections in the VCEM server profile GUI.
Figure 70 Flexible page ranges You can select pages by choosing them in groups or you can enter a page into the Go to page: dialog box . You can also use the browser's search and find features for quick access to a particular server profile. Recovering server profiles from an unreachable enclosure IMPORTANT: Profiles can fail to boot from Direct Attached SAN fabric after relocation to another enclosure.
NOTE: Server profiles can be recovered from VC Domains containing a single c-Class enclosure. Server profiles cannot be recovered from multi-enclosure VC Domains. Figure 72 VC Domain disabled enclosure candidates If the enclosure is operational, you will receive a message similar to the following: 3. 112 If the enclosure is not operational, click OK to continue disabling the enclosure. Figure 73 displays a list of server profiles that will be recovered.
Figure 73 Recover server profiles list Recovering server profiles from an unreachable enclosure 113
4. Click OK to proceed or Cancel to stop server profile recovery. If there are no assigned server profiles in the VC Domain a message similar to the following is displayed. VCEM detected that the selected VC Domain contains no assigned server profiles to recover. VCEM will disable this enclosure. If VCEM is successful in disabling the enclosure and recovering the profiles, you receive a message and you are also able to access it in the job details. Figure 74 shows the job details.
There are two options available when selecting an Ethernet network: • Select a Network • Multiple Networks For iSCSI networks, only Select a Network is available. When a network is already selected, click Change Network to edit it. Selecting a single network When selecting a single network, you can filter with the following options: • Name • Shared Uplink Set • VLAN Id • Label • Color Use the Is/Contains combination box to search by part of a word or phrase.
Assigning a server profile 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. Assigning this Server Profile can make it inconsistent with the upper level manager.
Copying a server profile 1. From the Server Profiles page, select the server profile that must be copied and assigned. NOTE: Profiles with NPIV settings edited by upper level managers such as Matrix OE cannot be copied directly in VCEM. These profiles must be managed through the upper level software that created them. 2. 3. 4. Click Copy. Enter a unique name for the new server profile. (Optional) Select an available bay to which the new server profile is assigned.
Moving a server profile to another bay in the same VC Domain Group To proceed, you must enter YES, and then click OK. NOTE: 1. 2. 3. VCEM does not respond if you cut and paste YES into the field. Select a server profile from the Server Profiles page. Click Move. The Move Server Profile page appears. 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 75: Figure 75 Moving a server profile 4. 5. 6.
Figure 76 Move profile prevalidation table VCEM performs five validation steps during the export process as displayed in Figure 76. 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.
Table 18 Prevalidation status Status Description Done Step has successfully completed. Configuration VCEM will perform some changes on the server profile in order to export it to the target VC Domain Group.
• • Confirms that the target VC Domain Group that the server profile will be exported to has a status of Configuration in synch. VC Domain Groups with other statuses such as the following list cannot receive exported server profiles: ◦ Under maintenance ◦ Incompatible firmware Ensures that the target VC Domain Group virtual MAC, WWN and Serial Number range types are compatible with addresses allocated in the selected server profile. See Table 11 (page 31)) for more information.
defined in the target VC Domain Group. Otherwise Step 4 will show a warning status at the prevalidation window. • Confirms that all VLAN network names and their associated Shared Uplink Set exist in the target VC Domain Group with the following conditions: ◦ Ethernet connections are defined as Multiple Networks. ◦ Multiple networks have the Force same VLAN mapping as Shared Uplink Sets option selected.
5. Validating Fabric data—VCEM performs the following validations for fabric connections during the export process: • Ensures that the fabric names and I/O bays exist in the target VC Domain Group. Fabric names and I/O bays used by the server profile FC and FCoE connections must match the fabric names and I/O bay positions defined in the target VC Domain Group. These two conditions are mandatory for the server profile FC/FCoE connection be exported successfully.
1. 2. 3. 4. Power down the original or source server. Select a new target server from the VC Domain Group spare pool. Move the VC server profile to the target server. Power up the new server. VC Server Profile Failover operations require the source and target servers to be configured to boot-from-SAN, and can be initiated from the VCEM graphical user interface (GUI) as a one-button operation or from a command line interface (CLI).
To initiate VC Server Profile Failover using the CLI, enter C:\>VCEM -failover arguments, then enter the appropriate argument as follows: • For a bay, enter -bay enclosure_name:bay_number • For a host, enter -host hostname • For an IP address, enter -ip IP_address The host and IP address are valid arguments only when Systems Insight Manager runs on the same system as VCEM and full server discovery is operating in Systems Insight Manager.
6. 7. 8. Select Run custom CMS tool, and then select VCEM Server Profile Failover by Hostname. If there is a specific time the event handler must be active, choose a time filter. Review the selected events, systems, and actions for the automatic event handler. VC Server Profile Failovers now occur whenever any designated system generates one of the events within the event collection.
6 Managing enclosure bay assignments Only the bays that are inside a VC Domain Group appear on the Bays page. Bays can be filtered by selecting one of the following entries in the Filter list: • All—Select this option to display all bays. • VC Domain—Select this option to display all bays that exist in a specified VC Domain. The second list can be used to select a specific VC Domain to use as a filter. • VC Domain Group—Select this option to display all bays that exist in a specific VC Domain Group.
To see more information about bays, select the Show more details check box. The following table describes the additional information that will be displayed. Item Description Server model Model of server Power Server is powered-up or powered-down UID Reports if the identification light on the device is powered-up or powered-down To see server bay status and blade server information (if there is a server in a selected bay), click the bay number, then a status window appears.
Figure 78 Window displaying the power status of a bay To remotely power down a bay: 1. Click the Bays tab. 2. To determine the power status of the bay, click the bay number. A status window appears. 3. Depending on the power status of the bay, perform one of the following steps: • If the bay is currently powered down, then proceed to the Assigning a server profile to a bay procedure section. • If the bay is currently powered up, then click Momentary Press, which automatically powers down the bay.
Assigning a server profile to a bay You can assign a server profile to a bay only if the bay is not already associated with a server profile and if the server is powered down. To assign a server profile to a bay: 1. Click the Bays tab. 2. (Optional) From the Filter list, select VC Domain or VC Domain Group, and click Filter. 3. Select the bay. 4. Click Assign Server Profile. The Assign Server Profile page appears. 5. Select an unassigned server profile. 6. Click OK.
For more information about failover pre-requirements, see “Preconditions for VC Server Profile Failover” (page 124) Performing a Server Profile Failover 131
7 Managing MAC and WWN addresses MAC Addresses NOTE: A "VCEM-defined” range has been reserved, from which VCEM allocates MAC addresses. VCEM no longer uses the “HP pre-defined” range for MAC address allocation. However, server profiles created before VCEM 1.40 will continue to use the HP pre-defined addresses already assigned to them. When using VCEM-assigned MAC addresses, you can choose between VCEM-defined MAC address ranges or user-defined MAC address ranges.
Creating MAC exclusion ranges VCEM requires that you define exclusion ranges for both MAC and WWN addresses if: • VCEM and VC Domains outside of VCEM management are sharing the same user-defined MAC and WWN ranges. • VCEM is running in a federated CMS environment where multiple instances of the VCEM application are operating on the same network. NOTE: In the case of federated CMS environments, you can select from a pre-defined VCEM MAC subrange during a new HP Insight Management DVD installation.
To change the status of an address from External to Free, use the Reclaim External button. Before freeing an address, verify that the address is no longer used by a VC Domain outside of VCEM. To reclaim MAC addresses: 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. 4. Select the Individual addresses tab. 5. From the Filter list, select External. 6.
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.
Item Description External Address Addresses used by server profiles in a VC Domain that has been released back to VCM and no longer managed by VCEM. Excluded Addresses Addresses that reside in a VCEM Exclusion range list. VCEM will not allocate any address that is marked as excluded. Creating WWN exclusion ranges VCEM requires that you define exclusion ranges for both MAC and WWN addresses if: • VCEM and VC Domains outside of VCEM management are sharing the same user-defined MAC and WWN ranges.
Figure 82 MAC exclusion ranges Figure 83 WWN exclusion ranges Address management tasks 137
Using VCEM subranges in a federated CMS environment In a federated CMS environment, it is critical to select unique pre-defined VCEM subranges during HP Insight Management DVD installation for each CMS in the federation. This prevents the different VCEM instances from using MAC or WWNs which belong to other instances. This also results in an automatic creation of VCEM exclusion ranges for MAC or WWNs which do not belong to a particular VCEM instance.
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. 4. 5. At the target CMS, browse to the MAC address management page and remove MAC exclusion range1 from the VCEM-defined exclusion ranges.
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 7.
Displaying factory default MAC and WWN addresses NOTE: There is not any label or attribute indicating that the MAC or WWN addresses displayed are factory defaults, it is up to you to identify that. For VC firmware 3.
4. Click Delete. You are prompted to confirm your choice. 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.
Deleting a custom WWN address range NOTE: 1. 2. 3. 4. Removing a custom WWN address range also removes its defined exclusion ranges. From the Select ranges to configure link, select WWN. Select the custom WWN range. Click Delete. You are prompted to confirm your choice. Click OK.
8 Working with Logical Serial Numbers This section describes how to view logical serial numbers that exist in server profiles being managed by VCEM. These numbers are displayed for informational purposes. Logical serial numbers move with a server profile. The logical serial number is a 10-character string.
9 Tracking VCEM job status Jobs The Jobs list provides detailed information about jobs that have occurred and are related to VCEM. To view these jobs, click the Jobs tab. The Jobs list appears. From this list, you can perform the following tasks: • Review a summary of jobs • Select and review details of jobs • Select and delete jobs Figure 86 Jobs list The following table lists describes the job item columns or drop-down menu in the Jobs list.
VCEM limits the number of jobs that it displays to 65,000. If the limit is reached, then only the most recent 65,000 jobs are viewable. To keep the list smaller, you can select the jobs to be deleted, and then click Delete. Reviewing job details To review the details of a particular job, click the hyperlink of the appropriate job name. The Job Details window appears. Deleting jobs To delete a particular job or multiple jobs, click Delete. Only pending, failed, or completed jobs can be deleted.
10 Upgrading VC firmware after VCEM is managing VC Domains The process for upgrading VC firmware requires extra steps when VCEM is managing the VC Domain. VCEM gains exclusive access to managed domains. However, using the VC Domain Maintenance capability, the VCM can be used to upgrade VC firmware while the VC Domain is being managed by VCEM. IMPORTANT: Starting with VCEM 7.1.1 or later versions of VC firmware prior to VC 3.30 are not supported. If you have versions of VC firmware before 3.
Performing the firmware update using the VC Domain Maintenance capability CAUTION: Do not update to VC firmware 3.7x or later if the VC Domain Group firmware mode is 3.15. This is because VC firmware 3.7x and later are not compatible with VC firmware 3.15. If you update to VC firmware 3.7x or later, your only options are to either remove the updated VC Domain from the VC Domain Group, or to use VCSU to downgrade the VC Domain firmware to the previous version.
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, see the HP Virtual Connect Manager Command Line Interface User Guide at http://www.hp.com/go/virtualconnect.
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.
Internal VCEM Error Message: Enclosure name contains too many characters - limit is 32 Performing VC Profile Failover on the specified VC Domain Bay Server... ERROR (30) - Could not initiate VC Profile Failover Internal VCEM Error Code: 5009 Internal VCEM Error Message: Invalid format for IP address - it must be: [0-255].[0-255].[0-255].
Show CLI usage online help This CLI command can be used to display brief usage help on the screen. >vcem -help Several CLI option keywords provide for abbreviated alternatives – that is, {-failover | -fo}.
13 Troubleshooting VCEM When you are upgrading to a new and different CMS, or are moving to a 64-bit CMS, you might need to migrate your data by using the Systems Insight Manager data migration tool. If you are upgrading to a new version of VCEM on the same CMS, data migration with the Systems Insight Manager data migration tool is not necessary. For more information, see the Data Migration of an Existing Microsoft Windows CMS to a new Insight Management 7.
3. 4. 5. 6. Enter set external-manager Username=xyz Enabled=false to temporarily disable the account. Identify the features that are enabled and disable them. See “Requirements for adding a VC Domain to a VC Domain Group” (page 30) for more information on enabled features. Enter set external-manager Username=xyz Enabled=true from the VCM command prompt to enable the account. Perform the VC Domain resynchronization operation again.
recreating the VC Domain Group. See the HP Matrix Operating Environment Infrastructure Orchestration User Guide at http://www.hp.com/go/matrixoe/docs.
• 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.
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.
2. list. If not, re-order the network adaptors so the network adaptor handling communications with VCM is the first one in the list. 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.
A job appears with Failed status A job might fail for several reasons. For more information about the reason of job failure and how to correct the issue, see the job details: 1. From the VCEM home page, click the Jobs tab. 2. Locate the job, either by its ID or its name. 3. For detailed information about the job and how you can resolve the issue, click the task name of this job. 4. (Optional) Job details might appear to be truncated when the text exceeds 256 characters.
Unable to add VC Domain to a VC Domain Group If the VC Domain is not the same as the VC Domain configuration group, then you might not be able to add the VC Domain to the VC Domain Group. To correct this issue, verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group. For more information, see “Requirements for adding a VC Domain to a VC Domain Group” (page 30).
VC Domain displays Missing External Manager lock status If the VC Domain displays a status of Missing External Manager lock icon, the external manager lock has either been suspended or removed. To correct this issue with a VC Domain, remove the VC Domain from VC Domain Group, break the external manager lock and release these MAC, WWN, and serial number address ranges as follows: 1. Telnet in to the VCM using an SSH connection such as SSH Administrator@xxx.xxx.xxx.xxx, where xxx.xxx.xxx.
For information on enclosure problems, see “Enclosure has a hardware failure and must be replaced” (page 169). • In a redundant environment, the failover between active and standby VC module is taking place. To correct this issue: 1. Verify that the failover between the active and standby VC module is taking place. 2. Wait a few minutes until the failover completes, and then try again. 3. Log into VCM (https://). A status of Active Virtual Connect Manager not at this IP address might appear.
1) Address is being used in VCEM. 2) Address conflicts with an existing Exclusion Range. 3) Address does not fall within the defined VCEM Global Range. To identify why the issue occurred, consider that both VC and VCEM use two MAC addresses for each Ethernet network connection and two WWN addresses for each Fibre Channel connection. However, only one of these addresses appears in the user interface.
Remove from VC Domain Group job is successful but with errors Occasionally, when successfully performing a remove from VC Domain Group job, an error might appear in the job detail. The error is related to VCEM being unable to: • Release control over the MAC and WWN address pools, or serial number range. • Remove external manager. To correct the issue related to removal of external manager or unable to release control of MAC, WWN, and serial number ranges, perform the following: 1.
3. Check the Systems Insight Manager database server status: a. If the database server is remote, then log in to the database server. b. In the Windows taskbar, check if the Microsoft SQL Server, Express or MSDE service is running. A red status means they are not running. c. Right-click the status, and then select Start. 4. If this issue still occurs, then uninstall and reinstall VCEM. .
Creating a server profile or adding a VC Domain with a server profile to a VC Domain Group fails Attempting to create a profile or adding a VC Domain to a VC Domain Group might fail if any of the following occur: • VCEM does not have enough free MAC or WWN addresses. • Some MAC or WWN addresses are already being used by another server profile. • The MAC or WWN addresses in use by the VC Domain are not defined as custom ranges in VCEM. To resolve this issue: 1.
Table 21 Components restored without a backup strategy Restored components Management server stored components Local user accounts Unassigned server profiles Network and SAN configurations VC Domain Groups Assigned server profiles MAC and WWN exclusions The Domain Network and SAN Configuration and assigned Server Profiles can be recovered from the VC modules. The VC Domain Group definitions, MAC and WWN custom ranges, and MAC and WWN address exclusions are stored only on the Management Server.
d. To remove the account and release the VC Domain from VCEM control, from the VCM command prompt, enter remove external-manager Username=xyz mactype= MacStart=<> MacEnd=<> wwnType= WwnStart=<> WwnEnd=<> serverIdType= serverIdStart=<> serverIdEnd=<> NOTE: “-quiet” is an option to suppress user confirmation prompts. This option is useful for scripting operations. This option is available for VC firmware 1.
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.
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.
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.
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.
Create VC Domain Group or Add VC Domain to VC Domain Group operations fail and the message "An invalid boot LUN was entered. Check the storage arrays for the proper LUN number" appears VCEM requires the boot target LUN configuration and server profiles to be either a three-digit decimal between 0–255, or a 16-digit hexadecimal value between 0 and FFFFFFFFFFFFFFFF.
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
With this service, Insight Management customers benefit from expedited problem resolution as well as proactive notification and delivery of software updates. For more information about this service, see the following website: http://www.hp.com/services/insight Registration for this service takes place following online redemption of the license certificate.
Computer output Text displayed by the computer. Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH. ERROR NAME The name of an error, usually returned in the errno variable. Key The name of a keyboard key. Return and Enter both refer to the same key. Term The defined use of an important word or phrase.
15 Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.com Include the document title and part number in your message. All submissions become the property of HP.
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 (continued) VCEM Subrange MAC Start End Start End 31 00-21-5A-9B-78-00 00-21-5A-9B-7B-FF 50:01:43:80:02:A3:78:00 50:01:43:80:02:A3:7B:FF 32 00-21-5A-9B-7C-00 00-21-5A-9B-7F-FF 50:01:43:80:02:A3:7C:00 50:01:43:80:02:A3:7F:FF 33 00-21-5A-9B-80-00 00-21-5A-9B-83-FF 50:01:43:80:02:A3:80:00 50:01:43:80:02:A3:83:FF 34 00-21-5A-9B-84-00 00-21-5A-9B-87-FF 50:01:43:80:02:A3:84:00 50:01:43:80:02:A3:87:FF 35 00-21-5A-9B-88-00 00-21-5A-9B-8B-FF 50:01:43:80:02:A3
Table 22 MAC and WWN subranges (continued) VCEM Subrange MAC 66 Start WWN End Start End 00-21-5A-9C-04-00 00-21-5A-9C-07-FF 50:01:43:80:02:A4:04:00 50:01:43:80:02:A4:07:FF 67 00-21-5A-9C-08-00 00-21-5A-9C-0B-FF 50:01:43:80:02:A4:08:00 50:01:43:80:02:A4:0B:FF 68 00-21-5A-9C-0C-00 00-21-5A-9C-0F-FF 50:01:43:80:02:A4:0C:00 50:01:43:80:02:A4:0F:FF 69 00-21-5A-9C-10-00 00-21-5A-9C-13-FF 50:01:43:80:02:A4:10:00 50:01:43:80:02:A4:13:FF 70 00-21-5A-9C-14-00 00-21-5A-9C-17-FF 50:01:43:80:02
Table 22 MAC and WWN subranges (continued) 182 VCEM Subrange MAC 101 Start End 00-21-5A-9C-90-00 00-21-5A-9C-93-FF 50:01:43:80:02:A4:90:00 50:01:43:80:02:A4:93:FF 102 00-21-5A-9C-94-00 00-21-5A-9C-97-FF 50:01:43:80:02:A4:94:00 50:01:43:80:02:A4:97:FF 103 00-21-5A-9C-98-00 00-21-5A-9C-9B-FF 50:01:43:80:02:A4:98:00 50:01:43:80:02:A4:9B:FF 104 00-21-5A-9C-9C-00 00-21-5A-9C-9F-FF 50:01:43:80:02:A4:9C:00 50:01:43:80:02:A4:9F:FF 105 00-21-5A-9C-A0-00 00-21-5A-9C-A3-FF 50:01:43:80:02:A4:A0:
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 management server A system in the management domain that executes the Systems Insight Manager software. All central operations within HP Insight Control are initiated from this system.
external port The Ethernet connectors (10GBASE-CX4 and RJ45) on the faceplate of the VC-Enet module labeled as ports 1-8, X1, and X2. firmware upgrade Upgrading VC firmware to a later version. free Address available for VCEM allocation. full configuration rights user A user who is automatically authorized for the All Tools toolbox on all systems, including the CMS. This type of user has been given special privileges to administer the HP Insight Control software.
MSCS Microsoft Cluster Server cluster Onboard Administrator The Onboard Administrator is the central point for controlling an entire c-Class rack. It offers configuration, power, and administrative control over the rack, and its associated blades (Compute Servers), blade management processors (iLOs), network switches (depending on the models of switches used) and storage components (such as SAN or SATA).
• Minor. A warning condition exists that can escalate into a more serious problem. • Normal. These events are not a problem. • Informational. No attention required. This status is provided as useful information unknown status HP 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.
Index A H adding a VC Domain to a VC Domain Group, 48 adding custom MAC address ranges, 134 adding custom WWN address range, 142 adding or removing VC modules to VC Domain Group configuration, 93 assigning a profile, 116 assigning a server profile, 116 assigning a server profile to a bay, 130 HP Virtual Connect Enterprise Manager key features and benefits, 9 product introduction, 9 upgrading VC firmware after VCEM is managing VC Domains, 147 B bays assigning a server profile to a bay, 130 powering down
assigning a server profile, 116 configuring multiple networks, 105 configuring network port speed, 106 configuring the target boot LUN, 104 copying and assigning a server profile to a bay, 117 creating a server profile, 98 deleting a server profile, 107 editing a server profile, 107 moving a server profile, 117 performing a VC server Profile Failover, 123 unassigning a server profile, 116 verifying the presence of EFI partition data, 115 server profile edit operation fails when target server is powered on,
adding a VC Domain to a VC Domain Group, 48 cancelling a VC Domain Maintenance task, 70 creating a VC Domain Group, 41 licensing an enclosure for VCEM, 40 multienclosure, 51 removing a VC Domain from a VC Domain Group, 50 requirements for adding a VC Domain to a VC Domain Group, 30 VC Domain in VC Domain Maintenance, 54 VC Domain tasks, 40 VC firmware updating, 22 VC Profile Failover CLI exit and error codes, 153 list details for specified VCEM job, 152 show CLI usage online help, 153 VC Server Profile Fail
