HPE BladeSystem c-Class Virtual
Connect Support
User Guide
Abstract
This document provides user information for the HPE BladeSystem c-Class Virtual Connect Support Utility Version 1.11.0/1.11.1, which
remotely upgrades the VC-Enet and VC-FC module firmware in HPE BladeSystem c-Class c3000 and c7000 Enclosures. This document is
for the person who installs, administers, and troubleshoots servers and storage systems. Hewlett Packard Enterprise assumes you are
qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
Part Number: 805652-002R
November 2015
Edition: 2
© Copyright 2015 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not
responsible for information outside HPE.com.
Confidential computer software. Valid license from Hewlett Packard Enterprise 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 Server® are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Contents
Introduction ............................................................................................................................................ 4
Overview ..................................................................................................................................................................4
Using HP-UX ............................................................................................................................................................4
Requirements ...........................................................................................................................................................4
Restrictions and limitations.......................................................................................................................................6
Supported modules ..................................................................................................................................................6
Command line syntax ...............................................................................................................................................7
Installation ............................................................................................................................................. 8
Installation and usage ..............................................................................................................................................8
Password masking ........................................................................................................................................9
Interactive mode ............................................................................................................................................9
Commands .......................................................................................................................................... 11
collect .....................................................................................................................................................................11
discover ..................................................................................................................................................................11
configbackup ..........................................................................................................................................................12
healthcheck ............................................................................................................................................................12
packageinfo ............................................................................................................................................................13
report ......................................................................................................................................................................14
resetvcm .................................................................................................................................................................15
supportdump ..........................................................................................................................................................15
update ....................................................................................................................................................................16
version ....................................................................................................................................................................17
Downgrades ........................................................................................................................................ 19
Overview ................................................................................................................................................................19
Restrictions.............................................................................................................................................................19
Manual activation ................................................................................................................................. 20
Manual activation of VC firmware ...........................................................................................................................20
Troubleshooting ................................................................................................................................... 21
VCSU error codes ..................................................................................................................................................21
Support and other resources................................................................................................................ 29
Accessing Hewlett Packard Enterprise Support .....................................................................................................29
Information to collect ...................................................................................................................................29
Accessing updates .................................................................................................................................................29
Websites.................................................................................................................................................................29
Customer Self Repair .............................................................................................................................................30
Remote support ......................................................................................................................................................37
Acronyms and abbreviations ................................................................................................................ 38
Documentation feedback ..................................................................................................................... 39
Index.................................................................................................................................................... 40
Contents
3
Introduction
Overview
The HPE BladeSystem c-Class Virtual Connect Support Utility enables administrators to upgrade
VC-Enet and VC-FC firmware, and to perform other maintenance tasks remotely on both BladeSystem
c-Class c7000 and c3000 Enclosures using a standalone command line utility.
When the utility initiates a firmware upgrade process, VCSU performs an automatic health check, and
then all modules are updated at the same time. The utility displays a message indicating that an update is
in progress and the percentage completed. After the module firmware updates are complete, the utility
activates all of the modules.
You can use the -f health parameter of the update command to force an update, even if the health of
a module is not in a good state.
Using HP-UX
When using HP-UX, use the swinstall command to install the utility.
Example command line:
swinstall -s /tmp/download vcsu
where "/tmp/download" is the local directory that contains the downloaded "vcsu.depot".
Requirements
•
A supported operating system must be installed on the client:
o
Microsoft Windows Server 2008 R2/2012
o
Microsoft Windows 7
o
Linux (RHEL 5.8, RHEL 5.9, RHEL 6.3, RHEL 6.4, SLES 11 SP2)
o
HP-UX 11.23 and 11.31
•
To run VCSU, the minimum required, available free disk space is 600 MB per installation instance.
For example, if you run VCSU three times in parallel against three different enclosures, you must
have approximately 1.8 GB of available disk space.
•
With VC version 4.01 and higher, a user must have the Export Support Files, Firmware Update
(VCSU), and Save Domain Configuration role operations enabled to perform a firmware update.
If the domain is managed by VCEM, configurable role operations must be delegated to one of the
following roles if they are to be performed while the domain is in Maintenance Mode: Network,
Storage or Domain. Administrators logging into VCM with a Server role account while the domain is
in Maintenance mode will be denied access to perform delegated operations such as exporting
support files, updating firmware, configuring port monitoring, or saving or restoring domain
configuration.
•
A valid HPEVirtual Connect firmware package must be available to install. To download the VC
firmware and the VCSU utility, go to the Hewlett Packard Enterprise website
(http://www.hpe.com/support/vc). Select the appropriate VC module, select Get drivers, software &
firmware, and then select the appropriate operating system. VCSU is listed in the "Utility - Tools"
category.
Introduction
4
•
Do not close the console application when a firmware update is in progress. If the application is
closed before the update completes, the module firmware might not update correctly, causing the
module firmware to be inoperative.
•
An Onboard Administrator user account with Administrative privileges and access to all Onboard
Administrators and interconnect bays must be available for use. If the enclosure is imported into a
Virtual Connect domain, a Virtual Connect user account with Domain privileges is also required. For
Virtual Connect version 4.01 and higher, a user account with Firmware Update (VCSU), Export
Support Files, and Save Domain Configuration role operations assigned to their role permissions is
required.
•
Ethernet network connectivity between the client system and the enclosure Onboard Administrator is
required. To validate this connectivity, open a web browser to the enclosure Onboard Administrator
before running the utility.
•
Ethernet network connectivity is required between the client system hosting VCSU and the VC
interconnect modules in the enclosure.
•
For VC 4.01 and lower, add the Virtual Connect Support Utility application to the list of exceptions for
any host-based firewall on the client if you do not have a healthy Backup VC module.
•
For VC 4.01 and lower, if you do not have a healthy Backup VC module, no firewalls can exist
between the client system and the remote enclosure Onboard Administrator. If a firewall exists, and
it is blocking ports, then the utility cannot open a connection with the remote modules to perform the
update.
•
Onboard Administrator firmware version 1.30 or higher is required for correct VCSU operation.
Onboard Administrator firmware version 4.00 or higher is required to use IPv6.
•
Only one instance of the VCSU accessing a single enclosure can be run on a single client at one
time. Using multiple clients to interface remotely with the same enclosure can interrupt the firmware
update process and prevent it from completing successfully.
•
During firmware update operations, the VC modules are unavailable for use. Attempting to reset or
remove the modules during the update process can result in a corrupted firmware image. Do not
reset or update the firmware for the Onboard Administrator of the target enclosure while VC modules
are being updated. These actions can interfere with the firmware update process and cause the
update to fail. During the firmware update process, LAN and SAN connectivity through the VC
modules, which might be hosted to servers in the enclosure, can be interrupted temporarily.
•
If VCSU is interrupted or loses network connectivity during the update, reset the affected module and
restart the firmware update process.
•
In a multi-enclosure environment, the Onboard Administrator user name and password must be
identical across the local and remote enclosures in the Virtual Connect domain. Otherwise, firmware
update of the remote enclosures does not succeed.
•
VCSU must be run on a management network.
•
The following libraries are required for VCSU to install on Linux 64-bit systems:
/lib/tls/libpthread.so.0
/lib/libdl.so.2
/usr/lib/libstdc++.so.6
/lib/tls/libm.so.6
/lib/libgcc_s.so.1
/lib/tls/libc.so.6
/lib/ld-linux.so.2
•
If VC is in FIPS mode, VCSU requires that the configuration password (-cp) option is specified for
the following commands:
Introduction
5
o
o
o
configbackup
supportdump
update
The length of the password must be a minimum of eight characters.
Restrictions and limitations
•
When updating from non-FIPS to FIPS mode, the DIP switch on the Primary module must be set to
FIPS mode. This action is not allowed in the case of an imported domain.
•
If the DIP switches are set to enable FIPS mode on a domain running VC firmware prior to 4.30,
update to 4.30 is blocked until the domain is deleted or the DIP switches are restored to the standard
(non-FIPS) configuration.
•
If the domain is in FIPS mode, all modules being updated must be FIPS compliant.
All modules must match the FIPS mode setting of the domain. This restriction does not apply to the
HPE 16Gb 24-Port FC module.
•
A VCSU update operation can be performed from a server blade in the same enclosure that is being
updated. However, this feature is supported only when using a redundant network configuration on
the server blade running the VCSU client.
•
This version of VCSU supports c3000 and c7000 enclosures.
•
VCSU does not update modules that are powered off, non-functional, or not physically present. A
status message indicates whether any modules are in these states.
•
VCSU does not update unknown or unsupported module types, including pass-thru Ethernet and FC
modules.
•
HTTP and HTTPS downloads are restricted to non-authenticated websites.
•
FTP downloads are restricted to non-SSL/TLS, Passive Transfer Mode FTP sites.
•
IP addresses that are not accessible time out within 20 seconds. IP addresses that have an active
SSL-enabled web server, but not an OA, fail immediately.
•
Before running VCSU, ensure that the maximum supported number of local user accounts for the
Onboard Administrator has not been reached. For multi-enclosure domains, verify this information
for each enclosure in the domain.
•
VCSU does not use any root certificates to connect to OA and VC.
•
VCSU does not support updating the firmware using IPv6 Link Local Addresses on Linux or HP-UX.
•
VCSU does not support the Windows 2008-based IIS FTP server for downloading the firmware.
Supported modules
Module
Version support
HPE 1/10Gb Virtual Connect Ethernet Module
3.62 or lower
HPE 1/10Gb-F Virtual Connect Ethernet Module
HPE Virtual Connect Flex-10 10Gb Ethernet Module
HPE Virtual Connect FlexFabric 10Gb/24-port Module
HPE Virtual Connect FlexFabric-20/40 F8 Module
HPE Virtual Connect Flex-10/10D Module
HPE 4Gb Virtual Connect Fibre Channel Module
HPE Virtual Connect 4Gb Fibre Channel Module
3.62 or lower
All versions
3.15 or higher
4.20 or higher
3.70 or higher
4.01 or lower
All versions
Introduction
6
Module
Version support
HPE Virtual Connect 8Gb 24-Port Fibre Channel
Module
2.10 or higher
HPE Virtual Connect 8Gb 20-Port Fibre Channel
Module
HPE Virtual Connect 16Gb 24-Port Fibre Channel
Module
2.10 or higher
4.40 or higher
Command line syntax
CLI input is case-insensitive except when otherwise noted. The general CLI syntax is as follows:
vcsu -a <command>
Parameters are extensions that provide extra information required for the execution of a particular
command. Whether or not a parameter is required depends on the specific action being executed.
For example, the version command includes parameters for IP address, username, and password. The
syntax is as follows:
vcsu -a version -i <IP> -u <USER> -p <PWD>
NOTE: When entering a username from a Linux command shell with the domain\username
format, use quotation marks around the username ("domain\username") so it is not
expanded by the Linux shell.
To display all modules and their current firmware version, enter the following:
vcsu -a version -i 192.168.1.100 -u Administrator -p password
Introduction
7
Installation
Installation and usage
To install and run the HPE BladeSystem c-Class Virtual Connect Support Utility:
1.
Download the utility and VC firmware from the Hewlett Packard Enterprise website
(http://www.hpe.com/support/cClass-vcsu):
a. Select your product.
b. Select Get drivers, software & firmware.
c. Select your operating system.
d. Under the download index, select the software category.
VCSU is found in the Utility - Tools category.
VC firmware is found in the Firmware - Blade Infrastructure category.
2.
Install the utility on the client system by running the MSI file.
3.
After the program is installed, click Start>Programs>Hewlett-Packard>Virtual Connect Support
Utility to start a console.
o
o
o
o
o
o
o
o
o
o
o
o
4.
To start the Virtual Connect Support Utility in interactive mode, enter vcsu.
To display the top-level help and available options, enter vcsu -a help.
To display version syntax and available options, enter vcsu -a version.
To display report syntax and available options, enter vcsu -a report.
To display update syntax and available options, enter vcsu -a update.
To display discover syntax and available options, enter vcsu -a discover.
To display collect syntax and available options, enter vcsu -a collect.
To display configbackup syntax and available options, enter vcsu -a configbackup.
To display supportdump syntax and available options, enter vcsu -a supportdump.
To display healthcheck syntax and available options, enter vcsu -a healthcheck.
To display packageinfo syntax and available options, enter vcsu -a packageinfo.
To display resetvcm syntax and available options, enter vcsu -a resetvcm.
Display all of the modules in the enclosure and ensure that connectivity exists between the utility and
the remote enclosure. Enter version.
Non-VC modules are shown as “Unknown or unsupported module.” Version information appears for
supported VC modules only.
5.
Display all modules in the target enclosure and which modules can be updated. Enter report.
The report command also displays firmware package file contents and versions. A valid firmware
package must be available on the local file system or supported remote server.
Non-VC modules are shown as “Unknown or unsupported module.” Detailed information appears for
supported VC modules only.
6.
Update the firmware on supported VC-Enet and VC-FC modules in the enclosure. Enter update.
VCSU only updates supported VC modules that are able to be updated and require an update. The
update process takes approximately 20 minutes for VC-Enet modules and 5 minutes for VC-FC
modules. These updates are performed simultaneously.
Installation 8
7.
Delete or back up the following files from the client machine after a successful firmware update:
o
Support dump taken during the update
o
Configuration backup taken during the update
Password masking
For all of the commands provided by VCSU, the user name, password, and IP address of the enclosure
OA must be provided. In some cases, the VC domain user name and password must also be specified.
VCSU enables the user to enter the password interactively with password masking, primarily for security
reasons. To do this, enter the password as *. A prompt is provided that masks the input.
Example:
vcsu -a version -i 192.168.1.100 -u Administrator -p *
OA Password
:***********
From a Linux command shell, use quotation marks around the asterisk so it is not expanded by the Linux
shell.
Example:
vcsu -a version -i 192.168.1.100 -u Administrator -p "*"
OA Password
:***********
Interactive mode
VCSU enters interactive mode when invoked without any parameters. Users are prompted to enter
missing command line parameters.
Example:
No command line parameters given. Starting interactive mode.
Please enter action ("help" for list): healthcheck
Please enter Onboard Administrator IP Address: 192.168.1.100
Please enter Onboard Administrator Username: Administrator
Please enter Onboard Administrator Password: ********
When running the Virtual Connect Support Utility in interactive mode, do not use quotation marks around
the firmware package path even if the path contains spaces. Only use quotation marks around the
firmware package path when specifying the package location on the command line with the -l
command-line parameter.
Questions
The following table provides information on interactive mode questions and requests for input.
Interactive mode
question/request
Description
Reference
Please enter action ("help\"
for list):
(required) Enter a command, or enter
help for a list of available
commands.
-a <command>
(required) Asked if help was entered
for previous question. Enter a
command.
-a <command>
(required for all commands except
discover and packageinfo) IP
address of the active OA in the
Commands (on page 11)
Please enter action:
Please enter Onboard
Administrator IP Address:
Commands (on page 11)
Commands (on page 11)
-i <IP>
Installation 9
Interactive mode
question/request
Please enter Onboard
Administrator Username:
Please enter Onboard
Administrator Password:
Please enter starting IP
address:
Description
primary enclosure
(required for all commands except
discover and packageinfo) User
name of the active OA in the primary
enclosure
(required for all commands except
discover and packageinfo)
Password of the active OA in the
primary enclosure
(required) First IP address in the
range to search
Please enter ending address:
(required) Ending IP address in the
range to search
Please enter firmware package
location:
(required) Full path to the Virtual
Connect package on the local
computer
Please enter the file location: (optional) Full path to the
configuration backup or support
dump file
Please enter the Configuration (optional) Password for the
configuration backup file
backup password:
Please enter Force Update
options if any (eg:
version,health):
Enter options separated by a
comma.
Enter one of the following: parallel,
Please enter VC-Enet module
odd-even, serial, or manual
activation order if any (eg:
parallel or odd-even or serial
or manual. Default: odd-even):
Enter one of the following: parallel,
Please enter VC-FC module
odd-even, serial, or manual
activation order if any (eg:
parallel or odd-even or serial
or manual. Default: serial):
Enter the time in minutes (maximum
Please enter the time (in
of 60 minutes).
minutes) to wait between
activating or rebooting VC-Enet
modules [max 60 mins. Default:
0 mins]:
Enter the time in minutes (maximum
Please enter the time (in
of 60 minutes).
minutes)to wait between
activating or rebooting VC-FC
modules [max 60 mins. Default:
0 mins]:
Reference
Commands (on page 11)
-u <USER>
Commands (on page 11)
-p <PWD>
discover
-s <START IP>
discover
-s <END IP>
packageinfo
report
update (on page 16)
-l <FILE>
configbackup
supportdump
-l <FILE>
configbackup
update (on page 16)
-cp <CONFIG PASS>
update (on page 16)
-f <FORCE>
update (on page 16)
-oe <ORDER>
update (on page 16)
-of <ORDER>
update (on page 16)
-we <MINUTES>
update (on page 16)
-wf <MINUTES>
Installation 10
Commands
collect
Contact the OA using the supplied credentials and execute a SHOW ALL from the OA CLI, saving the
output to an "oaShowAll.txt" file in the current directory.
This support action also contacts the primary VC module using the supplied credentials and executes the
following commands, saving the output to a "vcmShowAll.txt" file:
•
show enclosure *
•
show domain
•
show network *
•
show fabric *
•
show profile *
•
show stackinglink
•
show interconnect *
•
show firmware
Item
Description
Syntax
vcsu -a collect -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp <VCM
PASS>
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
VCM USER
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a
Virtual Connect domain. Minimum length is 1 character. Maximum length is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Example
Collect configuration information from OA and VC:
vcsu -a collect -i 192.168.0.100 -u Administrator -p password -vcu
Administrator -vcp password
discover
Locate remote OA enclosures that exist on the network within a specified address range. VCSU displays
the following:
•
Number of enclosures found
Commands
11
•
List of enclosure OA IPs with enclosure type, primary OA IP, and VC domain name
This command is useful if an Administrator cannot remember the exact IP address of the OA on a certain
enclosure, but knows the general IP address range.
Item
Description
Syntax
vcsu -a discover -s <START IP> -e <END IP>
Parameters:
START IP
First IP address in the range to search
END IP
Last IP address in the range to search
Example
Discover an enclosure in a certain address range:
vcsu -a discover -s 192.168.1.100 -e 192.168.1.200
configbackup
Using the supplied credentials, log in to Virtual Connect and request a configuration download. VCSU
saves the backup in the current directory using the file name supplied by Virtual Connect. This action
requires a functioning VC domain.
Item
Description
Syntax
vcsu -a configbackup -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp
<VCM PASS> [-cp <CONFIG PASS>] -l <LOCATION>
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
VCM USER
Name of the Virtual Connect user with Domain privileges. Required if an enclosure is in a
Virtual Connect domain. Minimum length is 1 character. Maximum length is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
CONFIG PASS Mandatory if the domain is in FIPS mode. Password for the configuration backup file.
Supported only for VC versions 3.00 and higher. The default is no password. Minimum
length is 8 characters for domains in FIPS mode.
LOCATION
Full path, including file name, to save the configuration backup file. If not provided, VCSU
saves the configuration backup file to the file name that VC provides and downloads it to the
current directory.
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Example
Request a configuration download from Virtual Connect:
vcsu -a configbackup -i 192.168.0.100 -u Administrator -p password -vcu
Administrator -vcp password
healthcheck
List the state of modules in the enclosure. This command is useful if an Administrator needs to know if
performing an action, such as a failover or a VC or OA firmware upgrade, would cause an outage.
Commands
12
On an enclosure configured for Virtual Connect, the command displays the following:
•
Onboard Administrator firmware version
•
Power: On, Off, other
•
Health: OK, Degraded, Failed, other
•
IP Address
•
Connectivity Test
•
Stacking link status (connection status and redundancy status)
•
For VC-Enet Modules:
o
VC Mode: Primary, Backup, Subordinate, Unintegrated
o
Module Configuration: In Sync, Not In Sync, Invalid
o
Domain Configuration (for primary or backup VC-Enet modules): In Sync, Not In Sync
The primary Virtual Connect module saves the domain configuration data to the backup module in a VC
domain at a regular interval. The 'Domain configuration' state indicates whether or not this data is in sync
between the two modules.
The 'Module configuration' state indicates whether all the modules in an enclosure are in sync with the
primary module regarding the Virtual Connect configuration information.
If a module is being reconfigured by Virtual Connect, or is rebooting, a "Not In Sync" or "Invalid"
configuration status might appear. Wait up to 2 minutes, and then execute the healthcheck command
again.
Item
Description
Syntax
vcsu -a healthcheck -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp
<VCM PASS>
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
VCM USER
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a
Virtual Connect domain. Minimum length is 1 character. Maximum length is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Example
List the state of modules in an enclosure:
vcsu -a healthcheck -i 192.168.0.100 -u Administrator -p password -vcu
Administrator -vcp password
packageinfo
Extract the package information from the supplied package path and display the following information:
•
Digital Signature Validation (for Virtual Connect firmware version 2.30 and higher)
•
Package Version
Commands
13
•
Ethernet Firmware Version Timestamp
•
Ethernet Firmware Supported Hardware
•
FC Firmware Version
•
FC Firmware Supported Hardware
•
Release Notes (extract, not display)
Item
Description
Syntax
vcsu -a packageinfo -l <FILE>
Parameter:
FILE
Full path to the Virtual Connect package on the local computer or supported remote server
Example
Display package information from a file named VCpackage:
vcsu -a packageinfo -l VCpackage
report
Display the current running firmware version on all modules in a specific target enclosure. Also display the
VC-Enet and VC-FC firmware versions provided in the specified VC package file, and whether or not the
module can be updated. In addition to displaying the module firmware version and status, the report
command also displays details about the VC package contents.
Because the package version details appear, you must provide a VC package file as part of the input at
the command line.
Item
Description
Syntax
vcsu -a report -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp <VCM PASS>
-l <FILE>
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
VCM USER
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual
Connect domain. Minimum length is 1 character. Maximum length is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
FILE
Full path to the Virtual Connect package on the local computer or supported remote server
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Example
Display all modules in an enclosure:
vcsu -a report -i 192.168.1.100 -u Administrator -p password -vcu
Administrator -vcp password -l VCpackage
Commands
14
resetvcm
Log in to the specified interconnect bay and restart the Virtual Connect service. This action is equivalent to
selecting the "Reset Virtual Connect Manager" option from the Tools pull-down menu on the Virtual
Connect GUI.
Item
Description
Syntax
vcsu -a resetvcm -i <IP> -u <USER> -p <PWD>
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Example
Reset the modules in an enclosure:
vcsu -a resetvcm -i 192.168.0.100 -u Administrator -p password
supportdump
Using the supplied credentials, log in to Virtual Connect and request a support information (debug dump)
download. VCSU saves the file in the current directory using the file name supplied by Virtual Connect.
This action requires a functioning VC domain.
Item
Description
Syntax
vcsu -a supportdump -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp <VCM
PASS> [-cp <CONFIG PASS>] -l <LOCATION>
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
VCM USER
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual
Connect domain. Minimum length is 1 character. Maximum length is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
CONFIG PASS Mandatory if the domain is in FIPS mode. Password for the configuration backup file.
Supported only for VC versions 4.30 and higher. The default is no password. Minimum
length is 8 characters for domains in FIPS mode.
LOCATION
Full path, including file name, to save the support dump file. If not provided, VCSU saves the
support dump file to the file name that VC provides and downloads it to the current directory.
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Example
Save support information:
Commands
15
vcsu -a supportdump -i 192.168.0.100 -u Administrator -p password -vcu
Administrator -vcp password
update
Update the firmware.
You must provide the primary OA IP address, user credentials, and the package file to use for the update.
You can force a module update in the following circumstances:
•
The target module contains a running firmware image that is the same version as the one in the
source package.
•
The target module is in a degraded or failed state.
If some of the modules are powered off, you can use the force option to update the modules that are
powered on.
Item
Description
Syntax
vcsu -a update -i <IP> -u <USER> -p <PWD> -l <FILE> [-f <FORCE>] -vcu
<VCM USER> -vcp <VCM PASS> [-q] [-oe <ORDER>] [-of <ORDER>] [-we
<MINUTES>] [-wf <MINUTES>] [-cp <CONFIG PASS>]
Parameters:
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
FILE
Full path to the Virtual Connect package on the local computer or supported remote server
FORCE
Optional. Comma-separated list of force operations under certain conditions:
VCM USER
Name of the Virtual Connect user with Domain privileges. This command is required if an
enclosure is in a Virtual Connect domain. Minimum length is 1 character. Maximum length
is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
-q
Optional. Specifies that the firmware update does not prompt for confirmation before
updating, and uses the default answer for the confirmation (YES).
-oe
Optional. Specifies VC-Enet module activation order. The following activation order
methods are supported:
•
•
•
•
•
•
-of
version—Allows an update of the same firmware version
health—Allows an update on a module with failed or degraded health
parallel—All modules are activated at the same time.
odd-even—(Default) The backup VC module is activated first. A force failover to the
backup module occurs, and then the primary module is activated. The modules in odd
bays are activated, and then modules in even bays are activated.
serial—The backup VC module is activated first. A force failover to the backup
module occurs, and then the primary module is activated. A checkpoint is completed
between the primary and standby module. Then the remaining modules are activated
one at a time, starting with the lowest numbered bay.
manual—Modules are updated but not activated. Use the VC GUI or the OA GUI to
activate (reboot) modules.
Optional. Specifies VC-FC module activation order. The following activation order methods
are supported:
•
•
parallel—All modules are activated at the same time.
odd-even—All modules in odd-numbered bays are activated first, and then modules in
even-numbered bays are activated.
Commands
16
Item
Description
•
•
serial—(Default) Modules are activated one at a time, starting with the lowest
numbered bay.
manual—Modules are updated but not activated. Use the OA GUI to activate (reboot)
modules.
-we
Optional. Specifies the amount of time, in minutes, to wait between activating or rebooting
VC-Enet modules. This command is required for some MPIO/teaming software on the
server blades in the enclosure. The default is 0, or no delay. Hewlett Packard Enterprise
recommends a minimum of 5 minutes.
-wf
Optional. Specifies the amount of time, in minutes, to wait between activating or rebooting
VC-FC modules. This command is required for some MPIO/teaming software on the server
blades in the enclosure. The default is 0, or no delay. Hewlett Packard Enterprise
recommends a minimum of 5 minutes.
-cp
Mandatory if the domain is in FIPS mode. Password for the configuration backup file.
Supported only for VC versions 3.00 and higher. The default is no password. Minimum
length is 8 characters for domains in FIPS mode.
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Examples
Update multiple modules in an enclosure imported into a VC domain with and IPv4 address:
vcsu -a update -i 192.168.1.100 -u Administrator -p password -vcu John -vcp
vcPass -l C:\images\vcfw-120.bin
Update multiple modules in an enclosure imported into a VC domain with and IPv6 address:
Vcsu –a update –i 2001:1::12 –u Administrator –p password –vcu John –vcp
vcPass –l C:\images\vcfw-120.bin
Perform an update and specify an activation ordering method:
vcsu -a update -i 192.168.1.100 -u Administrator -p password -vcu John -vcp
vcPass -l C:\images\vcfw-120.bin -oe serial -of parallel
Perform an update using a firmware image from a web server address:
vcsu –a update –i 192.168.1.100 –u Administrator –p password –l
http://www.myserver.com/vcfw-120.bin
Perform an update using a firmware image from an FTP server on the network with an IPv4 address:
vcsu –a update –i 192.168.1.100 –u Administrator –p password –l
ftp://user:[email protected]/vcfw-120.bin
Perform an update using a firmware image from an FTP server on the network with an IPv6 address:
vcsu –a update –i 2001:1::12 –u Administrator –p password –l
ftp://user:password@[2001:1:20]/vcfw-120.bin
Perform an update of the same firmware version on a degraded module:
vcsu -a update -i 192.168.1.100 -u Administrator -p password -l
C:\images\vcfc-120.bin -f version,health
version
Display the current running firmware version on all modules in a specific target enclosure.
Item
Description
Syntax
vcsu -a version -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp <VCM
PASS>
Parameters:
Commands
17
Item
Description
IP
IPv4 or IPv6 address of the active OA in the enclosure*
USER
Name of the OA user with privileges to access all enclosure interconnect bays. Minimum
length is 1 character. Maximum length is 40 characters.**
PWD
Password of the OA user. Minimum length is 3 characters. Maximum length is 40
characters.**
VCM USER
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual
Connect domain. Minimum length is 1 character. Maximum length is 31 characters.
VCM PASS
Password for the Virtual Connect user. Minimum length is 3 characters. Maximum length is
31 characters.
*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.
**In a multi-enclosure environment, USER and PWD parameters for the Onboard Administrator must be identical
across local and all remote enclosures in the Virtual Connect domain.
Examples
Display all modules and their current firmware versions:
vcsu -a version -i 192.168.1.100 -u Administrator -p password -vcu
Administrator -vcp password
Commands
18
Downgrades
Overview
This feature enables you to downgrade to a previously installed and running version of VC.
The following requirements are for downgrading firmware on a VC domain without destroying the domain.
Otherwise, to downgrade firmware on VC modules, you must first delete the domain and then use the -a
update command.
Restrictions
The following restrictions apply:
•
You must be running VC version 3.70 or higher to perform a downgrade.
•
You cannot downgrade to a VC version lower than version 3.17.
•
A previous upgrade must have been performed on the configuration using VCSU 1.7.0 or higher.
•
All servers in the domain must be powered off.
•
Multiple, consecutive firmware downgrades are not allowed.
•
You can downgrade only to the version previously installed and running on the primary module.
•
The VC configuration, including physical connections, uplink port connections, and module positions
in the enclosure, must be identical to the target downgrade configuration.
•
The VC credentials must be the same before and after the downgrade. After the downgrade, you
cannot change the password for the account used to perform the downgrade.
•
The primary E-net module must be in the lowest bay number.
•
If the primary VC module DIP switch is set to FIPS mode, VC firmware cannot be downgraded to a
non-FIPS capable version.
Downgrades
19
Manual activation
Manual activation of VC firmware
Use the following steps for manual activation of VC firmware:
1.
Determine which module is the Primary and which is Standby using the VCM CLI show
interconnect command or by executing VCSU with the -healthcheck option.
2.
In the base enclosure (ENC0), reset the module identified as the Standby module.
3.
Wait for the checkpoint to complete. You can view this within VCM, or you can run VCSU with the
-healthcheck option to see that the Domain configuration is "In Sync" on all the modules.
4.
Force a failover of VCM from the Primary to the Standby module by selecting Reset VCM from the
Tools pull-down menu and then selecting the checkbox to Force failover.
5.
Wait for the Standby module to become Primary and for the checkpoint to complete. (See step 3
above).
6.
In the base enclosure (ENC0), reset the module that was the original Primary module, but currently
is the Standby module.
7.
Wait for checkpoint to complete. You can view this within VCM, or you can run VCSU with the
-healthcheck option to see that the Domain configuration is "In Sync" on all the modules.
8.
After both the Primary and Standby modules are activated and are stable, reset all the modules on
the odd numbered side of each enclosure. This includes the base enclosure (ENC0) Bays 3, 5, and
7 and every remote enclosure (ENC1-ENC3) Bays 1, 3, 5, and 7.
9.
Wait for the checkpoint to complete. You can view this within VCM or you can run VCSU with the
-healthcheck option to see that the Domain configuration is "In Sync" on all the modules.
10.
After all the modules in the odd numbered I/O Bays are activated and are stable, reset all the
modules on the even numbered side of each enclosure. This includes the base enclosure (ENC0)
Bays 4, 6, and 8 and every remote enclosure (ENC1-ENC3) Bays 2, 4, 6, and 8.
Manual activation 20
Troubleshooting
VCSU error codes
Error code
Details
VCSU_SUCCESS
The operation was successful.
VCSU_ERROR_FAILED
The operation failed.
VCSU_ERROR_UNKNOWN
An unknown failure occurred.
VCSU_ERROR_ACCESS_DENIED
The user does not have the required privileges
to update the firmware.
VCSU_ERROR_INVALID_PARAMETER
One or more parameters are not valid.
VCSU_ERROR_INVALID_USERNAME
VCSU_ERROR_INVALID_PASSWORD
VCSU_ERROR_FILE_NOT_FOUND
The user name is not valid.
The password is not valid.
The specified file could not be found.
VCSU_ERROR_FILE_READ_FAILED
The specified file could not be read.
VCSU_ERROR_OA_COMMUNICATION_FAILURE
Unable to communicate with the Onboard
Administrator
VCSU_ERROR_VCM_COMMUNICATION_FAILURE
Unable to communicate with Virtual Connect
VCSU_ERROR_NULL_POINTER
A NULL pointer was specified.
VCSU_ERROR_PREVIOUS_UPDATE_INCOMPLETE
The previous firmware update operation did
not complete.
VCSU_ERROR_AUTHENTICATION_FAILURE
An authentication failure occurred.
VCSU_ERROR_BUFFER_TOO_SMALL
The specified buffer is too small.
VCSU_ERROR_UNSUPPORTED_FIRMWARE_PACKAGE The specified firmware package file is not
currently supported.
VCSU_ERROR_UNSUPPORTED_MODULE
One or more modules are not supported.
VCSU_ERROR_PACKAGE_NOT_SUPPORTED
The specified firmware package does not
support the module.
VCSU_ERROR_INVALID_URL
The specified URL is not valid.
VCSU_ERROR_URL_NOT_FOUND
The specified URL could not be found.
VCSU_ERROR_INVALID_ADDRESS
The specified address is not valid or does not
exist.
VCSU_ERROR_INVALID_TARGET_FILE
The specified target file is not valid or does not
exist.
VCSU_ERROR_FILE_OPEN_FAILED
The specified file could not be opened.
VCSU_ERROR_NO_WRITE_PERMISSION
The current user does not have write
permission to the specified directory.
VCSU_ERROR_FILE_WRITE_FAILED
Error in writing file to disk
VCSU_ERROR_INVALID_USER_CREDENTIALS
The user credentials are not valid.
VCSU_ERROR_AUTHENTICATION_REQUIRED
User authentication is required to perform the
requested operation.
VCSU_ERROR_NOT_IMPLEMENTED
The specified operation is not currently
implemented.
VCSU_ERROR_INVALID_TYPE
The specified type is not valid.
VCSU_ERROR_UNSUPPORTED_TYPE
VCSU_ERROR_MEMORY_ALLOCATION
The specified type is not currently supported.
Memory could not be allocated.
Troubleshooting
21
Error code
Details
VCSU_ERROR_INVALID_FIRMWARE_VERSION
The firmware version is not valid.
VCSU_ERROR_SOCKET_CREATE_FAILED
VCSU_ERROR_SOAP_INIT_FAILED
VCSU_ERROR_OBJECT_NOT_FOUND
VCSU_ERROR_INVALID_SYNTAX
VCSU_ERROR_INVALID_COMPONENT_TYPE
Socket could not be created.
A SOAP call initialization failure occurred.
The requested object does not exist.
The specified command syntax is not valid.
The specified component type is not valid.
VCSU_ERROR_UNSUPPORTED_ENDPOINT_VERSION
The version of the remote endpoint is not
supported.
VCSU_ERROR_UNKNOWN_ENDPOINT_TYPE
The remote endpoint is invalid or unknown.
VCSU_ERROR_TIMEOUT
Connection to the remote endpoint timed out.
VCSU_ERROR_MAINTENANCE_MODE
Maintenance mode is not set on the module.
VCSU_ERROR_CONFIGBACKUP_UNSUPPORTED
Configuration backup not supported on the
target.
VCSU_ERROR_SSH_SESSION_OPEN_FAILED
Unable to open an SSH session
VCSU_ERROR_SSH_SFTP_OPEN_FAILED
VCSU_ERROR_SSH_READ_FAILED
VCSU_ERROR_SSH_SFTP_READ_INCOMPLETE
VCSU_ERROR_SSH_SFTP_WRITE_FAILED
VCSU_ERROR_SSH_EXEC_FAILED
VCSU_ERROR_SSH_INVALID_RESPONSE
VCSU_ERROR_SSH_SESSION_INIT_FAILED
VCSU_ERROR_SSH_SFTP_INIT_FAILED
Unable to open an SFTP session
Unable to read from the SSH channel
Read from SFTP is incomplete.
The SFTP write failed.
The specified SSH command failed.
An invalid SSH response was received.
Unable to establish an SSH session
Unable to establish an SFTP session
VCSU_ERROR_SSH_SESSION_CREATE_FAILED
Unable to create an SSH session
VCSU_ERROR_SSH_LOGIN_FAILED
SSH login failed. Verify that the credentials
and the remote address are correct.
VCSU_ERROR_SSH_CONNECT_FAILED
Unable to connect to remote SSH endpoint
VCSU_ERROR_SSH_SESSION_NOT_ESTABLISHED
VCSU_ERROR_SSH_INVALID_COMMAND
VCSU_ERROR_SFTP_SHUTDOWN_FAILED
VCSU_ERROR_INVALID_IP_ADDRESS
The SSH session is not established.
Invalid SSH command
Failed to shut down SFTP
Invalid IP address
VCSU_ERROR_CONNECT_FAILED
Socket or connection call to the specified IP
failed.
VCSU_ERROR_OA_COMMUNICATION_FAILED
Unable to communicate using the given OA IP
VCSU_ERROR_GET_HOST_INFO_FAILED
Unable to retrieve host information from the
given IP
VCSU_ERROR_INVALID_OA_USERNAME
Invalid OA user name
VCSU_ERROR_INVALID_OA_PASSWORD
VCSU_ERROR_INVALID_BAY_NUMBER
VCSU_ERROR_OA_INIT_FAILED
VCSU_ERROR_OA_LOGIN_FAILED
VCSU_ERROR_OA_LOGOUT_FAILED
Invalid OA password
Invalid bay number
OA Initialization failed.
OA login failed.
OA logout from the current user failed.
VCSU_ERROR_OA_GET_NETWORK_INFO_FAILED
Could not get network information from either
Onboard Administrator
VCSU_ERROR_OA_FW_VERSION_NOT_SUPPORTED
OA firmware version is not supported without
force.
VCSU_ERROR_OA_FW_VERSION_SUPPORTED_WITH_ OA firmware version is not supported without
force.
FORCE
Communication to OA using SOAP failed.
VCSU_ERROR_OA_SOAP_CALL_FAILED
Troubleshooting
22
Error code
Details
VCSU_ERROR_VC_SOAP_CALL_FAILED
Communication to VC using SOAP failed.
VCSU_ERROR_OA_NOT_PRIMARY
VCSU_ERROR_OA_GET_VCM_MODE_FAILED
VCSU_ERROR_OA_INTERNAL_PASSWD_INVALID
VCSU_ERROR_INVALID_INFOBLOCK_FROM_OA
VCSU_ERROR_VCM_ACCESS_INFO_EXTRACTION_FAI
LED
VCSU_ERROR_UNSUPPORTED_ENCLOSURE
VCSU_ERROR_VCFC_NOT_RESPONDING
VCSU_ERROR_VENDOR_INFOBLOCK_RETURNED_ER
ROR
The specified OA is not primary.
Unable to retrieve OA VC mode information
The OA internal password length is invalid.
Invalid Info block from OA is received.
Unable to extract VC access information
The specified enclosure is not supported.
The VC FC module is not responding.
Vendor Info block returned an error.
VCSU_ERROR_BAY_INFO_RETRIEVAL_FAILED
Unable to retrieve information from the
interconnect module at the specified bay
VCSU_ERROR_NOT_PRIMARY_ENCLOSURE
The specified enclosure is not primary in the
domain.
VCSU_ERROR_PRIMARY_ENCLOSURE_NOT_FOUND
Failed to get Primary Enclosure information.
VCSU_ERROR_ENCLOSURE_NOT_IMPORTED
The specified enclosure is not imported in the
domain.
VCSU_ERROR_PRIMARY_OA_NOT_FOUND
Unable to find the Primary OA IP
VCSU_ERROR_BAY_COMMUNICATION_FAILURE
Unable to communicate with the interconnect
module in the specified bay
VCSU_ERROR_VCME_DOMAIN
VC ME domain
VCSU_ERROR_VCEM_DOMAIN
This VC domain is being managed by an
external manager. For instructions on
firmware updates, see the external manager
documentation.
VCSU_ERROR_CLI_COMMAND_FAILED
CLI command exited with non zero status.
VCSU_ERROR_WEBSERVER_NOT_RESPONDING
VCSU_ERROR_CHECKPOINT_NOT_REDUNDANT
VCSU_ERROR_CHECKPOINT_PENDING
VCSU_ERROR_VCM_LOCKED
VCSU_ERROR_VCM_NOT_LOCKED
VCSU_ERROR_CONFIG_PARSE_ERROR
VCSU_ERROR_VCM_CONFIG_NOT_IN_SYNC
VCSU_ERROR_SSL_FAILED
VCSU_ERROR_SSL_INIT_FAILED
VCSU_ERROR_SSL_WRITE_FAILED
VCSU_ERROR_SSL_READ_FAILED
VCSU_ERROR_SSL_OPEN_FAILED
VCSU_ERROR_FTP_NO_DATA
VCSU_ERROR_FTP_NOT_READY
VCSU_ERROR_FTP_USERNAME_NOT_VALID
VCSU_ERROR_FTP_PASSWORD_INVALID
VCSU_ERROR_FTP_REJECTED_PASSIVE_MODE
VCSU_ERROR_FTP_REJECTED_COMMAND
VCSU_ERROR_FTP_NO_RESPONSE
VCSU_ERROR_FTP_RECEIVE_ERROR
VCSU_ERROR_FTP_INVALID_IP
The web server is not responding.
Checkpoint not redundant
Checkpoint pending redundancy
VC is in a locked state.
VC is not in a locked state.
Failed to read the VC configuration details
VC configuration is not in sync.
SSL connection error
SSL initialization error
SSL write error
SSL read error
SSL open error
No data was received from the FTP server.
The FTP server is not ready.
The FTP username is not valid.
The FTP password is not valid.
The FTP server rejected passive mode.
The FTP server rejected the command.
The FTP server is not responding.
An FTP receive error exists.
Invalid FTP server IP address
Troubleshooting
23
Error code
Details
VCSU_ERROR_NO_UPDATABLE_MODULES
No target modules are found that can be
updated.
VCSU_ERROR_MODULE_UPDATE_NOT_REQD
The specified module is not required to be
updated.
VCSU_ERROR_MODULE_ACTIVATE_NOT_REQD
The specified module is not required to be
activated.
VCSU_ERROR_MODULE_INFO_NOT_AVAILABLE
The specified module's information is not
available.
VCSU_ERROR_MODULE_NOT_PRESENT
The specified module is not present.
VCSU_ERROR_MODULE_NOT_POWERED_ON
VCSU_ERROR_MODULE_NOT_OPERATIONAL
The specified module is not powered on.
The specified module is not operational.
VCSU_ERROR_ADMIN_PERMISSIONS_REQD
The admin privileges are required to upgrade
specified modules.
VCSU_ERROR_CHECKPOINT_RENAME_FAILED
The checkpoint rename operation failed on the
specified modules.
VCSU_ERROR_VCM_CONFIGURATION_NOT_IN_SYNC
The VC configuration is still not in sync.
VCSU_ERROR_VCM_FAILOVER_FAILED
Failover to backup module failed.
VCSU_ERROR_BAY_CONFIGURATION_FAILED
Unable to configure the bay
VCSU_ERROR_CLI_COMMAND_EXECUTION_FAILED
Unable to execute CLI command on the target
module
VCSU_ERROR_MODULE_NOT_UPGRADABLE
The specified module is not upgradeable.
VCSU_ERROR_MODULE_COMMAND_FAILED
VCSU_ERROR_RESET_TIME_OUT
VCSU_ERROR_RESET_FAILED
VCSU_ERROR_INVALID_MODULEID
The command on the target module failed.
The reset on the target module timed out.
The reset on the target module failed.
The specified module ID is invalid.
VCSU_ERROR_PREVIOUS_UPDATE_NOT_COMPLETET A previous firmware update operation on one
or more modules is not complete.
D
Another firmware update is running against
VCSU_ERROR_MULTIPLE_INSTANCE
the specified OA.
VCSU_ERROR_FC2_FW_EXTRACTION_FAILED
The extraction of the VC FC2 firmware
package failed.
VCSU_ERROR_DOWNGRADE_FROM_MULTIENCLOSU
RE
A downgrade from a 2.10 multi enclosure
domain is not supported.
VCSU_ERROR_NOT_MULTIENCLOSURE
Invalid module IDs for single enclosure update
VCSU_ERROR_VCM_MODE_RESTORE_FAILED
Failed to restore the VC mode of primary or
backup module
VCSU_ERROR_ACTIVATION_FAILED
Failed to activate one or more modules
VCSU_ERROR_UNINITIALIZED_MUTEX
Invalid mutex found
VCSU_ERROR_MODULE_NOT_FOUND
The specified module is not found at remote
endpoint.
VCSU_ERROR_DOWNGRADE_VCENET_VERSION
Internal Error: A downgrade from this version
of Virtual Connect firmware to the target
version would result in destruction of the
domain. Manually delete the Virtual Connect
domain and run the Virtual Connect Support
Utility again.
VCSU_ERROR_UNSUPPORTED_RESET_MODE
The specified reset mode is not supported.
VCSU_ERROR_CGI_FAILED
The specified CGI operation failed. Try the
operation again.
VCSU_XML_PARSING_FAILED
XML parsing of the description file failed.
VCSU_XML_FILE_EMPTY
The XML file is empty.
Troubleshooting
24
Error code
Details
VCSU_XML_INVALID_FILE
The XML file format is invalid.
VCSU_ERROR_PRIMARY_VCM_IP_NOT_FOUND
Could not get the Primary VC module IP
address
VCSU_ERROR_PRIMARY_VCM_NOT_FOUND
Could not find the Primary VC module
VCSU_ERROR_INVALID_HTTP_RESPONSE
VCSU_ERROR_UNKNOWN_HTTP_ERROR
VCSU_ERROR_HTTP_GET_ERROR
Invalid HTTP response
Unknown HTTP error
HTTP GET failed
VCSU_ERROR_HTTP_ERROR
The HTTP method returned an error. Check
the log for error details.
VCSU_ERROR_FILE_EXTRACT_FAILED
The specified firmware file could not be
extracted.
VCSU_ERROR_MODULE_IMAGE_INFO_NOT_AVAILABL
E
The image information for the specified
module type is not available in the package.
VCSU_ERROR_FW_SIGNATURE_VERIFICATION_FAILE
D
VCSU_ERROR_HEALTH_NOT_OK
VCSU_ERROR_POWER_NO_OP
VCSU_ERROR_POWER_UNKNOWN
VCSU_ERROR_POWER_OFF
VCSU_ERROR_POWER_STAGED_OFF
VCSU_ERROR_POWER_REBOOT
VCSU_ERROR_HEALTH_UNKNOWN
VCSU_ERROR_HEALTH_OTHER
VCSU_ERROR_HEALTH_DEGRADED
VCSU_ERROR_HEALTH_STRESSED
The signature verification of the specified
package failed.
The health of the module is not in a good state.
No Op
Unknown
Off
Staged Off
Reboot
Unknown
Other
Degraded
Stressed
VCSU_ERROR_HEALTH_PREDICTIVE_FAILURE
Predictive Failure
VCSU_ERROR_HEALTH_ERROR
Error
VCSU_ERROR_HEALTH_NON_RECOVERABLE_ERROR
VCSU_ERROR_HEALTH_STARTING
VCSU_ERROR_HEALTH_STOPPING
VCSU_ERROR_HEALTH_STOPPED
VCSU_ERROR_HEALTH_IN_SERVICE
VCSU_ERROR_HEALTH_NO_CONTACT
VCSU_ERROR_HEALTH_LOST_COMMUNICATION
VCSU_ERROR_HEALTH_ABORTED
VCSU_ERROR_HEALTH_DORMANT
VCSU_ERROR_HEALTH_SUPPORTING_ENTITY_IN_ER
ROR
VCSU_ERROR_HEALTH_COMPLETED
VCSU_ERROR_HEALTH_POWER_MODE
VCSU_ERROR_HEALTH_DMTF_RESERVED
VCSU_ERROR_HEALTH_VENDOR_RESERVED
Non Recoverable Error
Starting
Stopping
Stopped
In Service
No Contact
Lost Communication
Aborted
Dormant
Supporting Entity In Error
Completed
Power Mode
DMTF Reserved
Vendor Reserved
VCSU_ERROR_VLANID_NOT_SAME
Interconnect Module VLAN ID is different from
OA.
VCSU_ERROR_CONNECTION_UNKNOWN_MODULE
Unknown Module in bay
VCSU_ERROR_CONNECTION_FAILED
VCSU_ERROR_OPERATIONAL_MODE_UNKNOWN
IP connection to the module failed.
Unknown operational mode of the module
Troubleshooting
25
Error code
Details
VCSU_ERROR_DOMAIN_CONFIG_NOT_IN_SYNC
Domain Configuration is not in sync.
VCSU_ERROR_MODULE_CONFIG_NOT_IN_SYNC
VCSU_ERROR_MODULE_CONFIG_FIRMWARE_
INCOMPATIBLE
VCSU_ERROR_MODULE_CONFIG_INVALID_STATE
Module Configuration is not in sync.
Module Firmware Incompatible
Module Configuration is invalid.
VCSU_ERROR_UNSUPPORTED_CONFIGURATION
Enclosure or Interconnect Modules are in an
unsupported configuration.
VCSU_ERROR_SIM_INIT_FAILED
VCSU Simulator initialization failed.
VCSU_ERROR_CONFIG_READ_ERROR
Error reading VCSU Simulator Configuration
VCSU_ERROR_CONFIG_ELEM_NOT_FOUND
Element information not found in the XML
configuration file
VCSU_ERROR_UNSUPPORTED_VCSU_VERSION
This version of VCSU does not support the
update of specified firmware package.
VCSU_ERROR_UNSUPPORTED_OA_VERSION
One or more enclosure Onboard
Administrators is not running the minimum
required firmware version required by the
firmware package.
VCSU_ERROR_ACTIVATE_PRIMARY_BACKUP_FAILUR
E
Failed to activate primary/backup pair
VCSU_ERROR_VCEM_FW_MAINTENANCE_MODE
VC is locked and in firmware maintenance
state.
VCSU_ERROR_PRIMARY_BACKUP_HEALTH_NOT_OK
The health of primary or standby module is not
OK. The update cannot proceed.
VCSU_ERROR_MIN_TARGET_VERSION_ROLLBACK_
DOWNGRADE
The target version does not support the
downgrade of Virtual Connect firmware
without deletion of domain configuration.
VCSU_ERROR_MIN_VCM_VERSION_ROLLBACK_
DOWNGRADE
The current version of Virtual Connect
firmware does not support the downgrade
without deletion of domain configuration.
VCSU_ERROR_PRIMARY_NOT_IN_LOWER_BAY_FOR_
DOWNGRADE
Presence of subordinate module on lower bay
before primary module will not allow
downgrade.
VCSU_ERROR_ROLLBACK_DOWNGRADE_WILL_NOT_
PROCEED_FOR_MANUAL_ENET_ACTIVATION
Rollback downgrade will not proceed for
manual activation of E-net modules.
VCSU_ERROR_VCM_LOCKED_BY_VCEM_AND_FW_
MAINTENANCE_MODE
VC is locked by VCEM Firmware Maintenance
mode. Downgrade will not proceed.
VCSU_ERROR_ROLLBACK_DOWNGRADE_WILL_NOT_
PROCEED_FOR_SERVERPOWERON_NOSAFE
Powered ON servers or server profile
migration since upgrade and performing
downgrade may result in duplicate MAC/WWN
in the domain. Power OFF the servers to avoid
the MAC/WWN duplication and perform the
downgrade.
VCSU_ERROR_ROLLBACK_FAILED_TO_ACTIVATE_
LOWEST_BAY
Failed to activate lowest E-net bay for rollback
VCSU_ERROR_ROLLBACK_FAILED_TO_ACTIVATE_OD
DSIDE_MODULE
VCSU_ERROR_ROLLBACK_ACTIVATE_FAILURE
VCSU_ERROR_ROLLBACK_ODDMODULE_MANAGED_
STATUS_NOT_NORMAL
VCSU_ERROR_ADD_USER_FAILED
VCSU_ERROR_REMOVE_USER_FAILED
VCSU_ERROR_SET_NAME_FAILED
Failed to activate odd side modules for
rollback
Rollback activation failed
Odd module managed status is not Normal.
Unable to add user
Unable to remove user
Unable to set the user name
Troubleshooting
26
Error code
Details
VCSU_ERROR_AND_EXIT_FROM_UPDATE
Fatal error. One or more modules is
preventing VCSU from continuing. Correct
conditions listed above and retry.
VCSU_ERROR_MODULE_FAILOVER_FAILED
Module did not come up with proper role after
failover.
VCSU_ERROR_FIRMWARE_EXTRACT_FAILED
Failed to extract the VC firmware package
VCSU_ERROR_SET_TO_AUTO_FAILED
Failed to set the module to auto state
VCSU_ERROR_GET_ENCLOSURE_INFORMATION_FAIL Failed to get enclosure information
ED
Failed to set the module to subordinate state
VCSU_ERROR_SET_TO_SLAVE_FAILED
VCSU_ERROR_VC_LOGIN_FAILED
Failed to log in to Virtual Connect
VCSU_ERROR_ADD_VCM_USER_FAILED
Failed to add VC user in Onboard
Administrator
VCSU_ERROR_PRIMARYMODULE_BEING_IN_EVENBA
Y_
AND_NO_BACKUP_MODULE
Rollback will not proceed since primary
module is in even bay and there is no backup
module.
VCSU_ERROR_RESOLVE_HOST_INFO_FAILED
Failed to resolve the hostname
VCSU_ERROR_VCM_SKIP_FAILOVER
Virtual Connect does not have a valid Backup
module. Cannot failover.
VCSU_ERROR_DISCOVER_MODULES_FAILED
Failed to discover the Virtual Connect
modules
VCSU_ERROR_INVALID_OA_ADDRESS
Invalid Onboard Administrator IP Address
VCSU_ERROR_INVALID_VCM_ADDRESS
VCSU_ERROR_WRITE_OPERATION_FAILED
VCSU_ERROR_VCM_AUTHENTICATE_FAILED
Invalid Virtual Connect Manager IP Address
Failed to write into the file
Virtual Connect Manager authentication failed.
VCSU_ERROR_UNSUPPORTED_FIRMWARE_MODE
The firmware mode of the VCEM Domain
Group is not supported by the firmware
package.
VCSU_ERROR_DOMAIN_INVALID_CONFIGURATION
Onboard Administrator VCMODE is not
correct. Log into Virtual Connect Manager and
reestablish credentials, and retry Virtual
Connect Support Utility.
VCSU_ERROR_NO_ENET_MODULES
There are no VC-Enet modules in the domain.
VCSU_ERROR_SSH_SCP_WRITE_FAILED
VCSU_ERROR_FC_UPDATE_FAILED
The SCP write failed.
Failed to update the FC module
VCSU_ERROR_IPV6_DOWNGRADE_ERROR
The current version of Virtual Connect
firmware has IPv6 configuration that is not
supported by the target version. Downgrade
cannot be performed.
VCSU_ERROR_IPV6_DISCOVERY_NOT_SUPPORTED
VCSU does not support discovery using IPv6
addresses.
VCSU_ERROR_SAME_POWER_STATE
The power state of the specified module is
already the same. The operation cannot
continue.
VCSU_ERROR_ROLLBACK_CANNOT_PROCEED
VCSU cannot rollback to previous firmware
version.
VCSU_ERROR_VCM_DOMAIN_NOT_PRESENT
Virtual Connect Manager Domain is not
present.
VCSU_ERROR_FIPS_ROLLBACK_CANNOT_PROCEED
Target version does not support FIPS.
Rollback cannot proceed.
VCSU_ERROR_FIPS_CONFIGBACKUP_CANNOT_PROC cp option is required.
EED
Troubleshooting
27
Error code
Details
VCSU_ERROR_FIPS_ENCRYPTION_KEY_LENGTH
The provided encryption key password is less
than 8 characters.
VCSU_ERROR_FIPS_UPDATE_CANNOT_PROCEED
Target firmware does not support FIPS on one
or more modules. Update cannot proceed.
VCSU_ERROR_FIPS_DIP_SWITCH_NOT_SET
FIPS bit is not enabled on the switch
hardware.
VCSU_ERROR_UPDATE_FROM_NONFIPS_TO_FIPS_CA FIPS bit is set on one or more modules.
Update cannot proceed.
NNOT_PROCEED
Troubleshooting
28
Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website
(http://www.hpe.com/assistance).
•
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website (http://www.hpe.com/support/hpesc).
Information to collect
•
Technical support registration number (if applicable)
•
Product name, model or version, and serial number
•
Operating system name and version
•
Firmware version
•
Error messages
•
Product-specific reports and logs
•
Add-on products or components
•
Third-party products or components
Accessing updates
•
Some software products provide a mechanism for accessing software updates through the product
interface. Review your product documentation to identify the recommended software update
method.
•
To download product updates, go to either of the following:
•
o
Hewlett Packard Enterprise Support Center Get connected with updates page
(http://www.hpe.com/support/e-updates)
o
Software Depot website (http://www.hpe.com/support/softwaredepot)
To view and update your entitlements, and to link your contracts and warranties with your profile, go
to the Hewlett Packard Enterprise Support Center More Information on Access to Support
Materials page (http://www.hpe.com/support/AccessToSupportMaterials).
IMPORTANT: Access to some updates might require product entitlement when accessed
through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up
with relevant entitlements.
Websites
•
Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/enterprise/docs)
•
Hewlett Packard Enterprise Support Center (http://www.hpe.com/support/hpesc)
•
Contact Hewlett Packard Enterprise Worldwide (http://www.hpe.com/assistance)
Support and other resources 29
•
Subscription Service/Support Alerts (http://www.hpe.com/support/e-updates)
•
Software Depot (http://www.hpe.com/support/softwaredepot)
•
Customer Self Repair (http://www.hpe.com/support/selfrepair)
•
Insight Remote Support (http://www.hpe.com/info/insightremotesupport/docs)
•
Serviceguard Solutions for HP-UX (http://www.hpe.com/info/hpux-serviceguard-docs)
•
Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
(http://www.hpe.com/storage/spock)
•
Storage white papers and analyst reports (http://www.hpe.com/storage/whitepapers)
Customer Self Repair
Hewlett Packard Enterprise products are designed with many Customer Self Repair (CSR) parts to
minimize repair time and allow for greater flexibility in performing defective parts replacement. If during
the diagnosis period Hewlett Packard Enterprise (or Hewlett Packard Enterprise service providers or
service partners) identifies that the repair can be accomplished by the use of a CSR part, Hewlett Packard
Enterprise will ship that part directly to you for replacement. There are two categories of CSR parts:
•
Mandatory—Parts for which customer self repair is mandatory. If you request Hewlett Packard
Enterprise to replace these parts, you will be charged for the travel and labor costs of this service.
•
Optional—Parts for which customer self repair is optional. These parts are also designed for
customer self repair. If, however, you require that Hewlett Packard Enterprise replace them for you,
there may or may not be additional charges, depending on the type of warranty service designated
for your product.
NOTE: Some Hewlett Packard Enterprise parts are not designed for customer self repair. In order to
satisfy the customer warranty, Hewlett Packard Enterprise requires that an authorized service provider
replace the part. These parts are identified as "No" in the Illustrated Parts Catalog.
Based on availability and where geography permits, CSR parts will be shipped for next business day
delivery. Same day or four-hour delivery may be offered at an additional charge where geography
permits. If assistance is required, you can call the Hewlett Packard Enterprise Support Center and a
technician will help you over the telephone. Hewlett Packard Enterprise specifies in the materials shipped
with a replacement CSR part whether a defective part must be returned to Hewlett Packard Enterprise. In
cases where it is required to return the defective part to Hewlett Packard Enterprise, you must ship the
defective part back to Hewlett Packard Enterprise within a defined period of time, normally five (5)
business days. The defective part must be returned with the associated documentation in the provided
shipping material. Failure to return the defective part may result in Hewlett Packard Enterprise billing you
for the replacement. With a customer self repair, Hewlett Packard Enterprise will pay all shipping and part
return costs and determine the courier/carrier to be used.
For more information about the Hewlett Packard Enterprise CSR program, contact your local service
provider. For the North American program, go to the Hewlett Packard Enterprise CSR website
(http://www.hpe.com/support/selfrepair).
Réparation par le client (CSR)
Les produits Hewlett Packard Enterprise comportent de nombreuses pièces CSR (Customer Self Repair
= réparation par le client) afin de minimiser les délais de réparation et faciliter le remplacement des pièces
défectueuses. Si pendant la période de diagnostic, Hewlett Packard Enterprise (ou ses partenaires ou
mainteneurs agréés) détermine que la réparation peut être effectuée à l'aide d'une pièce CSR, Hewlett
Packard Enterprise vous l'envoie directement. Il existe deux catégories de pièces CSR :
Support and other resources 30
•
Obligatoire—Pièces pour lesquelles la réparation par le client est obligatoire. Si vous demandez à
Hewlett Packard Enterprise de remplacer ces pièces, les coûts de déplacement et main d'œuvre du
service vous seront facturés.
•
Facultatif—Pièces pour lesquelles la réparation par le client est facultative. Ces pièces sont
également conçues pour permettre au client d'effectuer lui-même la réparation. Toutefois, si vous
demandez à Hewlett Packard Enterprise de remplacer ces pièces, l'intervention peut ou non vous
être facturée, selon le type de garantie applicable à votre produit.
REMARQUE: Certaines pièces Hewlett Packard Enterprise ne sont pas conçues pour permettre au
client d'effectuer lui-même la réparation. Pour que la garantie puisse s'appliquer, Hewlett Packard
Enterprise exige que le remplacement de la pièce soit effectué par un Mainteneur Agréé. Ces pièces sont
identifiées par la mention "Non" dans le Catalogue illustré.
Les pièces CSR sont livrées le jour ouvré suivant, dans la limite des stocks disponibles et selon votre
situation géographique. Si votre situation géographique le permet et que vous demandez une livraison le
jour même ou dans les 4 heures, celle-ci vous sera facturée. Pour toute assistance, appelez le Centre
d’assistance Hewlett Packard Enterprise pour qu’un technicien vous aide au téléphone. Dans les
documents envoyés avec la pièce de rechange CSR, Hewlett Packard Enterprise précise s'il est
nécessaire de lui retourner la pièce défectueuse. Si c'est le cas, vous devez le faire dans le délai indiqué,
généralement cinq (5) jours ouvrés. La pièce et sa documentation doivent être retournées dans
l'emballage fourni. Si vous ne retournez pas la pièce défectueuse, Hewlett Packard Enterprise se réserve
le droit de vous facturer les coûts de remplacement. Dans le cas d'une pièce CSR, Hewlett Packard
Enterprise supporte l'ensemble des frais d'expédition et de retour, et détermine la société de courses ou
le transporteur à utiliser.
Pour plus d'informations sur le programme CSR de Hewlett Packard Enterprise, contactez votre
Mainteneur Agrée local. Pour plus d'informations sur ce programme en Amérique du Nord, consultez le
site Web Hewlett Packard Enterprise (http://www.hpe.com/support/selfrepair).
Riparazione da parte del cliente
Per abbreviare i tempi di riparazione e garantire una maggiore flessibilità nella sostituzione di parti
difettose, i prodotti Hewlett Packard Enterprise sono realizzati con numerosi componenti che possono
essere riparati direttamente dal cliente (CSR, Customer Self Repair). Se in fase di diagnostica Hewlett
Packard Enterprise (o un centro di servizi o di assistenza Hewlett Packard Enterprise) identifica il guasto
come riparabile mediante un ricambio CSR, Hewlett Packard Enterprise lo spedirà direttamente al cliente
per la sostituzione. Vi sono due categorie di parti CSR:
•
Obbligatorie—Parti che devono essere necessariamente riparate dal cliente. Se il cliente ne affida
la riparazione ad Hewlett Packard Enterprise, deve sostenere le spese di spedizione e di
manodopera per il servizio.
•
Opzionali—Parti la cui riparazione da parte del cliente è facoltativa. Si tratta comunque di
componenti progettati per questo scopo. Se tuttavia il cliente ne richiede la sostituzione ad Hewlett
Packard Enterprise, potrebbe dover sostenere spese addizionali a seconda del tipo di garanzia
previsto per il prodotto.
NOTA: alcuni componenti Hewlett Packard Enterprise non sono progettati per la riparazione da parte
del cliente. Per rispettare la garanzia, Hewlett Packard Enterprise richiede che queste parti siano
sostituite da un centro di assistenza autorizzato. Tali parti sono identificate da un "No" nel Catalogo
illustrato dei componenti.
In base alla disponibilità e alla località geografica, le parti CSR vengono spedite con consegna entro il
giorno lavorativo seguente. La consegna nel giorno stesso o entro quattro ore è offerta con un
supplemento di costo solo in alcune zone. In caso di necessità si può richiedere l'assistenza telefonica di
un addetto del centro di supporto tecnico Hewlett Packard Enterprise. Nel materiale fornito con una parte
di ricambio CSR, Hewlett Packard Enterprise specifica se il cliente deve restituire dei component. Qualora
sia richiesta la resa ad Hewlett Packard Enterprise del componente difettoso, lo si deve spedire ad
Hewlett Packard Enterprise entro un determinato periodo di tempo, generalmente cinque (5) giorni
lavorativi. Il componente difettoso deve essere restituito con la documentazione associata nell'imballo di
Support and other resources 31
spedizione fornito. La mancata restituzione del componente può comportare la fatturazione del ricambio
da parte di Hewlett Packard Enterprise. Nel caso di riparazione da parte del cliente, Hewlett Packard
Enterprise sostiene tutte le spese di spedizione e resa e sceglie il corriere/vettore da utilizzare.
Per ulteriori informazioni sul programma CSR di Hewlett Packard Enterprise, contattare il centro di
assistenza di zona. Per il programma in Nord America fare riferimento al sito Web
(http://www.hpe.com/support/selfrepair).
Customer Self Repair
Hewlett Packard Enterprise Produkte enthalten viele CSR-Teile (Customer Self Repair), um
Reparaturzeiten zu minimieren und höhere Flexibilität beim Austausch defekter Bauteile zu ermöglichen.
Wenn Hewlett Packard Enterprise (oder ein Hewlett Packard Enterprise Servicepartner) bei der Diagnose
feststellt, dass das Produkt mithilfe eines CSR-Teils repariert werden kann, sendet Ihnen Hewlett
Packard Enterprise dieses Bauteil zum Austausch direkt zu. CSR-Teile werden in zwei Kategorien
unterteilt:
•
Zwingend—Teile, für die das Customer Self Repair-Verfahren zwingend vorgegeben ist. Wenn Sie
den Austausch dieser Teile von Hewlett Packard Enterprise vornehmen lassen, werden Ihnen die
Anfahrt- und Arbeitskosten für diesen Service berechnet.
•
Optional—Teile, für die das Customer Self Repair-Verfahren optional ist. Diese Teile sind auch für
Customer Self Repair ausgelegt. Wenn Sie jedoch den Austausch dieser Teile von Hewlett Packard
Enterprise vornehmen lassen möchten, können bei diesem Service je nach den für Ihr Produkt
vorgesehenen Garantiebedingungen zusätzliche Kosten anfallen.
HINWEIS: Einige Hewlett Packard Enterprise Teile sind nicht für Customer Self Repair ausgelegt. Um
den Garantieanspruch des Kunden zu erfüllen, muss das Teil von einem Hewlett Packard Enterprise
Servicepartner ersetzt werden. Im illustrierten Teilekatalog sind diese Teile mit „No“ bzw. „Nein“
gekennzeichnet.
CSR-Teile werden abhängig von der Verfügbarkeit und vom Lieferziel am folgenden Geschäftstag
geliefert. Für bestimmte Standorte ist eine Lieferung am selben Tag oder innerhalb von vier Stunden
gegen einen Aufpreis verfügbar. Wenn Sie Hilfe benötigen, können Sie das Hewlett Packard Enterprise
Support Center anrufen und sich von einem Mitarbeiter per Telefon helfen lassen. Den Materialien von
Hewlett Packard Enterprise, die mit einem CSR-Ersatzteil geliefert werden, können Sie entnehmen, ob
das defekte Teil an Hewlett Packard Enterprise zurückgeschickt werden muss. Wenn es erforderlich ist,
das defekte Teil an Hewlett Packard Enterprise zurückzuschicken, müssen Sie dies innerhalb eines
vorgegebenen Zeitraums tun, in der Regel innerhalb von fünf (5) Geschäftstagen. Das defekte Teil muss
mit der zugehörigen Dokumentation in der Verpackung zurückgeschickt werden, die im Lieferumfang
enthalten ist. Wenn Sie das defekte Teil nicht zurückschicken, kann Hewlett Packard Enterprise Ihnen
das Ersatzteil in Rechnung stellen. Im Falle von Customer Self Repair kommt Hewlett Packard Enterprise
für alle Kosten für die Lieferung und Rücksendung auf und bestimmt den Kurier-/Frachtdienst.
Weitere Informationen über das Hewlett Packard Enterprise Customer Self Repair Programm erhalten
Sie von Ihrem Servicepartner vor Ort. Informationen über das CSR-Programm in Nordamerika finden Sie
auf der Hewlett Packard Enterprise Website unter (http://www.hpe.com/support/selfrepair).
Reparaciones del propio cliente
Los productos de Hewlett Packard Enterprise incluyen muchos componentes que el propio usuario puede
reemplazar (Customer Self Repair, CSR) para minimizar el tiempo de reparación y ofrecer una mayor
flexibilidad a la hora de realizar sustituciones de componentes defectuosos. Si, durante la fase de
diagnóstico, Hewlett Packard Enterprise (o los proveedores o socios de servicio de Hewlett Packard
Enterprise) identifica que una reparación puede llevarse a cabo mediante el uso de un componente CSR,
Hewlett Packard Enterprise le enviará dicho componente directamente para que realice su sustitución.
Los componentes CSR se clasifican en dos categorías:
Support and other resources 32
•
Obligatorio—componentes cuya reparación por parte del usuario es obligatoria. Si solicita a
Hewlett Packard Enterprise que realice la sustitución de estos componentes, tendrá que hacerse
cargo de los gastos de desplazamiento y de mano de obra de dicho servicio.
•
Opcional—componentes cuya reparación por parte del usuario es opcional. Estos componentes
también están diseñados para que puedan ser reparados por el usuario. Sin embargo, si precisa
que Hewlett Packard Enterprise realice su sustitución, puede o no conllevar costes adicionales,
dependiendo del tipo de servicio de garantía correspondiente al producto.
NOTA: Algunos componentes de Hewlett Packard Enterprise no están diseñados para que puedan ser
reparados por el usuario. Para que el usuario haga valer su garantía, Hewlett Packard Enterprise pone
como condición que un proveedor de servicios autorizado realice la sustitución de estos componentes.
Dichos componentes se identifican con la palabra "No" en el catálogo ilustrado de componentes.
Según la disponibilidad y la situación geográfica, los componentes CSR se enviarán para que lleguen a
su destino al siguiente día laborable. Si la situación geográfica lo permite, se puede solicitar la entrega en
el mismo día o en cuatro horas con un coste adicional. Si precisa asistencia técnica, puede llamar al
Centro de asistencia técnica de Hewlett Packard Enterprise y recibirá ayuda telefónica por parte de un
técnico. Con el envío de materiales para la sustitución de componentes CSR, Hewlett Packard Enterprise
especificará si los componentes defectuosos deberán devolverse a Hewlett Packard Enterprise. En
aquellos casos en los que sea necesario devolver algún componente a Hewlett Packard Enterprise,
deberá hacerlo en el periodo de tiempo especificado, normalmente cinco días laborables. Los
componentes defectuosos deberán devolverse con toda la documentación relacionada y con el embalaje
de envío. Si no enviara el componente defectuoso requerido, Hewlett Packard Enterprise podrá cobrarle
por el de sustitución. En el caso de todas sustituciones que lleve a cabo el cliente, Hewlett Packard
Enterprise se hará cargo de todos los gastos de envío y devolución de componentes y escogerá la
empresa de transporte que se utilice para dicho servicio.
Para obtener más información acerca del programa de Reparaciones del propio cliente de Hewlett
Packard Enterprise, póngase en contacto con su proveedor de servicios local. Si está interesado en el
programa para Norteamérica, visite la página web de Hewlett Packard Enterprise CSR
(http://www.hpe.com/support/selfrepair).
Customer Self Repair
Veel onderdelen in Hewlett Packard Enterprise producten zijn door de klant zelf te repareren, waardoor
de reparatieduur tot een minimum beperkt kan blijven en de flexibiliteit in het vervangen van defecte
onderdelen groter is. Deze onderdelen worden CSR-onderdelen (Customer Self Repair) genoemd. Als
Hewlett Packard Enterprise (of een Hewlett Packard Enterprise Service Partner) bij de diagnose vaststelt
dat de reparatie kan worden uitgevoerd met een CSR-onderdeel, verzendt Hewlett Packard Enterprise
dat onderdeel rechtstreeks naar u, zodat u het defecte onderdeel daarmee kunt vervangen. Er zijn twee
categorieën CSR-onderdelen:
•
Verplicht—Onderdelen waarvoor reparatie door de klant verplicht is. Als u Hewlett Packard
Enterprise verzoekt deze onderdelen voor u te vervangen, worden u voor deze service reiskosten en
arbeidsloon in rekening gebracht.
•
Optioneel—Onderdelen waarvoor reparatie door de klant optioneel is. Ook deze onderdelen zijn
ontworpen voor reparatie door de klant. Als u echter Hewlett Packard Enterprise verzoekt deze
onderdelen voor u te vervangen, kunnen daarvoor extra kosten in rekening worden gebracht,
afhankelijk van het type garantieservice voor het product.
OPMERKING: Sommige Hewlett Packard Enterprise onderdelen zijn niet ontwikkeld voor reparatie door
de klant. In verband met de garantievoorwaarden moet het onderdeel door een geautoriseerde Service
Partner worden vervangen. Deze onderdelen worden in de geïllustreerde onderdelencatalogus
aangemerkt met "Nee".
Afhankelijk van de leverbaarheid en de locatie worden CSR-onderdelen verzonden voor levering op de
eerstvolgende werkdag. Levering op dezelfde dag of binnen vier uur kan tegen meerkosten worden
aangeboden, indien dit mogelijk is gezien de locatie. Indien assistentie is gewenst, belt u het Hewlett
Packard Enterprise Support Center om via de telefoon ondersteuning van een technicus te ontvangen.
Support and other resources 33
Hewlett Packard Enterprise vermeldt in de documentatie bij het vervangende CSR-onderdeel of het
defecte onderdeel aan Hewlett Packard Enterprise moet worden geretourneerd. Als het defecte
onderdeel aan Hewlett Packard Enterprise moet worden teruggezonden, moet u het defecte onderdeel
binnen een bepaalde periode, gewoonlijk vijf (5) werkdagen, retourneren aan Hewlett Packard Enterprise.
Het defecte onderdeel moet met de bijbehorende documentatie worden geretourneerd in het
meegeleverde verpakkingsmateriaal. Als u het defecte onderdeel niet terugzendt, kan Hewlett Packard
Enterprise u voor het vervangende onderdeel kosten in rekening brengen. Bij reparatie door de klant
betaalt Hewlett Packard Enterprise alle verzendkosten voor het vervangende en geretourneerde
onderdeel en kiest Hewlett Packard Enterprise zelf welke koerier/transportonderneming hiervoor wordt
gebruikt.
Neem contact op met een Service Partner voor meer informatie over het Customer Self Repair
programma van Hewlett Packard Enterprise. Informatie over Service Partners vindt u op de Hewlett
Packard Enterprise website (http://www.hpe.com/support/selfrepair).
Reparo feito pelo cliente
Os produtos da Hewlett Packard Enterprise são projetados com muitas peças para reparo feito pelo
cliente (CSR) de modo a minimizar o tempo de reparo e permitir maior flexibilidade na substituição de
peças com defeito. Se, durante o período de diagnóstico, a Hewlett Packard Enterprise (ou
fornecedores/parceiros da Hewlett Packard Enterprise) concluir que o reparo pode ser efetuado pelo uso
de uma peça CSR, a Hewlett Packard Enterprise enviará a peça diretamente ao cliente. Há duas
categorias de peças CSR:
•
Obrigatória—Peças cujo reparo feito pelo cliente é obrigatório. Se desejar que a Hewlett Packard
Enterprise substitua essas peças, serão cobradas as despesas de transporte e mão-de-obra do
serviço.
•
Opcional—Peças cujo reparo feito pelo cliente é opcional. Essas peças também são projetadas
para o reparo feito pelo cliente. No entanto, se desejar que a Hewlett Packard Enterprise as
substitua, pode haver ou não a cobrança de taxa adicional, dependendo do tipo de serviço de
garantia destinado ao produto.
OBSERVAÇÃO: Algumas peças da Hewlett Packard Enterprise não são projetadas para o reparo feito
pelo cliente. A fim de cumprir a garantia do cliente, a Hewlett Packard Enterprise exige que um técnico
autorizado substitua a peça. Essas peças estão identificadas com a marca "No" (Não), no catálogo de
peças ilustrado.
Conforme a disponibilidade e o local geográfico, as peças CSR serão enviadas no primeiro dia útil após o
pedido. Onde as condições geográficas permitirem, a entrega no mesmo dia ou em quatro horas pode
ser feita mediante uma taxa adicional. Se precisar de auxílio, entre em contato com o Centro de suporte
técnico da Hewlett Packard Enterprise para que um técnico o ajude por telefone. A Hewlett Packard
Enterprise especifica nos materiais fornecidos com a peça CSR de reposição se a peça com defeito deve
ser devolvida à Hewlett Packard Enterprise. Nos casos em que isso for necessário, é preciso enviar a
peça com defeito à Hewlett Packard Enterprise, você deverá enviar a peça com defeito de volta para a
Hewlett Packard Enterprise dentro do período de tempo definido, normalmente em 5 (cinco) dias úteis. A
peça com defeito deve ser enviada com a documentação correspondente no material de transporte
fornecido. Caso não o faça, a Hewlett Packard Enterprise poderá cobrar a reposição. Para as peças de
reparo feito pelo cliente, a Hewlett Packard Enterprise paga todas as despesas de transporte e de
devolução da peça e determina a transportadora/serviço postal a ser utilizado.
Para obter mais informações sobre o programa de reparo feito pelo cliente da Hewlett Packard
Enterprise, entre em contato com o fornecedor de serviços local. Para o programa norte-americano, visite
o site da Hewlett Packard Enterprise (http://www.hpe.com/support/selfrepair).
Support and other resources 34
Support and other resources 35
Support and other resources 36
Remote support
Remote support is available with supported devices as part of your warranty or contractual support
agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event
notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your
product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for
remote support.
For more information and device support details, go to the Insight Remote Support website
(http://www.hpe.com/info/insightremotesupport/docs).
Support and other resources 37
Acronyms and abbreviations
DHCP
Dynamic Host Configuration Protocol
DNS
domain name system
FC
Fibre Channel
HTTPS
hypertext transfer protocol secure sockets
OA
Onboard Administrator
SOAP
Simple Object Access Protocol
SSH
Secure Shell
SSL
Secure Sockets Layer
TLS
Transport Layer Security
VC
Virtual Connect
VCM
Virtual Connect Manager
VCSU
Virtual Connect Support Utility
Acronyms and abbreviations 38
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us
improve the documentation, send any errors, suggestions, or comments to Documentation Feedback
(mailto:[email protected]). When submitting your feedback, include the document title, part
number, edition, and publication date located on the front cover of the document. For online help content,
include the product name, product version, help edition, and publication date located on the legal notices
page.
Documentation feedback 39
Index
A
P
authorized reseller 29
packageinfo command 13
password masking 9
problem diagnosis 21
B
before you contact Hewlett Packard Enterprise 29
R
C
report command 14
requirements, system 4
resetvcm command 15
resources 29
collect command 11
command line syntax 7
commands 11
configbackup command 12
contacting HPE 29
D
discover command 11
downgrade overview 19
downgrade restrictions 19
downgrades 19
S
support 29
support and other resources 29
supportdump command 15
supported servers 21
supported targets 21
T
error code 21
technical support 29
telephone numbers 29
troubleshooting 21
F
U
features 4
update command 16
H
V
healthcheck command 12
HPE Technical Support 29
HPE, contacting 29
version command 17
I
website, HPE 29
E
W
installing on HP-UX, silent 4
interactive mode 9
introduction 4
M
manual update 20
O
overview 4
Index 40