How it Works
Hp
Loading...
V
Loading...
Loading...
Virtual Connect Manager
Version 1.24 Release Notes and Compatibility Matrix
15 pgs1.05 Mb0
Table of contents
Loading...

Hp Virtual Connect Manager Command Line Interface Version 1.31 User Guide

HP Virtual Connect Manager Command Line
J
Interface Version 1.31 User Guide
Part Number 449298-002a
© Copyright 2007, 2008 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 and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Intended audience
This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

Contents

Introduction.................................................................................................................................. 5
Virtual Connect overview............................................................................................................................ 5
Command line overview............................................................................................................................. 5
Command line syntax ................................................................................................................................6
Parameters .....................................................................................................................................6
Options.......................................................................................................................................... 6
Properties .......................................................................................................................................7
Command batching ......................................................................................................................... 7
Supporting comments and blank lines in CLI scripts..............................................................................7
Unassigning multiple profiles............................................................................................................. 9
CLI command execution modes ................................................................................................................... 9
Remote access to the Virtual Connect Manager...........................................................................................10
Command output filtering ......................................................................................................................... 10
Command line............................................................................................................................ 12
Subcommands ........................................................................................................................................12
Managed elements.................................................................................................................................. 12
all ............................................................................................................................................... 13
devicebay ....................................................................................................................................14
domain ........................................................................................................................................ 14
enclosure...................................................................................................................................... 17
enet-connection ............................................................................................................................. 18
enet-vlan ...................................................................................................................................... 20
external-manager .......................................................................................................................... 21
fabric........................................................................................................................................... 22
fc-connection................................................................................................................................. 24
firmware ...................................................................................................................................... 26
igmp............................................................................................................................................ 27
interconnect..................................................................................................................................28
ldap ............................................................................................................................................ 29
ldap-certificate ..............................................................................................................................30
ldap-group.................................................................................................................................... 31
mac-cache.................................................................................................................................... 32
network........................................................................................................................................ 33
port-monitor .................................................................................................................................. 36
profile.......................................................................................................................................... 38
server .......................................................................................................................................... 40
serverid........................................................................................................................................ 43
server-port-map ............................................................................................................................. 44
snmp ........................................................................................................................................... 46
snmp-trap ..................................................................................................................................... 47
ssh............................................................................................................................................... 49
ssl-certificate .................................................................................................................................50
ssl-csr........................................................................................................................................... 50
ssl ............................................................................................................................................... 51
stackinglink................................................................................................................................... 52
Contents 3
status ........................................................................................................................................... 52
support-info................................................................................................................................... 52
systemlog ..................................................................................................................................... 52
uplinkport..................................................................................................................................... 53
uplinkset....................................................................................................................................... 55
user ............................................................................................................................................. 57
user-security.................................................................................................................................. 59
vcm .............................................................................................................................................60
version......................................................................................................................................... 60
Help subsystem ....................................................................................................................................... 60
Output format ......................................................................................................................................... 62
Interactive user output format .......................................................................................................... 62
Scriptable output format .................................................................................................................64
Configuring the Virtual Connect domain using the CLI..................................................................... 66
Basic configuration.................................................................................................................................. 66
Logging in to the CLI......................................................................................................................66
Domain setup................................................................................................................................ 67
Network setup............................................................................................................................... 69
Fibre Channel setup....................................................................................................................... 72
Server Profile setup ........................................................................................................................ 73
Logging out of the CLI .................................................................................................................... 76
Common management operations ............................................................................................................. 76
Resetting the Virtual Connect Manager....................................................................................................... 77
Technical support........................................................................................................................ 79
Before you contact HP.............................................................................................................................. 79
HP contact information............................................................................................................................. 79
Acronyms and abbreviations........................................................................................................ 80
Index......................................................................................................................................... 82
Contents 4

Introduction

Virtual Connect overview

