HP Virtual Connect for C-Class Bladesystem User Guide

HP Virtual Connect for c-Class BladeSystem User Guide

Part Number 416818-008 November 2008 (Eighth Edition)

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.

Microsoft is a U.S. registered trademark of Microsoft Corporation.

Intended audience This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

Contents

Setup...... 8 Virtual Connect overview...... 8 Pre-deployment planning ...... 9 Hardware setup overview...... 10 Default module configuration ...... 11 Virtual Connect Manager setup overview ...... 11 Component identification...... 13 HP 1/10Gb VC-Enet Module components and LEDs ...... 13 HP 1/10Gb VC-Enet Module components ...... 13 HP 1/10Gb VC-Enet Module LEDs...... 14 HP 1/10Gb VC-Enet Module system maintenance switch ...... 15 HP 1/10Gb-F VC-Enet Module components and LEDs ...... 16 HP 1/10Gb-F VC-Enet Module components ...... 16 HP 1/10Gb-F VC-Enet Module LEDs ...... 16 HP 1/10Gb-F VC-Enet Module system maintenance switch ...... 18 HP Virtual Connect Flex-10 10Gb Ethernet Module components and LEDs ...... 19 HP Virtual Connect Flex-10 10Gb Ethernet Module components ...... 19 HP Virtual Connect Flex-10 10Gb Ethernet Module LEDs ...... 20 HP Virtual Connect Flex-10 10Gb Ethernet Module system maintenance switch ...... 22 HP 4Gb Fibre Channel Module components and LEDs ...... 23 HP 4Gb VC-FC Module components ...... 23 HP 4Gb VC-FC Module LEDs ...... 24 HP 4Gb VC-FC Module system maintenance switch ...... 25 HP Virtual Connect 4Gb FC Module (with enhanced NPIV) components and LEDs ...... 26 HP Virtual Connect 4Gb FC Module components...... 26 HP Virtual Connect 4Gb FC Module LEDs ...... 27 HP Virtual Connect 4Gb FC Module system maintenance switch...... 28 Resetting the Administrator password and DNS settings...... 28 Warning messages...... 29 Installation ...... 31 Supported configurations ...... 31 HP BladeSystem c7000 Enclosure supported configurations ...... 31 HP BladeSystem c3000 Enclosure supported configurations ...... 33 Installation guidelines...... 33 HP Virtual Connect Flex-10 Module guidelines ...... 35 Firmware requirements ...... 35 Virtual Connect and EBIPA...... 35 Installing a VC-Enet module ...... 36 Upgrading to an HP Virtual Connect Flex-10 Module ...... 38 Installing a VC-FC module ...... 39 Factory default settings...... 41 Installing SFP/SFP+/XFP transceivers ...... 41 Removing SFP/SFP+/XFP transceivers ...... 42 Recommended stacking connections ...... 43 Loop prevention ...... 45

Contents 3

Connecting Virtual Connect Ethernet module uplinks ...... 45 Configuration example using a Cisco Core switch ...... 48 Failover and check-pointing ...... 50 HP Virtual Connect Manager...... 52 Configuring browser support ...... 52 Virtual Connect and RDP ...... 52 Accessing HP Virtual Connect Manager ...... 53 Command line overview...... 53 Logging on to the HP Virtual Connect Manager GUI ...... 54 HP Virtual Connect Home...... 55 About HP Virtual Connect Manager...... 55 Navigating the HP Virtual Connect Manager GUI...... 56 Navigation overview ...... 56 Tree view ...... 57 Domain Status summary ...... 58 Domain Status screen...... 60 Enclosures View ...... 61 Status icon definitions ...... 62 Other icon definitions...... 63 Export support information...... 63 Reset Virtual Connect Manager ...... 64 Running the setup wizards...... 64 HP Virtual Connect Domain Setup Wizard...... 64 HP Virtual Connect Network Setup Wizard...... 75 HP Virtual Connect Fibre Channel Setup Wizard ...... 85 Virtual Connect Manager Server Profile Wizard ...... 91 Verifying data center connections...... 100 Verify link and speed ...... 100 Verify network status using VC Manager ...... 101 Network management...... 102 Networks overview...... 102 Smart Link...... 102 Private Networks ...... 102 Define Ethernet Network screen...... 103 Defining a network ...... 104 Ethernet Networks (External Connections) screen ...... 105 Edit Ethernet Network screen ...... 107 Ethernet Networks (Server Connections) screen ...... 109 Ethernet Settings (MAC Addresses) screen ...... 110 Ethernet Settings (Port Monitoring) screen ...... 111 Select Monitored Ports screen...... 114 Ethernet Settings (Advanced Settings) screen...... 115 Server VLAN Tagging Support ...... 117 Multiple Networks Link Speed Settings ...... 119 MAC Cache Failover ...... 119 IGMP Snooping ...... 120 Stacking Links screen ...... 120 Shared uplink sets and VLAN tagging...... 120 Define New Shared Uplink Set screen...... 121 Defining a shared uplink set...... 123 Edit Shared Uplink Set screen ...... 124 Shared Uplink Sets (External Connections) screen ...... 127

Contents 4

Shared Uplink Sets (Associated Networks) screen ...... 127 Storage management ...... 129 Storage overview ...... 129 Virtual Connect Fabric...... 129 Login distribution ...... 130 Define SAN Fabric screen ...... 131 Enabling NPIV on the fabric switch...... 132 Brocade switch...... 132 Cisco switch ...... 133 McData switch ...... 133 SAN Fabrics (External Connections)...... 133 SAN Fabrics (Server Connections) ...... 134 Edit SAN Fabric...... 136 Fibre Channel Settings (FC SAN Settings) screen ...... 137 Server management ...... 139 Server profile overview ...... 139 Flex-10 overview ...... 140 Flex-10 configuration ...... 142 PXE settings ...... 145 Define Server Profile screen ...... 146 Advanced Profile Settings ...... 150 Defining a Server Profile...... 150 Fibre Channel boot parameters ...... 157 Server Profiles screen...... 158 Edit a Server Profile (single profile) screen ...... 159 Edit a Server Profile (Inline)...... 162 View printable report...... 163 Server profile troubleshooting ...... 163 Serial Number (Logical) Settings...... 164 Domain management ...... 166 Domain overview ...... 166 Enclosure serial numbers ...... 166 Domain Settings (Domain Configuration) screen ...... 166 Deleting a domain...... 167 Domain Settings (Domain IP Address) screen ...... 168 Domain Settings (Domain Enclosures)...... 169 Domain Settings (Backup/Restore) screen ...... 169 Domain Settings (Firmware Management) screen...... 170 Domain Settings (Local Users) screen ...... 172 Add new user ...... 175 Directory Settings (Directory Server) screen ...... 177 Directory Settings (Directory Groups) screen ...... 178 Add LDAP Group ...... 179 Directory Settings (Directory Certificate) screen...... 179 Test LDAP authentication ...... 180 SNMP and SMI-S overview...... 181 VC domain status change notifications ...... 183 SNMP Settings (SNMP Enet Settings)...... 183 SNMP Settings (SNMP FC Settings)...... 185 System Log screen ...... 186 System Log Configuration...... 187

Contents 5

Certificate Administration...... 189 Certificates/Authentications (SSL Certificate) screen ...... 189 Certificate Request...... 190 Certificate Upload ...... 191 Certificates/Authentications (SSH Administration) ...... 192 Web SSL Configuration...... 193 Hardware information screens...... 195 Enclosure Information screen...... 195 Enclosure Status screen ...... 196 Interconnect Bays Status and Summary screen...... 197 Interconnect Bay Summary screen (Ethernet module)...... 198 Interconnect Bay Summary screen (VC-FC Module) ...... 208 Administrative module removal...... 210 Interconnect Bay Overall Status icon definitions ...... 211 Interconnect Bay OA Reported Status icon definitions...... 211 Interconnect Bay VC Status icon definitions ...... 212 Interconnect Bay OA Communication Status icon definitions...... 212 Server Bays Summary screen ...... 213 Double-dense server bay option...... 213 Server Bay Overall Status icon definitions ...... 216 Server Bay OA Reported Status icon definitions...... 216 Server Bay VC Status icon definitions ...... 216 Server Bay OA Communication Status icon definitions ...... 217 Server Bay Status screen ...... 218 Regulatory compliance notices ...... 221 Regulatory compliance identification numbers ...... 221 Federal Communications Commission notice...... 221 FCC rating label...... 221 Class A equipment...... 221 Class B equipment ...... 221 Declaration of conformity for products marked with the FCC logo, United States only...... 222 Modifications...... 222 Cables...... 222 Canadian notice (Avis Canadien)...... 223 European Union regulatory notice ...... 223 Disposal of waste equipment by users in private households in the European Union...... 223 Japanese notice ...... 224 BSMI notice ...... 224 Korean notice ...... 224 Chinese notice ...... 225 Laser compliance ...... 225 Electrostatic discharge...... 226 Preventing electrostatic discharge ...... 226 Grounding methods to prevent electrostatic discharge...... 226 Technical support...... 227 Before you contact HP...... 227 HP contact information...... 227 Customer Self Repair ...... 227 Acronyms and abbreviations...... 235

Contents 6

Glossary ...... 238 Index...... 239

Contents 7

Setup

Virtual Connect overview Virtual Connect is a set of interconnect modules and embedded software for HP BladeSystem c-Class enclosures that simplifies the setup and administration of server connections. HP Virtual Connect includes the following components: • HP 1/10Gb Virtual Connect Ethernet Module for c-Class BladeSystem • HP 1/10Gb-F Virtual Connect Ethernet Module for the c-Class BladeSystem • HP Virtual Connect Flex-10 10Gb Ethernet Module for BladeSystem c-Class • HP 4Gb Virtual Connect Fibre Channel Module for c-Class BladeSystem • HP Virtual Connect 4Gb Fibre Channel Module for BladeSystem c-Class (enhanced NPIV) • HP Virtual Connect Manager Virtual Connect implements server edge virtualization so that server administrators can upgrade, replace, or move server blades within their enclosures without changes being visible to the external LAN and SAN environments. The Virtual Connect Manager is embedded on the Virtual Connect Ethernet module and is accessed by users through a web-based GUI or CLI. A web link to the GUI and console connection to the CLI are provided by the Onboard Administrator. The Virtual Connect Ethernet modules support the HP BladeSystem c7000 Enclosure, HP BladeSystem c3000 Enclosure, and all the server blades and networks contained within the enclosure. The modules enable connection to all brands of data center Ethernet switches. The Virtual Connect FC Modules enable connection of the enclosure to Brocade, Cisco, McData, or Qlogic data center Fibre Channel switches, but the modules do not appear as a switch to the Fibre Channel fabric. A Virtual Connect domain currently includes a single HP c-Class BladeSystem c7000 Enclosure for a total of 16 servers (or up to 32 servers if the double-dense option is enabled), or a single HP c-Class BladeSystem c3000 Enclosure for a total of eight servers (or up to 16 servers if the double-dense option is enabled). Within the domain, any server blade can access any LAN or SAN connected to a VC module, and a server blade can be used as a spare for any server blade within the same enclosure. By stacking (cabling) the Ethernet modules within the domain and connecting the FC modules to the same set of FC SAN(s), every server blade in the domain can be configured to access any external network connection. With this configuration, the Virtual Connect Manager can deploy and migrate a server blade profile to any server in the Virtual Connect domain without the need to change external LAN or SAN configurations.

Setup 8

Pre-deployment planning During the planning phase, the LAN and server administrator must determine how each server blade will connect to the network and in which IP network and VLAN the server will reside. In a traditional network, these connections are through physical cables. If a move from one network to another is required, the cables must also be moved. Virtual Connect provides a wire-once implementation when VC modules are connected to upstream or core switches and the VC networks and server profiles are defined. Assigning a server profile to a server blade completes the physical connection to the core network. In the event of a server blade failure or move, all of the configuration parameters can be transferred easily to the new server. Before beginning installation, complete the following tasks: • Be sure that the firmware revisions on all Virtual Connect modules in the domain are at the same revision level. The active Virtual Connect manager does not allow incompatible modules to be managed as part of the same Virtual Connect domain. For additional information, see "Firmware requirements (on page 35)." • Be sure that OA, iLO, server blade system ROM, Ethernet option ROM, and FC option ROM firmware are up-to-date. For additional information, see the HP Virtual Connect Release Notes and Compatibility Matrix and the HP website (http://www.hp.com/go/bladesystemupdates). • Determine which mezzanine cards, HBAs, and interconnect modules are going to be used and where they will be installed in the enclosure. For installation and information on mapping server ports to interconnect bays, see the appropriate HP BladeSystem enclosure setup and installation guide on the HP website (http://www.hp.com/go/bladesystem/documentation). • Determine the Ethernet stacking cable layout and ensure that the proper cable and transceiver options are ordered. Stacking cables allow any Ethernet NIC from any server to be connected to any of the Ethernet networks defined for the enclosure. o For information on cable layout, see "Recommended stacking connections (on page 43)." o For information on supported cable and transceiver options, see the Virtual Connect module QuickSpecs on the HP website (http://www.hp.com). • Determine which Ethernet networks will be connected to or contained within the enclosure. Most installations will have multiple Ethernet networks, each typically mapped to a specific IP subnet. The HP Virtual Connect Manager enables definition of up to 64 different Ethernet networks that can be used to provide network connectivity to server blades. Each physical NIC on a server blade can be connected to any one of these Ethernet networks. Virtual Connect Ethernet networks can be completely contained within the enclosure for server-to- server communication or connected to external networks through rear panel ports (uplinks). For each network, the administrator must use the Virtual Connect Manager to identify the network by name and to define any external port connections. • Determine which Fibre Channel fabrics will be connected to the enclosure. Each uplink has a capability of aggregating up to 16 server HBA N-port links into an N-port uplink through the use of NPIV. • Coordinate with data center personnel to ensure Ethernet network cable connections and Fibre Channel cable connections to the enclosure are installed or scheduled to be installed. • Determine the Ethernet MAC address range to be used for the servers within the enclosure.

Setup 9

Server and networking administrators should fully understand the selection and use of MAC address ranges before configuring the enclosure. For additional information, see "MAC address settings (on page 76)." • Determine the FC World Wide Name (WWN) range to be used for servers within the enclosure. Server and storage administrators should fully understand the selection and use of WWN ranges before configuring the enclosure. For additional information, see "WWN settings (on page 86)." • Identify the administrators for the Virtual Connect environment and identify what roles and administrative privileges they will require. The Virtual Connect Manager classifies each operation as requiring server, network, domain, or storage privileges. A single user may have any combination of these privileges. For additional information, see "Domain Settings (Local Users) screen (on page 172)."

IMPORTANT: If you plan on using VC-assigned MAC addresses and WWNs and are also working with server software that will be licensed by MAC addresses or WWNs, assign server profiles before deploying an image through RDP or attaching a license.

Hardware setup overview The following steps provide an overview of setting up the interconnect modules: 1. Install and set up the enclosure. See the appropriate HP BladeSystem enclosure setup and installation guide on the HP website (http://www.hp.com/go/bladesystem/documentation). 2. Install the interconnect modules ("Installation" on page 31). 3. Install stacking links ("Recommended stacking connections" on page 43). 4. Connect Virtual Connect Ethernet module uplinks to data center networks. The network administrator should have already installed the network cables into the rack with the proper labels. See "Connecting Virtual Connect Ethernet module uplinks (on page 45)." 5. Connect data center FC fabric links (if applicable). 6. Note the default DNS name, user name, and password settings for the Virtual Connect Ethernet module in interconnect bay 1, available on the module Default Network Settings label. 7. Note the default DNS name, user name, and password for the HP Onboard Administrator, available on the module Default Network Settings label. See the HP BladeSystem Onboard Administrator User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation). 8. Apply power to the enclosures. See "Default module configuration (on page 11)." See also the appropriate HP BladeSystem enclosure setup and installation guide. 9. Use the HP Onboard Administrator for basic setup of the enclosures (including enclosure name and passwords). See the HP BladeSystem Onboard Administrator User Guide. 10. Be sure that all Virtual Connect interconnect module management interfaces and server blade iLO interfaces have valid IP and gateway addresses using one of the following methods: o Run DHCP on the management network connected to the Onboard Administrator. o Configure the Onboard Administrator to set enclosure bay IP addresses. See "Virtual Connect and EBIPA (on page 35)." 11. Be sure that OA, iLO, server blade system ROM, Ethernet option ROM, and FC option ROM firmware are up-to-date. For additional information, see the HP Virtual Connect Release Notes and Compatibility Matrix or the HP website (http://www.hp.com/go/bladesystemupdates).

Setup 10

12. Access the HP Virtual Connect Manager using one of the following methods: o Use a web link from within the HP Onboard Administrator graphical user interface or use the dynamic DNS name from the Default Network Settings label. See "Accessing HP Virtual Connect Manager (on page 53)." o Access the Virtual Connect Manager CLI remotely through an SSH session. See the HP Virtual Connect Manager Command Line Interface User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation).

IMPORTANT: For proper management of enclosure devices there must be an Ethernet connection from the Onboard Administrator module to the external management network. For information on Onboard Administrator module cabling, see the HP BladeSystem Onboard Administrator User Guide.

Default module configuration When Virtual Connect modules are inserted into an enclosure that is not yet part of a Virtual Connect domain, the modules are configured to provide basic connectivity. After a Virtual Connect domain is defined for an enclosure, server blades within that enclosure are isolated from all external network and fabric connections until explicitly configured within the Virtual Connect Manager. The following describes the default module configuration prior to the creation of a Virtual Connect domain. When not part of a Virtual Connect domain, each Virtual Connect Ethernet module is configured so that all server ports connected to that module are connected to a single network, which is then connected to a single uplink. Additional ports on that module can be aggregated using LACP to provide greater bandwidth as long as they are connected to the same external switch. (For aggregation of links to an external switch, the external switch must support dynamic creation of link aggregation groups using the IEEE 802.3ad LACP.) All stacking links are disabled. This default configuration is to enable connectivity testing between server NICs and devices outside the enclosure prior to Virtual Connect domain configuration. Beginning with Virtual Connect Fibre Channel module firmware v1.20, when not part of a Virtual Connect domain, all of the VC-FC Module uplink ports are grouped into an uplink port group and dynamically distribute connectivity from all server blades across all available uplink ports.

Virtual Connect Manager setup overview The following steps provide an overview of setting up the HP Virtual Connect Manager: 1. Log in and run the domain setup wizard ("HP Virtual Connect Domain Setup Wizard" on page 64). a. Import the enclosure. b. Name the Virtual Connect domain. c. Set up local user accounts and privileges. 2. Run the network setup wizard ("HP Virtual Connect Network Setup Wizard" on page 75). a. Select a MAC address range to be used by server blade Ethernet NICs ("MAC Address Settings" on page 76). b. Confirm the stacking links provide the needed connectivity and redundancy. c. Set up the networks.

Setup 11

3. Run the Fibre Channel setup wizard ("HP Virtual Connect Fibre Channel Setup Wizard" on page 85). a. Select a WWN range to be used by server blade FC HBAs ("WWN settings" on page 86). b. Define the SAN fabrics. 4. Run the Server Profile wizard ("Virtual Connect Manager Server Profile Wizard" on page 91). a. Define a server profile template. b. Assign server profiles. c. Name server profiles. d. Create server profiles. After an enclosure is imported into a Virtual Connect domain, server blades that have not been assigned a server profile are isolated from all networks to ensure that only properly configured server blades are attached to data center networks. A server profile can be assigned and defined for each device bay so that the server blade can be powered on and connected to a deployment network. These profiles can then later be modified or replaced by another Server Profile ("Server Profiles screen" on page 158). A server profile can also be assigned to an empty bay to allow deployment at a later date.

Setup 12

Component identification

HP 1/10Gb VC-Enet Module components and LEDs HP 1/10Gb VC-Enet Module components

Item Description 1 Port X1 (10GBASE-CX4) 2 Port X2 (10GBASE-CX4) 3 USB 2.0 connector (covered) 4 Ports 1-8 (10/100/1000BASE-T) 5 Reset button (recessed) 6 Next button

Component identification 13

HP 1/10Gb VC-Enet Module LEDs

Item Description Status 1 Module locator (UID) Blue = Module ID is selected. Off = Module ID is not selected. 2 Module status Green = Normal operation Amber = Degraded condition Off = Module powered off 3 X1/X2 port status Green = Port is configured and operating (10GBASE-CX4) as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting HP 1/10Gb VC-Enet Modules. Blue = Port locator (PID) 4 X1/X2 link/port Green = Link activity Green flashing = Activity Off = No link 5 Port 1-8 port status Green = Port is configured and operating as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting HP 1/10Gb VC-Enet Modules. Blue = Port locator (PID) 6 Port 1-8 link/activity Green = 10/100 link Green flashing = 10/100 activity Off = No link

Component identification 14

Item Description Status 7 Port 1-8 link/activity Amber = 1000 link Amber flashing = 1000 activity Off = No link

HP 1/10Gb VC-Enet Module system maintenance switch

Switch Default Function 1 Off Off = Normal operation On = Restore factory default login and DNS information 2 Off Reserved 3 Off Reserved 4 Off Reserved

Component identification 15

HP 1/10Gb-F VC-Enet Module components and LEDs HP 1/10Gb-F VC-Enet Module components

Item Description 1 Port X1 (10GBASE-CX4) 2 Port X2 XFP connector* 3 Port X3 XFP connector* 4 Port S1 SFP connector** 5 Port S2 SFP connector** 6 USB 2.0 mini AB connector (covered) 7 Next button 8 Ports 1-4 (10/100/1000BASE-T) 9 Reset button (recessed)

* Supports 10GBASE-SR-XFP and 10GBASE-LR-XFP pluggable optical transceiver modules ** Supports 1000BASE-T-SFP and 1000BASE-SX-SFP pluggable optical transceiver modules

HP 1/10Gb-F VC-Enet Module LEDs

Item LED description Status 1 Module status Green = Normal operation Amber = Degraded condition Off = Power off 2 Module locator (UID) Blue = Module ID selected Off = Module ID not selected

Component identification 16

Item LED description Status 3 X1 port status Green = Port is configured and operating as (10GBASE-CX4) an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect modules. Blue = Port locator (PID) 4 X1 link/port activity Green = Link Green flashing = Activity Off = No link 5 Port X2/X3 status Green = Port is configured and operating as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect module. Blue = Port locator (PID) 6 Port X2/X3 activity Green = Link Green flashing = Activity Off = No link, unsupported or absent pluggable module 7 Port S1/S2 status Green = Port is configured and operating as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect module. Blue = Port locator (PID) 8 Port S1/S2 activity Green = Link Green flashing = Activity Off = No link, unsupported or absent pluggable module 9 Port 1-4 port status Green = Port is configured and operating as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect modules. Blue = Port locator (PID) 10 Port 1-4 link/activity Green = 10/100 link Green flashing = 10/100 activity Off = No link 11 Port 1-4 link/activity Amber = 1000 link Amber flashing = 1000 activity Off = No link

Component identification 17

HP 1/10Gb-F VC-Enet Module system maintenance switch

Switch Default Function 1 Off Off = Normal operation On = Restore factory default login and DNS information* 2 Off Reserved 3 Off Reserved 4 Off Reserved

*See "Resetting the Administrator password and DNS settings (on page 28)."

Component identification 18

HP Virtual Connect Flex-10 10Gb Ethernet Module components and LEDs HP Virtual Connect Flex-10 10Gb Ethernet Module components

Item Description 1 Port X1 (10GBASE-CX4), multiplexed with item 4 2 USB 2.0 mini AB connector (covered) 3 Next button 4 Port X1 SFP+ connector*, multiplexed with item 1 5 Port X2 SFP+ connector* 6 Port X3 SFP+ connector* 7 Port X4 SFP+ connector* 8 Port X5 SFP+ connector* 9 Port X6 SFP+ connector* 10 Port X7 SFP+ connector*, multiplexed with internal 10Gb interface cross-link 11 Port X8 SFP+ connector*, multiplexed with internal 10Gb interface cross-link 12 Reset button (recessed)

*Supports 1000BASE-T-SFP, 1000BASE-SX-SFP, 10GBASE-LR SFP+, 10GBASE-SR SFP+, and 10GBASE-LRM SFP+ pluggable transceiver modules

Component identification 19

HP Virtual Connect Flex-10 10Gb Ethernet Module LEDs

Item LED description Status 1 Module locator (UID) Blue = Module ID is selected. Off = Module ID is not selected. 2 Module status Green = Normal operation Amber = Degraded condition Amber flashing = Fault condition Off = Power off 3 X1 port status Green = Port is configured and operating as (10GBASE-CX4) an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect modules. Blue = Port locator (PID) Off = Unconfigured 4 X1 link/port activity Green = Link Green flashing = Activity Off = No link 5 X1-X6 link/port Green = 10G link activity Green flashing = 10G activity Amber = 1G link Amber flashing = 1G activity Off = No link

Component identification 20

Item LED description Status 6 X7/X8 link/port Green = 10G link activity Green flashing = 10G activity Amber = 1G link Amber flashing = 1G activity Off = No link 7 X7/X8 shared port Green = Port is active. activity Off = Port is inactive. 8 X7/X8 port status Green = Port is configured and operating as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect modules. Blue = Port locator (PID) Off = Unconfigured 9 X1/X6 port status Green = Port is configured and operating as an uplink port connected to a data center fabric. Amber = Port is operating as a stacking link interconnecting Virtual Connect modules. Blue = Port locator (PID) Off = Unconfigured 10 X1 shared port Green = Port is active. activity Off = Port is inactive.

Shared port operation Port X1 (10BASE-CX4) and Port X1 (SFP+) Port X1 (10BASE-CX4) is multiplexed with Port X1 (SFP+). Either the CX-4 port is active or the SFP+ port is active, but not both. The triangle LED underneath each port indicates which port is active. The SFP+ port always has precedence over the CX4 port. • If there is a module installed in the SFP+ port, the SFP+ port is the active port. o The LED under the SFP+ port is on. o The LED under the CX4 port is off. • If there is no module installed in the SFP+ port, the CX4 port is the active port. o The LED under the CX4 port is on. o The LED under the SFP+ port is off. Port X7 and port X8 • Port X7 (SFP+) and port X8 (SFP+) are each multiplexed with an internal 10Gb interface cross-link, which is provided on the enclosure midplane between two horizontally adjacent VC modules to establish stacking links. Either the port is active or the internal cross-link is active, but not both. The triangle LEDs underneath ports X7 and X8 indicate whether the SFP+ port is active or the internal

Component identification 21

cross-link is active. The SFP+ port always has precedence over the internal cross-link port. Port X7 is shared with internal cross-link 1, and Port X8 is shared with internal cross-link 2. • If there is a module installed in the SFP+ port, the SFP+ port is the active port. The LED under the SFP+ port is on. • If there is no module installed in the SFP+ port, and the port has not been configured as an uplink in a VC Ethernet network, then the corresponding internal cross-link is the active port. The LED under the SFP+ port is off. • If there is no module installed in the SFP+ port, and the port has been configured as an uplink in a VC Ethernet network, then the SFP+ port is the active port. The LED under the SFP+ port is on.

HP Virtual Connect Flex-10 10Gb Ethernet Module system maintenance switch

Switch Default Function 1 Off Off = Normal operation On = Restore factory default login and DNS information* 2 Off Reserved 3 Off Reserved 4 Off Reserved

*See "Resetting the Administrator password and DNS settings (on page 28)."

Component identification 22

HP 4Gb Fibre Channel Module components and LEDs HP 4Gb VC-FC Module components

Item Description 1 SFP 1/2/4 Gb port 1 2 SFP 1/2/4 Gb port 2 3 SFP 1/2/4 Gb port 3 4 SFP 1/2/4 Gb port 4 5 Reset button (recessed)

In the default configuration (before a Virtual Connect domain is created), all 1/2/4 Gb capable uplink ports are grouped into an uplink port group and dynamically distribute connectivity from all 16 server blades.

Component identification 23

HP 4Gb VC-FC Module LEDs

Item LED description Status 1 Module locator Blue = Module ID selected (UID) Off = Module ID not selected 2 Module status Green = Normal operation Amber = Degraded condition Off = Power off 3 Port Green = Port is configured as the uplink for one or more server HBAs. Blue = Port is selected. 4 Logged in Green = Logged in to an external Fibre Channel switch port Green flashing = Port logging into the fabric, port disabled, or port failed POST at startup Off = Port down, offline, no sync, or error 5 Activity Green flashing (variable) = Link activity Green flashing (1 Hz) = External fabric switch does not support NPIV Off = No activity

Component identification 24

HP 4Gb VC-FC Module system maintenance switch

Switch Default Function 1 Off Reserved 2 Off Reserved 3 Off Reserved 4 Off Reserved

When part of a Virtual Connect domain, Virtual Connect Manager overrides any system maintenance switch settings.

Component identification 25

HP Virtual Connect 4Gb FC Module (with enhanced NPIV) components and LEDs HP Virtual Connect 4Gb FC Module components

Item Description Device bays supported in default configuration 1 1/2/4 Gb capable SFP connectors 1-16 (c7000) 1-8 (c3000) 2 Reset button (recessed) —

In the default configuration (before a Virtual Connect domain is created), all 1/2/4 Gb capable uplink ports are grouped into an Uplink Port Group and dynamically distribute connectivity from all server blades.

Component identification 26

HP Virtual Connect 4Gb FC Module LEDs

Item LED description Status 1 Module locator Blue = Module ID selected (UID) Off = Module ID not selected 2 Module status Green = Normal operation Amber = Degraded condition Off = Power off 3 Port Green = Port is configured as the uplink for one or more server HBAs. Amber = Port is not configured. Blue = Port is selected. 4 Logged in Green = Logged in to an external Fibre Channel switch port Off = Port down, offline, no sync, or error 5 Activity Green flashing (variable) = Link activity Green flashing (1 Hz) = External fabric switch does not support NPIV. Off = No activity

Component identification 27

HP Virtual Connect 4Gb FC Module system maintenance switch

Switch Default Function 1 Off Reserved 2 Off Reserved 3 Off Reserved 4 Off Reserved

When part of a Virtual Connect domain, Virtual Connect Manager overrides any system maintenance switch settings.

Resetting the Administrator password and DNS settings If the system maintenance switch 1 is in the ON position on a VC-Enet module, the firmware restores the Administrator account password and DNS settings to the original factory defaults as found on the module label (without disturbing any other local user accounts), and also displays the password on the VC-Enet module management console. For information on accessing the VC-Enet module management console, see the OA user guide. The default password is no longer displayed after switch 1 is in the OFF position. Password restoration is done during each power-up sequence while switch 1 is in the ON position (and reserved switches are in the OFF position) and does not allow changes until the switch is placed back into the OFF position. For switch locations, see the appropriate system maintenance switch ("HP 1/10Gb VC- Enet Module system maintenance switch" on page 15, "HP 1/10Gb-F VC-Enet Module system maintenance switch" on page 18, "HP Virtual Connect Flex-10 10Gb Ethernet Module system maintenance switch" on page 22). After switch 1 is returned to the OFF position, users with appropriate privileges can then change the Administrator password. Only reset the password on the module running the Virtual Connect Manager (and/or its backup), and not other modules in the domain.

Component identification 28

The recommended password recovery procedure is as follows: 1. Remove the Virtual Connect Ethernet module from interconnect bay 1. 2. Remove the access panel from the Virtual Connect Ethernet module. 3. Set switch 1 to the ON position. Ensure that all other switches remain in the OFF position. 4. Install the access panel. 5. Insert the Virtual Connect Ethernet module into bay 1 and allow the module to power up and reach a fully booted and operational state (approximately 1 minute). 6. Remove the Virtual Connect Ethernet module from interconnect bay 2. This causes interconnect bay 1 to become the module running the active VC Manager. Because switch 1 is set, the Administrator password remains at the factory default for interconnect bay 1 (not overwritten by the change of state because of the failover). 7. Wait to ensure that the VC Manager has had time to become active on interconnect bay 1. Log into the VC Manager to confirm it is up and functional on interconnect bay 1. 8. Insert the Virtual Connect Ethernet module into interconnect bay 2 and allow the module to power on and reach a fully booted and operational state (approximately 1 minute). 9. Remove the Virtual Connect Ethernet module from interconnect bay 1. 10. Remove the access panel from the Virtual Connect Ethernet module. 11. Set switch 1 to the OFF position. Ensure that all other switches remain in the OFF position. 12. Install the access panel. 13. Insert the Virtual Connect Ethernet module into interconnect bay 1 and allow the module to power up and reach a fully booted and operation state (approximately 1 minute). 14. Log into the VC Manager using the factory default user name and password to log in to the module (regardless of whether it is running on the module in interconnect bay 1 or interconnect bay 2). 15. Change the Administrator password.

Warning messages When a warning icon appears in the banner at the top of a page, mouse over the icon to view important information. Warning message: VC-Enet Module DIP switches are not configured for normal operation. Additional information: Set the switches to the recommended configuration. See the appropriate system maintenance switch. Warning message: Administrator password reset switch is set. Additional information: Set the switches to the recommended configuration. See the appropriate system maintenance switch. Warning message: Port monitoring is enabled. Additional information: Port monitoring is configured and enabled within this Virtual Connect domain. Ethernet data from the monitored ports is replicated on the network analyzer port, which poses a security risk and could result in network loops if not connected properly. To disable or reconfigure port monitoring, see "Ethernet Settings (Port Monitoring) screen (on page 111)." Warning message: A firmware update is in progress.

Component identification 29

Additional information: See "Domain Settings (Firmware Management) screen (on page 170)."

Component identification 30

Installation

Supported configurations Versions 1.10 and higher of the Virtual Connect firmware support up to eight Virtual Connect Ethernet modules in a single c7000 enclosure, and up to four Virtual Connect Fibre Channel modules in a single c7000 enclosure. In addition, versions 1.20 and higher of the Virtual Connect firmware support up to four Virtual Connect Ethernet modules in a single c3000 enclosure, and up to two Virtual Connect Fibre Channel modules in a single c3000 enclosure. The following configuration guidelines help identify supported configurations: • In all Virtual Connect configurations, a Virtual Connect Ethernet module must be installed in interconnect bay 1. The embedded Virtual Connect Manager typically runs on this module. • To support high availability of the Virtual Connect environment, HP recommends that Virtual Connect Ethernet modules be used in interconnect bays 1 and 2. The embedded Virtual Connect Manager will run in an active/standby configuration. See "Failover and check-pointing (on page 50)." • Virtual Connect Ethernet modules are typically used in pairs to provide access to all Ethernet controllers on the server blade. • The specific interconnect bays with Ethernet connectivity, other than bay 1 and 2, depend on mezzanine card locations within the server blade. • If a Virtual Connect Ethernet module is installed in an interconnect bay, the only module that can be installed in the horizontally adjacent bay is another Virtual Connect Ethernet module of the same type. • If an HP VC-FC module is installed in an interconnect bay, the only module that can be installed in the horizontally adjacent bay is another VC-FC module. • For c3000 enclosures, when two Fibre Channel mezzanine cards are installed in slots 2 and 3 of a full-height server blade, the VC Manager only creates Fibre Channel connections and assigns WWNs to the ports associated with the Fibre Channel mezzanine card in slot 2. This restriction does not apply for c7000 enclosures.

IMPORTANT: To support high availability, always install Virtual Connect Ethernet modules in interconnect bays 1 and 2.

HP BladeSystem c7000 Enclosure supported configurations The following tables show a number of typical, supported configurations for an HP BladeSystem c7000 Enclosure.

[Bay 1] VC Ethernet [Bay 2] Empty [Bay 3] Other/empty [Bay 4] Other/empty [Bay 5] Other/empty [Bay 6] Other/empty [Bay 7] Other/empty [Bay 8] Other/empty

Installation 31

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] Other/empty [Bay 4] Other/empty [Bay 5] Other/empty [Bay 6] Other/empty [Bay 7] Other/empty [Bay 8] Other/empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC Ethernet [Bay 4] VC Ethernet [Bay 5] Other/empty [Bay 6] Other/empty [Bay 7] Other/empty [Bay 8] Other/empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] Other/empty [Bay 4] Other/empty [Bay 5] VC Ethernet [Bay 6] VC Ethernet [Bay 7] Empty [Bay 8] Empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC Ethernet [Bay 4] VC Ethernet [Bay 5] VC Ethernet [Bay 6] VC Ethernet [Bay 7] Empty [Bay 8] Empty

