HP Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem User Manual

HP Virtual Connect Manager Command Line

Part Number: 677486-003

Interface for c-Class BladeSystem Version

3.51/3.60 User Guide

Abstract

This document contains user information for the HP Virtual Connect Manager version 3.51/3.60 CLI. 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.

June 2012 Edition: 3

© Copyright 2012 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.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Introduction .................................................................................................................................. 6

What's new .............................................................................................................................................. 6

Changes from VC 3.30 to 3.51 ........................................................................................................ 6

Virtual Connect overview ............................................................................................................................ 6

Using multiple enclosures .................................................................................................................. 7

Command line overview ............................................................................................................................. 8

Command line syntax ................................................................................................................................ 8

Parameters ..................................................................................................................................... 8

Options .......................................................................................................................................... 9

Properties ....................................................................................................................................... 9

Command batching ......................................................................................................................... 9

Supporting comments and blank lines in CLI scripts ............................................................................ 10

Unassigning multiple profiles ........................................................................................................... 11

CLI command execution modes ................................................................................................................. 11

Remote access to the Virtual Connect Manager ........................................................................................... 12

Command output filtering ......................................................................................................................... 12

Command line ............................................................................................................................ 13

Subcommands ........................................................................................................................................ 13

Managed elements .................................................................................................................................. 13

all ............................................................................................................................................... 15

version ......................................................................................................................................... 15

banner ......................................................................................................................................... 15

config .......................................................................................................................................... 16

configbackup ................................................................................................................................ 17

devicebay .................................................................................................................................... 19

domain ........................................................................................................................................ 19

enclosure ...................................................................................................................................... 22

enet-connection ............................................................................................................................. 23

enet-vlan ...................................................................................................................................... 26

external-manager .......................................................................................................................... 27

fabric ........................................................................................................................................... 29

fc-connection ................................................................................................................................. 31

fcoe-connection ............................................................................................................................. 34

firmware ...................................................................................................................................... 37

igmp ............................................................................................................................................ 37

igmp-group ................................................................................................................................... 38

interconnect .................................................................................................................................. 38

interconnect-mac-table .................................................................................................................... 40

iscsi-boot-param ............................................................................................................................ 40

iscsi-connection ............................................................................................................................. 43

ldap ............................................................................................................................................ 46

ldap-certificate .............................................................................................................................. 47

ldap-group.................................................................................................................................... 48

link-dist-interval .............................................................................................................................. 49

lldp .............................................................................................................................................. 50

log-target ...................................................................................................................................... 50

Contents 3

loop-protect .................................................................................................................................. 52

mac-cache .................................................................................................................................... 53

nag-network .................................................................................................................................. 54

network ........................................................................................................................................ 55

network-access-group ..................................................................................................................... 59

network-range ............................................................................................................................... 60

port-monitor .................................................................................................................................. 63

profile .......................................................................................................................................... 65

radius .......................................................................................................................................... 69

radius-group ................................................................................................................................. 70

role ............................................................................................................................................. 72

server .......................................................................................................................................... 73

serverid ........................................................................................................................................ 75

server-port .................................................................................................................................... 76

server-port-map ............................................................................................................................. 76

server-port-map-range ..................................................................................................................... 78

snmp ........................................................................................................................................... 79

snmp-trap ..................................................................................................................................... 80

ssh............................................................................................................................................... 83

ssl ............................................................................................................................................... 84

ssl-certificate ................................................................................................................................. 84

ssl-csr ........................................................................................................................................... 85

stackinglink ................................................................................................................................... 86

statistics........................................................................................................................................ 86

statistics-throughput ........................................................................................................................ 88

status ........................................................................................................................................... 88

storage-management ...................................................................................................................... 89

supportinfo ................................................................................................................................... 90

systemlog ..................................................................................................................................... 91

tacacs .......................................................................................................................................... 91

uplinkport ..................................................................................................................................... 92

uplinkset ....................................................................................................................................... 95

user ............................................................................................................................................. 97

user-security .................................................................................................................................. 98

vcm ............................................................................................................................................. 99

User privileges ...................................................................................................................................... 100

Help subsystem ..................................................................................................................................... 104

Output format ....................................................................................................................................... 106

Interactive user output format ........................................................................................................ 106

Scriptable output format ............................................................................................................... 108

Statistics descriptions ............................................................................................................................. 110

Ethernet modules ......................................................................................................................... 110

Fibre Channel modules ................................................................................................................. 120

Configuring the Virtual Connect domain using the CLI ................................................................... 125

Basic configuration ................................................................................................................................ 125

Logging in to the CLI .................................................................................................................... 125

Domain setup .............................................................................................................................. 126

Network setup............................................................................................................................. 129

Server VLAN Tagging Support ...................................................................................................... 134

