HP BladeSystem c-Class Virtual Connect Support Utility Version 1.6.0 User Guide
Commands  13 
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 
•  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, the user 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> -l <FILE> 
Parameters:  
IP
IPv4 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 
BAY 
Optional. The bay number of the target module. If not specified, the default is all supported 
modules. 
*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 