[Bay 1] VC Ethernet [Bay 2] Empty [Bay 3] VC-FC [Bay 4] Empty [Bay 5] Other/empty [Bay 6] Other/empty [Bay 7] Other/empty [Bay 8] Other/empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC-FC [Bay 4] VC-FC [Bay 5] Other/empty [Bay 6] Other/empty [Bay 7] Other/empty [Bay 8] Other/empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC Ethernet [Bay 4] VC Ethernet [Bay 5] VC-FC [Bay 6] VC-FC [Bay 7] Empty [Bay 8] Empty

[Bay 1] VC Ethernet * [Bay 2] VC Ethernet [Bay 3] VC Ethernet [Bay 4] VC Ethernet [Bay 5] VC-FC [Bay 6] VC-FC [Bay 7] VC-FC [Bay 8] VC-FC * This configuration is only applicable for enclosures with full-height servers.

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC-FC [Bay 4] VC-FC [Bay 5] VC Ethernet [Bay 6] VC Ethernet

Installation 32

[Bay 7] Empty [Bay 8] Empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC-FC [Bay 4] VC-FC [Bay 5] VC Ethernet [Bay 6] VC Ethernet [Bay 7] VC Ethernet [Bay 8] VC Ethernet

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] Other/empty [Bay 4] Other/empty [Bay 5] VC-FC [Bay 6] VC-FC [Bay 7] Empty [Bay 8] Empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC-FC [Bay 4] VC-FC [Bay 5] VC-FC [Bay 6] VC-FC [Bay 7] Empty [Bay 8] Empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC Ethernet [Bay 4] VC Ethernet [Bay 5] VC Ethernet [Bay 6] VC Ethernet [Bay 7] VC Ethernet [Bay 8] VC Ethernet

HP BladeSystem c3000 Enclosure supported configurations The following tables show a number of typical, supported configurations for an HP BladeSystem c3000 Enclosure.

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] Empty [Bay 4] Empty

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC Ethernet [Bay 4] VC Ethernet

[Bay 1] VC Ethernet [Bay 2] VC Ethernet [Bay 3] VC-FC [Bay 4] VC-FC

Installation guidelines Observe the following guidelines: • To set up and configure Virtual Connect, interconnect bay 1 must be populated with a Virtual Connect Ethernet module. • To support failover configuration for Virtual Connect, install a second Virtual Connect Ethernet module in interconnect bay 2.

Installation 33

