HP Virtual Connect for c-Class BladeSystem Version 4.10 User Guide Abstract This document contains user information for HP Virtual Connect version 4.10. 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.
© Copyright 2013 Hewlett-Packard Development Company, L.P. 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® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Contents Introduction .................................................................................................................................. 8 What's new .............................................................................................................................................. 8 Virtual Connect documentation.................................................................................................................... 9 Virtual Connect overview.............................
Managing users ...................................................................................................................................... 65 Local Users screen ......................................................................................................................... 66 Configuring LDAP, RADIUS, and TACACS+ ...................................................................................... 68 Virtual Connect networks .............................................................
Managing server profiles ....................................................................................................................... 175 Define Server Profile screen .......................................................................................................... 175 Server Profiles screen ................................................................................................................... 197 Edit Server Profile screen .....................................................
Domain Status screen............................................................................................................................. 268 Module status definitions and causes ....................................................................................................... 269 Export support information...................................................................................................................... 270 Reset Virtual Connect Manager ......................................
Upgrading OA from previous versions to OA 4.00 .......................................................................... 297 VC downgrades to versions older than 4.10 ................................................................................... 297 OA downgrades from OA 4.00 .................................................................................................... 297 Multi-enclosure considerations .............................................................................................
Introduction What's new The user guide contains information about the following changes in VC 4.10: • Manageability enhancements: o VC management support for IPv6 IMPORTANT: Use of IPv6 requires OA and iLO from SPP 2013.09.0 (B) or higher SPP releases. • o Ability to hide unused FlexNICs. The FlexNICs (physical functions) that do not map to profile connections are not enumerated in the OS as network interfaces.
• o The HP ProLiant BL460c Gen8 Server Blade o The HP FlexFabric 10Gb 2-port 534FLB Adapter o The HP FlexFabric 10Gb 2-port 534M Adapter o The HP QMH2672 16Gb FC HBA for BladeSystem c-Class VCEM compatibility: o VCEM requires IPv4 connectivity to manage Virtual Connect. o If you are running VCEM 6.3.1 or later to manage a VC 4.10 domain, the 4.10 domain can be in a VCDG in 3.30 firmware mode or later. To enable new features in VC 4.10, you must upgrade to VCEM 7.2.2 or later. VCEM 7.2.
• HP Virtual Connect Manager Command Line Interface for c-Class BladeSystem User Guide This guide provides information for using the Virtual Connect Command Line Interface, including use scenarios and complete descriptions of all subcommands and managed elements. • HP Virtual Connect Ethernet Cookbook: Single and Multiple Domain (Stacked) Scenarios This guide helps new Virtual Connect users understand the concepts of and implement steps for integrating Virtual Connect into a network.
NOTE: Using a Flex-10 capable NIC with an HP VC Flex-10 or FlexFabric module provides the ability to divide a 10Gb NIC into four FlexNICs with configurable bandwidth. • • VC-FC modules o HP VC 4Gb Fibre Channel Module for BladeSystem c-Class (enhanced NPIV) o HP VC 8Gb 24-Port Fibre Channel Module for BladeSystem c-Class o HP VC 8Gb 20-Port Fibre Channel Module for BladeSystem c-Class HP VCM NOTE: Beginning with VC 4.10, the HP 4GB Virtual Connect Fibre Channel Module is no longer supported.
Each version of VC is tested and supported with one or more SPPs. For a list of supported SPPs that must be installed, see the VC release notes.
HP Virtual Connect Manager Configuring browser support Access to the VCM GUI is provided through HTTPS (HTTP exchanged over an SSL-encrypted session) and requires HTTPS (port 443) to be enabled on the management network. The minimum supported screen resolution is 1024 x 768 with 256 colors. For optimal viewing, HP recommends setting the screen resolution to 1280 x 1024. Requirements The VCM web interface requires an XSLT-enabled browser with support for JavaScript 1.3 or the equivalent.
Pop-up windows must be enabled 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.
Command Line Interface overview The VCM Command Line Interface can be used as an alternative method for administering the VCM. Using the CLI can be useful in the following scenarios: • You can develop tools that utilize VCM 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. • You can batch commands using script files.
If the default password for the Administrator user has been changed and needs to be restored, see information about resetting the administrator password and DNS settings in the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation). Logon problems might be caused by the following: • You have recently upgraded the VCM firmware.
• HP Virtual Connect Manager Fibre Channel Setup Wizard • HP Virtual Connect Manager Server Profile Setup Wizard These wizards can also be launched at any time using the Tools pull-down menu at the top of the GUI. For more information about the setup wizards, see the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).
If a red icon with a horizontal white bar appears, an external manager such as VCEM is managing the VCM. Mouse over the icon to display a tool tip with information about the external manager. About HP Virtual Connect Manager To view detailed product information, select About HP Virtual Connect Manager from the Help pull-down menu.
• SAN Fabric • Network Access Group • Enclosure • Module • Interconnect Bay • Device Bay • IGMP filter • Filter set • FCoE network Menu items The following table lists the items available from the pull-down menu at the top of the screen.
Menu item Links to Index VC Manager help file index For This Page Help topic specific to the current page Virtual Connect Documentation on hp.com The Virtual Connect Documentation page on the HP website (http://www.hp.
Virtual Connect domains Understanding Virtual Connect domains A basic VC domain 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).
Managing domains Use the following screens to manage the VC domain: • • Domain Settings (Configuration) screen (on page 23) o Change the domain name o Delete a domain o Configure a customized login screen message Domain Settings (IP Address) screen (on page 25) o • • • Set a domain IP address for the VC domain Domain Settings (Enclosures) screen (on page 26) o View enclosures in the domain o Add enclosures to the domain o Remove enclosures from the domain Domain Settings (Backup/Restore)
Domain Settings (Configuration) screen Use this screen to change the domain name, delete a domain, configure and view auto-deployment, and configure a customized login screen message. To access this screen, click Configuration in the left navigation tree, or select Domain Settings from the Configure menu. Only users with domain role permissions can make changes on this screen. The following table describes the available actions in the Domain Settings (Configuration) screen.
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 257)." 2. Navigate to the Domain Settings (Configuration) screen (on page 23). 3. Click Delete. A domain name confirmation window is displayed. 4. Enter the name of the domain to be deleted.
Task Action View the configuration file Click View next to Configuration File. View the deployment log Click View next to Deployment Log. View the CLI output Click View next to CLI Output. For more information on auto-deployment, see "Appendix B: Auto-deployment process (on page 278)." Domain Settings (IP Address) screen Beginning with VC 4.10, VCM supports the use of IPv6 addresses.
Task Action Use a Virtual Connect Domain IPv4 or IPv6 Address setting • • For IPv4, select the box next to Use Virtual Connect Domain IPv4 Address, and then enter the IPv4 Address, Subnet Mask, and Gateway. For IPv6, select the box next to Use Virtual Connect Domain IPv6 Address, and then enter the IPv6 Address and Gateway. Save changes Click Apply. Cancel without saving changes Click Cancel. For more information on IPv6, see "Appendix C: Using IPv6 with Virtual Connect (on page 292).
Column Description OA IPv4 Address IPv4 IP address of the OA. "Local Enclosure" indicates this enclosure is managed by the local Onboard Administrator. OA IPv6 Address IPv6 IP address of the OA. "Local Enclosure" indicates this enclosure is managed by the local Onboard Administrator. Status Displays whether the enclosure has been imported Action Perform import and delete operations. The following table describes the available actions in the Domain Settings (Enclosures) screen.
o 3. Onboard Administrator Password Click OK. IMPORTANT: No more than four enclosures can be found or imported. If an enclosure is unintentionally found, it can be removed by clicking Delete. 4. Click the Import link in the Action column. -orLeft-click on the enclosure row, right-click to display a menu, and then select Import. Virtual Connect Manager imports the enclosure and provides status information.
Domain Settings (Backup/Restore) screen Use this screen to create a backup file of the Virtual Connect domain configuration to restore a configuration that has been lost, or to revert to a previously saved configuration. The domain configuration includes network definitions, MAC address settings, WWN settings, Fibre Channel fabric settings, local user accounts, and server profile definitions.
CAUTION: Restoring a Virtual Connect domain configuration from a backup file that was created on another Virtual Connect domain is not supported and can cause serious faults within this and other Virtual Connect Domains within the environment. The restore selection and configuration files should only be used to restore the same previously existing domain. 3.
Task Action Click Add below the table, or right-click inside the table, and then select Add a credential ("Adding or editing a credential" on page 31) Add. Click the Edit link in the Action column, or left-click on the credential row, Edit a credential ("Adding or right-click to display a menu, and then select Edit. editing a credential" on page 31) Delete a credential Click the Delete link in the Action column, or left-click on the credential row, right-click to display a menu, and then select Delete.
6. Click Apply.
protocol. The managed information is presented as a hierarchical database called a MIB. Each element of the managed information is identified by a unique identifier called Object ID. Basic SNMP support is provided for both VC-Enet modules and VC-FC modules. Each VC module has an independent SNMP agent that supports a set of MIBs. MIB support for each module depends both on the type of module (VC-Enet or VC-FC) and the role of the module in the VC domain.
MIB VC-Enet VC-FC VC LLDP MIB (LLDP-MIB) X — VC LLDPv2 MIB (LLDPv2-MIB) X — VC LACP MIB (LACP-MIB) X — VC QOS MIB (VC-QOS-MIB) X — * Not supported by the HP 8Gb 24-Port FC Module The VC Module MIB is a VC-specific MIB that describes the state of a specific VC module. In addition to unique VC module attributes, it defines traps for reporting alerts on port statistics, such as throughput, errors, and discards.
Trap vcFcFabricManagedStatusChanged 3 Category Severity MIB VCM Fabric Status Corresponds to the VCD-MIB name of the new state — — VC module status change (deprecated) — vcModuleManagedStatusChanged Profile status change (deprecated) VC-Enet Module Status or Corresponds to the VCD-MIB VC-FC Module Status name of the new state — — — vcProfileManagedStatusChanged3 VCM Profile Status Physical server change (deprecated) — vcPhysicalServerManagedStatusChang ed3 VCM Server Status Corresponds to t
connUnitPortStatus value Severity ready NORMAL warning WARNING failure CRITICAL nonparticipating INFO initializing INFO bypass INFO ols MAJOR other INFO Trap categories and required user role permissions In general, users with domain role permission can perform any SNMP configuration change operations. Users with network role permission can perform Ethernet configuration change operations, and users with storage role permission can perform FC configuration change operations.
• INFO—Operational information on the fully functioning component. • UNKNOWN—VC Manager has not yet established communication with the component. • NORMAL—The component is fully functional. Trap severities are only supported for VC-Enet or VCM traps. VC Module MIB traps The following table lists traps in the VC Module MIB. Trap name Trap data Description vcModRoleChange moduleRole The VCM role of the module has changed.
Trap name Trap data Description vcModPortProtectionConditio Port index to the ifTable (ifIndex) nDetected Port index to the vcModulePortTable Port protection status A port protection condition is detected on this port. If the new port protection status is a value other than OK, the port may be disabled to protect the VC module from further service degradation. Administrative action is required to recover the port from this condition.
Modules not redundantly connected, failure of module enc0:iobay1 or enc0:iobay2 or enc1:iobay2 will isolate some modules; Port enc0:iobay5:d3:v1 loop detected and automatically disabled The domain managed status ReasonCodes are provided in the following table. Domain reason code Description vcDomainOk All enclosures and profiles are normal in the domain. vcDomainAbnormalEnclosuresAndProfil One or more enclosures and profiles are abnormal in the domain. es At least one enclosure is not OK or Degraded.
Module reason code Description vcEnetmoduleEnclosureDown The module is unable to communicate with the enclosure/OA. vcEnetmoduleModuleMissing A configured module has been removed. vcEnetmodulePortprotect A condition has been detected on the port causing port protection to be activated. vcEnetmoduleIncompatible The module is incompatible, for example, a configured Enet module is replaced with an FC module. vcEnetmoduleHwDegraded The module is being reported as degraded by the OA.
vcEnetNetworkManagedStatusChanged The following is an example of an Ethernet network Cause string: Network BLUE has failed The following is an example of an Ethernet network RootCause string: Port enc0:iobay5:X3 is unlinked; Port enc0:iobay5:X4 is incompatible The Ethernet network managed status ReasonCodes are provided in the following table. Ethernet network reason code Description vcNetworkOk The network is functioning normally. vcNetworkUnknown The condition of the network is unknown.
vcDomainStackingLinkRedundancyStatusChange The stacking link connection redundancy status has changed. The vcDomainStackingLinkRedundant OID contained within this trap indicates whether all VC-Enet modules will remain connected to each other with the loss of a link. vcTestTrap The VC domain test trap is received when the administrator sends a test trap via the VC GUI or CLI. The test trap is sent to all configured trap destinations.
Field name Description Enable SNMP Select to enable SNMP. System Contact Specify a 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. The maximum length is 39 characters.
Adding an SNMP trap destination To add an SNMP trap destination, right-click the header row of the SNMP Trap Destination table, or click Add at the bottom of the SNMP Trap Destination table. You can configure up to five VC-Enet and five VC-FC SNMP trap destinations. To add an SNMP trap destination: 1. Enter a unique name for the new trap being added. No spaces are allowed. 2. Select the correct radio button, and then enter the IPv4 address, IPv6 address, or DNS name for the trap destination.
• Highlight the item, and then drag and drop it into the right window. Select trap severities To select a trap severity, do one of the following: • Highlight the item, and then click the right arrow. • Highlight the item, and then drag and drop it into the right window. For a definition of trap severities, see "Trap severities (on page 36)." When an event causes a trap to be generated with the severity listed in the right window, it is sent to the trap destination.
The VC-FC SNMP settings apply to all VC-FC modules in the VC domain. The following table describes the fields within the SNMP Configuration screen. Field name Description Enable SNMP Select to enable SNMP. Enable SMI-S Select to enable SMI-S. System Contact Specify a contact name for this system when SNMP is enabled. The maximum length is 20 characters. Read Community Controls SNMP read access when SNMP is enabled. The default value is "public".
Task Action Add SNMP access ("Adding SNMP access" on page 45) Click Add below the SNMP Access table, or right-click on the header row of the SNMP Access table, and then select Add. Delete SNMP access Click Delete in the Action column, or right-click on the SNMP Access row, and then select Delete. Add an SNMP trap destination ("Adding an SNMP trap destination" on page 44) Click Add below the destination table, or right-click on the header row of the destination table, and then select Add Destination.
Viewing the system log Use the following screens to view and configure domain system log information: • System Log (System Log) screen (on page 48) o • View logged information events within VCM System Log (Configuration) screen (on page 50) o View remote log destination settings o Set remove log destination settings System Log (System Log) screen The System Log screen displays logged information of events within Virtual Connect Manager.
System Log entry format A wide variety of events are generated by Virtual Connect and logged into the System Log, or SysLog. The remote logging capability is supported using the syslog protocol defined in RFC 3164. The remote logging feature also provides an option for transmission over TCP and secure transmission support using stunnel.
• SEVERITY_MINOR–An error condition that has no service impact • SEVERITY_MAJOR–A critical event that impairs service and requires immediate action (substantially diminished capacity or a service outage) • SEVERITY_CRITICAL–A critical event that severely impairs service and requires immediate action (substantially diminished capacity or a service outage) System Log (Configuration) screen Use this screen to view or set remote log destination settings.
To delete a remote log destination, select the checkbox next the preferred destination, and then click Delete.
If VCM is configured with a VC domain IP address, then future certificate requests generated will reflect this domain IP address. For information on generating a new certificate, see "SSL Certificate Administration (Certificate Signing Request) screen (on page 53)." For information on uploading certificates for use in the VC-Enet module, see "SSL Certificate Administration (Certificate Upload) screen (on page 56).
Row Description 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.
If the existing certificate has the proper key length, the data is accepted and is included in the certificate request, and is also included in the signed certificate. The fields that can be specified appear, populated with the values found in the existing certificate. The following table describes the fields on the SSL Certificate Administration (Certificate Signing Request) screen.
Field Possible values Description Organization Name (O) 1 to 60 characters in length The organization that owns this VC domain. When this information is used to generate a certificate signing request, the issuing certificate authority can verify that the organization requesting the certificate is legally entitled to claim ownership of the given company name or organization. Common Name (CN) 1 to 60 characters in length.
The certificate, by default, requests a valid duration of 10 years (this value is currently not configurable). When you click Apply, a standardized certificate signing request is generated by the Virtual Connect Manager using the supplied data. The content of the request in the text box can be sent to the Certificate Authority of your choice for signing.
When renewing certificates, the upload removes any previous Signed Certificate from VCM. You must add a new certificate or update with a renewed certificate in your browser. See browser Help for information on installing or renewing certificates. SSH Key Administration screen 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.
After you have authorized one or more SSH keys, you can delete all of them by clicking Clear SSH Keys. Removing the authorized SSH keys does not affect current SSH sessions. Web SSL Configuration screen This screen enables you to change the currently configured SSL encryption strength. This screen is only available to users with domain user role permission.
When the web SSL encryption strength is changed, logged in users are notified that they must reconnect.
HP BladeSystem c-Class enclosures 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 replacement of the enclosure midplane.
The management interfaces for all enclosure Onboard Administrators and VC modules within the same VC domain must be on the same lightly loaded subnet and highly reliable network. Overloads or loss of connectivity can disable configuration attempts until the connectivity is re-established and synchronized with the domain. The Onboard Administrator IP addresses used must be configured to be static.
have network and storage access. Both the Primary and Standby modules in the base enclosure must be recovered to regain management access to the VC domain. For more information, see the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation). Enclosures View screen This graphical representation consists of an enclosure front view and rear view.
Enclosures view (multiple enclosures) When more than one enclosure has been imported, each enclosure is displayed on the Enclosures View screen.
Virtual Connect users and roles Understanding VC administrative roles Each user account can be set up to have a combination of up to four user role permissions: • • • • Domain o Define local user accounts, set passwords, define roles o Configure role-based user authentication o Import enclosures o Name the VC domain o Set the domain IP address o Administer SSL certificates o Delete the VC domain o Configure SNMP settings Network o Configure network default settings o Select the MAC a
o Update firmware o Save configuration to disk o Restore the configuration from a backup It is possible to create a user with no user role permissions. This user can only view status and settings.
Local Users screen The first time this screen appears, the Administrator account, which has all administrative user role permissions, might be the only user listed. The Administrator account cannot be deleted or have domain user role permissions removed. However, the Administrator password can be changed, and the network, server, and storage user role permissions can be removed. The default Administrator password is identified on the Default Network Settings label on the primary VC module.
o Non-alphanumeric character Click Apply to save your changes. • To set a session timeout period, enter a number between 10 and 1440 in the Session Timeout box. To disable a session timeout period, enter 0. Click Apply to save your changes. Any change in the timeout value affects all open sessions and is applied to new sessions. • To edit the delete confirmation preference, select or clear Auto Populate Name During Delete Confirmation, and then click Apply.
Adding a new user Observe the following user settings guidelines: • Username is a required field. • The Username field must contain an alpha-numeric value with 1 to 31 characters. • The Password field must contain an alpha-numeric value with 3 to 40 characters. The default password length is 8 characters.
For LDAP authentication, the VCM contacts and external LDAP server on which user accounts have been set up. During login, VCM sends an authentication request to the server and waits for a login accept or login reject response from the server. RADIUS and TACACS+ provide remote user authentication. At login, an external RADIUS or TACACS+ server is contacted by the VCM to authenticate the user login.
Local users can test an LDAP configuration before applying it. For more information, see "Test LDAP authentication (on page 70)." The following table describes the fields within the LDAP Server Settings (LDAP Server) screen. Clicking another link in the pull-down menu or left navigation tree causes current edits that have not been applied to be lost. Field Description Enable LDAP Authentication Select to enable LDAP authentication.
7. Click Test. The status window displays any problems encountered during the test. When testing is complete, click Close. LDAP Server Settings (LDAP Groups) screen Use this screen to manage the LDAP Group settings for VCM. The following table describes the fields within the LDAP Server Settings (LDAP Groups) screen.
Field Description Group Name The Directory Server group name. Microsoft Active Directory servers have a reverse mapping from the user to the groups the user belongs to. To determine if the user is a member of the group, other servers might need to combine the Group Name with a Search Context to look up the group. To open the Edit LDAP Group window, click the Group Name.
Field Description Roles Select zero or more roles (Domain, Network, Storage, Server) to assign to the group. When a role is selected, the operations for the selected role have a checkmark next to them. Role operations can be edited from the "Role Management (Role Operations) screen (on page 84)." To add the new group, click Add. LDAP Server Settings (LDAP Certificate) screen Use this screen to manage LDAP server certificates. Directory Certificates provide authentication of the Directory Server.
Column Description 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 To The date and time when this certificate becomes invalid Delete Click X in the line of the certificate to delete.
Field Description Server Key A shared secret text string to be used for encrypting user details. This string must match between VCM and the RADIUS server. The secret-key is a plain text string of 1 to 128 characters. Add/Remove Secondary Server Select to add or remove a secondary RADIUS server. To add a secondary server, select the Add/Remove Secondary Server check box to display the Secondary Server Parameters, complete the fields as described in the table above, and then click Apply.
secret = require_message_authenticator = no } nastype = other The RADIUS server ignores authentication requests from an unknown client. Therefore, if the client entry is absent, the server ignores it. The server does not send a reject response. 4. Add the following to the dictionary file /usr/local/share/freeradius/dictionary.hp for HP: ATTRIBUTE HP-VC-groups 192 string HP The RADIUS server logs are available in the logfile /usr/local/var/log/radius/radius.log.
RADIUS Settings (RADIUS Groups) screen Use this screen to manage the RADIUS Group settings for Virtual Connect Manager. The following table describes the fields within the RADIUS Settings (RADIUS Groups) screen. Field Description Group Name The RADIUS group name. Roles Zero or more roles (Domain, Network, Storage, Server) assigned to the group. A user can be a member of multiple groups, in which case the roles are cumulative.
Add or Edit RADIUS Group Use this screen to add or edit a RADIUS Group. The following table describes the fields within the Add/Edit RADIUS Group screen. Field Description Group Name This is the group name value configured as the vendor-specific attribute HP-VC-Groups on the RADIUS server. The name can consist of 1 to 255 standard text-string characters (alphanumeric characters, hyphen (-), underscore (_), period (.)) except backslash (\) and single quote ('). You cannot change the name on edit.
Users with domain user role permissions can test a TACACS+ configuration before applying it. For more information, see "Test TACACS+ authentication (on page 82)." The following table describes the fields within the TACACS+ Settings screen. Clicking another link in the pull-down menu or left navigation tree causes current edits that have not been applied to be lost. Field Description Enable TACACS Authentication Select to enable TACACS+ authentication.
Required TACACS+ server settings The following TACACS+ server settings must be configured on VC to enable TACACS+-based authentication: • Enable or disable flag • TACACS+ server IP address • Server SSL port number—the default (well-known) value for TACACS+ authentication is 49. • Shared secret server key—this is a plain text key that must be configured both on VC and on the server. Both keys should match. The length of the secret key can vary from 1 to 128 characters.
autocmd = domain:network of privileges } <------- Colon-separated list } group = ALL_STAFF { } # End config file In this example, two different usages of autocmd= are shown: • Separate lines used for each privilege, supported in VC 3.30 and higher • Colon-separated privilege list, supported in VC 4.10 and higher Configuration can differ from one TACACS+ server to another. For more information, see the TACACS+ server documentation during configuration.
autocmd = network:server of privileges } <------- Colon-separated list } group = ALL_STAFF { } # End config file The configuration above is supported for the TACACS+ server downloaded from the tac plus website (http://www.pro-bono-publico.de/projects/tac_plus.html). Configuration can differ from one TACACS+ server to another. For more information, see the TACACS+ server documentation during configuration.
Role Management (Role Authentication Order) screen Use this screen to specify the authentication services to be used during log in and to set the order in which each authentication method is queried for each role. Role authentication order is followed for role-prefixed logins only, such as "domain:user1".
Role Management (Role Operations) screen Use this screen to change the role operations allowed for Network, Server, Storage, and Domain roles. You must have Domain Administrator role permission to make these changes. Changes apply to all users assigned to a given role. For example, if the Domain Administrator changes the role operations to allow Network users to export support files, all Network users are able to export support files.
Virtual Connect networks Understanding networks and shared uplink sets The VC-Enet modules use standard Ethernet bridge circuitry with special firmware so that they function 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.
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 Shared Uplink Set screen (on page 131).
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 network.
• • Ethernet Settings (Advanced Settings) screen ("Ethernet Networks (Advanced Settings)" on page 96) o Set Server VLAN Tagging Support o Set VLAN Capacity o Use the Multiple Networks Link Speed Settings to set a custom value for preferred link connection speed or maximum link connection speed o Enable or disable MAC Cache Failover o Modify the refresh interval for MAC Cache Failover o Enable or disable network loop protection for all VC-Enet modules in the domain o Reset network loop protect
o Edit a server profile o Define a new network o Illuminate the PID for all uplink ports associated with a network Network Access Groups screen Before VC 3.30, any server profile could be assigned any set of networks. If policy dictated that some networks should not be accessed by a system that accessed other networks (for example, the Intranet and the Extranet) there was no way to enforce that policy automatically. With VC 3.
The Network Access Groups screen is accessible to all users, but only users with network user role permissions can add, edit, and delete network access groups. The following table describes the available actions in the Network Access Groups screen. Task Action View networks that are members of a network access group Click the network access group name.
Define Network Access Group screen To access this screen, click Add at the bottom of the Network Access Groups screen (on page 89), or select Network Access Groups from the Define pull-down menu. To add a network access group: 1. Enter a name for the network access group in the Network Access Group Name field. The name can consist of up to 64 alphanumeric characters, including the hyphen (-), underscore (_), and period (.). 2.
This screen can only be edited by users with network role permissions, but it is viewable by all authorized users. To edit a network access group: 1. Enter a new name for the network access group in the Network Access Group Name field. The name can consist of up to 64 alphanumeric characters, including the hyphen (-), underscore (_), and period (.). You cannot rename the Default network access group. 2.
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. IMPORTANT: HP recommends that you do not use port monitoring with an analyzer in loopback configuration with any VC module. When port monitoring is enabled, a warning icon appears in the banner at the top of the page.
Field name Description • • • switch. Currently there is no active traffic on this link. Unlinked—There is no physical VC module or switch connection. FCoE Active—An FCoE network has been defined, uplinks are connected, and an FCoE-capable switch has been correctly configured. No FCoE—An FCoE network has been defined, uplinks are connected, but an FCoE-capable switch has not been configured, or the connection is to a non-FCoE switch.
Task Action Clear selections and settings without saving and return to the Virtual Connect homepage Click Cancel. Select Monitored Ports screen The Select Monitored Ports screen appears when you click the Select Ports button on the Ethernet Settings (Port Monitoring) screen. You can select up to 16 server ports to monitor. A counter at the top right of the screen displays the current number of selected physical ports.
Task Action Filter by Profile Filter the list by a specific profile Select All Profiles or a single profile from the Filter by Profile profiles list. The assigned networks are listed by each subport. If multiple networks are assigned, mouse over the label to see a listing of all networks associated with the subport. Filter by Physical Server Filter the list by server bay Select All Bays or a single bay from the Filter by Physical Server bay list.
You can tunnel VLAN tags and map VLAN tags in the same domain. As of VC 3.30, tunneling and mapping is configured at the network level, not at the domain level. Server VLAN tunneling is supported only on networks with dedicated uplinks and cannot be used with shared uplink sets.
IMPORTANT: Depending on the NIC firmware versions in use, you might need to upgrade the NIC firmware for these speed enforcement settings to work correctly. To change these settings: 1. Click the selection box, and then select a setting (100Mb to 10Gb): o Set preferred connection speed. This value is the default speed for server profile connections mapped to this network. The server administrator can increase or decrease this setting on an individual profile connection. o Set maximum connection speed.
• 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 the link, then the next best uplink is made active.
Pause flood protection Ethernet switch interfaces use pause frame based flow control mechanisms to control data flow. When a pause frame is received on a flow control enabled interface, the transmit operation is stopped for the pause duration specified in the pause frame. All other frames destined for this interface are queued up. If another pause frame is received before the previous pause timer expires, the pause timer is refreshed to the new pause duration value.
Configuration changes can be made without having to enable Throughput Statistics. Applying configuration changes when Throughput statistics is enabled clears all existing samples. Some conditions can clear existing Throughput Statistics: • Disabling the collection of Throughput Statistics clears all existing samples. • Changing the sampling rate clears all existing samples. • Power cycling a VC-Enet module clears all Throughput Statistics samples for that module.
• It provides Service Level Agreements for network traffic and to optimize network utilization. • Different traffic types such as management, backup, and voice have different requirements for throughput, jitter, delays and packet loss. • IP-TV, VOIP, and Internet expansion create additional traffic and latency requirements. • In some cases, capacity cannot be increased. Even when possible, increasing capacity may still encounter issues if traffic needs to be re-routed because of a failure.
The diagram below illustrates a pass-through configuration where packets are transmitted in the same order as they are received. The QoS feature introduced in VC 4.01 allows administrators to configure traffic queues for different priority network traffic, categorize and prioritize ingress traffic and adjust DOT1P priority settings on egress traffic.
The QoS screen is accessible to all users with network or domain role permissions. All other users have read-only access. Select the configuration type from the pull-down list: • Passthrough—Incoming non-FCoE packets are not classified or altered. There are no traffic classes, maps, or rules. • Custom (with FCoE Lossless) (on page 104)—Enable QoS and allow a customized configuration that includes FCoE class. The configuration defines two system classes: Best Effort and FCoE Lossless.
Traffic Classes A traffic class allows you to categorize packets requiring similar traffic management. The following table describes the columns on the traffic class screen. Clicking another link in the pull-down menu or left navigation tree causes current edits that have not been applied to be lost. Item Description Name Name of the traffic class. Real Time One user-defined class can be designated as real time.
Action Description Edit the Share for a traffic class Click on the number in the Share column, and then type in a new number. Click Apply. Edit the Max Share for a traffic class Click on the number in the Max Share column, and then type in a new number. Click Apply. Edit the egress DOT1P priority for a traffic class Click on the number in the Max Share column, and then select a new number from the pull-down list.
Virtual Connect uses the 802.1 Q priority for all other traffic. VC administrators can map DSCP/ToS values to 802.1p egress priorities to be set on packets before they are placed on an egress queue. Virtual Connect retains and obeys L2 markings on tunneled vNets without applying any changes to them. To change the traffic class for an Ingress DOT1P Value or Ingress DSCP Value, select a traffic class from the drop-down list, and then click Apply.
Item Description Share Minimum guaranteed bandwidth that each traffic class gets. The sum of shares of all enabled classes and the Best_Effort class equals 100. Max Share Maximum share that the traffic class can use when other traffic classes are not using their maximum share. Egress DOT1P Priority The egress dot1p priority marking on the VLAN tag. Enabled The FCoE Lossless and Best_Effort classes are enabled by default. Other classes are enabled if the checkbox in the Enabled column is selected.
Ingress Traffic Classifiers The Classification for uplinks and Classification for downlinks pull-down lists allow you to choose what classification method is applied to traffic in the specified direction. The default classification for uplinks is DOT1P. The default classification for downlinks is DSCP/DOT1P. When both DOT1P and DSCP are being used for one traffic flow, DSCP is used for IP traffic and DOT1P is used for non-IP traffic.
IGMP Settings (IGMP Configuration) screen From this screen you can do the following: • Enable or disable IGMP Snooping (on page 111) • Modify the idle timeout interval for IGMP Snooping • Allow or prevent flooding of unregistered IGMP multicast traffic • Monitor and manage multicast group membership for hosts subscribing to IGMP multicast traffic • Manage new Multicast Filter rules for a Multicast filter ("Multicast Filtering" on page 111) • Configure IGMP multicast filters and associate them w
Task Action Filter the entries in the table Click Filter, use the pull-down menus to select the filter you want to view, and then click Go. Edit a filter Click the Edit link in the Action column, or left-click on the filter row, right-click to display a menu, and then select Edit. Define a new filter Click +, or right-click in the table to display a menu, and then click Add. For more information, see "Add, edit, or delete a multicast filter (on page 113).
• If an empty filter or empty filter set is assigned to a profile Enet connection, no IGMP Report received from the respective server port is snooped. • If a filter rule is deleted from a multicast filter in use by a profile connection, it can take several seconds (up to the idle timeout setting) for the server port to be removed from the IGMP group table. With only IGMP Snooping enabled: • Multicast traffic for registered groups is forwarded to all member ports.
Add, edit, or delete a multicast filter Clicking another link in the pull-down menu or left navigation tree causes current edits that have not been applied to be lost. To add a multicast filter: 1. Click + in the Multicast Filtering section of the IGMP Settings (IGMP Configuration) screen ("IGMP Snooping" on page 111). 2. Enter a unique name for the multicast filter. 3. (Optional). Enter up to 16 labels. Labels are used to manage large numbers of filters. 4. (Optional).
Assigning a filter or filter set to a profile connection A Multicast Filter or a Multicast Filter Set can be associated with one or more server profile Ethernet connections. • If IGMP snooping is enabled, the defined filters are active after they are associated with a profile connection. • When IGMP snooping is disabled, you can still configure filters and assign them to profiles; however, IGMP filtering will not be in effect.
3. (Optional) Select a color for the set. 4. (Optional) Enter a label for the set. 5. Drag and drop multicast filters that should be members of the filter set from the Excluded filter set field to the Included filter set field. 6. Click Apply. To edit a multicast filter set: 1. Click on the set to edit. 2. Make any changes. 3. Click Apply.
Field name Description Network Network Name Name of the network Color A network can have a user-defined color to group and identify the network within VCM. Labels A network can have up to 16 user-defined labels to group and identify the network within VCM. Smart Link (on page 86) To enable Smart Link, edit the network settings after the network is created. The checkbox is not available until an uplink is added to the network.
Task Action Designate the network as a private network Select the Private Network checkbox. Enable VLAN tunneling Select the Enable VLAN Tunneling checkbox. Set a custom value for preferred link connection speed or maximum link connection speed Select the Advanced Network Settings checkbox. For more information, see "Advanced Network Settings (on page 119)." Set the Connection Mode Select Auto or Failover. For a description of these modes, see "Defining a network (on page 117).
8. Use the cascading menu to select a port, and then click Add to add one or more external ports. To ensure a high availability connection, select two or more ports. Only available ports are listed, displaying the current port link status. 9. Select the speed and duplex (where applicable) of the uplink ports. Click the pull-down box under Speed/Duplex, and then select a setting. Half-duplex operation is not supported by the VC-Enet module.
IMPORTANT: For best performance, HP recommends limiting the number of shared uplinks sets in one domain to two. There is a 1000 network limit per Virtual Connect domain. Advanced Network Settings These settings affect only newly created profiles. Versions of VC prior to v4.01 used the "preferred speed" to control bandwidth allocation. When existing profiles are upgraded to VC v4.01, the "maximum speed" from the network is set automatically on the connection.
Edit Ethernet Network screen To access this screen, do one of the following: • Click the Edit link for a network on the Ethernet Networks (External Connections) screen (on page 122). • Click a network on the Interconnect Bay Summary screen ("Ethernet Bay Summary (General Information) screen" on page 230). • Enter a network name in the Find Configuration Items search field in the left navigation tree, and then select the network.
Field name Description Enable VLAN Tunneling ("VLAN Tunneling Support" on page 86) Shows whether VLAN tunneling is enabled (checked) or disabled (unchecked) External Uplink Ports Shared Uplink Set/External VLAN ID/Native VLAN These options are only available if there are shared uplink sets defined. For more information, see “Shared uplink sets and VLAN tagging (on page 85).
Task Action Change the uplink interface port speed or disable the port Click the pull-down box under Speed/Duplex, and then select a 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 117)." Delete an added port Click the Delete link in the Action column, or left-click the port to select it, right-click to display a menu, and then select Delete.
Column name Description Ethernet Networks Shows the overall network status and network name Type Displays the type of network (ENET or FCOE) PID Shows whether the PID is on or off for the port Shared Uplink Set (VLAN ID) Shows the name of the shared uplink set and its VLAN ID (if applicable) Overall Port Status Shows the link status, link speed, and connectivity of the port. If the port is unlinked and no connectivity exists, the cause is displayed.
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.
• • • Edit Shared Uplink Set screen (on page 131) o Edit the properties of an existing shared uplink set o Add or delete an associated network Shared Uplink Sets (External Connections) screen (on page 134) o View a list of external shared uplink connections o Add a shared uplink set o Edit a shared uplink set o Delete a shared uplink set o Copy a shared uplink set Shared Uplink Sets (Associated Networks) screen (on page 137) o View mappings of networks to external shared uplink connections
Field name Description uplink sets with an associated FCoE network, the port role is N/A. Port Status Shows the link status, link speed, and connectivity of the port. If the port is unlinked and no connectivity exists, the cause is displayed. For more information about possible causes, see "Port status conditions (on page 261).
Task Action Add an associated FCoE network Click Add in the Associated FCoE Network section. For more information, see "Defining an FCoE network (on page 129)." Add a single associated network Click Add above the table, or right-click on the header row to display a menu, and then select Add. Select the a single Associated Network radio button, and then enter the network name and VLAN ID in the fields provided.
Aggregation groups require multiple ports from a single VC-Enet module to be connected to a single external switch that supports automatic formation of LACP aggregation groups, or multiple external switches that utilize distributed link aggregation. HP has guidelines available for users who wish to connect to external switches that support distributed link aggregation capabilities. Multiple aggregation groups may be formed from the ports selected for the network.
e. To add labels to the network, type a label in the Labels field, and then press Enter. Labels are used as text-based identifiers for the network within VCM. Each label can contain up to 24 characters, excluding spaces. Each network can have up to 16 labels. f. Select whether to enable (checked) or disable (unchecked) Smart Link (on page 86). g. Select whether to designate (checked) or not designate (unchecked) the network as a private network ("Private Networks" on page 86). h.
The following FCoE capable ToR switches have been tested and are supported with this feature: • Cisco Nexus 50x0 switch operating as either NPV Gateway or FC Forwarder (FCF). In FCF mode, FC SAN switches must be Cisco MDS family for interoperability. • Cisco Nexus 55xx switch operating as either NPV Gateway or FC Forwarder (FCF). In FCF mode, FC SAN switches must be Cisco MDS family for interoperability.
2. Enter the Network Name. The name can be up to 64 characters in length (no spaces). 3. Enter an external VLAN ID. 4. To add a color to the network, select a color from the Color pull-down menu. The network color is used as a visual identifier for the network within VCM. 5. To add labels to the network, type a label in the Labels field, and then press Enter. Labels are used as text-based identifiers for the network within VCM. Each label can contain up to 24 characters, excluding spaces.
Use this screen to edit the properties of an existing shared uplink set, add an associated network, or delete an associated network. This screen has the same fields as the Define Shared Uplink screen. The screen can be edited only by users with network role permissions, but it is viewable by all authorized users. The following table describes the fields within the Edit Shared Uplink Set screen.
Field name Description more information about possible causes, see "Port status conditions (on page 261)." ConnectorType 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 LLDP system name or management IP address and switch port number appear. A link is provided to obtain more information about the far-end switch port.
Task Action Change connection mode Select Auto or Failover. For shared uplink sets with an associated FCoE network, this setting is unavailable. Change the LACP timer Select Domain Default, Short, or Long for the LACP timer. Add an associated FCoE network Click Add in the table. For more information, see "Defining an FCoE network (on page 129)." Add a single associated network Click Add above the table, or right-click on the header row to display a menu, and then select Add.
This summary screen provides an overview of external shared uplink connections. This screen is only applicable if multiple networks identified by VLAN tags are being connected over a single external uplink set. The following table describes the fields within the Shared Uplink Sets (External Connections) screen. Field Description Shared Uplink Set Displays the status, UID, and name of the shared uplink set Has FCoE Indicates whether the shared uplink set contains an FCoE network.
Task Action Copy a shared uplink set Click the Copy link in the Action column, or left-click to select an uplink set, right-click to display a menu, and then select Copy. For more information, see "Copy Shared Uplink Set screen (on page 136)." Copy Shared Uplink Set screen To access this screen: • Click the Copy link for a shared uplink set on the Shared Uplink Sets (External Connections) screen (on page 134).
2. Create new network names for the associated networks (VLANs). To be renamed, all networks must share a common part of the naming convention. For example, if the original network names end in –A, you can replace that portion of the name with –B for the copied networks. a.
This summary screen displays the mapping of networks to external shared uplink connections. This screen is only applicable if multiple networks identified by VLAN tags are being connected over a single external uplink set. The following table describes the fields within the Shared Uplink Sets (Associated Networks) screen.
Virtual Connect fabrics Understanding FC fabrics Beginning with Virtual Connect 3.70, there are two supported VC SAN fabric types, FabricAttach fabrics and DirectAttach fabrics. A FabricAttach fabric uses the traditional method of connecting VC-FC and VC FlexFabric modules, which requires an upstream NPIV-enabled SAN switch.
• By default, all of the FlexFabric FC-capable uplinks are configured as Ethernet until they are configured as part of the VC SAN fabric. After the FC-capable uplinks are configured as part of the VC SAN fabric, the FC SFP transceivers connected to those uplinks become enabled and allow connectivity to the data center SAN fabric.
• The VC-FC and FlexFabric modules use dynamic login distribution to equally distribute server logins across all available uplink ports. The port with the least number of active logins is used for server connectivity. When the number of logins is equal, VC-FC or FlexFabric modules utilize a round-robin technique. • The VC-FC and FlexFabric modules use dynamic login distribution to provide an uplink port failover path that enables server connections to fail over within the VC SAN fabric.
Re-distribution allows server logins to be automatically redistributed to the newly available uplink ports to avoid an unbalanced situation. In addition, VCM enables you to manually re-distribute server logins at any time using the GUI or the CLI. For more information, see "Login re-distribution (on page 149).
• When creating the DirectAttach fabric, all participating uplinks can be connected to the same 3PAR storage system in order to form a VC SAN fabric correctly. When a DirectAttach VC SAN fabric is using multiple uplink ports, features of login balancing and login re-distribution are not applicable. These features apply only on the uplinks within a FabricAttach VC SAN fabric.
• You can attach up to four HP 3PAR storage systems directly to the VC FlexFabric module using a single VC SAN fabric. This limitation is due to the number of FC-capable uplink ports available on the FlexFabric module. Mixed FabricAttach and DirectAttach VC SAN fabrics Mixing FabricAttach and DirectAttach VC SAN fabrics is fully supported in the same Virtual Connect domain.
Bay groups In a multi-enclosure environment, all enclosures must have the same VC-FC and FlexFabric module configuration. For example, if the local enclosure has VC-FC modules in bays 3 and 4, each remote enclosure must also have VC-FC modules in bays 3 and 4. This is called an FC bay group. The concept of the FC bay group is applicable to both the FabricAttach and DirectAttach VC SAN fabric.
• • • o View of list of SAN fabrics with external connection information o Add, edit, or delete a fabric o Redistribute logins on a SAN fabric SAN Fabrics (Server Connections) screen (on page 155) o View a list of SAN fabrics with server connection information o Delete a fabric o Redistribute logins on a SAN fabric o Define a SAN fabric Edit SAN Fabric screen (on page 151) o Modify a fabric name o Set the uplink port speed o Change the login re-distribution o Add or delete an uplink
• Single enclosure domain • Multi-enclosure domain 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. Fabric Type The type of fabric. This option is available after a FlexFabric module port is added. Supported fabric types are FabricAttach and DirectAttach.
Column Description FabricAttach. Select FabricAttach if the FlexFabric module is connected using traditional SAN switches. For this fabric type, the advanced settings appear, allowing you to change the login re-distribution and set the preferred and maximum connection speed. Select DirectAttach if the FlexFabric module is directly connected to a supported storage target.
Task Description Set the preferred or maximum FCoE connection speed After a FlexFabric module port has been added, select the Show Advanced Settings checkbox, click the selection box, and then select a setting (0.1Gb to 8 Gb): • • Set Preferred FCoE Connection Speed—Applies to server profiles with an FCoE connection specified. Select a speed value for the FCoE connection and server port associated with this fabric.
• Set a custom value for the Maximum FCoE Connection Speed. This value is the maximum speed for server profile connections mapped to this network. To see how logins are currently distributed on the VC-FC module, navigate to the Interconnect Bays Status and Summary screen (on page 228) and select the desired VC-FC module. A new Uplink Port column is added to the Server Ports section of the screen.
To see how logins are currently distributed on the VC FlexFabric module, navigate to the Interconnect Bays Status and Summary screen (on page 228) and select the desired VC FlexFabric module. A new SAN Uplink Port column is added to the Server Ports tab. You can also see how logins are currently distributed on the VC-FC or FlexFabric modules by logging in to the upstream FC SAN fabric switch.
Use this screen to edit a SAN fabric configuration. The following table describes the fields within the Edit SAN Fabric screen. Field Description Fabric Fabric Name Descriptive name for the fabric. Do not use spaces. Status Status of the fabric Fabric Type The type of fabric, FabricAttach or DirectAttach. After a fabric is defined, its type cannot be changed. Login Re-distribution Login Re-distribution setting for the fabric. For all standard VC-FC modules, this is always Manual.
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 pull-down arrow in the Configured Speed field, and then select a speed. The default value is Auto, which auto-negotiates the speed with the FC switch to which the ports are connected. If 8Gb is chosen for the uplink speed on an FC module that does not support 8Gb, the value is automatically translated to "Auto" within VCM.
This screen lists all of the SAN fabrics that have been created and displays the external connection information. The following table describes the fields within the SAN Fabrics (External Connections) screen. Field Description Status Status of the fabric SAN Fabric Name of the fabric Fabric Type The type of fabric, FabricAttach or DirectAttach Login Re-Distribution Login Re-distribution setting for the fabric. For all standard VC-FC modules, this is always Manual.
Task Action Delete a SAN fabric Click the Delete link in the Action column, or left-click to select a fabric, right-click to display a menu, and then select Delete. Re-distribute logins Click the ReDistribute link in the Action column, or left-click to select a fabric, right-click to display a menu, and then select Redistribute Logins. SAN Fabrics (Server Connections) screen To access this screen, click SAN Fabrics in the left navigation tree, and then click the Server Connections tab.
Task Action Edit a SAN fabric Click the Go To Fabric link in the Action column, or highlight the desired SAN, right-click, and then select Go To Fabric. Edit a profile If necessary, click the + next to the fabric name to expand the information. Click the Go To Profile link in the Action column, or highlight the desired profile row, right-click, and then select Go To Profile.
Virtual Connect server profiles Understanding server profiles The I/O connection profile, or server profile, provides a link between the server and the networks and fabrics defined in VC. The server profile can include MAC and WWN addresses, as well as boot parameters for the various connection protocols supported by VC. After being defined, the server profile can be assigned to any server blade within the Virtual Connect domain. VCM supports up to 256 profiles within the domain.
• Before creating the first server profile, do the following: o Select whether to use assigned serial numbers or factory default serial numbers. o Select whether to use movable, administered MAC addresses and WWNs, or the local server blade factory default MAC addresses and WWNs. • After an enclosure is imported into a Virtual Connect domain, server blades are isolated from the networks and SAN fabrics until a server profile is created and assigned.
and 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 boot and gain access to the network and fabric when the server and interconnect modules are ready.
For more information, see "iSCSI and FCoE port assignments (on page 167)" and "Creating FCoE HBA connections for a BL890c i4 (on page 182)." • FC profile connection entries are mapped to blades such that all of the FC HBAs on the first blade are mapped first, then the HBAs on the second blade, and so on. When a profile is first created, it has enough FC profile connections for the HBAs on one blade. The maximum number of FC connections allowed is 4 times the original number of entries.
The total actual shareable bandwidth cannot exceed 10Gb; however, the preferred speed and maximum bandwidth settings can exceed a total of 10Gb, allowing ports to take advantage of unused bandwidth when available. A Flex-10 capable NIC (embedded Ethernet or mezzanine card) is seen as eight FlexNICs per 10Gb port if that NIC is directly connected to an HP Virtual Connect Flex-10 or FlexFabric module.
• Windows 2012 and higher (64-bit) • VMware ESXi 5.1 and higher (64-bit) • RHEL 5.8 and higher (64-bit with KVM) • RHEL 6.2 and higher (64-bit with KVM) • SLES 11 SP2 and higher (64-bit with KVM) When SR-IOV VFs are allocated to a connection, an event is logged to the VCM system log. The VCM system log indicates that SR-IOV has been enabled.
For more information, see "Bandwidth assignment (on page 169)." 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.
Because of the many possible configurations of the FlexFabric module, pluggable modules can differ for each uplink port on the FlexFabric module. If the uplink port is being used for an FC fabric, an SFP-FC connector is required. SFP speeds of 2Gb, 4Gb, or 8Gb are supported for this configuration. A 1G SFP connector is not supported on ports X1-X4 for either Ethernet or FC configurations. For Ethernet ports, the 10GbE SFP-LRM pluggable module is not supported on ports X1-X4.
• Use BIOS—Current BIOS settings are used for embedded NICs and mezzanine NIC PXE operations. VC Manager makes no changes to the current settings. This is not applicable to Flex-10 LOM ports when used with Flex-10 interconnect modules. In this situation, the USE-BIOS option for PXE boot in a VC profile always allows a server to PXE boot from a LOM port irrespective of the initial LOM settings in the BIOS utility (F9 screen).
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). iSCSI offload and boot The iSCSI configuration setup feature enables you to configure a server to boot from a remote iSCSI target as part of the VC server profile. Use the iSCSI offload feature to offload iSCSI protocol processing from the OS to the NIC.
The following steps provide an overview of the procedure to enable iSCSI boot: 1. Create iSCSI connections on the Profile page. 2. Enable boot on those connections by choosing Primary and optionally Secondary under Boot Setting. 3. Enter all iSCSI boot parameters for the primary and secondary connections. It is possible (and likely) that most or all the parameters associated with primary and secondary connections are the same. 4. Apply the Profile.
• The corresponding physical functions for each port on the same adapter must have the same personality. For example, if MZ1:1-b is iSCSI, MZ1:2-b must also be iSCSI; it cannot be Ethernet. • PXE and iSCSI can be enabled at the same time on a single port (PXE on a, iSCSI on b). • PXE and FCoE can be enabled at the same time on a single port (PXE on a, FCoE on b). • FCoE and iSCSI cannot be enabled at the same time on a single port, since they use the same PF.
Device Port Type VC Connections Assigned LOM 1 NC551i Enet 1, FCoE 1, Enet 7 2 NC551i Enet 2, FCoE 2, Enet 8 1 NC551m Enet 3, FCoE 3, Enet 9 2 NC551m Enet 4, FCoE 4, Enet 10 1 NC551m Enet 5, iSCSI 1 2 NC551m Enet 6, iSCSI (PF disabled) MEZ1 MEZ2 Bandwidth assignment In Flex-10 environments, four FlexNICs must share a single 10Gb link. Each FlexNIC is allocated a guaranteed portion of that 10Gb link's bandwidth and can transmit up to 10Gb.
In cases where the requested bandwidth settings you specified 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.
Ethernet Settings (MAC Addresses) screen To access this screen, click and expand the Ethernet link in the left navigation tree and select MAC Addresses, click Network Settings in the Network section of the home page, or select Ethernet Network Settings from the Configure menu at the top of the screen. This screen lists the MAC Address type and range that is used when creating server profiles.
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.
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. Access this screen in one of the following ways: • Click WWN Settings under Fibre Channel Settings in the left navigation tree. • Select Fibre Channel Settings from the Configure pull-down menu.
CAUTION: The use of Serial Number 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. Advanced Profile Settings MAC addresses for the domain are provided by Virtual Connect.
When assigning WWNs to FC HBA ports, Virtual Connect assigns 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. Virtual Connect assigns or migrates WWNs for server FC ports connected to HP Virtual Connect modules.
IMPORTANT: The data grids throughout the GUI are editable. Left-click the mouse to select a line to be edited. Right-click the mouse to bring up a context menu. NOTE: The process to assign, modify, or unassign a profile to an Integrity BL8x0c i2 server blade or Integrity BL8x0c i4 server blade can take up to several minutes. The following table describes the fields within the Define Server Profile screen.
Column name Description Profile Name Descriptive name for the server profile. The text can be up to 64 alpha-numeric characters, dashes, and underscores. Do not use spaces. Network Access Group Associates a network access group to the profile. The default network access group is "default." Hide Unused Flex NICs Prevents the operating system from enumerating FlexNICs, including those that are not mapped to profile connections. Enumerating the unmapped network resources might consume shared resources.
Column name Description Auto—The maximum port speed is determined by the maximum configured speed for the network. 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 behaves like "Auto". Custom—You can configure any speed from 100Mb to the maximum configured speed for the network in 100-Mb increments.
Column name Description types are "Auto", "Preferred", "Custom" and "Disabled". If a SAN Fabric is assigned to the connection, the supported port speed types are "1", "2", "4", "8", "Preferred", "Custom" and "Disabled". For all port speed types, if configured, the maximum allocated port speed is determined by the maximum connection speed for that SAN Fabric or FCoE network. Auto—VCM determines the appropriate port speed based on the available bandwidth for the port.
Task Action See "Multiple network connections for a server port (on page 192)." Change the port speed setting 1 2 Click the pull-down arrow in the Port Speed Type Column. Select Preferred, Auto, Custom, or Disabled. If Custom is selected, set the port speed, and then click OK. Enable or disable PXE, or Use BIOS 1 2 Click the pull-down arrow in the PXE column. Select Enabled or Disabled. If the existing PXE configuration on the server is correct, the 'Use BIOS' PXE setting should be chosen.
Task Action Cancel without saving changes Click Cancel. If using VC-assigned MAC addresses, WWNs, or non-default Fibre Channel boot parameters, always power off the affected server blades before assigning a profile. When assigning a VC-assigned serial number, power off the server blade. To power off a server blade, see "Server Bay status screen (on page 257)." To define a server profile: 1. Enter the server profile name. The server profile name can be up to 64 characters in length (no spaces).
6. Set up iSCSI HBA connections. See "Creating iSCSI connections (on page 185)." 7. Set up FC HBA connections. Two Fibre Channel connections exist for each set of horizontally adjacent interconnect bays in the enclosure that contain VC-FC modules. For each connection, do the following: a. Click the down arrow under FC SAN Name to select an available SAN. b. Click the down arrow under Port Speed to select Auto, 1Gb, 2Gb, 4Gb, 8Gb, or Disabled for that port. The default is Auto. 8.
mapped to LOMs 1 and 2 on blades 1 and 2. The next pair of entries for I/O bays 1 and 2 would get mapped to LOMs 1 and 2 on the third blade, and the fourth set of entries for I/O bays 1 and 2 would get mapped to LOMs 1 and 2 on the fourth blade. To have FCoE entries mapped to LOMs 3 and 4 on each blade in the server, you must add three extra sets of FCoE entries, and then add the additional entries for I/O bays 1 and 2. See ports 17-24 in the figure below.
A configuration with HP VC Flex-10/10D modules in I/O Bays 1 and 2 and HP VC FlexFabric modules in I/O Bays 3 and 4 in a pre-4.01 environment would only allow mapping of FCoE connections to the VC FlexFabric modules in I/O Bays 3 and 4. A server profile in this environment would have the following mapping for the Ethernet and FCoE connections. Ethernet connections are shown in the following table.
Ethernet profile connection Map to bay 2 14 Map to server port Not mapped FCoE connections for new profiles have changed to the connections shown in the following table. FCoE profile connection Map to bay Map to server port 1 1 LOM1:1B (FCoE network only) 2 2 LOM1:2B (FCoE network only) 3 3 Mezz1:1B (either FCoE network or SAN Fabric) 4 4 Mezz1:2B (either FCoE network or SAN Fabric) After upgrading from versions previous to VC v4.
• HP NC551m Dual-Port FlexFabric Converged Network Adapters • HP NC553i 10Gb 2-port FlexFabric Converged Network Adapter • HP NC553m 10Gb 2-port FlexFabric Converged Network Adapter • HP Virtual Connect FlexFabric 10Gb/24-port Module • HP Virtual Connect Flex-10 10Gb Ethernet Module • Any Ethernet switch • Any target that supports the iSCSI protocol, for example, the HP LeftHand Networks 2120 with 10Gb iSCSI (CX4 connection) You might need to update the BIOS on the mezzanine card for iSCSI to
Item Description Target Primary IP Address Primary IP address used by the iSCSI target Target Primary Port The TCP port associated with the primary target IP address. The default value is 3260. Target secondary IP Address Alternate target IP address to use if the primary port is unavailable Target secondary Port The TCP port associated with the secondary target IP address. The default value is 3260.
To use DHCP when configuring the iSCSI boot configuration, select the Use DHCP to retrieve iSCSI parameters check box. Selecting this option requires a DHCP server to be set up with iSCSI extensions to provide boot parameters to servers. The DHCP Vendor ID is offered by the initiator to the DHCP server to retrieve the iSCSI boot configured data. For more information, see the documentation that ships with the DHCP server and "DHCP option 43 (on page 190).
iSCSI Boot Assistant The iSCSI Boot Assistant retrieves the iSCSI boot and authentication data for HP LeftHand P4000 series devices, and then automatically populates most fields on the iSCSI HBA Connections screen (on page 185). This information enables you to configure a server to boot from an LHN target as part of the VC server profile. Before using the iSCSI Boot Assistant, you must complete the following: • Configure the LHN target with the boot volumes appropriately.
DHCP option 43 The format of DHCP option 43 is as follows: ‘iscsi:’’:’’:’’:’’:’’:’’:’’:’ • Strings shown in quotes are part of the syntax and are mandatory. • Fields enclosed in angular brackets (including the angular brackets) should be replaced with their corresponding values. Some of these fields are optional and can be skipped.
iscsi:”192.168.0.2”:”3261”:”000000000000000E”:”iqn.2009-4.com:1234567890 ”::”E”::”E” • o Target IP address: 192.168.0.2 o Target TCP port: 3261 o Target boot LUN: 0x0E o Target iqn name: iqn.2009-04.com:1234567890 o Initiator name: Not specified. Use the Initiator name already configured. Use the default name if none was configured. o Header Digest: Enabled o Data digest: Not specified. Assume disabled. o Authentication Type: One-way CHAP Default TCP Port and Mutual CHAP: iscsi:”192.168.0.
Define Server Profile screen (multiple enclosures) When defining server profiles in a multi-enclosure configuration, profiles can be assigned to server bays in any of the enclosures that have been added and imported into the domain. Multiple network connections for a server port Server port connections to virtual networks are defined on the Define Server Profile screen (on page 175).
To use this feature, under Ethernet Adapter Connections, select Unassigned or a network name, click the down-arrow, and then select Multiple Networks from the pull-down list. When the 'Multiple Networks' option is selected, a separate window is displayed to enable the defining and editing of virtual networks and VLAN ID mappings. A window appears and displays additional options.
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. You can choose only from a list of shared uplink sets when selecting Multiple Networks. After selecting a shared uplink set from the pull-down list, a list of VLANs that belong to the chosen shared uplink set is displayed. The server VLAN mappings are the same as those used on the shared uplink set, which are automatically displayed and cannot be changed.
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. 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.
IMPORTANT: Care must be taken not to exceed the limit per physical server port. For example, if you configure 150 VLAN mappings for a server connection (FlexNIC-a) of a Flex-10 physical server port, then you can only map 12 VLANs to the remaining three server connections (FlexNIC-b, FlexNIC-c, and FlexNIC-d) of the same physical server port. If you exceed the 162 VLAN limit, the physical server port is disabled and the four server connections are marked as Failed.
Server Profiles screen This screen lists all server profiles that have been defined within the domain, including assigned and unassigned profiles. From this screen, you 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.
Task Action Show all profiles, only assigned profiles, or only unassigned profiles Click the down arrow in the Show: box. Define a new profile Left-click in the table, right-click to display a menu, and then click Add; or select Server Profile from the Define menu at the top of the screen; or click Add at the bottom of the screen. Edit a server profile Left-click on the profile row, right-click to display a menu, and then click Edit; or click the Edit link in the Action column.
• Modify FC HBA 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 • Modify FCoE HBA connections • Set FC boot parameters NOTE: The process to assign, modify, or unassign a profile to an Integrity BL8x0c i2 server blade can take up to several minutes.
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. Hide Unused FlexNICs Prevents the operating system from enumerating FlexNICs, including those that are not mapped to profile connections. Enumerating the unmapped network resources might consume shared resources. Selecting this option might reorder NIC enumeration in the host operating system.
Column name Description administrator to manually readjust the network configuration, such as NIC teaming, to restore communication.
Column name Description iSCSI HBA Connections Port Relative order of the iSCSI port on the server receiving the profile Network Name Unassigned or name of the network associated with this port Status Displays the current linked status of the selected port Port Speed Type The requested operational speed for the server port. Valid values include "Auto", "Preferred", "Custom", and "Disabled". The default value is "Preferred".
Column name Description the connection. For the HP Virtual Connect 4Gb FC Module, supported speed values include "Auto","1Gb","2Gb", "4Gb", and "Disabled". If the value is set to 8Gb, the speed is auto-negotiated by Virtual Connect.* WWPN As of VC 3.70, the actual hardware WWN for mapped connections appears. For unmapped connections, FACTORY-DEFAULT continues to appear. If the profile is assigned, the WWN assigned to the port appears.
Column name Description profile is unassigned and the domain is set to show factory default MAC addresses, FACTORY-DEFAULT appears. If the profile is using VC-defined MAC addresses, the VC-defined MAC address appears. If the profile is using hardware MAC addresses, FACTORY-DEFAULT appears. Mapping Server hardware mapping assignment. See "iSCSI and FCoE port assignments (on page 167)." Action Delete a connection. Connections can be removed starting with the last connection in the list.
Task Action right-click to display a menu, and then click Delete. Add an iSCSI connection Click Add at the bottom of the iSCSI HBA Connections table, or right-click in the table, and then select Add. Delete an FC SAN connection Click the Delete link in the Action column, or click the connection to select it, right-click to display a menu, and then click Delete. Add an FC SAN connection Click Add at the bottom of the FC HBA Connections table, or right-click in the table, and then select Add.
b. Hover the mouse over each server blade in the Front View of the enclosure to find the HP ProLiant BL680c G7 Server Blade, and then click the server blade. The Server Bay Status screen appears. You can also view this screen by clicking the HP ProLiant BL680c G7 Server Blade device bay from the Device Bays link in the Hardware section in the left navigation tree. c. 2. Be sure that the Power Status/Control status value is Off. If the status is On, click Momentary Press to power down the server blade.
a. Click SAN Fabrics in the left navigation tree or select SAN Fabric from the Define menu at the top of the screen. b. Right-click the heading row on the External Connections tab on the SAN Fabrics screen, and then select Add or click the Add button. The Define SAN Fabric screen appears. c. Enter a Fabric Name, and then select an available port of an available bay for the SAN fabric from the Add Port pull-down list. Select one or more uplink ports for an HP VC FlexFabric 10Gb/24-port Module. d.
e. Be sure that the SAN fabric appears on the SAN Fabrics screen with the appropriate bay and ports assigned. 3. Add a server profile for the HP ProLiant BL680c G7 Server Blade. a. Click Server Profiles in the left navigation tree or select Server Profile from the Define menu at the top of the screen. b. Right-click the Server Profiles list on the Server Profiles screen, and then select Add, or click the Add button. The Define Server Profile screen appears. c. Enter a Profile Name.
d. If necessary, click Unassigned in the Ethernet Adapter Connections section, and then select an available network from the pull-down list. e. In the FCoE HBA Connections section, click the Unassigned FC SAN Name for the bay you used when you created the SAN fabric in step 2, and then select the SAN fabric you created from the pull-down list.
f. In the Assign Profile to Server Bay section, select the bay for the HP ProLiant BL680c G7 Server Blade to which you want to assign the server profile from the Unassigned Server pull-down list. g. Click Apply to save changes and stay on this screen, or click Apply & Close to save changes and to go the Server Profiles summary screen. h. On the Server Profiles screen, be sure that the server profile with FCoE connections has been properly assigned. 4.
a. Click the device bay for the HP ProLiant BL680c G7 Server Blade in the Server Bay Assignment column of the Server Profiles screen, or from the Device Bays link in the Hardware section in the left navigation tree. The Server Bay Status screen appears. b. Click Momentary Press to power up the server blade. c. 5. Be sure that the Power Status/Control indicator turns green and the status value is On. Verify the HP ProLiant BL680c G7 Server Blade FCoE connections: a.
Unassigning a server profile with FCoE connections to an HP ProLiant BL680c G7 Server Blade and deleting the SAN fabric To unassign a server profile with FCoE connections from an HP ProLiant BL680c G7 Server Blade and delete the SAN fabric: 1. Be sure that the HP ProLiant BL680c G7 Server Blade is powered down: a. Click the HP ProLiant BL680c G7 Server Blade device bay in the Device Bays link in the Hardware section in the left navigation tree. The Server Bay Status screen appears. b.
c. Click Apply to save changes and remain on the Edit Server Profile screen, or click Apply & Close to save changes and go to the Server Profiles screen. d. On the Server Profiles screen, be sure that the Server Bay Assignment for the server profile with FCoE connections is Unassigned.
e. Right-click the server profile with FCoE connections, and then select Delete. f. 3. In the Confirmation dialog box, enter the name of the server profile, and then click OK. Delete the SAN fabric: a. Click SAN Fabrics in the left navigation tree. The SAN Fabrics screen appears.
b. On the External Connections tab, right-click the SAN fabric you want to delete, and then select Delete. c. In the Confirmation dialog box, enter the name of the SAN fabric, and then click OK.
d. Click the HP ProLiant BL680c G7 Server Blade device bay in the Hardware Overview section in the left navigation tree. The Server Bay Status screen appears. Be sure that the Power Status/Control status value is Off. e. Scroll down to the Server Ethernet Adapter Information section and be sure that no assigned SAN fabric appears in the Network column for the HP ProLiant BL680c G7 Server Blade.
• When a profile is added, the FC/FCoE connections initially displayed are based on the FC/FCoE module configuration in the domain. A pair of horizontally adjacent FC/FCoE-capable modules has two connections. • Connections can only be added or removed from the bottom. You can only add or delete connections at the end of the list. • You can remove connections at any time (one at a time, from the bottom).
4 Start with modules in Bays 3 and 4, create a profile (add 2 connections), install modules into Bays 5 and 6, then edit the profile. Port 1 2 3 4 Connected to — Bay 3 Bay 3 Bay 4 Bay 5 Bay 3 — Bay 4 — Bay 4 Bay 6 — Add connection is disallowed because the current FC module configurations do not match the existing connections in the profile. This profile is not useful after the hot-plug install. To resolve this issue, delete connections 3 and 4, save the profile, and then scenario 3 applies.
9 Start with FCoE-capable modules in Bays 1 and 2, then create a profile and add connections. Port 1 2 Connected to Bay 1 Bay 1 — Bay 2 — — Bay 2 — — — Port Connected to 1 Bay 1 2 Bay 2 3 Bay 1 4 Bay 2 5 Bay 1 6 Bay 2 7 Bay 1 8 Bay 2 Add connection, 6 times* 10 Port Start with 8 FCoE-capable 1 modules, then create a profile and add connections.
IMPORTANT: If you plan to use Insight Control Server Deployment for RedHat Linux installation and also plan to use User- or HP-defined MAC addresses, you must import the enclosure and assign profiles before running Insight Control Server Deployment. "Rip and replace" is not supported in a Virtual Connect environment. For more information on HP Insight Control Server Deployment, see the HP website (http://www.hp.com/servers/rdp).
Virtual Connect modules Firmware updates To update firmware, use the HP BladeSystem c-Class Virtual Connect Support Utility v1.9.0. For more information on updating the firmware, see the HP BladeSystem c-Class Virtual Connect Support Utility documentation on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).
• The VCM configuration, module types, and cabling configuration must be the same before and after the upgrade. • The VCM credentials must be the same before and after the upgrade. • Do not perform a downgrade if servers are powered on or if a server profile migration operation has been performed since the upgrade. Performing a downgrade under these conditions can result in duplicate MACs/WWNs in the domain.
o • Failed indicates that one or more modules are not connected properly. Check the cable connections. Redundancy Status indicates whether all VC-Enet modules would remain fully interconnected if a module or external cable was removed or had failed. Horizontally-adjacent modules are considered to have OK redundancy status because of the reliability of their internal link. o OK indicates that redundant/reliable connections exist.
The collection of Throughput Statistics can be enabled or disabled, and the sample rate can be configured. The sampling rate determines the total sampling time frame. The available sampling rates go from 1 to 5 minutes or 1 hour, collecting up to 12.5 days of samples, depending on the sampling rate. For detailed information about Throughput Statistics settings, see "Configuring Throughput Statistics (on page 100).
Task Action Refresh data in the chart Click Refresh at the button of the chart. The Refresh option will be disabled according to the sampling rate. It becomes enabled after the time frame established by the sampling rate has elapsed. Zoom selected chart range To draw a zoom area, click on the chart and drag the mouse until all the data points of interest are highlighted. A new chart is generated focusing on the points selected after releasing the mouse button.
Removing an enclosure To remove a remote enclosure from the domain: 1. Disassociate all profiles, networks, port sets, and port monitors from the enclosure. If the enclosure is currently in a No-COMM state, the remote enclosure remains in VC mode. The No-COMM condition must be repaired prior to the enclosure removal. 2. Take the enclosure out of VC mode manually with the Onboard Administrator command line for that enclosure. 3. Click Remove Enclosure.
Enclosure Status screen When a VC domain loses connectivity with a remote enclosure Onboard Administrator, the Enter OA Credential button appears on this screen. For more information, see "Recovering remote enclosures (on page 271)." The following table describes the rows within the Enclosure Status screen.
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.
Causes for INCOMPATIBLE status When an interconnect module status is INCOMPATIBLE, details can be viewed in the System log ("System Log (System Log) screen" on page 48). The system log provides information about why an interconnect module is marked incompatible so that proper corrective action can be taken.
• FC modules in multi-enclosure double dense domains When using VC-FC modules, multi-enclosure double dense domains require similar and compatible VC-FC modules in bays 5, 6, 7, and 8 in all enclosures. If a multi-enclosure double dense configuration contains incompatible VC-FC modules in bays 5, 6, 7, or 8 in either the local or remote enclosures, some or all of the compatible VC-FC modules in the remote enclosures might be designated INCOMPATIBLE after import. Corrective action: a.
Row Description Module Host Name Includes controls that enable you to set a custom host name for the module and reset the module Memory Module Usage Displays the current memory usage of the module in kilobytes. Under normal operating conditions, memory utilization generally remains below the threshold value of 90% (red line). Power Status/Control Power state of the device The following table describes the rows within the Interconnect Bay Information table.
Ethernet Bay Summary (Uplink Port Information) screen This screen provides a summary of the interconnect module uplink port information. To remove a module, see "Interconnect module removal and replacement (on page 262)." The following table describes the columns within the Uplink Port Information (Enet) table.
Column Description Port Uplink port number WWN Factory assigned WWPN for this uplink port SAN Fabric Name of the SAN Fabric connected to this port Port Speed Setting Speed setting of the uplink port Connector Status Status of the uplink port Connected To WWN of the principal FC switch to which the VC-FC uplink port is connected Detailed Stats / Info ("FC Port Detailed Statistics screen" on page 245) Click to display detailed statistics about this FC port.
Column Description 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 SAN Fabric Name of the SAN fabric associated with this port SAN Uplink Port SAN uplink port associated with this server port Profile Name of the server blade profile Status Shows the link status, link speed, and connectivity of the port.
Column Description Internal VLAN ID Internal VLAN ID used by Virtual Connect Manager Network Name The name of the network associated with this port (downlink ports only) LAG membership table Relates the LAG IDs and uplink ports, which can help you understand the information in the MAC address table LAG ID LAG IDs for this module Uplink Port(s) Uplink ports that are a member of the LAG ID Ethernet Bay Summary (IGMP Multicast Groups) screen This screen shows the IGMP multicast groups that are acti
Ethernet Bay Summary (Name Server) screen This screen contains a list of entries in the name server table for the VC FlexFabric module. The following table describes the columns within the Name Server table.
To refresh the statistics, click Refresh Statistics. The following tables describe the rows within the Ethernet Port Detailed Statistics screen.
DCBX Information* Description Overall Status The overall status of DCBX protocol exchange with peer entity. The status value “Ok” indicates that no error is detected in DCBX operation; for example, the protocol exchange is successfully completed, or the port is not enabled for DCBX. The status value “Failed” indicates an error in one of the DCBX feature information exchanges. The specific reason for the error appears in the individual feature state field below the pending status.
Port Statistic Description IpInReceives The total number of input datagrams received from interfaces, including those received in error IpInHdrErrors The number of input datagrams discarded because of errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, and errors discovered in processing their IP options IpForwDatagrams The number of input datagrams for which this entity was not their final IP destination.
Port Statistic Description 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) rec
Port Statistic Description 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.
Port Statistic Description 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.
Port Statistic Description 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.
Port Statistic Description 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.
Pluggable Module Information* Description vendor-oui IEEE company ID of the manufacturer (not HP). This is defined in SFF-8472 in the Vendor OUI [Address A0h, Bytes 37-39] field. vendor-part-number Manufacturer part number (not an HP part number). This is defined in SFF-8472 in the Vendor OUI [Address A0h, Bytes 40-55] field. vendor-revision Manufacturer part revision number (not an HP part revision number). This is defined in SFF-8472 in the Vendor OUI [Address A0h, Bytes 56-59] field.
The following tables describe the rows within the FC Port Detailed Statistics screen.
Port Statistics Description fcInvalidTxWords Number of invalid transmission words fcSmoothingOverflowErrors Frames received with no receive buffer available due to buffer-to-buffer credit handling errors fcDecodeErrors Number of decode errors FC Bay Summary screen This screen provides a summary of the interconnect module status and port information. To remove a module, see "Interconnect module removal and replacement (on page 262).
Row Description 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.
Column Description HBA Port HBA port number Server Blade Server blade bay location SAN Fabric Name of the SAN Fabric connected to this port To edit the SAN Fabric, click the SAN Fabric in the left navigation tree.
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 Device is disabled. Enable the component in Virtual Connect Manager. Initializing Device is initializing. Wait until initialization is complete. (This icon should only be seen at startup.) Unavailable Device is active but unable to provide service.
Server Bays Summary screen Device bay numbering is affected by whether the 'Allow the double density device bays' option was selected while using the Domain Setup Wizard. Bays might appear as 'Covered' or 'Unknown.' For more information, see "Double-dense server bay option (on page 251)." If a multi-blade server is installed, the bay numbering shows a span of bays, for example, Bays 1-4, in the Bay column. For more information, see "Multi-blade servers (on page 159).
If the VC domain is configured for double-dense server mode, and a profile is assigned to an empty double-dense server bay, then a hot-plug installation of a single-dense server into the corresponding single-dense server bay results in the profile not being activated because the profile is not assigned to the single-dense server bay. To recover the profile, assign the profile to the single-dense server bay.
If the Onboard Administrator is downgraded to a version lower than 3.70, subsequent recovery of the double-dense enabled enclosure might result in bays A and B being marked 'Unknown.
Integrity blade devices 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. (This icon should only be seen at startup.) Profile pending Device has a pending profile assignment. The profile might need changes that require power cycling the server.
Icon Operational state Meaning (orange) Corrective action configuration attributes. Incompatible Device does not match the configuration. BIOS version level is not at a level that supports Virtual Connect. No communication Cannot communicate with the device. Check the physical connections and IP address. Missing data VCM is missing data about one or more blades in the multi-blade server.
Icon Operational state Meaning Corrective action Missing Device is configured but not accessible. Device is not operational because of an error. Insert the correct hardware module. Failed Reset the device or application, or replace the device. Server Bay OA Communication Status icon definitions Icon Operational state Meaning Corrective action OK Device is fully operational. None Failed Cannot communicate with the device.
Server Bay Status screen To change the power state of the server, click Momentary Press. If the server is powered on, click Press and Hold to force a shutdown. The following table describes the rows within the Server Bay Status table in the Server Bay Status screen. Server Bay Status NOTE: Servers connected through VC 8Gb 24-Port FC Modules can take between 15 and 25 seconds to recover from a module uplink port failure.
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 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 on or off.
Column Description Port Number Relative Fibre Channel Port number Adapter Mezzanine number where the HBA is connected Module Port Module bay number and module port number to which the device is connected Model Type of mezzanine installed WWN World Wide Port Name of the port, either assigned by Virtual Connect or as provided by the hardware SAN Fabric Module bay number and module port number of the SAN fabric Server Bay Status screen - multi-blade servers To change the power state of the serve
The following table describes the rows within the Server Blade Information table in the Server Bay Status screen.
Port status conditions Port status information appears on several screens throughout the GUI. If a port status is unlinked and no connectivity exists, one of the following appears: • Not Linked/E-Key—The port is not linked because of an electronic keying error. For example, a mismatch in the type of technology exists between the server and module ports. • Not Logged In—The port is not logged in to the remote device.
Interconnect module removal and replacement Virtual Connect modules It is not necessary to remove the module from the domain if the module is not in use. The module is removed automatically from the domain without user intervention. Replacing a primary or backup VC module with a different VC module type is not allowed without first deleting the domain.
Replacing an HP 4Gb VC-FC Module, HP VC 4Gb FC Module, or HP 8Gb 20-Port FC Module with an HP VC 8Gb 24-Port FC Module 1. If necessary, upgrade the VC domain firmware. (Minimum v2.10 or higher is required to support the HP VC 8Gb 24-Port FC Module). 2. Verify that the replacement will result in a good configuration. See "Multiple enclosure requirements (on page 61)." 3. Verify that the user has server and storage role permissions. 4.
10. Re-assign the server profiles, and then add the FC connections to the profiles. Possible errors If the previous 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. Then, the correct module type can be inserted. If the previous steps have been followed and the server is not connecting properly to the network, power down the server, and then power it back up.
6. Ensure that the modules are removed from the Virtual Connect GUI. If the modules still appear on the GUI, there are still profiles with connections to the modules or networks with uplinks on the modules. Do not proceed until the modules are removed. 7. Install the HP Virtual Connect Flex-10, FlexFabric, or Flex-10/10D modules. 8. Reassign the server profiles or add the connections to the profiles, depending on what was done in step 3.
Upgrading to an HP Virtual Connect FlexFabric module from a VC-FC module Replacing any VC-FC module with an HP VC FlexFabric module: 1. If necessary, upgrade the VC domain firmware. (Minimum v3.15 or higher is required to support an HP VC FlexFabric module). 2. Verify that the replacement will result in a good configuration. See "Multiple enclosure requirements (on page 61)." 3. Verify that the user has server and storage role permissions. 4.
Maintenance and troubleshooting 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. To view a summary of systems that have an alert icon displayed, click the Domain Status link. See "Domain Status screen (on page 268).
Icon Status Description Disabled A device or item is disabled. Warning A device is initializing or susceptible to outage. Unknown Status of this item is unknown. Normal Status of this line item is okay. Informational — (blue) 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 access this screen, click the Domain Status link at the top left of the screen.
VC displays cause and root cause information for domain status alerts. To view detailed information about a device, click that device name in the list. Module status definitions and causes INCOMPATIBLE—Module is incompatible with the module in the horizontally adjacent bay. UNKNOWN—Status is unknown. The following table lists module status definitions and possible causes.
Status Possible cause Suggested action INCOMPATIBLE The module type is not supported by VC. Replace the module. Export support information Virtual Connect Manager enables you to generate a support log, which can then be exported for technical support assistance. This operation is available to users with the Export Support Files role operation assigned their VC role. For more information, see "Role Management (Role Operations) screen (on page 84).
• If the Force Failover checkbox is not selected or a VC-Enet module is not available in the alternate interconnect bay, the VCM restarts on the current VC-Enet module, and you are presented the logon screen for the current VC-Enet module after VCM restarts. Reset times depend on the size and complexity of the VC domain configuration. When resetting the VC-Enet module, VCM is temporarily unavailable.
Server blade power on and power off guidelines 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 administrators power off servers with the server console before attempting such operations within the Virtual Connect Manager. If any changes are made to a server profile that require modifications to the server, the server blade must be powered off.
Flex-10 connection changes that do not require power off With Virtual Connect v2.10 and higher, it is not necessary to power off a server blade with Flex-10 connections in the following instances: • • Changing a connection's network: o From a single network to another single network o From a single network to multiple networks o From multiple networks to a single network Modifying the networks or VLAN IDs in a connection with multiple networks With Virtual Connect v2.
• o Troubleshoot a problem o Setup, install, and configure HP Subscriber's Choice website (http://www.hp.
Appendix A: Using Virtual Connect with nPartitions Understanding nPartitions The HP BL870c i4 or HP BL980c i4 servers can be partitioned into separate, smaller servers, called nPartitions, using iLO. Each nPartition is treated identically to a server of comparable size and type. The set of blades that are conjoined by a Blade Link is referred to as a Blade Link Domain. An nPartition must be wholly contained within a blade link domain. The configuration of nPars is explained below.
o Bay 4 (HP Integrity BL890c i4 nPar) iLO controls the blade link to change the configuration of nPars in the blade link domain, and the information about the new configuration is communicated through the OA to VCM.
When the reconfiguration is done, the OA generates blade remove events for the first two blades, resulting in VCM treating the AA partition as having been removed. Then the OA generates a blade add event for the first blade that identifies it as a single-blade partition, and likewise for the second blade. No events (remove or add) occur for the third and fourth blades because the C and D partitions are not affected by the reconfiguration.
Appendix B: Auto-deployment process Overview of the auto deployment process Auto-deployment enables administrators to set up a configuration on the local management network to allow a form of pre-provisioning for Virtual Connect domain configurations. The deployment configuration provides easy, automated initial setup of domain configurations for one or more enclosures available on the network.
CentOS DHCP setup The setup on a Linux CentOS or RedHat distribution requires modification of the DHCP configuration file to support VC auto-deployment capabilities. Install the DHCP service if it is not already installed: >yum install dhcp If the DHCP server installation was installed at the time the OS was installed, then you must edit the /etc/dhcp/dhcpd.conf file. An example DHCP configuration file is provided below.
} } option bootfile-name “myconfig-1.script” hardware ethernet 00:02:c3:d0:e5:83; fixed-address 192.168.1.100; host enclosure2 { option tftp-server-name “192.168.1.3”; option bootfile-name “myconfig-2.script” hardware ethernet 00:02:c3:d0:e5:84; fixed-address 192.168.1.
>cp myconfig-2.script /tftpboot VC configuration file The following sample configuration script can be used for basic deployment testing of the DHCP and TFTP setup. After deployment, the domain configuration can be validated through the GUI or VCMCLI. Example myconfig.script #============================================ # myconfig.script # # A simple VCMCLI configuration script used # for Auto-Deployment testing # # Version 2012.0728.
NOTE: No enclosures currently exist in the domain. Please use the 'import enclosure' command to import an enclosure. GETTING STARTED: help : Displays a list of available subcommands exit : Quits the command shell ? : Displays a list of managed elements for a subcommand ? : Displays detailed help for a command ->import enclosure username=Administrator password=MyPassword Importing enclosure, please wait...
--- ->show auto-deployment ==================================================================== Status Last TFTP TFTP Server TFTP File Deployment Mode ==================================================================== Configuring -- -AUTO 192.168.1.102 myconfig.
Property Description TFTP Server The TFTP Server property displays the TFTP server used for the deployment operation. If the TFTP Mode is "AUTO", then the value is populated with the server provided by DHCP. If the TFTP Mode is "MANUAL", the value of the property is expected to be provided by the user with the VCMCLI set autodeployment command, and can also be configured in the GUI. This field allows an IPv4 or IPv6 address as well as a DNS name.
Typical failure deployment status values Status Comment Resolution Waiting for DHCP Cause: The DHCP server might not be properly configured to support auto-deployment (BOOTP settings). This status does not result in a failed deployment, but the deployment process enters a "polling" state waiting for DHCP to provide the appropriate TFTP settings to VC. If the deployment is in this state, the process can be stopped with the stop auto-deployment command if it cannot proceed.
Status Comment Resolution Configuration File Too Big The VC configuration file on the TFTP server is too Remove commands or comments from big. Configuration files are currently limited to 512K the file to make sure that it is smaller than in size. 512K, and start the deployment process again. Failed to Clear Domain Configuration A failure occurred while attempting to clear the domain configuration. This failure is generally caused by an internal failure, and typically should not occur.
add profile Profile1 add profile Profile2 add user Admin password=Admin123 privileges=* poweron server * Configuration file output During the processing of the configuration script downloaded from the TFTP server, the VCMCLI commands are executed appropriately to configure the domain. During this processing, VCMCLI might display SUCCESS or ERROR messages as a part of the command processing. The show auto-deployment output can be used to display the VCMCLI output during deployment.
Stopping a deployment operation If a deployment process is currently in progress, you can cancel the deployment process by using the stop auto-deployment command. A canceled deployment process results in the deployment status showing "Aborted by user". If the deployment was stopped while the domain was being configured, the domain is left in the state of the last executed configuration command.
VC GUI auto-deployment status and settings The Auto-Deployment Settings are available in the GUI under the Domain Settings page, as shown in the following figure. Deployment wait and retry states During the deployment process, three states exist that could cause the process to stall until a condition is resolved by the user.
Waiting for TFTP This wait/retry state can occur if the TFTP server to be used by the deployment is offline or is not accessible on the network, or if the TFTP configuration file cannot be downloaded from the TFTP server. Resolution includes testing the TFTP server to ensure it is accessible by other TFTP clients on the management network, and verifying the file referenced in the DHCP configuration to ensure it is correct for the TFTP server address and the configuration file on the TFTP server.
TFTP logging and enablement When deploying a large number of enclosures with the auto-deployment capability, it might be difficult to know which configurations completed (and when), and which configurations might have a failure or are stuck in a waiting loop because of a configuration issue. To help with deployment status awareness and provide a common place for TFTP logs, you can have the TFTP status and logs posted back to the TFTP server.
Appendix C: Using IPv6 with Virtual Connect IPv6 addresses in VC Beginning with VC 4.10, Virtual Connect interconnect modules can be configured to use IPv6 addresses for communication over an IPv6 management network. IPv6 address configuration is controlled by the OA. To enable IPv6 addressing in the VC, select the IPv6 enable check box in the OA web GUI page or execute the appropriate OA command in the OA CLI.
The DHCPv6 address is displayed in the OA web GUI as one of the addresses available for communication with the VC. VC 4.10 does not support stateless DHCPv6. EBIPAv6 address EBIPAv6 is the mechanism for configuring fixed addresses for VC management interfaces. This occurs through the OA web GUI or through the OA CLI. The EBIPAv6 option precludes the DHCPv6 option. Therefore, with EBIPAv6 enabled, VC does not configure a DHCPv6 address even if the DHCPv6 option is enabled.
• VCSU version 1.9.0 can be used to update VC to 4.10 using IPv4 as target addresses. Observe the following additional requirements for enabling IPv6 support in VC: • The ability to enable or disable IPv6 as a stack is an enclosure-wide configuration, and can be done using the OA CLI or the OA Web GUI. • Although IPv6 is supported on OA versions prior to 4.00, IPv6 support for VC requires OA 4.00 or later. • On versions earlier than OA 4.
Migrations Migration from IPv4 to a dual configuration VC version OA version <4.00 VC version <4.10 • • • • VC version 4.10 or higher • • • OA version 4.00 or higher • Upgrade VC to 4.10 or higher. Upgrade OA to 4.00 or higher. • Enable IPv6 on all OAs starting with the local enclosure. • Enable DCPv6 or RA-SLAAC or both to enable global addressing. Upgrade VC to 4.10 or higher. Enable IPv6 on all OAs starting with the local enclosure, if not already done.
When disabling IPv6 in a multi enclosure environment, ensure IPv4 addresses are configured and reachable in all the enclosures. IPv6 should be disabled in the primary enclosure first and then in the remote enclosures. When a multi-enclosure domain is in dual configuration (IPv4-IPv6), disabling IPv6 in the primary enclosure ensures that only IPv4 interconnect/OA module addresses are displayed to users in the VCM GUI and CLI.
must be enabled on OA 4.00. If IPv6 is enabled on OA 4.00, then VC4.10 can have IPv4 and IPv6 (dual) address configurations. If the OA is earlier than 4.00 and only VC is upgraded to 4.10, then VC remains in IPv4-only address configurations. In this mode, if you attempt to configure IPv6 addresses, then appropriate warning messages are displayed. Upgrading OA from previous versions to OA 4.00 To use IPv6 functionality on VC, the minimum version of OA must be 4.00. If only the OA is upgraded to 4.
• storage-management Appendix C: Using IPv6 with Virtual Connect 298
Acronyms and abbreviations BPDU Bridge Protocol Data Unit CFG constant frequency generator CHAP Challenge Handshake Authentication Protocol CMC centralized management console DNS domain name system DO data object FC Fibre Channel FCoE Fibre Channel over Ethernet FCS Frame Check Sequence GMII Gigabit media independent interface HBA host bus adapter IGMP Internet Group Management Protocol Acronyms and abbreviations 299
IQN iSCSI qualified name LACP Link Aggregation Control Protocol LAG link aggregation group LAG ID link aggregation group ID LDAP Lightweight Directory Access Protocol LHN LeftHand Networks LLA link local address LLDP Link Layer Discovery Protocol LUN logical unit number MAC Media Access Control NPIV N_Port ID Virtualization OA Onboard Administrator PF Flex-10 physical function PHY physical layer device Acronyms and abbreviations 300
PLS physical signaling POST Power-On Self Test QoS Quality of Service RADIUS Remote Authentication Dial-In User Service RBSU ROM-Based Setup Utility RD receive data RMON remote monitoring SIM Systems Insight Manager SLAAC stateless address autoconfiguration SMI-S Storage Management Initiative Specification SNIA Storage Networking Industry Association SR-IOV Single root I/O Virtualization SSH Secure Shell SSL Secure Sockets Layer Acronyms and abbreviations 301
TACACS+ Terminal Access Controller Access Control System Plus TCN Spanning Tree Topology Change Notification UDP User Datagram Protocol VCDG Virtual Connect Domain Group VCEM Virtual Connect Enterprise Manager VCM Virtual Connect Manager VCSU Virtual Connect Support Utility VF SR-IOV virtual function VID VLAN ID VLAN virtual local-area network WWN World Wide Name WWPN worldwide port name Acronyms and abbreviations 302
Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index A About menu 18 accessing HP Virtual Connect Manager 14 ActiveX 13 activity indicator 20 adding a credential 31 adding a RADIUS group 78 adding a user 66 adding an LDAP group 72 adding an SNMP trap destination 44 adding enclosures 27 adding FC connections 216 adding FCoE connections 216 adding new users 68 adding SNMP access 45 additional information 273 Advanced Network Settings 119 Advanced Profile Settings 174 assign server profiles 205, 276 attribute number 78 auto-deployment 24, 278 auto-deployme
Domain Settings (Backup/Restore) 29 Domain Settings (Configuration) screen 23 Domain Settings (Domain IP Address) 25 Domain Settings (Enclosures) 26 Domain Settings (Local Users) 66 Domain Settings (Storage Management Credentials) 30 domain static addressing 293 Domain Status screen 268 Domain Status summary 267 domain, deleting 23, 24 domain, managing 22 double-dense server blades 251 dynamic DNS 14 E EBIPAv6 address 293 edit a network access group 91 edit a RADIUS group 78 edit a server profile 198 edit
iSCSI boot 166 iSCSI Boot Assistant 189 iSCSI boot configuration 185, 190 iSCSI connections 175, 185 iSCSI offload 166 iSCSI port assignments 167 multicast filtering 110, 111, 113, 114 multiple enclosure guidelines 61 multiple enclosures, adding and importing 27 multiple enclosures, using 60 multiple networks link speed settings 97 multiple networks option 192 J N Javascript 13 name servers, interconnect bay 236 native VLAN 85 navigating the interface 18 network access groups 89 network analyzer port 9
Q Quality of Service 101, 103 R RADIUS authentication, testing 76 RADIUS group, adding 78 RADIUS Settings (RADIUS Groups) 77 RADIUS Settings (RADIUS Server) 74, 75 RADIUS, configuration 68, 75 read community 42, 45 reconfiguring nPars 276 recovering remote enclosures 271 Red Hat procedures 219 redeployment scenarios 288 remote enclosures, recovering 271 remote log test 50 remote logging 50 removing an enclosure 28, 226 required user role permissions, trap categories 36 resetting the system 270 restore doma
traffic classes 104, 107 trap categories 36 tree navigation 18 troubleshooting 267 troubleshooting, server profiles 271 tunnel VLAN tags 86 typical failure deployment status values 285 U unassigning server profiles 212 understanding nPartitions 275 unknown device bay 251 upgrading from older versions to VC 4.10 296 upgrading OA from previous versions to OA 4.