Fibre Channel setup ..................................................................................................................... 135

Serial number settings .................................................................................................................. 136

Server profile setup ...................................................................................................................... 137

Logging out of the CLI .................................................................................................................. 147

Contents 4

Common management operations ........................................................................................................... 147

Port status conditions ............................................................................................................................. 148

Resetting the Virtual Connect Manager ..................................................................................................... 149

Support and other resources ...................................................................................................... 151

Before you contact HP ............................................................................................................................ 151

HP contact information ........................................................................................................................... 151

Acronyms and abbreviations ...................................................................................................... 152

Documentation feedback ........................................................................................................... 156

Index ....................................................................................................................................... 157

Contents 5

Introduction

What's new

The command line interface user guide contains the following changes for VC 3.51:

• The output for the show server-port command has been updated.

Changes from VC 3.30 to 3.51

Command Changes Virtual Connect 3.30 Virtual Connect 3.51

show server-port

This command now shows the link status for FlexNIC ports. The profile column has been removed. The profile associated with the FlexNIC ports is now displayed as part of the physical port information.

Virtual Connect overview

HP Virtual Connect is a set of interconnect modules and embedded software for HP BladeSystem c-Class enclosures that simplifies the setup and administration of server connections. Virtual Connect includes the following components:

• VC-Enet modules

o HP 1/10Gb Virtual Connect Ethernet Module for c-Class BladeSystem o HP 1/10Gb-F Virtual Connect Ethernet Module for the c-Class BladeSystem

The FlexNIC port output columns were Adapter Type, Network, MAC Address, Fabric, Port, WWN, and Profile.

The FlexNIC port output columns are Status, Network, MAC Address, Fabric, Port, and WWN.

o HP Virtual Connect Flex-10 10Gb Ethernet Module for BladeSystem c-Class o HP Virtual Connect FlexFabric 10Gb/24-port Module for BladeSystem c-Class, which provides the

capability to configure Ethernet and FC/FCoE or iSCSI connections

• VC-FC modules

o HP 4Gb Virtual Connect Fibre Channel Module for c-Class BladeSystem o HP Virtual Connect 4Gb Fibre Channel Module for BladeSystem c-Class (enhanced NPIV) o HP Virtual Connect 8Gb 24-Port Fibre Channel Module for BladeSystem c-Class o HP Virtual Connect 8Gb 20-Port Fibre Channel Module for BladeSystem c-Class

• HP Virtual Connect Manager

Virtual Connect implements server edge virtualization between the server and the data center infrastructure so networks can communicate with pools of HP BladeSystem servers, and so you can upgrade, replace, or move server blades within the enclosures without changes being visible to the external LAN and SAN environments. The external networks connect to a shared resource pool of servers rather than to individual

Introduction 6

servers. Virtual Connect cleanly separates server enclosure administration from LAN and SAN administration.

VCM is embedded on the VC-Enet module. You can access VCM through a web-based GUI or CLI. The Onboard Administrator provides a web link to the Virtual Connect GUI.

The VC modules support the HP BladeSystem c7000 Enclosure, the HP BladeSystem c3000 Enclosure, and all the server blades and networks contained within the enclosure. FlexFabric modules are only supported in BladeSystem c7000 enclosures and G6 or newer server blades with Virtual Connect firmware v3.15 and later.

VC-Enet modules enable connectivity to all brands of data center Ethernet switches. VC-Enet modules can also be directly connected to other types of devices, such as printers, laptops, rack servers, and network storage devices.

The VC-FC and FlexFabric modules enable connectivity of the enclosure to Brocade, Cisco, McDATA, or QLogic data center FC switches. Every FC fabric is limited in the number of switches it can support, but the VC-FC modules do not appear as switches to the FC fabric and do not count against FC fabric limits.

A basic Virtual Connect 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). For more information on the double-dense option, see "Double-dense server bay option" in the user guide. Within the domain, any server blade with the requisite LAN or SAN devices can access any LAN or SAN connected to a VC module, and a server blade of a given processor type (Integrity or X86) can be used as a spare for any server blade of the same processor type within the same enclosure, as long as the server has the requisite number and type of connections. Using network access groups feature, the network administrator can clearly define a separation of networks based on their allowed functionality and prevent the server administrator from assigning specific network combinations in the same server profile.

By stacking (cabling) the VC-Enet modules together within the domain and connecting the VC-FC or FlexFabric module FC uplinks on the same bay of all enclosures to the same FC switch, every server blade in the domain can be configured to access any external network or fabric connection. With this configuration, you can use VCM to deploy and migrate a server blade profile to any server in the Virtual Connect domain without changing external LAN or SAN configurations.

Using multiple enclosures