If the Virtual Connect Ethernet module installed in interconnect bay 1 is an HP Virtual Connect Flex- 10 10Gb Ethernet Module, then the Virtual Connect Ethernet module installed in interconnect bay 2 must also be an HP Virtual Connect Flex-10 10Gb Ethernet Module. • To avoid connectivity loss, do not install Virtual Connect and non-Virtual Connect modules in interconnect bays connected to the same server blade mezzanine card. • Do not mix Virtual Connect Ethernet modules and Virtual Connect Fibre Channel modules in interconnect bays connected to the same server blade mezzanine card because this action generates an enclosure electronic keying error. • For each Ethernet mezzanine port you want to manage with Virtual Connect Manager, install a Virtual Connect Ethernet module in the interconnect bay connected to that port. For more information, see the appropriate HP BladeSystem enclosure setup and installation guide. • Virtual Connect assigns or migrates MAC addresses for device bay ports connected to Virtual Connect Ethernet modules only. • When using stacking cables to connect multiple Virtual Connect Ethernet modules or using optional optical transceiver modules, order the cables separately. For more information, see the HP Virtual Connect QuickSpecs on the HP website (http://www.hp.com/go/bladesystem/interconnects). • For web browser compatibility with Virtual Connect Manager v1.20 or higher, use Microsoft® Internet Explorer 6.x or 7.x, or Mozilla Firefox 2.x or 3.x. For additional information, see the Virtual Connect Manager release notes on the HP website (http://www.hp.com/go/bladesystem/documentation). • For more information on BladeSystem port mapping, see the HP BladeSystem enclosure setup and installation guide that ships with the enclosure. • For the most current product information, see the release notes on the HP website (http://www.hp.com/go/bladesystem/documentation). • VC-FC module SFP ports can be connected only to Fibre Channel switch ports that support N_port_ID virtualization. To verify that NPIV support is provided, see the firmware documentation that ships with the Fibre Channel switch. • Install the VC-FC modules in interconnect bays 3 or higher. Interconnect bays 1 and 2 are reserved for Ethernet modules. • All modules in the enclosure require a valid and unique IP address, and all modules must be on the same subnet. Use a DHCP server or the Onboard Administrator EBIPA feature to assign each module an IP address.

NOTE: Virtual Connect assigns and migrates MAC addresses and/or WWNs for ports connected to Virtual Connect Ethernet modules or Virtual Connect Fibre Channel modules only.

For more information on the association between the server blade mezzanine connectors and the interconnect bays, see the HP BladeSystem enclosure setup and installation guide that ships with the enclosure. During server blade installation, the location of the mezzanine card determines the installation location of the interconnect modules. For specific interconnect module port connection information for each blade, see the HP BladeSystem enclosure setup and installation guide that ships with the enclosure. Connections differ by server blade type.

Installation 34

HP Virtual Connect Flex-10 Module guidelines The following guidelines apply to the installation or replacement of HP Virtual Connect Flex-10 10Gb Ethernet Modules: • Only install HP Virtual Connect Flex-10 Modules into bays horizontally adjacent to bays containing HP Virtual Connect Flex-10 Modules. If any other type of module is installed, the second one discovered is set to UNKNOWN and no connections are made to the server NICs attached to the interconnect bay. The module is set to UNKNOWN because it will be automatically removed from the VC domain when physically removed from the interconnect bay. • Replacing a HP Virtual Connect Flex-10 Module with any other type of Virtual Connect Ethernet module requires the module be administratively removed prior to replacement if the module is connected to a Flex-10 NIC that corresponds to an Ethernet connection in a server profile. For additional information, see "Administrative module removal (on page 210)." If the replacement module is not administratively removed, the module is marked as INCOMPATIBLE and no connections are made to the server NICs attached to the interconnect bay. • An empty interconnect bay horizontally adjacent to a bay containing an HP Virtual Connect Flex-10 Module is treated as if it has a Flex-10 compatible Ethernet module for server configuration. If the corresponding server NIC is Flex-10, it is partitioned according to the connections in the server profile. Adding a module that does not support Flex-10 when the corresponding server is configured for Flex-10 results in the module being set to INCOMPATIBLE.

Firmware requirements

IMPORTANT: For optimal operation of HP Virtual Connect, use the recommended firmware versions.

Always install the most current firmware for the following items: • Server blade system ROMs • Ethernet mezzanines • Fibre Channel mezzanines • HP BladeSystem Onboard Administrator • iLO HP recommends using the HP BladeSystem c-Class Virtual Connect Support Utility to install HP Virtual Connect module firmware. For the procedures, be sure to read the instructions on the web page and in the HP BladeSystem c-Class Virtual Connect Support Utility release notes. For additional information on required firmware versions and to download firmware upgrades, see the HP website (http://www.hp.com/go/bladesystemupdates).

Virtual Connect and EBIPA Enclosure Bay IP Addressing is used to specify IP addresses for the interconnect modules, which are then provided to the modules by the Onboard Administrator.

Installation 35

Because Virtual Connect communicates with other components through the Onboard Administrator, special considerations are required when using EBIPA with Virtual Connect Ethernet modules: • The Onboard Administrator must be on the same IP subnet as all Virtual Connect modules. • The Onboard Administrator IP address must be set properly before changing the IP addresses of the Virtual Connect modules.

Installing a VC-Enet module 1. Remove the interconnect blank.

NOTE: HP Virtual Connect works optimally in enclosures configured with HP Virtual Connect interconnect modules only.

2. Prepare the VC-Enet module for installation (HP 1/10Gb VC-Enet Module shown).

Installation 36

3. Install the module into the interconnect bay (HP 1/10Gb VC-Enet Module shown). Push the module in slowly and smoothly until firmly seated.

4. If the VC Manager configuration includes three or more VC-Enet modules, install stacking links (typically 10GBASE-CX4 cables) between the modules. For more information, see "Connecting Virtual Connect Ethernet Module uplinks (on page 45)." 5. Connect the data center network cables to the appropriate VC-Enet module faceplate ports. This step can be deferred until after setup of the Virtual Connect Manager software. See "Default module configuration (on page 11)." For VC-Enet Modules with fiber Ethernet ports (such as 1000BASE-SFP and 10GBASE-XFP), fiber ports can be used to connect to the data center if they are populated with a supported pluggable SFP, XFP, or SFP+ transceiver module. For HP Virtual Connect Flex-10 10Gb Ethernet Modules, the SFP+ ports can be used to connect to the data center if they are populated with a supported pluggable SFP or SFP+ transceiver module.

IMPORTANT: For proper thermal operation, always install SFP dust covers in SFP ports without SFP transceivers installed.

6. Remove the perforated portion of the Default Network Setting label that extends beyond the faceplate of the VC-Enet module installed in interconnect bay 1, or record the information contained on the label. The Default Network Settings label contains the DNS name, username, and password of the interconnect module in interconnect bay 1. This information is required for access to the HP Virtual Connect Manager. 7. Power on and configure the enclosure. See the appropriate HP BladeSystem enclosure setup and installation guide on the HP website (http://www.hp.com/go/bladesystem/documentation). 8. Connect a workstation to the data center network hosting the HP BladeSystem Onboard Administrator for the enclosure. 9. Start and log on to the workstation. 10. Open a compatible web browser.

Installation 37

11. Log on to the HP BladeSystem Onboard Administrator. For specific instructions, see the HP BladeSystem Onboard Administrator User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation). 12. Verify that the HP Onboard Administrator firmware is at revision 1.30 or higher. HP recommends using version 2.25 or higher. For specific instructions, see the HP BladeSystem Onboard Administrator User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation).

IMPORTANT: For proper Virtual Connect operation, always assign an IP address to each server blade iLO and interconnect module.

13. Be sure that the server blade BIOS and NIC options ROM are at the appropriate revision level. See the HP website (http://www.hp.com/go/bladesystemupdates). 14. Review the Onboard Administrator bay summary screens to verify that each server blade iLO and interconnect module has been assigned an IP address. Each IP address must be valid and unique, and all iLOs and Virtual Connect modules must be on the same subnet. For more information, see the HP BladeSystem Onboard Administrator User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation). 15. From the Onboard Administrator enclosure overview screen, click the Virtual Connect Manager link. The Virtual Connect Manager logon screen appears. 16. Enter the user name from the Default Network Settings label into the Username field. 17. Enter the password from the Default Network Settings label into the Password field, and then click Sign In. The HP Virtual Connect Manager Setup Wizard screen appears. 18. Use the VC Manager to administer the VC-Enet module for the enclosure. After an enclosure is imported into a Virtual Connect domain, server blades that have not been assigned a server profile are isolated from all networks to ensure that only properly configured servers are attached to data center networks. A pre-deployment server profile can be defined within the Virtual Connect Manager for each device bay so that the server blade can be powered on and connected to a deployment network. These profiles can then be modified at a later time or replaced by another server profile. See "Server Profiles screen (on page 158)."

Upgrading to an HP Virtual Connect Flex-10 Module Upgrading an enclosure to Flex-10 support requires several steps, depending on the starting configuration. Replacing a Virtual Connect Ethernet Module with an HP Virtual Connect Flex-10 Module in bays 3 to 8 1. Upgrade the VC domain firmware to v2.00. 2. Save the configuration. 3. If there are any Flex-10 NICs with profile connections that are connected to the interconnect bays being upgraded, the profile connections must be removed. This can be done by un-assigning the profile (recommended) or by deleting the connections from the profile. 4. Remove the existing non-Flex-10 modules from BOTH horizontally adjacent bays. 5. Administratively remove the modules ("Administrative module removal" on page 210). 6. Install the HP Virtual Connect Flex-10 Modules.

Installation 38

7. Re-assign the server profiles or add the connections to the profiles, depending on what was done in step 3. Replacing a Virtual Connect Ethernet Module with an HP Virtual Connect Flex-10 Module in bays 1 or 2 1. Upgrade the VC domain firmware to v2.00. 2. Save the configuration. 3. Upgrade any modules in bays 3 to 8 using the steps above. 4. Save the configuration. This is very important. 5. Remove the modules from bays 1 and 2. 6. Install the HP Virtual Connect Flex-10 Modules in bays 1 and 2. 7. Import the domain, and then select the option to restore the domain from a saved configuration file. Possible errors If the above steps are not followed exactly, the module might be set to the UNKNOWN or INCOMPATIBLE state depending on how the error state was reached. The module should be physically removed and administratively removed, if necessary. Then, the correct module type can be inserted. If the above steps have been followed and the server is not connecting properly to the network, power down the server, and then power it back up.

Installing a VC-FC module 1. Remove the interconnect blank.

NOTE: HP Virtual Connect works optimally in enclosures configured with HP Virtual Connect interconnect modules only.

Installation 39

2. Prepare the VC-FC module for installation (HP Virtual Connect 4Gb Fibre Channel Module shown).

3. Install the VC-FC module into the interconnect bay (HP Virtual Connect 4Gb Fibre Channel Module shown). Push the module in slowly and smoothly until firmly seated.

4. Connect the data center SAN switch ports to the VC-FC module 1/2/4 Gb SFP ports.

IMPORTANT: For proper thermal operation, always install SFP dust covers in SFP ports without SFP transceivers installed.

IMPORTANT: For proper Virtual Connect operation, always assign an IP address to each server blade iLO and interconnect module.

5. Review the Onboard Administrator bay summary screens to verify that each server blade iLO and interconnect module has been assigned an IP address. Each IP address must be valid and unique, and all iLOs and Virtual Connect modules must be on the same subnet. For more information, see the HP BladeSystem Onboard Administrator User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation).

Installation 40

6. Configure the VC-FC module: o If VC-Enet modules are installed in the same enclosure, use the Virtual Connect Manager to administer VC-FC modules. o If VC-Enet modules are not installed in the same enclosure, the VC-FC module operates in the default configuration only.

Factory default settings The Virtual Connect Delete Domain operation ("Deleting a domain" on page 167) returns all VC-FC modules to the factory default settings. VC-FC modules that are physically removed from a VC domain can be returned to the factory default settings when placed into a new enclosure by applying power, and then pressing and holding the reset button on the front panel for at least 10 seconds. When moved from a VC domain and placed into an enclosure not part of a VC domain, VC-FC modules retain assigned mappings until reset to the factory default.

Installing SFP/SFP+/XFP transceivers

WARNING: To avoid serious injury, never look directly into an open transceiver port.

CAUTION: Disconnect all cables before removing or installing an SFP/SFP+/XFP transceiver, because of the potential damage to the cables, the cable connector, or the optical interfaces in the transceiver. Removing and installing a transceiver can shorten the useful life. Do not remove and insert transceivers more often than is necessary.

CAUTION: Do not remove the dust plugs from the fiber-optic SFP/SFP+/XFP transceiver or the rubber plugs from the fiber-optic cable until you are ready to connect the cable. The plugs and caps protect the transceiver ports and cables from contamination and ambient light.

1. Remove the dust cap and save it for future use.

IMPORTANT: Use only SFP, SFP+, and XFP transceivers approved for this device.

2. Install the transceiver with the label side up. (SFP transceiver shown).

Installation 41

Ensure that the latch is closed and that the transceiver is fully seated.

3. Do one of the following: o Connect the appropriate cable. o Install the dust plug onto the transceiver.

Removing SFP/SFP+/XFP transceivers

WARNING: To avoid serious injury, never look directly into an open transceiver port.

1. Disconnect all cables. 2. Open the latch.

Installation 42

3. Remove the transceiver. (SFP transceiver shown).

4. Install dust plugs on the fiber-optic transceiver and rubber plugs on the fiber-optic cable.

CAUTION: Be sure to install the dust plugs on the fiber-optic transceiver and the rubber plugs on the fiber-optic cable. The plugs and caps protect the transceiver ports and cables from contamination and ambient light.

Recommended stacking connections Stacking links are used to interconnect Virtual Connect Ethernet modules when more than two Virtual Connect Ethernet modules are installed in a single enclosure. This feature enables all Ethernet network controllers on all servers in the Virtual Connect domain to have access to any Virtual Connect Ethernet module uplink port. By using these module-to-module links, a single pair of uplinks can function as the data center network connections for the entire Virtual Connect domain. Stacking enables any server NIC physically connected to a VC module to be connected to any Ethernet network. Each interconnect module has several numbered Ethernet connectors. All of these connectors can be used to connect to data center switches or they can be used to stack Virtual Connect modules and enclosures. Virtual Connect automatically detects when one Virtual Connect Ethernet module port is connected to another Virtual Connect Ethernet module port within the domain and turns the port ID indicator amber. All Virtual Connect Ethernet modules within the Virtual Connect Domain must be interconnected. Any combination of 1-Gb and 10-Gb cables can be used to interconnect the Virtual Connect Ethernet modules. However, the following illustration provides recommended configurations for two, four, six, or eight Virtual Connect Ethernet modules. A 10-Gb stacking link is already provided on the enclosure midplane for horizontally adjacent Virtual Connect Ethernet modules (bays 1 and 2, 3 and 4, 5 and 6, or 7 and 8 of the c7000 enclosure, or bays 1 and 2, or 3 and 4 of the c3000 enclosure).

NOTE: Port X0 is the 10Gb port connected through the midplane of horizontally-adjacent VC- Enet modules. Port X7 and x8 connect to the internal link between horizontally-adjacent Flex- 10 enabled VC-Enet modules. These ports appear in the list of stacking link connections within the user interface.

Installation 43

Virtual Connect Ethernet modules support 10GBASE-CX4 stacking cables 0.5 m to 7 m (1.64 ft to 23.00 ft). The 1000BASE-T links can also be used as stacking links of up to 100 m (328 ft). Ports with different connector types can be aggregated if the link speed is the same. For example, CX4 and SFP+ ports both running at 10G can be aggregated to provide enhanced throughput for the stacking link.

NOTE: The CX4 interface uses the same physical connector as Infiniband, but Infiniband cables are tuned differently and will not perform as well in CX4 applications. HP recommends purchasing CX4 cable assemblies that meet the IEEE CX4 specifications and support 10- Gigabit communication at distances from 3 m to 15 m (9.84 ft to 49.20 ft).

Fully redundant interconnection of Virtual Connect Ethernet modules is recommended. The recommended stacking configurations have redundant connections. If a stacking cable is lost, the Ethernet packets within the Virtual Connect domain are automatically re-routed to the uplink through the redundant path. This configuration also helps preserve network connectivity if an Ethernet interconnect module fails or is removed. Due to the reliability of the midplane connection between horizontally-adjacent Virtual Connect Ethernet modules, external stacking cables are not needed in configurations with two Virtual Connect Ethernet modules in interconnect bays 1 and 2.

Installation 44

Loop prevention When link is established on a Virtual Connect Ethernet module port, the port exchanges LLDP packets with the far-side connection. This LLDP protocol is an IEEE 802.1 standard that makes use of special BPDU packets that are not forwarded by Ethernet bridges or switches. As part of the LLDP exchange, Virtual Connect can determine whether a Virtual Connect Ethernet module port is connected to another port within the same Virtual Connect domain. If the port is connected, the port is designated as a stacking link and treated as such. If the port is not connected, then the port is available for use as an uplink port. Only ports that have not been designated as an uplink port in a network are eligible to become stacking links. If a port has been designated as an uplink port, and then is subsequently connected to another Virtual Connect Ethernet module, the port will not become a stacking link until it is removed from the network definition as an uplink port. To avoid network loops, Virtual Connect must first verify that only one active uplink exists per network from the Virtual Connect domain to the external Ethernet switching environment. Second, Virtual Connect must be sure that no network loops are created by the stacking links between Virtual Connect modules. • One active link—A VC uplink set can include multiple uplink ports. To prevent a loop with broadcast traffic coming in one uplink and going out another, only one uplink or uplink LAG is active at a time. The uplink or LAG with the greatest bandwidth should be selected as the active uplink. If the active uplink loses link, then the next best uplink will be made active. • No loops through stacking links—If multiple Virtual Connect Ethernet modules are used, they are interconnected via stacking links, which might appear as an opportunity for loops within the VC environment. For each individual network in the Virtual Connect environment, VC will block certain stacking links to ensure that each network has a loop-free topology. The loop avoidance feature can not be disabled or changed. However, the preferred uplink connection for a network can be identified when defining network uplinks.

Connecting Virtual Connect Ethernet module uplinks Each interconnect module has several numbered Ethernet connectors. All of these connectors can be used to connect to data center switches (uplink ports) or they can be used to stack Virtual Connect modules as part of a single Virtual Connect domain (stacking ports). See "Recommended stacking connections (on page 43)." Networks must be defined within the Virtual Connect Manager so that specific, named networks can be associated with specific external data center connections. See "Define Ethernet Network screen (on page 103)." These named networks can then be used to specify networking connectivity for individual servers. See "Ethernet Networks (Server Connections) screen (on page 109)." The following sections provide an overview of the types of external connections and their behaviors. Mapping individual networks to individual external uplink ports The simplest approach to connecting the defined networks to the data center is to map each network to a specific external uplink port. This uplink port is defined by the following: • Enclosure name • Interconnect bay containing the Virtual Connect Ethernet module

Installation 45

• Selected port on that module

Port status indicators can be used to locate a specific port or to provide additional status. Following is an example of simple network mapping, where the Virtual Connect enclosure is named Enclosure1 and Virtual Connect Ethernet modules are in interconnect module bays 1 and 2.

Network Uplink port Production_Network Enclosure1:Bay1:PortX2 Dev_Network Enclosure1:Bay1:Port4 Backup_Network Enclosure1:Bay2:Port3 iSCSI_Storage_Network Enclosure1:Bay2:PortX2

In this case, the Ethernet packets are passed unchanged between the server blades and the external networks. Any VLAN tags added by the server or external switch are ignored and pass through the Virtual Connect Ethernet modules. Mapping a single network to multiple uplinks (uplink port set) A single network can be mapped to more than one external uplink port to provide improved throughput and availability, referred to as an uplink port set. Review the following guidelines before mapping a single network to an uplink port set: • External uplink ports within an uplink port set can be on the same Virtual Connect Ethernet module or on multiple Virtual Connect Ethernet modules within the Virtual Connect domain. • Cables can be connected to one or more data center Ethernet switches. • When multiple external uplink ports are used for the same network, the Virtual Connect Ethernet modules provide automatic loop prevention by allowing for a single active link or link set at any one time. • The Virtual Connect system automatically chooses the uplink (ports) that optimize throughput and availability. Where possible, links within the uplink port set automatically form a link aggregation group using LACP. This action requires multiple uplink ports on a single Virtual Connect Ethernet module to be connected to an external switch that is capable and configured to form link aggregation groups using LACP.

Installation 46

Following is an example of a single network mapped to four external uplink ports.

Network Uplink port set Production_Network { Enclosure1:Bay1:Port1 Enclosure1:Bay1:Port2 Enclosure1:Bay2:Port1 Enclosure1:Bay2:Port2 }

In this example, the ports from Bay 1 could be connected to one external switch, and the ports on Bay 2 could be connected to a second switch. If the external switches support link aggregation, then this configuration would provide an active 2-Gb link to one switch and a standby 2-Gb link to the other. To make Virtual Connect Manager aware of individual network connections, see "Define Ethernet Network screen (on page 103)." Mapping multiple networks to a single, shared external uplink port The network administrator can choose to reduce the number of cables between the Virtual Connect enclosure and the data center switches by mapping multiple networks to a single, shared uplink port. In this case, a network is not just mapped to an uplink port, but to a VLAN on that port. This configuration requires VLAN tags to be added to each packet as it leaves the Virtual Connect domain and that packets entering the Virtual Connect domain be tagged (the VLAN tag is stripped from packets entering the Virtual Connect domain before they are routed to the appropriate server).

Following is an example of an uplink port being defined as a shared uplink port so that it can then be used as the external connection for multiple networks. Shared_Uplink_Port_A = Enclosure1:Bay1:PortX2

Network Shared uplink port and VLAN Production_Network Shared_Uplink_Port_A:VLAN_15 Dev_Network Shared_Uplink_Port_A:VLAN_21 Backup_Network Shared_Uplink_Port_A:VLAN_32 iSCSI_Storage_Network Shared_Uplink_Port_A:VLAN_76

Installation 47

Because appropriate VLAN tags are added as the packets leave the enclosure, this type of uplink should not be used in cases where VLAN tags are already added on the server itself. The system drops any Ethernet packets with server-inserted VLAN tags that are received on networks connected to shared uplink ports. Mapping multiple networks to a shared uplink port set It is also possible to map multiple VLAN-tagged networks to a set of shared uplink ports. The resulting shared uplink port set allows for the minimum number of cables while still providing for link aggregation and failover. In the following example, a shared uplink port set is first defined to provide aggregation and failover. Shared_Uplink_Set_A = {Enclosure1:Bay1:PortX2, Enclosure1:Bay2:PortX2}

Network Shared uplink port set and VLAN Production_Network Shared_Uplink_Set_A:VLAN_15

Dev_Network Shared_Uplink_Set_A:VLAN_21 Backup_Network Shared_Uplink_Set_A:VLAN_32 iSCSI_Storage_Network Shared_Uplink_Set_A:VLAN_76

In this example, all of the defined networks share a single active uplink port (such as Enclosure1:Bay1:PortX2) using VLAN tagging, while the second link in the shared uplink port set is available for failover. The shared uplink port set can also be constructed of multiple 1-Gb external ports.

NOTE: One network can be designated as a native VLAN, causing all untagged incoming Ethernet packets to be placed on this network. For additional information, see "Shared uplink sets and VLAN tagging (on page 120)."

To make Virtual Connect Manager aware of shared network connections, see "Define New Shared Uplink Set ("Define New Shared Uplink Set screen" on page 121)."

Configuration example using a Cisco Core switch There are several ways to implement a redundant Virtual Connect configuration. This example acts as a reference for anyone who is not familiar with switch configurations. This example is just one of several ways to connect an HP Virtual Connect to a Cisco Core switch. Connecting Virtual Connect to a Cisco Core/distribution switch using a shared uplink set and VLAN tagging done at the VC/data center boundary

Installation 48

In the example below LACP is used on the Cisco Switch to connect to a shared uplink set using three uplink ports. VLANs 10, 20, 30, and 40 from the network are tagged on the three shared uplink ports.

NOTE: Change Channel Mode to LACP on the Cisco switch.

By default, all ports on a Catalyst 4500/4000 switch and a Catalyst 6500/6000 switch use channel protocol PAgP and as such are not running LACP. For all ports concerned, you must change the channel mode to LACP. On switches running CatOS, you can only change channel mode per module. In the following example, channel mode for slots 1 and 2 are changed using the following command: set channelprotocol lacp module_number The changes can be verified by using the following command: show channelprotocol.

CatOSSwitch (enable) set channelprotocol lacp 1 Mod 1 is set to LACP protocol. CatOSSwitch (enable) set channelprotocol lacp 2 Mod 2 is set to LACP protocol. CatOSSwitch (enable) show channelprotocol Channel Module Protocol ------1 LACP 2 LACP 3 PAGP 5 PAGP On switches running Cisco IOS Software specify which interfaces should be using LACP by entering the following interface configuration command: channel-protocol lacp:

CiscoIOSSwitch(config-if)#channel-protocol lacp Example switch configuration of a Cat 6500 switch using IOS. (Ports 7/46, 7/47, and 7/48 on the Cat 6500 switch are used to uplink to the Virtual Connect module): interface Port-channel10

Installation 49

switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,20,30,40 switchport mode trunk no ip address

interface GigabitEthernet7/46 description test-VC switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,20,30,40 switchport mode trunk no ip address speed 1000 channel-protocol lacp channel-group 10 mode active ! interface GigabitEthernet7/47 description test-VC switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,20,30,40 switchport mode trunk no ip address speed 1000 channel-protocol lacp channel-group 10 mode active ! interface GigabitEthernet7/48 description test-VC switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,20,30,40 switchport mode trunk no ip address speed 1000 channel-protocol lacp channel-group 10 mode active

Failover and check-pointing Virtual Connect Manager runs as a high-availability pair when Virtual Connect Ethernet modules are installed in interconnect bay 1 and interconnect bay 2. The active VC Manager is usually on interconnect bay 1 at power up.

IMPORTANT: To support high availability, always install Virtual Connect Ethernet modules in interconnect bays 1 and 2.

If you are not using dynamic DNS, use the Onboard Administrator to access the Virtual Connect Ethernet module in bay 1. Then, you can optionally set a Virtual Connect Domain IP address so that you have a consistent IP address to access VC Manager whether it is running from bay 1 or from bay 2 because of a failover. Each time a configuration is changed, it is written to local flash memory and then check-pointed to the standby module. Configurations can also be backed up to a workstation using the GUI or Virtual Connect Support Utility.

Installation 50

NOTE: HP recommends saving a configuration after each session and before updating firmware.

Installation 51

HP Virtual Connect Manager

Configuring browser support Access to the application must be through HTTPS (HTTP exchanged over an SSL-encrypted session). For optimal viewing, HP recommends setting the screen resolution to 1280 x 1024. Requirements The HP Virtual Connect Manager Web interface requires an XSLT enabled browser with support for JavaScript 1.3 or equivalent. The following browsers are supported: • Microsoft® Internet Explorer 6.x or 7.x • Mozilla Firefox 2.x or 3.x If you received a notice that your browser does not have the required functionality, examine your browser settings to see if they meet the requirements below or contact your administrator. The following browser settings must be enabled before running the application: Javascript Client-side javascript is used extensively by this application. Check the browser settings to make sure javascript is enabled before running the application. ActiveX When using Microsoft® Internet Explorer with this application, ActiveX must be enabled. Check the browser settings to make sure ActiveX is enabled before running the application. Pop-up Windows Pop-up windows must be allowed for certain features to function correctly. Check the browser settings to make sure pop-up blockers are not enabled before running the application. Cookies Cookies must be enabled for certain features to function correctly. Check your browser settings to make sure cookies are enabled before running the application. If a notice is received that the browser does not have the required functionality, verify that the browser settings meet the preceding requirements.

Virtual Connect and RDP If you plan on using VC-assigned MAC addresses and WWNs and are also working with server software that will be licensed by MAC addresses or WWNs, assign server profiles before deploying an image through RDP or attaching the license.

HP Virtual Connect Manager 52

IMPORTANT: If you plan to use RDP for RedHat Linux installation and also plan to use User- or HP-defined MAC addresses, you must import the enclosure before running RDP.

Accessing HP Virtual Connect Manager Access to the Virtual Connect Manager is over the same Ethernet connection used to access the enclosure Onboard Administrator and server blade iLO connections. There are four ways to access HP Virtual Connect Manager: • If running dynamic DNS on the management network, locate the Default Network Settings label on the module in interconnect bay 1, and then type the DNS name into the address field of the web browser. If you are not running dynamic DNS, use the Onboard Administrator to access the Virtual Connect Manager. • Log on to the enclosure Onboard Administrator. From the enclosure overview screen, select the Virtual Connect Manager link from the left navigation window. The Onboard Administrator firmware must be version 2.25 or higher.

• Log on to the enclosure Onboard Administrator. Select Interconnect Bays in the left navigation window of the Onboard Administrator user interface to display the Interconnect Bays summary screen. Select the Management URL link for the Virtual Connect Ethernet module in bay 1. The Virtual Connect Manager typically runs on the Virtual Connect Ethernet module in bay 1 unless that module becomes unavailable, causing a failover to the Virtual Connect Manager running in bay 2. If you cannot connect to the Virtual Connect Manager in bay 1, try connecting to the management URL for bay 2. • Access the Virtual Connect Manager CLI remotely through an SSH session.

Command line overview The HP Virtual Connect Manager Command Line Interface can be used as an alternative method for managing the Virtual Connect Manager. Using the CLI can be useful in the following scenarios:

HP Virtual Connect Manager 53

• HP Management Applications (for example, Systems Insight Manager or Insight Control tools) can query the Virtual Connect Manager for information these tools need to present a complete management view of HP BladeSystem enclosures and devices. This interface is also used by the Management tools to execute provisioning and configuration tasks to devices within the enclosure. • Users can develop tools that utilize Virtual Connect Manager functions for data collection and for executing provisioning and configuration tasks. • When no browser is available or you prefer to use a command line interface, you can access management data and perform configuration tasks. For additional information, see the HP Virtual Connect Manager Command Line Interface User Guide on the HP website (http://www.hp.com/go/bladesystem/documentation).

Logging on to the HP Virtual Connect Manager GUI Log on using the user name (Administrator) and password from the Default Network Settings label for interconnect bay 1. If the default network settings have been changed and need to be restored, see "Resetting the Administrator password and DNS settings (on page 28)."

Possible causes for log on problems: • The information is not being entered correctly. Passwords are case-sensitive. • The account being entered is not an account for HP Virtual Connect Manager. • The account being entered has been deleted, disabled, or locked out.

HP Virtual Connect Manager 54

• The password for the account needs to be changed. • There is no connection to the Virtual Connect Ethernet module running the active Virtual Connect Manager. • The Virtual Connect Manager is in the middle of a failover or recovery. • The attempted IP sign-in address is not valid for the specified account. • The attempted IP sign-in address is for a Virtual Connect Ethernet module not running the active Virtual Connect Manager. • The browser settings are incorrect. See "Configuring browser support (on page 52)."

NOTE: Virtual Connect Manager supports only one user logged in at a time.

HP Virtual Connect Home This screen provides access for the management of enclosures, servers, networking, and storage.

About HP Virtual Connect Manager To view detailed product information, select About HP Virtual Connect Manager from the Help pull-down menu.

HP Virtual Connect Manager 55

Navigating the HP Virtual Connect Manager GUI Navigation overview The HP Virtual Connect Manager navigation system consists of a tree view on the left side of the page that lists all of the system devices and available actions. The tree view remains visible at all times. The right side of the page, which includes a pull-down menu at the top, displays details for the selected device or activity.

Menu item Links to Define Ethernet Network Define Ethernet Network screen (on page 103) Shared Uplink Set Define New Shared Uplink Set screen (on page 121) Server Profile Define Server Profile screen (on page 146) Configure Domain Settings Domain Settings (Domain Configuration) screen (on page 166) Ethernet Network Settings Ethernet Settings (MAC Addresses) screen (on page 110) Fibre Channel Settings Fibre Channel Settings (FC SAN Settings) screen (on page 137) Local User Accounts Domain Settings (Local Users) screen (on page 172) Firmware Update Domain Settings (Firmware Management) screen (on page 170) Certificate Administration Certificates/Authentications (SSL Certificate) screen (on page 189) Tools Hardware Overview Enclosures View (on page 61) Firmware Update Domain Settings (Firmware Management) screen (on page 170) Domain Setup Wizard Welcome screen for the Domain Setup Wizard ("HP Virtual Connect Domain Setup Wizard" on page 64) Network Setup Wizard Welcome screen for the Network Setup Wizard ("HP Virtual Connect Network Setup Wizard" on page 75) Fibre Channel Setup Wizard Welcome screen for the Fibre Channel Setup Wizard ("HP Virtual Connect Fibre Channel Setup Wizard" on page 85) Server Profile Wizard Welcome screen for the Server Profile Wizard ("Virtual Connect Manager Server Profile Wizard" on page 91)

HP Virtual Connect Manager 56

Menu item Links to Backup/Restore Domain Domain Settings (Backup/Restore) screen Configuration (on page 169) System Log System Log screen (on page 186) Export Support Information Support log ("Export support information" on page 63) Reset Virtual Connect Manager Reset Virtual Connect Manager screen ("Reset Virtual Connect Manager" on page 64) Help Table of contents VC Manager help file table of contents Index VC Manager help file index For This Page Help topic specific to the current page Virtual Connect Documentation on The Virtual Connect Documentation page hp.com on the HP website (http://www.hp.com/go/bladesystem/d ocumentation). About HP Virtual Connect Manager Specific information about this Virtual Connect domain.

Tree view The tree view aids in navigation for enclosure devices. The appearance of the tree view depends on several factors including user permissions, device availability, and device status. If a user account is configured without network, server, storage, or domain privileges, some options might not be visible in the tree view. The tree view provides category-based navigation for the major systems within the enclosure. When a category is expanded (by clicking the white plus sign in the blue box next to the category), all devices associated with that category are displayed.

HP Virtual Connect Manager 57

To select the device and open the device detail page, click the link for an individual device. Individual device pages contain detailed information about the selected device and any other functions related to that device.

Domain Status summary The Domain Status summary provides a count of Virtual Connect elements that are in an alert status other than OK. Virtual Connect elements summarized here include networks, shared uplink sets, server profiles, interconnect modules, and server blades.

HP Virtual Connect Manager 58

To view a summary of systems that have an alert icon displayed, click the Domain Status link. See "Domain Status screen (on page 60)."

HP Virtual Connect Manager 59

Domain Status screen This screen provides an overall domain status and a detailed summary of systems that currently have an alert status other than OK. To view detailed information about a device, click that device name in the list.

Additional information on the issue might be available as a tooltip for the severity icon. To see this information, mouse over the severity icon. For information on specific status error messages, see "Status error messages (on page 60)."

Status error messages There may be instances where modules with different versions of firmware are running in the same domain. For example, the installation of a new module either to replace a failed module or to add additional connections. This situation can result in an error message. VCM_OP_STATE_FW_INCOMPATIBLE_FAILOVER_CRITICAL Possible cause: The management application running on the active VC-Enet module has a database that is not compatible with the management application running on the backup VC-Enet module. Action: Immediately upgrade the firmware on the backup module to the same level as the active module. You can also downgrade the firmware on the active module, but this action results in a loss of configuration data. If you have a backup of the configuration that is compatible, you can recover the data by restoring from the saved configuration file. VCM_OP_STATE_FW_INCOMPATIBLE_FAILOVER_MAJOR

HP Virtual Connect Manager 60

Possible cause: The management application running on the active VC-Enet module is an earlier version than the backup VC-Enet module. If there is a failover to the backup module, the domain will lose its redundancy because the later firmware on the current backup will upgrade the configuration database and cause it to be unreadable by the earlier version. Action: Upgrade the backup module to the same firmware version as is running on the active module. You should also save the current configuration file immediately. Note that this state can also exist for a short time during firmware upgrade, so if you are currently upgrading the firmware in your domain, you can ignore this message. VCM_OP_STATE_FW_INCOMPATIBLE_LESS_CAPABLE Possible cause: The firmware running on this module is less capable than the firmware on the active VC- Enet module. Some features might not work properly. Action: Upgrade the firmware to the version running on the active module. VCM_OP_STATE_FW_INCOMPATIBLE_MISMATCH Possible cause: The firmware running on this module is different than the firmware on the active VC-Enet module. Action: Upgrade the firmware to the version running on the active module.

Enclosures View This graphical representation consists of an enclosure front view and rear view. To display a window with information about a particular device, mouse over that device in this graphical view. The Enclosures view provides status on each device in the enclosure and the option to select an individual device for more detailed information.

HP Virtual Connect Manager 61

To display the Enclosures View screen, click Hardware Overview in the left window.

Status icon definitions

Icon Status Description

Critical A device or system is indicating a potential outage. Incompatible A profile is incompatible with assigned hardware. / Mismatch

Missing A device or item is missing. Major A device or system is degraded. (orange) Minor A device or system is degraded.

(yellow)

Disabled A device or item is disabled. Warning A device is initializing or susceptible to outage. (blue)

Unknown Status of this item is unknown.

Normal Status of this line item is okay. Informational —

HP Virtual Connect Manager 62

Other icon definitions

Icon Description Click to edit the properties of this line item.

Click to delete this line item. Mouse over to view specific help for the associated field. The UID/PID of this line item is unlit.

The UID/PID for this line item is lit.

Click to copy the properties of this line item, to define a new profile. The server blade is powered on.

(green) The server blade is powered off.

(amber) Click to save the edit changes for this line item.

Click to exit edit mode for this line item.

Click to view a printable report of the onscreen summary. This icon is grayed out if no report function is available for that screen.

Edit mode. Onscreen device status is not updated while the screen has unsaved changes.

Export support information Virtual Connect Manager enables users to generate a support log, which can then be exported for technical support assistance. To generate a support log, select Export Support Information from the Tools pull-down menu. Allow several minutes for Virtual Connect Manager to collect all of the information. After the information is collected, you are prompted to save the information file locally. Following is a list of the support information that is collected: • System Log files • VC Manager trace files • Web Server Log file • VC Manager configuration files • VC-Enet module database content in XML format • VC-FC module database content in XML format • Ethernet switch status and configuration information • Operating system status information • Directory listings • Boot Loader environment variables

HP Virtual Connect Manager 63

Reset Virtual Connect Manager Users must have Administrative privileges to reset the Virtual Connect Manager. To reset the Virtual Connect Manager application running on the primary Virtual Connect Ethernet module, select Reset Virtual Connect Manager from the Tools pull-down menu. The Reset Virtual Connect Manager screen is displayed. • If the Force Failover checkbox is selected and a Virtual Connect Ethernet module is available in the alternate interconnect bay (interconnect Bays 1 and 2 can host the Virtual Connect Manager), the GUI counts down from 90 seconds. Then the GUI is redirected to the alternate Virtual Connect Ethernet module for login after the Virtual Connect Manager has restarted. • If the Force Failover checkbox is not selected or a Virtual Connect Ethernet module is not available in the alternate interconnect bay, the GUI counts down from 90 seconds, the Virtual Connect Manager restarts on the current Virtual Connect Ethernet Module, and the user is presented the login screen for the current Virtual Connect Ethernet module after the Virtual Connect Manager has restarted. When resetting the Virtual Connect Ethernet module, Virtual Connect Manager is temporarily unavailable to the user. If failover is specified and a standby Virtual Connect Ethernet module is available, users are logged off and must reconnect using the standby Virtual Connect Ethernet module IP address.

Running the setup wizards HP Virtual Connect Domain Setup Wizard A Virtual Connect domain consists of an enclosure and a set of associated modules and server blades that are managed together by a single instance of the Virtual Connect Manager. The Virtual Connect domain contains specified networks, server profiles, and user accounts that simplify the setup and administration of server connections. Establishing a Virtual Connect domain enables administrators to upgrade, replace, or move servers within their enclosures without changes being visible to the external LAN/SAN environments. Before getting started, perform the following tasks: • Verify that the HP Onboard Administrator is running the latest firmware (must be at least v2.25 or later). • Note the following information from the Default Network Settings label attached to the Virtual Connect Ethernet module in interconnect module bay 1: o DNS name o User name o Password • Connect any Ethernet module stacking cables ("Recommended stacking connections" on page 43). After logging in for the first time, the Virtual Connect Domain Setup Wizard appears. This wizard walks the user through the following tasks: • Importing the enclosure (creating the domain) • Naming the domain • Administrating local users

HP Virtual Connect Manager 64

If the wizard is cancelled before the enclosure is imported, the user is returned to the login screen. To restart the wizard, select Domain Setup Wizard from the Configure menu on the homepage.

Local Enclosure To communicate with other Virtual Connect modules and server blades, Virtual Connect Manager requires the login credentials for the local Onboard Administrator.

NOTE: An Onboard Administrator user name and password with full administrative privileges for the selected enclosure is required.

HP Virtual Connect Manager 65

Enter the user name and password for the enclosure Onboard Administrator. The local enclosure is automatically detected and selected. If an error is displayed, it indicates that an invalid Onboard Administrator user name and password, or one without sufficient privileges, might have been used.

Enclosure Import/Recovery After the Virtual Connect Manager has successfully established contact with the Onboard Administrator, you can create a Virtual Connect domain by importing the enclosure or by restoring a previously-created Virtual Connect domain from a saved configuration file. If you plan to use double density server blades, select the 'Allow the double density device bays' checkbox to display server device bays as double density slots. Actual installed hardware overrides this option.

CAUTION: This option cannot be modified. After the enclosure is imported, the only way to display server device bays as single density slots again is to delete the domain and create a new one.

For additional information, see "Using double-dense server blades (on page 68)." Select the appropriate method for creating the Virtual Connect domain. • To create the Virtual Connect domain by importing an enclosure, select the 'Create a new Virtual Connect domain' radio button, and then click Next. This process can take several minutes as the Virtual Connect Manager establishes contact with each module in the enclosure and identifies its capabilities.

HP Virtual Connect Manager 66

• To create a domain using an existing configuration file, select the 'Restore a Virtual Connect domain using an externally-saved configuration file' radio button, and then click Next.

HP Virtual Connect Manager 67

Enclosure Import After making the selection to create a new Virtual Connect domain by importing the enclosure on the Enclosure Import/Recovery screen, the Import Status screen appears and provides information about whether the import was successful. If the import is not successful, error information is displayed.

Using double-dense server blades Beginning with version 1.31, Virtual Connect Manager supports the use of double density server blades, which means support for up to 32 device bays in a single c7000 enclosure. This support also provides 32 new device bays (1A-16A and 1B-16B) for profile assignment. On a c3000 enclosure, this feature supports 8 additional or 16 total device bays. (1A-8A and 1B-8B.) The two physical servers A and B in a double density server blade correspond to the left and the right sides of the device bay in c7000 enclosures, or the top and bottom of the device bay in c3000 enclosures. Servers A and B have independent iLO, power, presence, and status capabilities. In c7000 enclosures, Bays 1A-16A are associated with the left sides of the double density server blades seated in the half-height bays 1-16. Bays 1B-16B are associated with the right sides of the double density server blades seated in the half-height bays 1-16. In c3000 enclosures, Bays 1A-8A are associated with the top of the double-dense server blades seated in the half-height bays 1-8. Bays 1B-8B are associated with the bottom of the double-dense server blades seated in the half-height bays 1-8.

Enclosure recovery If restoring a Virtual Connect domain using an externally saved configuration file, click Browse and locate the saved configuration file. If the configuration file was originally created on an enclosure with a different serial number, the checkbox must be selected to allow it to be used in a new enclosure. Click

HP Virtual Connect Manager 68

Next to continue restoring the enclosure. At the end of the restoration, the browser returns to the login screen. After the domain is restored, one of the local user accounts from the original Virtual Connect domain must be used to login.

General Settings The Virtual Connect domain name must be unique within the data center, and can be up to 64 characters without spaces or special characters.

HP Virtual Connect Manager 69

The Domain Setup Wizard automatically assigns a domain name (enclosurename_vc_domain). This name can be changed when running the setup wizard, or at anytime from the "Domain Settings (Domain Configuration) screen (on page 166)."

HP Virtual Connect Manager 70

Local Users

The first time this page appears, the only local user account is the Administrator account, which has domain privileges. The Administrator account cannot be deleted or have domain privileges removed. The Administrator password can be changed. The default Administrator password is identified on the Default Network Settings label on the VC-Enet module in bay 1 of the enclosure. To reset the Administrator password to the factory default, see "Resetting the Administrator password and DNS settings (on page 28)." The following tasks can be performed on this screen: • To create a new local user account, click Add User. The User Settings screen is displayed. • To edit attributes of a defined local account, select the user name from this screen. • To delete a user account, click the Delete icon for that line item.

HP Virtual Connect Manager 71

• To enable strong passwords or enable local users, click Advanced.

To enable the use of strong passwords, select the 'Require Strong Passwords' checkbox. Use the up and down arrows to select a password length between 3 and 40 characters. With strong passwords enabled, passwords must also contain at least one character from three of the following four categories: • Upper-case character • Lower-case character • Numeric character • Non-alphanumeric character To enable local users, select the 'Enable Local Users' checkbox. To disable local users, deselect the 'Enable Local Users' checkbox. If you disable local users before properly setting up both directory services groups and directory services, you cannot log in to the Virtual Connect Manager.

HP Virtual Connect Manager 72

User Settings

Observe the following user settings guidelines: • Username is a required field. • Username must contain an alpha-numeric value with 1 to 13 characters. • Password must contain an alpha-numeric value with 3 to 40 characters. • If strong passwords are enabled, the password must contain the administrator-designated number of characters, and at least one character from three of the following four categories: o Upper-case character o Lower-case character o Numeric character o Non-alphanumeric character Up to 32 local user accounts can be created. Each account can be set up to have a combination of up to four access privileges: • Domain o Define local user accounts, set passwords, define roles o Import enclosures o Name the VC domain o Set the domain IP address o Update firmware

HP Virtual Connect Manager 73

o Administer SSL certificates o Delete the VC domain o Save configuration to disk o Restore the configuration from a backup • Networking o Configure network default settings o Select the MAC address range to be used by the VC domain o Create, delete, and edit networks o Create, delete, and edit shared uplink sets • Server o Create, delete, and edit server Virtual Connect profiles o Assign and unassign profiles to device bays o Select and use available networks o Power on and off server blades within the enclosure • Storage o Select the WWNs to be used by the domain o Setup the connections to the external FC Fabrics It is possible to create a user with no privileges. This user can only view status and settings.

NOTE: The vcmuser_ account is an internal Onboard Administrator account created and used by Virtual Connect Manager to communicate with the Onboard Administrator. This account can show up in the Onboard Administrator system log. This account cannot be changed or deleted.

Finish domain wizard Click Finish to complete this wizard, and then run the Network Setup Wizard ("HP Virtual Connect Network Setup Wizard" on page 75) to define the Ethernet networks that will be available within the Virtual Connect domain.

HP Virtual Connect Manager 74

Deselect the Start the Network Setup Wizard checkbox, and then click Finish to go to the Home page.

HP Virtual Connect Network Setup Wizard This wizard establishes external Ethernet network connectivity for the HP BladeSystem c-Class enclosure using HP Virtual Connect. A user account with network privileges is required to perform these operations. Use this wizard to do the following: • Identify the MAC addresses to be used on the servers deployed within this Virtual Connect domain. • Choose the method of handling VLAN tagged packets from servers. • Setup connections from the HP c-Class enclosure to the external Ethernet networks. These connections can be uplinks dedicated to a specific Ethernet network or shared uplinks that carry multiple Ethernet networks with the use of VLAN tags. Be sure to connect any Ethernet module stacking cables before running the setup wizard.

HP Virtual Connect Manager 75

To initiate this wizard, click the Network Setup Wizard link on the homepage, or select Network Setup Wizard from the Tools pull-down menu.

MAC Address Settings At this point in the wizard, you are asked to select the type of Ethernet MAC addresses to be used on the server blades within the enclosure. Choose either the server factory default Ethernet MAC address that came with the server or the Ethernet MAC addresses assigned by Virtual Connect. Be sure to fully understand the following information before making this selection.

IMPORTANT: Configuring Virtual Connect to assign server blade MAC addresses requires careful planning to ensure that the configured range of MAC addresses is used once within the environment. Duplicate MAC addresses on an Ethernet network can result in a server network outage.

Each server blade Ethernet NIC ships with a factory default MAC address. The MAC address is a 48-bit number that uniquely identifies the Ethernet interface to other devices on the network. While the hardware ships with default MAC addresses, Virtual Connect has the ability to assign MAC addresses that will override the factory default MAC addresses while the server remains in that Virtual Connect enclosure. When configured to assign MAC addresses, Virtual Connect securely manages the MAC addresses by accessing the physical NICs through the enclosure Onboard Administrator and the iLO interfaces on the individual server blades. Always establish control processes to ensure that a unique MAC address range is used in each Virtual Connect domain in the environment. Reusing address ranges could result in server network outages caused by multiple servers having the same MAC addresses.

HP Virtual Connect Manager 76

If using Virtual Connect assigned MAC addresses, the following notes apply: • Virtual Connect automatically reserves both a primary address and an iSCSI MAC address for use by multifunction gigabit server adapters, such as the HP NC373m PCI Express Dual Port Multifunction Gigabit server adapter. Only the primary MAC address is used by standard (not multifunction) Ethernet devices. • If a server blade is moved from a Virtual Connect managed enclosure to a non-Virtual Connect enclosure, the local MAC addresses on that server blade are automatically returned to the original factory defaults. If a server blade is removed from a bay within a Virtual Connect domain and installed in another bay in the same Virtual Connect domain or in a bay in a different domain, it is assigned the new set of addresses appropriate for that server location.

Assigned MAC addresses The MAC address range used by the Virtual connect domain must be unique within the environment. HP provides a set of pre-defined ranges that are for use by Virtual Connect Manager and will not conflict with server factory default MAC addresses. When using the HP-defined MAC address ranges, ensure that each range is used only once within the environment.

HP Virtual Connect Manager 77

Select the type and range of MAC address, and then click Next.

Selecting VC-assigned MAC address ranges When using VC-assigned MAC addresses, you can choose between using an HP pre-defined MAC address range or using a user-defined MAC address range. • HP pre-defined MAC address range (recommended). These pre-defined ranges are reserved and will never show up as factory default on any hardware. There are 64 ranges of 1024 unique addresses to choose from. Be sure to use each range only once within a data center. • User-defined MAC address range. To avoid potential conflict with other hardware MAC addresses in the environment, consider using a subrange of MAC addresses reserved by the IEEE for locally- administered MAC addresses. Ensure that the range does not conflict with any Ethernet device already deployed within the enterprise.

IMPORTANT: If you plan to use RDP for RedHat Linux installation and also plan to use User- or HP-defined MAC addresses, you must import the enclosure before running RDP.

Select the type and range of MAC address, and then click Next.

NOTE: After any server profiles are deployed using a selected MAC address range, that range cannot be changed until all server profiles are deleted.

Stacking Links Be sure to connect any Ethernet module stacking cables before running the setup wizard.

HP Virtual Connect Manager 78

IMPORTANT: For a Virtual Connect environment to operate properly, all Virtual Connect Ethernet modules within the Virtual Connect domain must be interconnected with stacking links. HP strongly recommends that redundancy be maintained in stacking links to ensure continued connectivity of servers to the external networks.

At this point in the wizard, the user can see if all stacking cables are properly installed so that all Virtual Connect Ethernet modules within the domain are interconnected: • Connection Status indicates whether all of the Virtual Connect Ethernet modules within the domain are interconnected with stacking cables and accessible. Lack of connection status to all Virtual Connect Ethernet modules results in a critical alert. o OK indicates that all modules are connected. o Failed indicates that one or more modules are not connected properly. Check the cable connections. • Redundancy Status indicates if all Virtual Connect Ethernet modules would remain fully interconnected if a module or external cable was removed or failed. Horizontally-adjacent modules are considered to have OK redundancy status because of the reliability of their internal link. o OK indicates redundant/reliable connections are in place. o Degraded indicates additional stacking cables should be connected to provide full redundancy. The table on this screen lists all of the Ethernet stacking links found within the Virtual Connect domain. Each row of the table identifies the link speed and the connections on both sides of the link, identified by the module and port number. Port X0 indicates the 10Gb port connected through the midplane of horizontally-adjacent VC-Enet modules. Port X7 and X8 connects to the internal link between horizontally-adjacent Flex-10 enabled VC-Enet modules. For additional information, see “Supported configurations (on page 31)” and “Recommended stacking connections (on page 43)."

NOTE: Virtual Connect does not support stacking for FC modules, so each VC-FC module requires uplink connections to the external FC SAN environment.

HP Virtual Connect Manager 79

Define Network Connection To begin, select one of the following external network connections: • Connection with uplink(s) dedicated to a single network ("Define Single Network" on page 82) This selection leads to the definition of a network within the Virtual Connect environment and identifies any module uplink ports used to connect to that network in the data center. Internal-only networks (without external uplinks) can also be defined. These single networks will pass through any VLAN tags added by the server or added externally. • Connection with uplink(s) carrying multiple networks (using VLAN tagging) ("Define Shared Uplink Port Set" on page 84) This choice leads to the definition of multiple networks within the Virtual Connect environment that all share a common set of module uplink ports. Network traffic from each of the networks within the Virtual Connect environment receives a VLAN tag as it exits on a shared uplink port. Virtual Connect uses the VLAN tag on incoming network traffic to place it on the appropriate internal network. Ethernet VLAN tags are added on egress and stripped on ingress. This type of network connection should not be used when VLAN tags are being inserted by the server.

HP Virtual Connect Manager 80

After each network is defined, the user has the option of defining additional networks or finishing the wizard. To determine the types of network connections to use, see "Connecting Virtual Connect Ethernet module uplinks (on page 45)."

HP Virtual Connect Manager 81

Define Single Network

To define a network: 1. Enter a name for the network that will be easily understood and recognized by the server administrators defining and deploying server profiles. The network name can be up to 64 characters in length (no spaces). 2. To enable Smart Link, select the box under Smart Link ("Smart Link" on page 102). 3. To designate as a private network, select the box under Private Network ("Private Networks" on page 102). 4. To enable VLAN tunneling, select the box under Enable VLAN Tunneling. This option is only available if the 'Tunnel VLAN Tags' radio button is selected on the Advanced Settings tab of the Ethernet Settings screen. See server VLAN tagging support restrictions and limitations. ("Restrictions and limitations" on page 118) 5. Select the specific Virtual Connect Ethernet module external uplink ports that will connect the network to the data center. The available external ports are listed in the multi-level Add Port drop-down menu. Each port is labeled as linked or not linked. This status refers to whether or not a current connection to an external switch exists. If the network is to be local to the servers within the VC domain (enclosure), then no uplinks need to be selected. For additional information, see "Define Ethernet Network screen (on page 103)."

HP Virtual Connect Manager 82

Advanced Network Settings These settings affect only newly created profiles. Changing these settings does not affect any assigned profiles. To set the speed, click the selection box, select a setting (100Mb to 10Gb), and then click OK. • Set a Custom value for the Preferred Link Connection Speed. This value is the default speed for server profile connections mapped to this network. The server administrator can override this setting on an individual profile connection. • Set a Custom value for the Maximum Link Connection Speed. This value is the maximum speed for server profile connections mapped to this network. The server administrator can override this setting on an individual profile connection. For additional information, see "Multiple Networks Link Speed Settings (on page 119)."

HP Virtual Connect Manager 83

Define Shared Uplink Port Set

To define multiple networks that share a common set of external uplink ports: 1. Enter an overall name for the set of shared uplinks (up to 64 characters, no spaces). 2. From the Add Port drop-down menu, select the external uplink ports that will carry these networks. 3. Click Add Network to define the name and VLAN identifier of each network to use these shared uplinks. For additional information, see "Shared uplink sets and VLAN tagging (on page 120)." a. To use native VLAN, select the box under Native. Only one VLAN can be designated as the native VLAN. b. To use Smart Link, select the box under Smart Link ("Smart Link" on page 102). c. To designate as a private network, select the box under Private Network ("Private Networks" on page 102). 4. Click Apply. For additional information, see "Define New Shared Uplink Set screen (on page 121)."

Finish network wizard When the Network Setup Wizard completes, external Fibre Channel connectivity can be configured (if applicable) or server profiles can be defined and associated with server blades. To establish external Fibre Channel connectivity: 1. Be sure the Start the Fibre Channel Wizard checkbox is selected.

HP Virtual Connect Manager 84

2. Click Finish. The Fibre Channel Wizard Welcome screen is displayed. To begin deploying server blades: 1. Be sure the Start Fibre Channel Wizard checkbox is not selected. 2. Click Finish. 3. Select Define Server Profile from the homepage. Additional network connections can be defined at any time by using one of the following methods: • Select the Define a Network link on the homepage. • Select the Define a Shared Uplink Set link on the homepage. • Select Ethernet Network from the Define pull-down menu.

HP Virtual Connect Fibre Channel Setup Wizard This wizard configures external Fibre Channel connectivity for the HP BladeSystem c-Class enclosure using HP Virtual Connect. A user account with storage privileges is required to perform these operations. Use this wizard to do the following: • Identify WWNs to be used on the server blades deployed within this Virtual Connect domain. • Create SAN fabrics.

HP Virtual Connect Manager 85

To initiate this wizard, click the Fibre Channel Wizard link on the homepage, or select Fibre Channel Setup Wizard from the Tools pull-down menu.

WWN settings At this point in the wizard, you are asked to select the type of FC WWNs to be used on the server blades within the enclosure. You can choose to use the server factory default WWNs that came with the FC HBA mezzanine card or to use FC WWNs assigned by Virtual Connect. Be sure to fully understand the following information before making this selection. Each server blade FC HBA mezzanine card ships with factory default port and node WWNs for each FC HBA port. Each WWN is a 64-bit number that uniquely identifies the FC HBA port/node to other devices on the network. While the hardware ships with default WWNs, Virtual Connect has the ability to assign WWNs that will override the factory default WWNs while the server remains in that Virtual Connect enclosure. When configured to assign WWNs, Virtual Connect securely manages the WWNs by accessing the physical FC HBA through the enclosure Onboard Administrator and the iLO interfaces on the individual server blades. When assigning WWNs to a FC HBA port, Virtual Connect will assign both a port WWN and a node WWN. Because the port WWN is typically used for configuring fabric zoning, it is the WWN displayed throughout the Virtual Connect user interface. The assigned node WWN is always the same as the port WWN incremented by one. Configuring Virtual Connect to assign WWNs in server blades maintains a consistent storage identity (WWN) even when the underlying server hardware is changed. This method allows server blades to be replaced without affecting the external Fibre Channel SAN administration.

HP Virtual Connect Manager 86

CAUTION: To avoid storage networking issues and potential loss of data associated with duplicate WWNs on a FC SAN fabric, plan carefully when allowing Virtual Connect to assign server blade WWNs so that the configured range of WWNs is used only once within the environment.

Assigned WWNs The WWN range used by the Virtual Connect domain must be unique within the environment. HP provides a set of pre-defined ranges that are reserved for use by Virtual Connect and do not conflict with server factory default WWNs. When using the HP-defined WWN ranges, be sure that each range is used only once within the environment.

HP Virtual Connect Manager 87

Select the type and range of WWNs, and then click Next.

Select SAN Fabric Type Select the type of SAN fabric to create: • Static—permanently maps the server connection to a specific uplink port. • Dynamic—load balances traffic based on the number of SAN logins on a port. This type of mapping provides failover and failback within the Virtual Connect fabric.

HP Virtual Connect Manager 88

For additional information on creating FC SAN fabrics, see "Storage overview (on page 129)."

Define SAN Fabric The following actions are available on this screen: • Name the fabric. • Select the uplink port speed. • Select the uplink port(s) to be used. Only uplinks on the same bay can be in the same SAN fabric.

HP Virtual Connect Manager 89

• When finished, click Apply.

Finish Fibre Channel wizard When the Fibre Channel Setup Wizard completes, server profiles can be defined and associated with server blades. To begin deploying server blades: 1. Be sure the Start the Server Profile Wizard checkbox is selected. 2. Click Finish. The Server Profile Wizard Welcome screen appears. The FC SAN configuration can be changed at any time by using one of the following methods: • Select the Fibre Channel Settings (WWN) link on the homepage.

HP Virtual Connect Manager 90

• Select Fibre Channel Settings from the Configure pull-down menu.

Virtual Connect Manager Server Profile Wizard This wizard enables you to setup and configure network/SAN connections for the server blades within the enclosure. Use the wizard to define a server profile template that identifies the server connectivity to use on server blades within the enclosure. Then use the template to create and apply server profiles to up to 16 server blades automatically. Once created, the individual server profiles can be edited independently. Before beginning the server profile wizard, do the following: • Complete the Network Setup Wizard. • Complete the Fibre Channel Setup Wizard (if applicable). • Be sure that any server blades to be configured using this wizard are powered off. This wizard walks you through the following tasks: • Designate serial numbers (logical) (optional) • Define a server profile template • Assign server profiles • Name server profiles

HP Virtual Connect Manager 91

• Create server profiles

Serial Numbers (Logical) Use this screen to assign serial numbers (logical) to server blades within the domain. By configuring Virtual Connect to assign serial numbers (logical), a server blade can present a single serial number to licensing software. This method avoids the need to re-install serial number sensitive software after a recovery. Configuring Virtual Connect to assign serial numbers (logical) requires planning to be sure that the configured range of serial numbers are used only once within your environment.

CAUTION: The use of Serial Number (Logical) Settings might prevent the proper operation of software designed to track servers by serial number or UUID. Do not enable this feature until you consider and understand the impact to the entire software environment in which the servers operate. This impact includes, but is not limited to, warranty service, asset tracking, server deployment, and software licensing.

HP Virtual Connect Manager 92

For additional information, see "Serial Number (Logical) Settings (on page 164)."

HP Virtual Connect Manager 93

Assigned Serial Numbers (Logical) Select the type and range of serial numbers (logical). Be sure that each range is used only once in your environment.

Define Server Profile Template Use this screen to create a new server profile definition, which defines and configures Ethernet and Fibre Channel connectivity for the server.

HP Virtual Connect Manager 94

For additional information, see "Define a Server Profile screen ("Define Server Profile screen" on page 146)" and "Advanced Profile Settings (on page 150)."

HP Virtual Connect Manager 95

Assign Server Profiles Server profiles are created from the defined template. When these server profiles are created, you can choose to automatically assign them to device bays or to leave the server profiles unassigned.

HP Virtual Connect Manager 96

Name Server Profiles The table displays the automatically-generated names that will be assigned to the new server profiles. You can edit the profile names before continuing. Be sure the names are unique and meaningful.

Create Server Profiles This screen provides confirmation of each profile that was created.

HP Virtual Connect Manager 97

If creation of a server profile failed, see "Server profile troubleshooting (on page 163)."

HP Virtual Connect Manager 98

Defined Server Profiles This screen provides an overview of the server profiles that have been created. For additional information, see "Server Profiles screen (on page 158)."

HP Virtual Connect Manager 99

Finish Server Profile Wizard The Server Profile Wizard is complete. Click Finish to display the Virtual Connect Manager homepage.

Verifying data center connections After completing the cabling between the HP BladeSystem c-Class enclosure and the data center networks, use the following techniques to verify that the network connections are operating properly: • Verify that all external connections are linked and operating at the right speed. • Review the Virtual Connect Manager Network status screens ("Verify network status using VC Manager" on page 101). • Use port IDs to verify network connections. • Configure a server and verify network connectivity.

Verify link and speed Verify that all external ports connected to the data center are linked and are operating at the appropriate speed. 1. Verify that all Virtual Connect Ethernet modules are powered on and functioning properly. The module status LED should be green for all modules connected and configured in Virtual Connect for data center use.

HP Virtual Connect Manager 100

If the LED is not green, use the HP Onboard Administrator user interface to diagnose the problem and verify that the module is powered on. 2. Verify that all Virtual Connect Fibre Channel modules are powered on and functioning properly. The module status LED should be green for all modules connected and configured in Virtual Connect for data center use. If the LED is not green, use the HP Onboard Administrator user interface to diagnose the problem and verify that the module is powered on. 3. Verify that the data center switches are powered on. 4. Verify that each external port is linked and operating at the appropriate speed using link/speed activity LEDs for that port. If ports are not linked, verify the cables being used are not defective, and verify that both ends of the link are configured for the same speed/duplex settings. Both sides of the configuration must match for the link to be established. For autonegotiation, both ports must be configured to run autonegotiation. To use a forced speed, (for example 100 Mb full-duplex), both ports must be configured to be the same forced speed. Mismatched configuration can result in ports not linking up, or not functioning properly. Note that Virtual Connect Ethernet modules do not support half-duplex operations. 5. Verify that the port status indicator (port number) of each configured external port is illuminated green (assuming no port IDs are turned on). This status indicates that the port is actively configured as part of an external connection.

Verify network status using VC Manager The HP Virtual Connect Manager provides many status and summary screens that can be used to verify that the networks were defined properly and mapped to the appropriate network. These summary screens can be used to print a report for review and reference. The most useful summary screen is the Ethernet Networks (External Connections) screen. To access this screen, click the Ethernet Networks link in the left VC Manager navigation window. The following actions are available from this screen: • Identify the external ports associated with each Ethernet network. • View the current port status (link, speed) of each external port. • View the current active/standby state of each external port. • Access information about attached switches (if the external switch supports LLDP). • Highlight the port IDs for all external ports associated with a specific network.

HP Virtual Connect Manager 101

Network management

Networks overview The Virtual Connect Ethernet module uses standard Ethernet bridge circuitry with special firmware so that it functions as a configurable Ethernet port aggregator. For a specific external data center connection, only the selected server Ethernet NIC ports are visible on what appears to be an isolated, private, loop- free network. The Virtual Connect Ethernet module uplinks do not participate in the data center Spanning Tree Protocol or other switch management protocols that could disrupt the data center network. The Virtual Connect Ethernet module uplinks support link aggregation, link layer discovery protocol (LLDP), and VLAN tagging. VLAN tagging enables uplinks to be shared to carry multiple networks. Virtual Connect allows users to identify an associated network as the native VLAN, causing all untagged incoming Ethernet packets to be placed onto the designated network. Only one associated network can be designated as the native VLAN. All outgoing Ethernet packets are VLAN tagged. Each network defined within Virtual Connect may have one or more uplinks. Virtual Connect independently ensures that no loops are created within the enclosure and that the resulting tree structure is optimized for the uplinks to the data center. When multiple uplinks are used on a network, HP Virtual Connect Manager first verifies if any of the ports can be collected together into an aggregation group (requires connections to go from a single Virtual Connect Ethernet module to a single data center switch), and then it picks a single link (or aggregation group) as the connection to the external network. The remaining connections are blocked and held as standby ports.

Smart Link Enabling Smart Link configures the network so that if all external links lose their link to external switches, Virtual Connect drops the Ethernet link on all local server blade Ethernet ports connected to that network. This feature can be useful when using certain server network teaming (bonding) configurations.

Private Networks The Private Networks option provides extra networking security. When checked, the network is configured so that all server ports connected to it cannot communicate with each other within the Virtual Connect domain. All packets from servers are sent through the VC domain and out the uplink ports only. Servers on the network can only communicate with each other through an external Layer 3 router that redirects the traffic back to the VC domain.

Network management 102

Define Ethernet Network screen The Define Ethernet Network screen is accessible to all users with network privileges from the Define a Network link on the Virtual Connect Manager homepage or the Define pull-down menu.

The following table describes the fields within the Define Ethernet Network screen.

Field name Description Network Network Name Name of the network Smart Link (on page 102) Select whether to enable (checked) or disable (unchecked) Smart Link Private Network ("Private Networks" on Select whether to designate (checked) or not designate (unchecked) this page 102) network as a private network Enable VLAN Tunneling ("Server VLAN Select whether to enable (checked) or disable (unchecked) VLAN Tagging Support" on page 117) Tunneling (this option is not available if VLAN mapping is enabled) External Uplink Ports Use Shared Uplink Set Enables selection or creation of a shared uplink set Port Network port locations (enclosure, bay, and port numbers) Port Role Applicable when Failover Connection Mode is selected. The port can be designated as Primary or Secondary. Port Status Displays the active link status and interface speed of the selected port Connector Type Displays the type of connector on the port, for example RJ-45

Network management 103

Field name Description Connected to If the port is connected to a switch that supports LLDP, the switch MAC address and switch port are displayed. A link is provided to obtain more information about the far-end switch port. PID When selected, sets/clears the port identifier color as blue on the HP 1/10Gb VC-Enet module to aid in the location of the specific uplink. The PID status for the overall network is also displayed. Speed/Duplex Pull-down menu to specify the speed and duplex (where applicable) of the uplink port. Half-duplex operations are not supported by the VC-Enet module. Delete Click to delete the line item.

The following table describes the available actions in the Define Ethernet Network Screen. Clicking another link in the pull-down menu or left-hand navigation window causes current edits that have not been applied to be lost.

Task Action Enable Smart Link on the network being Select the box under Smart Link. defined Designate the network as a private Select the box under Private Network. network Enable VLAN tunneling Select the box under Enable VLAN Tunneling. This option is only available if the 'Tunnel VLAN Tags' radio button is selected on the Advanced Settings tab of the Ethernet Settings screen. Set a custom value for preferred link Click Advanced. connection speed or maximum link connection speed Enable the selection or creation of a Select the box next to Use Shared Uplink set. shared uplink set Add an external uplink port to the Click the Add Port drop-down box, and then select an available port. network Change the uplink interface port speed Click the drop-down box under Speed/Duplex, and then select a or disable the port setting. Change the connection mode Click the down arrow in the box next to Connection Mode, and then select Auto or Failover. For a description of these modes, see "Defining a network (on page 104)." Delete an added port Click X in the Delete column for that port. Clear unsaved changes on the screen Click Clear. Save changes and remain on this Click Apply. screen Cancel without saving changes and Click Cancel. return to the summary screen

Defining a network To define a standalone network: 1. Enter a network name. The network name can be up to 64 characters in length (no spaces).

Network management 104

2. Select whether to enable (checked) or disable (unchecked) Smart Link (on page 102). 3. Select whether to designate (checked) or not designate (unchecked) this network as a private network ("Private Networks" on page 102). 4. Select whether to enable (checked) or disable (unchecked) VLAN tunneling ("Server VLAN Tagging Support" on page 117). This option is only available if the 'Tunnel VLAN Tags' radio button is selected on the Advanced Settings tab of the Ethernet Settings screen. 5. If the network is to be used only internal to the Virtual Connect domain or enclosure, go to step 7 (do not add any external ports). 6. Add one or more external port using the Add Port pull-down menu. Only available ports are listed and they will display the current port link status. Select two or more ports to ensure a high availability connection. 7. Select the Connection Mode: o Auto (recommended)—This mode enables the uplinks to attempt to form aggregation groups (using IEEE 802.3ad link aggregation control protocol) and to select the highest-performance uplink as the active path to external networks. Aggregation groups require multiple ports from a single Virtual Connect Ethernet module to be connected to a single external switch that supports automatic formation of LACP aggregation groups. Multiple aggregation groups may be formed from the ports selected for the network. The highest performing aggregation group is selected as active with other aggregation groups and individual links used as standby connections. o Failover—If this mode is selected, set the port to Primary or Secondary. Only a single link is used as the active link to the external networks with other ports used as standby connections. 8. Click Apply or OK. The network is now defined and available for use in creating server profiles. To define a network that uses an existing Shared Uplink Set, use the Define/Edit Shared Uplink Set screen or define the additional network as follows: 1. Enter the network name. 2. Select the Use Shared Uplink Set box. 3. Select an existing Network from the dropdown list or click the Create icon. If the Create icon is selected, the Define a Shared Uplink Set screen appears so that a new Shared Uplink Set can be created. 4. Enter an external VLAN ID. 5. Click Apply. To create an internal network, which connects one server to another, do not select a port. Enter the network name and then click Define Network.

NOTE: By default, Virtual Connect supports Jumbo Frames up to 9KB.

Ethernet Networks (External Connections) screen To access this screen, click the Ethernet Networks link in the left VC Manager navigation window, and then click the External Connections tab. To view a list of all defined Ethernet networks, click Ethernet Networks in the left window.

Network management 105

This summary screen displays the external connections for each network and is available to all authorized users.

The following table describes the columns within the summary table on the Ethernet Networks (External Connections) screen.

Column name Description

Ethernet Networks Shows the overall network status, network name, and PID state Shared Uplink Set (VLAN ID) Shows the name of the shared uplink set and its VLAN ID (if applicable) Port Status Shows whether each individual port associated with the network is linked or unlinked and the current link speed Connector Type Displays the type of connector on the port, for example, RJ-45 Connected to If the individual port is connected to a switch that supports LLDP, the switch MAC address and switch port are displayed. A link is provided to obtain more information about the far-end switch port. Uplink Port Lists the status of the individual port and the location of the individual port (enclosure, bay, port)

The following table describes the available actions in the Ethernet Networks (External Connections) screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Sort list view Click the down arrow next to the Show box to display All Networks, or one specific network. Edit a network Click on the name of the network in the table listing. Edit a shared uplink set Click on the name of the shared uplink set in the table listing.

Network management 106

Task Action

Define a new network Click Define Network. Illuminate the PID for all uplink ports Click on the circle next to the network in the list. associated with a network View a printable report Click View Printable Report.

Edit Ethernet Network screen Use this screen to edit the properties of an existing network or to delete a network. This screen has similar fields to the Define Ethernet Network screen (on page 103). This screen can only be edited by users with network privileges, but it is viewable by all authorized users.

The following table describes the fields within the Edit Network screen.

Field name Description Network Network Name Name of the network Smart Link Shows whether Smart Link is enabled (checked) or disabled (unchecked) Private Network Shows whether this network is designated (checked) or not designated (unchecked) as a private network Enable VLAN Tunneling Shows whether VLAN tunneling is enabled (checked) or disabled (unchecked)

Network management 107

Field name Description Status Displays the current status of the network PID PID status for the overall network State Displays the current state of the network (enabled or disabled) External Uplink Ports Use Shared Uplink Set Enables selection or creation of a shared uplink set Port Network port locations (enclosure, bay, and port numbers) Port Role Applicable when Failover Connection Mode is selected. The port can be designated as Primary or Secondary. Port Status Displays the current linked status of the selected port Connector Type Displays the type of connector on the port, for example, RJ-45 Connected to If the port is connected to a switch that supports LLDP, the switch MAC address and switch port number are displayed. A link is provided to obtain more information about the far-end switch port. PID When selected, this option sets/clears the port identifier color as blue on the HP 1/10Gb VC-Enet Module to aid in the location of the specific uplink. The PID status for the overall network is also displayed. Speed/Duplex Pull-down menu to specify the speed and duplex (where applicable) of the uplink port Delete Click to delete the line item.

The following table describes the available actions in the Edit Network Screen. Clicking another link in the pull-down menu or left-hand navigation window causes current edits that have not been applied to be lost.

Task Action Enable or disable Smart Link on the Select the box under Smart Link. network being defined Designate or do not designate the Select the box under Private Network. network as a private network Enable or disable VLAN tunneling Select the box under Enabled VLAN Tunneling. This option is only available if the 'Tunnel VLAN Tags' radio button is selected on the Advanced Settings tab of the Ethernet Settings screen. Enable or disable the network Click the drop-down box under State, and then select a setting. Set a custom value for preferred link Click Advanced. connection speed or maximum link connection speed Enable the selection or creation of a Select the checkbox next to Use Shared Uplink Set. shared uplink set Add an external uplink port to the Click the Add Port drop-down box, and then select an available port. network Change the uplink interface port speed Click the drop-down box under Speed/Duplex, and then select a or disable the port setting. Change the connection mode Click the down arrow in the box next to Connection Mode, and then select Auto or Failover. For a description of these modes, see "Defining a network (on page 104)." Delete an added port Click X in the Delete column for that port.

Network management 108

Task Action View updated information on the Click Refresh. network Delete the network Click Delete. Clear unsaved changes on the screen Click Clear. Save changes and remain on this Click Apply. screen Cancel without saving changes and Click Cancel. return to the summary screen

Ethernet Networks (Server Connections) screen This summary screen lists the server ports connected to each network in the Virtual Connect domain. This screen is viewable by all authorized users.

The following table describes the columns within the Ethernet Networks (Server Connections) screen.

Column name Description Ethernet Networks Shows the overall network status, network name, and PID state Port Shows the overall status of the individual server port as well as the port number within the server MAC Lists the MAC address for the server port Location Lists the enclosure and device bay for the server blade (when the profile is assigned to a device bay)

Network management 109

Column name Description Profile Shows the overall status of the associated server profile and the server profile name. Click the profile name to display the edit screen for the profile.

The following table describes the available actions in the Ethernet Networks (Server Connections) screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action Sort list view Click the down arrow next to the Show box to display All Networks, or one specific network. Edit a network Click on the name of the network in the table listing. Edit a server profile Click on the name of the profile in the table listing. Define a new network Click Define Network. Illuminate the PID for all uplink Click on the circle next to the network name in the list. ports associated with a network View a printable report Click the View Printable Report icon.

Ethernet Settings (MAC Addresses) screen To access this screen, click the Network Settings (MACs) link in the left VC Manager navigation window, or click Network Settings in the Network section of the Home page. This screen lists the MAC Address type and range that will be used when creating server profiles. This screen is the same as the MAC Addresses Settings screen used in the Network Setup Wizard ("HP Virtual Connect Network Setup Wizard" on page 75). The Type field identifies what MAC addresses will be assigned to server blades deployed within the Virtual Connect environment. HP provides a number of pre-defined MAC address ranges or you can choose to enter a range of locally-owned MAC addresses. HP does not recommend using the server factory default because these addresses do not move when the server profile is assigned to a new physical server blade. When using HP pre-defined or user-defined MAC address ranges, only use each range once within the domain to avoid multiple servers having the same MAC addresses. After MAC addresses have been assigned as part of creating a server profile, this setting cannot be changed. The screen can be changed only by users with network privileges. No changes in MAC address ranges are permitted after server profiles are created. You must delete all server profiles to change the MAC address range settings.

Network management 110

For additional information, see "MAC address settings (on page 76)."

Ethernet Settings (Port Monitoring) screen To access this screen, click Port Monitoring under Ethernet Settings in the left window, or on the Home Page, click Port Monitoring in the Network section. The port monitoring screen is accessible to all users with server and network administrator privileges. All other users have read-only access. Port monitoring enables a set of server ports to have their network traffic duplicated to an unused uplink port for purposes of monitoring and/or debugging network traffic on those server ports.

CAUTION: The network analyzer port should only be connected directly to a network analyzer. Improper connection of this port or improper configuration of port monitoring could result in network loops and cause a network outage.

Network management 111

Whenever port monitoring is enabled, a warning icon appears in the banner at the top of the page. If port monitoring is configured and enabled within the Virtual Connect domain, Ethernet data from the monitored ports is replicated on the network analyzer port, which poses a security risk and could result in network loops if not connected properly.

The following table describes the fields within the Ethernet Settings (Port Monitoring) screen.

Field name Description Port Monitoring State Used to enable or disable port monitoring. This feature allows the network administrator to disable port monitoring while maintaining the monitored port configuration. Network Analyzer Port This is the port to which all monitored traffic is directed. After selection, this port is no longer available for use in any other Virtual Connect Ethernet network. Port Identifies the enclosure, bay, and port number of the network analyzer port. Port Status Displays link status of the network analyzer port PID PID status icon (lit or unlit) for the network analyzer port Speed/Duplex Pull-down menu to specify the speed and duplex (where applicable) of the network analyzer port Detailed statistics Click the link to display detailed statistics about this port Delete Displays Delete icon. Click to remove the network analyzer port. To change the network analyzer port, the current port must first be deleted. Monitored Port List Displays up to 16 server ports that are monitored at the same time.

Network management 112

Field name Description Direction Direction of traffic on the port being monitored. Valid choices are From Server, To Server, or Both. The default is Both. Server Profile Identifies the server profile associated with the monitored port if one exists. Port Enclosure, bay, and port number of monitored port MAC MAC address of monitored port Server Bay Assignment Enclosure and server device bay the monitored port is associated with Network Network associated with the downlink port, if one exists Delete Displays Delete icon. Click to remove the port from the monitored list.

The following table describes the available actions in the Ethernet Settings (Port Monitoring) screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action Enable or disable port Click the drop-down box under Port Monitoring State. monitoring Select a mirror-to port Click the down arrow in the Add Port box. The current network analyzer port must be deleted before a new one can be selected. Change the Network Analyzer Click the drop-down box under Speed/Duplex, and then select a Port speed setting. Delete the Network Analyzer Click the Delete icon. Port View detailed statistics for the Click on the Detailed Statistics link. Network Analyzer Port Add a port to the monitored port Click Select Port.... A list of server ports is displayed with checkboxes to list select or deselect the monitored ports. Clear selections and settings Click Clear. without saving Apply new selections and Click Apply. settings Clear selections and settings Click Cancel. without saving and return to the Virtual Connect homepage

Network management 113

Select Monitored Ports screen The Select Monitored Ports screen is displayed when the Select Ports button is clicked on the Ethernet Settings (Port Monitoring) screen. You can select up to 16 server ports to monitor. The list of ports can be filtered by selecting one or more of the drop-down boxes at the top of the screen.

The following table describes the available actions in the Select Monitored Ports screen.

Task Action Select a port to be monitored Select the checkbox corresponding to the port. Remove a port from the Deselect the checkbox corresponding to the port. monitored list Filter the list by I/O bay Select an I/O bay from the Filter by Interconnect Module module bay drop-down list. Only I/O bays with VC-Enet interconnect devices are displayed. Filter the list by interconnect Select a port from the Filter by Interconnect Module ports drop-down list. module server port Filter the list by a specific profile Select a profile from the Filter by Profile profiles drop-down list. Filter the list by a profile Select a profile connection from the Filter by Profile profile connection connection drop-down list. Filter the list by server bay Select a bay from the Filter by Physical Server bay drop-down list. Filter the list by server port Select a port from the Filter by Physical Server port drop-down list. Accept selected ports and return Click OK. to the Port Monitoring screen Clear newly selected ports Click Cancel. without saving and return to the Port Monitoring screen

Network management 114

Ethernet Settings (Advanced Settings) screen Use this screen to perform the following tasks: • Set Server VLAN Tagging Support (on page 117) • Use the Multiple Networks Link Speed Settings (on page 119) to set a custom value for preferred link connection speed or maximum link connection speed • Enable or disable MAC Cache Failover • Modify the refresh interval for MAC Cache Failover (on page 119) • Enable or disable IGMP Snooping (on page 120) • Modify the idle timeout interval for IGMP Snooping

Network management 115

This screen can be changed only by users with server and network administrator privileges.

Network management 116

Server VLAN Tagging Support This option provides explicit VLAN tagging support for server links, enabling each server link to be shared among multiple networks. Users can map server VLAN-tagged Ethernet packets to specific networks, which is essential in deploying server virtualization applications such as a virtual operating system solution. The following figure shows tunneled VLAN tags. On the dedicated, green network, both uplink and server VLAN tags are tunneled through Virtual Connect unchanged. On the shared, red and blue networks, uplink VLAN tags are mapped to networks. Untagged frames are mapped to the native VLAN, if present, otherwise they are dropped. Server frames are untagged only, and tagged frames are dropped. Each server port is connected to a single vNet.

Network management 117

The following figure shows mapped VLAN tags, a feature that enables users to define how each server VLAN tag is mapped to a specific network. Each server port can connect to multiple networks. Server NIC1 is connected to both the Green and Red networks. Server NIC2 is connected to the Red network, and Server NIC3 is connected to the Red, Blue, and Orange networks. All server NICs can send and received tagged or untagged traffic.

If Virtual Connect is set to map VLAN tags, VC-Enet modules accept incoming frames with valid server VLAN tags and translate server-assigned VLANs into corresponding internal network VLANs, thus placing the server packet on the correct network. When these frames reach the uplinks, network VLANs are once again translated into external data center VLANs. Similarly, VLANs are translated back to server-assigned VLANs (or stripped and untagged) before sending frames out to servers. This function allows for the possibility of configurations where server VLANs might not match external VLANs used on uplinks. To avoid this scenario, you can select the 'Force server connections to use the same VLAN mappings as shared uplink sets' option. Server port connections to networks are defined on the Define Server Profile screen (on page 146).

Restrictions and limitations • Maximum of 32 networks per shared uplink set • Maximum of 28 server VLAN-to-network mappings per server link • You can select to tunnel VLAN tags or map VLAN tags on a domain, but not both (the option is grayed out if it is not supported by the configuration). • The port VLAN ID must be selected from a specific shared uplink set. • When the 'Tunnel VLAN Tags' option is selected on the Ethernet Settings (Advanced Settings) screen (on page 115) or the 'Enable VLAN Tunneling' option is selected on the Define Ethernet Network screen (on page 103), server VLAN tagging is only supported on networks with dedicated uplinks, and it cannot be used with shared uplink sets. • If the 'Tunnel VLAN Tags' option is selected and VLAN tunneling is enabled on any dedicated network, the 'Map VLAN Tags' option cannot be selected. VLAN tunneling must be disabled on all dedicated networks before the 'Map VLAN Tags' option can be selected. Before Virtual Connect v1.31, all Networks had tunneling enabled. If you upgrade from a previous version you cannot

Network management 118

enable mapping of VLANs unless you disable tunneling on each network from the Edit Ethernet Network screen.

TIP: Use CLI scripting to automate the disabling of VLAN tunneling on multiple dedicated vNets. For information on CLI scripting, see the HP BladeSystem Virtual Connect Command Line Interface User Guide.

• If the 'Map VLAN Tags' option is selected and any server port is connected to multiple networks, the 'Tunnel VLAN Tags' option cannot be selected. All server profile connections assigned to multiple networks must be assigned to a single network (or 'Unassigned') before the 'Tunnel VLAN Tags' option can be selected. • The 'Force server connections to use the same VLAN mappings as shared uplink sets' checkbox can be selected under the following conditions: o The 'Map VLAN Tags' option is selected o No server profile connections are assigned to multiple networks not linked to a Shared Uplink Set This action forces all server connections mapped to multiple networks to be linked to a shared uplink set. Server administrators cannot override this selection when creating or editing a profile.

Multiple Networks Link Speed Settings When using mapped VLAN tags (multiple networks over a single link), these settings are used for the overall link speed control. Select the checkbox next to each item to set the value. These settings affect only newly created profiles. Changing these settings does not affect any assigned profiles. To set the speed, click the selection box, select a setting (100Mb to 10Gb), and then click OK. • Set a Custom value for the Preferred Link Connection Speed. This value is the default speed for server profile connections mapped to this network. The server administrator can override this setting on an individual profile connection. • Set a Custom value for the Maximum Link Connection Speed. This value is the maximum speed for server profile connections mapped to this network. The server administrator can override this setting on an individual profile connection. Virtual Connect can only control link speed for Flex-10 NICs when they are connected to an HP Virtual Connect Flex-10 Module. Virtual Connect cannot control the link speed of traditional NICs. For additional information, see "Flex-10 overview (on page 140)."

MAC Cache Failover When a VC-Enet uplink that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly-active connection. Enabling Fast MAC Cache Failover causes Virtual Connect to transmit Ethernet packets on newly-active links, which enables the external Ethernet switches to identify the new connection (and update their MAC caches appropriately). This transmission sequence repeats a few times at the MAC refresh interval (5 seconds recommended) and completes in about 1 minute.

IMPORTANT: Be sure to set switches to allow MAC addresses to move from one port to another without waiting for an expiration period or causing a lock out.

Network management 119

IGMP Snooping The IGMP Snooping feature allows VC-Enet modules to monitor (snoop) the IGMP IP multicast membership activities and configure hardware Layer 2 switching behavior of multicast traffic to optimize network resource usage. Currently only IGMP v1 and v2 (RFC2236) are supported. The IGMP Snooping idle timeout interval is set to 260 seconds by default. This value is the "Group Membership Interval" value as specified by IGMP v2 specification (RFC2236). For optimum network resource usage, set the interval to match the configuration on the customer network's multicast router settings.

Stacking Links screen To access this screen, click the Stacking Links link under Fibre Channel Settings in the left VC Manager navigation window This screen shows the current status of Virtual Connect Ethernet module stacking links. This screen is the same as the stacking links screen ("Stacking Links" on page 78) used in the Network Setup Wizard.

Shared uplink sets and VLAN tagging A shared uplink set is a way of identifying Virtual Connect Ethernet module uplinks that will carry multiple networks over the same cable. In this case, each Ethernet packet carries a VLAN tag (IEEE 802.1Q) to identify the specific network to which it belongs. On shared uplinks, the VLAN tags are added when packets leave the VC-enabled enclosure and are removed when packets enter the enclosure. The external

Network management 120

Ethernet switch and the Virtual Connect Manager must be configured to use the same VLAN tag identifier (a number between 1 and 4094) for each network on the shared uplink(s). Virtual Connect places no special restrictions on which VLAN identifiers can be used, so the VLAN IDs already used for the networks in the data center can be used on these shared uplinks. To configure a shared uplink set for VLAN tagging, obtain a list of the network names and their VLAN IDs. A shared uplink set enables multiple ports to be included to support port aggregation and link failover with a consistent set of VLAN tags. Because VLAN tags are added or removed when Ethernet packets leave or enter the VC-Enet shared uplink, the VLAN tags have no relevance after the Ethernet packet enters the enclosure.

IMPORTANT: If you are deploying a server where VLAN tags will be used (added) on the server itself, do not connect the server Ethernet port carrying VLAN-tagged traffic to a shared uplink set.

Identifying an associated network as the native VLAN causes all untagged incoming Ethernet packets to be placed onto this network. Only one associated network can be designated as the native VLAN. All outgoing Ethernet packets are VLAN tagged. To enable native VLAN when defining a shared uplink set, select the box under Native. To enable or disable native VLAN on an existing network, go to the Edit a Shared Uplink Set screen ("Edit Shared Uplink Set screen" on page 124). Click on the edit icon, and then select or deselect the box under Native.

Define New Shared Uplink Set screen To access this screen, click the Shared Uplink Sets link in the left VC Manager navigation window, and then click Define Uplink Set, or select Define Uplink Set from the Define pull-down menu. The Define New Shared Uplink Set screen is accessible to all users with network privileges by clicking the Define a Shared Uplink link from the VC Manager homepage or the Define pull-down menu. The Define New Shared Uplink Set screen is also accessible from the Network Setup Wizard ("HP Virtual Connect Network Setup Wizard" on page 75).

Network management 121

A maximum of 32 associated networks is supported in each shared uplink set.

The following table describes the fields within the Define New Shared Uplink Set screen.

Field name Description

Ethernet Shared External Uplink Set Uplink Set Name Descriptive name for the shared uplink set. Do not use spaces. External Uplink Ports Port Enclosure, bay, and port number Port Role Displays whether the port is designated as primary or secondary Port Status Displays linked or unlinked Connector type The type of connector on the port, for example, RJ-45 Connected to If the individual port is connected to a switch that supports LLDP, the switch MAC address and switch port number are displayed. A link is provided to obtain more information about the far-end switch port. PID PID status icon (lit or unlit) for the port Speed/Duplex Pull-down menu to specify the speed and duplex (where applicable) of the uplink port Delete Displays Delete icon. Click to delete that line item. Associated Networks (VLAN- tagged) Network Name Displays the name of the associated networks

Network management 122

Field name Description

VLAN ID Displays the VLAN ID number Native Select whether native VLAN is enabled (checked) or disabled (unchecked) Smart Link Select whether Smart Link is enabled (checked) or disabled (unchecked) Private Network Select to designate (checked) or not to designate (unchecked) this network as a private network Advanced Displays icon that accesses advanced network settings

The following table describes the available actions in the Define New Shared Uplink Set screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Add an external port Click the down arrow on Add Port. Select the enclosure, bay number, and port number. Set the Port Role to primary or Click the down arrow in the Port Role column and select Primary or secondary Secondary. Change the uplink interface Click the drop-down box under Speed/Duplex, and then select a setting. port speed or disable the port Delete a port Click the Delete icon in the Delete column of the port to be deleted. Change connection mode Click the down arrow in the box next to Connection Mode, and then select Auto or Failover. For information on Connection Modes, see "Defining a shared uplink set ("Define New Shared Uplink Set screen" on page 121)." Add an Associated Network Click Add Network. Enable native VLAN on the Select the box under Native. Only one network can be designated as the network being defined native VLAN. Enable or disable Smart Link on Select the box under Smart Link. the network being defined Designate or do not designate Select the box under Private Network. this network as a private network Set a custom value for Click on the Advanced icon for the line item to be changed. preferred link connection speed or maximum link connection speed Edit associated network Click on the Edit icon for the line item to be changed. properties Delete an associated network Click on the Delete icon for the line item to be deleted.

Defining a shared uplink set To define a shared uplink set, use the following steps: 1. Enter the shared uplink set name. The uplink set name can be up to 64 characters in length (no spaces).

Network management 123

2. Add one or more external ports using the Add Port pull-down menu. Only available ports are listed and they will display the current port link status. Select two or more ports to ensure a high availability connection. 3. Select the speed and duplex (where applicable) of the uplink ports. Click the drop-down box under Speed, and then select a setting. Half-duplex operation is not supported by the Virtual Connect Ethernet module.

IMPORTANT: Be sure that the uplink interface port speed matches the speed set on the corresponding network switch port. If using autonegotiation, both ports must be configured to use autonegotiation or they might not link.

4. Select the Connection Mode: o Auto (recommended)—This mode enables the uplinks to attempt to form aggregation groups (using IEEE 802.3ad link aggregation control protocol) and to select the highest-performance uplink as the active path to external networks. Aggregation groups require multiple ports from a single Virtual Connect Ethernet module to be connected to a single external switch that supports automatic formation of LACP aggregation groups. Multiple aggregation groups may be formed from the ports selected for the network. The highest performing aggregation group is selected as active with other aggregation groups and individual links used as standby connections. o Failover—If this mode is selected, set the port to Primary or Secondary. Only a single link is used as the active link to the external networks with other ports used as standby connections. 5. Identify the Associated Networks that will use this shared uplink: a. Click Add Network to add a row in the Associated Networks table. b. Enter the name of the network. c. Enter the number for the VLAN ID (1 to 4094) for that network as defined by the network administrator and as configured on the external Ethernet switch. d. Select whether to enable (checked) or disable (unchecked) native VLAN. Only one network can be selected as the native VLAN. See "Shared uplink sets and VLAN tagging (on page 120)." e. Select whether to enable (checked) or disable (unchecked) Smart Link (on page 102). f. Select whether to designate (checked) or not designate (unchecked) the network as a private network ("Private Networks" on page 102). g. Click the Advanced icon to set a custom value for preferred link connection speed or maximum link connection speed. h. Repeat steps a. through g. for all networks to use the shared uplink set, up to a maximum of 32 per shared uplink set. 6. Click Apply. The shared uplink and associated networks are now defined and available for use in creating server profiles.

Edit Shared Uplink Set screen To access this screen, click the shared uplink set to be edited in the left VC Manager navigation window.

Network management 124

Use this screen to edit the properties of an existing shared uplink set, add/delete an associated network, or delete a shared uplink set. This screen has the same fields as the Define Shared Uplink screen. The screen can be edited only by users with network privileges, but it is viewable by all authorized users.

The following table describes the fields within the Edit Shared Uplink Set screen.

Field name Description

Ethernet Shared External Uplink Set Uplink Set Name Descriptive name for the shared uplink set. Do not use spaces. Status Displays the status icon for the named uplink set PID Displays PID status icon (lit or unlit) External Uplink Ports Port Enclosure, bay, and port number Port Role Displays whether the port is designated as primary or secondary Port Status Displays linked or unlinked Connector type The type of connector on the port, for example, RJ-45 Connected to If the individual port is connected to a switch that supports LLDP, the switch MAC address and switch port number are displayed. A link is provided to obtain more information about the far-end switch port. PID PID status icon (lit or unlit) for the port

Network management 125

Field name Description

Speed/Duplex Pull-down menu to specify the speed and duplex (where applicable) of the uplink port. Half-duplex operations are not supported by the VC-Enet module. Delete Displays Delete icon. Click to delete that line item. Associated Networks (VLAN- tagged) Network Name Displays the name of the associated networks VLAN ID Displays the VLAN ID number Native Select whether native VLAN is enabled (checked) or disabled (unchecked). Smart Link Select whether Smart Link is enabled (checked) or disabled (unchecked). Private Network Select whether to designate (checked) or not designate (unchecked) the network as a private network. Advanced Hover mouse over the icon to view Ethernet connection port speed settings.

The following table describes the available actions in the Edit Shared Uplink Set screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Rename shared uplink set Click on the uplink set name and edit. Set the Port Role to primary or Click the down arrow in the Port Role column and select Primary or secondary Secondary. Change the uplink interface port Click the drop-down box under Speed/Duplex, and then select a setting. speed or disable a port Delete a port Click the Delete icon in the Delete column of the port to be deleted. Change connection mode Click the down arrow in the box next to Connection Mode, and then select Auto or Failover. Add an associated network Click Add Network. Enter the network name and VLAN ID in the fields provided. Enabled native VLAN on the Select the box under Native. network Enable Smart Link on the Select the box under Smart Link. Network Designate the network as a Select the box under Private Network. private network Set a custom value for preferred Click on the Advanced icon for the line item to be changed. link connection speed or maximum link connection speed Edit an associated network Click on the Edit icon for the line item to be changed. Delete an associated network Click on the Delete icon for the line item to be deleted.

Network management 126

Shared Uplink Sets (External Connections) screen To access this screen, click the Shared Uplink Sets link in the left VC Manager navigation window. This summary screen provides an overview of external shared uplink connections and access to the Associated Networks tab to view the mapping of networks to those uplinks. This screen is only applicable if multiple networks are being connected over a single external uplink set by the use of VLAN tagging.

Shared Uplink Sets (Associated Networks) screen To access this screen, click the Shared Uplink Sets link in the left VC Manager navigation window, and then click the Associated Networks tab.

Network management 127

This summary screen displays the mapping of networks to external shared uplink connections. This screen is only applicable if multiple networks are being connected over a single external uplink set by the use of VLAN tagging.

Network management 128

Storage management

Storage overview The Virtual Connect Fibre Channel modules enable the c-Class administrator to reduce FC cabling by making use of N_Port_ID virtualization (NPIV). The HP VC-FC acts as an HBA aggregator where each NPIV-enabled N-port uplink can carry the FC traffic for multiple HBAs. Because it uses an N-port uplink, it can be connected to data center Brocade, McData, Cisco, and Qlogic FC switches that support the NPIV protocol. When the server blade HBAs log in to the fabric through the VC-FC module, the HBA WWN is visible to the FC switch name server and can be managed as if it was connected directly.

IMPORTANT: The HP 4Gb Virtual Connect Fibre Channel Module must be connected to a data center Fibre Channel switch that supports N_Port_ID virtualization (NPIV). See the switch firmware documentation for information to determine whether a specific switch supports NPIV and for instructions on enabling this support.

The VC-FC module has four uplinks. Each uplink is completely independent of the other uplinks and has a capability of aggregating up to 16 server HBA N-port links into an N-port uplink through the use of NPIV. In previous versions of Virtual Connect, a one-to-one relationship existed between VC-FC uplinks and external FC SAN fabrics. Beginning with version 1.31 of Virtual Connect Manager, users can group multiple VC-FC module uplinks logically into a Virtual Connect fabric when attached to the same Fibre Channel SAN fabric. Using this feature, users can access more than one FC SAN fabric in their data center, plus have a flexible and fully redundant way to connect server blades to Fibre Channel SANs. Now a user can connect to up to four SAN fabrics from one VC-FC module.

Virtual Connect Fabric By default, all four of the VC-FC uplinks are grouped into a single fabric distributing connectivity from all 16 server blades in the enclosure. If a port in the group becomes unavailable, hosts logged in through that port are reconnected to the fabric through the remaining ports in the group, resulting in auto-failover. However, users can redistribute the connections manually. When static mapping of a server HBA to a Virtual Connect fabric is preferred, users can select which specific uplink ports shall be members of the Virtual Connect fabric. The mapping of the server HBA ports to uplink ports uses the following mechanism:

Number of uplinks FC connectivity for device bays: 1 uplink 1-16 (Either uplink 1, 2, 3, or 4) 2 uplinks in any combination Least # uplink - 1, 3, 5, 7, 10, 12, 14, (1-2, 1-3, 1-4, 2-3, 2-4, or 3-4) 16 Next # uplink - 2, 4, 6, 8, 9, 11, 13, 15

Storage management 129

Number of uplinks FC connectivity for device bays: 3 uplinks in any combination Least # uplink - 1, 4, 7, 10, 13, 16 (1-2-3, 1-2-4, 1-3-4, 2-3-4) Next # uplink - 2, 5, 8, 11, 14 Next # uplink - 3, 6, 9, 12, 15 4 uplinks Uplink #1 - 1, 5, 11, 15 (All uplinks 1, 2, 3 and 4) Uplink #2 - 2, 6, 12, 16 Uplink #3 - 3, 7, 9, 13 Uplink #4 - 4, 8, 10, 14

To form a Virtual Connect fabric correctly, participating uplinks must be connected to the same SAN fabric. With Dynamic Load Balancing the module provides an uplink port path failover that allows server connections to failover within the Virtual Connect fabric. Server connections are redistributed across all available (currently logged-in into the external SAN) uplink ports.

• Dynamic Load Balancing—Balances traffic based on the number of SAN logins on a port. This type of mapping provides failover and failback within the Virtual Connect fabric. • Static Login Distribution—Permanently maps the server connection to a specific uplink port.

Storage management 130

Define SAN Fabric screen To define a SAN fabric, select the Define SAN Fabric link on the Home page, or click Define SAN Fabric on the SAN Fabrics screen.

The following table describes the columns and fields within the Define SAN Fabric screen.

Column Description

Fabric Name Descriptive name for the virtual fabric. Do not use spaces. Configured Speed Speed of the uplink port(s) Uplink Port Number of the enclosure uplink port Bay Enclosure bay selected for the SAN fabric. Only uplinks on the same bay can be in the same SAN fabric. Port Port number Port Status Status of the uplink port Speed Port speed for the uplink ports in the fabric Connected To WWN of the principal switch on the SAN fabric that this port is connected to on the other end. Delete When the X in the column is bold, this line item is eligible for deletion.

The following table describes the available actions in the Define SAN Fabric screen. Clicking another link in the pull-down menu or left navigation window causes the current edits that have not been applied to be lost.

Storage management 131

Task Description

Create a fabric name Type a name in the Fabric Name field. Do not use spaces. Set the uplink port(s) speed Click the drop-down arrow in the Configured Speed field and select a speed. Select the login distribution (on page Click Advanced, and then select static or dynamic login distribution. 130) Add an uplink port Click Add Port. Delete an uplink port Click X in the line of the uplink port to delete. Clear current changes without saving Click Clear. Save changes and remain on this Click Apply. screen Clear the current, unsaved changes Click Cancel. and return to the home page

Enabling NPIV on the fabric switch When installing the VC-FC module, NPIV must be enabled on the fabric switch that is attached to the VC- FC module uplinks before the server blade HBAs can log in to the fabric. See the Fibre Channel switch firmware documentation for information on whether it supports NPIV and for instructions on enabling this support.

Brocade switch Most Brocade Fibre Channel switches running Fabric OS 5.1.0 or later will support NPIV. All Brocade 4Gb capable Fibre Channel switches are by default configured with NPIV enabled. When not enabled by default, use the portCfgNPIVPort command within the Brocade switch command line interface to enable NPIV. For additional information on usage of the portCfgNPIVPort command, see the Brocade switch firmware documentation. To enable NPIV on all other Brocade Fibre Channel Switches use the following Fabric OS CLI procedure. 1. To enable or disable NPIV on a port-by-port basis From Brocade Fabric OS CLI use the portCfgNPIVPort command. Example: To enable NPIV on port 10 enter following command: switch:admin> portCfgNPIVPort 10, 1 2. To specify the number of virtual N_Port_IDs per port or per switch, use the configure command with either of the following parameters: switch.login.perPortMax—Use this parameter to set the number of virtual N_Port_IDs per port to a value between 0 and 255. The default setting is 126. switch.login.perSwitchMax—Use this parameter to set the number of virtual N_Port_IDs per switch to a value between 0 and (126 * number of ports). The default setting is (15 * number of ports). Example: switch:admin> switchdisable switch:admin> configure

Storage management 132

Configure...

Fabric parameters (yes, y, no, n): [no] Virtual Channel parameters (yes, y, no, n): [no] F-Port login parameters (yes, y, no, n): [no] y Maximum logins per switch: (1..4032) [4032] 2048 Maximum logins per port: (1..255) [255] 126 . . switch:admin> switchenable

Cisco switch Cisco Fibre Channel switches running SAN-OS 3.0 or later will support NPIV. To enable NPIV on Cisco Fibre Channel Switches running the Cisco Device Manager, use the following procedure: 1. From the Cisco Device Manager, click Admin, and then select FeatureControl. The Feature Control window appears. 2. Click the row titled NPIV. 3. In the Action column select enable, and then click Apply. 4. Click Close to return to the Name Server screen. 5. Click Refresh to display the Host ports.

McData switch McDATA Fibre Channel switches with E/OS 8.0 or later will support NPIV. McDATA switches require an optional license to enable this function. Use the following procedure to apply this license and enable NPIV: 1. From a browser, open the web user interface for the McDATA switch that is to be connected to the VC-FC module. The Node List view details the devices attached to the McDATA switch. 2. To install the NPIV license, click Maintenance, and then select Options Features. 3. Enter the license key for NPIV in the Feature Key field. Select the key as the "N_Port ID Virtualization (NPIV)." Link from the window and apply the key by clicking OK. A check mark in the left window indicates that the N_Port ID Virtualization key is installed. 4. Click Configure, and then select Ports>NPIV. 5. Click Enable. 6. At the prompt click OK if you are sure you want to enable NPIV. 7. In the Login column, set the value to 17 or higher for each port connected to the VC-FC to ensure proper operation. 8. Click OK to save changes.

SAN Fabrics (External Connections) To access this screen, click SAN Fabrics in the left VC Manager navigation window. This screen lists all of the SAN fabrics that have been created and displays the external connection information. To delete a fabric, select the checkbox of that line item, and then click Delete.

Storage management 133

To redistribute logins on a SAN fabric, click Redistribute Logins. 'Redistribute Logins' is only valid for a Virtual Connect fabric with Dynamic Login Distribution.

SAN Fabrics (Server Connections) To access this screen, click SAN Fabrics in the left VC Manager navigation window, and then click the Server Connections tab. This screen lists all of the SAN fabrics that have been created and displays the server connection information. To delete a fabric, select the checkbox of that line item, and then click Delete.

Storage management 134

To redistribute logins on a SAN fabric, click Redistribute Logins. 'Redistribute Logins' is only valid for a Virtual Connect fabric with Dynamic Login Distribution.

Storage management 135

Edit SAN Fabric Use this screen to edit a SAN fabric configuration.

The following table describes the fields within the Edit SAN Fabric screen.

Field Description

Fabric Name Descriptive name for the virtual fabric. Do not use spaces. Status Status of the virtual fabric Login Distribution Type of login distribution assigned to the fabric (dynamic or static) Configured Speed Speed of the uplink port Uplink Port Number of the enclosure uplink port Bay Enclosure bay selected for the SAN fabric Port Port number Port Status Status of the uplink port Speed Speed of the uplink port Connected To WWN of the principal switch on the SAN fabric that this port is connected to on the other end Delete When the X in the column is bold, this line item is eligible for deletion.

The following table describes the available actions in the Edit SAN Fabric screen. Clicking another link in the pull-down menu or left navigation window causes the current edits that have not been applied to be lost.

Storage management 136

Task Description

Modify a fabric name Type a name in the Fabric Name field. Do not use spaces. Set the uplink port speed Click the drop-down arrow in the Configured Speed field and select a speed. Select the login distribution (on page Click Advanced, and then select static or dynamic login distribution. 130) Add an uplink port Click Add Port. Delete an uplink port Click X in the line of the uplink port to delete. Clear current changes without saving Click Clear. Save changes and remain on this Click Apply. screen Clear the current, unsaved changes Click Cancel. and return to the home page

Fibre Channel Settings (FC SAN Settings) screen Use this screen to assign World Wide Names. Each server blade FC HBA mezzanine card ships with factory default port and node WWNs for each FC HBA port. Each WWN is a 64-bit number that uniquely identifies the FC HBA port/node to other devices on the network. While the hardware ships with default WWNs, Virtual Connect has the ability to assign WWNs that will override the factory default WWNs while the server remains in that Virtual Connect enclosure. When configured to assign WWNs, Virtual Connect securely manages the WWNs by accessing the physical FC HBA through the enclosure Onboard Administrator and the iLO interfaces on the individual server blades. When assigning WWNs to a FC HBA port, Virtual Connect will assign both a port WWN and a node WWN. Because the port WWN is typically used for configuring fabric zoning, it is the WWN displayed throughout the Virtual Connect user interface. The assigned node WWN is always the same as the port WWN incremented by one. Configuring Virtual Connect to assign WWNs in server blades maintains a consistent storage identity (WWN) even when the underlying server hardware is changed. This method allows server blades to be replaced without affecting the external Fibre Channel SAN administration.

There are two ways to access this screen: • Click WWN Settings under Fibre Channel Settings in the left window of the homepage.

Storage management 137

• Select Fibre Channel Settings from the Configure pull-down menu.

Storage management 138

Server management

Server profile overview A Virtual Connect server profile is a logical grouping of attributes related to server connectivity that can be assigned to a server blade. The server profile can include MAC address, PXE, and network connection settings for each server NIC port and WWN, SAN fabric connection, and SAN boot parameter settings for each Fibre Channel HBA port. After being defined, the server profile can be assigned to any server blade within the Virtual Connect domain. A Virtual Connect domain can have a maximum of 64 Virtual Connect server profiles. Virtual Connect provides the ability to configure PXE settings when using either VC Assigned or factory default MAC addresses. In addition, Use BIOS is an option for PXE, which maintains the current settings as configured by RBSU. Virtual Connect also provides the ability to override the Virtual Connect assigned MACs and/or WWNs when creating a new profile. See "Define Server Profile Screen (on page 146)." When a server profile is assigned to a server blade, the Virtual Connect Manager securely connects to the server blade, configures the NIC ports with the appropriate MAC addresses and PXE settings, and configures the FC HBA ports with the appropriate WWNs and SAN boot settings. In addition, the Virtual Connect Manager automatically connects the server blade Ethernet and Fibre Channel ports to the specified networks and SAN fabrics. This server profile can then be re-assigned to another server blade as needed, while maintaining the server's network and SAN identity and connectivity. The Virtual Connect Manager can be configured so that server blades use server factory default MACs/WWNs or Virtual-Connect-administered MACs/WWNs. These administered values override the default MAC addresses and WWNs when a server profile is assigned to a server, and appear to pre- boot environments and host operating system software as the hardware addresses. To use administered MAC addresses, select a range of HP pre-defined or user-specified MAC addresses. See "MAC address settings (on page 76)."

IMPORTANT: Be sure to review the following list of guidelines before creating and deploying server profiles.

• The server blade firmware and option card firmware must be at a revision that supports Virtual Connect profile assignment. See the HP website (http://www.hp.com/go/bladesystemupdates). • Before creating the first server profile, select whether to use moveable, administered MAC addresses and WWNs or whether to use the local server blade factory default MAC addresses and WWNs. See "MAC address settings (on page 76)" and "WWN settings (on page 86)." • After an enclosure is imported into a Virtual Connect domain, server blades remain isolated from the networks and SAN fabrics until a server profile is created and assigned. • Server blades must be powered off to receive (or relinquish) a server profile assignment when using Virtual Connect-administered MAC addresses, WWNs, or changing Fibre Channel boot parameters.

Server management 139

• FC SAN Connections are shown in server profile screens when only there is an HP Virtual Connect Fibre Channel Module in the enclosure managed by Virtual Connect. FC SAN Connections are added in pairs and cannot be deleted. If an HP Virtual Connect Fibre Channel Module is added to a Virtual Connect domain that has existing profiles, an option to add FC connections appears in the existing profiles during editing. • Some server profile SAN boot settings (controller boot order) are applied by Virtual Connect only after the server blade has been booted at least once with the final mezzanine card configuration. • If PXE, controller boot order, or SAN boot settings are made outside of Virtual Connect (using RBSU or other configuration tools), Virtual Connect will restore the settings defined by the server profile after the server blade completes the next boot cycle. • To boot properly from SAN when using Linux and VMware ESX 3.0.1 and ESX 3.0.2, change the QLogic QMH2462 4Gb FC HBA connection option to 'point-to-point only' in the QLogic BIOS configuration utility. The Emulex LPe 1105-HP 4Gb FC HBA does not require using the 'point-to-point' connection option to boot properly from SAN. Server profiles are associated with a specific enclosure device bay. After a profile is assigned, the Virtual Connect Manager configures the server blade in that device bay with the appropriate MAC/PXE/WWN/SAN boot settings and connects the appropriate networks and fabrics. Server blades that have been assigned a profile and remain in the same device bay do not require further Virtual Connect Manager configuration during a server or enclosure power cycle. They will boot and gain access to the network and fabric when the server and interconnect modules are ready. If a server blade is inserted into a device bay already assigned a server profile, Virtual Connect Manager automatically updates the configuration of that server blade before it is allowed to power up and connect to the network. If a server blade is moved from a Virtual Connect managed enclosure to a non-Virtual Connect enclosure, local MAC addresses and WWNs are automatically returned to the original factory defaults. This feature prevents duplicate MAC addresses and WWNs from appearing in the data center because of a server blade redeployment.

NOTE: If you are using server factory default MAC addresses WWNs and default Fibre Channel boot parameters, you do not have to power off a server to make any profile changes. If you are using HP assigned or user assigned MAC addresses or WWNs, you must power a server off when moving a profile to the server or away from the server.

Flex-10 overview Flex-10 technology is exclusive to Virtual Connect environments, and it allows Flex-10 enabled 10Gb NICs to enumerate as four FlexNICs per 10Gb port. These FlexNICs are actual PCIe functions, and they appear to the operating system or hypervisor as discrete NICs, each with its own driver instance.

Server management 140

Although these four FlexNICs share a single 10Gb physical interface, Virtual Connect is able to keep traffic for the FlexNICs isolated, and each FlexNIC is assigned to a different Virtual Connect network. Each FlexNIC can be assigned a different bandwidth (from 100Mb to 10Gb), which is enforced by hardware mechanisms.

A Flex-10 capable NIC (embedded Ethernet or mezzanine card) only enumerates as four FlexNICs per 10Gb port if that NIC is directly connected to an HP Virtual Connect Flex-10 Module or an empty interconnect bay. Eight FlexNICs are enumerated when connected to an empty interconnect bay because it is assumed that an HP Virtual Connect Flex-10 Module will be plugged into that bay. If a Flex-10 capable NIC is connected to a Virtual Connect interconnect module that does not support Flex-10 or a non-Virtual Connect interconnect module, that NIC enumerates as only one Ethernet device per physical port. The following table shows an example of how a BL495c Flex-10 embedded Ethernet device would be enumerated when connected to different interconnects. For more information about mapping between servers and interconnect bays, see the HP c-Class enclosure documentation.

Connected to Number of NICs enumerated to the host HP Virtual Connect Flex-10 Module 8 HP 1/10GB-F VC-Enet Module 2 HP GbE2c Ethernet Blade Switch 2 Cisco Catalyst Blade Switch 3120 2 Empty interconnect bay 8

Server management 141

Flex-10 configuration Network administrator For each Virtual Connect network, the network administrator can set a "Preferred" and "Maximum" speed for FlexNICs that connect to that network. FlexNICs cannot connect to a network at a speed higher than the maximum speed set by the network administrator for that network. The "preferred" speed setting is the speed recommended by the network administrator for any FlexNIC that attaches to that network. The server administrator can choose to follow or disregard this recommendation. The network administrator can change these two settings by clicking the Advanced button on the create/edit network screen. For additional information, see "Multiple Networks Link Speed Settings (on page 119)." Server administrator The server administrator can configure a requested bandwidth for every connection in a server profile. Virtual Connect can control the link speed of FlexNICs, but cannot control the link speed of traditional NICs. The server administrator has three choices for Requested Bandwidth for each connection: 1. Preferred. Choosing "Preferred" sets the requested bandwidth equal to the bandwidth recommended by the network administrator's "Preferred" speed setting for that network. If the administrator has not configured a preferred bandwidth for the network, this setting is treated the same as "Auto". 2. Custom. Choosing "Custom" enables the user to specify a number between 100Mb and 10Gb (in increments of 100Mb) for requested bandwidth. 3. Auto. Choosing "Auto" evenly distributes the available bandwidth between all connections assigned to "auto". For additional information, see "Bandwidth assignment (on page 144)." Although the Port Speed Setting is available for all network connections in a profile, Virtual Connect can only control link speed for Flex-10 NICs when they are connected to an HP Virtual Connect Flex-10 Module. Virtual Connect cannot control the link speed of traditional NICs. Allowing specification of port speed regardless of the underlying NIC allows the profile to configure the connection automatically when moved to or from Flex-10 enabled servers and NICs.

Server management 142

The Allocated Bandwidth column displays "not allocated" until the profile is assigned to a device bay that contains a server. At that time, bandwidth is allocated to each connection and the result is reported in this column. See "Bandwidth assignment (on page 144)." The Mapping column describes how each connection of a profile is assigned to physical devices in a server, and to which interconnect bay that device is connected. The four FlexNICs on port 1 of a server LOM that supports Flex-10 are numbered LOM:1-a, LOM:1-b, LOM:1-c, and LOM:1-d. If a LOM does not support Flex-10, then it is simply referenced by its port number (for example, LOM:1 or LOM:2).

Port assignment A server profile is simply a list of connections and other parameters until that profile is applied to a physical server. The same profile can be mapped to server hardware differently depending on the presence or absence of different mezzanine cards, and if Ethernet devices in the server are capable of supporting Flex-10. In versions of firmware prior to VC 2.00 (versions that do not support Flex-10), server profile connections are assigned to a half-height server in the following order: 1. Assign a connection to LOM port 1. 2. Assign a connection to LOM port 2. 3. Assign a connection to MEZ1 port 1 (if present). 4. Assign a connection to MEZ1 port 2 (if present). 5. Assign a connection to MEZ2 port 1 (if present). 6. Assign a connection to MEZ2 port 2 (if present). 7. Assign a connection to MEZ2 port 3 (if present). 8. Assign a connection to MEZ2 port 4 (if present). Connections are assigned to full-height servers in a similar way, but MEZ1 could have four ports and an additional mezzanine slot (MEZ3) exists. Virtual Connect v2.00 implements the same assignment algorithm with the exception that the algorithm repeats for all remaining unassigned profile connections. Additional profile connections can be assigned to Flex-10 capable devices with a maximum of four connections per Flex-10 capable port. For example, a profile with eight connections is assigned to a half-height server with a Flex-10 LOM and a traditional NIC mezzanine in MEZ1 in the following order: 1. Assign profile connection 1 to LOM port 1. 2. Assign profile connection 2 to LOM port 2. 3. Assign profile connection 3 to MEZ1 port 1. 4. Assign profile connection 4 to MEZ1 port 2. 5. Assign profile connection 5to LOM port 1 because it is Flex-10 capable and can support up to four connections. 6. Assign profile connection 6 to LOM port 2 because it is Flex-10 capable and can support up to four connections. 7. MEZ1 is not Flex-10 capable in this example, so additional connections cannot be assigned to MEZ1. Therefore, assign profile connection 7 to LOM port 1 because it is Flex-10 capable and can support up to four connections.

Server management 143

8. Assign profile connection 8 to LOM port 2 because it is Flex-10 capable and can support up to four connections.

Bandwidth assignment In Flex-10 environments, four FlexNICs must share a single 10Gb link. Each FlexNIC is allocated a portion of that 10Gb link's bandwidth. The bandwidth assigned to the four FlexNICs in a single physical port cannot exceed 10Gb, but the requested bandwidth settings specified by the user might exceed 10Gb. Each FlexNIC is assigned a bandwidth value that is a portion of a 10Gb link. A 10Gb NIC might not be able to saturate a 10Gb link, so FlexNIC bandwidth is limited to a proportion of the NIC's actual throughput. For example, a FlexNIC that is assigned a requested bandwidth value of 5Gb might not be able to achieve a full 5Gb of throughput, but that FlexNIC is allocated half of the NIC's actual throughput. Requested bandwidth is translated to assigned bandwidth with the following rules: 1. FlexNICs with a "preferred" or "custom" value for requested bandwidth receive their allocated bandwidth first. For example, if the requested bandwidth setting for the four FlexNICs on a given port are all 2Gb, then each FlexNIC can be assigned 2Gb of bandwidth.

Requested Allocated FlexNIC a 2Gb 2Gb FlexNIC b 2Gb 2Gb FlexNIC c 2Gb 2Gb FlexNIC d 2Gb 2Gb

2. After bandwidth is allocated in rule 1 above, FlexNICs with an "Auto" value for the requested bandwidth divide the remaining bandwidth evenly . For example, if the requested bandwidth setting for the four FlexNICs on a given port are 1Gb, Auto, Auto, and Auto, then the first FlexNIC is assigned 1Gb (as per rule 1) and the other three FlexNICs divide the remaining 9Gb evenly (3Gb each). There might be some cases where the bandwidth does not divide evenly as Virtual Connect assigns bandwidth in increments of 100Mb. Connections with a "preferred" setting to a network where no preferred speed has been defined are treated as a connection set to "auto".

Requested Allocated FlexNIC a 1Gb 1Gb FlexNIC b Auto 3Gb FlexNIC c Auto 3Gb FlexNIC d Auto 3Gb

In cases where the requested bandwidth settings specified by the user for the four FlexNICs in a single physical port exceed 10Gb, the following rules are applied in this order: 1. If FlexNICs with a "preferred" or "custom" value for requested bandwidth exceed 10Gb, each FlexNIC is allocated bandwidth proportional to its requested bandwidth setting. For example, if four FlexNICs on a given port have requested bandwidth settings of 1Gb, 2Gb, 4Gb, and 5Gb, their allocated bandwidth is as shown in the table below. In this example, 200Mb remains after dividing the 10Gb link. 100Mb is added to the two connections with the least bandwidth.

Requested Calculation Allocation + remainder FlexNIC a 1Gb (1/12)*10Gb = 800Mb 900Mb

Server management 144

Requested Calculation Allocation + remainder FlexNIC b 2Gb (2/12)*10Gb = 1600Mb 1700Mb FlexNIC c 4Gb (4/12)*10Gb = 3300Mb 3300Mb FlexNIC d 5Gb (5/12)*10Gb = 4100Mb 4100Mb

2. Every FlexNIC that is linked must be allocated at least 100Mb. For example, if four FlexNICs on a given port have requested bandwidth settings of 2Gb, 8Gb, Auto, and Auto, their allocated bandwidth is as shown in the table below. In this example, 100Mb must be allocated to the two FlexNICs set to "Auto" because no bandwidth would remain after allocating 2Gb and 8Gb to the first two FlexNICs. The two FlexNICs set for 2Gb and 8Gb requested bandwidth are allocated a proportion of the 9800Mb remaining after the two FlexNICs set to "Auto" receive 100Mb. In this example, there is a remainder of 100Mb, and that remainder is assigned to the FlexNIC whose allocated bandwidth differs the most from its requested bandwidth.

Requested Calculation Allocation + remainder FlexNIC a 2Gb (2/10)*9800Mb = 1900Mb 2000Mb FlexNIC b 8Gb (8/10)*9800Mb = 7800Mb 7800Mb

FlexNIC c Auto 100Mb 100Mb FlexNIC d Auto 100Mb 100Mb

PXE settings Virtual Connect Manager v1.20 and higher supports three PXE options: • Enable—VC Manager sends a configuration update to the mezzanine NIC or embedded NIC associated with the port to enable PXE operations. • Disable—VC Manager sends a configuration update to the associated mezzanine NIC or embedded NIC to disable PXE operations. • Use BIOS—Current BIOS settings are used for embedded NICs and mezzanine NIC PXE operations. VC Manager makes no changes to the current settings. HP BladeSystem c-Class server blades have a factory default configuration for PXE to be enabled on embedded NIC 1 only and this is included as the last entry in the RBSU IPL priority list (boot order). VC Manager and the BIOS limit the number of PXE enabled embedded NICs to one. However, additional NIC ports from a mezzanine adapter can be enabled simultaneously using the "Use BIOS" settings. All mezzanine NIC ports can be enabled for PXE booting at the same time, along with one embedded NIC port. If one or more mezzanine NIC ports are enabled for PXE booting, the user should review the RBSU IPL list to validate or update the boot order priority. If you need to enable PXE on more than one NIC port, you must set all of the NICs' PXE configuration option in the VC Manager to "Use BIOS", and configure the individual PXE NIC settings using RBSU: F9 during POST to configure an embedded NIC, and F1 during POST to configure the mezzanine NIC ports. After all of the selected NIC ports are PXE enabled, you must configure the boot order using the RBSU boot order settings. Only the first FlexNIC on each physical port of a Flex-10 device can be used for PXE boot. Virtual Connect cannot enable PXE boot on the remaining FlexNICs of a physical port.

Server management 145

Redundancy for PXE operations can be achieved using multiple PXE enabled NICs. However, the Virtual Connect Manager is limited to enabling only one NIC for PXE booting. If a configuration requires more than one NIC to have PXE enabled, you should set all NICs in the VC Manager to the "Use BIOS" setting, and configure the NIC PXE settings through their respective BIOS utilities (F9 for embedded NICs, and F1 for mezzanine NIC ports.) The following table lists examples of valid configurations for PXE enabling NIC ports. This is only a sampling of the possible valid configurations.

PXE enabled PXE disabled Server blade configuration Embedded NIC 1, Embedded NIC 2, BL46xc with a dual-port NIC Mezzanine Mezz 1 NIC port 1 Mezz NIC port 2 adapter Embedded NIC 2, Embedded NIC 1, BL46xc with a dual-port NIC Mezzanine Mezz 1 NIC port 1 Mezz NIC port 2 adapter Embedded NIC 1, Embedded NIC 1 BL46xc with a dual-port NIC Mezzanine Mezz 1 NIC port 1,2 adapter Mezz 1 NIC port 1,2 Embedded NIC 1,2 BL46xc with a dual-port NIC Mezzanine adapter Embedded NIC 1, Embedded NIC 2, 3,4 BL48xc with a dual-port NIC Mezzanine Mezz 1 NIC port 1 Mezz 1 NIC port 1 adapter and a quad-port NIC Mezzanine adapter Mezz 2 NIC ports 1,2 Mezz 2 NIC port 3,4 Embedded NIC 4, Embedded NIC 1,2,3 BL48xc with a dual-port NIC Mezzanine Mezz 1 NIC ports 1,2 adapter and a quad-port NIC Mezzanine Mezz 2 NIC ports 1,2,3,4 adapter Mezz 1 NIC port 1 Embedded NIC 1,2,3,4 BL48xc with a dual-port NIC Mezzanine Mezz 2 NIC ports 1 Mezz 1 NIC port 2 adapter and a quad-port NIC Mezzanine adapter Mezz 2 NIC port 2,3,4

In each configuration above, only one embedded NIC port is allowed to have PXE enabled (any embedded NIC port is eligible), but any and all mezzanine NIC ports can be enabled whether or not an embedded NIC port is being enabled. For more information on RBSU, see the HP ROM-Based Setup Utility User Guide on the Documentation CD or the HP website (http://www.hp.com/support/smartstart/documentation).

Define Server Profile screen Use this screen to create a new server profile definition, which defines and configures Ethernet and Fibre Channel connectivity for the server. This screen can be edited only by users with server privileges, but it is viewable by all authorized users.

IMPORTANT: The network setup wizard or equivalent steps must be performed before defining server profiles. See "HP Virtual Connect Network Setup Wizard (on page 75)."

Server management 146

The following table describes the fields within the Define Server Profile screen.

Column name Description

Profile Profile Name Descriptive name for the server profile. The specified text is used as the base (prefix) for the name of the created Virtual Connect server profiles. The text can be up to 48 alpha-numeric characters, dashes, and underscores. Do not use spaces. Ethernet Network Connections (Physical ports) Port Relative order of the Ethernet port on the server receiving the profile. System board NICs are first in the order, followed by NICs on mezzanine cards. Network Name Name of the network associated with this port selected from list of defined networks Status Displays the current linked status of the selected port

Server management 147

Column name Description

Port Speed Setting The requested operational speed for the server port. Valid values include "Auto", "Preferred", and "Custom". The default value is "Preferred". If the speed type is "Auto", the maximum port speed is determined by the maximum configured speed for the network. If the speed type is "Preferred", the speed of the network is the same as the preferred speed of the network to which the connection is associated. If no preferred speed is configured for a network, it defaults to "Auto". If the speed type is "Custom", the user can configure any speed from 100Mb-MAX Configured speed for the network in 100Mb increments. PXE Shows whether PXE is enabled, disabled, or USE BIOS is selected on that port. Only one port can have PXE enabled for VC controlled addresses. MAC Type of MAC address assignment configured for the Virtual Connect domain Delete When the X in the column is bold, this line item is eligible for deletion. FC SAN Connections (Physical ports) Port Relative order of the Fibre Channel port on the server receiving the profile Connected to Bay number of the VC FC module to which the port is connected FC SAN name Name of the SAN fabric to which the port is connected, or Unassigned Status Status of the Fibre Channel module port connected to the server HBA port Port speed Speed of the VC-FC module port connected to the server HBA port WWPN Type of WWN address assignment configured for the Virtual Connect domain Assign Profile to Server Bay Power Icon indicates if the server blade is powered on or off (when a server is selected) Server Bay Assignment Displays the enclosure name, bay number, and type of server blade S/N Serial number of the server blade in the device bay Model Model name of the server blade in the device bay Status Status of the server blade in the device bay UID Icon indicates if the server blade UID is on or off

The following table describes the available actions in the Define Server Profile screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Create a profile name Enter a name in the Profile Name field. Select to use server factory Click Advanced.... defaults for Ethernet MAC addresses Select to use server factory Click Advanced.... defaults for Fibre Channel WWNs

Server management 148

Task Action

Select to use factory defaults for Click Advanced.... serial numbers (logical) Assign a Network Name 1 Click the drop-down arrow in the Network Name field. 2 Select a network from the previously defined networks. You can also select multiple networks. See "Multiple network connections for a server port (on page 151)."

Change the port speed setting 1 Click the drop-down arrow in the Port Speed Setting Column. 2 Select Preferred, Auto, or Custom. If Custom is selected, set the port speed, and then click OK.

Enable or disable PXE, or Use 1 Click the drop-down arrow in the PXE column. BIOS 2 Select Enabled or Disabled. If the existing PXE configuration on the server is correct, the 'Use BIOS' PXE setting should be chosen. This setting is the default. Delete an Ethernet Network Click the Delete icon in the delete column of the line item to be removed. Connection The first two connections cannot be deleted. Add Network Connection Click Add Network Connection. Change the SAN fabric Click the drop-down arrow in the FC SAN Name box. Multiple fabrics can connection be selected. Change or disable the port Click the drop-down arrow in the Port Speed box. speed View Fibre Channel Boot Click the Show Fibre Channel Boot Parameters checkbox. Parameters

Enable Fibre Channel Boot on a 1 Click the Show Fibre Channel Boot Parameters checkbox. port 2 Click the drop-down arrow in the SAN Boot box. 3 Select the boot order. 4 Enter a valid Boot Target name and LUN in the edit boxes.

Disable Fibre Channel Boot on a 1 Click the Show Fibre Channel Boot Parameters checkbox. port 2 Click the drop-down arrow in the SAN Boot box. 3 Select Disabled.

Revert to BIOS settings for Fibre 1 Click the Show Fibre Channel Boot Parameters checkbox. Channel Boot 2 Click the drop-down arrow in the SAN Boot box. 3 Select Use BIOS.

Change the profile bay 1 Click Select Location in the Server Bay Assignment column. assignment 2 Select the device bay or Unassigned. Clear unsaved changes on the Click Clear. screen Save changes and return to the Click Apply. Server Profile screen Cancel without saving changes Click Cancel. and return to the All Server Profiles screen

Server management 149

Advanced Profile Settings MAC addresses for the domain are provided by Virtual Connect. You can override this setting and use the MAC addresses that were assigned to the hardware during manufacture by selecting the Use Server Factory Defaults for Ethernet MAC addresses checkbox. This action applies to every Ethernet connection in the profile. For additional information, see "MAC Address Settings (on page 76)." WWNs for the domain are provided by Virtual Connect. You can override this setting and use the WWNs that were assigned to the hardware during manufacture by selecting the Use Server Factory Defaults for Fibre Channel WWNs checkbox. This action applies to every Fibre Channel connection in the profile. For additional information, see "WWN settings (on page 86)." Serial numbers (logical) for the domain are provided by Virtual Connect. You can override this setting and use the serial numbers that were assigned to the hardware during manufacture by selecting the User Server Factory Defaults for Serial Numbers (Logical) checkbox. This action applies to this profile. For additional information, see "Serial Number (Logical) Settings (on page 164)."

Defining a Server Profile If VC-assigned MAC addresses, WWNs, or non-default Fibre Channel boot parameters are being used, the affected server blades must be powered off before assigning a profile. To power off a server blade, see "Server Bay status screen (on page 218)." To define a server profile, use the following steps: 1. Enter the server profile name.

Server management 150

The server profile name can be up to 64 characters in length (no spaces). Because the server profile can be assigned to different locations, HP recommends that the name reflect the server function. The profile can be renamed at any time. 2. Setup Ethernet Network Connections for ports 1 and 2. Do the following for each port: a. Click the down arrow under Network Name to select an available Ethernet network. b. To override the current PXE settings on the server, click the down arrow under PXE and select Disabled or Enabled. Only one port can have PXE enabled by Virtual Connect on a server blade. However, if the default 'Use BIOS' setting is selected, the settings currently in the server BIOS are used. The 'Use BIOS' selection can allow more than one NIC port (on mezzanine cards only) to have PXE enabled. Only one embedded NIC can have PXE enabled. The MAC field indicates whether the profile will be using a server factory default or a VC-defined MAC address. VC-defined MAC addresses are not assigned until the profile is created. PXE allows an Ethernet port to be used for a network boot. PXE should only be enabled on a port that is connecting to a network with an appropriately configured PXE environment. 3. If the server will use more than two network connections, click Add Network Connection, and then select the appropriate network. When additional network connections are added, the X in the Delete column becomes active for those new connections. Click the X to delete additional network connections from the list. 4. If the VC domain contains VC-FC modules, set up the Fibre Channel connections (there will be two Fibre Channel connections for each set of horizontally adjacent interconnect bays in the enclosure that contain VC-FC modules). Do the following for each port: a. Click the down arrow under FC SAN connection to select an available SAN. b. Click the down arrow under Port Speed to select Auto, 2Gb, 4Gb, or Disabled for that port. Auto is the default. 5. To modify the Fibre Channel boot parameters, select the Show Fibre Channel Boot Parameters checkbox. See "Fibre Channel boot parameters (on page 157)." 6. To assign the server profile to a device bay (this step may be deferred), click the down arrow next to Select Location to select an enclosure and bay number. If a server blade is present in the selected location, it must be powered off for the profile to be saved and assigned properly. For complete information on server power requirements when assigning or removing server profiles, see "Server profile troubleshooting (on page 163)." 7. Click Apply.

Multiple network connections for a server port Server port connections to virtual networks are defined on the Define Server Profile screen (on page 146). Previous to Virtual Connect Manager v1.31, each server port could only be connected to a single virtual network. With v1.31 and higher, each server port can be connected to multiple virtual networks, each using a unique server VLAN ID for virtual network mapping.

Server management 151

To use this shared server links feature, select 'Multiple Networks...' from the drop-down list under Ethernet Network Connections (Physical ports). This option is available only if the 'Map VLAN Tags' option is selected on the Ethernet Settings (Advanced Settings) screen (on page 115). When the 'Multiple Networks' option is selected, a separate window is displayed to enable the defining and editing of virtual networks and VID mappings.

Server management 152

A window is displayed to select additional options.

Server port connections to virtual networks are defined on the Define Server Profile screen (on page 146). Previous to Virtual Connect Manager v1.31, each server port could only be connected to a single virtual network. With v1.31 and higher, each server port can be connected to multiple virtual networks, each using a unique server VLAN ID for virtual network mapping. To use this shared server links feature, select 'Multiple Networks...' from the drop-down list under Ethernet Network Connections (Physical ports). This option is available only if the 'Map VLAN Tags' option is selected on the Ethernet Settings (Advanced Settings) screen (on page 115). When the 'Multiple Networks' option is selected, a separate window is displayed to enable the defining and editing of virtual networks and VID mappings.

Defining server VLAN mappings Forced VLAN Mappings If the 'Force same VLAN mappings as Shared Uplink Sets' option is selected, server VLAN mappings are the same as the shared uplink set VLAN mappings. Users can choose only from a list of shared uplink sets when selecting Multiple Networks. After selecting a shared uplink set from the drop-down list, a list of vNets that belong to the chosen shared uplink set is displayed. Next to each network is a checkbox to allow the user to select or deselect individual networks to be connected to the server. If the shared uplink set has more than 28 networks, only the first 28 are selected to enforce the maximum number of VLAN mappings supported on a server. The server VLAN mappings are the same as those used on the shared uplink set, which are automatically displayed and cannot be changed. One of the networks can also be selected as the 'Untagged' network,

Server management 153

which means that untagged packets are placed on that vNet, and the VC-Enet module also transmits untagged to the server for that network. The 'untagged' network defaults to be the 'Native' network, but it does not have to be the same as the 'Native' network on the shared uplink set. In fact, each server port can designate a different untagged network. The external VLAN mapping is ignored when the network is untagged. With this 'forced' option selected, the server connection VLAN mappings are linked to the chosen shared uplink set. Any change to the uplink VLAN mappings is reflected automatically on the server connection using those shared uplink set VLAN mappings. Therefore, to minimize network outage time, any VLAN mapping changes to the uplinks requires immediate changes being made to the VLAN tagging on the servers.

No Forced VLAN Mappings If the 'Force same VLAN mappings as Shared Uplink Sets' option is not selected, users can choose available networks and assign a unique server VLAN associated with the network for this server port. Not forcing VLAN mappings provides greater flexibility in selecting the set of networks to connect to each server port, and enables administrators to specify server VLAN mappings independent of those assigned by the network administrator for the shared uplink sets. The untagged option is always available, but it might be unassigned, that is, any untagged frame from the server is dropped. Each network can be selected only once per server port. Similarly, each server-assigned VLAN must be unique per server port. This option is not available if the domain-wide 'Force server connections to use the same VLAN mappings as shared uplink sets' checkbox on the Advanced Settings tab of the Ethernet Settings screen is selected. If the selected network is part of a shared uplink set, it has an associated external VLAN mapping. This external VLAN is used to pre-populate the server-assigned VLAN entry to maintain consistency throughout the VC domain. However, multiple networks on different shared uplink sets can have the same external

Server management 154

VLAN mapping. If those networks are selected for the same server port, the user must edit the server VLAN to ensure all VLANs are unique for each server port. Server VLAN mappings are not linked to the uplink VLAN mappings. If a pre-populated server VLAN mapping is accepted, and later the uplink VLAN mapping is changed, the changes are not propagated to the server side. Finally, to simplify configuration, a "Copy From…" button is available to copy existing network mappings from a shared uplink set or from other server ports.

VLAN ID mapping guidelines • For each server port, all VLAN mappings must be unique. When the 'Force same VLAN mappings as Shared Uplink Sets' option is selected, this setting is handled automatically because all networks within a shared uplink set must have unique VLAN IDs. If the global 'Force same VLAN mappings as Shared Uplink Sets' option is not selected, then each network can only be mapped to one server VLAN (including untagged). After being mapped, a network is no longer available in the drop-down list of available networks. • Different server VLANs can be mapped to the same network between two different server ports. For example, in server port 1, server VLAN 100 maps to the Purple network. In port 2, server VLAN 200 also maps to the Purple network. The result is that these different server VLANs can communicate with each other directly, and a broadcast frame on VLAN 100 from server port 1 is sent into the VC Domain and comes out to VLAN 200 on server port 2. This behavior extends to any number of different server VLANs mapped to the same vNet in any given VC Domain. • The same server VLAN can be mapped to two different networks. This action has a similar but opposite effect to the above scenario. For example, server VLAN 300 is mapped to the Green network on server port 1, but mapped to the Red network on server port 2. This mapping means that server VLAN 300 is split into separate broadcast domains for different server ports.

Server management 155

• If an external VLAN is "Unassigned," packets with that tag are dropped, which is the same as if that external VLAN was never specified. However, this setting allows users to pre-define or reserve a spot for that VLAN and activate it later by connecting it to a VC Ethernet network. Copying VLAN mappings Server network mapping is similar to the set of networks defined under a shared uplink set. The only difference is that when defining a shared uplink set, the networks are created in the Virtual Connect Domain along with options such as "Native VLAN", "Smart Link", and so on, while defining server network mappings does not result in creation of any networks in the VC Domain. Because of this similarity, a Copy From… button is available to copy a set of existing external VLAN to network mappings from a shared uplink set into a server port's mappings. The network designated as "Native VLAN" in a shared uplink set by default accepts untagged or tagged frames from external switches, but VC Manager always transmits tagged frames from this vNet out to external switches. When used as server mapping, this behavior is reversed. By default, VC transmits untagged frames to the server from the Native VLAN, that is, the Native VLAN is copied as the "untagged" option for a server port. To change this default, simply set the "untagged" option to be "Unassigned" and manually add a new mapping for the Native VLAN. Because shared uplink sets can support up to 32 networks and server ports are restricted to 28 mappings, only the first 28 mappings of a shared uplink set are copied. It is also possible to copy VLAN mappings from a server profile. To copy VLAN mappings, click Copy From.... Select Profile or UplinkSet from the dropdown list, and then select from the available options to copy the VLAN mappings.

Server management 156

Fibre Channel boot parameters Virtual Connect Manager supports setting Fibre Channel boot parameters and enable/disable of Fibre Channel boot. This change can be made when running the Fibre Channel Setup Wizard, or from the Define a Server Profile screen ("Define Server Profile screen" on page 146). To access the Fibre Channel boot parameters, select the Show Fibre Channel Boot Parameters checkbox. There are four SAN Boot options: • Use BIOS/EFI (default)—SAN boot settings are not configured by Virtual Connect Manager. BIOS settings are used. • Primary—Port is enabled for SAN boot, and is first in the boot order. • Secondary—Port is enabled for SAN boot, and is second in the boot order. • Disabled—Port is disabled for SAN boot.

IMPORTANT: If Use BIOS is not selected, any parameters set on this screen override the settings used in other tools, such as RBSU.

A server blade must be powered on at least once with the mezzanine cards installed before Virtual Connect can properly set the device boot order. The BIOS must first discover the local devices before Virtual Connect can properly configure the boot order. When a server blade is first powered on after profile assignment, any Fibre Channel HBA ports that have SAN boot enabled are configured. However, it may require a subsequent reboot for the boot controller order to be set correctly. If the boot settings are changed in the RBSU, the Virtual Connect specified boot settings are not re-applied until the server has completed POST. If SAN boot is enabled for a port, be sure that the Target Port Name and LUN are entered correctly. For additional information on SAN boot parameters, see the HP website (http://www.hp.com/go/storage).

Server management 157

Server Profiles screen This screen lists all server profiles that have been defined within the domain, including assigned and unassigned profiles. From this screen, users can see the assigned device bays, NIC MAC addresses, FC HBA WWNs, network connections, and Fibre Channel Fabric and Boot Parameters for all server profiles as well as generate a printable report of this information. Users with network privileges can create a new profile based on an existing profile or edit inline many attributes of the server profiles.

The following table describes the columns and fields within the Server Profiles screen.

Column Description

Profile Status and name of each server profile Power Power status of the server in Server location Server bay assignment The location of the device bay to which the server profile is assigned Port The port number and type within the server profile MAC/WWN MAC address assigned to the Ethernet port or WWPN assigned to the Fibre Channel HBA port LAN/SAN The network connection for the Ethernet port or SAN Fabric for the Fibre Channel HBA port

The following table describes the available actions within the Server Profiles screen.

Server management 158

Task Action

Show all profiles, only assigned Click the down arrow in the Show: box. profiles, or only unassigned profiles Define a new profile Click Define Profile or select Server Profile from the Define menu at the top of the screen. View a printable report Click the View Printable Report icon. Refresh the screen information Click Refresh. Clear current changes without Click Clear. saving Save changes and remain on this Click Apply. screen Edit a server profile For detailed editing, click on that profile in the list to go to the Edit Server Profile screen, or click on the Inline Edit icon to make edits to the profile without leaving the current screen. See "Edit a Server Profile (Inline) (on page 162)." Copy a server profile Click the Copy icon in the line of the server profile to copy, or click on the server profile to go to the Edit Server Profile screen. Then, click Copy Profile. Delete a single server profile Click X in the line of the profile to delete. Delete one or more server profiles Select the checkbox at the left of each line item to be deleted, and then click Delete.

Edit a Server Profile (single profile) screen Use this screen to edit the properties of an existing server profile. This screen enables you to do the following: • Change the profile name • Add, delete, or change network connections • Change the network port speed settings • Enable or disable PXE • Modify Fibre Channel connection settings (if there are one or more VC Fibre Channel modules in the Virtual Connect domain) • Assign, unassign, or re-assign the profile to a device bay • Copy the profile • Delete the profile If VC-assigned MAC addresses, WWNs, or non-default Fibre Channel boot parameters are being used, the server blade must be powered off before any server side changes can be made. To power off a server blade, see "Server Bay Status screen (on page 218)." Changes to Ethernet network and Fibre Channel fabric settings can be made without powering down the server. For complete information on server power requirements when assigning or removing server profiles, see "Server profile troubleshooting (on page 163)." The screen can be edited only by users with server privileges, but it is viewable by all authorized users.

Server management 159

TIP: Server profiles can also be edited from the Server Profiles screen (on page 158).

The following table describes the fields within the Edit Server Profile screen.

Column name Description

Profile Profile Name Descriptive name for the server profile. Do not use spaces. Status Status of the server profile Ethernet Network Connections (Physical ports) Port Relative order of the Ethernet port on the server receiving the profile. System board NICs are first in the order, followed by NICs on mezzanine cards Network Name Name of the network associated with this port selected from list of defined networks Status Status of the network

Server management 160

Column name Description

Port Speed Setting The requested operational speed for the server port. Valid values include "Auto", "Preferred", and "Custom". If the speed type is "Auto", the maximum port speed is determined by the maximum configured speed for the network. If the speed type is "Preferred", the speed of the network is the same as the preferred speed of the network to which the connection is associated. If no preferred speed is configured for a network, it defaults to "Auto". If the speed type is "Custom", the user can configure any speed from 100Mb-MAX Configured speed for the network in 100Mb increments. Allocated Bandwidth Allocated bandwidth of the port. See Bandwidth assignment (on page 144). PXE Enables or disables PXE on the network connection. Valid values are "enabled", "disabled", and "UseBios". If this value is not specified, the default is "UseBios". Only one connection can have PXE enabled per profile. MAC The MAC address assigned to the port, or "Server Factory Default" if not using VC-assigned MAC addresses Mapping Server hardware mapping assignment. See Port assignment (on page 143). Delete When the X in the column is bold, this line item is eligible for deletion. FC SAN Connections (Physical ports) Port Relative order of the Fibre Channel port on the server receiving the profile Connected to Bay number of the VC-FC module to which the port is connected FC SAN name Name of the SAN fabric to which the port is connected, or Unassigned Status Status of the Fibre Channel module Port speed Speed of the VC-FC module port connected to the port WWPN The World Wide Port Name assigned to the port or Server Factory Default if not using VC-assigned MAC addresses Delete When the X in the column is bold, this line item is eligible for deletion. Assign Profile to Server Bay Power Icon indicates if the server blade is powered on or off (when a server is selected). Server Bay Assignment Displays the enclosure name, bay number, and type of server blade S/N Serial number of the server blade in the device bay Model Model name of the server blade in the device bay Status Status of the server blade in the device bay UID Icon indicates if the server blade UID is on or off.

The following table describes the available actions in the Edit a Server Profile screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Edit a profile name Type a name in the Profile Name field.

Server management 161

Task Action

Assign a Network Name Click the drop-down arrow in the Network Name field and select a network. Change the port speed setting Click the drop-down arrow in the Port Speed Setting column, and then select Preferred, Auto, or Custom. If Custom is selected, set the port speed, and then click OK. Enable or disable PXE, or use Click the drop-down arrow in the PXE column and select enabled, disabled, the Use BIOS setting or Use BIOS. Delete an Ethernet Network Click the Delete icon in the Delete column of the line item to be removed. Connection The first two Ethernet connections cannot be deleted. Add Network Connection Click Add Network Connection. Change the SAN fabric Click the drop-down arrow in the FC SAN name box. connection Change or disable the port Click the drop-down arrow in the Port Speed box. speed View Fibre Channel Boot Click the Show Fibre Channel Boot Parameters checkbox. Parameters Enable Fibre Channel Boot on a Click the Show Fibre Channel Boot Parameters checkbox. Click the drop- port down arrow in the SAN Boot box, and then select the boot order. Enter a valid Boot Target name and LUN in the edit boxes. Disable Fibre Channel Boot on a Click the Show Fibre Channel Boot Parameters checkbox. Click the drop- port down arrow in the SAN Boot box, and then select Disabled. Revert to BIOS settings for Fibre Click the Show Fibre Channel Boot Parameters checkbox. Click the drop- Channel Boot down arrow in the SAN Boot box, and then select Use BIOS. Change the profile bay Click Select Location in the Server Bay Assignment column, and then select assignment the server bay or Unassigned. Delete the profile Click Delete. Copy the properties of this Click Copy Profile. profile to use in creating a new profile Clear unsaved changes on the Click Clear. screen Save changes and remain on Click Apply. this screen Cancel without saving changes Click Cancel. and return to the All Server Profiles screen

Edit a Server Profile (Inline) The Server Profiles screen allows for inline editing of one or more server profiles. Select the Edit icon to the right of each server profile name to be edited. When the Edit icon is selected, that table row enables authorized users to assign, unassign, or re-assign the server profile as well as modify the network connections.

Server management 162

When multiple changes have been made, all may be applied by clicking Apply at the bottom of the screen. To save the changes for an individual row, click the Save icon within the row. Clicking the Cancel icon removes the row from edit mode and cancels any changes that have been made. See "Other icon definitions (on page 63)."

View printable report This report is available on the Server Profiles screen (on page 158), and lists the set of profiles that have been defined in the Virtual Connect domain: • To filter the report for only assigned or unassigned profiles, click the down arrow in the Show: box. • To print the report, click the print icon. • To close the window and return to the Server Profiles screen, click Close.

Server profile troubleshooting Certain server profile changes require the server blade in the device bay to be powered off before the change can be made. HP recommends that servers be powered off using the server console before attempting such operations within the Virtual Connect Manager. The Virtual Connect Manager also provides an opportunity to power off the server blade before such operations. A server blade must be powered off if any changes are made that require modifications to the server. Network or Fabric changes do not require the server blade to be powered off. Server side settings include:

Server management 163

• Assigning a VC- or user-defined MAC address • Changing the PXE setting • Assigning a VC-defined WWN • Changing the Fibre Channel boot parameters

IMPORTANT: The server blade must be powered off for all profile changes if there is a Flex-10 NIC in the server, and the server is connected to an HP Virtual Connect Flex-10 Modules or in an empty bay.

If any of the above settings are changing, the server must be powered off before the profile action can occur. If the server blade is not powered off, a message is displayed and no changes are made. In this case, power off the server blade and repeat the action. When server side settings are changing, operations that require server blades to be powered off include the following: • When assigning a profile to a server blade already installed in a device bay • When deleting a profile, moving a profile to a different device bay, or un-assigning a profile from the existing bay • When making modifications to a profile that affect settings on the server blade (e.g., PXE enable/disable, changing the number of connections, or changing Fibre Channel boot parameters) Changing the network connected to an already defined Ethernet port, changing the Fabric connected to a Fibre Channel port, or changing the speed of a Fibre Channel port can be done without powering off the server blade. In addition, if server factory defaults are used for MAC addresses and WWNs, and BIOS Fibre Channel boot settings are used, the profile can be assigned or un-assigned without powering down the server blade. In some cases, server profiles can be assigned to server blades when certain mismatches between the server profile definition and the server blade exist. The following list summarizes Virtual Connect behavior under these circumstances: • If the number of Network connections in the profile is more than the number of physical Ethernet ports, the profile is assigned, but a warning message appears. • If a non Virtual Connect Ethernet switch is connected to any port in the profile, the profile is assigned, but the MAC address is not changed on the NIC. A warning message appears. • If the number of Fibre Channel connections in the profile is more than the number of physical Fibre Channel HBA ports, the profile is assigned, but a warning message appears.

NOTE: The BL860c server blade does not support configuration of Fibre Channel boot parameters or PXE settings via Virtual Connect. Other Virtual Connect server profile settings will be configured properly when using the appropriate BL860c firmware.

Serial Number (Logical) Settings The serial number (logical) setting feature enables users to add a serial number (logical) and UUID (logical) to server profiles. By configuring Virtual Connect to assign serial numbers (logical), a profile can present a single serial number regardless of the physical server. With these configuration values added to server profiles, software that is licensed to a particular server, based on one or both of these values, can

Server management 164

be migrated to new server hardware without re-licensing the software for the new server hardware. This features prevents the user from having to reinstall serial number sensitive software after a system recovery. If a user needs to access the physical serial number of a server blade, the OA displays both the physical and serial numbers (logical). After server profile creation, the following guidelines apply: • Serial numbers (logical) can be changed from factory default to VC-assigned. • Factory default serial numbers cannot be changed to serial numbers (logical). • User-defined serial number (logical) ranges can be expanded. • User-defined serial number (logical) ranges cannot be reduced. • All components must be at the required versions or the feature does not function: o OA, v2.20 or higher o iLO, v1.60 or higher For additional information on required firmware versions and to download firmware upgrades, see the HP website (http://www.hp.com/go/bladesystemupdates).

Server management 165

Domain management

Domain overview A Virtual Connect domain currently includes a single HP c-Class BladeSystem c7000 Enclosure for a total of 16 servers (or up to 32 servers if the double-dense option is enabled), or a single HP c-Class BladeSystem c3000 Enclosure for a total of 8 servers (or up to 16 servers if the double-dense option is enabled). Within the domain, any server blade can access any LAN or SAN connected to a VC module, and a server blade can be used as a spare for any server blade within the same enclosure. By stacking (cabling) the Ethernet modules within the domain and connecting the FC modules to the same set of FC SAN(s), every server blade in the domain can be configured to access any external network connection. With this configuration, the Virtual Connect Manager can deploy and migrate a server blade profile to any server in the Virtual Connect domain without the need to change external LAN or SAN configurations.

Enclosure serial numbers The enclosure serial number is used by the Virtual Connect Manager to associate a Virtual Connect domain with a particular enclosure. The enclosure serial number can be altered for maintenance purposes, such as when replacing the enclosure midplane. For more information, see SET ENCLOSURE SERIAL_NUMBER in the HP BladeSystem Onboard Administrator Command Line Interface User Guide. Enclosure serial numbers are unique as shipped from the factory, and must remain unique for proper Virtual Connect Manager operation. Use care when altering the enclosure serial number to ensure that serial numbers are unique within the management network.

Domain Settings (Domain Configuration) screen Use this screen to change the domain name or delete a domain. The Remove from Domain feature (also known as administrative removal) enables users to remove an interconnect module from the Virtual Connect domain without having to delete the entire domain, or having the bay permanently configured for a specific interconnect module type. After an Ethernet module has been physically removed from the enclosure and none of its ports are part of an Ethernet network and/or Shared Uplink Set, the module can be removed from the Virtual Connect domain. A FC module can be administratively removed when none of its fabrics are in use by a profile.

Domain management 166

For additional information, see "Interconnect Bay summary screen (Ethernet module) (on page 198)" and "Administrative module removal (on page 210)."

The following table describes the available actions in the Domain Settings (Domain Configuration) screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Change the domain name Enter the revised domain name, and then click Apply. Display single-dense server bays Click the checkbox next to the appropriate selection. Available if double-dense compatibility is selected during import. Delete a domain Verify that the correct domain name is displayed, and then click Delete Domain. See "Deleting a domain (on page 167)." Save changes and remain on this screen Click Apply. Clear the enclosure checkboxes Click Cancel.

Deleting a domain

CAUTION: Deleting a domain returns all settings to factory default. This action cannot be undone.

1. Power off all servers that are associated with profiles. See "Server Bay Status screen (on page 218)." 2. Navigate to the Domain Settings (Domain Configuration) screen (on page 166).

Domain management 167

3. Click Delete Domain. A domain name verification window is displayed. 4. Enter the name of the domain to be deleted. This should be the name of the domain you are currently logged into, displayed in the Virtual Connect Domain Name box on the Domain Settings (Domain Configuration) screen (on page 166). 5. Click OK.

Domain Settings (Domain IP Address) screen Use this screen to set a domain IP address for the Virtual Connect domain. The optional domain IP address setting allows for a consistent IP address that is independent of the interconnect module on which it is running. If set, this IP address must be unique within the network and must be different than the IP address of the module itself. If this IP address is not set, the VC Manager can still be reached through the IP address of the host Virtual Connect Ethernet module. To use an optional domain IP address, select the Use Domain IP address checkbox, and then enter the IP Address, Subnet Mask, and Default Gateway.

NOTE: Even if a domain IP address is provided, the normal IP address assigned to the interconnect bay can still be used.

The following table describes the available actions in the Domain Settings (Domain IP Address) screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Domain management 168

Task Action

Use a domain IP address Select the box next to Use Domain IP address, and then enter the IP Address, Subnet Mask, and Gateway. Clear unsaved changes on the screen Click Clear. Save changes and remain on this screen Click Apply. Cancel without saving changes Click Cancel.

Domain Settings (Domain Enclosures) This screen displays information about the domain enclosure.

Domain Settings (Backup/Restore) screen Use this screen to create a backup file of the Virtual Connect domain configuration or to restore a configuration that has been lost. The domain configuration includes network definitions, MAC address settings, WWN settings, Fibre Channel fabric settings, local user accounts, and server profile definitions. The backup file stores the same information that is check-pointed between the active and standby modules during normal operation.

IMPORTANT: Virtual Connect Manager cannot use backup configurations created with previous versions of Virtual Connect Manager. For example, if you are currently using v2.00, you cannot use a backup configuration that was created using v1.20.

Domain management 169

Use the following steps to back up a domain configuration: 1. Click Backup Configuration. 2. Navigate to the hard drive location for the backup file. 3. Name the file (usually the domain name), and then click Save. Use the following steps to restore a domain configuration: 1. Enter or browse to the backup file. 2. Select the file. 3. Select the "Ignore enclosure serial number in restored configuration file" checkbox if you want to restore a configuration that was generated on another enclosure. If this is not selected, a configuration generated on another enclosure is rejected. 4. Select the "Disallow restore of 1.1x configuration file" checkbox if you want to restore the firmware to a revision other than what is stored in the configuration file. 5. Click Restore Configuration. 6. Confirm the domain configuration to be restored, and then click OK.

Domain Settings (Firmware Management) screen To update the Virtual Connect Ethernet module firmware, select Firmware Update from the Tools pull-down menu, or click Firmware Management in the left window.

Domain management 170

The automated firmware update process simplifies administration and minimizes network downtime and outage by upgrading and activating all non-Active Virtual Connect Ethernet modules in an optimized manner. To maximize availability of the connections between server blades and networks, horizontally adjacent modules (for example, bays 3 and 4) are never activated simultaneously. After all non-Active Virtual Connect Ethernet modules and VC-FC modules are fully upgraded, the Active Virtual Connect Ethernet module is activated for a brief network outage. Upon activation, the Virtual Connect Manager performs a failover to the Standby Virtual Connect Ethernet module, which is already fully upgraded and operational. You will be prompted to log in again. To begin an automated update, click Automated Update. To retain full control of the firmware update process, you can use the individual Update/Activate buttons for each of the Virtual Connect Ethernet modules and VC-FC modules.

IMPORTANT: HP recommends that all VC-Enet modules in the domain are at the same revision level. Some versions of the Virtual Connect firmware might not be compatible. The active Virtual Connect Manager does not allow incompatible modules to be managed as part of the Virtual Connect domain.

To update firmware: 1. Select an update package using one of the following methods: o Enter a local file name in the File field, or click Browse to find a local file, and then click Upload. o Enter the URL location of the firmware update, and then click Apply. When the file transfer is complete, a dialog box displays, "Successfully uploaded." 2. Click OK. The Firmware Management screen appears.

Domain management 171

TIP: Click on the firmware description link to view release notes for this version.

3. Update the firmware using one of the following methods: o Click Automated Update. o Click Update in the row of each module to be updated. The screen displays the progress of the file being transferred and installed. When complete, the Update button is replaced with an Activate button. Click Activate to complete the firmware update. The module is rebooted and brought on line. Network traffic can be affected during the activation step because that module is unavailable.

IMPORTANT: The active module cannot be activated until the Standby VCM is activated. The Activate button is disabled for the currently active module until the Standby VCM is successfully activated. When the process is complete, the active module can be activated. The Active VCM will transition to the standby before the activation process is started on the active module.

Domain Settings (Local Users) screen

Domain management 172

The following tasks can be performed on this screen: • To create a new local user account, click Add User. The User Settings screen is displayed. • To edit attributes of a defined local account, select the user name from this screen. • To delete a user account, click the Delete icon for that line item. • To enable strong passwords or enable local users, click Advanced.

Column Description

User Name The user name must begin with a letter and is case sensitive.

Domain management 173

Column Description

Privileges Shows what privileges the user has (Domain, Network, Storage, and/or Server) Full Name The user's full name. All users can modify their own full name. Contact Contact information for the user account. The contact information can be the name of an individual, a telephone number, or other useful information. All users can modify their own contact information. Account Status Shows whether a user account is enabled or disabled. Delete Displays the Delete icon. Click the icon to delete that line item.

The following table describes the available actions in the Domain Settings (Local Users) screen. Clicking another link in the pull-down menu or left navigation window causes current edits that have not been applied to be lost.

Task Action

Edit user properties Click on that user in the User Name column. Add a new user Click Add User. Enable or disable strong passwords Click Advanced. Enable or disable local users Click Advanced. Return to the HP Virtual Connect Click Cancel. Manager homepage

Domain management 174

Add new user

Domain management 175

o Update firmware o Administer SSL certificates o Delete the VC domain o Save configuration to disk o Restore the configuration from a backup • Networking o Configure network default settings o Select the MAC address range to be used by the VC domain o Create, delete, and edit networks o Create, delete, and edit shared uplink sets • Server o Create, delete, and edit server Virtual Connect profiles o Assign and unassign profiles to device bays o Select and use available networks o Select serial numbers (logical) and UUIDs (logical) to be used by server profiles o Power on and off server blades within the enclosure • Storage o Select the WWNs to be used by the domain o Setup the connections to the external FC Fabrics It is possible to create a user with no privileges. This user can only view status and settings.

Domain management 176

Directory Settings (Directory Server) screen This screen enables Administrators to set up an LDAP server to authenticate users accessing the CLI based on user name, password, and role. Beginning with version 1.31 of Virtual Connect Manager, users can test an LDAP configuration before applying it. See, "Test LDAP authentication (on page 180)."

The following table describes the fields within the Directory Settings (Directory Server) screen.

Field Description

Enable LDAP Authentication Select to enable LDAP authentication Enable Local Users Select to enable local users Directory Server Address The IP address or the DNS name of the domain of the directory service. Directory Server SSL Port The port used for LDAP communications. The default port is port 636. Search Context 1 First searchable path used to locate the user when the user is trying to authenticate using directory services. Search Context 2 Second searchable path used to locate the user when the user is trying to authenticate using directory services. Search Context 3 Third searchable path used to locate the user when the user is trying to authenticate using directory services. Use NT Account Name Select to use NT account name mapping Mapping (DOMAIN/Username)

Domain management 177

Directory Settings (Directory Groups) screen Use this screen to manage the Directory Group settings for Virtual Connect Manager.

The following table describes the fields within the Directory Settings (Directory Groups) screen.

Field Description

Checkbox Used to select Directory Group for editing or deleting Group Name This is the Directory Server group name. Microsoft Active Directory servers have a reverse mapping from the user to the groups the user is a member of. Other servers might need to combine the Group Name with a Search Context to look up the group, to determine if the user is a member of the group. To open the Edit LDAP Group window, click the Group Name. Starting with Virtual Connect v1.31, nested group memberships (groups that are members of groups) are searched to a depth of up to four levels when determining group membership. Privilege Level Zero or more privileges (Domain, Network, Storage, Server) assigned to the group. A user can be a member of multiple groups, in which case the privileges are cumulative. If the user is only a member of a group (or groups) with no privileges, the user can log in and view the Virtual Connect configuration, but can not make any changes. If a user is not a member of any group, the user can not log in. Description A text description for the group.

To remove a group from the configuration, click the Delete icon. To open the Add LDAP Group page, click New.

Domain management 178

Add LDAP Group Use this screen to add a Directory Group.

The following table describes the fields within the Add LDAP Group screen.

Field Description

Group Name This is the Directory Server group name. Microsoft Active Directory servers have a reverse mapping from the user to the groups the user is a member of. Other servers might need to combine the Group Name with a Search Context to look up the group, to determine if the user is a member of the group. Starting with Virtual Connect v1.31, nested group memberships (groups that are members of groups) are searched to a depth of up to four levels when determining user group membership. Privilege Level Select zero or more privileges (Domain, Network, Storage, Server) to assign to the group. Description A text description for the group.

To add the new group, click Add.

Directory Settings (Directory Certificate) screen Directory Certificates provide authentication of the Directory Server. There are two ways to verify the identify of the Directory Server: • Install certificates that complete a certificate chain to a root Certificate Authority.

Domain management 179

• Install a certificate that exactly matches the certificate provided by the Directory Server. To upload a certificate, select the certificate from the list, and then click Certificate Upload. If no certificates are installed, no authentication of the Directory Server is performed (although the connection to the Directory Server must be established using SSL). The following table describes the columns within the Directory Settings (Directory Certificate) screen.

Column Description

MD5 Fingerprint Unique fingerprint of the certificate, calculated using cryptographic hash function Message-Digest algorithm 5 (MD5). This fingerprint can be used to further verify that the correct certificate is being used. Version Version of the certificate Valid from The date and time when this certificate became valid Valid until The date and time when this certificate becomes invalid Delete Click X in the line of the certificate to delete.

Test LDAP authentication Beginning with v1.31 of Virtual Connect Manager, local users can test their LDAP configuration before making the configuration active. To test an LDAP configuration: 1. Be sure that LDAP group settings are configured. 2. Be sure that any LDAP certificates are installed. 3. Access the Directory Settings (Directory Server) screen (on page 177). 4. Enter the LDAP configuration information. 5. Click Test. 6. Enter a valid username and password. 7. Click Test.

Domain management 180

The status window displays problems encountered during the test, if any. When testing is complete, click Done.

SNMP and SMI-S overview SNMP is used by network management systems to monitor network-attached devices for conditions that warrant administrative attention. SNMP consists of a set of standards for network management, including an Application Layer protocol, a database schema, and a set of data objects. The SNMP configuration is controlled by the Virtual Connect Manager and applies to all modules in the VC domain. The SNMP agent software module residing on a primary module provides access to managed information using SNMP protocol. The managed information is presented as a hierarchical database called MIB. Each element of the managed information is identified by a unique identifier called Object ID. Basic SNMP support is provided for both the VC-Enet module and the VC-FC module. The ability to enable or disable SMI-S is available on the VC-FC module. The SMI-S was created by SNIA to standardize storage management solutions. SMI-S replaces multiple disparate managed object models, protocols, and transports with a single object-oriented model for each type of component in a storage network. SMI-S enables management applications (such as HP SIM) to support storage devices from multiple vendors quickly and reliably because they are no longer proprietary. SMI-S detects and manages storage elements by type, not by vendor. Users must have Administrative privileges to configure SNMP or SMI-S capabilities. The VC-Enet module supports the applicable groups of the following SNMP MIBs: • Compaq Host MIB

Domain management 181

• Compaq System Info MIB • RFC 3418 SNMPv2-MIB • RFC 2863 IF-MIB • RFC 4188 BRIDGE-MIB The VC-Enet module supports the following SNMP traps: • cpqHoSWRunningStatusChangeTrap from CPQ-HOST MIB The VC domain status has changed as described in the next section. • coldStart trap from SNMPv2-MIB CRITICAL—A coldStart trap signifies that the SNMP agent is reinitializing itself and that its configuration might have been altered. The VC-FC module supports the applicable groups of the following SNMP MIBs: • Compaq Host MIB • Compaq System Info MIB • Compaq Rack MIB The VC-FC module supports the following FC industry standard MIBs: • Fibre Alliance MIB • Fabric Element MIB The VC-FC module supports the following SNMP traps: • connUnitStatusChange (1.3.6.1.3.94.0.1) INFO—The overall status of the connectivity unit has changed. Status is sent when any of the following notifications occur: o Switch.OperChange o Switch.StateChange • connUnitDeletedTrap (1.3.6.1.3.94.0.3) INFO—A connUnit has been deleted from this agent. Status is sent when an Eport.OperChange event occurs and the connUnitTable is smaller than previously noted. • connUnitEventTrap (1.3.6.1.3.94.0.4) INFO—An event has been generated by the connectivity unit. Status is sent when a change notification occurs that does not fit into any other specific category. • connUnitSensorStatusChange (1.3.6.1.3.94.0.5) CRITICAL—The overall status of the connectivity unit has changed. Status is sent when any of the following notifications occur: o Chassis.PsBadAlarm o Chassis.PsOkAlarm o Chassis.FanBadAlarm o Chassis.FanOkAlarm o Blade.OverheatAlarm o Blade.OverwarmAlarm

Domain management 182

• connUnitPortStatusChange (1.3.6.1.3.94.0.6) INFO—The overall status of the connectivity unit has changed. Sent whenever any of the following notifications occur: o UserPort.StateChange o UserPort.OperChange • coldStart CRITICAL—A coldStart trap signifies that the SNMP agent is reinitializing itself and that its configuration might have been altered. • authenticationFailure CRITICAL—An authenticationFailure trap signifies that the SNMP agent has received a protocol message that is not properly authenticated.

VC domain status change notifications When a VC domain changes status, VC Manager generates a trap. The state changes are: • NORMAL—The component is fully functional. • CRITICAL—The component is incapable of managing installed VC components. • MAJOR—One or more of the component's subsystems are not operating properly, causing serious disruption to functions. • MINOR—One or more of a component's subsystems are not operating properly, causing slight disruption to functions. • WARNING—The component has a potential problem. • UNKNOWN—VC Manager has not yet established communication with the component.

SNMP Settings (SNMP Enet Settings) By enabling SNMP for VC-Enet modules, network management systems can monitor VC-Enet modules in the domain for events such as warnings and errors that might require corrective actions. The user must have network administrator privileges to administer SNMP Enet settings.

Domain management 183

The VC-Enet SNMP settings apply to all VC-Enet modules in the Virtual Connect domain.

The following table describes the fields within the SNMP Settings (SNMP Enet Settings) screen.

Field name Description

Enable SNMP Select to enable SNMP System Contact Specify contact name for this system when SNMP is enabled Read Community Controls SNMP read access when SNMP is enabled. The default value for read community string is "public". The read community string must always be set when SNMP is enabled. SNMP Alert Destinations SNMP trap destination table. Maximum number of trap destinations allowed is five. After entering an IP address and community string, click Add. To remove an IP address, highlight the address, and then click Remove. IP Address SNMP trap destination IP address Community String The Community String acts like a password for a given trap destination. The trap receiving application can use the community string to filter the incoming traps. Default: public

To apply changes made on this screen, click Apply.

Domain management 184

SNMP Settings (SNMP FC Settings) By enabling SNMP for VC-FC modules, network management systems can monitor the VC-FC modules in the domain for events such as warnings and errors that might require corrective actions. The user must have network administrator privileges to administer SNMP FC settings. The VC-FC SNMP settings apply to all VC-FC modules in the VC domain.

The following table describes the fields within the SNMP Settings (SNMP FC Settings) screen.

Field name Description

Enable SMI-S Select to enable SMI-S Enable SNMP Select to enable SNMP System Contact Specify contact name for this system when SNMP is enabled Read Community Controls SNMP read access when SNMP is enabled. The default value for read community string is "public". The read community string must always be set when SNMP is enabled. SNMP Alert Destinations SNMP trap destination table. Maximum number of trap destinations allowed is five. After entering an IP address and community string, click Add. To remove an IP address, highlight the address, and then click Remove. IP Address SNMP trap destination IP address

Domain management 185

Field name Description

Community String The Community String acts like a password for a given trap destination. The trap receiving application can use the community string to filter the incoming traps. Default: public

To apply changes made on this screen, click Apply.

System Log screen The System Log screen displays logged information of events within Virtual Connect Manager. To access the System Log screen, click on System Log in the left navigation pane, or select System Log from the Tools pull-down menu. Events are logged with the most recent event displayed at the end of the list. Use the scroll bar on the right of the screen to scroll through the list if it is longer than the display box. When the log reaches maximum capacity, the oldest logged event is automatically deleted as new events are added. Click Refresh to display the most current information.

Domain management 186

System Log Configuration

Use this screen to view or set remote log destination settings.

Column Description

Log host The IP address or the DNS of the configured remote log destination Log severity Severity of the log messages that should be sent to the specified destination. Valid values include "Critical", "Error", "Warning", and "Informational". Transport The transport protocol to be used for sending the log messages to the destination. Valid values include "TCP" and "UDP". Port The port to be used on the destination to send the log messages. Valid values include 1 to 65536. The default value is 514. Security Secure transmission of the log messages. Valid values include "None" and "STunnel". The default value is "None", and no encryption is used during transmission. The "STunnel" option can be used only if the transport protocol used is TCP. Date Format The timestamp format for the log messages. Valid values include "RFC3164" (Nov 26 13:15:55) and "ISO8601" (1997-07-16T19:20:30+01:00). The default value is "RFC3164". Enabled Enables or disables the remote log destination

To define a new remote log destination, click Define Target. To send a test message to all enabled remote log destinations, click Test.

Domain management 187

To delete a remote log destination, select the checkbox next the preferred destination, and then click Delete.

Domain management 188

Certificate Administration

Certificates/Authentications (SSL Certificate) screen This page displays the detailed information of the Secure Socket Layer (SSL) Certificate currently in use by the Virtual Connect Manager. An SSL certificate is used to certify the identity of the Virtual Connect Manager and is required by the underlying HTTP server to establish a secure (encrypted) communications channel with the client Web browser. On initial start up, the Virtual Connect Manager generates a default self-signed SSL Certificate valid for 10 years, and the certificate is issued to the DNS name of the Virtual Connect Ethernet module (the dynamic DNS name from the Default Networks Setting label). Because this default certificate is self- signed, the "issued by" field is also set to the same DNS name. If the Virtual Connect Manager is configured with a Virtual Connect domain IP address, then future certificate requests generated are issued to this domain IP address. For information on generating a new certificate, see "Certificate Request (on page 190)."

NOTE: When using a domain IP address, Certificate Administration allows a common certificate to be utilized between a Primary in Bay 1 and a subsequent Primary in Bay 2 after a failover.

Certificate Administration 189

The following table describes the tables within the Certificate/Authentications (SSL Certificate) screen.

Row Description

Issued to The subject, or "Common Name," to which this SSL Certificate is issued. By default, this is the dynamic DNS name of the HP 1/10Gb VC-Enet Module. If a Virtual Connect domain IP address is configured, a new certificate request is issued to the domain IP address. Issued by Name of the Certificate Authority (CA) that issued this SSL Certificate By default, the Virtual Connect Manager generates a self-signed certificate, which means the "Issued by" field contains the same dynamic DNS name as the "Issued for" field. If the Domain Administrator has requested a new certificate and it is signed by a CA, then the name of the CA is displayed. Valid from The date and time starting when this certificate became valid Valid until The date and time when this certificate becomes invalid Serial Number Serial number of the certificate. This serial number is unique per Certificate Authority that issued it. Version Version of the certificate MD5 Fingerprint Unique fingerprint of the certificate, calculated using cryptographic hash function Message-Digest algorithm 5 (MD5). This fingerprint can be used to further verify that the correct certificate is being used. SHA1 Fingerprint Unique fingerprint of the certificate, calculated using cryptographic hash function Secure Hash Algorithm 1 (SHA1). This fingerprint can be used to further verify that the correct certificate is being used.

Certificate Request This page displays a standardized certificate signing request generated by the Virtual Connect Manager. The content of the request in the text box can be sent to a Certificate Authority of your choice for signing. After signed and returned from the Certificate Authority, the certificate may be uploaded by clicking Certificate Upload on the Certificates/Authentications (SSL Certificate) screen. If a Virtual Connect domain IP address is configured for the Virtual Connect Manager at the time this certificate request is generated, the certificate request is issued to the domain IP address. Otherwise, the request is issued to the dynamic DNS name of the HP 1/10Gb VC-Enet Module. The certificate, by default, requests a valid duration of 10 years (this value is currently not configurable).

Certificate Administration 190

Note that a new certificate request is generated each time this web page is visited, so the content may not be the same each time.

Certificate Upload There are two methods for uploading certificates for use in the HP 1/10Gb VC-Enet Module: • Paste the certificate contents into the text field and click Upload. • Paste the URL of the certificate into the URL field and click Apply. The certificate to be uploaded must be from a certificate request sent out and signed by a Certificate Authority for this particular Virtual Connect Manager. Otherwise, the certificate fails to match the private keys used to generate the certificate request, and the certificate is rejected. Also, if the Virtual Connect domain has been destroyed or re-imported, you will have to repeat the steps for generating a certificate request and have it signed by a Certificate Authority again because the private keys are destroyed and recreated along with the Virtual Connect domain.

Certificate Administration 191

If the new certificate is successfully accepted and installed by the Virtual Connect Manager, you are automatically logged out. The HTTP server must be restarted for the new certificate to take effect.

Certificates/Authentications (SSH Administration) This screen lists the current user (assuming administrator privileges) of each authorized SSH key and enables the user to add new keys. Only local users can have authorized SSH keys. • SSH Fingerprint—Identifies the server and can be used to authenticate that the SSH client is connecting to the correct host. • Authorized SSH Keys—Lists the authorized SSH key data for the currently logged in user. • Add New SSH Keys—Allows the user to create or replace the authorized SSH keys. The user can enter the SSH keys in the text box or provide a URL to a file containing the user's SSH keys. The current content of the Authorized SSH Keys is replaced with the new list of SSH keys after clicking Set SSH Keys. The key file should contain the User Name of a local user at the end of the public key. Each key is associated with a local user account. If the local account does not exist for the User Name at the end of the SSH key file, the key authorization fails.

Certificate Administration 192

When a user has authorized one or more SSH keys, the user can delete all of them by clicking Clear SSH Keys. Removing the authorized SSH keys does not affect current SSH sessions.

Web SSL Configuration This screen enables you to change the currently configured SSL encryption strength. This screen is only available to users with Domain Administration privileges. To change the current strength, select 'Any SSL Key Length,' to allow all SSL encryption, or 'Only Strong Key Lengths' to require strong encryption strength (at least 128 bits). Click Apply to save changes, or click Cancel to keep current settings.

Certificate Administration 193

When the web SSL encryption strength is changed, logged in users are notified that they must reconnect.

Certificate Administration 194

Hardware information screens

Enclosure Information screen

The following table describes the rows within the Enclosure Information screen.

Row Description Part Number The part number to be used when ordering an additional enclosure of this type Product Name The common descriptive name of the enclosure Serial Number The unique serial number of the enclosure Asset Tag If configured, the asset tag of the enclosure, used for inventory control Manufacturer Name of the enclosure manufacturer Spare Part Number The part number to be used when ordering a replacement enclosure Rack Name Name of the enclosure rack (assigned through the Onboard Administrator) Time Zone The time zone assigned to the enclosure Blade Bays Number of device bays in the enclosure Interconnected Trays Number of interconnect trays in the enclosure

Hardware information screens 195

Enclosure Status screen

The following table describes the rows within the Enclosure Status screen.

Row Description

Overall Status Represents the most severe condition of hardware status, VC status, and OA communication status Hardware Status Enclosure health status from the OA VC Status Enclosure health status from the Virtual Connect Manager

OA Communication Status Current Virtual Connect Manager to Onboard Administrator communication state

Hardware information screens 196

Interconnect Bays Status and Summary screen

The following table describes the rows within the Interconnect Bays Status table in the Interconnect Bays Status and Summary screen.

Row Description

Status Overall status of the interconnect bays in the enclosure Rack Name Name of the enclosure rack (assigned through the Onboard Administrator) Enclosure Name Name of the enclosure (assigned through the Onboard Administrator)

The following table describes the columns within the Interconnect Bays Summary table in the Interconnect Bays Status and Summary screen.

Column Description

Bay Bay number and connection type Status Status of the interconnect module in the bay Module UID icon (click to toggle UID state) and type of module installed in this bay Power Icon indicates whether the interconnect module is powered on or off Firmware Rev Firmware revision of the interconnect module installed in this bay

Hardware information screens 197

Interconnect Bay Summary screen (Ethernet module) This screen provides a summary of the interconnect module status and port information. To remove a module from the domain, see "Administrative module removal (on page 210)."

The following table describes the rows within the Interconnect Bay Status (VC-Enet Module) table in the Bay Summary screen.

Row Description

Overall Status Represents the worst condition of OA Reported Status, VC Status, and OA Communication Status Hardware Status Component health status from the Onboard Administrator VC Status Component health status from the Virtual Connect Manager OA Communication Status Current Virtual Connect Manager to Onboard Administrator communication state Rack Name Name of the enclosure rack (assigned through the Onboard Administrator) Enclosure Name Name of the enclosure (assigned through the Onboard Administrator) Bay Number of the bay being summarized on this screen Power Power state of the device

The following table describes the rows within the Interconnect Bay Information table in the Bay Summary screen.

Hardware information screens 198

Row Description

Part Number The part number to be used when ordering an additional module of this type Product Name The common descriptive name of the module Serial Number The unique serial number of the module Spare Part Number The part number to be used when ordering a replacement module of this type Manufacturer The manufacturer of the module Firmware Rev The current firmware revision of the module

The following table describes the columns within the Uplink Port Information table in the Bay Summary screen.

Column Description

Label Uplink port number Network(s) Network name or the name of the shared uplink associated with this port Status Displays whether the port is linked or unlinked Connector Type Displays the physical type of the faceplate connector, type of pluggable module if one is present, or "Internal" to indicate the inter-switch link is active on the VC-Enet module. LAG ID Identifies the group of ports that have been aggregated together to form an 802.3ad Link Aggregation Group. This ID is unique only within a single VC- Enet module, meaning the same LAG ID can be used on different VC-Enet modules, but it is only meaningful for ports within the same VC-Enet module.

Hardware information screens 199

Column Description

Connected to Displays the MAC address of the device that this port is connected to on the other end. The device must support LLDP to display this information Detailed Statistics Click to display detailed statistics about this port.

The following table describes the columns within the Server Port Information table in the Bay Summary screen.

Column Description

Label Server side port number (determined by the device bay and NIC) Flex NIC Flexible network interface port Physical server Number of the device bay and a description of the installed server blade Network Network name or the name of the shared uplink associated with this port Profile Name of the server blade profile Status Displays whether the server blade is linked or unlinked Detailed Statistics Click to display detailed statistics about this port

Port Detailed Statistics screen This screen provides details on Port Information, Port Status, Port Statistics, and Remote Device Information. To reset the statistics, click Reset Statistics.

Hardware information screens 200

To refresh the statistics, click Refresh Statistics.

The following tables describe the rows within the Port Detailed Statistics screen.

Port Information Description

Port Number Relative Ethernet port number Connector Type Type of port connector, for example RJ-45 Enclosure Bay Number of the enclosure bay where the port is located

Port Status Description

Speed Speed and duplex (where applicable) of the uplink port Link Status Shows whether link is linked or unlinked Trunking Mode Trunking mode of the port, for example AUTO CFG Speed CFG speed setting of the port, for example AUTO

Port Statistic Description

reset_time Port reset time. IfInOctets The total number of octets received on the interface, including framing characters. IfInUcastPkts The number of subnetwork-unicast packets delivered to a higher-layer protocol. IfInNUcastPkts The number of non-unicast (subnetwork-broadcast or subnetwork- multicast) packets delivered to a higher-layer protocol.

Hardware information screens 201

Port Statistic Description

IfInDiscards The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being delivered to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. IfInErrors The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. IfInUnknownProtos The number of packets received via the interface that were discarded because of an unknown or unsupported protocol. IfOutOctets The total number of octets transmitted out of the interface, including framing characters. IfOutUcastPkts The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent. IfOutNUcastPkts The total number of packets that higher-level protocols requested be transmitted to a non-unicast (subnetwork-broadcast or subnetwork- multicast) address, including those that were discarded or not sent. IfOutDiscards The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. IfOutErrors The number of outbound packets that could not be transmitted because of errors. IfOutQLen The length of the output packet queue (in packets). IpInReceives The total number of input datagrams received from interfaces, including those received in error. IpInHdrErrors The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options. IpForwDatagrams The number of input datagrams for which this entity was not their final IP destination. As a result, an attempt was made to find a route to forward them to that final destination. In entities that do not act as IP Gateways, this counter includes only those packets that were Source- Routed via this entity, and the ones for which Source-Route option processing was successful. IpInDiscards The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (possibly for lack of buffer space). This counter does not include any datagrams discarded while awaiting re-assembly. Dot1dBasePortDelayExceededDiscar The number of frames discarded by this port due to excessive transit ds delay through the bridge. It is incremented by both transparent and source route bridges. Dot1dBasePortMtuExceededDiscard The number of frames discarded by this port due to an excessive size. It s is incremented by both transparent and source route bridges.

Hardware information screens 202

Port Statistic Description

Dot1dBasePortInFrames The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames. Dot1dBasePortOutFrames The number of frames that have been transmitted by this port to its segment. A frame transmitted on the interface corresponding to this port is counted by this object only if the frame is for a protocol being processed by the local bridging function, including bridge management frames. Dot1dBasePortInDiscards Count of valid frames received that were discarded (filtered) by the Forwarding Process. EtherStatsDropEvents The total number of events in which packets were dropped by the probe due to lack of resources. This number is not necessarily the number of packets dropped, but is just the number of times this condition has been detected. EtherStatsMulticastPkts The total number of good packets received that were directed to a multicast address. This number does not include packets directed to the broadcast address. EtherStatsBroadcastPkts The total number of good packets received that were directed to the broadcast address. This number does not include multicast packets. EtherStatsUndersizePkts The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well-formed. EtherStatsFragments The total number of packets received that were less than 64 octets in length (excluding framing bits, but including FCS octets) and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). It is normal for StatsFragments to increment because both runts, which are normal occurrences due to collisions, and noise hits are counted. EtherStatsPkts64Octets The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits, but including FCS octets). EtherStatsPkts65to127Octets The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits, but including FCS octets). EtherStatsPkts128to255Octets The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits, but including FCS octets). EtherStatsPkts256to511Octets The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits, but including FCS octets). EtherStatsPkts512to1023Octets The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits, but including FCS octets). EtherStatsPkts1024to1518Octets The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits, but including FCS octets).