Virtual Connect is a set of interconnect modules and embedded software for HP BladeSystem c-Class enclosures that simplifies the setup and administration of server connections. HP Virtual Connect includes the HP 1/10Gb Virtual Connect Ethernet Module for c-Class BladeSystem, the HP 4Gb Virtual Connect Fibre Channel Module for c-Class BladeSystem, and the HP Virtual Connect Manager.
Virtual Connect implements server edge virtualization so that server administrators can upgrade, replace, or move server blades within their enclosures without changes being visible to the external LAN and SAN environments.
The Virtual Connect Manager is embedded on the HP 1/10Gb Virtual Connect Ethernet Module for c­Class BladeSystem and is accessed by users through web links provided by the Onboard Administrator or through direct connection to the embedded web server.
The HP 1/10Gb VC-Enet Module supports the HP BladeSystem c7000 Enclosure, HP BladeSystem c3000 Enclosure, and all the server blades and networks contained within the enclosure and enables connection to all brands of data center Ethernet switches.
The HP 4Gb VC-FC Module enables connection of the enclosure to Brocade, Cisco, McData, or Qlogic data center Fibre Channel switches, but does not appear as a switch to the Fibre Channel fabric.
A Virtual Connect domain currently includes a single HP c-Class BladeSystem enclosure for a total of 16 servers. Within the domain, any server blade can access any LAN or SAN connected to a VC module, and a server blade can be used as a spare for any server blade within the same enclosure.
By stacking (cabling) the Ethernet modules within the domain, every server blade in the domain can be configured to access any external network connection. Fibre Channel modules within different I/O bays are each connected directly to the same set of FC SAN(s). With this configuration, the Virtual Connect Manager can deploy and migrate a server blade profile to any server in the Virtual Connect domain without the need to change external LAN or SAN configurations.

Command line overview

The CLI can be used as an alternative method for managing the Virtual Connect Manager. Using the CLI can be useful in the following scenarios:
• HP Management Applications (for example: Systems Insight Manager or Insight Control tools) can
query the Virtual Connect Manager for information these tools need to present a complete management view of HP BladeSystem enclosures and the devices contained within. This interface is also used by the Management tools to execute provisioning and configuration tasks to devices within the enclosure.
• Users can develop tools that utilize Virtual Connect Manager functions for data collection and for
executing provisioning and configuration tasks.
Introduction 5
• When no browser is available or you prefer to use a command line interface, you can access
management data and perform configuration tasks.

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 Operation performed on a managed element managed element Management entity being operated on parameters Command extensions for a particular management operation options Attributes used to customize or control command execution behavior such as output
format, quiet-mode, and others
properties One or more name or value pairs that are accessories to the command operation,
Example: ->add user mark password=asdf89g fullname="Mark Smith" enabled=true
mainly for set and add operations
In the above 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) are required to 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, and more than one property is separated by a space.

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, 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.
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 for suppressing interactive prompts that would normally require input from the user.
Options are distinguished from other command line elements by using a hyphen (-) in front of the option. Option arguments are required or optional depending on the option being specified. For example, the -
Introduction 6
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:
-<option>[=argument1>,<argument2>, . . .]
Example: ->show user suzi -output=script1 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

In previous versions of the CLI, the user had the following options to enable different CLI command invocations:
• Interactively input commands at the shell after logging in via SSH. This method works well for
interactive users, but not necessarily for automation. Although users could write expect scripts for command processing, the solution is not optimal.
• Enter remote shell script commands, one-at-a-time, using a remote SSH client. This method enhances
automation, but performance is lessened because each command requires logging in and logging out of the remote SSH server in the firmware. Because the authentication and command processing is performed over an encrypted channel, users experience a performance hit. If the user script is performing many operations in the client script, the time necessary to perform the tasks increases.
The updated version of the CLI supports a new enhancement that enables users to enter multiple CLI commands in a single command-line invocation. This capability is useful in situations where users prefer to batch several commands together and execute them in a particular sequence, within the context of the same user login SSH session. This method improves the overall performance of lengthy script processing.
Example 1: Sample commands with no command batching
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

Scripts are useful for batching many CLI commands. Administrators can create a single CLI script to configure an entire VC domain from scratch and use it on multiple enclosures.
Introduction 7
The updated version of the CLI supports command scripts that contain blank lines and comments. In previous firmware versions, all commands that were provided as input to the CLI through scripts could only be valid commands. Supporting comments and blank lines enables users to maintain descriptive comments and notes in the configuration script more easily.
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 allow script automation and better security, SSH public/private key-pairs can be generated and uploaded to the public key to the VC firmware.
>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.
>plink Admin@192.168.0.120 -m myscript.txt The following sample script illustrates a CLI script that contains this type of formatting. Note that all
comment lines must begin with "#".
#-----------------------------------------------------------------------­# This is my sample Virtual Connect Domain Configuration Script # Revision 1.0.1.2 # February 15, 2008 #------------------------------------------------------------------------
# Add Some 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 Some Profiles with Default VC-Enet and VC-FC Connections add profile MyProfile add profile AnotherProfile add profile Profile45
# Add a few VC-Enet Networks add network MyNetwork add network Network2
# Add a few uplink ports to the networks add uplinkport enc0:1:1 network=MyNetwork add uplinkport enc0:1:2 network=Network2
Introduction 8
# Create a Shared Uplink Port Set add uplinkset SharedSet1
# Assign a profile to a device bay assign profile MyProfile enc0:1
# Done!!!