Multiple enclosure support enables up to four c7000 enclosures to be managed within a single Virtual Connect domain for a total of 128 servers, if double-dense support is enabled while using the Domain Setup Wizard. There are 16 half-height or 8 full-height server bays in a c7000 enclosure. A combination of full-height and half-height servers can be used in the same enclosure.

Multiple enclosure domains are not supported on c3000 enclosures. The VC-Enet or FlexFabric modules use stacking cables between enclosures so that network traffic can be routed from any server Ethernet port to any uplink within the VC domain. Since FC does not support stacking, the VC-FC or FlexFabric module FC uplinks on the same bay of all enclosures must be connected to the same FC switch to enable profile mobility.

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. The Onboard Administrator user credential for all enclosures must be consistent to enable VCSU firmware updates for VC modules in the remote enclosures. All FC-capable modules in the same horizontally adjacent bay pair (bays 1-2, 3-4, and so on) must be of the same type and position in all enclosures.

Introduction 7

Multi-enclosure double-dense domains require similar and compatible VC-FC modules in bays 5, 6, 7, and 8 in all enclosures if FC connectivity is required. If a multi-enclosure double-dense configuration contains incompatible VC-FC modules in bays 5, 6, 7, or 8 in the local or remote enclosures, some or all of the compatible VC-FC modules in the remote enclosures might be designated INCOMPATIBLE after import.

Command line 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. These script files can be run manually or scheduled to run

automatically.

Command line syntax

CLI input is case-insensitive, except when otherwise noted. The general CLI syntax format is as follows:

<subcommand> <managed element> <parameters> [<options>] [<properties>]

Item Description

subcommand

managed element parameters options

properties

Operation performed on a managed element

Target management entity Command extensions for a particular management operation Attributes used to customize or control command execution behavior such as output

format, quiet-mode, and others One or more name and value pairs that are accessories to the command operation,

mainly for set and add operations

Example: ->add user mark password=asdf89g fullname="Mark Smith" enabled=true In the example, add is the subcommand, user is the managed element, mark is a required parameter for

the operation, password is a required property, and fullname and enabled are optional properties. Depending on the specific command being executed, certain parameters or properties might be required.

For example, when adding a new user, both a parameter representing the user name, as well as a password (in the form of a property) must be specified. All other user properties are optional at the time the user is added. In general, the properties are in the format name=value. Separate multiple properties with spaces.

Parameters

Parameters are command extensions that provide extra information needed for the execution of a particular command. Whether or not a parameter is required depends on the specific command being executed. For example, the show user command has an optional parameter, which represents the user name if the user instance is being managed. If show user is entered without the optional parameter, then a summary listing of all users is shown. However, if the optional parameter (user name) is provided, only a single user instance is displayed, for example, show user paul.

Introduction 8

Some commands require that a parameter be specified, for example, the add user command. The required parameter is the user name (add user jake), and if the username is not provided, an error message displays indicating that a required parameter is missing.

Options

Options enable users to control certain behavior characteristics available during the command execution. Some examples of options include controlling output format and specifying a quiet mode to suppress interactive prompts.

Distinguish options from other command line elements by using a preceding hyphen (-). Option arguments are required or optional, depending on the option being specified. For example, the -output option requires an argument, which is a list of one or more output format attributes. However, the -quiet option does not require any arguments to be specified.

The general format of a CLI option is as follows:

Example: ->show user suzi -output=script1

-<option>[=argument1>,<argument2>, . . .]

In the example, -output is the option, and script1 is an option argument.

Properties

Properties are specific configuration attributes of a managed element. Properties are commonly used during set operations or add operations where a managed element is being modified or created. In some limited circumstances, properties might also be used as a part of a show or other command.

IMPORTANT: If a property value contains embedded spaces, then the entire property value must

be contained within single or double quotes. Likewise, if a double quote is part of a property value, it should be contained within single quotes, and if a single quote is part of a property value, it should be contained within double quotes.

Command batching

Scripts are useful for batching many CLI commands. You can create a single CLI script to configure an entire VC domain from scratch and use it on multiple enclosures.

When using a Linux SSH client, simply redirect the script into SSH. If the SSH keys are not configured on the client and in the firmware, a password prompt appears. To enable script automation and better security, SSH public/private key-pairs can be generated and uploaded to the public key to the VC firmware. For example:

>ssh Admin@192.168.0.120 < myscript.txt

When using a Windows-based SSH client, pass the file to the client using the -m option. If the SSH keys are not configured on the client and in the firmware, a password prompt appears. To allow script automation and better security, SSH public/private key-pairs can be generated and uploaded to the public key to the VC firmware. For example:

>plink Admin@192.168.0.120 -m myscript.txt

The CLI enables you to enter multiple CLI commands in a single command-line invocation. This capability is useful when batching several commands together and executing them in a particular sequence, within the context of the same SSH session. This method improves the overall performance of lengthy script processing.