Hardware information screens 203

Port Statistic Description

EtherStatsOversizePkts The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well-formed. EtherStatsJabbers The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). This definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms. EtherStatsOctets The total number of octets of data (including those in bad packets) received on the FCS octets). This object can be used as a reasonable estimate of Ethernet utilization. If greater precision is required, the StatsPkts and StatsOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows: Utilization = [(Pkts * (9.6 + 6.4) + (Octets * .8)) / (Interval * 10,000)]. The result of this equation is the value Utilization which is the percent utilization of the Ethernet segment on a scale of 0 to 100 percent. EtherStatsPkts The total number of packets (including bad packets, broadcast packets, and multicast packets) received. EtherStatsCollisions The best estimate of the total number of collisions on this Ethernet segment. The value returned depends on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Therefore, a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Therefore, probes placed on a station and a repeater should report the same number of collisions. Additionally, an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected. EtherStatsCRCAlignErrors The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). TXNoErrors All packets transmitted without errors, less oversized packets. RXNoErrors All packets received without errors, less oversized and undersized packets.

Hardware information screens 204

Port Statistic Description

Dot3StatsAlignmentErrors A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). According to the conventions of IEEE 802.3 Layer Management, received frames for which multiple error conditions are obtained are counted exclusively according to the error status presented to the LLC. This counter does not increment for 8-bit wide group encoding schemes. Dot3StatsFCSErrors A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with a frame-too-long or frame-too- short error. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). According to the conventions of IEEE 802.3 Layer Management, received frames for which multiple error conditions are obtained are counted exclusively according to the error status presented to the LLC. Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the frame to fail the FCS check. Dot3StatsSingleCollisionFrames A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the dot3StatsMultipleCollisionFrames object. This counter does not increment when the interface is operating in full-duplex mode. Dot3StatsMultipleCollisionFrames A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the dot3StatsSingleCollisionFrames object. This counter does not increment when the interface is operating in full-duplex mode. Dot3StatsSQETestErrors A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. The SQE TEST ERROR is set in accordance with the rules for verification of the SQE detection mechanism in the PLS Carrier Sense Function as described in IEEE Std. 802.3, 1998 Edition, section 7.2.4.6. This counter does not increment on interfaces operating at speeds greater than 10 Mb/s or operating in full-duplex mode. Dot3StatsDeferredTransmissions A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions. This counter does not increment when the interface is operating in full-duplex mode. Dot3StatsLateCollisions The number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision- related statistics. This counter does not increment when the interface is operating in full-duplex mode.