Unassigning multiple profiles

In previous firmware releases, if the user needed to unassign multiple profiles from several device bays, the unassign profile <profileName> command could be used at the command line. When many profiles need to be unassigned, sending a command for each server profile to be unassigned can be tedious.
To simplify this scenario, the remove profile command has been extended to include unassigning 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 displays for that server/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 using the dedicated management shell. The shell is
provided after the user logs in with valid credentials, and only accepts known VCM CLI commands as input. Users can quit the shell by using the exit command. An example of logging into the interactive management shell is provided below. In the example, the primary VCM is located at IP address
192.168.0.120.
>ssh 192.168.0.120
login as: michael password: ***********
-------------------------------------------------------------------­HP Virtual Connect Management CLI v1.31
Introduction 9
(C) Copyright 2006-2007 Hewlett-Packard Development Company, L.P. All Rights Reserved
--------------------------------------------------------------------
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 In some cases, users 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. An example of how to use the non-interactive mode for CLI command execution is provided below. In the example, the primary VCM is located at IP address 192.168.0.120.
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.
->ssh Administrator@192.160.0.120 show enclosure <command output displayed to console>

Remote access to the Virtual Connect Manager

The Virtual Connect Manager CLI can be accessed remotely through any SSH session:
1. Start an SSH session to the Virtual Connect Manager using any SSH client application.
2. When prompted, type the assigned IP address or DNS name of the Virtual Connect Manager, and
then press Enter.
3. Type a valid user name, and then press Enter.
4. Type a valid password, and then press Enter. The CLI command prompt displays.
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.

Command output filtering

The CLI provides output filtering capabilities that enable users 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 examples below illustrate some common usage scenarios for output filtering. Example 1: Displaying all enabled users
Introduction 10
->show user enabled=true Example 2: Displaying on VC Ethernet Interconnect Modules
->show interconnect type=VC-ENET Example 3: Displaying all external uplink 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 11

Command line

Subcommands

Command Description
add assign delete exit help import load poweroff poweron reboot remove reset save set show unassign update
Add a new object to the domain or to another object Assign a server profile to a device bay Delete the domain configuration Exit the Virtual Connect Manager command-line shell Display context-sensitive help for a command or object Import an enclosure into the domain Transfer a file from a remote location to the domain Power off one or more servers Power on one or more servers Reboot one or more servers Remove or delete an existing object (for example, users or profiles) Perform a reset operation on an object (for example, vcm) Transfer a file from the domain to a remote location Modify one or more configuration properties of an object Display properties or information about an object Unassign a server profile from a device bay Update firmware on one or more interconnect modules

Managed elements

Managed element Description
all (on page 13) devicebay (on page 14)
domain (on page 14)
enclosure (on page 17) enet-connection (on page 18)
enet-vlan (on page 20) external-manager (on page 21)
fabric (on page 22) fc-connection (on page 24)
Display all VC domain managed elements Display enclosure device bay information Manage general virtual connection domain settings and
information Manage general enclosure settings and information Manage Ethernet network connections Manage Ethernet VLAN connections Manage external manager settings and information Manage Fibre Channel SAN fabrics Manage Fibre Channel SAN fabric connections
Command line 12
Managed element Description
firmware (on page 26) igmp (on page 27) interconnect (on page 28) ldap (on page 29)
ldap-certificate (on page 30) ldap-group (on page 31)
mac-cache (on page 32) network (on page 33)
port-monitor (on page 36) profile (on page 38)
server (on page 40) serverid (on page 43)
server-port-map (on page 44) snmp (on page 46) snmp-trap (on page 47) ssh (on page 49) ssl-certificate (on page 50) ssl-csr (on page 50)
ssl (on page 51) stackinglink (on page 52) status (on page 52)
support-info (on page 52) systemlog (on page 52)
uplinkport (on page 53) uplinkset (on page 55) user (on page 57)
Manage interconnect module firmware Manage ethernet IGMP Snooping settings Manage I/O interconnect modules Manage LDAP configuration settings Manage LDAP certificate information Manage LDAP group configuration settings Manage Ethernet MAC cache failover settings Manage Virtual Connect ethernet networks Monitor port monitor configurations Manage virtual connect server profiles Manage physical HP BladeSystem servers Manage virtual server ID configuration settings Manage shared server downlink port mapping configuration Modify SNMP configurations Modify SNMP-trap configurations Display SSL configuration and information Manage SSL certificate information Manage an SSL certificate signing request Manage weak SSL encryption Display stacking link information and status Display overall virtual connect domain status information Manage virtual connect support information Display virtual connect manager system event log Manage interconnect module uplink ports Manage shared uplink port sets Manage local virtual connect user configurations
all
user-security (on page 59) vcm (on page 60)
version (on page 60)
Manage user security settings Manage the virtual connect domain manager Display CLI version information
The following sections provide detailed information on how the subcommands are used with each managed element.
To display command help, type a command followed by ? or -help. For additional information on the help subcommand, see "Help subsystem (on page 60)."
Manage all Virtual Connect domain elements. Supported actions: help, show
Command line 13
Item Description
show all
Syntax Examples

