HP Virtual Connect FlexFabric 10Gb24-port Module for c-Class BladeSystem - Manual (Page 7)

Introduction 7
Changes from VC 4.01 to VC 4.10
Command Changes Virtual Connect 4.01 Virtual Connect 4.10
add profile
set profile
Modified to include the
HideUnusedFlexNIC
s property
add profile add profile
[HideUnusedFlexNIC
s=]
add fabric
set fabric
Modified the
description of the
LinkDist properties
to remove the reference
to the HP 4Gb VC-FC
Module.
The HP 4GB VC-FC
Module, HP VC 4Gb FC
Module, HP VC 8Gb
20-Port FC Module, and
HP VC 8Gb 24-Port
Module support only
manual login
redistribution. The HP VC
FlexFabric
10Gb/24-port Module
supports both auto and
manual login
redistribution.
The HP VC 4Gb FC
Module, HP VC 8Gb
20-Port FC Module, and
HP VC 8Gb 24-Port
Module support only
manual login
redistribution. The HP VC
FlexFabric 10Gb/24-port
Module supports both
auto and manual login
redistribution.
show uplinkport The Status property
displays Non-HP
instead of
Uncertified.
show uplinkport
The Status property
previously displayed
Uncertified.
show uplinkport
The Status property
displays Non-HP.
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
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, 2013