Hardware information screens 205

Port Statistic Description

Dot3StatsExcessiveCollisions A count of frames for which transmission on a particular interface fails due to excessive collisions. This counter does not increment when the interface is operating in full-duplex mode. Dot3StatsInternalMacTransmitErrors A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors object. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted. Dot3StatsCarrierSenseErrors The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. The count represented by an instance of this object is incremented, at most, once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt. This counter does not increment when the interface is operating in full-duplex mode. Dot3StatsFrameTooLongs A count of frames received on a particular interface that exceeds the maximum permitted frame size. The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). According to the conventions of IEEE 802.3 Layer Management, received frames for which multiple error conditions are obtained are counted exclusively according to the error status presented to the LLC. Dot3StatsInternalMacReceiveErrors A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors object. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted. Dot3StatsSymbolErrors For an interface operating at 100 Mb/s, the number of times an invalid data symbol occurred when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. The count represented by an instance of this object is incremented, at most, once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. Dot3ControllnUnknownOpcodes A count of MAC Control frames received on this interface that contain an opcode that is not supported by this device.

Hardware information screens 206

Port Statistic Description

Dot3InPauseFrames A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation. This counter does not increment when the interface is operating in half-duplex mode. Dot3OutPauseFrames A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. This counter does not increment when the interface is operating in half-duplex mode. IfHCInOctets The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets. IfHCInUcastPkts The number of packets, delivered by this sublayer to a higher sublayer, which were not addressed to a multicast or broadcast address at this sublayer. This object is a 64-bit version of ifInUcastPkts. IfHCInMulticastPkts The number of packets, delivered by this sublayer to a higher sublayer, which were addressed to a multicast address at this sublayer. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifInMulticastPkts. IfHCInBroadcastPkts The number of packets, delivered by this sublayer to a higher sublayer, which were addressed to a broadcast address at this sublayer. This object is a 64-bit version of ifInBroadcastPkts. IfHCOutOctets The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets. IfHCOutUcastPkts The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sublayer, including those that were discarded or not sent. This object is a 64-bit version of ifOutUcastPkts. IfHCOutMulticastPkts The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sublayer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifOutMulticastPkts. IfHCOutBroadcastPckts The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sublayer, including those that were discarded or not sent. This object is a 64-bit version of ifOutBroadcastPkts.