devicebay

Manage general enclosure device bay settings and information.
Supported actions: help, show
Item Description
show devicebay Syntax
Parameter
DeviceBayID (Optional)
Examples
Display all Virtual Connect domain configuration objects. This commands is typically useful for displaying a snapshot of the entire domain configuration with a single command.
show all [*]
->show all
Displays all configuration objects (summary view)
->show all * Displays all configuration objects (detailed view)
Display device bays of all enclosures that exist in the Virtual Connect domain.
show devicebay [<DeviceBayID>|*]
The reference ID of a device bay in the domain The format of the device bay name is <EnclosureID:DeviceBay> Example: “enc0:1” indicates device bay 1 of the local enclosure being
managed. If * is specified, then all enclosures are displayed with detailed output format.
If EnclosureID is not specified, the default enclosure is the local enclosure where the Virtual Connect manager and domain exist.
->show devicebay Displays a summary listing of all device bays
->show devicebay * Displays detailed information for all device bays
->show devicebay enc0:2 Displays detailed information for a specific device bay of a specific enclosure
->show devicebay enc1:4 Displays detailed information for a specific device bay 4 of a remote enclosure

domain

Manage general Virtual Connect domain settings and information. Supported actions: delete, help, set, show
Command line 14
Item Description
delete domain
Syntax Option
quiet
Examples
Delete the existing Virtual Connect domain configuration. Deleting the domain removes the entire Virtual Connect domain configuration
and resets it to the original defaults. After the domain has been deleted, you are logged out and the Virtual Connect Manager resets.
delete domain [-quiet]
Suppresses user confirmation prompts. This option is useful when scripting delete domain operations.
->delete domain Deletes the Virtual Connect domain configuration and prompts for user
confirmation
->delete domain -quiet Deletes the Virtual Connect domain quietly without prompting for user
confirmation (primarily used in automated scripting scenarios)
Item Description
set domain
Syntax
Properties
Name(optional)
DomainIP (optional)
IpAddress (optional)
SubnetMask (Required if IP address specified)
Gateway (Required if IP address specified)
MacType (optional)
Modify general Virtual Connect domain configuration properties, such as the domain name, domain IP address, and MAC and WWN address pool settings.
set domain [Name=<NewName>] [DomainIp=<Enabled|Disabled>] [IpAddress=<IPAddress>] [SubnetMask=<mask>] [Gateway=<Gateway>] [MacType=<VC-Defined|Factory-Default| User-Defined>] [MacPool=<1-64>] [MacStart=<address>] [MacEnd=<address>] [WwnType=<VC-Defined | Factory-Default | User-Defined>] [WwnPool=<1-64>] [WwnStart=<WWN Address>] [WwnEnd=<WWN Address>]
The new name of the domain. Valid characters include alphanumeric, "_", and ".". The maximum length of the name is 64 characters.
Enables or disables the Virtual Connect domain IP address. If enabled, then a valid IP address subnet mask must be configured. If disabled, then DHCP is used to obtain a valid IP address.
Enabling domain IP address configuration or changing the domain IP address can cause a temporary loss of connectivity to the Virtual Connect Manager. Use caution when changing these settings. Valid values include "Enabled" and "Disabled".
A valid IP address to use for the domain IP address configuration. The IP address must be in the format: xxx.xxx.xxx.xxx, where x is a number between 0 and 9. Example: 192.168.0.10
A valid subnet mask for the domain IP address configuration. The subnet mask must be in the format: xxx.xxx.xxx.xxx, where x is a number between 0 and 9. For example: 255.255.255.0
A valid gateway address for the domain IP address configuration. The gateway address must be in the format: xxx.xxx.xxx.xxx, where x is a number between 0 and 9. For example: 192.168.0.1
The type of MAC address source to use for assignment. Valid values include "VC­Defined", "Factory-Default", and "User-Defined".
Command line 15
Item Description
MacPool (optional)
MacStart (Required if IP address specified)
MacEnd (Required if IP address specified)
WwnType(optional)
WwnPool(optional)
WwnStart (Required if IP address specified)
WwnEnd (Required if IP address specified)
Examples
The pre-defined MAC pool to use for address assignment. Valid values include integers 1-64. This property is only valid if the MacType is set to "VC-Defined". If not specified, the default pool ID is 1.
The starting MAC address in a custom user-defined range. This property is only valid if the MacType is set to "User-Defined".
The ending MAC address in a custom user-defined range. This property is only valid if the MacType is set to "User-Defined".
The type of WWN address source to use for assignment. Valid values include "VC-Defined", "User Defined", and "Factory-Default".
The pre-defined WWN pool to use for address assignment. Valid values include integers 1-64. This property is only valid if the WwnType is set to "VC-Defined". If not specified, the default pool ID is 1.
The starting WWN address in a custom user-defined range. This property is only valid if the WwnType is set to "User-Defined".
The ending WWN address in a custom user-defined range. This property is only valid if the WwnType is set to "User-Defined".
->set domain Name=MyNewDomainName Changes the name of the Virtual Connect domain
->set domain DomainIp=Enabled
Enables the domain IP address
->set domain DomainIp=Enabled IpAddress=192.168.0.120 SubnetMask=255.255.255.0 Gateway=192.168.0.1
Configures the domain IP address and enables it
->set domain DomainIp=Disabled Disables the domain IP address and uses DHCP instead
->set domain MacType=VC-Defined MacPool=10 Sets the MAC address source to VC-Defined with a pre-defined range
->set domain MacType=Factory-Default Sets the MAC address source to use factory default MAC addresses
->set domain MacType=User-Defined MacStart=00-17-A4-77-00­00 MacEnd=00-17-A4-77-00-FF
Sets the MAC address source to a custom, user-defined address range
->set domain WwnType=VC-Defined WwnPool=5 Sets the WWN address source to VC-Defined with a pre-defined range
->set domain WwnType=Factory-Default Sets the WWN address source to use factory default WWN addresses
->set domain WwnType=User-Defined WwnStart=50:06:0B:00:00:C2:62:00 WwnEnd=50:06:0B:00:00:C2:62:FF
Sets the WWN address source to a custom, user-defined address range
Command line 16
Item Description
show domain
Syntax Parameter
addressPool (Optional)
Examples