Example 1: Sample commands with no command batching

Introduction 9

add profile Profile1 add network Network1 add uplinkset UplinkSet1

Example 2: Sample commands using command batching

add profile Profile1;add network Network1;add uplinkset UplinkSet1

Supporting comments and blank lines in CLI scripts

The CLI supports command scripts that contain blank lines and comments. Support for comments and blank lines enables you to maintain descriptive notes within the configuration script.

The following sample script illustrates a CLI script that contains this type of formatting. All comment lines must begin with "#".

#-----------------------------------------------------------------------# This is my sample Virtual Connect Domain Configuration Script # Revision 1.0.1.2 # February 15, 2012 #------------------------------------------------------------------------

# Add Users add user SomeNetworkUser password=pass1 privileges=network add user SomeStorageUser password=pass2 privileges=storage add user SomeDomainUser password=pass6 privileges=domain add user SomeAdminUser password=pass3 privileges=* add user DomainNetworkUser password=764dhh privileges=domain,network

# Add Profiles with Default VC-Enet and VC-FC Connections add profile MyProfile add profile AnotherProfile add profile Profile45

# Add VC-Enet Networks add network MyNetwork add network Network2

# Add uplink ports to the networks add uplinkport enc0:1:1 network=MyNetwork add uplinkport enc0:1:2 network=Network2

# Create a Shared Uplink Port Set add uplinkset SharedSet1

Introduction 10

# Assign a profile to a device bay assign profile MyProfile enc0:1

# Done!!!

Unassigning multiple profiles

The unassign profile command includes the ability to unassign multiple profiles from device bays with a single command.

The following example illustrates four server profiles being unassigned from device bays with a single CLI command. If an operation fails on one of the device bays, an error message appears for that server or device bay, but the remaining operations continue.

->unassign profile * SUCCESS: Profile1 unassigned from device bay enc0:1 SUCCESS: MyProfile2 unassigned from device bay enc0:2 SUCCESS: GreenProfile unassigned from device bay enc0:3 SUCCESS: RedProfile unassigned from device bay enc0:4

CLI command execution modes

The Virtual Connect Manager CLI provides two different methods for executing commands: interactive shell mode and non-interactive mode.

Interactive Shell Mode This mode is used to invoke CLI command operations with the dedicated management shell. The shell is

provided after you log in with valid credentials, and only accepts known VCM CLI commands as input. You can quit the shell by using the exit command. See the example of logging in to the interactive management shell below. In the example, the primary VCM is located at IP address 192.168.0.120.

>ssh 192.168.0.120

--------------------------------------------------------------------

GETTING STARTED:

help : displays a list of available subcommands exit : quits the command shell <subcommand> ? : displays a list of managed elements for a subcommand <subcommand> <managed element> ? : displays detailed help for a command

Non-Interactive Mode

Introduction 11

In some cases, you might want to write automated scripts that execute a single command at a time. These scripts can be used to batch several commands in a single script file from the SSH client. See the example of how to use the non-interactive mode for CLI command execution below. In the example, the primary VCM is located at IP address 192.168.0.120.

->ssh Administrator@192.160.0.120 show enclosure <command output displayed to user's screen>

IMPORTANT: To suppress prompting for a password during login, you must first setup the SSH

encryption keys using the VCM Web GUI, and configure your SSH client properly with the keys. For additional information on configuring the SSH keys, see the HP Virtual Connect for c-Class BladeSystem User Guide.

Remote access to the Virtual Connect Manager

To access the VCM CLI remotely through any SSH session:

1. Using any SSH client application, start an SSH session to the Virtual Connect Manager.

2. When prompted, enter the assigned IP address or DNS name of the Virtual Connect Manager.

3. Enter a valid user name.

4. Enter a valid password. The CLI command prompt appears.

5. Enter commands for the Virtual Connect Manager.

6. To terminate the remote access SSH session, close the communication software or enter exit at the CLI

command prompt.

To access the VCM CLI remotely through the Onboard Administrator CLI, run the connect interconnect command from the Onboard Administrator CLI.

Command output filtering

The CLI provides output filtering capabilities that enable you to display only properties of interest. This feature is useful for filtering large amounts of output data for specific information. One or more properties can be specified in the output filtering rules.

The following examples illustrate some common usage scenarios for output filtering: Example 1: Displaying all enabled users

->show user enabled=true

Example 2: Displaying all VC Ethernet modules

->show interconnect type=VC-ENET

Example 3: Displaying all external uplinks that have a link established

->show uplinkport status=linked

Example 4: Displaying all uplink ports with connector type of RJ-45 and speed configured to Auto

->show uplinkport type=RJ45 Speed=Auto

Example 5: Displaying all servers currently powered on

->show server power=On

Introduction 12

+ 25 hidden pages