Remote Device Information Description remote_type Type of remote device. Virtual Connect uses this information to configure the link as an uplink, a stacking link, or to disable. This information is based on the LLDP data sent by the device to which the port is attached. remote_discovered_time Time the remote device was identified, represented in seconds. This information is based on the LLDP data sent by the device to which the port is attached. remote_chassis_id_type Chassis ID subtype of the remote device. remote_chassis_id Chassis ID value of the remote device. remote_port_id_type Port ID subtype of the remote device. remote_port_id Port ID value of the remote device. remote_port_desc Port description of the remote device.

Hardware information screens 207

Remote Device Information Description

remote_system_name System name of the remote device. If the remote device is a VC-Enet module, remote_system_name is the remote device's VC domain name. remote_system_desc Description of the remote system. If the remote device is a VC-Enet module, remote_system_desc is the module's hardware description and firmware revision. remote_system_capabilities System capabilities of the remote system, for example, repeater, bridge, or router. remote_mgmt_addr_type Management address subtype of the remote device, for example, IPv4, IPv6, or DNS. remote_mgmt_addr Management address of the remote device.

Interconnect Bay Summary screen (VC-FC Module) This screen provides a summary of the interconnect module status and port information. To remove a module from the domain, see "Administrative module removal (on page 210)."

The following table describes the rows within the Interconnect Bay Status (VC-FC Module) table in the Bay Summary screen.