enclosure

Manage general enclosure settings and information.
Displays general Virtual Connect domain information, including the Virtual Connect domain name, the VCM domain IP address settings, and MAC/WWN address settings for the domain.
show domain [addressPool]
Displays all the VC-defined address pool range available for use
->show domain Displays domain information
->show domain addressPool Displays the VC-defined address pools for the domain
Supported actions: help, import, remove, show
Item Description
import enclosure
Syntax
Parameter
IpAddress (Required for remote enclosures)
Properties
UserName (Required) Password (Required)
DoubleDense (Optional)
Examples
Import local and remote enclosures into the Virtual Connect domain.
import enclosure [<IpAddress>] UserName=<username> Password=<password> [DoubleDense=<True|False>]
The password field is optional on the command line. If not specified on the command line, the user is prompted for the same interactively.
The IP address of the remote enclosure to be imported. This property is required when importing a remote enclosure into the domain. If the IP address is not given, then the local enclosure is assumed.
A valid username of the Onboard Administrator user A valid password of the Onboard Administrator user to be used for importing
the enclosure. If no password is given at the command-line, the password is prompted for interactively during the import operation.
If the enclosure being imported supports double-density servers, then this property enables the device bay display format to support a display for double-dense servers. The default behavior is display for single-dense servers in the enclosure.
->import enclosure UserName=Administrator Password=fgg7h*1
Imports the local enclosure
->import enclosure 192.168.0.11 username=Administrator password=myOaPassword
Imports a remote enclosure
Command line 17
Item Description
->import enclosure UserName=Administrator Password=fgg7h*1 DoubleDense=true
Imports the local enclosure with double-dense device bay display format
Item Description
remove enclosure
Remove a remote enclosure that has been imported into the domain. The local enclosure is not allowed to be removed from the domain using the remove enclosure command.
Syntax
remove enclosure <EnclosureID | *>
Parameter
EnclosureID (Required)
The enclosure ID of the remote enclosure to be removed from the domain, where "*" removes all the remote enclosures that exist in the domain. The enclosure IDs can be identified for a particular enclosure by using the show enclosure command. The local enclosure cannot be removed from the domain with this command.
Examples
->remove enclosure encl Removes a remote enclosure
->remove enclosure * Removes all remote enclosures from the domain
Item Description
show enclosure
Syntax Parameter
EnclosureID (optional)
Examples
Display all enclosures in the domain. show enclosure [<EnclosureID>|*]
The ID of an enclosure in the domain. If specified, then only details for the specified enclosure are displayed.
->show enclosure Displays a summary listing of all enclosures
->show enclosure * Displays detailed information for all enclosures
->show enclosure enc0 Displays detailed information for a specific enclosure
->show enclosure encl Displays detailed information for a single enclosure

enet-connection

Manage Ethernet network connections.
Supported actions: add, help, remove, set
Item Description
add enet-connection
Add a new Ethernet network connection to an existing server profile.
Command line 18
Item Description
Syntax
Parameter
ProfileName (required)
Properties
Networkn (optional)
PXE (optional)
AddressType (optional)
EthernetMAC (required if AddressType is User­Defined)
iScsiMAC (required if AddressType is User­Defined)
Examples
add enet-connection <ProfileName> [Network=<NetworkName>] [PXE=<enabled|disabled|UseBios>] [AddressType=Factory-Default|User-Defined>] [EthernetMAC=<MAC Address> iScsiMAC=<MAC Address>]
The name of an existing profile to which the new connection is added.
The name of an existing network to associate with the connection. If the network name is not specified, or is set to "unassigned," then the network remains unassigned. (optional)
Enables or disabled PXE on the network connection. Valid values are "enabled", "disabled", and "UseBios". If this value is not specified, the default is "UseBios."
Only one connection can have PXE enabled per profile. The source of MAC address assignments to be used during the creation
of the new connection. If not specified, the default is the domain default. If "User-Defined" is specified, then both an Ethernet MAC Address and iSCSI MAC Address must also be specified. Valid values include "Factory-Default" and "User-Defined".
The user-defined Ethernet MAC address to use for the connection. This property is required if the AddressType specified is "User-Defined."
The user-defined iSCSI MAC address to use for the connection. This property is required if the AddressType specified is "User-Defined."
->add enet-connection MyNewProfile Network=SomeNetwork
Adds a new Ethernet network connection to a profile
->add enet-connection MyNewProfile Network=SomeNetwork2 PXE=enabled
Adds a new Ethernet network connection and enables PXE
->add enet-connection MyNewProfile Adds a new Ethernet network connection and leaves the network
unassigned
->add enet-connection MyNewProfile AddressType=Factory-Default
Adds a new Ethernet network connection and uses factory default addresses
->add enet-connection MyNewProfile AddressType=User­Defined EthernetMAC=00-17-A4-77-00-00 iScsiMAC=00­17-A4-77-00-01
Adds a new Ethernet network connection and provides user-defined MAC addresses
Item Description
remove enet-connection
Remove the last Ethernet network connection from an existing server profile.
Command line 19
Item Description
Syntax
remove enet-connection <ProfileName>
Parameter
ProfileName (required)
The name of the profile from which to remove the ethernet connection.
Example
->remove enet-connection MyProfile Removes an ethernet network connection from a profile.
Item Description
set enet-connection
Syntax
Parameters
ProfileName (required) Port (required)
Properties
NetworkName
PXE
Examples
Modify an ethernet connection of a server profile.
set enet-connection <ProfileName> <Port> [Network=<NetworkName>] [PXE=<enabled|disabled|UseBios>]
The name of the server profile that contains the connection to modify The port number of the connection being modified
The name of the Ethernet network to associate with the connection. Applies to Ethernet network connections only. A blank string will make the ethernet connection unassigned.
Enables or disables PXE on a connection. Valid values are "enabled", "disabled", and "UseBios". Applies to Ethernet network connections only.
PXE can be enabled on one connection per profile.
->set enet-connection MyProfile 2 NetworkName=NewNetworkName
Changes the network of an Ethernet connection
->set enet-connection RedProfile 1 NetworkName="" Sets a network connection to "unassigned"
->set enet-connection GreenProfile 3 PXE=disabled Disables PXE on an Ethernet connection

enet-vlan