Row Description

Overall Status Represents the worst condition of OA Reported Status, VC Status, and OA Communication Status Hardware Status Component health status from the Onboard Administrator

Hardware information screens 208

Row Description

VC Status Component health status from the Virtual Connect Manager OA Communication Status Current Virtual Connect Manager to Onboard Administrator communication state Rack Name Name of the enclosure rack (assigned through the Onboard Administrator) Enclosure Name Name of the enclosure (assigned through the Onboard Administrator) Bay Number of the bay being summarized on this screen Power Status Control Power state of the device Uplink Ports Used Number of uplink ports used to connect to the SAN. This number specifies the oversubscription ratio (4:1, 8:1, or 16:1).

The following table describes the rows within the Interconnect Bay Information table in the Bay Summary screen.

Row Description

Hardware information screens 209

The following table describes the rows within the Uplink Port information table in the Bay Summary screen.

Column Description

Port The uplink port number WWN World Wide Name assigned to the port or Server Factory Default if not assigning WWNs SAN Fabric Name of the SAN Fabric connected to the uplink port Port Speed Speed setting of the uplink port Connector Status Status of the uplink port Connected To MAC address of the device that this port is connected to on the other end. The device must support LLDP to display this information.

The following table describes the rows within the Server Port Information table in the Bay Summary Screen. Click Less < to display only the Port, Server Blade, SAN Fabric, Connected To, and Profile columns. Click More > to display all columns.

Column Description

Port Port number Server Blade Bay location of the server blade SAN Fabric Name of the SAN FAbric connected to this port Connected To MAC address of the device that this port is connect to on the other end. The device must support LLDP to display this information. Profile Server Profile(s) with connections to this port HBA Port HBA port number HBA Port Speed Speed setting of the HBA Port HBA Port Status Status of the HBA port HBA WWPN World Wide Port Name assigned to the port or Server Factory Default if not assigning WWNs

Administrative module removal The Remove from Domain feature enables users to remove an interconnect module from the Virtual Connect domain without having to delete the entire domain, or having the bay permanently configured for a specific interconnect module type. To temporarily remove the module from the domain, do not click Remove from Domain. Simply re-install it into the enclosure. To permanently remove the module from the Virtual Connect domain be sure the following conditions are met:

NOTE: The attachment of stacking link cables to a module does not prevent a Remove from Domain action.

VC-Enet conditions: • The user must have Domain privileges.

Hardware information screens 210

• The module must be physically removed from the bay. • The interconnect bay must remain empty for this procedure. • The module uplink and downlink ports cannot be in use by networks, uplink sets, or profiles (including FC profiles) in the enclosure. • Port monitoring cannot be enabled on that bay. VC-FC conditions: • The user must have Domain privileges. • Physically remove the module from the bay. • The interconnect bay must remain empty for this procedure. • Change all fabrics on that module to Unassigned for all Virtual Connect profile configurations. If these conditions are met, click Remove from Domain. If these conditions are not met, the Remove from Domain button is not available, or an error message is displayed.

Interconnect Bay Overall Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Unknown Device operational state cannot be Check Onboard Administrator determined. communication.

Initializing Device is initializing. Wait until initialization is complete. (blue) (This icon should only be seen at startup.) Degraded Device is partially operational, but Check and correct the Onboard

(yellow) capability is lost. Administrator error condition.

Misconfigured Device has a configuration error. Correct the Virtual Connect Manager (orange) configuration attributes.

Incompatible Device does not match the Remove the incorrect hardware. Insert (orange) configuration. the correct module.

No communication Cannot communicate with the Check the physical connections and IP (orange) device. address.

Missing Device is configured but not Insert the correct hardware module. accessible.

Failed Device is not operational because Reset the device or application, or of an error. replace the device.

Interconnect Bay OA Reported Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Unknown Device operational state cannot be Check Onboard Administrator determined. communication.

Hardware information screens 211

Icon Operational state Meaning Corrective action Degraded Device is partially operational, but Check and correct the Onboard

(yellow) capacity is lost. Administrator error condition.

Failed Device is not operational because Check and correct the Onboard of an error. Administrator error condition.

Interconnect Bay VC Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Unknown Device operational state cannot be Check Onboard Administrator determined. communication.

Disabled User has administratively disabled Enable the component in Virtual the device. Connect Manager.

Initializing Device is initializing. Wait until initialization is complete. (blue) (This icon should only be seen at startup.)

Unavailable Device is active but unable to Attempt to re-establish connection. (blue) provide service. Degraded Device is partially operational, but Check and correct the Onboard

(yellow) capacity is lost. Administrator error condition.

Misconfigured Device has a configuration error. Correct the Virtual Connect Manager (orange) configuration attributes.

Incompatible Device does not match the Remove the incorrect hardware. Insert (orange) configuration. the correct module.

No communication Cannot communicate with the Check the physical connections and IP (orange) device. address.

Missing Device is configured but not Insert the correct hardware module. accessible.

Failed Device is not operational because Reset the device or application, or of an error. replace the device.

Interconnect Bay OA Communication Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Failed Cannot communicate with the Do one or more of the following: device. • Reset the interconnect module. • Check if the physical device is properly seated in the bay. • Check the IP address.

Hardware information screens 212

Server Bays Summary screen

Device bay numbering is dependent upon whether the 'Allow the double density device bays' option was selected while using the Domain Setup Wizard. Bays might be displayed as 'Covered' or 'Unknown.' For additional information, see "Double-dense server bay option (on page 213)." The following table describes the columns within the Server Bays Summary screen.

Column Description

Bay Bay number Status Status of the server blade in the bay Device Type of server blade installed in the bay Power Icon indicates whether the server blade is powered on or off Assigned Profile Name of the server profile assigned to the device bay

Double-dense server bay option If the 'Allow the double density device bays' option was selected while using the Domain Setup Wizard, VC Manager displays the server bays as double-dense, regardless of the actual hardware installed. For example, if a full-height server blade is installed in physical Bay 1 of a double-dense enabled enclosure, Bay 1A and Bay 1B in VC Manager are displayed as 'Covered.' If a double-dense server blade is installed in physical Bay 1, Bay 1 in VC Manager is displayed as COVERED, and Bays 1A and 1B display the appropriate double-dense server blade information.

Hardware information screens 213

If VC Manager is downgraded to a version lower than v1.31, the double-dense bays and servers are no longer displayed within the VC Manager. Any profiles associated with a double-dense bay are unassigned.

Hardware information screens 214

Use of the double-dense server bay option requires OA version 2.20 or higher. If the OA is downgraded to a lower version, subsequent recovery of the double-dense enabled enclosure results in bays A and B being marked 'Unknown.'

Hardware information screens 215

Server Bay Overall Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Unknown Device operational state cannot be Check Onboard Administrator determined. communication.

Initializing Device is initializing. Wait until initialization is complete. (blue) (This icon should only be seen at startup.)

Profile pending Device has a pending profile Turn server power off and apply the (blue) assignment. new profile. Degraded Device is partially operational, but Check and correct the Onboard

(yellow) capacity is lost. Administrator error condition.

Misconfigured Device has a configuration error. Correct the Virtual Connect Manager (orange) configuration attributes.

Incompatible Device does not match the BIOS version level is not at a level that (orange) configuration. supports Virtual Connect.

No communication Cannot communicate with the Check the physical connections and IP (orange) device. address.

Missing Device is configured but not Insert the correct hardware module. accessible.

Failed Device is not operational because Reset the device or application, or of an error. replace the device.

Server Bay OA Reported Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Unknown Device operational state cannot be Check Onboard Administrator determined. communication. Degraded Device is partially operational, but Check and correct the Onboard

(yellow) capacity is lost. Administrator error condition.

Failed Device is not operational because Check and correct the Onboard of an error. Administrator error condition.

Server Bay VC Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Unknown Device operational state cannot be Check Onboard Administrator determined. communication.

Disabled User has administratively disabled Enable the component in Virtual the device. Connect Manager.

Hardware information screens 216

Icon Operational state Meaning Corrective action

Initializing Device is initializing. Wait until initialization is complete. (blue) (This icon should only be seen at startup.)

Profile pending Device has a pending profile Turn server power off and apply the (blue) assignment. new profile. Degraded Device is partially operational, but Check and correct the Onboard

(yellow) capacity is lost. Administrator error condition.

Misconfigured Device has a configuration error. Correct the Virtual Connect Manager (orange) configuration attributes.

Incompatible Device does not match the BIOS level is not at a level that (orange) configuration. supports Virtual Connect.

No communication Cannot communicate with the Check the physical connections and IP (orange) device. address.

Missing Device is configured but not Insert the correct hardware module. accessible.

Failed Device is not operational because Reset the device or application, or of an error. replace the device.

Server Bay OA Communication Status icon definitions

Icon Operational state Meaning Corrective action

OK Device is fully operational. None

Hardware information screens 217

Server Bay Status screen

To change the power state of the server blade, click Momentary Press. To power the server blade on or off, click Press and Hold. The following table describes the rows within the Server Bay Status table in the Server Bay Status screen. Server Bay Status

Row Description