Manage Ethernet VLAN connections.
Supported actions: help, set, show
Item Description
set enet-vlan
Syntax
Properties
Modifiy general Ethernet VLAN configuration settings.
set enet-vlan VLanTagControl=<Tunnel|Map> [SharedServerVLanId=<true|false>]
Command line 20
Item Description
VLanTagControl (optional)
Determines how Ethernet packet VLAN tags are handled by the domain. Valid values include: "Tunnel" and "Map".
The "tunnel" option results in VLAN tagging to be supported only on networks with dedicated uplinks. Also, Ethernet ports connected to networks using shared uplink sets can only transmit and receive untagged frames.
The "map" option results in being able to add more than one network to a single Ethernet port for the server profiles and also being able to specify VLAN mapping between server tags and VC networks. Also, Ethernet networks with dedicated uplinks can only transmit and receive untagged frames.
SharedServerVLanId (optional)
Enables or disables the option to force server ports connected to multiple VC Ethernet networks to use the same VLAN mappings as those used by corresponding shared uplink sets. Valid values include: "true" and "false".
Setting the value to "true" restricts the server network connections to be selected from a single shared uplink, and the VLAN ID cannot be modified.
Setting the value to "false" allows the user to select any VC Ethernet network for the server Ethernet connections, and VLAN ID mappings can be modified to ensure uniqueness.
SharedServerVLanId can be "true" only if VLanTagControl is set to "Map".
Example
->set enet-vlan VLanTagControl=Map SharedServerVLanId=true
Sets the VLanTagControl to Map and SharedServerVLanId
Item Description
show enet-vlan
Syntax Example

external-manager

Manage external manager settings and information.
Supported actions: delete, help, set, show
Item Description
show external­manager
Syntax Example
Item Description
remove external­manager
Display general Ethernet VLAN configuration settings.
show enet-vlan
->show enet-vlan
Displays Ethernet VLAN configuration settings
Display the information of an existing external manager.
show external-manager
->show external-manager
Displays the information of an existing external manager
Remove an existing external manager (VCEM) and regain local management control of the domain.
Command line 21
Item Description
Syntax Property
UserName (required)
Example
remove external-manager UserName=<username>
A valid external manager user name. The username can be identified using the "show external-manager" command.
->remove external-manager UserName=A17005068 Removes external management control of the VC Manager
Item Description
set external­manager
Syntax
Properties
UserName (required)
Enabled (required)
Examples
Enable or disable an existing external manager’s control of the Virtual Connect domain.
set external-manager UserName=<username> Enabled=<true|false>
A valid external manager username. The username can be identified using the show external-manager command.
Enables or disables the external manager. Valid values include "true" and "false"
->set external-manager UserName=A17005068 Enabled=false Disables the external manager
->set external-manager UserName=A17005068 Enabled=true Enables the external manager

fabric

Manage Fibre Channel SAN fabrics.
Support actions: add, help, remove, set, show
Item Description
add fabric
Syntax
Parameter
Name (required)
Properties
Bay (required) Ports (required)
Speed (optional)
Login (optional)
Add a new VC Fibre Channel SAN Fabric to the domain.
add fabric <Name> Bay=<BayNum> Ports=<PortList> [Speed=<Auto|1Gb|2Gb|4Gb>] [Login=<Static|Dynamic>]
A unique name for the new VC-FC Fabric to be added to the domain
The specific interconnect bay number with which the fabric is associated A list of one or more logical FC ports to be added to the fabric. Each port is
specified in the format "<port1>,<port2>,...", where port is the interconnect module port number to be added to the fabric (affects all modules within a bay group). Example: "1,2,3,4".
The port speed for the uplink ports in the fabric. Valid values include: "Auto", "1Gb", "2Gb", and "4Gb". The default port speed is "Auto".
Specifies the login distribution scheme to use for load balancing. Valid values include: "Static" and "Dynamic". The default login distribution is "Static".
Command line 22
Item Description
Examples
->add fabric MyFabric1 Bay=3 Ports=1,2 Adds a new fabric, using default values
->add fabric MyFabric2 Bay=3 Ports=1 Speed=2Gb Adds a new fabric with speed set to 2Gb
->add fabric MyFabric3 Bay=3 Ports=1,2,3,4 Login=Dynamic Adds a new fabric with dynamic login distribution
->add fabric MyFabric4 Bay=3 Ports=1,2 Adds a new fabric with two logical ports
Item Description
remove fabric
Syntax
Remove an existing VC FC SAN fabric from the domain. remove fabric <Name | *>
Parameter Name (required)
The name of an existing fabric or "*" to be removed
Examples
->remove fabric VFabric_1 Removes VC FC SAN fabric VFabric_1
->remove fabric * Removes all VC FC fabrics from the domain
Item Description
set fabric
Syntax
Parameter
FabricName (required)
Option
loadBalance
Properties
Name (optional) Speed (optional)
Login (optional)
Ports (optional)
Examples
Modify an existing FC SAN fabric.
set fabric <Name> [-loadBalance] [Name=<NewName>] [Speed=<Auto|1Gb|2Gb|4Gb>] [Login=<Static|Dynamic>] [Ports=<PortList>]
The name of an existing FC SAN fabric to modify (required)
Perform load balancing on a fabric configured for dynamic login distribution
The new name of the fabric The port speed for the uplink ports in the fabric Valid values include: “Auto”, “1Gb”,
“2Gb”, and “4Gb”. The default port speed is “Auto”. Specifies the login distribution scheme to use for load balancing. Valid values
include: "Static" and "Dynamic". The default login distribution is "Static". A list of one or more logical FC ports associated with the fabric. Each port is
specified in the format "<port1>,<port2>,...", where port is the interconnect module port to be modified in the fabric (affects all modules within a bay group). A blank string removes all the ports that are assigned to the fabric.
Command line 23
Item Description
->set fabric MyFabric1 Name=MyNewName1 Changes the name of an existing fabric
->set fabric MyFabric2 Speed=2Gb Login=Dynamic Modifies the port speed and login distribution
->set fabric MyFabric3 Ports=1,2,3,4 Modifies the fabric ports contained in the fabric
->set fabric MyFabric4 ports=”” Removes the fabric ports assigned to the fabric
->set fabric MyFabric5 -loadBalance Performs load balancing on a fabric with dynamic login distribution
Item Description
show fabric Syntax
Parameter
FabricName (optional)
Examples
Display all FC SAN fabrics. show fabric [<FabricName> | *]
Name of an existing FC SAN fabric. “*” displays detailed output of all the fabrics in the VC domain. If not specified, summary output of all fabrics is displayed.
->show fabric Displays a summary listing of all FC SAN fabrics
->show fabric * Displays detailed information for all FC SAN fabrics
->show fabric SAN_5 Displays detailed information for a specific FC SAN fabric

fc-connection

Add a new Fibre Channel SAN connection to a server profile.
Supported actions: add, help, set
Item Description
add fc-connection
Syntax
Parameter
ProfileName (required)
Properties
Fabric (optional)
Add a new FC SAN connection to an existing server profile.
add fc-connection <ProfileName> [Fabric=<FabricName>] [Speed=<Auto|1Gb|2Gb|4Gb|Disabled>] [AddressType=Factory-Default|User-Defined] [PortWWN=<WWN address>] [NodeWWN=<WWN address>]
The name of an existing profile to which the new connection is added. (required)
The name of an existing fabric to associate with the connection. If the fabric name is not specified, then the connection will be marked as “Unassigned” but associated with a specific bay.
Command line 24
Item Description
Speed (optional)
AddressType (optional)
PortWWN (required if AddressType is User­Defined)
NodeWWN (required if AddressType is User­Defined)
Examples
The port speed of the connection port. Valid values include "Auto", "1Gb", "2Gb", "4Gb", and "Disabled". If not specified, then the default port speed is set to "Auto".
The source of WWN address assignments to be used during the creation of the new connection. If not specified, the default is the domain default. If "UserDefined" is specified, then both a Port WWN and Node WWN must also be specified. Valid values include "Factory-Default" and "User-Defined".
The user-defined Port WWN address to use for the connection. This property is required if the AddressType specified is "User-Defined". PortWWN must be an unused WWN address.
The user-defined Node WWN address to use for the connection. This property is required if the AddressType specified is "User-Defined". The NodetWWN must be an unused WWN address.
->add fc-connection MyNewProfile Fabric=SAN_5 Adds a new FC SAN fabric connection to a profile
->add fc-connection MyNewProfile Fabric=SomeFabric Speed=4Gb
Adds a new FC SAN connection and configures the port speed
->add fc-connection MyNewProfile Adds a new FC SAN connection and uses the next available fabric
->add fc-connection MyNewProfile AddressType=Factory­Default
Adds a new FC SAN connection and uses factory-default addresses
->add fc-connection MyNewProfile AddressType=User­Defined PortWWN=50:06:0B:00:00:C2:62:00 NodeWWN=50:06:0B:00:00:c2:62:00
Adds a new FC SAN connection and provides user-defined WWN addresses
Item Description
remove fc-connection
Syntax
Remove the last FC connection from an existing server profile. remove fc-connection <ProfileName>
Parameter ProfileName (required)
The name of an existing profile from which the last FC connection to be removed.
Example
->remove fc-connection MyProfile Removes an FC-connection from a profile
Item Description
set fc-connection
Syntax
Modify an existing server profile connection.
set fc-connection <ProfileName> <Port> [Fabric=<FabricName>] [Speed=<Auto|1Gb|2Gb|4Gb|Disabled>] [BootPriority=<priority>] [BootPort=<portName>] [BootLun=<LUN>]
Command line 25
Loading...
+ 58 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use