Overall Status Represents the worst condition of Hardware Status, VC Status, and OA Communication Status Hardware Status Component health status from the Onboard Administrator VC Status Component health status from the Virtual Connect Manager OA Communication Status Current Virtual Connect Manager to Onboard Administrator communication state Assigned Server Profile Name of the profile currently assigned to the server blade in this bay Enclosure Name Name of the enclosure where this server blade is installed UID Icon indicates whether the UID is lit or unlit. Power Icon indicates whether server blade in that bay is powered on or off.

The following table describes the rows within the Server Blade Information table in the Server Bay Status screen.

Hardware information screens 218

Server Blade Information

Row Description

Serial Number The unique serial number of the server blade Product Name The common descriptive name of the server blade Server Name If configured, the server name of the installed server blade Part Number The part number to be used when ordering an additional or replacement server blade of this type Asset Tag If configured, the asset tag of the installed server blade

The following table describes the columns within the Server Ethernet Adapter Information table in the Server Bay Status screen. Server Ethernet Adapter Information

Column Description

Ethernet adapter Port number where the adapter is installed Flex NIC Flexible network interface port Location Connection location of this adapter Model Type of adapter installed MAC Address MAC address of the Ethernet adapter

Hardware information screens 219

Column Description

Network Network name associated with this adapter Connected to Bay number

The following table describes the columns within the SAN Ports table in the Server Bay Status screen. SAN Ports

Column Description

Port Number Relative Fibre Channel Port number Adapter Mezzanine number where the HBA is connected Model Type of mezzanine installed WWN VC-Assigned WWN or "Server Factory Default" if not assigning WWNs Connected to Bay number

Hardware information screens 220

Regulatory compliance notices

Regulatory compliance identification numbers For the purpose of regulatory compliance certifications and identification, this product has been assigned a unique regulatory model number. The regulatory model number can be found on the product nameplate label, along with all required approval markings and information. When requesting compliance information for this product, always refer to this regulatory model number. The regulatory model number is not the marketing name or model number of the product.

Federal Communications Commission notice Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency (RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules. These rules place computers and related peripheral devices into two classes, A and B, depending upon their intended installation. Class A devices are those that may reasonably be expected to be installed in a business or commercial environment. Class B devices are those that may reasonably be expected to be installed in a residential environment (for example, personal computers). The FCC requires devices in both classes to bear a label indicating the interference potential of the device as well as additional operating instructions for the user.

FCC rating label The FCC rating label on the device shows the classification (A or B) of the equipment. Class B devices have an FCC logo or ID on the label. Class A devices do not have an FCC logo or ID on the label. After you determine the class of the device, refer to the corresponding statement.

Class A equipment This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at personal expense.

Class B equipment This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency

Regulatory compliance notices 221

energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: • Reorient or relocate the receiving antenna. • Increase the separation between the equipment and receiver. • Connect the equipment into an outlet on a circuit that is different from that to which the receiver is connected. • Consult the dealer or an experienced radio or television technician for help.

Declaration of conformity for products marked with the FCC logo, United States only This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. For questions regarding this product, contact us by mail or telephone: • Hewlett-Packard Company P. O. Box 692000, Mail Stop 530113 Houston, Texas 77269-2000 • 1-800-HP-INVENT (1-800-474-6836). (For continuous quality improvement, calls may be recorded or monitored.) For questions regarding this FCC declaration, contact us by mail or telephone: • Hewlett-Packard Company P. O. Box 692000, Mail Stop 510101 Houston, Texas 77269-2000 • 1281-514-3333 To identify this product, refer to the part, series, or model number found on the product.

Modifications The FCC requires the user to be notified that any changes or modifications made to this device that are not expressly approved by Hewlett-Packard Company may void the user’s authority to operate the equipment.

Cables Connections to this device must be made with shielded cables with metallic RFI/EMI connector hoods in order to maintain compliance with FCC Rules and Regulations.

Regulatory compliance notices 222

Canadian notice (Avis Canadien) Class A equipment This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. Class B equipment This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

European Union regulatory notice This product complies with the following EU Directives: • Low Voltage Directive 2006/95/EC • EMC Directive 2004/108/EC Compliance with these directives implies conformity to applicable harmonized European standards (European Norms) which are listed on the EU Declaration of Conformity issued by Hewlett-Packard for this product or product family. This compliance is indicated by the following conformity marking placed on the product:

This marking is valid for non-Telecom products and EU harmonized Telecom products (e.g. Bluetooth).

This marking is valid for EU non-harmonized Telecom products. *Notified body number (used only if applicable—refer to the product label) Hewlett-Packard GmbH, HQ-TRE, Herrenberger Strasse 140, 71034 Boeblingen, Germany

Disposal of waste equipment by users in private households in the European Union

Regulatory compliance notices 223

This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for the recycling of waste electrical and electronic equipment. The separate collection and recycling of your waste equipment at the time of disposal will help to conserve natural resources and ensure that it is recycled in a manner that protects human health and the environment. For more information about where you can drop off your waste equipment for recycling, please contact your local city office, your household waste disposal service or the shop where you purchased the product.

Japanese notice

BSMI notice

Korean notice Class A equipment

Regulatory compliance notices 224

Class B equipment

Chinese notice Class A equipment

Laser compliance This product may be provided with an optical storage device (that is, CD or DVD drive) and/or fiber optic transceiver. Each of these devices contains a laser that is classified as a Class 1 Laser Product in accordance with US FDA regulations and the IEC 60825-1. The product does not emit hazardous laser radiation. Each laser product complies with 21 CFR 1040.10 and 1040.11 except for deviations pursuant to Laser Notice No. 50, dated May 27, 2001; and with IEC 60825-1:1993/A2:2001.

WARNING: Use of controls or adjustments or performance of procedures other than those specified herein or in the laser product's installation guide may result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation: • Do not try to open the module enclosure. There are no user-serviceable components inside. • Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein. • Allow only HP Authorized Service technicians to repair the unit.

The Center for Devices and Radiological Health (CDRH) of the U.S. Food and Drug Administration implemented regulations for laser products on August 2, 1976. These regulations apply to laser products manufactured from August 1, 1976. Compliance is mandatory for products marketed in the United States.

Regulatory compliance notices 225

Electrostatic discharge

Preventing electrostatic discharge To prevent damaging the system, be aware of the precautions you need to follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor may damage system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the device. To prevent electrostatic damage: • Avoid hand contact by transporting and storing products in static-safe containers. • Keep electrostatic-sensitive parts in their containers until they arrive at static-free workstations. • Place parts on a grounded surface before removing them from their containers. • Avoid touching pins, leads, or circuitry. • Always be properly grounded when touching a static-sensitive component or assembly.

Grounding methods to prevent electrostatic discharge Several methods are used for grounding. Use one or more of the following methods when handling or installing electrostatic-sensitive parts: • Use a wrist strap connected by a ground cord to a grounded workstation or computer chassis. Wrist straps are flexible straps with a minimum of 1 megohm ±10 percent resistance in the ground cords. To provide proper ground, wear the strap snug against the skin. • Use heel straps, toe straps, or boot straps at standing workstations. Wear the straps on both feet when standing on conductive floors or dissipating floor mats. • Use conductive field service tools. • Use a portable field service kit with a folding static-dissipating work mat. If you do not have any of the suggested equipment for proper grounding, have an authorized reseller install the part. For more information on static electricity or assistance with product installation, contact an authorized reseller.

Electrostatic discharge 226

Technical support

Before you contact HP Be sure to have the following information available before you call HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error messages • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level

HP contact information For the name of the nearest HP authorized reseller: • See the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html). For HP technical support: • In the United States, for contact options see the Contact HP United States webpage (http://welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone: o Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. o If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com/hps). • In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).

Customer Self Repair HP products are designed with many Customer Self Repair (CSR) parts to minimize repair time and allow for greater flexibility in performing defective parts replacement. If during the diagnosis period HP (or HP service providers or service partners) identifies that the repair can be accomplished by the use of a CSR part, HP will ship that part directly to you for replacement. There are two categories of CSR parts: • Mandatory—Parts for which customer self repair is mandatory. If you request HP to replace these parts, you will be charged for the travel and labor costs of this service.

Technical support 227

• Optional—Parts for which customer self repair is optional. These parts are also designed for customer self repair. If, however, you require that HP replace them for you, there may or may not be additional charges, depending on the type of warranty service designated for your product. NOTE: Some HP parts are not designed for customer self repair. In order to satisfy the customer warranty, HP requires that an authorized service provider replace the part. These parts are identified as "No" in the Illustrated Parts Catalog. Based on availability and where geography permits, CSR parts will be shipped for next business day delivery. Same day or four-hour delivery may be offered at an additional charge where geography permits. If assistance is required, you can call the HP Technical Support Center and a technician will help you over the telephone. HP specifies in the materials shipped with a replacement CSR part whether a defective part must be returned to HP. In cases where it is required to return the defective part to HP, you must ship the defective part back to HP within a defined period of time, normally five (5) business days. The defective part must be returned with the associated documentation in the provided shipping material. Failure to return the defective part may result in HP billing you for the replacement. With a customer self repair, HP will pay all shipping and part return costs and determine the courier/carrier to be used. For more information about HP's Customer Self Repair program, contact your local service provider. For the North American program, refer to the HP website (http://www.hp.com/go/selfrepair). Réparation par le client (CSR) Les produits HP comportent de nombreuses pièces CSR (Customer Self Repair = réparation par le client) afin de minimiser les délais de réparation et faciliter le remplacement des pièces défectueuses. Si pendant la période de diagnostic, HP (ou ses partenaires ou mainteneurs agréés) détermine que la réparation peut être effectuée à l'aide d'une pièce CSR, HP vous l'envoie directement. Il existe deux catégories de pièces CSR: • Obligatoire - Pièces pour lesquelles la réparation par le client est obligatoire. Si vous demandez à HP de remplacer ces pièces, les coûts de déplacement et main d'œuvre du service vous seront facturés. • Facultatif - Pièces pour lesquelles la réparation par le client est facultative. Ces pièces sont également conçues pour permettre au client d'effectuer lui-même la réparation. Toutefois, si vous demandez à HP de remplacer ces pièces, l'intervention peut ou non vous être facturée, selon le type de garantie applicable à votre produit. REMARQUE: Certaines pièces HP ne sont pas conçues pour permettre au client d'effectuer lui-même la réparation. Pour que la garantie puisse s'appliquer, HP exige que le remplacement de la pièce soit effectué par un Mainteneur Agréé. Ces pièces sont identifiées par la mention "Non" dans le Catalogue illustré. Les pièces CSR sont livrées le jour ouvré suivant, dans la limite des stocks disponibles et selon votre situation géographique. Si votre situation géographique le permet et que vous demandez une livraison le jour même ou dans les 4 heures, celle-ci vous sera facturée. Pour bénéficier d'une assistance téléphonique, appelez le Centre d'assistance technique HP. Dans les documents envoyés avec la pièce de rechange CSR, HP précise s'il est nécessaire de lui retourner la pièce défectueuse. Si c'est le cas, vous devez le faire dans le délai indiqué, généralement cinq (5) jours ouvrés. La pièce et sa documentation doivent être retournées dans l'emballage fourni. Si vous ne retournez pas la pièce défectueuse, HP se réserve le droit de vous facturer les coûts de remplacement. Dans le cas d'une pièce CSR, HP supporte l'ensemble des frais d'expédition et de retour, et détermine la société de courses ou le transporteur à utiliser.

Technical support 228

Pour plus d'informations sur le programme CSR de HP, contactez votre Mainteneur Agrée local. Pour plus d'informations sur ce programme en Amérique du Nord, consultez le site Web HP (http://www.hp.com/go/selfrepair). Riparazione da parte del cliente Per abbreviare i tempi di riparazione e garantire una maggiore flessibilità nella sostituzione di parti difettose, i prodotti HP sono realizzati con numerosi componenti che possono essere riparati direttamente dal cliente (CSR, Customer Self Repair). Se in fase di diagnostica HP (o un centro di servizi o di assistenza HP) identifica il guasto come riparabile mediante un ricambio CSR, HP lo spedirà direttamente al cliente per la sostituzione. Vi sono due categorie di parti CSR: • Obbligatorie – Parti che devono essere necessariamente riparate dal cliente. Se il cliente ne affida la riparazione ad HP, deve sostenere le spese di spedizione e di manodopera per il servizio. • Opzionali – Parti la cui riparazione da parte del cliente è facoltativa. Si tratta comunque di componenti progettati per questo scopo. Se tuttavia il cliente ne richiede la sostituzione ad HP, potrebbe dover sostenere spese addizionali a seconda del tipo di garanzia previsto per il prodotto. NOTA: alcuni componenti HP non sono progettati per la riparazione da parte del cliente. Per rispettare la garanzia, HP richiede che queste parti siano sostituite da un centro di assistenza autorizzato. Tali parti sono identificate da un "No" nel Catalogo illustrato dei componenti. In base alla disponibilità e alla località geografica, le parti CSR vengono spedite con consegna entro il giorno lavorativo seguente. La consegna nel giorno stesso o entro quattro ore è offerta con un supplemento di costo solo in alcune zone. In caso di necessità si può richiedere l'assistenza telefonica di un addetto del centro di supporto tecnico HP. Nel materiale fornito con una parte di ricambio CSR, HP specifica se il cliente deve restituire dei componenti. Qualora sia richiesta la resa ad HP del componente difettoso, lo si deve spedire ad HP entro un determinato periodo di tempo, generalmente cinque (5) giorni lavorativi. Il componente difettoso deve essere restituito con la documentazione associata nell'imballo di spedizione fornito. La mancata restituzione del componente può comportare la fatturazione del ricambio da parte di HP. Nel caso di riparazione da parte del cliente, HP sostiene tutte le spese di spedizione e resa e sceglie il corriere/vettore da utilizzare. Per ulteriori informazioni sul programma CSR di HP contattare il centro di assistenza di zona. Per il programma in Nord America fare riferimento al sito Web HP (http://www.hp.com/go/selfrepair). Customer Self Repair HP Produkte enthalten viele CSR-Teile (Customer Self Repair), um Reparaturzeiten zu minimieren und höhere Flexibilität beim Austausch defekter Bauteile zu ermöglichen. Wenn HP (oder ein HP Servicepartner) bei der Diagnose feststellt, dass das Produkt mithilfe eines CSR-Teils repariert werden kann, sendet Ihnen HP dieses Bauteil zum Austausch direkt zu. CSR-Teile werden in zwei Kategorien unterteilt: • Zwingend – Teile, für die das Customer Self Repair-Verfahren zwingend vorgegeben ist. Wenn Sie den Austausch dieser Teile von HP vornehmen lassen, werden Ihnen die Anfahrt- und Arbeitskosten für diesen Service berechnet. • Optional – Teile, für die das Customer Self Repair-Verfahren optional ist. Diese Teile sind auch für Customer Self Repair ausgelegt. Wenn Sie jedoch den Austausch dieser Teile von HP vornehmen lassen möchten, können bei diesem Service je nach den für Ihr Produkt vorgesehenen Garantiebedingungen zusätzliche Kosten anfallen.

Technical support 229

HINWEIS: Einige Teile sind nicht für Customer Self Repair ausgelegt. Um den Garantieanspruch des Kunden zu erfüllen, muss das Teil von einem HP Servicepartner ersetzt werden. Im illustrierten Teilekatalog sind diese Teile mit „No“ bzw. „Nein“ gekennzeichnet. CSR-Teile werden abhängig von der Verfügbarkeit und vom Lieferziel am folgenden Geschäftstag geliefert. Für bestimmte Standorte ist eine Lieferung am selben Tag oder innerhalb von vier Stunden gegen einen Aufpreis verfügbar. Wenn Sie Hilfe benötigen, können Sie das HP technische Support Center anrufen und sich von einem Mitarbeiter per Telefon helfen lassen. Den Materialien, die mit einem CSR- Ersatzteil geliefert werden, können Sie entnehmen, ob das defekte Teil an HP zurückgeschickt werden muss. Wenn es erforderlich ist, das defekte Teil an HP zurückzuschicken, müssen Sie dies innerhalb eines vorgegebenen Zeitraums tun, in der Regel innerhalb von fünf (5) Geschäftstagen. Das defekte Teil muss mit der zugehörigen Dokumentation in der Verpackung zurückgeschickt werden, die im Lieferumfang enthalten ist. Wenn Sie das defekte Teil nicht zurückschicken, kann HP Ihnen das Ersatzteil in Rechnung stellen. Im Falle von Customer Self Repair kommt HP für alle Kosten für die Lieferung und Rücksendung auf und bestimmt den Kurier-/Frachtdienst. Weitere Informationen über das HP Customer Self Repair Programm erhalten Sie von Ihrem Servicepartner vor Ort. Informationen über das CSR-Programm in Nordamerika finden Sie auf der HP Website unter (http://www.hp.com/go/selfrepair). Reparaciones del propio cliente Los productos de HP incluyen muchos componentes que el propio usuario puede reemplazar (Customer Self Repair, CSR) para minimizar el tiempo de reparación y ofrecer una mayor flexibilidad a la hora de realizar sustituciones de componentes defectuosos. Si, durante la fase de diagnóstico, HP (o los proveedores o socios de servicio de HP) identifica que una reparación puede llevarse a cabo mediante el uso de un componente CSR, HP le enviará dicho componente directamente para que realice su sustitución. Los componentes CSR se clasifican en dos categorías: • Obligatorio: componentes para los que la reparación por parte del usuario es obligatoria. Si solicita a HP que realice la sustitución de estos componentes, tendrá que hacerse cargo de los gastos de desplazamiento y de mano de obra de dicho servicio. • Opcional: componentes para los que la reparación por parte del usuario es opcional. Estos componentes también están diseñados para que puedan ser reparados por el usuario. Sin embargo, si precisa que HP realice su sustitución, puede o no conllevar costes adicionales, dependiendo del tipo de servicio de garantía correspondiente al producto. NOTA: Algunos componentes no están diseñados para que puedan ser reparados por el usuario. Para que el usuario haga valer su garantía, HP pone como condición que un proveedor de servicios autorizado realice la sustitución de estos componentes. Dichos componentes se identifican con la palabra "No" en el catálogo ilustrado de componentes. Según la disponibilidad y la situación geográfica, los componentes CSR se enviarán para que lleguen a su destino al siguiente día laborable. Si la situación geográfica lo permite, se puede solicitar la entrega en el mismo día o en cuatro horas con un coste adicional. Si precisa asistencia técnica, puede llamar al Centro de asistencia técnica de HP y recibirá ayuda telefónica por parte de un técnico. Con el envío de materiales para la sustitución de componentes CSR, HP especificará si los componentes defectuosos deberán devolverse a HP. En aquellos casos en los que sea necesario devolver algún componente a HP, deberá hacerlo en el periodo de tiempo especificado, normalmente cinco días laborables. Los componentes defectuosos deberán devolverse con toda la documentación relacionada y con el embalaje de envío. Si no enviara el componente defectuoso requerido, HP podrá cobrarle por el de sustitución. En

Technical support 230

el caso de todas sustituciones que lleve a cabo el cliente, HP se hará cargo de todos los gastos de envío y devolución de componentes y escogerá la empresa de transporte que se utilice para dicho servicio. Para obtener más información acerca del programa de Reparaciones del propio cliente de HP, póngase en contacto con su proveedor de servicios local. Si está interesado en el programa para Norteamérica, visite la página web de HP siguiente (http://www.hp.com/go/selfrepair). Customer Self Repair Veel onderdelen in HP producten zijn door de klant zelf te repareren, waardoor de reparatieduur tot een minimum beperkt kan blijven en de flexibiliteit in het vervangen van defecte onderdelen groter is. Deze onderdelen worden CSR-onderdelen (Customer Self Repair) genoemd. Als HP (of een HP Service Partner) bij de diagnose vaststelt dat de reparatie kan worden uitgevoerd met een CSR-onderdeel, verzendt HP dat onderdeel rechtstreeks naar u, zodat u het defecte onderdeel daarmee kunt vervangen. Er zijn twee categorieën CSR-onderdelen: • Verplicht: Onderdelen waarvoor reparatie door de klant verplicht is. Als u HP verzoekt deze onderdelen voor u te vervangen, worden u voor deze service reiskosten en arbeidsloon in rekening gebracht. • Optioneel: Onderdelen waarvoor reparatie door de klant optioneel is. Ook deze onderdelen zijn ontworpen voor reparatie door de klant. Als u echter HP verzoekt deze onderdelen voor u te vervangen, kunnen daarvoor extra kosten in rekening worden gebracht, afhankelijk van het type garantieservice voor het product. OPMERKING: Sommige HP onderdelen zijn niet ontwikkeld voor reparatie door de klant. In verband met de garantievoorwaarden moet het onderdeel door een geautoriseerde Service Partner worden vervangen. Deze onderdelen worden in de geïllustreerde onderdelencatalogus aangemerkt met "Nee". Afhankelijk van de leverbaarheid en de locatie worden CSR-onderdelen verzonden voor levering op de eerstvolgende werkdag. Levering op dezelfde dag of binnen vier uur kan tegen meerkosten worden aangeboden, indien dit mogelijk is gezien de locatie. Indien assistentie gewenst is, belt u een HP Service Partner om via de telefoon technische ondersteuning te ontvangen. HP vermeldt in de documentatie bij het vervangende CSR-onderdeel of het defecte onderdeel aan HP moet worden geretourneerd. Als het defecte onderdeel aan HP moet worden teruggezonden, moet u het defecte onderdeel binnen een bepaalde periode, gewoonlijk vijf (5) werkdagen, retourneren aan HP. Het defecte onderdeel moet met de bijbehorende documentatie worden geretourneerd in het meegeleverde verpakkingsmateriaal. Als u het defecte onderdeel niet terugzendt, kan HP u voor het vervangende onderdeel kosten in rekening brengen. Bij reparatie door de klant betaalt HP alle verzendkosten voor het vervangende en geretourneerde onderdeel en kiest HP zelf welke koerier/transportonderneming hiervoor wordt gebruikt. Neem contact op met een Service Partner voor meer informatie over het Customer Self Repair programma van HP. Informatie over Service Partners vindt u op de HP website (http://www.hp.com/go/selfrepair). Reparo feito pelo cliente Os produtos da HP são projetados com muitas peças para reparo feito pelo cliente (CSR) de modo a minimizar o tempo de reparo e permitir maior flexibilidade na substituição de peças com defeito. Se, durante o período de diagnóstico, a HP (ou fornecedores/parceiros de serviço da HP) concluir que o reparo pode ser efetuado pelo uso de uma peça CSR, a peça de reposição será enviada diretamente ao cliente. Existem duas categorias de peças CSR:

Technical support 231

• Obrigatória – Peças cujo reparo feito pelo cliente é obrigatório. Se desejar que a HP substitua essas peças, serão cobradas as despesas de transporte e mão-de-obra do serviço. • Opcional – Peças cujo reparo feito pelo cliente é opcional. Essas peças também são projetadas para o reparo feito pelo cliente. No entanto, se desejar que a HP as substitua, pode haver ou não a cobrança de taxa adicional, dependendo do tipo de serviço de garantia destinado ao produto. OBSERVAÇÃO: Algumas peças da HP não são projetadas para o reparo feito pelo cliente. A fim de cumprir a garantia do cliente, a HP exige que um técnico autorizado substitua a peça. Essas peças estão identificadas com a marca "No" (Não), no catálogo de peças ilustrado. Conforme a disponibilidade e o local geográfico, as peças CSR serão enviadas no primeiro dia útil após o pedido. Onde as condições geográficas permitirem, a entrega no mesmo dia ou em quatro horas pode ser feita mediante uma taxa adicional. Se precisar de auxílio, entre em contato com o Centro de suporte técnico da HP para que um técnico o ajude por telefone. A HP especifica nos materiais fornecidos com a peça CSR de reposição se a peça com defeito deve ser devolvida à HP. Nos casos em que isso for necessário, é preciso enviar a peça com defeito à HP dentro do período determinado, normalmente cinco (5) dias úteis. A peça com defeito deve ser enviada com a documentação correspondente no material de transporte fornecido. Caso não o faça, a HP poderá cobrar a reposição. Para as peças de reparo feito pelo cliente, a HP paga todas as despesas de transporte e de devolução da peça e determina a transportadora/serviço postal a ser utilizado. Para obter mais informações sobre o programa de reparo feito pelo cliente da HP, entre em contato com o fornecedor de serviços local. Para o programa norte-americano, visite o site da HP (http://www.hp.com/go/selfrepair).

Technical support 232

Technical support 233

Technical support 234

Acronyms and abbreviations

BPDU Bridge Protocol Data Unit

CFG constant frequency generator

DHCP Dynamic Host Configuration Protocol

DNS domain name system

DO data object

FC Fibre Channel

FCS Frame Check Sequence

GMII Gigabit media independent interface

HBA host bus adapter

LACP Link Aggregation Control Protocol

LAG link aggregation group

LAG ID link aggregation group ID

Acronyms and abbreviations 235

LDAP Lightweight Directory Access Protocol

LLDP Link Layer Discovery Protocol

MAC Media Access Control

NPIV N_Port ID Virtualization

OA Onboard Administrator

PHY physical layer device

PLS physical signaling

POST Power-On Self Test

RBSU ROM-Based Setup Utility

RD receive data

RDP Rapid Deployment Pack

RMON remote monitoring

SIM Systems Insight Manager

SNMP Simple Network Management Protocol

Acronyms and abbreviations 236

SSL Secure Sockets Layer

TCP/IP Transmission Control Protocol/Internet Protocol

USB universal serial bus

VID VLAN ID

VLAN virtual local-area network

WWN World Wide Name

Acronyms and abbreviations 237

Glossary

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.

shared server links A feature that enables each server link to be shared among multiple networks with the use of VLAN tagging.

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 VLAN on the external connection and appropriate VLAN tags are removed or added as Ethernet packets enter or leave the Virtual Connect domain.

shared uplink port set A set of Ethernet uplinks that are used together to provide improved throughput and availability 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 Virtual Connect domain.

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.

stacking port A VC-Enet module external port used to connect to other VC-Enet modules within an active Virtual Connect domain. Stacking ports are automatically identified by the VC-Enet modules. The port number (port ID) is lit amber.

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

Glossary 238

Index

components, HP Virtual Connect 4Gb FC A Module 26 components, HP Virtual Connect Flex-10 Module 19 About menu 55 configuration example 48 accessing HP Virtual Connect Manager 10, 53 configuration, default module 11 ActiveX 52 configuration, redundant 43 adding an LDAP group 179 connection mode 104 administrative module removal 210 connection mode, changing 103, 107 Advanced Network Settings 83 connection status 78 Advanced Profile Settings 150 connectivity 146 allowing double density device bays 66 connectors 13 assign server profiles 96 contact information 227 assigned MAC addresses 76 contacting HP 227 assigned serial numbers (logical) 94 cookies 52 assigned WWNs 87 covered device bay 213 authorized reseller 227 create server profiles, Server Profile Wizard 97 customer self repair (CSR) 227 B backup domain 169 D boot paramaters, Fibre Channel 157 data center connections, verifying 100 Brocade switch 132 Declaration of Conformity 222 browser requirements 52, 53 define a server profile 146, 150 buttons 13 define network 82, 103, 104 define network connection 80 C define SAN fabric 89, 131 cables 222 define server profile template 94 cabling 43, 45 define server VLAN mappings 153 Canadian notice 223 define shared uplink set 84, 121, 123 certificate administration 189 delete a domain 167 certificate upload 191 delete a server profile 158 certificate, requesting 190 deleting a network 107 check-pointing 50 device bay, information 213 Cisco Core switch 48 Directory Settings (Directory Certificate) 179 Cisco switch 133 Directory Settings (Directory Groups) 178 class A equipment 221 Directory Settings (Directory Server) 177 class B equipment 221 DNS label 36 CLI (Command Line Interface) 53 DNS settings 28 command line interface, using 53 domain name 69, 166 command line overview 53 Domain Settings (Backup/Restore) 169 component identification 13, 16 Domain Settings (Domain Configuration) screen 166 components 13, 16, 19, 23, 26 Domain Settings (Domain IP Address) 168 components, HP 1/10GB VC-Enet Module 13 Domain Settings (Enclosures) 169 components, HP 1/10Gb-F VC-Enet module 16 Domain Settings (Firmware Management) 170 components, HP 4Gb VC-FC Module 23 Domain Settings (Local Users) 172

Index 239

domain setup wizard 64 Fibre Channel Settings (FC SAN Settings) 137 Domain Status screen 60 Fibre Channel settings (WWN) 86 Domain Status summary 58 finish wizard 74, 84, 90, 100 domain, deleting 166, 167 firmware requirements 35 double density device bays, allowing 66 firmware, Onboard Administrator requirements 53 double-dense server blades 213 firmware, updating 170

E G EBIPA (Enclosure Bay IP Addressing) 35 general settings 69 edit a server profile 159, 162 graphical view 61 edit a shared uplink set 124 grounding methods 226 edit an Ethernet network 107 edit SAN fabric 136 H electrostatic discharge 226 hardware setup 10, 36, 39 enable local users 71 help resources 227 enclosure import 66, 68 high availability support 31, 50 enclosure information 195 homepage, Virtual Connect Manager 55 enclosure recovery 66, 68 HP 1/10Gb VC-Enet Module 15 enclosure serial number 166 HP 1/10Gb-F VC-Enet Module 18 enclosure status information 196 HP 4Gb VC-FC Module 25 enclosures view 61 HP technical support 227 error messages 60 HP Virtual Connect 4Gb FC Module 28 Ethernet connections 146, 158 HP Virtual Connect Flex-10 Ethernet Module 22 Ethernet module components 13, 16 Ethernet module LEDs 13, 14, 16 Ethernet module, installing 36 I Ethernet Networks (External Connections) 105 icons 62, 63, 211, 212, 216, 217 Ethernet Networks (Server Connections) 109 identification number 221 Ethernet networks, viewing 105 IGMP snooping 115, 120 Ethernet Settings (Advanced Settings) 115 iLO connector 53 Ethernet Settings (MAC Addresses) 110 import enclosures 68 Ethernet Settings (Port Monitoring) 111 installation guidelines 33 European Union notice 223 installation, management card 31 export support information 63 installing, Ethernet module 36 external connections 45 installing, FC module 39 external port connections, verifying 100 interconnect bay, summary 197, 198, 208 external uplink ports 82, 84 Internet Explorer support 52 iSCSI MAC address 76 F iSCSI support 76 fabric switch, enabling NPIV 132 factory default settings 41 J failover 33, 50, 64 Japanese notice 224 Fast MAC Cache Failover 115, 119 Javascript 52 FC connections 146, 158 jumbo frames 104 FC module, installing 39 FCC rating label 221 K Federal Communications Commission (FCC) notice 221, 222 Korean notices 224 Fibre Channel boot parameters 157

Index 240

L Onboard Administrator, required firmware revision 53 LACP 11 LAG ID 198 P LDAP authentication, testing 180 LDAP group, adding 179 password, resetting 28 LEDs 13, 14, 16, 20, 24, 27 phone numbers 227 LEDs, HP 1/10Gb VC-Enet Module 14 port detailed statistics 200 LEDs, HP 1/10Gb-F VC-Enet module 16 port monitoring 111 LEDs, HP 4Gb VC-FC Module 24 port WWN 86 LEDs, HP Virtual Connect 4Gb FC Module 27 private networks 82, 102, 103, 104 LEDs, HP Virtual Connect Flex-10 Module 20 PXE deployment 145 licensed software and MACs or WWNs 52 local user accounts 71, 172 R logging in 54 RDP, using with Virtual Connect 52 login distribution 130 recommended screen resolution 53 loop prevention 45 recommended stacking connections 43 recovery, enclosure 68

M Red Hat procedures 52 MAC address settings 76, 110 redundancy status 78 MAC cache failover settings, configuring 115, 119 redundant configuration 43 map VLAN tags 117 regulatory compliance identification numbers 221 McData switch 133 regulatory compliance notices 221, 223 menu map 56 remote log test 187 modifications, FCC notice 222 remote logging 187 module configuration, default 11 remove module from the domain 210 module, remove from domain 210 requirements, web interface 53 monitored ports, selecting 114 resetting the adminsitrator password 28 Mozilla support 52 resetting the system 64 multiple networks link speed settings 115, 119 restore domain 169 multiple networks option 151 S

N SAN Fabrics (External Connections) 133 name server profiles 97 SAN Fabrics (Server Connections) 134 native VLAN 84, 120 SAN fabrics, defining available 88 navigating 56 select monitored ports 114 network analyzer port 111 serial number (logical) settings 92, 164 network mapping 45 serial number, enclosure 166 network, creating internal 104 series number 221 network, deleting 107 server bay, information 213 networks overview 102 server bay, status information 218 node WWN 86 server connections, viewing 109 NPIV 33, 129 server profile overview 139 NPIV, enabling on the fabric switch 132 server profile troubleshooting 163 server profile, defining 150 O server profile, delete 158 server profiles 158 Onboard Administrator login credentials 65 setup wizard 64, 75, 85, 91 Onboard Administrator, accessing Virtual Connect SFP transceiver, installing 41 Module 53 SFP transceiver, removing 42

Index 241

shared port operation 21 verify link and speed 100 shared server links 117, 151 verify network status 101 Shared Uplink Sets (Associated Networks) 127 view Ethernet networks 105 Shared Uplink Sets (External Connections) 127 view printable report 163 shared uplink sets and VLAN tagging 120 view server connections 109 Smart Link 82, 102, 103, 104 Virtual Connect fabric 129 SMI-S (Storage Management Initiative Virtual Connect Manager setup overview 11 Specification) 181, 185 Virtual Connect overview 8 SNMP (Simple Network Management Protocol) 181 VLAN tagging 45, 102, 117, 118 SNMP settings 183 VLAN tags, map 117, 153 SNMP traps 183 VLAN tags, tunnel 117 SSH administration 192 VLAN tunneling, enable or disable 82, 103, 104, SSH fingerprint 192 107 SSH key, adding 192 SSH keys, authorized 192 W SSL certificate administration 189 Warning and alarm messages 29 stacking links 78, 120 web browser requirements 53 static electricity 226 Web SSL configuration 193 statistics, port detail 200 website, HP 227 status error messages 60 WWN settings 86 status icons 62, 211, 212, 216, 217 WWN, selecting a range 87 storage management 129 storage overview 129 strong password 71 X support 63, 227 XFP transceiver, installing 41 supported browsers 53 XFP transceiver, removing 42 supported configurations 31, 33 switches 132, 133 system log 186 system log configuration 187 system maintenance switch 15, 18, 25, 28

T technical support 63, 227 test LDAP authentication 180 Transmission Control Protocol/Internet Protocol (TCP/IP) 237 tree navigation 57 troubleshooting, server profiles 163 tunnel VLAN tags 117

U unknown device bay 213 user accounts 71 user settings 73

V VC-assigned MAC addresses 78 verify data center connections 100

Index 242