0% found this document useful (0 votes)
11 views

Cb25000044 2500 Series Managment Module User Guide

Uploaded by

Jayson JHBZA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views

Cb25000044 2500 Series Managment Module User Guide

Uploaded by

Jayson JHBZA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 620

Hitachi Compute Blade 2500 Series

Management Module User Guide

Document Organization

Product Version

Getting Help

Contents

MK-99CB2500004-04
© 2014-2015 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying and recording, or stored in a database or retrieval
system for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and
assumes no responsibility for its use. This document contains the most current information available
at the time of publication. When new or revised information becomes available, this entire
document will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the most
recent product announcement for information about feature and product availability, or contact
Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of
the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is
governed by the terms of your agreements with Hitachi Data Systems Corporation.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi
Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and
other countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,


Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are
registered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,
FlashCopy, IBM, Lotus, MVS, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA,
z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International
Business Machines Corporation.

All other trademarks, service marks, and company names in this document or website are
properties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

ii
Hitachi Compute Blade 2500 Series Management Module User Guide
Contents
Preface .............................................................................................. xv
Intended Audience ............................................................................................... xvi
Product Version .................................................................................................... xvi
Release Notes ...................................................................................................... xvi
Document Organization ........................................................................................ xvi
Referenced Documents ........................................................................................ xvii
Document Conventions ........................................................................................ xvii
Conventions for storage capacity values ............................................................... xviii
Getting help ......................................................................................................... xix
Comments ........................................................................................................... xix

1 Management Module Overview ........................................................... 1-1


Management modules .......................................................................................... 1-2
Settings for the consoles used for management module operations ......................... 1-2
Logging in to the Web console ....................................................................... 1-2
Components of the Web console .................................................................... 1-3
Dashboard of the Web console ....................................................................... 1-5
Logging in to the CLI console ......................................................................... 1-8
CLI console initial window .............................................................................. 1-9
Logging out from the CLI console ................................................................. 1-10
LCD touch console specifications and functionality ......................................... 1-10
Connecting the LCD touch console to the server chassis ................................. 1-11

2 Preparations for Using the Management Module .................................. 2-1


Language settings ............................................................................................... 2-3
Time settings ...................................................................................................... 2-3
Time settings that can be specified in the management module ........................ 2-3
Time settings to enable DST .......................................................................... 2-4
Setting the time of the management module ................................................... 2-5
Synchronizing the time of the management module with the time of an NTP
server ........................................................................................................... 2-6
Synchronizing the time of the management module with the time of other
modules ....................................................................................................... 2-7
Strengthening the security of management modules and BMC ................................ 2-8
Services provided by management modules and their security settings ............. 2-8

iii
Hitachi Compute Blade 2500 Series Management Module User Guide
Services provided by BMC and their security settings ....................................... 2-9
Security strength for management modules and BMC ..................................... 2-10
Points to check before setting the security strength for management modules
and BMC ..................................................................................................... 2-11
Differences in usable functionality depending on the security strength settings 2-11
Setting the security strength for management modules and BMC .................... 2-15
TLS version settings ..................................................................................... 2-16
Configuring TLS version settings ................................................................... 2-17
IP address restriction settings for management module services ..................... 2-17
Editing the Telnet connection settings ........................................................... 2-18
Editing the FTP connection settings .............................................................. 2-19
Editing the SSH/SFTP connection settings ..................................................... 2-20
Editing the HTTP connection settings ............................................................ 2-20
Editing the HTTPS connection settings .......................................................... 2-21
Login banner settings .................................................................................. 2-21
Setting the display of a login banner ............................................................. 2-22
Disabling the Web console functionality ......................................................... 2-23
Disabling a USB port .................................................................................... 2-23
Disabling or enabling a USB port ................................................................... 2-23
Strengthening security by using digital certificates ............................................... 2-24
Digital certificates ........................................................................................ 2-24
Specifications for using digital certificates ...................................................... 2-25
Using self-signed certificates ........................................................................ 2-26
Using digital certificates signed by certificate authority ................................... 2-27
Setting the chassis ID to identify the server chassis .............................................. 2-28
Chassis ID ................................................................................................... 2-28
Setting the chassis ID .................................................................................. 2-29
User management using management modules ................................................... 2-29
Management module roles ........................................................................... 2-29
Setting a role .............................................................................................. 2-30
Management module user accounts .............................................................. 2-31
Initial account settings (the settings at shipping time) .................................... 2-32
Setting up a user account ............................................................................ 2-32
Setting a password expiration date ............................................................... 2-33
Setting a password expiration date ............................................................... 2-35
User management using an LCD touch console .............................................. 2-35
Setting a PIN for the LCD touch console ........................................................ 2-36
Initializing a PIN for the LCD touch console ................................................... 2-36
Disabling the LCD touch console functionality ................................................ 2-37
Network settings ................................................................................................ 2-37
Functionality available for management interfaces of each module .................. 2-37
Management network .................................................................................. 2-37
Internal network .......................................................................................... 2-38
Changing the IP address of the internal network ............................................ 2-39
IP address settings ...................................................................................... 2-40
IP address setting items ............................................................................... 2-41
Setting the IP addresses of management modules, server blades, and switch
modules ...................................................................................................... 2-42
Setting DNS servers ..................................................................................... 2-44
Improving failure handling by configuring management modules in a
redundant configuration ............................................................................... 2-45

iv
Hitachi Compute Blade 2500 Series Management Module User Guide
Improving failure handling by configuring management networks in a
redundant configuration ............................................................................... 2-46
Changing the monitoring time for the management network ........................... 2-48
Operating identification lamps of each module ..................................................... 2-48
Identification lamp ....................................................................................... 2-48
Operating the identification lamp of the management module ........................ 2-49
Operating the identification lamp of a management LAN module ..................... 2-50
Operating the identification lamp of a server blade ........................................ 2-51
Operating the identification lamp of an I/O adapter ....................................... 2-51
Operating the identification lamp of a switch module ..................................... 2-52
Power supply operation for a server blade ........................................................... 2-53
Power supply operation for a server blade by using the management module .. 2-53
Setting the server blade operation performed when the power supply of the
system unit is restored ................................................................................. 2-53
Efficient operation of server blades by SMP configurations .................................... 2-54
SMP configurations for server blades ............................................................. 2-54
Configuring SMP configurations for server blades ........................................... 2-55
Operating server blades by using the remote console ........................................... 2-56
Remote console ........................................................................................... 2-56
Starting the remote console ......................................................................... 2-56
Checking remote console session information ................................................ 2-57
Disconnecting remote console sessions ......................................................... 2-57
Operating server blades by using the OS console ................................................. 2-57
OS console .................................................................................................. 2-58
Checking OS serial port settings ................................................................... 2-58
Starting the OS console ................................................................................ 2-59
Notes on using the OS console ..................................................................... 2-59
Setting server blades, switch modules, and Hitachi Fibre Channel adapter ............. 2-61
Modules that can be operated from a management module ............................ 2-61
Setting the BMC of a server blade ................................................................. 2-62
BMC setting items for a server blade ............................................................. 2-62
Setting the UEFI for a server blade ............................................................... 2-76
Setting a switch module ............................................................................... 2-77
Setting a Hitachi Fibre Channel adapter ......................................................... 2-77
Setting items for a Hitachi Fibre Channel adapter ........................................... 2-77
Setting WWNs and MAC addresses ...................................................................... 2-79
WWNs and MAC addresses ........................................................................... 2-79
Selecting WWNs and MAC addresses to be used in the Basic mode ................. 2-80
Selecting WWNs and MAC addresses to be used in the LP mode ..................... 2-81
Relation between N+M cold standby and WWN and MAC address ................... 2-81
Initializing Optional Physical WWNs and Optional Physical MAC addresses ....... 2-82
Initializing or changing Optional Physical WWNs ............................................ 2-82
Initializing or changing Optional Physical MAC addresses ................................ 2-83
WWNs and MAC addresses that can be checked in management module
consoles ..................................................................................................... 2-84
Checking the Default Physical WWN .............................................................. 2-85
Checking Optional Physical WWNs ................................................................ 2-86
Checking the currently used WWN ................................................................ 2-86
Checking the Default Physical MAC address ................................................... 2-86
Checking Optional Physical MAC addresses .................................................... 2-87
Checking the currently used MAC addresses .................................................. 2-87

v
Hitachi Compute Blade 2500 Series Management Module User Guide
What you can check in the change log for Optional Physical WWNs and MAC
addresses ................................................................................................... 2-87
Controlling power consumption by using the power control functionality ................ 2-88
Power control functionality ........................................................................... 2-88
Accurate power control (APC) functionality .................................................... 2-90
Setting the upper limit on power consumption during system unit operation .... 2-90
Server blade operation for when the upper limit on power consumption during
system unit operation is set .......................................................................... 2-91
Disabling power control for server blades ...................................................... 2-93
Disabling power control for server blades ...................................................... 2-93
Behavior of the APC functionality for the system unit when the power control
is disabled for server blades ......................................................................... 2-94
DCMI .......................................................................................................... 2-96
Enabling and disabling the DCMI mode ......................................................... 2-97
List of supported DCMI commands ............................................................... 2-98
Power capacity expansion functionality ........................................................ 2-101
Power supply according to the number of installed power supply modules ..... 2-106
Using surplus power to expand the usable power ......................................... 2-108
Displaying monitored electric power values .................................................. 2-108
Checking electric power usage .................................................................... 2-109
Setting the power-off sequence for server blades when the power capacity is
exceeded .................................................................................................. 2-110
Setting the forced-power-off sequence for server blades when the power that
can be supplied to the system unit is insufficient .......................................... 2-110
Specifying all settings for a server chassis by using an import file ........................ 2-111
Importing a settings file ............................................................................. 2-111
Checking the template used to set the import file format .............................. 2-113
Importing a settings file ............................................................................. 2-116
Notes on changing the settings for import files ............................................ 2-117
Example of changing the settings for an import file ...................................... 2-117
Causes and actions to take if importing of an import file fails ........................ 2-119

3 Efficient Management of Servers Using the Management Module .......... 3-1


Linkage with the server management software (HCSM) .......................................... 3-2
Linkage with HCSM ........................................................................................ 3-2
Specifying the HCSM linkage options .............................................................. 3-3
Specifying information regarding HCSM registered in the management module .. 3-5
Preparation for running the server blades in a redundant configuration (N+M cold
standby) ............................................................................................................. 3-6
N+M cold standby ......................................................................................... 3-6
Mechanism of N+M cold standby .................................................................... 3-8
Notes on N+M cold standby ........................................................................... 3-9
Settings inherited through N+M cold standby .................................................. 3-9
Time required for the standby server blade to take over for the active server
blade .......................................................................................................... 3-11
Required unit configuration for N+M cold standby .......................................... 3-12
Configuring an environment for running server blades in a redundant
configuration (N+M cold standby) ....................................................................... 3-13
General procedure for configuring N+M cold standby ..................................... 3-13
Collecting the settings for the active server blade (Smart configure) ................ 3-14
Settings that must be specified to collect settings from the active server blade 3-16
Points to be checked before executing Smart configure .................................. 3-16

vi
Hitachi Compute Blade 2500 Series Management Module User Guide
Executing Smart configure to collect the settings from the active server blade . 3-16
Enabling the N+M cold standby support functionality ..................................... 3-17
Specifying WWN, iSCSI, and FCoE settings in the SAN .................................... 3-18
Specifying the necessary settings for the active server blade .......................... 3-18
Setting N+M cold standby from HCSM ........................................................... 3-18
Confirming that the standby server blade can take over for the active server
blade .......................................................................................................... 3-19
Notes on changing the settings after starting the N+M cold standby operation 3-19
Notes on replacing the CNA after starting the N+M cold standby operation ...... 3-20
Restoring N+M cold standby following recovery from a power failure .............. 3-20
Failure management through failover from the active to standby server blade (HA
monitor) ............................................................................................................ 3-21
HA monitor ................................................................................................. 3-21
Setting the reset path .................................................................................. 3-22
Highly-reliable HA monitor ............................................................................ 3-24
High-speed failover support functionality ....................................................... 3-25
Cluster management functionality ................................................................. 3-26
Notes on using the high-speed failover support functionality ........................... 3-26
Notes on using the cluster management functionality ..................................... 3-26
Enabling the high-speed failover support functionality for the HA monitor and
the cluster management functionality ............................................................ 3-27
Troubleshooting for the cluster management functionality .............................. 3-28
Viewing the host information of the server blade .................................................. 3-32
Installing the necessary tool (server installation and monitoring tool) .............. 3-32
Host information that can be viewed ............................................................. 3-32
Notes on viewing the host information .......................................................... 3-34
Displaying the host information .................................................................... 3-34
Deleting the host information ....................................................................... 3-35
Managing user account information by using LDAP ............................................... 3-35
LDAP linkage ............................................................................................... 3-35
General procedure for configuring Active Directory ......................................... 3-37
Registering a server certificate ..................................................................... 3-38
Registering a user for connecting to an LDAP server ...................................... 3-38
Registering a user account for logging into the management module and
server blades .............................................................................................. 3-39
Registering a group that is used for group authentication ............................... 3-41
Overview of configuring management modules and server blades for LDAP
linkage ........................................................................................................ 3-41
Displaying the settings for linking with an LDAP server ................................... 3-45
Setting the information to connect to an LDAP server ..................................... 3-45
Configuring the information related to the LDAP directory searches ................. 3-46
Setting the information to identify a group .................................................... 3-46
Initializing the LDAP linkage settings ............................................................. 3-47
Managing user account information by using RADIUS ........................................... 3-47
Overview .................................................................................................... 3-48
Supported RADIUS servers ........................................................................... 3-48
Settings for the RADIUS server ..................................................................... 3-48
Settings for the management module ........................................................... 3-48
RADIUS server connection confirmation ........................................................ 3-50
Specifying the RADIUS server authentication settings ..................................... 3-50
Registering the RADIUS server ..................................................................... 3-50
Checking the connection to the RADIUS server .............................................. 3-50

vii
Hitachi Compute Blade 2500 Series Management Module User Guide
Monitoring the operating status of the system unit by using an SNMP manager ...... 3-51
SNMP functionality ....................................................................................... 3-51
Specifications for SNMP functionality ............................................................. 3-52
Requirements for the SNMP functionality ....................................................... 3-53
General procedure for configuring the SNMP functionality ............................... 3-53
Getting the Management Information Base (MIB) file for managing a system
unit ............................................................................................................ 3-55
Configuring SNMP manager settings ............................................................. 3-55
Setting items necessary for SNMP agents and managers on management
module ....................................................................................................... 3-56
Configuring SNMP agent settings on the management module ........................ 3-58
Configuring SNMP manager settings on the management module ................... 3-59
Confirming that the SNMP manager can receive traps correctly ....................... 3-59
Notifying the status of the management module through email ............................. 3-60
Information that can be notified by email ...................................................... 3-60
Requirements for receiving email notification messages ................................. 3-61
Specifications for the email notification functionality ....................................... 3-61
Setting items for the email notification functionality ....................................... 3-63
Configuring email notification settings ........................................................... 3-64
Confirming that an email message can be sent properly ................................. 3-65
List of messages when sending an email message fails .................................. 3-66
Syslog transfer .................................................................................................. 3-68
Overview .................................................................................................... 3-68
Audit events to transfer ............................................................................... 3-68
Log format .................................................................................................. 3-68
Using Syslog transfer ................................................................................... 3-69
Editing the Syslog transfer settings of the management module ...................... 3-70
Editing the Syslog transfer settings of BMC .................................................... 3-70

4 Server Maintenance and Management by Management Modules ........... 4-1


Log data output by management modules and server blades .................................. 4-2
Logs viewable from management modules ...................................................... 4-2
Checking the system event log ....................................................................... 4-3
Checking the Optional Physical WWN change log ............................................. 4-3
Checking the Optional Physical MAC address change log .................................. 4-4
Checking the MAR log .................................................................................... 4-4
Checking the environment log ........................................................................ 4-5
Dump log ...................................................................................................... 4-5
Checking the dump log .................................................................................. 4-7
Notes on using the operation log and the audit log .......................................... 4-7
Specifications of the operation log and the audit log ........................................ 4-8
Operation log format ..................................................................................... 4-8
Format of the audit log ................................................................................ 4-11
Checking the operation log and the audit log ................................................. 4-13
List of operation log and audit log messages ................................................. 4-13
Updating management module firmware ............................................................. 4-26
Firmware that can be updated on management modules ................................ 4-26
Points to check before updating management module firmware ...................... 4-26
General procedure for updating the management module firmware and
dictionary .................................................................................................... 4-29
Obtaining the management module firmware and dictionary ........................... 4-31

viii
Hitachi Compute Blade 2500 Series Management Module User Guide
Checking the current versions of the management module firmware and
dictionary, and the system states (active and standby) of management
modules ...................................................................................................... 4-31
Updating the management module firmware and dictionary ............................ 4-32
Confirming that the management module firmware and dictionary were
updated ...................................................................................................... 4-34
Updating server blade firmware .......................................................................... 4-34
Points to check before updating server blade firmware ................................... 4-35
General procedure for updating server blade firmware ................................... 4-36
Obtaining server blade firmware ................................................................... 4-37
Checking the current version of server blade firmware ................................... 4-37
Updating server blade firmware .................................................................... 4-38
Confirming that server blade firmware was updated ....................................... 4-39
Restoring settings by management modules ........................................................ 4-40
Information that can be restored by management modules ............................ 4-40
Saving management module settings ............................................................ 4-40
Restoring management module settings ........................................................ 4-41
File management functionality ............................................................................ 4-41
About the file management functionality ....................................................... 4-41
Structure of the user directory for management modules ............................... 4-42
Uploading a file to a management module ..................................................... 4-43
Downloading a file from a management module ............................................ 4-43
Deleting a file from a management module ................................................... 4-44

5 Commands That Can Be Executed From the CLI Console ...................... 5-1
Command input format ........................................................................................ 5-3
Command conventions .................................................................................. 5-3
notes on using commands ............................................................................. 5-3
Commands to manage the server chassis .............................................................. 5-4
set chassis id ................................................................................................ 5-4
set chassis maintenance-mode ....................................................................... 5-5
set chassis usb validity ................................................................................... 5-6
set mac additional ......................................................................................... 5-7
set wwn additional ........................................................................................ 5-8
show chassis maintenance-mode .................................................................... 5-9
show chassis setting .................................................................................... 5-10
show chassis status ..................................................................................... 5-12
show chassis usb validity ............................................................................. 5-13
show mac additional .................................................................................... 5-14
show mac current ........................................................................................ 5-16
show mac original ....................................................................................... 5-18
show wwn additional ................................................................................... 5-20
show wwn current ....................................................................................... 5-23
show wwn original ....................................................................................... 5-25
shutdown chassis ........................................................................................ 5-26
Commands to manage server blades ................................................................... 5-27
assign blade hvm firmware ........................................................................... 5-27
bmc-reset blade .......................................................................................... 5-28
clear blade hvm ........................................................................................... 5-29
delete blade os-info ..................................................................................... 5-30
disconnect blade bmc session ....................................................................... 5-31
export blade efi setting ................................................................................ 5-31

ix
Hitachi Compute Blade 2500 Series Management Module User Guide
import blade efi setting ................................................................................ 5-32
init blade bmc setting .................................................................................. 5-33
init blade efi setting ..................................................................................... 5-34
poweroff blade ............................................................................................ 5-35
poweron blade ............................................................................................ 5-36
pre-configure blade ..................................................................................... 5-37
reset blade .................................................................................................. 5-38
set blade ac-recovery ................................................................................... 5-39
set blade bmc account ................................................................................. 5-40
set blade bmc time local .............................................................................. 5-42
set blade ipmi account ................................................................................. 5-43
set blade led ............................................................................................... 5-45
set blade maintenance-mode ........................................................................ 5-45
set blade lom license ................................................................................... 5-46
set blade mgmt-lan ...................................................................................... 5-47
set blade mgmt-v6 address .......................................................................... 5-48
set blade os-mode ....................................................................................... 5-50
set blade preconf ......................................................................................... 5-51
set blade smp construction ........................................................................... 5-52
set blade tpm license ................................................................................... 5-54
show blade bmc account .............................................................................. 5-54
show blade bmc session ............................................................................... 5-56
show blade bmc time local ........................................................................... 5-58
show blade firmware ................................................................................... 5-59
show blade hardware ................................................................................... 5-60
show blade hvm setting ............................................................................... 5-68
show blade ipmi account .............................................................................. 5-70
show blade maintenance-mode .................................................................... 5-71
show blade mgmt-lan .................................................................................. 5-72
show blade mgmt-v6 setting ........................................................................ 5-73
show blade os-info ...................................................................................... 5-75
show blade setting ...................................................................................... 5-76
show blade smp construction ....................................................................... 5-78
show blade status ........................................................................................ 5-80
update blade firmware bulk .......................................................................... 5-86
Commands to manage management modules ...................................................... 5-87
clear mgmt-module boot-disable ................................................................... 5-87
delete mgmt-module file .............................................................................. 5-88
restart mgmt-module ................................................................................... 5-89
set mgmt-module led ................................................................................... 5-90
set mgmt-module dns .................................................................................. 5-91
set mgmt-module maintenance-mode ........................................................... 5-92
set mgmt-module mgmt-lan ......................................................................... 5-93
set mgmt-module mgmt-v6 address .............................................................. 5-94
set mgmt-module int-lan .............................................................................. 5-95
set mgmt-module serial-port ........................................................................ 5-96
show mgmt-module firmware ....................................................................... 5-97
show mgmt-module hardware ...................................................................... 5-98
show mgmt-module int-lan ......................................................................... 5-102
show mgmt-module maintenance-mode ...................................................... 5-103
show mgmt-module mgmt-lan .................................................................... 5-104
show mgmt-module mgmt-v6 setting .......................................................... 5-105

x
Hitachi Compute Blade 2500 Series Management Module User Guide
show mgmt-module mnt-lan ....................................................................... 5-107
show mgmt-module serial-port ................................................................... 5-107
show mgmt-module status ......................................................................... 5-108
shutdown mgmt-module ............................................................................ 5-110
switch mgmt-module behavior .................................................................... 5-111
sync mgmt-module firmware ...................................................................... 5-111
sync mgmt-module fru ............................................................................... 5-112
sync mgmt-module int-lan .......................................................................... 5-113
update mgmt-module firmware ................................................................... 5-114
Commands to manage management LAN modules ............................................. 5-114
set mgmt-lan-module led ........................................................................... 5-114
show mgmt-lan-module hardware ............................................................... 5-115
show mgmt-lan-module status .................................................................... 5-117
Commands to manage I/O adapters .................................................................. 5-119
set iobd led ............................................................................................... 5-119
show iobd hardware .................................................................................. 5-120
show iobd status ....................................................................................... 5-122
Commands to manage switch modules .............................................................. 5-124
poweroff sw-module .................................................................................. 5-124
poweron sw-module .................................................................................. 5-125
set sw-module led ..................................................................................... 5-125
set sw-module maintenance-mode .............................................................. 5-126
set sw-module mgmt-lan ............................................................................ 5-127
set sw-module mgmt-v6 address ................................................................ 5-128
show sw-module firmware .......................................................................... 5-129
show sw-module hardware ......................................................................... 5-130
show sw-module maintenance-mode ........................................................... 5-132
show sw-module mgmt-lan ......................................................................... 5-133
show sw-module mgmt-v6 setting ............................................................... 5-134
show sw-module status .............................................................................. 5-135
Commands for power supply management ........................................................ 5-137
set power blade poweroff order .................................................................. 5-137
set power capping ..................................................................................... 5-138
set power dcmi-mode ................................................................................ 5-139
set power power-expansion ........................................................................ 5-140
set power ps-module ................................................................................. 5-141
show power ps-module .............................................................................. 5-142
show power setting .................................................................................... 5-143
show ps-module hardware ......................................................................... 5-145
show ps-module status .............................................................................. 5-148
Commands to manage fan modules ................................................................... 5-149
show fan-module status ............................................................................. 5-150
Commands for fan control module management ................................................ 5-151
show fan-control-module hardware ............................................................. 5-151
show fan-control-module status .................................................................. 5-152
Commands to manage the LCD touch console .................................................... 5-154
clear lcd password ..................................................................................... 5-154
set lcd validity ........................................................................................... 5-154
show lcd setting ........................................................................................ 5-155
Commands for user management ...................................................................... 5-156
add user account ....................................................................................... 5-156
add user role ............................................................................................. 5-158

xi
Hitachi Compute Blade 2500 Series Management Module User Guide
change-password user account ................................................................... 5-160
clear user ldap ........................................................................................... 5-162
delete user account ................................................................................... 5-162
delete user role ......................................................................................... 5-163
disconnect user session .............................................................................. 5-164
modify user account .................................................................................. 5-164
modify user role ........................................................................................ 5-167
set user ldap group .................................................................................... 5-169
set user ldap search ................................................................................... 5-172
set user ldap server ................................................................................... 5-173
set user password policy ............................................................................ 5-174
show user account ..................................................................................... 5-176
show user ldap .......................................................................................... 5-179
show user password policy ......................................................................... 5-181
show user role ........................................................................................... 5-183
show user session ...................................................................................... 5-187
Commands for time settings ............................................................................. 5-188
set time dst ............................................................................................... 5-188
set time local ............................................................................................. 5-190
set time timezone ...................................................................................... 5-191
show time dst ............................................................................................ 5-191
show time local ......................................................................................... 5-193
show time timezone ................................................................................... 5-194
Commands for language setting ........................................................................ 5-195
set language system .................................................................................. 5-195
show language system ............................................................................... 5-195
Commands for security settings ........................................................................ 5-196
set security strength .................................................................................. 5-196
set security tls mgmt-module ...................................................................... 5-198
show security setting ................................................................................. 5-199
Commands for remote access management ....................................................... 5-202
delete e-mail mgmt-lan address .................................................................. 5-202
delete hcsm manager ................................................................................. 5-202
delete hitrack manager .............................................................................. 5-203
disconnect hcsm session ............................................................................ 5-203
send e-mail latest mgmt-lan ....................................................................... 5-204
send e-mail select mgmt-lan ....................................................................... 5-205
send hcsm alert ......................................................................................... 5-205
set e-mail mgmt-lan address ...................................................................... 5-206
set e-mail mgmt-lan notification .................................................................. 5-207
set hcsm agent .......................................................................................... 5-209
set hcsm manager ..................................................................................... 5-209
set hitrack agent ........................................................................................ 5-211
set hitrack manager ................................................................................... 5-211
set remote-access protocol ftp .................................................................... 5-212
set remote-access protocol http .................................................................. 5-213
set remote-access protocol https ................................................................ 5-215
set remote-access protocol ssh ................................................................... 5-216
set remote-access protocol telnet ................................................................ 5-218
show e-mail mgmt-lan ............................................................................... 5-219
show hcsm setting ..................................................................................... 5-221
show hitrack setting ................................................................................... 5-223

xii
Hitachi Compute Blade 2500 Series Management Module User Guide
show remote-access protocol ftp ................................................................. 5-224
show remote-access protocol http ............................................................... 5-225
show remote-access protocol https ............................................................. 5-227
show remote-access protocol ssh ................................................................ 5-228
show remote-access protocol telnet ............................................................ 5-229
Commands for SNMP management ................................................................... 5-231
delete snmp manager ................................................................................ 5-231
export snmp mib ....................................................................................... 5-232
set snmp agent ......................................................................................... 5-232
set snmp manager ..................................................................................... 5-233
show snmp agent ...................................................................................... 5-235
show snmp manager .................................................................................. 5-236
show snmp mib ......................................................................................... 5-238
test snmp trap ........................................................................................... 5-238
Commands for LPAR manager management ...................................................... 5-239
delete hvm firmware .................................................................................. 5-239
show hvm firmware ................................................................................... 5-240
update hvm firmware ................................................................................. 5-240
Commands to collect log data ........................................................................... 5-241
export log failure ....................................................................................... 5-241
export log mar-log all ................................................................................. 5-242
export log mar-log latest ............................................................................ 5-242
show log environment ................................................................................ 5-243
show log error ........................................................................................... 5-244
show log hcsm-log ..................................................................................... 5-245
show log mac-edit ..................................................................................... 5-246
show log mar-log ....................................................................................... 5-247
show log power ......................................................................................... 5-248
show log sel .............................................................................................. 5-251
show log svpsts ......................................................................................... 5-253
show log wwn-edit ..................................................................................... 5-254
Commands to obtain backups ........................................................................... 5-255
restore blade bmc ...................................................................................... 5-255
restore blade efi ........................................................................................ 5-256
restore blade fc-hba ................................................................................... 5-256
restore factory ........................................................................................... 5-258
show blade bmc backup ............................................................................. 5-258
show blade efi backup ................................................................................ 5-259
show blade fc-hba backup .......................................................................... 5-260
Commands for console management ................................................................. 5-262
change console .......................................................................................... 5-263
exit ........................................................................................................... 5-264
set web-console function ............................................................................ 5-264
show web-console function ........................................................................ 5-265
Commands to identify parts .............................................................................. 5-266
show parts-db list ...................................................................................... 5-266
show parts-db unit ..................................................................................... 5-267
update parts-db ......................................................................................... 5-268

A Software license information .............................................................. A-1


Software license information ................................................................................ A-2

xiii
Hitachi Compute Blade 2500 Series Management Module User Guide
B HCSM alert log message .................................................................... B-1
HCSM alert log message ...................................................................................... B-2

Glossary

Index

xiv
Hitachi Compute Blade 2500 Series Management Module User Guide
Preface
This document describes how to use the Compute Blade 2500 series.
This preface includes the following information:
Notice: The use of Compute Blade 2500 series and all other Hitachi Data
Systems products is governed by the terms of your agreement(s) with Hitachi
Data Systems.

□ Intended Audience

□ Product Version

□ Release Notes

□ Document Organization

□ Referenced Documents

□ Document Conventions

□ Conventions for storage capacity values

□ Getting help

□ Comments

Preface xv
Hitachi Compute Blade 2500 Series Management Module User Guide
Intended Audience
This document is intended for the personnel who are involved in planning,
managing, and performing the tasks to prepare your site for Compute Blade
installation and to install the same.
This document assumes the following:
• The reader has a background in hardware installation of computer
systems.
• The reader is familiar with the location where the Compute Blade will be
installed, including knowledge of physical characteristics, power systems
and specifications, and environmental specifications.

Product Version
This document was revised due to the addition of restrictions on HCSM
linkage.

Release Notes
Read the release notes before installing and using this product. They may
contain requirements or restrictions that are not fully described in this
document or updates or corrections to this document.

Document Organization
The table below provides an overview of the contents and organization of this
document. Click the chapter title in the left column to go to that chapter. The
first page of each chapter provides links to the sections in that chapter.

Chapter Description

Chapter 1, Management Module Gives an overview of the management modules.


Overview

Chapter 2, Preparations for Using Describes the basic configuration for operating the
the Management Module management module.

Chapter 3, Efficient Management of Describes how to efficiently manage each system


Servers Using the Management unit using the functionality provided by the
Module management module.

Chapter 4, Server Maintenance and Explains how to maintain and manage a blade
Management by Management server by using management modules.
Modules

Chapter 5, Commands That Can Be Describes the commands that can be executed
Executed From the CLI Console from the CLI console and how to use them.

Appendix A, Software license Describes software license information of


information management module.

xvi Preface
Hitachi Compute Blade 2500 Series Management Module User Guide
Chapter Description

Appendix B, HCSM alert log message Describes HCSM alert log message.

Referenced Documents
• Hitachi Compute Blade 2500 Series Getting Started Guide,
MK-99CB2500003
• Hitachi Compute Blade 2500 Series UEFI Setup Guide, MK-99CB2500005
• Hitachi Compute Blade 2500 Series Logical partitioning manager User
Guide, MK-99CB2500006
• Hitachi Compute Blade 2500 Series MIB User Guide, MK-99CB2500007
• Hitachi Compute Blade Series SMASH and IPMI User's Guide,
MK-99COM144
• Hitachi Compute Blade Emulex Adapter User's Guide for Hardware,
MK-99COM104

Document Conventions
The term “Compute Blade” refers to all the models of the Compute Blade,
unless otherwise noted.
The Hitachi Virtualization Manager (HVM) name has been changed to Hitachi
logical partitioning manager (LPAR manager, or LP). If you are using HVM
based logical partitioning feature, substitute references to Hitachi logical
partitioning manager (LPAR manager, or LP) with HVM.
This document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, other than the window


title, including menus, menu options, buttons, fields,
and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual


text provided by the user or system. Example: copy
source-file target-file
Note: Angled brackets (< >) are also used to
indicate variables.
screen/code Indicates text that is displayed on screen or entered
by the user. Example: # pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual
text provided by the user or system. Example: #
pairdisplay -g <group>
Note: Italic font is also used to indicate variables.

[ ] square brackets Indicates optional values. Example: [ a | b ]


indicates that you can choose a, b, or nothing.

Preface xvii
Hitachi Compute Blade 2500 Series Management Module User Guide
Convention Description

{ } braces Indicates required or expected values. Example: { a


| b } indicates that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or


more options or arguments. Examples: [ a | b ]
indicates that you can choose a, b, or nothing. { a |
b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

Icon Meaning Description

WARNING This indicates the presence of a potential risk that


might cause death or severe injury.

CAUTION This indicates the presence of a potential risk that


might cause relatively mild or moderate injury.

NOTICE This indicates the presence of a potential risk that


might cause severe damage to the equipment
and/or damage to surrounding properties.

Note Calls attention to important or additional


information.

Tip This indicates advice on how to make the best use


of the equipment.

Conventions for storage capacity values


Physical storage capacity values (for example, disk drive capacity) are
calculated based on the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical storage capacity values (for example, logical device capacity) are
calculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

xviii Preface
Hitachi Compute Blade 2500 Series Management Module User Guide
Logical capacity unit Value

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Getting help
The Hitachi Data Systems customer support staff is available 24 hours a day,
seven days a week. If you need technical support, log on to the Hitachi Data
Systems Portal for contact information: https://portal.hds.com

Comments
Please send us your comments on this document: [email protected].
Include the document title and number including the revision level (for
example, -07), and refer to specific sections and paragraphs whenever
possible. All comments become the property of Hitachi Data Systems
Corporation.
Thank you!

Preface xix
Hitachi Compute Blade 2500 Series Management Module User Guide
xx Preface
Hitachi Compute Blade 2500 Series Management Module User Guide
1
Management Module Overview
This chapter gives an overview of the management modules.

□ Management modules

□ Settings for the consoles used for management module operations

Management Module Overview 1-1


Hitachi Compute Blade 2500 Series Management Module User Guide
Management modules
Management modules are hardware that manage an entire system unit by
monitoring the environment of the system unit and by controlling various
modules in the system unit, such as server blades, switch modules, power
supply modules, and fan modules. If the management modules detect a
system failure, they can notify the administrator via email, SNMP, or another
method.
This manual describes how to use management modules and other related
equipment to set up the system unit.
Management modules provide consoles for viewing the status of the system
unit and for configuring the system unit settings. To manage the CB 2500
system unit, use an external PC that is connected to the system unit via the
management LAN. This PC is called the system console. When you operate
the system unit through the system console, you can select a console type
depending on the intended use. The following three types of consoles are
provided:
• Web console
This feature allows you to operate the CB 2500 by using the GUI of the
system console browser.
• CLI console
This feature allows you to operate the CB 2500 by executing commands
in the system console.
• LCD touch console
This is an I/O device. By connecting the LCD touch console to a USB port
on the system unit, you can check the status of the system unit and
operate the system unit. By using the LCD touch console, you can set up
the system unit without using the system console.

Settings for the consoles used for management module


operations
This section describes the consoles that are used to operate the management
modules.

Logging in to the Web console


This section describes how to log in to the Web console.
To log in to the Web console:
1. Start the Web browser for the system console, and then enter the
following URL:
https://192.168.0.1/

Note: If you changed the IP address or port number for the management
modules, enter the URL that matches the changed settings.

1-2 Management Module Overview


Hitachi Compute Blade 2500 Series Management Module User Guide
2. Enter the user account and password for the system administrator.
The user account and password are set to their initial values (the values
at shipping time). Enter the following values:
¢ User account: "administrator"
¢ Password: "password"

Note: We strongly recommend that you change the password after


logging in.

Related topics
• Components of the Web console on page 1-3
• Dashboard of the Web console on page 1-5
• Setting up a user account on page 2-32

Components of the Web console


The following figure shows the components of the Web console.

Figure 1-1 Components of the Web console

Table 1-1 List of the components of the Web console

Area (Menu or
Item Description
Pane)

Menu File Save web console Downloads Web console logs.


log

Log out Logs out from the Web


console.

Management Module Overview 1-3


Hitachi Compute Blade 2500 Series Management Module User Guide
Area (Menu or
Item Description
Pane)

Action Dump Log Downloads logs from a


management module.

Edit login account Changes settings such as the


settings display language and the
password that the user
currently uses to log in.

Help User's Guide Displays the User's Guide.

About Displays information about


the management module
firmware version.

Maintenance mode Indicates that one or more


modules are in maintenance
mode.

Log out Logs out from the Web


console.

Global tab Dashboard tab When you log in to the Web


console, this window appears
first.
This tab gives an overview of
the system unit's operating
status and power
consumption, and displays a
list of events (log) that
occurred in the system unit.

Resources tab Manages installed modules


and resources.

Alerts tab Displays and downloads the


failure information and logs
that were recorded in the
system unit.

Administration tab Configures basic settings for


the system unit and settings
for connecting to other
systems.

Navigation area The left pane of the window displays the modules and functionality
that you can operate and configure in a tree format. From this tree,
select the module or functionality you want to configure.

General Tasks Dump Log Downloads logs from a


management module.

Edit login account settings Changes settings such as the


display language and the
password that the user
currently uses to log in.

Application area Displays details about the module or functionality that was selected
in the Navigation area, action items for operating the module or
functionality, and action buttons.

1-4 Management Module Overview


Hitachi Compute Blade 2500 Series Management Module User Guide
Dashboard of the Web console
When you log in to the Web console, the Dashboard appears first. The
Dashboard displays the operating status of the system unit, power
consumption, and a list of events that occurred in the system unit (the
system event log). The following figure shows the window components.

Figure 1-2 Dashboard

Chassis status
The operating status for each type of installed module is displayed. The table
below describes the possible operating statuses.
If a module is in a warning or failure state, check the details in the system
event log.

Table 1-2 Chassis status icons

Icon Description

No border The module installed in the applicable location is


running normally.

The module installed in the applicable location is


in a warning state.
Check the warning details in the system event
log.

The module installed in the applicable location is


in a failure state.
Check the failure details in the system event log.

The module installed in the applicable location is


being initialized, and the module type cannot be
recognized yet.

Management Module Overview 1-5


Hitachi Compute Blade 2500 Series Management Module User Guide
Icon Description

The module installed in the applicable location is


set to maintenance mode.

Table 1-3 Summary of chassis statuses (located to the right of the chassis
image)

Icon Description

Normal The modules are running properly.

One or more modules are in a warning state.


Warning
Check the warning details in the system event
log.

One or more modules are in a failure state.


Failure
Check the failure details in the system event log.

Power summary
Displays the input power value and the power consumption value.

Table 1-4 Power summary

Item Description

Input power (AC) Present input power Displays the amount of power (AC)
that is currently being supplied to the
system unit.

Accurate power control Displays the value calculated by


value (APC AC) converting the upper limit for APC
(Present) power consumption to AC power.

Power supply (DC) Maximum power supply Displays the maximum power supply
of the system unit.

Power consumption Present power Displays the total power consumption


(DC) consumption of the installed modules.

Power rating of chassis Displays the total rated power of the


installed modules.

Accurate power control Displays the upper limit for APC


value (APC) (Present) power consumption.

System event log


Displays the log of events that occurred in the system unit. A summary of the
number of unchecked failures is displayed in the upper part of the pane.
Note that this list displays only the 100 most recent events. To view all
events recorded in the system unit, click the Show SELs button to open the
system event log window. Click the Dump Log button to download logs from
a management module.

1-6 Management Module Overview


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 1-5 Occurred event

Item Description

Check Indicates whether the event is already checked.


• Blank: This event is already checked. Events that are
already checked are excluded from the number of
unchecked events that is displayed as a summary.
• ! : This event is not checked. Events that are not yet
checked are included in the number of unchecked events
that is displayed as a summary.

Level There are the four event levels: normal, caution, warning,
and failure. The event level is indicated as follows:
• Blank: Indicates an event recorded when the user's
operation or the system unit's behavior was normal. A
blank is also displayed for caution-level events.

: Indicates an event requiring user caution occurred,
such as a communication failure or a configuration error.

: Indicates an event recorded when a failure occurs
on a module but the module can continue operating.
Check the details of the warning and remove the cause of
the problem.

: Indicates an event recorded when a failure occurred
on a module and the module can no longer operate.
Check the details of the failure and take the appropriate
action.

Date and Time Displays the date and time when the event occurred.

Module Displays the module where the event occurred.

Slot Displays the number of the slot where the module is installed.

Message Displays a general description of the event.

Note: Press the save button within two minutes after the dialog for selecting
a location for a downloaded file to be saved opens on the browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the message
"Internet Explorer cannot download [IP address] - [File name]. Server
returned invalid or unrecognized response." is returned or the file is
incorrectly saved as a smaller size.
In such a case, download the file again.

Related topics
• Controlling power consumption by using the power control functionality on
page 2-88
• Checking the system event log on page 4-3

Management Module Overview 1-7


Hitachi Compute Blade 2500 Series Management Module User Guide
Logging in to the CLI console
This section describes how to log in to the CLI console.

Tasks to complete in advance


Install terminal software for the system console in advance. For some OSs
(including Linux), terminal software is already installed as the default settings
of the OS. The terminal software must provide the following functionality:
• Use of Telnet (for Telnet connections)
• Use of SSH version2 (for SSH connections)

Note:
• Input and output characters might be limited depending on specifications
of the terminal software. For the type of the terminal to be emulated, set
the same type as that of the terminal for the OS to be used.
• Depending on terminal settings, Japanese output might not be possible.
To log in to the CLI console:
1. Start a terminal emulator (such as Telnet) for the system console.
2. For LAN connections, connect to the IP address (192.168.0.1) for
management modules via SSH or Telnet.
For serial connections, specify the COM port number for the system
console to which the management module is connected.

Note: To use the CLI console in a serial connection, first expand the
window width so that each entered command can fit on a single line. If a
command exceeds a single line, the command lines and execution results
might not be displayed correctly in the command prompt.
If a connection is successfully established, the Login prompt appears.
3. In the Login prompt, enter the user account for the system administrator
and then press the [Enter] key.
The initial value (the value at shipping time) of the user account is
"administrator".
4. Enter the password and then press the [Enter] key.
The initial value (the value at shipping time) of the password is
"password".

Note: If password expiration dates are set to be managed, you might not
be able to log in if the password expires. To be able to log in again, see
Setting a password expiration date on page 2-33 to update the
password.
Note that you need the account privilege to update the password.
• If you specify the setting to deny login attempts when the password
expires, the following message appears and the user cannot login
when a user who has the expired password attempts to log in:
Your password has expired.

1-8 Management Module Overview


Hitachi Compute Blade 2500 Series Management Module User Guide
• If you specify the setting that requires the password to be updated
when the password expires, the message below appears when a user
who has the expired password attempts to log in. Enter the current
and new passwords by following the displayed message. The
management module changes the password to enable the user to log
in.
Your password has expired. Please change the password.
Old password: (Enter the current password.)
New password: (Enter the new password.)
Retype password: (Enter the new password again.)
If you incorrectly enter the current password three times, the
connection with the CLI console is closed.

Note: We strongly recommend that you change the password after


logging in.

After you log in, the initial window appears.

Related topics
• CLI console initial window on page 1-9
• Logging out from the CLI console on page 1-10
• Setting up a user account on page 2-32
• Setting a password expiration date on page 2-33

CLI console initial window


This section describes the items that are displayed in the initial window after
you log in.
The following is an example of the initial window:
Compute Blade CB 2500 Management Module
ALL RIGHTS RESERVED, COPYRIGHT (C), 2014, HITACHI, LTD.
Chassis ID : chassis#2
Firmware Revision : A0100-A-1234

The initial window displays the following items:


Chassis ID
The chassis ID
Firmware Revision
The version of the management module firmware
$
The CLI prompt For each account, you can specify either of the following
formats for the CLI prompt:
¢ cid(n)$: cid is the chassis ID, and n is the slot number of the
management module.
¢ $: Initial setting (the setting at shipping time)

Management Module Overview 1-9


Hitachi Compute Blade 2500 Series Management Module User Guide
When the password expiration date of a logged-in user approaches, the initial
window displays the following message that prompts the user to change their
password:
Your password will expire soon. Please change password before
expiration.

If there is a user whose password has expired when a user who has the
account privilege logs in, the initial window displays the following warning
message:
There is the account that the password has expired.

If there is a user whose password expiration date is approaching when a user


who has the account privilege logs in, the initial window displays the following
warning message:
There is the account that the password will expire soon.

Related topics
• Logging in to the CLI console on page 1-8
• Setting the chassis ID to identify the server chassis on page 2-28
• Updating management module firmware on page 4-26

Logging out from the CLI console


To log out from the CLI console, enter exit in the CLI prompt and then press
the Enter key.

Tip: If you set a session timeout value, you will be logged out automatically
after a certain period of time during which no operations are performed.
When you log in, the time registered for the account is applied as the non-
operation timeout value. You can change the non-operation timeout value for
each account.
The initial setting (the setting at shipping time) of the non-operation timeout
period is 10 minutes.

Related topics
• exit on page 5-264

LCD touch console specifications and functionality


The following figure shows the external view of the LCD touch console.

1-10 Management Module Overview


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 1-3 External view of the LCD touch console
The specifications for the LCD touch console are as follows:

Table 1-6 Hardware specifications for the LCD touch console

Item Specifications

USB cable length 1.5 m

LCD touch console operation unit Display resolution: 320 x 240 dots
Number of output colors: 18-bit color
Power: Supplied from the server chassis
Internal memory: No data storage area that the
user can use.

A USB flash drive is required to use some functionality. When you use the
LCD touch console, prepare a USB flash drive. The following table shows USB
flash drives that can be used.

Table 1-7 USB flash drives that can be used in LCD touch console
functionality

Item Specifications

Capacity A maximum of 32 GB

Format FAT 32

USB interface 1.1 and 2.0

Related topics
• Connecting the LCD touch console to the server chassis on page 1-11

Connecting the LCD touch console to the server chassis


To connect the LCD touch console to the server chassis, connect the USB
cable of the LCD touch console to a USB connection port on the front of a
management module. Note that "management module" here means the
active management module. The management module has two USB

Management Module Overview 1-11


Hitachi Compute Blade 2500 Series Management Module User Guide
connection ports. You can use the LCD touch console regardless of which USB
connection port is connected.

Note:
• If you connect the LCD touch console to a USB port that is disabled, the
LCD touch console displays "Please wait...", and the screen does not
change. Connect the LCD touch console to a USB port that is enabled.
• If you disable a USB port to which the LCD touch console is connected,
the LCD touch console might operate differently from normal. To disable
USB ports, first remove the connected LCD touch console.

Tip: You cannot use a USB hub or a USB switching device to connect the LCD
touch console and the server chassis.

Related topics
• LCD touch console specifications and functionality on page 1-10
• Disabling a USB port on page 2-23

1-12 Management Module Overview


Hitachi Compute Blade 2500 Series Management Module User Guide
2
Preparations for Using the Management
Module
This chapter describes the basic configuration for operating the management
module.

□ Language settings

□ Time settings

□ Strengthening the security of management modules and BMC

□ Strengthening security by using digital certificates

□ Setting the chassis ID to identify the server chassis

□ User management using management modules

□ Network settings

□ Operating identification lamps of each module

□ Power supply operation for a server blade

□ Efficient operation of server blades by SMP configurations

□ Operating server blades by using the remote console

□ Operating server blades by using the OS console

□ Setting server blades, switch modules, and Hitachi Fibre Channel adapter

Preparations for Using the Management Module 2-1


Hitachi Compute Blade 2500 Series Management Module User Guide
□ Setting WWNs and MAC addresses

□ Controlling power consumption by using the power control functionality

□ Specifying all settings for a server chassis by using an import file

2-2 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Language settings
You can select either English or Japanese as the language to use to operate
the system unit. Note that, if the language settings of the account are
configured, the account settings have priority over the language settings of
the management module.
You can set the language to use to operate the system unit from the Web
console or the CLI console.
To set the language for the system unit from the Web console:
1. From the tree view in the Administration tab, select Language.
2. Click the Edit button.
3. Change the language settings, and then log out of the Web console.
The change will take effect when you next log in.
To set the language for the system unit from the CLI console:
1. You can use the show language system command to check the current
language settings. To change the language settings, execute the set
language system command.

Related topics
• show language system on page 5-195
• set language system on page 5-195

Time settings
This section explains how to set the time of the system unit.

Time settings that can be specified in the management module


You can set up the date, time, time zone, and daylight saving time (DST) in
the management module. You can also synchronize the time of the
management module with the time of a server configured outside the system
unit or the time of modules in the system unit.
Set the correct time in the management module before starting system unit
operation.

Table 2-1 Time information that can be set in the management module

LCD touch
Operation Web console CLI console
console

Setting the time for the Y Y Y


management module

Preparations for Using the Management Module 2-3


Hitachi Compute Blade 2500 Series Management Module User Guide
LCD touch
Operation Web console CLI console
console

Synchronizing the time of the Y -- --


management module with the
time of an NTP server

Synchronizing the time of the Y -- --


management module with the
time of other modules

Note that you can collectively set the time zone and DST by using the import
functionality during initial setup.

Related topics
• Time settings to enable DST on page 2-4
• Setting the time of the management module on page 2-5
• Synchronizing the time of the management module with the time of an
NTP server on page 2-6
• Synchronizing the time of the management module with the time of other
modules on page 2-7
• Specifying all settings for a server chassis by using an import file on page
2-111

Time settings to enable DST


You can enable DST in the management module. The following describes the
meaning of the DST start and end dates when DST is enabled from each
console.
From each console of the management module, you can specify the condition
for the DST start and end dates by combining [Month], [Date], [Day of the
week], and [Time]. For [Month] and [Time], the displayed months and times
are the DST start and end dates.
• When [Date] is specified:
DST starts and ends on the specified month and date. In this condition,
the specification for [Day of the week] is disabled.
• When [First day on or after the specified date] is specified:
DST starts and ends on the first specified day of the week on or after the
specified date. For example, when [First day on or after the specified
date] is Sunday and [Date] is 8, the date is the first Sunday on or after
8th of the month, that is, the second Sunday.
• When [Last day on or before the specified date] is specified:
DST starts and ends at the first specified day of the week on or before the
specified date. For example, when [Last day on or before the specified
date] is Sunday, [Month] is 3, and [Date] is 24, the date is the first
Sunday on or before the 24th of March, that is, the second Sunday from
the end of the month.

2-4 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• When [Last day in the month] is specified:
DST starts and ends at the first specified day of the week on or before the
specified date.
For example, when [Last day on or before the specified date] is Sunday,
[Month] is 3, and [Date] is 24, the date is the first Sunday on or before
the 24th of March, that is, the second Sunday from the end of the month.
In this condition, the specification for [Date] is disabled.

Related topics
• Time settings that can be specified in the management module on page
2-3
• Setting the time of the management module on page 2-5

Setting the time of the management module


To set time information of the system unit, use the Web console, the CLI
console, or the LCD touch console. You can set up the date, time, time zone,
and DST.
To set the time of the management module from the Web console:
1. From the tree view in the Administration tab, select Date and Time.
2. In the Local time tab or the Time zone tab, click the Edit button.
3. Specify the necessary items, and perform the processing.
To set the time of the management module from the CLI console:
1. Execute the following commands to match your purpose.

Table 2-2 Commands used for setting a time

Operation item Command

Displaying the time settings show time local

Changing the time settings set time local

Displaying the time zone setting show time timezone

Changing the time zone setting set time timezone

Displaying the daylight saving time setting show time dst

Changing the daylight saving time setting set time dst

To set the time of the management module from the LCD touch
console:
1. From the System settings menu, touch the Time settings button.
2. The Time settings window appears.

Preparations for Using the Management Module 2-5


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Time settings that can be specified in the management module on page
2-3
• show time local on page 5-193
• set time local on page 5-190
• show time timezone on page 5-194
• set time timezone on page 5-191
• show time dst on page 5-191
• set time dst on page 5-188

Synchronizing the time of the management module with the time of


an NTP server
If you install an NTP server outside the system unit, you can synchronize the
time of the management module with the time of the NTP server.

Figure 2-1 NTP server linkage


You can install a maximum of four NTP servers, and include plural servers in
a redundant configuration in preparation for a failure. If you enable the time
synchronization using an NTP server, synchronization is performed
immediately after the system unit starts, and then continuously every 30
minutes.
In the initial settings (the settings at shipping time) of the system unit,
linking with an NTP server is disabled.
To enable linkage with an NTP server from the Web console:
1. From the tree view in the Administration tab, select Date and Time.
2. In the NTP tab, click the Edit button.
3. Specify the necessary items, and perform the processing.

2-6 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Time settings that can be specified in the management module on page
2-3

Synchronizing the time of the management module with the time of


other modules
You can synchronize the time of BMC and LPAR manager by using the time of
the management module as a reference.

Figure 2-2 Management module time synchronization


In the BMC and LPAR manager time settings, Synchronizing from
management module must be selected. If time synchronization is enabled,
synchronization is performed immediately after BMC and LPAR manager are
booted, and then continuously every 15 minutes.
To set the time of BMC from the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. From the Edit menu in the BMC tab, select BMC time.
3. Set the BMC time adjustment method to Using NTP servers.

Note: For CB520X B1/B2, BMC time adjustment method is only set to
Synchronize time to the management module using NTP.

Related topics
• Time settings that can be specified in the management module on page
2-3

Preparations for Using the Management Module 2-7


Hitachi Compute Blade 2500 Series Management Module User Guide
Strengthening the security of management modules and
BMC
This section explains how to strengthen the security of management modules
and BMC.

Services provided by management modules and their security


settings
The following table describes the functionality provided to secure the
management modules.
(A): Supported protocol
(B): Default port number
(C): Ciphertext or cleartext
(D): Service disabled
(E): Restriction on the connection source IP address
(F): Changing port number
(G): Available if the security strength is set to [High]

Table 2-3 Functionality provided by management modules

Functionality (A) (B) (C) (D) (E) (F) (G)

Web console HTTP 80 Cleartext Y1 Y2 Y --

HTTPS3 443 Ciphertext Y1 Y2 Y Y

CLI console Telnet 23 Cleartext Y1 Y2 -- --

SSH4 22 Ciphertext Y1 Y2 -- Y

Sending and receiving files FTP 20, 21 Cleartext Y1 Y2 -- --

SFTP 22 Ciphertext Y1 Y2 -- Y

Email notification SMTP 25 Select Y5 -- Y Y


(StartTLS) cleartext or
ciphertext

SNMP functionality (polling) SNMP (v1/ 161 Cleartext Y6 Y Y --


v2c)

SNMP (v3) 161 Select Y6 Y Y Y


cleartext or
ciphertext

SNMP functionality (trapping) SNMP (v1/ 162 Cleartext Y5 Y Y --


v2c)

SNMP (v3) 162 Select Y5 Y Y Y


cleartext or
ciphertext

2-8 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Functionality (A) (B) (C) (D) (E) (F) (G)

LDAP linkage LDAPS 636 Ciphertext Y5 -- Y Y

Time synchronization NTP 123 Cleartext Y5 -- -- Y

HCSM linkage (command) HTTPS 443 Ciphertext Y7 Y Y Y

HCSM linkage (alert) Hitachi 22611 Ciphertext Y5 Y Y Y


protocol

HA monitor linkage Hitachi --8 Cleartext Y9 -- Y Y


protocol

Hi-Track HTTPS 443 Ciphertext Y7 Y Y Y

Syslog transfer SYSLOG 514 Select Y5 -- Y Y


cleartext or
ciphertext

Legend:
Y: Can be set
--: Cannot be set
Notes:
1. Connections from all IP addresses are not allowed. The port is open.
Connections to both IPv4 networks and IPv6 networks become impossible.
2. This setting is necessary for IPv4 networks and IPv6 networks.
3. A certificate error (warning) is displayed whenever an IPv6 address is used for HTTPS access.
4. Connection using version 1 is not supported.
5. Disabling the functionality also disables the service. No communication is performed with respect to
the port.
6. Disabling the functionality also disables the service. The port is open.
7. Disabling the functionality also disables the service. You can also disable the service by disabling
HTTPS. The port is open.
8. By default, no port number is set. The port number is set when HA monitor is used.
9. Disabling the functionality also disables the service. The port is blocked.

Services provided by BMC and their security settings


The following table describes the functionality provided to secure the BMC.
(A):Supported protocol
(B):Default port number
(C):Ciphertext or cleartext
(D):Service disabled
(E):Restriction on the connection source IP address
(F):Changing port number
(G):Available if the security strength is set to [High]

Preparations for Using the Management Module 2-9


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-4 Functionality provided by BMC

Functionality (A) (B) (C) (D) (E) (F) (G)

Server blade Web console HTTPS 443 Ciphertext Y Y -- Y

IPMI over LAN IPMI v1.5 623 Cleartext Y Y -- --

IPMI v2.0 623 Ciphertext Y Y -- Y1

Remote console Hitachi 5001 Ciphertext Y Y Y Y


protocol

Syslog transfer SYSLOG 514 Select Y -- Y Y


cleartext
or
ciphertext

Legend:
Y: Can be set
--: Cannot be set
Note:
1. Connection is available only when Cipher suite ID is 3 and both Username and Password are not
blank.

Security strength for management modules and BMC


The management interfaces of management modules and BMC have the
following two security strengths: [Default] and [High]. The initial setting (the
setting at shipping time) is [High]. You can increase security in the following
ways by setting the security strength to [High]:
• If encrypted communication is available, cleartext communication is not
allowed.
• For encrypted communication, only encryption algorithms with high
security strength are used.

Table 2-5 Setting security strength for management modules and BMC

Operation Web console CLI console LCD touch console

Checking the Y Y --
security strength
settings for
management
modules and BMC

Changing the Y Y --
security strength
settings for
management
modules and BMC

2-10 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: If the security strength setting for the management module is [High],
use Internet Explorer to connect to the Web console of the management
module.
To use Firefox to connect to the Web console of the management module, set
the security strength for the management module to [Default].

Related topics
• Points to check before setting the security strength for management
modules and BMC on page 2-11
• Differences in usable functionality depending on the security strength
settings on page 2-11
• Setting the security strength for management modules and BMC on page
2-15

Points to check before setting the security strength for management


modules and BMC
• If you set the security strength for the management module to [High]
when the HTTPS service is disabled, the Web console and HCSM become
unusable. Be careful when changing the settings.
• You can change the security strength for the management module when
all of the following conditions are met:
¢ All server blades have been initialized.
¢ All server blades are powered off.
¢ All management modules have been initialized.
• If you change the security strength settings for the management module,
all management modules will be restarted. The changed settings are
applied at restart.
If you change the security strength settings for BMC, the changed
settings are instantly applied without restarting.
• If the security strength for management modules is set to [High], you
cannot use management tools that connect to the management modules
by using SNMP v1/v2c.

Related topics
• Security strength for management modules and BMC on page 2-10

Differences in usable functionality depending on the security


strength settings
The table below describes the relationship between the security strength for
management modules and server blades and the usable functionality. In the
table, Y indicates available functionality, and N indicates unavailable
functionality.

Preparations for Using the Management Module 2-11


Hitachi Compute Blade 2500 Series Management Module User Guide
TLS
Management module Server blade
Cipher suite Security strength Security strength
Default High Default High

TLS_RSA_WITH_AES_128_CBC_SHA Y N Y N

TLS_RSA_WITH_AES_256_CBC_SHA Y N N N

TLS_DHE_RSA_WITH_AES_128_CBC Y N N N
_SHA

TLS_DHE_DSS_WITH_AES_128_CB Y N N N
C_SHA

TLS_EMPTY_RENEGOTIATION_INFO Y Y N N
_SCSV

TLS_RSA_WITH_AES_128_CBC_SHA Y Y Y Y
256

TLS_RSA_WITH_AES_256_CBC_SHA Y Y Y Y
256

TLS_DHE_RSA_WITH_AES_256_GC Y Y N N
M_SHA384

TLS_DHE_DSS_WITH_AES_256_GC Y Y2 N N
M_SHA384

TLS_DHE_RSA_WITH_AES_128_CBC Y Y N N
_SHA256

TLS_DHE_DSS_WITH_AES_128_CB Y Y2 N N
C_SHA256

TLS_DHE_RSA_WITH_AES_256_CBC Y Y N N
_SHA256

TLS_DHE_DSS_WITH_AES_256_CB Y Y N N
C_SHA256

TLS_DHE_RSA_WITH_AES_256_SHA Y N N N

TLS_DHE_DSS_WITH_AES_256_SH Y N N N
A

TLS_RSA_WITH_AES_256_GCM_SH Y Y N N
A384

TLS_RSA_WITH_AES_128_GCM_SH Y Y N N
A256

TLS_DHE_RSA_WITH_3DES_EDE_C Y1 N N N
BC_SHA

TLS_DHE_DSS_WITH_3DES_EDE_C Y1 N Y N
BC_SHA

TLS_DHE_RSA_WITH_AES_128_GC Y Y N N
M_SHA256

2-12 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Management module Server blade
Cipher suite Security strength Security strength
Default High Default High

TLS_DHE_DSS_WITH_AES_128_GC Y Y2 N N
M_SHA256

TLS_RSA_WITH_3DES_EDE_CBC_S Y1 N Y N
HA

TLS_RSA_WITH_RC4_128_MD5 Y N N N

TLS_RSA_WITH_RC4_128_SHA Y N N N

TLS_DHE_DSS_WITH_RC4_128_SH Y2 N N N
A

Note:
1. Syslog transfer does not support the cipher suite.
2. Only syslog transfer supports the cipher suite.

Management module Server blade


Server certificate (public-key
Security strength Security strength
algorithm)
Default High Default High

RSA1024 N N N N

RSA2048 Y Y Y Y

RSA4096 N N N N

DSA1024 N N N N

Management module Server blade


Server certificate (signature
Security strength Security strength
algorithm)
Default High Default High

SHA-1 verification Y Y N N

SHA-1 creation Y N N N

SHA-256 verification Y Y Y Y

SHA-256 creation N Y Y Y

SHA-384 verification N N N N

SHA-384 creation N N N N

Preparations for Using the Management Module 2-13


Hitachi Compute Blade 2500 Series Management Module User Guide
SSH
Management module Server blade
Host-key algorithm Security strength Security strength
Default High Default High

RSA1024 N N N N

RSA2048 Y Y Y Y

RSA4096 N N N N

DSA1024 Y N Y N

Management module Server blade


Key exchange algorithm Security strength Security strength
Default High Default High

diffie-hellman-group1-sha1 Y Y Y Y

diffie-hellman-group14-sha1 Y Y Y Y

diffie-hellman-group-exchange-sha1 Y Y Y Y

diffie-hellman-group-exchange- Y Y Y Y
sha256

Management module Server blade


Encryption algorithm Security strength Security strength
Default High Default High

3des N N N N

3des-cbc Y Y Y Y

aes128-cbc Y Y Y Y

aes192-cbc Y Y Y Y

aes256-cbc Y Y Y Y

aes128-ctr Y Y Y Y

aes192-ctr Y Y Y Y

aes256-ctr Y Y Y Y

blowfish-cbc Y N Y N

cast128-cbc Y N Y N

arcfour Y N N N

arcfour128 Y N N N

arcfour256 Y N N N

[email protected] Y N N N

2-14 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Management module Server blade
Message authentication
Security strength Security strength
algorithm
Default High Default High

hmac-md5 N N N N

hmac-sha1 Y Y Y Y

hmac-ripemd160 N N N N

[email protected] N N N N

[email protected] Y N N N

hmac-sha1-96 Y Y Y Y

hmac-md5-96 Y Y N N

hmac-sha2-256 Y Y Y Y

hmac-sha2-512 Y Y Y Y

SNMP v3
Management module Server blade
Encryption algorithm Security strength Security strength
Default High Default High

None Y N SNMP is not supported.

DES Y N

AES128 Y Y

Management module Server blade


Authentication algorithm Security strength Security strength
Default High Default High

None Y N SNMP is not supported.

MD5 Y N

SHA1 Y Y

Related topics
• Security strength for management modules and BMC on page 2-10

Setting the security strength for management modules and BMC


To set the security strength for management modules and BMC, use the Web
console or the CLI console.

Preparations for Using the Management Module 2-15


Hitachi Compute Blade 2500 Series Management Module User Guide
To set the security strength for management modules and BMC from
the Web console:
1. In the Resources tab, from the tree view under Systems, select
Security strength setting.
2. In the Security strength tab, click the Edit button.
3. Change the security strength settings.
To set the security strength for management modules and BMC from
the CLI console:
1. To check the current security strength, execute the show security
setting command. To change the security strength, execute the set
security strength command.

Related topics
• Security strength for management modules and BMC on page 2-10
• Points to check before setting the security strength for management
modules and BMC on page 2-11
• show security setting on page 5-199
• set security strength on page 5-196

TLS version settings


TLS is used for encrypted communications at management interfaces for
management modules and BMC. You can enable or disable each TLS version.
You can change the setting for the TLS versions below. In the initial settings
(the settings at shipping time), this setting is enabled for all versions. You
cannot disable all of the TLS versions.
• TLS 1.0
• TLS 1.1
• TLS 1.2
The following table shows which management module consoles can be used
in each operation.

Table 2-6 TLS version settings

Operation Web console CLI console LCD touch console

Configuring the TLS Y Y --


version settings for
management
modules

Configuring the TLS Y -- --


version settings for
BMC

2-16 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Configuring TLS version settings on page 2-17

Configuring TLS version settings


To configure the TLS version settings for management modules and BMC, use
the Web console or the CLI console. From the CLI console, you can configure
the TLS version settings for management modules only.

Note:
• If the security strength for management modules and BMC is set to
[High], only TLS 1.2 is enabled among TLS versions for management
modules, and other versions are disabled. For BMC, SMASH (WS-
Management) uses TLS 1.0.
• If the security strength is set to [High] or [Default] and communication is
enabled only with TLS 1.2, connections to HCSM that do not support TLS
1.2 are not available. For details about the procedure required to use
HCSM, see the HCSM instruction manuals.
• The TLS version settings for BMC are not included in the configuration
information of server blades inherited from N+M cold standby. When
configuring N+M cold standby, set the same BMC security strength to
both the active and standby server blades.
To configure the TLS version settings for management modules and
BMC from the Web console:
1. In the Resources tab, from the tree view under Systems, select
Security strength setting.
2. In the TLS version tab, click the Edit button.
3. Change the TLS settings.
To configure the TLS version settings for management modules and
BMC from the CLI console:
1. To check the current setting of each TLS version, execute the show
security setting command. To change the TLS version settings,
execute the set security tls mgmt-module command.

Related topics
• TLS version settings on page 2-16
• show security setting on page 5-199
• set security tls mgmt-module on page 5-198

IP address restriction settings for management module services


For Telnet, FTP, SSH/SFTP, HTTP, and HTTPS services, you can specify the
following settings per service.
• Enable and disable the service.

Preparations for Using the Management Module 2-17


Hitachi Compute Blade 2500 Series Management Module User Guide
• Set connectable IP addresses.
If you set connectable IP addresses, connections from IP addresses other
than the set IP addresses are refused.
You can set connectable IP addresses for each type of network: IPv4
networks and IPv6 networks.
You can specify a range of connectable IP addresses (in network address
format) for each IPv4 network service and for each IPv6 network service.
• Change the port number (for HTTP and HTTPS only).
Note that you can collectively set the allowance of Telnet, SSH/SFTP, FTP,
HTTP, and HTTPS connections by using the import functionality during initial
setup.
You can change service settings from each console of the management
module.

Table 2-7 IP address restriction settings for management module services

Operation Web console CLI console LCD touch console

Editing Telnet Y Y Y
connection settings

Editing FTP Y Y Y
connection settings

Editing SSH/SFTP Y Y Y
connection settings

Editing HTTP Y Y Y
connection settings

Editing HTTPS Y Y Y
connection settings

Related topics
• Editing the Telnet connection settings on page 2-18
• Editing the FTP connection settings on page 2-19
• Editing the SSH/SFTP connection settings on page 2-20
• Editing the HTTP connection settings on page 2-20
• Editing the HTTPS connection settings on page 2-21
• Specifying all settings for a server chassis by using an import file on page
2-111

Editing the Telnet connection settings


To edit the Telnet connection settings, use the Web console, the CLI console,
or the LCD touch console.
To edit the Telnet connection settings from the Web console:
1. From the tree view in the Administration tab, select Service.

2-18 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
2. In the Telnet tab, click the Edit button.
3. Set the necessary items, and perform the processing.
To edit the Telnet connection settings from the CLI console:
1. To check the current Telnet connection settings, execute the show
remote-access protocol telnet command. To edit the settings,
execute the set remote-access protocol telnet command.

To edit the Telnet connection settings from the LCD touch console:
1. From the System settings menu, touch the Service settings button.
2. The Service settings window appears.

Related topics
• IP address restriction settings for management module services on page
2-17
• show remote-access protocol telnet on page 5-229
• set remote-access protocol telnet on page 5-218

Editing the FTP connection settings


To edit the FTP connection settings, use the Web console, the CLI console, or
the LCD touch console.
To edit the FTP connection settings from the Web console:
1. From the tree view in the Administration tab, select Service.
2. In the FTP tab, click the Edit button.
3. Set the necessary items, and perform the processing.
To edit the FTP connection settings from the CLI console:
1. To check the current FTP connection settings, execute the show remote-
access protocol ftp command. To edit the settings, execute the set
remote-access protocol ftp command.

To edit the FTP connection settings from the LCD touch console:
1. From the System settings menu, touch the Service settings button.
2. The Service settings window appears.

Related topics
• IP address restriction settings for management module services on page
2-17
• show remote-access protocol ftp on page 5-224
• set remote-access protocol ftp on page 5-212

Preparations for Using the Management Module 2-19


Hitachi Compute Blade 2500 Series Management Module User Guide
Editing the SSH/SFTP connection settings
To edit the SSH/SFTP connection settings, use the Web console, the CLI
console, or the LCD touch console.
To edit the SSH/SFTP connection settings from the Web console:
1. From the tree view in the Administration tab, select Service.
2. In the SSH/SFTP tab, click the Edit button.
3. Set the necessary items, and perform the processing.
To edit the SSH/SFTP connection settings from the CLI console:
1. To check the current SSH/SFTP connection settings, execute the show
remote-access protocol ssh command. To edit the settings, execute
the set remote-access protocol ssh command.

To edit the SSH/SFTP connection settings from the LCD touch


console:
1. From the System settings menu, touch the Service settings button.
2. The Service settings window appears.

Related topics
• IP address restriction settings for management module services on page
2-17
• show remote-access protocol ssh on page 5-228
• set remote-access protocol ssh on page 5-216

Editing the HTTP connection settings


To edit the HTTP connection settings, use the Web console, the CLI console,
or the LCD touch console.
To edit the HTTP connection settings from the Web console:
1. From the tree view in the Administration tab, select Service.
2. In the HTTP tab, click the Edit button.
3. Set the necessary items, and perform the processing.
To edit the HTTP connection settings from the CLI console:
1. To check the current HTTP connection settings, execute the show
remote-access protocol http command. To edit the settings, execute
the set remote-access protocol http command.

To edit the HTTP connection settings from the LCD touch console:
1. From the System settings menu, touch the Service settings button.
2. The Service settings window appears.

2-20 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• IP address restriction settings for management module services on page
2-17
• show remote-access protocol http on page 5-225
• set remote-access protocol http on page 5-213

Editing the HTTPS connection settings


To edit the HTTPS connection settings, use the Web console, the CLI console,
or the LCD touch console.
To edit the HTTPS connection settings from the Web console:
1. From the tree view in the Administration tab, select Service.
2. In the HTTPS tab, click the Edit button.
3. Set the necessary items, and perform the processing.
To edit the HTTPS connection settings from the CLI console:
1. To check the current HTTPS connection settings, execute the show
remote-access protocol https command. To edit the settings, execute
the set remote-access protocol https command.

To edit the HTTPS connection settings from the LCD touch console:
1. From the System settings menu, touch the Service settings button.
2. The Service settings window appears.

Related topics
• IP address restriction settings for management module services on page
2-17
• show remote-access protocol https on page 5-227
• set remote-access protocol https on page 5-215

Login banner settings


As a method for warning users who attempt unauthorized access, the system
administrator can set a warning banner to appear before the display of the
login window of the Web console or the login prompt (login:) of the CLI
console. In the initial settings (the settings at shipping time), this
functionality is disabled. To enable the functionality, you need to set a text
message to be displayed in a login banner.
From the management module, you can enable or disable a login banner, and
set a text message to be displayed in a login banner. You can use the
following consoles.

Preparations for Using the Management Module 2-21


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-8 Login banner settings

Operation Web console CLI console LCD touch console

Setting the display Y -- --


of a login banner

Related topics
• Setting the display of a login banner on page 2-22

Setting the display of a login banner


To disable or enable the display of a login banner and set a text message to
be displayed in the login banner, use the Web console.
The following characters can be set for a login banner:
• Maximum number of characters in the message: 1,599 (approximately 80
characters x 20 lines)
• Available character types: alphanumeric characters, symbols, space
characters (ASCII character codes from 0x20 to 0x7e), and line feed
characters (LF)
However, the percent sign (%), whose ASCII character code is 0x25, and
the back slash (\), whose ASCII character code is 0x5c, are excluded.
Japanese characters including one-byte Kana characters cannot be used.

Tip:
• If you disable the display of a login banner, the login banner is not
displayed but the text content that was set is retained. If you re-enable
the display of a login banner, the text content that was set can be
displayed.
• A login banner is backed up when you save management module settings.
Therefore, if you recover settings, the login banner is also recovered to
the state when it was saved.
To set the display of a login banner from the Web console:
1. From the tree view in the Administration tab, select Login banner.
Whether the display of a text message is enabled or disabled is displayed,
as is the body of the text message.
2. Click the Edit button.
3. Set the necessary items, and perform the processing.

Related topics
• Login banner settings on page 2-21

2-22 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Disabling the Web console functionality
To prevent unauthorized access, you can disable operations from the Web
console. You can enable or disable the Web console independently for both
the case where the Web console is connected from the management LAN
ports (MGMT1 or MGMT2) and the case where the Web console is connected
from the maintenance LAN port (MAINT) used by maintenance personnel. In
the initial settings (the settings at shipping time), the Web console is
enabled.

Note: For usual operation, do not disable the Web console operations
performed from the maintenance port. If you do so, you will not be able to
perform maintenance work.
To check whether the Web console is enabled, execute the show web-
console function command from the CLI console. To toggle the Web
console setting between enabled and disabled, execute the show web-
console function command from the CLI console.

Related topics
• Functionality available for management interfaces of each module on
page 2-37
• Management network on page 2-37
• show web-console function on page 5-265
• set web-console function on page 5-264

Disabling a USB port


To prevent unauthorized use of USB devices, you can disable USB ports for
the management module. You can also specify the settings for each USB port.
You can use the following consoles.

Table 2-9 Settings to disable or enable a USB port

Operation Web console CLI console LCD touch console

Disabling or enabling Y Y --
a USB port

Related topics
• Disabling or enabling a USB port on page 2-23

Disabling or enabling a USB port


To disable or enable a USB port, you can use the Web console or the CLI
console.

Preparations for Using the Management Module 2-23


Hitachi Compute Blade 2500 Series Management Module User Guide
To disable or enable a USB port from the Web console:
1. In the Resources tab, from the tree view under Modules, select
Management Modules.
2. From the Action pull-down menu, click Edit ManagementModule USB
Configuration.
To disable or enable a USB port from the CLI console:
1. To check the USB port settings, execute the show chassis usb validity
command. To disable or enable a USB port, execute the set chassis usb
validity command.

Note:
• If you disable a USB port to which a USB device is connected, the USB
device might operate differently from normal. To disable USB ports, first
remove the connected USB devices.
• If you connect the LCD touch console to a USB port that is disabled, the
LCD touch console displays "Please wait...", and the screen does not
change. Connect the LCD touch console to a USB port that is enabled.

Tip: If you disable USB ports, you cannot use functionality that uses USB
devices, such as operating the system unit from the LCD touch console and
specifying all settings for a server chassis by using an import file.

Related topics
• Disabling a USB port on page 2-23
• show chassis usb validity on page 5-13
• set chassis usb validity on page 5-6

Strengthening security by using digital certificates


This section explains how to use digital certificates to strengthen security
from the Web console.

Digital certificates
You can achieve the functionality below by using digital certificates. You can
use self-signed certificates and certificates signed by a certificate authority.
• Authenticating the management module
When you use the Web Console, the management module provides the
digital certificate. You can verify the management module by checking the
CA that has signed the digital certificate.
• Encrypting communications between the Web browser and the
management module
You can encrypt communication when using the Web console to prevent
communication from being tapped or tampered with.

2-24 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Authenticating BMC
When you use the server blade Web console or remote console, BMC
provides the digital certificate. You can verify BMC by checking the CA
that has signed the digital certificate.
• Encrypting communications between the Web browser and BMC, or the
remote console and BMC
You can encrypt communication when using the Web console or remote
console of the server blade to prevent communication from being tapped
or tampered with.

Related topics
• Specifications for using digital certificates on page 2-25
• Using self-signed certificates on page 2-26
• Using digital certificates signed by certificate authority on page 2-27

Specifications for using digital certificates


The following table lists the specifications when using digital certificates on
the Web console.

Table 2-10 Digital certificate specifications for the Web console

Item Description

Public key algorithm, bit length RSA (2048 bits)

Format of certificates that can be PEM


imported

Format of certificates when downloaded PEM

Format of certificates that can be created PEM

Information about the subject that can be See the table below.
included in the certificate

Table 2-11 Information about the subject that can be included in the
certificate

Subject Description

Country (C) Shows two letters for a country.

State or province (ST) Shows the name of a state or province.


This item can be no more than 30 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Locality (L) Shows the name of a city or region.


This item can be no more than 50 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Preparations for Using the Management Module 2-25


Hitachi Compute Blade 2500 Series Management Module User Guide
Subject Description

Organization (O) Shows the name of an organization (company).


This item can be no more than 60 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Organizational unit Shows the name of an organizational unit.


(OU) This item can be no more than 60 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Common name (CN) This item must be entered.


Shows a common name (a domain name when the management
module is connected).
This item can be no more than 60 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . : [ ]

Email address Shows an email address.


Displayable ASCII characters are available.

DN qualifier Shows a DN qualifier.


This item can be no more than 60 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Surname Shows a surname.


This item can be no more than 60 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Given name Shows a given name.


This item can be no more than 60 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Initials Shows initials.


This item can be no more than 20 characters long, and can
contain alphanumeric characters, spaces, and the following
symbols: ' ( ) + , - . / : = ?

Related topics
• Digital certificates on page 2-24
• Using self-signed certificates on page 2-26
• Using digital certificates signed by certificate authority on page 2-27

Using self-signed certificates


To use a self-signed certificate, perform the following procedure.
1. Download the digital certificate to a client PC.

2-26 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
A self-signed digital certificate is already created when the management
module and server blade are shipped. From the Web browser, download
the digital certificate to your client PC.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.
In such a case, download the file again.
2. Import the downloaded digital certificate to the Web browser.
Import the digital certificate downloaded in step 1 to the Web browser of
the client PC. For details about how to import the digital certificate to the
web browser, see the Web browser Help.
3. Connect to the Web console by using HTTPS.
You can use the encryption functionality of communication paths.

Related topics
• Digital certificates on page 2-24
• Specifications for using digital certificates on page 2-25

Using digital certificates signed by certificate authority


To use a digital certificate signed by a certificate authority, perform the
following procedure.
1. Create a certificate signing request (CSR) from the Web console.
To create a CSR for the management module, from the tree view in the
Administration tab, click Certificate and then the Create CSR button.
To create a CSR for BMC, in the Resources tab, from the tree view under
Modules, select the target server blade, and then in the BMC tab, click
Edit and then Edit certificate. From the pull-down menu in the BMC
server certificate settings dialog box, select Create CSR.
2. Submit the created CSR to a certificate authority to obtain the signed
digital certificate.
3. Import the signed digital certificate from the Web console.
To create a CSR for the management module, from the tree view in the
Administration tab, click Certificate and then the Import server
certificate button.
To import a BMC certificate, in the Resources tab, from the tree view
under Modules, select the target server blade, and then in the BMC tab,
click Edit and then Edit certificate.

Preparations for Using the Management Module 2-27


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: Use a character encoding other than UTF-8 for a digital certificate
to be imported to the management module. If you use UTF-8 encoding, a
part of the digital certificate information might not be displayed after the
digital certificate is imported.
Make sure that the displayed digital certificate information matches the
obtained digital certificate information before importing. If you fail to
import the digital certificate, perform the procedure again from CSR
creation.
4. Connect to the Web console by using HTTPS
You can use the encryption functionality of communication paths. To
enable the management module authentication functionality, the root
certificate for the CA must have been imported to the Web browser of the
client PC. For details about the confirmation method, see the Web
browser Help or ask the CA.

Related topics
• Digital certificates on page 2-24
• Specifications for using digital certificates on page 2-25

Setting the chassis ID to identify the server chassis


This section describes chassis IDs that are set for server chassis.

Chassis ID
You can register an identifier called a chassis ID in a server chassis. Chassis
IDs are used to identify equipment when information about the equipment
connected from the Web console, CLI console, and LCD touch console is
displayed.
You can set the chassis ID using no more than 20 characters. In the initial
settings (the settings at shipping time), a part of the server chassis serial
number is set for the chassis ID.
The table below describes the consoles used when you set the chassis ID
from the management module.

Tip: You can also set the chassis ID from HCSM.

Table 2-12 Chassis ID settings

Operation Web console CLI console LCD touch console

Setting the chassis Y Y --


ID

2-28 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Setting the chassis ID on page 2-29

Setting the chassis ID


To set the chassis ID, use the Web console or the CLI console.
To set the chassis ID from the Web console:
1. In the Resources tab, from the tree view under Modules, select
Chassis.
2. In the Settings tab, click the Chassis ID button.
To set the chassis ID from the CLI console:
1. To check the current chassis ID setting, execute the show chassis
setting command. To set the chassis ID, execute the set chassis id
command.

Related topics
• Chassis ID on page 2-28
• show chassis setting on page 5-10
• set chassis id on page 5-4

User management using management modules


This section explains how to manage user information by using the
management module.

Management module roles


On the management module consoles, you can customize operation privileges
for each user. For example, to fit the system administrator role, you can
divide users into those who have the privileges to operate server blades and
those who have the privileges to operate server chassis.
The following table describes the privileges that can be assigned to the roles.

Table 2-13 Privileges assignable to roles

Privilege name Description

Server blade Can operate and configure server blades.


Each server blade slot has its own privileges.

Switch module Can operate and configure switch modules.


Each switch module slot has its privileges.

Network Can configure networks.

Chassis Can operate and configure server chassis.

Preparations for Using the Management Module 2-29


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege name Description

Account Can add or delete accounts and roles.

In addition to the above privileges, you can add the following settings:
• To permit only viewing of the content, grant the "readonly" attribute to
the role.
• To deny remote accesses to server blades (accesses by using a remote
console or an OS console), grant the "Disable Remote Console launch"
attribute to the role.
In addition, server chassis have a built-in role (Administrators) to which all
privileges are granted. You cannot change the privileges of the Administrator
role.

Tip: When server blades are in an SMP configuration, assign the privileges for
all server blades constituting the SMP configuration.

The following table describes the consoles used when you set a role from the
management module.

Table 2-14 Role settings

Operation Web console CLI console LCD touch console

Setting a role Y Y --

Related topics
• Setting a role on page 2-30
• Operating server blades by using the remote console on page 2-56
• Operating server blades by using the OS console on page 2-57

Setting a role
To set (create, modify, or delete) a role, use the Web console or the CLI
console. You can register up to 16 roles other than the built-in role
(Administrator).
To set a role from the Web console:
1. From the tree view in the Administration tab, click Users and Roles.
2. From the Action pull-down menu, click Show and edit role settings.
3. Set the role to be granted to each role.
To set a role from the CLI console:
1. Execute the following commands to match your purpose.

2-30 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-15 Commands used for setting a role

Operation item Command

Displaying roles show user role

Adding a role add user role

Modifying a role modify user role

Deleting a role delete user role

Related topics
• show user role on page 5-183
• add user role on page 5-158
• modify user role on page 5-167
• delete user role on page 5-163

Management module user accounts


On the management module, you need an account to perform the following
operations.
• Logging in to the Web console and the CLI console
The requirement for each account to enter a password can prevent
unauthorized login to the Web console or the CLI console. Multiple
accounts can be created so that each user uses a different account.
• Sending and receiving files by using FTP
You can use FTP to send files to, and receive files from, a user directory.
To use the functionality to send and receive files, you need to enter an
account and password.

Tip: You do not need an account to log in to the LCD touch console because a
PIN is set to prevent unauthorized login.

The following table describes the consoles used when you set the user
management account from the management module.

Table 2-16 User account settings

Operation Web console CLI console LCD touch console

Setting a user account Y Y --

Related topics
• Initial account settings (the settings at shipping time) on page 2-32
• Setting up a user account on page 2-32
• Setting a PIN for the LCD touch console on page 2-36

Preparations for Using the Management Module 2-31


Hitachi Compute Blade 2500 Series Management Module User Guide
Initial account settings (the settings at shipping time)
The following table describes the account that is registered in the
management module in the initial settings (the settings at shipping time).

Table 2-17 Initial settings (the settings at shipping time)

Item Setting value

User name administrator

Status Enabled

Role Administrators

Language Follows the system settings

CLI console prompt chassis-ID(slot-number-for-management-


module)$

Session timeout 10 minutes

Password password

Setting up a user account


To set (create, modify, or delete) a role, use the Web console or the CLI
console. You can register up to 16 user accounts.

Tip:
• Set the account name for the user account, using no more than 31
characters. The name can contain alphanumeric characters and the
following symbols: - . _ The account name must start with an
alphanumeric character.
• Set the password for the user account, using no more than 31 ASCII
characters.

Information you need to check in advance


• Initial settings (the settings at shipping time)
To set a user account from the Web console:
1. From the tree view in the Administration tab, click Users and Roles.
2. Click the Create, Delete, or Edit button.
A dialog box corresponding to the clicked button appears.
3. Specify the necessary items, and perform the processing.

Tip: From the Edit login account settings button under [General Tasks] in
the lower left of the window, you can edit the account of the currently
logged-in user.
To set a user account from the CLI console:
1. Execute the following commands to match your purpose.

2-32 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-18 Commands used for user account settings

Operation item Command

Displaying user accounts show user account

Adding a user account add user account

Modifying a user account modify user account

Deleting a user account delete user account

Changing the password for a user account change-password user account

Related topics
• Management module user accounts on page 2-31
• Initial account settings (the settings at shipping time) on page 2-32
• show user account on page 5-176
• add user account on page 5-156
• modify user account on page 5-164
• delete user account on page 5-162
• change-password user account on page 5-160

Setting a password expiration date


You can set a expiration date for passwords used to log in to the Web console
or the CLI console of the management module.
For the management module, if you set the period (the number of days) for
which passwords are considered to be valid, you can manage the password
expiration dates.
If you create an account or change the password, the expiration date is set
again for the password of that account.
The expiration date is calculated and set as follows: the-day-when-the-
operation-is-performed + the-period-for-which-the-password-is-considered-
to-be-valid. Passwords are valid until when the number of days left is 0.

Tip: If [Password expiration date] is 0, the password is considered valid for


that day (until the system time changes to the next day).

To display or set information related to management of the password


expiration dates, the account privilege is required.
You can set one of the following for the operation when the password of an
account expires:
• Require the password to be updated.
• Deny login attempts.

Preparations for Using the Management Module 2-33


Hitachi Compute Blade 2500 Series Management Module User Guide
If you specify the setting that requires update of the password, the
management module displays a window for updating the password to allow
login when a user requires logging in to the console by using the expired
password. Then, the user with that account can change the password.
If you specify the setting to deny login attempts, users cannot log in to the
console of the management module. The administrator needs to change the
expired password. In this case, if you specify the setting for the user to
change the expired password and there is a new login request, the
management module displays a window to update the password only once,
and then allows the user to login. Then, the user of that account can change
the password.
If the password of an account that has the account privilege expires, the
operation is the same as the setting that requires the password to be
updated, regardless of the setting.
This functionality is available for accounts registered in the management
module. When linking with an LDAP server, the management module does
not manage the password expiration dates for user accounts in the LDAP
directory.
In the initial settings (when shipped), management of the password
expiration dates is disabled.

Table 2-19 Initial settings (settings at shipping time) for the management
of the password expiration dates

Item Setting value

Management of password expiration Disable


date

Password expiry period (day) -----

Change expired password Disable

Tip: To manage the password expiration dates, set a value in the range from
1 to 365 (days) for [Password expiry period (day)].

The following table describes the consoles used when you set a password
expiration date from the management module.

Table 2-20 Settings for password expiration dates

Operation Web console CLI console LCD touch console

Setting a password Y Y --
expiration date

Related topics
• Management module user accounts on page 2-31
• Setting up a user account on page 2-32

2-34 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Setting a password expiration date on page 2-35

Setting a password expiration date


You can set a password expiration date by using the Web console or the CLI
console.
To set management of the password expiration dates from the Web
console:
1. From the tree view in the Administration tab, click Users and Roles.
2. Select the Password Policy tab.
3. Click the Edit button, and set the required item.
To set the management of the password expiration dates from the
CLI console:
1. To display the settings for the management of the password expiration
dates, execute the show user password policy command. To set
management of the password expiration dates, execute the show user
password policy command.

Related topics
• Management module user accounts on page 2-31
• Setting up a user account on page 2-32
• Setting a password expiration date on page 2-33
• show user password policy on page 5-181
• set user password policy on page 5-174

User management using an LCD touch console


Account authentication is not performed for the LCD touch console. To
prevent inappropriate use of the console, you can manage users by using
either of the following methods:
• Set a personal identification number (PIN) for the LCD touch console.
• Disable the LCD touch console functionality.
If you forget the PIN or you want to disable PIN authentication, you can
initialize the PIN.
The following table describes the consoles used when you change the user
management settings for the LCD touch console from the management
module.

Preparations for Using the Management Module 2-35


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-21 User management using an LCD touch console

Operation Web console CLI console LCD touch console

Setting a PIN for the -- -- Y


LCD touch console

Initializing a PIN for Y Y --


the LCD touch
console

Disabling the LCD -- Y --


touch console
functionality

Related topics
• Setting a PIN for the LCD touch console on page 2-36
• Initializing a PIN for the LCD touch console on page 2-36
• Disabling the LCD touch console functionality on page 2-37

Setting a PIN for the LCD touch console


The PIN settings for an LCD touch console are set for the entire system unit.
Therefore, enter the same PIN even when using a different LCD touch
console. You can set a password consisting of a four-digit number. In the
initial settings (the settings at shipping time), PIN authentication is disabled.
To set a PIN for the LCD touch console:
1. From the System settings menu, touch the PIN settings button.
2. The PIN settings window for the LCD touch console appears.

Note: The window does not display the PIN code, so keep your PIN in a
secure place. If you forget the PIN, you can initialize it from the Web console.
If you initialize the PIN, PIN authentication is disabled.

Related topics
• User management using an LCD touch console on page 2-35
• Initializing a PIN for the LCD touch console on page 2-36

Initializing a PIN for the LCD touch console


To initialize a PIN for the LCD touch console, use the Web console.
To initialize a PIN for the LCD touch console from the Web console:
1. From the tree view in the Administration tab, click Users and Roles.
2. From the Actions menu, click Initialize LCD PIN.

2-36 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To initialize a PIN for the LCD touch console from the CLI console:
1. Execute the clear lcd password command.

Related topics
• User management using an LCD touch console on page 2-35
• Setting a PIN for the LCD touch console on page 2-36
• clear lcd password on page 5-154

Disabling the LCD touch console functionality


To disable the LCD touch console functionality, use the CLI console. If the
functionality is disabled, the LCD touch console becomes inoperable even if it
is connected to a system unit.
In the initial settings (the settings at shipping time), the LCD touch console
functionality is enabled.
To disable the LCD touch console functionality from the CLI console:
1. To check the current settings, execute the show lcd setting command.
To enable or disable the functionality, execute the set lcd validity
command.

Related topics
• User management using an LCD touch console on page 2-35
• show lcd setting on page 5-155
• set lcd validity on page 5-154

Network settings
This section describes networks for operating the system unit.

Functionality available for management interfaces of each module


Each management module, server blade, and switch module installed in the
system unit has its own management interface.
By connecting the management interface of each module to the network, you
can establish communication with consoles and management software such
as HCSM and SNMP.
Note that, when two management modules are installed in the system unit,
only the management interface of the active management module is active.

Management network
The management network is configured to enable operations from the
management module to each module.

Preparations for Using the Management Module 2-37


Hitachi Compute Blade 2500 Series Management Module User Guide
L2SW, which is embedded in the management module, and management
interfaces of each module connect to each other in the system unit. You can
establish a connection to the management interfaces of each module by using
cables to connect external output ports (MGMT1 and MGMT2) of the
management module to the ports of each module.
The following figure shows an outline of the management network.

Figure 2-3 Management network

Note:
• Do not connect a cable to the MAINT port. This port is used exclusively for
maintenance work by maintenance personnel.
• The ports of the standby management module are usually closed. These
ports are opened if a failure occurs on the management module or Link
Fault Tolerance is enabled.

Internal network
Apart from the management network, the system unit has an internal
network within the unit. The internal network is used for the following
purposes:
• Controlling communication between the management modules
• Controlling communication between the management module and server
blades

2-38 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Controlling communication between the management module and switch
modules
The system unit uses a 24-bit mask network (subnet mask: 255.255.255.0)
for the internal network. For the IP address/subnet mask,
192.168.253.0/255.255.255.0 is set in the initial settings (the settings at
shipping time) of the system unit. The IP address used in the internal
network cannot be used outside the system unit. If you want to use the
network IP address specified with 192.168.253.0/255.255.255.0 outside the
system unit, change the internal network settings.
The following table describes the consoles used when you change the internal
network settings from the management module.

Table 2-22 Internal network settings

Operation Web console CLI console LCD touch console

Changing the IP address of Y Y --


the internal network

Related topics
• Changing the IP address of the internal network on page 2-39

Changing the IP address of the internal network


To change the IP address of the internal network, use the Web console.

Operations that you need to perform in advance


• Stop the server blade operation.
If you change the IP address while server blades are in operation, a
failure event that might occur during restart of the management module
might not be detected.
To change the IP address of the internal network from the Web
console:
1. In the Resources tab, from the tree view under Systems, select
Network, and then Internal LAN.
2. Click the Edit button, and set the IP address.
Changing the IP address restarts the management module.
To change the IP address of the internal network from the CLI
console:
1. Execute the set mgmt-module int-lan command.
If you change the IP address, the management module is restarted.

Related topics
• Internal network on page 2-38

Preparations for Using the Management Module 2-39


Hitachi Compute Blade 2500 Series Management Module User Guide
• set mgmt-module int-lan on page 5-95
• show mgmt-module int-lan on page 5-102

IP address settings
You can configure the network for management interfaces of each module
from the management module.
By using functionality that supports IPv6 networks, you can set IPv4
addresses and IPv6 addresses.
In this manual, the term "IP addresses" indicates both IPv4 addresses and
IPv6 addresses.
The following table describes the initial settings (the settings at shipping
time) of IP addresses. IPv6 addresses are disabled.

Table 2-23 IP address (IPv4) settings at shipping time

Default
Module IP address Subnet mask
gateway

Management 192.168.0.1 255.255.255.0 0.0.0.0


module

Server blades 1 to 0.0.0.0 0.0.0.0 0.0.0.0


15

Switch module 1 0.0.0.0 0.0.0.0 0.0.0.0

Switch module 2 0.0.0.0 0.0.0.0 0.0.0.0

From the management module, you can change the IP address settings for
each module. Note that you can collectively set the IP address of the
management module, server blades, and switch modules by using the import
functionality during initial setup.

Table 2-24 IP address settings

Operation Web console CLI console LCD touch console

Setting the IP address of Y Y Y


the management module

Setting the IP address of a Y Y --


server blade

Setting the IP address of a Y Y --


switch module

Setting DNS servers Y Y --

Related topics
• IP address setting items on page 2-41

2-40 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Setting the IP addresses of management modules, server blades, and
switch modules on page 2-42
• Specifying all settings for a server chassis by using an import file on page
2-111

IP address setting items


To connect to the management interface of each module, set the items
below.
If you want to use IPv6 networks, set both an IPv4 address and IPv6
address.

Item Window

IPv4 networks IPv4 address Set the IPv4 address, subnet mask, and default
gateway that are used for connecting to the
Subnet mask management interface for each module over IPv4
Default networks.
gateway

IPv6 networks Static address Set the IPv4 address, prefix, and default gateway that
• IPv6 are used for connecting to the management interface
address for each module over IPv6 networks.

• Prefix Specify IPv6 addresses in the format defined in RFC


4291.
• Default
gateway For details on how to set up IPv6 addresses, access the
following URL:
https://www.iana.org/assignments/ipv6-address-
space/ipv6-address-space.xhtml

Stateless Enable or disable Stateless Address Autoconfiguration


address (SLAAC).
If SLAAC is enabled, IPv6 addresses are generated
automatically based on the prefixes and interface IDs
distributed by a router (MAC addresses), and set for the
management interfaces of modules.
You can set Enable or disable Stateless Address
Autoconfiguration for management modules and server
blades.

Note:
• Even if you connect to management modules over an IPv6 network, you
cannot delete the IPv4 address.
• If you change the IPv4 address or IPv6 address that is being connected to
a management module via the Web console or the CLI console, the IPv4
or IPv6 connection is closed.
• To use HA monitor and LPAR manager, use an IPv4 network.
• To connect to server blades over IPv6 networks, the firmware of the
server blades must support IPv6 networks.

Preparations for Using the Management Module 2-41


Hitachi Compute Blade 2500 Series Management Module User Guide
• To use Stateless Address Autoconfiguration on server blades, the server
blade firmware must support the functionality.
• To connect management modules over IPv6 networks, set static
addresses. You cannot enable only stateless addresses.
• To connect HCSM and management modules over IPv6 networks, set
static addresses and disable stateless addresses.
• To connect to a management module via an IPv6 network, set global
unicast addresses for the IPv6 addresses. For default gateways, set the
link local address or global unicast address of the router that exists in the
same link as the management modules. We recommend setting the link
local address.

Related topics
• Setting the IP addresses of management modules, server blades, and
switch modules on page 2-42

Setting the IP addresses of management modules, server blades, and


switch modules
To set the IP addresses of management modules, server blades, and switch
modules, use the Web console, the CLI console, or the LCD touch console.

Tip: You do not need to set the IP addresses of the non-primary server
blades in an SMP configuration if those blades do not use IPMI over LAN,
SMASH-CLP, or WS-Management. Use the IP addresses of the initial settings
(the settings at shipping time).
To set the IP addresses of management modules, server blades, and
switch modules, from the Web console:
1. In the Resources tab, from the tree view under Systems, select
Network, and then Management LAN.
2. In the IP Address (v4) tab or IP Address (v6) tab, click the Edit
button.
3. Change the settings of the necessary items.
To set the IP addresses of management modules, server blades, and
switch modules, from the CLI console:
1. Execute the following commands to match your purpose.
You cannot set IPv6 stateless addresses from the CLI console.

Table 2-25 Commands used for setting the IP addresses of management


modules, server blades, and switch modules

Operation item Command

Checking the IPv4 address of the show mgmt-module mgmt-lan


management module

2-42 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation item Command

Changing the IPv4 address of the set mgmt-module mgmt-lan


management module

Checking the IPv6 address of the show mgmt-module mgmt-v6 setting


management module

Changing the IPv6 address of the set mgmt-module mgmt-v6 address


management module

Checking the IPv4 address of a server blade show blade mgmt-lan

Changing the IPv4 address of a server blade set blade mgmt-lan

Checking the IPv6 address of a server blade show blade mgmt-v6 setting

Changing the IPv6 address of a server blade set blade mgmt-v6 address

Checking the IPv4 address of a switch show sw-module mgmt-lan


module

Changing the IPv4 address of a switch set sw-module mgmt-lan


module

Checking the IPv6 address of a switch show sw-module mgmt-v6 setting


module

Changing the IPv6 address of a switch set sw-module mgmt-v6 address


module

To set the IP address of the management module from the LCD touch
console:
1. From the System settings menu, touch the Network settings button.
2. The Network settings window appears.
3. Change the settings of the necessary items.
Only the IPv4 address of the management module can be set from the LCD
touch console. To set other IP addresses from the LCD touch console, set up
import files.

Related topics
• IP address settings on page 2-40
• Specifying all settings for a server chassis by using an import file on page
2-111
• show mgmt-module mgmt-lan on page 5-104
• set mgmt-module mgmt-lan on page 5-93
• show mgmt-module mgmt-v6 setting on page 5-105
• set mgmt-module mgmt-v6 address on page 5-94
• show blade mgmt-lan on page 5-72
• set blade mgmt-lan on page 5-47
• show blade mgmt-v6 setting on page 5-73
• set blade mgmt-v6 address on page 5-48

Preparations for Using the Management Module 2-43


Hitachi Compute Blade 2500 Series Management Module User Guide
• show sw-module mgmt-lan on page 5-133
• set sw-module mgmt-lan on page 5-127
• show sw-module mgmt-v6 setting on page 5-134
• set sw-module mgmt-v6 address on page 5-128

Setting DNS servers


You can register a maximum of three DNS servers for IPv4 addresses and
IPv6 addresses, respectively. You can specify whether DNS servers for IPv4
addresses are to be accessed first or DNS servers for IPv6 addresses are to
be accessed first, when name resolutions are performed on DNS servers.
A maximum of three DNS servers are used in total from DNS servers for IPv4
addresses and for IPv6 addresses. Either DNS servers for IPv4 addresses or
DNS servers for IPv6 addresses are preferentially used based on the priority
setting. If three servers are used, an access attempt will not be made to DNS
servers.
If four or more DNS servers are registered, DNS servers that have the fourth
or lower priority are not used.
Example:
The following example shows the usage sequence in the following
configuration:
¢ Setting values
Priority setting: IPv6
DNS server 0 for IPv4 addresses: 192.168.0.200
DNS server 1 for IPv4 addresses: 192.168.0.201
DNS server 2 for IPv4 addresses: 0.0.0.0 (not configured)
DNS server 0 for IPv6 addresses: 2001:2000::100:100
DNS server 1 for IPv6 addresses: 2001:2000::100:101
DNS server 2 for IPv6 addresses: 0.0.0.0 (not configured)
¢ Usage sequence
a. 2001:2000::100:100
b. 2001:2000::100:101
c. 192.168.0.200
Note: The IP address 192.168.0.201 is the fourth priority, and the
server is not used.
To set DNS servers, use the Web console or the CLI console.
To set DNS servers from the Web console:
1. In the Resources tab, from the tree view under Systems, select
Network, and then Management LAN.
2. In the DNS tab, click the Edit button.
3. Change the settings of the necessary items.

2-44 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To set DNS servers from the CLI console:
1. Execute the following commands to match your purpose.

Table 2-26 Commands used for setting DNS servers

Operation item Command

Check DNS servers used for IPv4 addresses. show mgmt-module mgmt-lan

Set DNS servers used for IPv4 addresses. set mgmt-module dns

Check DNS servers used for IPv6 addresses. show mgmt-module mgmt-v6 setting

Set DNS servers used for IPv4 addresses. set mgmt-module dns

Check the priorities of DNS servers used for show mgmt-module mgmt-v6 setting
IPv4 addresses or DNS servers used for IPv6
addresses.

Set the priorities of DNS servers used for set mgmt-module dns
IPv4 addresses and DNS servers used for
IPv6 addresses.

Related topics
• show mgmt-module mgmt-lan on page 5-104
• set mgmt-module dns on page 5-91
• show mgmt-module mgmt-v6 setting on page 5-105

Improving failure handling by configuring management modules in a


redundant configuration
In the initial configuration (the configuration at shipping time), the CB 2500
has two management modules installed. If management modules are
configured in a redundant configuration, system unit operations can continue
even if a failure occurs in one of the management modules.
If management modules are configured in a redundant configuration, only the
management interfaces of the active management module are enabled and
the ports of the standby management module are closed.
If a failure occurs in the active management module, the standby
management module becomes the active management module to continue
operations. The ports of the new active management module are opened, and
the management interfaces are enabled. The IP addresses of the
management interface of the new active management module are assigned
as follows:

Address type Address allocation

IPv4 address The IP addresses of the previously active management


modules are inherited. To connect to the management
IPv6 static address interfaces of management modules, you do not need
to be aware of which management module is active.

Preparations for Using the Management Module 2-45


Hitachi Compute Blade 2500 Series Management Module User Guide
Address type Address allocation

IPv6 stateless address IPv6 addresses are generated automatically based on


the prefixes and interface IDs distributed by a router
(MAC addresses), and are then assigned.
The IPv6 addresses are different from those of the
previously active management modules.

Tip: The LAN cables need to be connected to both the active and standby
management modules to continue operations even after the management
modules are switched.

Figure 2-4 Example of management modules configured in a redundant


configuration

Improving failure handling by configuring management networks in


a redundant configuration
You can configure the management network in a redundant configuration if
the management modules are in a redundant configuration. This functionality
is called Link Fault Tolerance (LFT). The figure below shows an outline of LFT.

2-46 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 2-5 Link Fault Tolerance
MGMT1 and MGMT2 ports are subject to LFT. These ports can be enabled or
disabled independently. In the initial settings (the settings at shipping time),
the ports are enabled. These ports are switched separately. Therefore, if
MGMT1 and MGMT2 are connected to different switches and a switching
occurs in either of the external switches, only the port that is connected to
the switch is switched.
If a link-down state is detected on a port of the active management module
continuously for three seconds while the LFT is enabled, the port is switched.
After the port is switched, if a link-up state is detected on the port of the
active management module continuously for 180 seconds, the port is
recovered.
You can change the link-down detection time for switching and link-up
detection time for recovery in the range from one to 3600 seconds.
You can configure the LFT functionality from the management module.

Preparations for Using the Management Module 2-47


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-27 Redundancy settings of the management network

Operation Web console CLI console LCD touch console

Changing the monitoring Y -- --


time for the management
network

Related topics
• Changing the monitoring time for the management network on page
2-48

Changing the monitoring time for the management network


Use the Web console to change the monitoring time for the management
network.
To configure the management network in a redundant configuration
from the Web console:
1. In the Resources tab, from the tree view under Systems, select
Network, and then Link Fault Tolerance.
2. Click the Edit button.
3. Change the settings of any necessary items.

Related topics
• Improving failure handling by configuring management networks in a
redundant configuration on page 2-46

Operating identification lamps of each module


This section describes the identification lamps installed on the system unit.

Identification lamp
Identification lamps called identification LEDs (LID) are installed in the
modules below. From the appearance of the system unit, you can identify the
module on which operations are being performed based on the indicator
statuses of the identification lamps.
• Management module
• Management LAN module
• Server blade
• I/O adapter
• Switch module
You can turn on or off identification lamps from the management module.

2-48 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-28 Identification lamp operation

Operation Web console CLI console LCD touch console

Operating the Y Y Y
identification lamp of
the management
module

Operating the Y Y Y
identification lamp of
a management LAN
module

Operating the Y Y Y
identification lamp of
a server blade

Operating the Y Y --
identification lamp of
an I/O adapter

Operating the Y Y Y
identification lamp of
a switch module

Related topics
• Operating the identification lamp of the management module on page
2-49
• Operating the identification lamp of a management LAN module on page
2-50
• Operating the identification lamp of a server blade on page 2-51
• Operating the identification lamp of an I/O adapter on page 2-51
• Operating the identification lamp of a switch module on page 2-52

Operating the identification lamp of the management module


To operate the identification lamp of the management module, use the Web
console, the CLI console, or the LCD touch console.
To operate the identification lamp of the management module from
the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target management module.
2. From the Condition tab, click the LID ON button or the LID OFF button.
To operate the identification lamp of the management module from
the CLI console:
1. To check whether the identification lamp is currently lit, execute the show
mgmt-module status command. To edit the settings, execute the set
mgmt-module led command.

Preparations for Using the Management Module 2-49


Hitachi Compute Blade 2500 Series Management Module User Guide
To operate the identification lamp of the management module from
the LCD touch console:
1. From the Maintenance menu, touch the Management Module (MM)
button.
2. In the Management module window, click the target management
module.
3. From the pull-down menu, select LID ON/OFF, and then touch the
Operation button.
4. The LID window appears.

Related topics
• Identification lamp on page 2-48
• show mgmt-module status on page 5-108
• set mgmt-module led on page 5-90

Operating the identification lamp of a management LAN module


To operate the identification lamp of a management LAN module, use the
Web console, the CLI console, or the LCD touch console.
To operate the identification lamp of a management LAN module from
the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target management module.
2. From the Management LAN Module tab, click the LID ON button or the
LID OFF button.
To operate the identification lamp of a management LAN module from
the CLI console:
1. To check whether the identification lamp is currently lit, execute the show
mgmt-lan-module status command. To edit the settings, execute the
set mgmt-lan-module led command.

To operate the identification lamp of a management LAN module from


the LCD touch console:
1. From the Maintenance menu, touch the Management Module (MM)
button.
2. In the Management module window, click the target management
module.
3. From the pull-down menu, select Management LAN LID ON/OFF, and
then touch the Operation button.
4. The Management LAN LID ON/OFF window appears.

Related topics
• Identification lamp on page 2-48

2-50 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• show mgmt-lan-module status on page 5-117
• set mgmt-lan-module led on page 5-114

Operating the identification lamp of a server blade


To operate the identification lamp of a server blade, use the Web console, the
CLI console, or the LCD touch console.

Tip: In an SMP configuration, you can operate individual identification lamps


of the server blades constituting the SMP configuration.

To operate the identification lamp of a server blade from the Web


console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. From the Condition tab, click the LID ON button or the LID OFF button.
To operate the identification lamp of a server blade from the CLI
console:
1. To check whether the identification lamp is currently lit, execute the show
blade status command. To edit the settings, execute the set blade
led command.

To operate the identification lamp of a server blade from the LCD


console:
1. From the Maintenance menu, touch the Server Blade (SB) button.
2. In the Server blade window, click the target server blade.
3. From the pull-down menu, select LID ON/OFF, and then touch the
Operation button.
4. The LID window appears.

Related topics
• Identification lamp on page 2-48
• show blade status on page 5-80
• set blade led on page 5-45

Operating the identification lamp of an I/O adapter


To operate the identification lamp of an I/O adapter, use the Web console,
the CLI console, or the LCD touch console.
To operate the identification lamp of an I/O adapter from the Web
console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.

Preparations for Using the Management Module 2-51


Hitachi Compute Blade 2500 Series Management Module User Guide
2. From the I/O Board tab, click the LID ON button or the LID OFF
button.
To operate the identification lamp of an I/O adapter from the CLI
console:
1. To check whether the identification lamp is currently lit, execute the show
iobd status command. To edit the settings, execute the set iobd led
command.

Related topics
• Identification lamp on page 2-48
• show iobd status on page 5-122
• set iobd led on page 5-119

Operating the identification lamp of a switch module


To operate the identification lamp of a switch module, use the Web console,
the CLI console, or the LCD touch console.
To operate the identification lamp of a switch module from the Web
console:
1. In the Resources tab, from the tree view under Modules, select the
target switch module.
2. From the Condition tab, click the LID ON button or the LID OFF button.
To operate the identification lamp of a switch module from the CLI
console:
1. To check whether the identification lamp is currently lit, execute the show
sw-module status command. To edit the settings, execute the set sw-
module led command.

To operate the identification lamp of a switch module from the LCD


touch console:
1. From the Maintenance menu, touch the Switch module (SW) button.
2. In the Server blade window, click the target switch module.
3. From the pull-down menu, select LID ON/OFF, and then touch the
Operation button.
4. The LID window appears.

Related topics
• Identification lamp on page 2-48
• show sw-module status on page 5-135
• set sw-module led on page 5-125

2-52 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Power supply operation for a server blade
This section explains how to control the power supplies of server blades.

Power supply operation for a server blade by using the management


module
You can operate the power supply of a server blade by using the
management module. For details about how to turn on and off and restart the
power supply, see the Hitachi Compute Blade 2500 Series Getting Started
Guide. This manual explains how to set the operation of the server blade to
prepare for a trouble such as a power outage.
The following table describes the consoles used when you set the operation of
a server blade from the management module.

Table 2-29 Power supply operation for a server blade

Operation Web console CLI console LCD touch console

Setting the server blade Y Y --


operation performed when
the power supply of the
system unit is restored

Related topics
• Setting the server blade operation performed when the power supply of
the system unit is restored on page 2-53

Setting the server blade operation performed when the power supply
of the system unit is restored
From the Web console or the CLI console, set the server blade operation
(power on/off, or recover the status before the failure occurred) performed
when the system unit is turned on. You can automatically restore the power
supply of the server blade when power is restored after a power outage.

Note:
• If the N+M cold standby functionality is enabled, make sure that you set
the server blade restore operation by using the management module. If
you configure a power supply restore operation from the UEFI setup
menu, automatic server power-on might not work correctly.
• For a standby server blade in N+M cold standby, set the operation to
[Power OFF]. If the standby server blade operation is set to [Power ON],
N+M cold standby failover cannot be performed for the server blade.

Tip: If peripheral devices need to start before the server blade, you can set
the waiting time from booting the server chassis to turning on the server
blade to no more than 60 minutes.

Preparations for Using the Management Module 2-53


Hitachi Compute Blade 2500 Series Management Module User Guide
To set the operation of a server blade from the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. In the Settings tab, click the Edit Server Blade settings button.
3. Set the time to wait until power is restored, and the operation to perform
when power is restored.
To set the operation of a server blade from the CLI console:
1. Execute the set blade ac-recovery command.

Related topics
• Power supply operation for a server blade by using the management
module on page 2-53
• Preparation for running the server blades in a redundant configuration (N
+M cold standby) on page 3-6
• set blade ac-recovery on page 5-39

Efficient operation of server blades by SMP configurations


An SMP configuration is composed of multiple server blades. This section
describes SMP configurations.

SMP configurations for server blades


CB 2500 server blades support 2-blade SMP configurations and 4-blade SMP
configurations. In a 2-blade SMP configuration, two server blades are
connected by a 2-blade SMP connection board. In a 4-blade SMP
configuration, four server blades are connected by a 4-blade SMP connection
board. A maximum of eight CPUs can be used in an inter-blade SMP
configuration.
In a 2-blade SMP configuration or a 4-blade SMP configuration, the server
blade installed in the slot with the smallest server blade slot number (the
lower left slot of the front of the unit) is called the primary server blade. The
numbers of the server blade slots in which the primary server blade of a 2-
blade SMP configuration can be installed are 1, 3, 5, 9, 11, and 13. The
numbers of the server blade slots in which the primary server blade of a 4-
blade SMP configuration can be installed are 1 and 9.
You can use management modules to configure SMP configurations. You can
separately specify an SMP configuration pattern for slot numbers 1 to 8 and
for slot numbers 9 to 15.

2-54 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-30 SMP configuration settings

Operation Web console CLI console LCD touch console

Configuring SMP Y Y --
configurations for server
blades.

Related topics
• Configuring SMP configurations for server blades on page 2-55

Configuring SMP configurations for server blades


To configure an SMP configuration for server blades, use the Web console or
the CLI console. Before you change settings, connect the server blades that
are to constitute an SMP configuration to an SMP connection board.

Note:
• If you cannot configure an SMP configuration for server blades due to a
problem such as a server blade or an SMP connect board not being
installed, a message indicating the problem appears.
• You cannot include different models of server blades or different types of
processors together in an SMP configuration.
To configure an SMP configuration for server blades from the Web
console:
1. In the Resources tab, from the tree view under Systems, click SMP
Management.
2. Click the SMP configuration settings button.
The SMP configuration settings dialog box appears.
3. Select the configuration to be configured and then click the Confirm
button.
To configure an SMP configuration for server blades from the CLI
console:
1. Execute the show blade smp construction command to check the
current SMP configuration settings. To change SMP configuration settings,
execute the set blade smp construction command.

Related topics
• SMP configurations for server blades on page 2-54
• show blade smp construction on page 5-78
• set blade smp construction on page 5-52

Preparations for Using the Management Module 2-55


Hitachi Compute Blade 2500 Series Management Module User Guide
Operating server blades by using the remote console
This section explains how to operate server blades by using the remote
console.

Remote console
The remote console is a tool for remotely controlling the VGA display,
keyboard, mouse, CD/DVD, or FD as the graphical console of each server
blade. You can start a remote console from the Web console or a Web
browser of the system console.
You can manage remote console sessions from a management module
console.
For an overview and details about how to set up the remote console, see the
Hitachi Compute Blade 2500 Series Getting Started Guide.

Table 2-31 Remote console operations

Operation Web console CLI console LCD touch console

Starting the remote Y -- --


console

Checking remote -- Y --
console session
information

Disconnecting -- Y --
remote console
sessions

Related topics
• Starting the remote console on page 2-56
• Checking remote console session information on page 2-57
• Disconnecting remote console sessions on page 2-57

Starting the remote console


You can start the remote console in one of two ways: from the Web console
of the server blade and from the Web console of a management module. If
you want to change only the server blade settings, we recommend that you
operate from the Web console of the server blade. For details, see the Hitachi
Compute Blade 2500 Series Getting Started Guide.
This manual explains how to start the remote console from the Web console
of a management module.

Note: To start the remote console in the environment where multiple IP


addresses are assigned to BMC, start the remote console by using a system
console that can connect to any BMC IP addresses.

2-56 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To start the remote console from the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.

Tip: In an SMP configuration, select the primary server blade.

2. From the Server blade Action menu in the Condition tab, click Start
Remote Console.
The remote console window appears. If the server blade is powered on, a
VGA window of the server blade appears. If the server blade is powered
off and video is not output, No Signal is displayed.

Tip: When you start a remote console, a warning message might appear
depending on the Java VM version. Click Yes or Run.

Related topics
• Remote console on page 2-56

Checking remote console session information


Use the CLI console to check remote console session information.
To check remote console sessions from the CLI console:
1. Execute the show blade bmc session command.

Related topics
• Remote console on page 2-56
• show blade bmc session on page 5-56

Disconnecting remote console sessions


To disconnect remote console sessions, use the CLI console.
To disconnect remote console sessions from the CLI console:
1. Execute the disconnect blade bmc session command.

Related topics
• Remote console on page 2-56
• disconnect blade bmc session on page 5-31

Operating server blades by using the OS console


This section explains how to operate server blades by using the OS console.

Preparations for Using the Management Module 2-57


Hitachi Compute Blade 2500 Series Management Module User Guide
OS console
The OS console provides functionality to transfer serial port input and output
of the server blade to the system console via a LAN, and to remotely control
a serial console.

Tip: The OS console cannot be used for the following operations. For these
operations, use the remote console.
• Operation before booting the OS
• OS installation

Table 2-32 OS console operations

Operation Web console CLI console LCD touch console

Starting the OS -- Y --
console

Related topics
• Checking OS serial port settings on page 2-58
• Starting the OS console on page 2-59
• Notes on using the OS console on page 2-59

Checking OS serial port settings


The OS console uses the COM2 port of the server blade. The setting method
is different for each type of server blade OS.
For Windows:
Confirm that the COM2 port settings of the OS are the following.

Table 2-33 COM2 port settings

Item Settings

Port COM2

Baud rate 115200

Data 8 bits

Parity None

Stop 1 bit

Flow control None

Recommended terminal type VT100

Tip: The OS console cannot be used as Windows Special Administration


Console (SAC).

For Linux:

2-58 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Set the following OS parameters.

Table 2-34 Example of Linux parameters

Item Settings

/boot/grub/grub.conf setting Add console=tty0 console=ttyS1,115200 at the end


of each kernel line.

/etc/inittab setting • Add co:2345:respawn:/sbin/agetty 115200


ttyS1 vt100 to the last line.
• Execute init q.

/etc/sysconfig/kudzu setting Change to SAFE=yes. (If this setting does not exist,
add it.)

/etc/securetty setting Add ttyS1.

Note:
• For the Linux Login mode, Linux must be installed in Text mode.
If you installed Linux by selecting Graphic mode, you need to change the
Login mode to Text mode. For details about how to change the setting,
see the documentation for your OS.

Related topics
• OS console on page 2-58

Starting the OS console


Use the CLI console to start the OS console.
To start the OS console from the CLI console:
1. Execute the change console -b command.

Tip:
• If another terminal is using the OS console, you cannot start the OS
console.
• If you are disconnected from a network while using the OS console, the
OS console session might remain for a while. This state can be released
by disconnecting the remote console session.

Related topics
• OS console on page 2-58
• change console on page 5-263

Notes on using the OS console


This section provides notes on using the OS console.

Preparations for Using the Management Module 2-59


Hitachi Compute Blade 2500 Series Management Module User Guide
OS console operations
• Input operation
Keyboard entry is assumed, and fast data input such as file transfer is not
supported. Use the keyboard for input operation.
• Recovering a session when it becomes disconnected
Depending on your environment, the window display might become
significantly slower, or the terminal software session might become
disconnected. In such a case, reconnect to the OS console. Note that
applications that output a lot of characters might have lower performance
because of their output processing. For these applications, evaluate their
purposes in advance, and suppress display of the output if necessary.
• Characters missed when transferred
If you cut and paste characters into the OS console, some characters
might be left out.

If the system console displays garbled characters:


Character codes or display colors might be handled differently by the system
console and server blades. The following describes causes of garbled
characters in the system console and actions to be taken.

Cause Recovery procedure

The communication condition is Check the software settings on the system console
incorrectly set. side.

An inappropriate character set In the software on the system console side, select an
is selected in the software on appropriate character set.
the system console side.

Inappropriate character codes See the documentation for the software on the sending
are sent from the software side, and then take action.
(such as Windows and Linux) of
the sending side.

Linux System Request key functionality


To use the System Request key functionality in the OS console, send the
following sequence.

Item Operation

For Telnet Send a Telnet IAC (interpreted as command) break sequence, or send
connection Ctrl + \. How a break signal is sent from terminal software varies
depending on the software.
For details, see the documentation for your terminal software.

For an SSH Send Ctrl + \.


connection

2-60 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• OS console on page 2-58
• Checking OS serial port settings on page 2-58

Setting server blades, switch modules, and Hitachi Fibre


Channel adapter
This section explains how to specify the settings of modules such as server
blades and switch modules by using a management module.

Modules that can be operated from a management module


The settings of modules such as server blades and switch modules that are
installed in the CB 2500 can be directly specified from the management
module, or can be specified after using links to jump to the console of each
module. Performing operations on the management module console provides
unified management of the CB 2500 modules without connecting to other
consoles.
You can specify the settings of the following types of modules from a
management module console.

Table 2-35 Module settings that can be specified from a management


module

Operation Web console CLI console LCD touch console

Setting the BMC of a Y -- --


server blade

Setting the UEFI of a Y -- --


server blade

Setting a switch -- Y --
module

Setting a Hitachi Y Y --
Fibre Channel
adapter

Setting LPAR Y Y --
manager1

Note:
1. For details about the LPAR manager settings, see the Hitachi Compute Blade 2500
Series Logical partitioning manager User Guide.

Related topics
• Setting the BMC of a server blade on page 2-62
• Setting the UEFI for a server blade on page 2-76
• Setting a switch module on page 2-77

Preparations for Using the Management Module 2-61


Hitachi Compute Blade 2500 Series Management Module User Guide
• Setting a Hitachi Fibre Channel adapter on page 2-77

Setting the BMC of a server blade


To change the BMC settings of a server blade, use the Web console.
To set the BMC from the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. In the BMC tab, click the Edit button to select the item to be edited.
3. Specify the necessary items, and perform the processing.
The specified items are immediately applied.

Note: If you specify an asset management tag of a server blade, the tag
information is applied to the following items:
• The Product name field displayed in the Hardware tab of the server
blade
• The server name displayed in HCSM

Related topics
• BMC setting items for a server blade on page 2-62

BMC setting items for a server blade


This section describes items that can be set for the BMC.

BMC time items


Table 2-36 BMC time items

Item Description

Time adjustment method Uses NTP to regularly adjust the time with management
modules.
For the CB 520H B3, time can be synchronized manually
or by using the IPMI command.

Time zone Enter the BMC time zone between -12:00 and +14:00.

Daylight saving time Use Select either [Enable] or [Disable] for daylight saving
time of the BMC.

Start date Enter the date in the MM-DD format (M and D indicate a
number between 0 and 9).
You can specify 00-00 or a valid date

Start condition Select one from the following:


• Start date
• The first Start day of the week after Start date
• The last Start day of the week before Start date

2-62 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description
• The last Start day of the week

Start day of the Select No set, Sun, Mon, Tue, Wed, Thu, Fri, or Sat.
week

Start time Enter the time in the HH:MM format (H and M indicate a
number between 0 and 9).
You can specify the time in the range from 00:00 to
23:59.

End date The setting format is the same as the start date.

End condition Select one from the following:


• End date
• The first End day of the week after End date
• The last End day of the week before End date
• The last End day of the week

End day of the week The setting format is the same as the start day of the
week.

End time The setting format is the same as the start time.

Network
Table 2-37 Network

Item Description

Restriction on the Use Select [Enable] or [Disable].


connection source IPv4 If you select [Enable], only connections from the IPv4
address addresses that are set for allowed IPv4 addresses 1
to 4 are permitted.
If you select [Disable], connections from all IP
addresses are allowed.
However, even if you select [Disable], if incorrect
values are entered to allowed IPv4 addresses 1 to 4,
this setting fails.

Allowed IPv4 address Enter an IPv4 address to be permitted to connect to


1 the BMC in the xxx.xxx.xxx.xxx format or the CIDR
format (xxx.xxx.xxx.xxx/yy). To permit connection
Allowed IP address 2 only to the specified IPv4 address, enter the address
Allowed IP address 3 in the xxx.xxx.xxx.xxx format. To collectively permit
connection by using the high-order bits of an IPv4
Allowed IP address 4 address, enter the address in the CIDR format. All
IPv4 addresses that have the common numeric
values for the number of bits specified by yy from the
beginning of the IPv4 address in xxx.xxx.xxx.xxx will
be permitted connection (xxx indicates a number
between 0 and 255). For yy, specify a number
between 8 and 30 as the network address prefix
length.

Preparations for Using the Management Module 2-63


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description
Example: If 192.168.0.1/16 is specified, all IPv4
addresses that are in the 192.168.xxx.xxx format will
be permitted connection.
This setting restricts connection for the following
functionality:
• Server blade Web console
• Remote console
• IPMI over LAN

Restriction on the Use Select [Enable] or [Disable].


connection source IPv6 If you select [Enable], only connections from the IP
address addresses that are set for allowed IPv6 addresses 1
to 4 are permitted.
If you select [Disable], connections from all IP
addresses are permitted.
However, even if you select [Disable], if incorrect
values are entered to allowed IPv6 addresses 1 to 4,
the setting fails.

Allowed IPv6 address Enter an IPv6 address to be permitted to connect to


1 the BMC in hexadecimal notation separated by colons
(:) every 16 bits
Allowed IPv6 address (xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx) or in
2 hexadecimal notation with prefix
Allowed IPv6 address (xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/yyy). If
3 there are consecutive blocks of 0s, you can specify
two colons (::) instead of 0s. However, only one such
Allowed IPv6 address replacement is allowed.
4 Example: FEDC:0:0:3210:0:0:7654:3210 to FEDC::
3210:0:0:7654:3210
To collectively permit connection by using the high-
order bits of IPv6 addresses, enter the address in the
hexadecimal notation with prefix. All IPv6 addresses
that have the common numeric values for the number
of bits specified by yyy from the beginning of the
IPv6 address will be permitted connection. For yyy,
specify a value from 1 to 128 as prefix length.
Example: If you specify
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210/64 or
FEDC:BA98:7654:3210::/64, all IPv6 addresses in
the range of
FEDC:BA98:7654:3210:xxxx:xxxx:xxxx:xxxx are
permitted.
This setting restricts connection for the following
functionality:
• Server blade Web console
• Remote console
• IPMI over LAN

2-64 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
BMC user account items
Table 2-38 BMC user account items

Item Description

Password aging Use Select [Disable] or [Enable].

Password expiry If you select [Disable] for Use, 0 is set.


period(day) If you select [Enable] for Use, enter a value
in the range from 1 to 365 for this item.

User account 1 Use Select [Disable] or [Enable].


User account 1 cannot be set to [Disable].

User name You can enter a character string of 1 to 16


characters. The string can contain
alphanumeric characters and the following
symbols: . _ $ - = + * % ? @ / \ ' ! ~ ; ^
()[]{}|,`
The symbols <, >, &, #, ", and spaces
cannot be used.
The first character must be an alphanumeric
character.

Password You can enter a character string of 1 to 20


characters. The string can contain
alphanumeric characters and symbols
(excluding the following invalid symbols).
The symbols <, >, &, #, ", and spaces
cannot be used.

Password (Confirm) Enter the same character string as


[Password].

Password expiration Displays the number of days left until the


date password expiration date, regardless of
whether the password aging functionality is
disabled or enabled. When the number of
days left is 0, you need to set the password
again if the password aging functionality is
enabled.

User account 2 Same as user account Same as user account 1. However, for user
1. accounts 2 through 4, you can specify
User account 3 [Disable] for [Use].
User account 4

Note: For CB 520X B1 and CB 520H B3, the password aging functionality of
the BMC user account settings is supported for the following versions:
Server blade firmware
- For CB 520X B1, Integrated firmware 07-15 or later.
- For CB 520H B3, Integrated firmware 08-16 or later.

Preparations for Using the Management Module 2-65


Hitachi Compute Blade 2500 Series Management Module User Guide
IPMI/SMASH user accounts
Table 2-39 IPMI/SMASH user accounts

Item Description

Password aging Use Select [Disable] or [Enable].

Password expiry period(day) If you select [Disable] for Use, 0 is set.


If you select [Enable] for Use, enter a
value in the range from 1 to 365 for this
item.

User account 1 Use Select [Disable] or [Enable].

User name You can enter a character string of 1 to 16


characters. The string can contain
alphanumeric characters and the following
symbols: . _ $ - = + * % ? @ / \ ' ! ~ ; ^
()[]{}|,`
The symbols <, >, &, #, ", and spaces
cannot be used.
The first character must be an
alphanumeric character.

Password You can enter a character string of 1 to 20


characters. The string can contain
alphanumeric characters and symbols
(excluding the following invalid symbols).
The symbols <, >, &, #, ", and spaces
cannot be used.

Password (Confirm) Enter the same character string as


[Password].

Privilege You can select from the following privilege


levels:
• Administrator (initial setting)
• Operator
• User
• Callback
• NO ACCESS

Password expiration date Displays the number of days left until the
password expiration date, regardless of
whether the password aging functionality
is disabled or enabled. When the number
of days left is 0, you need to set the
password again if the password aging
functionality is enabled.

User account 2 Same as user account 1. Same as user account 1. However, for
user accounts 2 through 9, you can
User account 3 change the user name.
User account 4

User account 5

User account 6

2-66 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description

User account 7

User account 8

User account 9

Note: For details, see Hitachi Compute Blade Series SMASH and IPMI User's
Guide.

Note: For CB 520X B1 and CB 520H B3, the password aging functionality of
the IPMI/SMASH user account settings is supported for the following
versions:
Server blade firmware
- For CB 520X B1, Integrated firmware 07-15 or later.
- For CB 520H B3, Integrated firmware 08-16 or later.

Server blade Web console


Table 2-40 Server blade Web console

Item Description

Use Select [Disable] or [Enable].


The server blade Web console only supports HTTPS
connections.
If you set [Disable], the BMC will discard HTTPS
connections.
In addition, you will not be able to start the remote
console.

Enable login Select Disable or Enable. The default value is Enable.


With this item disabled, https connection is available
but login is not.

HTTPS port number Port number of the server blade Web console.
Shows 443. The port number cannot be changed.

TLS version TLS v1.0 Select [Disable] or [Enable].


TLS v1.1 If you select [Disable], the TLS version cannot be used
TLS v1.2 to connect to the server blade Web console.
If you set the security strength to [High], only TLS 1.2
will be enabled and other versions will be fixed to
[Disable].

Preparations for Using the Management Module 2-67


Hitachi Compute Blade 2500 Series Management Module User Guide
Remote console
Table 2-41 Remote console

Item Description

Use Select [Disable] or [Enable].


If you set [Disable], the BMC will discard connection
requests from KVM/vMedia clients.

Port number Enter the port number for receiving connection


requests from KVM/vMedia clients.
Specify 5001 or a port number in the range from
1024 to 65535.

TLS version TLS v1.0 Select [Disable] or [Enable].


TLS v1.1 If you select [Disable], the TLS version cannot be
TLS v1.2 used to connect to the remote console.
If you set the security strength to [High], only TLS
1.2 will be enabled and other versions will be fixed
to [Disable].

Note: The following numbers cannot be used as a remote console port


number.
5985, 5986, 5988, and 5989
To use a remote console, set the port number to a value other than those
listed above.

IPMI over LAN


Table 2-42 IPMI over LAN

Item Description

Use Select [Disable] or [Enable].


If you select [Disable], BMC will discard RMCP/RMCP+
packets.

Port number Shows 623. The port number cannot be changed.

SMASH (WS-Management)
Table 2-43 SMASH (WS-Management)

Item Setting values

Use Select [Disable] or [Enable].


If you select [Disable], the BMC discards connection requests from
WS-Management clients.
If you set the security strength to [High], this item is fixed to
[Disable].

Port number Enter the port number for receiving connection requests from WS-
Management clients.

2-68 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values
Specify 5986 or a port number in the range from 1024 to 65535.

TLS versions (TLS v1.0, TLS v1.1, Select [Enable] or [Disable].


and TLS v1.2) If you select [Disable], the TLS version cannot be used to connect
from WS-Management clients.
If the security strength is set to [High], only TLS1.2 is enabled.
Others will be fixed to [Disable].

SMASH (CLP)
Table 2-44 SMASH (CLP)

Item Setting values

Use Select [Disable] or [Enable].


If you select [Disable], the BMC discards connection requests from
SSH clients.

Port number Enter the port number for receiving connection requests from SSH
clients.
Specify 22 or a port number in the range from 1024 to 65535.

login banner
Table 2-45 login banner

Item Setting values

Use Select [Disable] or [Enable].


If you select [Enable], a login banner is displayed on the login
window of the server blade Web console and the SMASH (CLP)
login window.

Message You can enter a maximum 100 lines or 1600 characters for the
message displayed in the login banner. Displayable ASCII
characters are available.

Asset Information items


Table 2-46 Asset Information items

Item Setting values

Asset Tag Sets an asset tag for a server blade.


You can enter no more than 63 alphanumeric characters and
symbols.

Preparations for Using the Management Module 2-69


Hitachi Compute Blade 2500 Series Management Module User Guide
DNS
Table 2-47 DNS

Item Setting values

Priority Select IPv4 or IPv6. If you select IPv4, IPv4 DNS


servers are used first. If you select IPv6, IPv6 DNS
servers are used first.

DNS (IPv4) DNS server 1 Enter the IPv4 address of a DNS server in the format
of xxx.xxx.xxx.xxx. If no DNS server is used, do not
DNS server 2 enter any values.
DNS server 3

DNS (IPv6) DNS server 1 Enter the IPv6 address of a DNS server in
hexadecimal notation separated by colons (:) every
DNS server 2 16 bits (xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx).
DNS server 3 If there are consecutive blocks of 0s, you can specify
two colons (::) instead of 0s. However, only one such
replacement is allowed.
Example: FEDC:0:0:3210:0:0:7654:3210 to FEDC::
3210:0:0:7654:3210
If no DNS server is used, do not enter any values.

Syslog transmission
Table 2-48 Syslog transmission

Item Setting values

Use Select [Disable] or [Enable].


If you select [Enable], the syslog for BMC is transferred to an
external syslog server.

Syslog destination server Enter the IPv4 address for the syslog destination server in the
format of xxx.xxx.xxx.xxx or in FQDN (a maximum of 127
characters).

Audit event notice Select Notify or Not notify.

Port number Specify the port number to be used to connect to the target Syslog
server.
Specify 514 or a number between 1 and 65535 for the port
number.

Transfer protocol Select UDP or TCP or TLS.

TLS version If TLS is selected as the transfer protocol, specify the TLS version.

Format Select the operation or audit log format for the system logs to
transfer. For details on the formats, see Syslog format in Log
format on page 3-68.

2-70 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
LDAP
Table 2-49 LDAP

Item Setting values

LDAP server settings Use Select [Disable] or [Enable].


If you select [Enable], LDAP is used in SMASH
authentication.
If you enable this item, you cannot use the RADIUS
functionality.

User authentication Select an authentication method.


method • Only LDAP authentication
• Use LDAP authentication if local authentication
fails.

LDAP server 1 Enter the IPv4 address for an LDAP server in the
format of XXX.XXX.XXX.XXX or in FQDN (a maximum
LDAP server 2 of 127 characters).
LDAP server 3

Port number Specify the number of the port that is used for
connecting to LDAP servers.
Specify 398 or a value in the range from 1024 to
65535 for the port number.

Connection settings TSL version Specify a TLS version that is used for connecting to
the LDAP servers.

Anonymous binding Select [Disable] or [Enable]. If you select [Disable],


the specified bind DN and bind password is used to
bind LDAP servers.

Bind DN Specify a DN used for binding. You can use a


maximum of 254 ASCII characters. However, you
cannot use a space character for the first or last
character. This item is used when anonymous biding
is disabled.

Bind password Specify a password used for binding. You can use a
maximum of 32 ASCII characters. This item is used
when anonymous biding is disabled.

Bind password (for Enter the same characters as those entered in the
confirmation) Bind password field.

Directory search settings Base DN Specify the DN which is the starting point of directory
searching.

Login ID attribute Specify the user entry attribute that is used as the
login ID. If you do not specify this item,
sAMAccountName is used.

Role attribute Specify the user entry attribute that is used to obtain
the role for the user. If you do not specify this item,
the user is assumed to have no role. For details on
how to set roles, see the descriptions about
registration of user accounts.

Preparations for Using the Management Module 2-71


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values

Search timeout Specify a period (in seconds) from when the specified
period (in seconds) LDAP server does not return any responses while
searching the user entry to when a timeout occurs.
Specify 10 seconds or a value in the range from 1 to
20 seconds.

Referral number LDAP has the referral functionality, which returns a


referral instructing an LDAP client to query another
LDAP server when the specified LDAP server cannot
find the user entry information. As the number of
referrals, specify the number of LDAP servers to be
queried as 10 or a value in the range from 0 to 10. If
you specify 0, the referral functionality is disabled.

Group authentication Authentication Select a group authentication method.


settings method • [Disable group authentication]: Does not perform
authentication based on the groups that are set
in the LDAP server.
• [Static Groups]: Performs authentication based
on the groups specified for group DNs 1 to 5 and
the roles specified for group DNs 1 to 5.
• [Dynamic Groups]: Performs authentication
based on the groups that were temporarily
created from the search DN and search filter
which were entered by the user.

Group DN 1 Specify the DN for the group entry. This item is used
when the group type is "static group".
If the user is not a member of the groups specified for
group DNs 1 to 5, user authentication fails and the
user cannot log in to the BMC service.

Role of group DN 1 Specify the role for the group entry. This item is used
when the group type is "static group". If the user is
not a member of any groups specified for group DNs 1
to 5, the group role specified in this item is not
assigned to the user. You can select one of the
following four group roles:
• [None]: No group role is assigned.
• [Use the user entry role]: Instead of the group
role, the user entry role specified in [Role
attribute] of [Directory search setting] is used.
• [Administrator]: The group members can use
each service of the server blade BMC.
• [SMASH]: The group members can use the
SMASH-CLP and WS-Management for the server
blade BMC.

Group DN 2 Same as group DN 1.

Role of group DN 2 Same as the role of group DN 1.

Group DN 3

Role of group DN 3

Group DN 4

2-72 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values

Role of group DN 4

Group DN 5

Role of group DN 5

Search DN Specify the DN which is a starting point of directory


searching when a dynamic group is created.

Search filter Specify an attribute and an attribute value.


Temporarily forms a dynamic group by grouping the
user entries located under the search DN that satisfies
the attribute and attribute value that are specified for
this item.

Dynamic group role Specify the role for the group entry. This item is used
when the group type is "dynamic group". If the user is
not a member of the dynamic group, the group role
specified for this item is not assigned to the user. You
can select one of the following four group roles:
• [None]: No group role is assigned.
• [Use the user entry role]: Instead of the group
role, the user entry role specified in [Role
attribute] of [Directory search setting] is used.
• [Administrator]: The group members can use
each service of the server blade BMC.
• [SMASH]: The group members can use the
SMASH-CLP and WS-Management for the server
blade BMC.

RADIUS
Table 2-50 RADIUS

Item Setting values

RADIUS server Use Select [Disable] or [Enable].


settings If you enable this item, RADIUS is used for SMASH
authentications.
If you enable this item, you cannot use the LDAP
functionality.

User authentication Select a user authentication method.


method • RADIUS authentication only
• If Local authentication fails, try RADIUS
authentication

RADIUS server1 Server name Enter the IPv4 address for a RADIUS server in the format
settings of XXX.XXX.XXX.XXX or in FQDN (maximum of 127
characters).

Authentication Select an authentication method.


method • PAP
• CHAP

Preparations for Using the Management Module 2-73


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values
• MS-CHAPv2

Port number Enter the destination port number for authentication of


(Authentication) the RADIUS server.
Specify 1812 or a value in the range from 1 to 65535 for
the port number.

Shared Secret Enter a key character string shared between BMC and the
RADIUS server.
You can enter a character string of 32 to 64 characters.
The string can contain alphanumeric characters and the
following symbols: . _ $ - = + * % ? : @ / \ ' ! ~ ; ^ ( )
[]{}|,`
The symbols <, >, &, #, ", and spaces cannot be used.

Retransmit retry Enter the number of times to reconnect to the RADIUS


server if the RADIUS server does not respond. Specify 3
time or a value in the range from 1 to 10 times.

Timeout period(sec) Enter the period (in seconds) from when the RADIUS
server does not respond to when a timeout occurs.
Specify 10 seconds or a value in the range from 1 to 60
seconds.

RADIUS server2 Same as the RADIUS Same as the RADIUS server1 settings.
settings server1 settings.

RADIUS server3
settings

Note: For CB 520X B1 and CB 520H B3, the RADIUS functionality is


supported for the following versions:
Server blade firmware
- For CB 520X B1, Integrated firmware 07-15 or later.
- For CB 520H B3, Integrated firmware 08-16 or later.

Certificate settings
Table 2-51 Certificate settings - Current certificate information

Item Setting values

Version Displays the certificate version.


This is a value from 1 to 3.

Serial number Displays the serial number of the key.

Public key algorithm and key length Displays the algorithm used by the SSL public
key and key length.
The available algorithm is RSA and the key
length is 2048 bits.

Date and time when the certificate was issued Displays the date and time when the certificate
was issued

2-74 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values

Expiration date of the certificate Displays the expiration date of the certificate.

Issuer Common name (CN) Certificate authority (issuer)

Subject Country (C) Shows two letters for a country.

State or province (ST) Shows the name of a state or province.


This item can be no more than 30 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Locality (L) Shows the name of a city or region.


This item can be no more than 50 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Organization (O) Shows the name of an organization (company).


This item can be no more than 60 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Organizational unit (OU) Shows the name of an organizational unit.


This item can be no more than 60 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Common name (CN) This item must be entered.


Displays a common name (a domain name used
when the management module is connected).
This item can be no more than 60 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + , - .

Email address Shows an email address.


Displayable ASCII characters are available.

DN qualifier Shows a DN qualifier.


This item can be no more than 60 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Surname Shows a surname.


This item can be no more than 60 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Given name Shows a given name.


This item can be no more than 60 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

Preparations for Using the Management Module 2-75


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values

Initials Shows initials.


This item can be no more than 20 characters
long, and can contain alphanumeric characters,
spaces, and the following symbols: ' ( ) + ,
-./:=?

SHA1 fingerprint Displays the fingerprint for the certificate.


The fingerprint is a 20-byte hash value that is
generated by the SHA-1 algorithm.

SSH host key


Table 2-52 SSH host key

Item Setting values

SSH host key Key length Enter the IPv4 address of a DNS server in the
format of xxx.xxx.xxx.xxx. If no DNS server is used,
do not enter any values.

Fingerprint Displays the SSH key fingerprint.

Related topics
• Setting the BMC of a server blade on page 2-62
• Strengthening security by using digital certificates on page 2-24
• Registering a user account for logging into the management module and
server blades on page 3-39

Setting the UEFI for a server blade


Use the Web console to change the UEFI settings for a server blade.

Note:
• Specify settings from the UEFI setup menu because some items cannot be
set from a management module. For details about the settings for the
UEFI, see the Hitachi Compute Blade 2500 Series UEFI Setup Guide.
• Change the UEFI settings while the server blade is powered off or after
the OS booting is completed.
If you change the server blade settings after the server blade is powered
on but before the OS is booted, the changes to the UEFI settings might
not be applied.
• After the settings were specified, if N+M cold standby is switched before
the server blade is restarted, the changed values are discarded.

2-76 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To set UEFI from the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. In the EFI tab, click the Edit button to select the item to be edited.
3. Specify the necessary items, and perform the processing.
The specified items are applied after the server blade restarts.

Setting a switch module


When changing the switch module settings, use the CLI console to log in to
the switch module console.
To configure a switch module from the CLI console:
1. Execute the change console command to access the CLI console of a
switch module. To log in to the switch module console, you must enter
the switch module account.

Related topics
• change console on page 5-263

Setting a Hitachi Fibre Channel adapter


To change Hitachi Fibre Channel adapter settings, use the Web console.
To set a Hitachi Fibre Channel adapter from the Web console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. From the I/O card tab, select a Fibre Channel adapter, click the Show
details button, and then click the Edit button.
3. Specify the necessary items, and perform the processing.
The specified items are applied after the server blade restarts.

Note: After the settings were specified, if N+M cold standby is switched
before the server blade is restarted, the changed values are discarded.

Related topics
• Setting items for a Hitachi Fibre Channel adapter on page 2-77

Setting items for a Hitachi Fibre Channel adapter


This section describes items that can be set for a Hitachi Fibre Channel
adapter.

Preparations for Using the Management Module 2-77


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-53 Setting items for a Hitachi Fibre Channel adapter

Item Setting values

HBA BIOS Enable/ Disables or enables the SAN booting functionality.


Disable To detect LUs, specify [Enable].
Normally, enable only the HBA port of the boot path and disable
other HBA ports.
The value that can be set is either Enable or Disable. The initial
setting is Enable.

Connection Type Sets the connection type.


Specifies the connection type of the Fibre Channel interface.
The value that can be set is Auto, Point to Point, or Arbitrated
Loop. The initial setting is Auto.

Data Rate (Gbps) Sets the data transfer rate.


Specifies the data transfer speed of the Fibre Channel interface.
The value that can be set varies depending on the installed card as
shown in the following.
For Hitachi 8Gbps Fibre Channel adapter:
Auto (initial setting), 2Gbps, 4Gbps, or 8Gbps
For Hitachi 16Gbps Fibre Channel adapter:
Auto (initial setting), 4Gbps, 8Gbps, or 16Gbps

Login Delay Time Sets the delay time before login.


(sec) Sets the estimated time, before login to the target port, required for
each piece of equipment to recognize that the Fibre Channel
connection configuration has changed. You need to set a time that
takes into account the configuration scale and the high load status.
The valid value range is 0 to 60 seconds. The initial setting is 3
seconds.

Persistent Binding Sets the persistent binding functionality of the OS driver.


Set Disable to forcibly disable the persistent binding setting saved
on the OS to boot the OS.
This setting is valid only in Linux, and the boot driver is not used. In
addition, the setting value must be the same for all adapters.
The value that can be set is either Enable or Disable. The initial
setting is Enable.

Boot Priority Disables or enables the priority order of LU detection.


Disables or enables the Boot Priority List.
If enabled, the target LU is searched only from the LUs registered in
the Boot Priority List. If disabled, the Boot Priority List is ignored,
and the currently available LUs are searched.
The value that can be set is either Enable or Disable. The initial
setting is Disable.

HBA ISOL cmd Sets the isolation status for HBA port booting. To boot in the
isolated status, set ON.
The value that can be set is either ON or OFF. The initial setting is
OFF.

2-78 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Setting values
This item appears only for the Hitachi 16Gbps Fibre Channel
adapter.

Multiple PortID This parameter is used in combination with Connection Type. Set
Enable to extend the connection form of the direct connection
configuration.
This parameter has restrictions and notes on the environment to be
used. For details, see the manual Hitachi Gigabit Fibre Channel
Adapter User's Guide (BIOS/EFI Edition).
The value that can be set is either Enable or Disable. The initial
setting is Disable.
This item appears only for the Hitachi 16Gbps Fibre Channel
adapter.

Boot Device List This is a list of target LUs for the boot priority setting.
Registers the list of LUs to be searched, when Enable is set for the
Boot Priority.
Only the target LUs that are registered in the list are searched, and
the currently available LUs are not searched even if registered LUs
cannot be detected.

Related topics
• Setting a Hitachi Fibre Channel adapter on page 2-77

Setting WWNs and MAC addresses


This section describes the WWNs and MAC addresses of the system unit.

WWNs and MAC addresses


A system unit can use the following three types of WWNs and MAC
addresses:
• Default Physical WWNs and Default Physical MAC addresses
These are unique and unchangeable WWN and MAC address that Fibre
Channel adapters and LAN mezzanine cards have.
• Optional Physical WWNs and Optional Physical MAC addresses
WWNs and MAC addresses that are additionally assigned to Fibre Channel
adapters and LAN mezzanine cards.
These are rewritable and only used by Compute Blade. Even if a Fibre
Channel adapter or LAN mezzanine card is replaced, Optional Physical
WWNs and Optional Physical MAC addresses do not change as long as the
Fibre Channel mezzanine card or LAN mezzanine card is installed in the
same slot. Therefore, even if a mezzanine card is replaced, you do not
need to change the settings of the LAN switch module and other
associated equipment.

Preparations for Using the Management Module 2-79


Hitachi Compute Blade 2500 Series Management Module User Guide
Optional Physical WWNs are also used by the N+M cold standby
functionality.
• WWNs and MAC addresses used in LPAR manager
WWNs and MAC addresses managed by LPAR manager. For details, see
the Hitachi Compute Blade 2500 Series Logical partitioning manager User
Guide.

Note: Optional Physical MAC addresses cannot be used on the following


adapters:
• 1Gb 4-port LAN adapter
• 10G BASE-SR 2-port LAN adapter
• 10G BASE-T 2-port LAN adapter

Note: If you selected Custom for the Personality setting for the onboard CNA,
you cannot use the functionality that assigns Optional Physical WWNs and
that assigns Optional Physical MAC addresses. If you select Custom, you must
select the Default Physical WWN and the Default Physical MAC address for
operation.

Related topics
• Preparation for running the server blades in a redundant configuration (N
+M cold standby) on page 3-6
• Selecting WWNs and MAC addresses to be used in the Basic mode on
page 2-80
• Selecting WWNs and MAC addresses to be used in the LP mode on page
2-81
• Relation between N+M cold standby and WWN and MAC address on page
2-81

Selecting WWNs and MAC addresses to be used in the Basic mode


In Basic mode, you can select Optional Physical or Default Physical as the
WWN and MAC address types for each server blade.
If you change the WWN or MAC address type, the value of all Fibre Channel
adapters and LAN mezzanine cards that are installed on the server blade
change.

Tip:
• The Optional Physical type does not change the WWN or MAC address
when a mezzanine card is replaced. Therefore, the influence on the OS
and external devices can be minimized.
• In an SMP configuration, the settings for the primary server blade are
applied to all server blades constituting the SMP configuration. You do not
need to configure settings for non-primary server blades.
Set a WWN and MAC address of Basic mode from the Web console or the CLI
console.

2-80 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To set a WWN and MAC address for Basic mode from the Web
console:
1. In the Resources tab, from the tree view under Modules, select the
target server blade.
2. In the Settings tab, click the Edit Server Blade settings button.
The Server Blade n settings dialog box appears.
3. In Smart Configure, set WWN type and MAC type.
To set a WWN and MAC address for Basic mode from the CLI console:
1. See the following Table 2-54 Commands used for setting WWNs and MAC
addresses in Basic mode on page 2-81.

Table 2-54 Commands used for setting WWNs and MAC addresses in Basic
mode

Operation item Command

Displaying the WWN type show blade setting

Setting the WWN type set blade preconf

Displaying the MAC type show blade setting

Setting the MAC type set blade preconf

Related topics
• WWNs and MAC addresses on page 2-79
• show blade setting on page 5-76
• set blade preconf on page 5-51

Selecting WWNs and MAC addresses to be used in the LP mode


In LP mode, setting the WWN type is not required because the WWNs that
are used in LPAR manager are always used.
If a PCI device is shared, the MAC address that is used in LPAR manager is
used regardless of the MAC type setting. If a PCI device is used in dedicated
mode, the MAC address specified as the MAC type is used.

Relation between N+M cold standby and WWN and MAC address
To run N+M cold standby in Basic mode, Optional Physical WWNs are always
used. When an N+M failover occurs, SAN connections are inherited by setting
the Optional Physical WWNs of the Fibre Channel adapter that is installed in
the active server blade to the Fiber Channel adapter of the standby server
blade.
In N+M cold standby, even if an N+M failover is performed, the WWNs
recognized by the OS on the server blade do not change. Therefore, any

Preparations for Using the Management Module 2-81


Hitachi Compute Blade 2500 Series Management Module User Guide
software functionality (such as Persistent Binding) that depends on a WWN
can be used without any changes.
For a MAC address, you can select the Default Physical MAC address or an
Optional Physical MAC address, according to the MAC type setting. If you
select an Optional Physical MAC address, the MAC address value is inherited
when an N+M failover is performed. The MAC addresses recognized by the
OS on the server blade are not changed even if an N+M failover is performed.
Therefore, you can specify OS settings that depend on the MAC address.
When running the N+M cold standby in LP mode, the WWN and MAC address
that are used in LPAR manager are inherited when an N+M failover is
performed. As in Basic mode, the WWNs and MAC addresses recognized by
the OS on the server blade are not changed even if an N+M failover is
performed. Therefore, any software functionality that depends on a WWN or
MAC address can be used.

Related topics
• Preparation for running the server blades in a redundant configuration (N
+M cold standby) on page 3-6

Initializing Optional Physical WWNs and Optional Physical MAC


addresses
In the N+M cold standby, another server blade can inherit Optional Physical
WWNs and MAC addresses. When changing back to the Optional Physical
WWN and MAC address that were set before N+M was switched, initialize or
change the Optional Physical WWN and MAC address from the Web console.

Tip: When server blades are in an SMP configuration, all server blades
constituting the SMP configuration are the target of the initialization and
change.

Related topics
• Initializing or changing Optional Physical WWNs on page 2-82
• Initializing or changing Optional Physical MAC addresses on page 2-83

Initializing or changing Optional Physical WWNs


This section explains how to initialize or change Optional Physical WWNs.

Information you need to check in advance


• Optional Physical WWNs before they are changed
To initialize or change Optional Physical WWNs from the Web
console:
1. From the Systems tree view in the Resources tab, click WWN
Management.

2-82 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
2. Select the target server blade, and then in the Show details menu, click
Optional Physical WWN.
The Optional Physical WWN List window appears.
3. Click the Edit button or the Initialize button, and then set an Optional
Physical WWN.
If you click the Initialize button, the setting of the Optional Physical
WWN returns to the initial settings (the settings at shipping time).
To change Optional Physical WWNs from the CLI console:
1. Execute the set wwn additional command.

Related topics
• Initializing Optional Physical WWNs and Optional Physical MAC addresses
on page 2-82
• set wwn additional on page 5-8

Initializing or changing Optional Physical MAC addresses


This section explains how to initialize or change Optional Physical MAC
addresses.

Information you need to check in advance


• Optional Physical MAC addresses before they are changed
To initialize or change Optional Physical MAC addresses from the Web
console:
1. From the Systems tree view in the Resources tab, click MAC
Management.
2. Select the target server blade, and then from the Show details menu,
click Optional Physical MAC.
The Optional Physical WWN List window appears.
3. Click the Edit button or the Initialize button, and then set an Optional
Physical MAC address.
If you click the Initialize button, the setting of the Optional Physical MAC
address returns to the initial settings (the settings at shipping time).
To change Optional Physical MAC addresses from the CLI console:
1. Execute the set mac additional command.

Related topics
• Initializing Optional Physical WWNs and Optional Physical MAC addresses
on page 2-82
• set mac additional on page 5-7

Preparations for Using the Management Module 2-83


Hitachi Compute Blade 2500 Series Management Module User Guide
WWNs and MAC addresses that can be checked in management
module consoles
You can check information in the following table from the Web console or CLI
console of a management module. By checking the information from the
management module, you can check the values of WWNs and MAC addresses
without needing to turn on the server blade and then checking the
information on the OS window or UEFI window. In addition, by listing the
WWNs and MAC addresses of the mezzanine cards installed on the server
blade, you can check the currently used WWNs and MAC addresses at a
glance.

Table 2-55 Information that can be checked on each console

LCD touch
Item Web console CLI console
console

Default Physical WWN Y Y N

Optional Physical WWN Y Y N

Currently used WWN Y Y N

Default Physical MAC Y Y N


address

Optional Physical MAC Y Y N


address

Currently used MAC Y Y N


address

WWNs used in LPAR Y N N


manager1

MAC addresses used in Y N N


LPAR manager1

Legend:
Y : Supported
N : Not supported
Notes:
1. For details about how to check WWNs and MAC addresses that are used by LPAR
manager, see the Hitachi Compute Blade 2500 Series Logical partitioning manager
User Guide.

Note:
• The WWNs and MAC addresses that are changed from a management
module will be applied to the actual Fibre Channel adapters and LAN
mezzanine cards the next time the server blade is turned on. For this
reason, if you do not turn on the server blade after changing WWNs or
MAC addresses, the values of the current WWNs or current MAC
addresses displayed on the management module consoles might be
different from the value assigned to the actual Fibre Channel adapters or
LAN mezzanine cards.

2-84 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• For onboard CNA, WWNs displayed in the Web console or the CLI console
are shown in Table 2-56 WWNs displayed in the Web and CLI consoles on
page 2-85.
Because the onboard CNA has only one controller, Current WWN and
Default Physical WWN are displayed only for port 0 and port 1.
If Personality for onboard CNA is not set to FCoE, the current WWN and
Default Physical WWN cannot be shown. In that case, the following
message appears.
For the Web console:
Not card installed Not exist WWN Information
For the CLI console:
WWN information does not exist

Table 2-56 WWNs displayed in the Web and CLI consoles

Port World wide port name World wide node name

0 World wide port name for port 0 of World wide node name for port 0 of
controller 0 controller 0

1 World wide port name for port 1 of World wide node name for port 1 of
controller 0 controller 0

2 World wide port name for port 0 of World wide node name for port 0 of
controller 1 controller 1

3 World wide port name for port 1 of World wide node name for port 1 of
controller 1 controller 1

Related topics
• Checking the Default Physical WWN on page 2-85
• Checking Optional Physical WWNs on page 2-86
• Checking the currently used WWN on page 2-86
• Checking the Default Physical MAC address on page 2-86
• Checking Optional Physical MAC addresses on page 2-87
• Checking the currently used MAC addresses on page 2-87
• What you can check in the change log for Optional Physical WWNs and
MAC addresses on page 2-87

Checking the Default Physical WWN


This section explains how to check the Default Physical WWN information
from the Web console and the CLI console.
To check the Default Physical WWN from the Web console:
1. From the Systems tree view in the Resources tab, click WWN
Management.
2. From the Show details menu, click Default Physical WWN.

Preparations for Using the Management Module 2-85


Hitachi Compute Blade 2500 Series Management Module User Guide
To check the Default Physical WWN from the CLI console:
1. Execute the show wwn original command.

Related topics
• show wwn original on page 5-25

Checking Optional Physical WWNs


To check Optional Physical WWNs, use the Web console.
To check Optional Physical WWNs from the Web console:
1. From the Systems tree view in the Resources tab, click WWN
Management.
2. From the Show details menu, click Optional Physical WWN.
To check Optional Physical WWNs from the CLI console:
1. Execute the show wwn additional command.

Related topics
• show wwn additional on page 5-20

Checking the currently used WWN


To check the currently used WWN, use either the Web console or the CLI
console.
To check the currently used WWN from the Web console:
1. From the Systems tree view in the Resources tab, click WWN
Management.
2. Click the Show Current WWN button.
To check the currently used WWN from the CLI console:
1. Execute the show wwn current command.

Related topics
• show wwn current on page 5-23

Checking the Default Physical MAC address


To check the Default Physical MAC address, use either the Web console or the
CLI console.
To check the Default Physical MAC address from the Web console:
1. From the Systems tree view in the Resources tab, click MAC
Management.

2-86 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
2. From the Show details menu, click Default Physical MAC.
To check the Default Physical MAC address from the CLI console:
1. Execute the show mac original command.

Related topics
• show mac original on page 5-18

Checking Optional Physical MAC addresses


To check Optional Physical MAC addresses, use the Web console.
To check Optional Physical MAC addresses from the Web console:
1. From the Systems tree view in the Resources tab, click MAC
Management.
2. From the Show details menu, click Optional Physical MAC.
To check Optional Physical MAC addresses from the CLI console:
1. Execute the show mac additional command.

Related topics
• show mac additional on page 5-14

Checking the currently used MAC addresses


To check the currently used MAC addresses, use either the Web console or
the CLI console.
To check the currently used MAC addresses from the Web console:
1. From the Systems tree view in the Resources tab, click MAC
Management.
2. Click the Show Current MAC button.
To check the currently used MAC addresses from the CLI console:
1. Execute the show mac current command.

Related topics
• show mac current on page 5-16

What you can check in the change log for Optional Physical WWNs
and MAC addresses
Management module logs changes caused by operations such as changing
settings or initialization of Optional Physical WWNs or MAC addresses,

Preparations for Using the Management Module 2-87


Hitachi Compute Blade 2500 Series Management Module User Guide
inheriting information by using N+M cold standby. You can check the change
log from the CLI console.
The change log records time, values before and after the change, the trigger
for the change (either failover by the N+M cold standby or a change from a
console). After a change, you can check the times when Optional Physical
WWNs or MAC addresses were changed, how they were changed, and what
triggered the change.

Related topics
• Checking the Optional Physical WWN change log on page 4-3
• Checking the Optional Physical MAC address change log on page 4-4

Controlling power consumption by using the power control


functionality
This section describes the functionality that controls power usage of the
system unit.

Power control functionality


The system unit provides accurate power control (APC) functionality and the
Data Center Manageability Interface (DCMI). A management module
automatically calculates the allowable setting range for APC functionality
based on the power supply module configuration and accurate power control
settings.
The following table indicates settings related to the power control
functionality. You can change these settings, except the setting that enables
or disables the DCMI mode, while the server blades are powered on.
However, the management module automatically limits the allowable range
to prioritize the continuous operation of server blades.

Table 2-57 Settings related to the power control functionality

Item Description

Power supply Redundancy Sets power supply module redundancy for


module the system unit:
configuration • 200 VAC - 240 VAC: N+N/N+1
(default)
The management module automatically
calculates the power capacity usable by
the system unit based on this setting.

Power capacity expansion Disables or enables the power capacity


functionality expansion functionality.
• Disable or Enable (default)

2-88 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description
The management module automatically
calculates the power capacity usable by
the system unit based on this setting.

Accurate power Setting the accurate power Sets the upper limit for the power
control (APC) control upper limit consumption while operating the
settings equipment.
You cannot set a value that exceeds the
range from the maximum power supply of
the system unit to the minimum power
consumption of the system unit.
In the initial settings (the settings at
shipping time), this value is set to the
maximum power supply of the system
unit.
The minimum power consumption of the
system unit is the sum of the rated power
of installed modules to which the
maximum power consumption of when the
maximum power capping is applied to the
APC-enabled server blades is applied.

Enable/Disable APC for You can select target server blades for
server blade power capping (power control).
In the initial settings (the settings at
shipping time), the setting is [Enable].
Changing this value will change the
minimum power consumption of the
system unit. The accurate power control
upper limit cannot be less than the
minimum power consumption of the
system unit.

DCMI mode Enabling and disabling the Enables or disables the DCMI mode for
settings DCMI mode for the entire the entire server chassis.
server chassis In the initial settings (the settings at
shipping time), the setting is [Disable].
You can enable or disable the DCMI mode
only when all server blades that support
DCMI in the server chassis have been
initialized and the main power is powered
off.
The DCMI mode and the APC functionality
are mutually exclusive. Therefore, you
cannot use both at the same time.

Tip: We recommend that you use the APC for power control functionality
because DCMI cannot use the management module to control power for the
entire chassis.
In addition, to use DCMI, server blades need to support DCMI. Select the
power control functionality to be used depending on the intended use.

Preparations for Using the Management Module 2-89


Hitachi Compute Blade 2500 Series Management Module User Guide
Accurate power control (APC) functionality
The accurate power control (APC) functionality restricts the power
consumption during system unit operation to the power consumption upper
limit or less, by using the power capping (power control) functionality of the
server blade.
If excess power consumption is detected for a server blade, this functionality
controls power consumption by reducing the clock rate of the server blade to
the optimum level so that power consumption is at or below the upper limit.
The management module automatically calculates and assigns the ratio of
performance suppression for each server blade so that the ratio is uniform to
the capping capability of each server blade.

Tip:
• For server blades that cannot tolerate momentary performance
suppression, before setting the accurate power control upper limit, disable
the APC setting.
If you cannot allow momentary performance degradation in all server
blades, review the accurate power control upper limit, the APC setting for
server blades, the power supply module configuration, and the power
supply facility environment settings.
In a virtual environment, we recommend that the APC functionality is
disabled on virtual servers because the performance of all virtual
machines on the virtual servers is degraded.
The following table describes the consoles used when you set the APC
functionality from a management module.

Table 2-58 Setting the APC functionality

Operation Web console CLI console LCD touch console

Using the APC functionality Y -- --


to set the upper limit on
power consumption during
the system unit operation

Related topics
• Setting the upper limit on power consumption during system unit
operation on page 2-90

Setting the upper limit on power consumption during system unit


operation
To use the APC functionality to set the upper limit on power consumption
during the system unit operation, use the Web console.

2-90 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To set the APC functionality from the Web console:
1. From the Systems tree view in the Resources tab, click Power
Management.
2. From the Action pull-down menu, click Edit accurate power control
(APC).
Set the power consumption upper limit for the equipment.

Related topics
• Server blade operation for when the upper limit on power consumption
during system unit operation is set on page 2-91

Server blade operation for when the upper limit on power


consumption during system unit operation is set
The following example shows an overview of the operation when the accurate
power control upper limit of the system unit is set to 2,000 W.
The following conditions are assumed:
• Accurate power control upper limit of the system unit: 2,000 W
• Power consumed by modules other than server blades: 800 W. > Power
usable by server blades: 1,200 W.
• Power consumption specification for server blades: Rated power
(maximum power consumption): 400 W, Maximum power consumption
when power capping is applied to the maximum: 150 W
• Number of installed server blades: 4 with the same power consumption
specifications
• APC: Enabled > The power consumption per server blade is limited to 300
W or less.
1. When the accurate power control upper limit of the system unit is 2,400
W or more:

Preparations for Using the Management Module 2-91


Hitachi Compute Blade 2500 Series Management Module User Guide
2. When the accurate power control upper limit of the system unit is set to
2,000 W by using the APC functionality:

Related topics
• Setting the upper limit on power consumption during system unit
operation on page 2-90

2-92 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Disabling power control for server blades
For server blades that cannot tolerate performance suppression, by disabling
power control, you can remove desired server blades from capping targets.
When server blades are in an SMP configuration, the settings for the primary
server blade are applied to non-primary server blades.
The following table describes the consoles used when you disable power
control for server blades from a management module.

Table 2-59 Disabling power control for server blades

Operation Web console CLI console LCD touch console

Disabling power control for Y Y --


server blades

Related topics
• Disabling power control for server blades on page 2-93

Disabling power control for server blades


To disable power control for server blades, use either the Web console or the
CLI console.

Tip: When server blades are in an SMP configuration, the settings for the
primary server blade are applied to non-primary server blades.

To disable power control for server blades from the Web console:
1. From the Systems tree view in the Resources tab, click Power
Management.
2. From the Server blade tab, select the target server blade and then Edit
power capping.
Set the APC functionality for the selected server blade.
To disable power control for server blades from the CLI console:
1. To check settings of the APC, execute the show power setting
command. To change the settings, execute the set power capping
command.

Related topics
• show power setting on page 5-143
• set power capping on page 5-138
• Behavior of the APC functionality for the system unit when the power
control is disabled for server blades on page 2-94

Preparations for Using the Management Module 2-93


Hitachi Compute Blade 2500 Series Management Module User Guide
Behavior of the APC functionality for the system unit when the
power control is disabled for server blades
The following example shows the operation overview when the accurate
power control upper limit of the system unit is set to 2,000 W and power
capping is disabled for two server blades.
The following conditions are assumed:
• Accurate power control upper limit of the system unit: 2,000 W
• Power consumed by modules other than server blades: 800 W. > Power
usable by server blades: 1,200 W.
• Power consumption specification for server blades: Rated power
(maximum power consumption): 400 W, Maximum power consumption
when power capping is applied to the maximum: 150 W
• Number of installed server blades: 4
• APC is disabled for server blades 1 and 2. > The power consumption for
each of server blades 3 and 4 is limited to 200 W. This is because server
blades 3 and 4 share 400 W, which is the result of multiplying 400 W (the
rated power of server blades 1 and 2) by 2 and then subtracting the
result from 1,200 W (the power usable by server blades).

Note: As shown in the following example, when the rated power of server
blades whose power capping is disabled is subtracted from the power that
can be consumed by server blades and the remaining value is shared by
other server blades, power control cannot be disabled if the remaining value
is less than the maximum power consumption of when power capping is
applied to the maximum.
• Accurate power control upper limit of the system unit: 2,000 W
• Power consumed by modules other than server blades: 700 W. > Power
usable by server blades: 1,300 W.
• Power consumption specification for server blades: Rated power
(maximum power consumption): 400 W, Maximum power consumption
when power capping is applied to the maximum: 150 W
• Number of installed server blades: 4
• APC is disabled for server blades 1, 2, and 3. > This power control cannot
be disabled. This is because the result of multiplying 400 W (the rated
power of server blades 1, 2, and 3) by 3 and then subtracting from 1,300
W (power usable by server blades) is 100 W and is less than 150 W which
is the maximum power consumption of when power capping is applied to
the maximum.
1. When the accurate power control upper limit of the system unit is 2,400
W or more:

2-94 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
2. When the accurate power control upper limit of the system unit is set to
2,000 W:

3. When the power control is disabled for server blades 1 and 2:

Preparations for Using the Management Module 2-95


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Disabling power control for server blades on page 2-93

DCMI
CB 2500 supports the Data Center Manageability Interface (DCMI) version
1.5. If you issue a DCMI command (IPMI command base) from the OS of a
server blade or an external management PC that is connected by the LAN to
BMC of a server blade that supports DCMI, you can manage the power supply
and monitor various environmental values.
To use DCMI, you need to set the DCMI mode of the server chassis to
[Enable] beforehand. Server blades that support DCMI can receive DCMI
commands only when the DCMI mode is enabled. Server blades that do not
support DCMI are unable to receive DCMI commands even if the DCMI mode
is enabled.

Note:
• You cannot use both DCMI and APC functionality at the same time. If you
enable DCMI mode, the APC functionality is automatically disabled and
you cannot change the settings.
• You can enable or disable DCMI mode only when all server blades that
support DCMI in the server chassis have been initialized and the main
power is powered off.
• If you enable DCMI mode, the settings of the APC functionality are
initialized. Similarly, if you disable DCMI mode, the DCMI settings are
initialized.

2-96 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• If power supply is insufficient due to a power failure, etc., while DCMI
mode is enabled, forced power capping by the management module is
preferentially performed so that the equipment can continue operating.
To use DCMI, server blades need to support DCMI. For details about server
blades that support DCMI, see the specifications of each server blade
described in an appendix of the Hitachi Compute Blade 2500 Series Getting
Started Guide.

Related topics
• Enabling and disabling the DCMI mode on page 2-97
• Manual Hitachi Compute Blade 2500 Series Getting Started Guide

Enabling and disabling the DCMI mode


To enable or disable the DCMI mode, use the Web console or the CLI console.
If you change the setting that switches the DCMI mode, the server blades
that support DCMI are automatically reinitialized.
To set the DCMI mode from the Web console:
1. From the Systems tree view in the Resources tab, click Power
Management.
2. From the Action pull-down menu, select DCMI mode.
Enable or disable the DCMI mode.
To set the DCMI mode from the CLI console:
1. Execute the set power dcmi-mode command.
If you change the DCMI mode and then server blades that support DCMI
are reinitialized, check the system event log to make sure that the
initialization of the target server blades is completed.
If you use the Web console for to check the system event log, in the
Resources tab, select Server blades from the tree view under
Modules, select the server blade to be checked, and then make sure that
Initialization Status is OK in the Condition tab of the server blade.

Note: Do not change the setting that switches DCMI mode while updating
Integrated firmware on a server blade that supports DCMI.
To change the setting that switches DCMI mode, first check each server blade
that supports DCMI to make sure that Integrated firmware is not being
updated. If you update the Integrated firmware, check the system event log
before the DCMI mode setting that switches DCMI mode and then make sure
that the target server blade was initialized normally.

Related topics
• DCMI on page 2-96
• set power dcmi-mode on page 5-139

Preparations for Using the Management Module 2-97


Hitachi Compute Blade 2500 Series Management Module User Guide
List of supported DCMI commands
The following table shows the commands supported by CB 2500 from among
the commands defined in DCMI version 1.5.

Table 2-60

Min Privilege Support of CB


DCMI command NetFn CMD
Level 2500
Get DCMI Capabilities DCGRP (2Ch, 01h Session-less Y
Info 2Dh)
Set DCMI DCGRP (2Ch, 12h Admin Y
Configuration 2Dh)
Parameters

Get DCMI DCGRP (2Ch, 13h User Y


Configuration 2Dh)
Parameters

Get Management DCGRP (2Ch, 09h User Y


Controller Identifier 2Dh)
String

Set Management DCGRP (2Ch, 0Ah Admin Y


Controller Identifier 2Dh)
String

Get Asset Tag DCGRP (2Ch, 06h User Y


2Dh)
Set Asset Tag DCGRP (2Ch, 08h Operator Y
2Dh)
Get Device ID App (06h, 07h) 01h User Y
Get System GUID App (06h, 07h) 37h User Y
Get Chassis Chassis (00h, 00h User Y
Capabilities 01h)
Get Chassis Status Chassis (00h, 01h User Y
01h)
Chassis Control Chassis (00h, 02h Operator Y
01h)
Chassis Identify Chassis (00h, 04h Operator Y
01h)
Get ACPI Power State App (06h, 07h) 07h User Y
Set System Boot Chassis (00h, 08h Operator N1
Options 01h)
Get System Boot Chassis (00h, 09h Operator Y
Options 01h)
Get SEL Info Storage (0Ah, 40h User Y
0Bh)
Reserve SEL Storage (0Ah, 42h User Y
0Bh)

2-98 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Min Privilege Support of CB
DCMI command NetFn CMD
Level 2500
Get SEL Entry Storage (0Ah, 43h User Y
0Bh)
Clear SEL Storage (0Ah, 47h Operator Y
0Bh)
Get DCMI Sensor Info DCGRP (2Ch, 07h Operator Y
2Dh)
Get SDR Repository Storage (0Ah, 20h Operator Y
Info 0Bh)
Reserve SDR Storage (0Ah, 22h Operator Y
Repository 0Bh)
Get SDR Storage (0Ah, 23h User Y
0Bh)
Get Sensor Threshold S/E (04h, 05h) 27h Operator Y
Get Sensor Reading S/E (04h, 05h) 2Dh User Y
Set Sensor Event S/E (04h, 05h) 28h Operator N
Enable

Get Sensor Event S/E (04h, 05h) 29h User N


Enable

Get Power Reading DCGRP (2Ch, 02h User Y


2Dh)
Get Power Limit DCGRP (2Ch, 03h User Y
2Dh)
Set Power Limit DCGRP (2Ch, 04h Operator Y
2Dh)
Activate/Deactivate DCGRP (2Ch, 05h Operator Y
Power Limit 2Dh)
Set Thermal Limit DCGRP (2Ch, 0Bh Operator Y
2Dh)
Get Thermal Limit DCGRP (2Ch, 0Ch User Y
2Dh)
Get Temperature DCGRP (2Ch, 10h User Y
Readings 2Dh)
Reset Watchdog Timer App (06h, 07h) 22h Operator11 Y
Set Watchdog Timer App (06h, 07h) 24h Operator11 Y
Get Channel App (06h, 07h) 38h None Y
Authentication
Capabilities

Set Session Privilege App (06h, 07h) 3Bh User Y


Level

Close Session App (06h, 07h) 3Ch User10 Y


Get Session Info App (06h, 07h) 3Dh User Y

Preparations for Using the Management Module 2-99


Hitachi Compute Blade 2500 Series Management Module User Guide
Min Privilege Support of CB
DCMI command NetFn CMD
Level 2500
Get Payload App (06h, 07h) 4Ah User Y
Activation Status

Get Payload Instance App (06h, 07h) 4Bh User Y


Info

Get Channel Payload App (06h, 07h) 4Eh User Y


Support

Activate Payload App (06h, 07h) 48h Configurable7 Y


Deactivate Payload App (06h, 07h) 49h Configurable7 Y
Get Channel Cipher App (06h, 07h) 54h None Y
Suites

SOL Activating Transport 20h None Y


(0Ch, 0Dh)
Set LAN Configuration Transport 01h Admin Y
Parameters (0Ch, 0Dh)
Get LAN Configuration Transport 02h Operator Y
Parameters (0Ch, 0Dh)
Set Channel Access App (06h, 07h) 40h Admin Y
Get Channel Access App (06h, 07h) 41h User Y
Get Channel Info App (06h, 07h) 42h User Y
Set User Access App (06h, 07h) 43h Admin Y
Get User Access App (06h, 07h) 44h Operator Y
Set User Name App (06h, 07h) 45h Admin Y
Get User Name App (06h, 07h) 46h Operator Y
Set User Password App (06h, 07h) 47h Admin Y
Set User Payload App (06h, 07h) 4Ch Admin Y
Access

Get User Payload App (06h, 07h) 4Dh Operator Y


Access

Set SOL Configuration Transport 21h Admin Y


Parameters (0Ch, 0Dh)
Get SOL Configuration Transport 22h User Y
Parameters (0Ch, 0Dh)
Set BMC Global App (06h, 07h) 2Eh system interface Y
Enables

Get BMC Global App (06h, 07h) 2Fh system interface, Y


Enables User
Clear Message Flags App (06h, 07h) 30h system interface Y
Get Message Flags App (06h, 07h) 31h system interface Y
Get Message App (06h, 07h) 33h System Interface Y

2-100 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Min Privilege Support of CB
DCMI command NetFn CMD
Level 2500
Send Message App (06h, 07h) 34h User Y

Legend:
Y: Supported by CB 2500
N: Not supported by CB 2500
Note:
1. The command is finished normally, but the setting is not reflected.

Related topics
• DCMI on page 2-96

Power capacity expansion functionality


In a power supply redundant configuration, the power supply expansion
functionality expands the available power by using surplus power of standby
power systems when both active and standby systems are in normal
operation. This functionality eases the restriction for installing server blades
and restriction of performance caused by applying power capping to server
blades.
When redundant power supply fails, this functionality prevents the power
overload that exceeds the allowable power of power supply modules in the
system unit by applying high-speed power capping to the server blades to
return the available power within the rated value. To achieve the power
supply expansion functionality, the power supply module whose power
receiving performance has improved is adopted.
The following show the summaries of operations in which the power capacity
expansion functionality is enabled and disabled.
The following shows an example when six power supply modules are
mounted in an N+N redundant configuration.

Summary of operation when the power capacity expansion


functionality is disabled
Normal operation of redundant power supply: Maximum supplied power is
7,395 W
Two power supply systems supply 3,697.5 W each.

Preparations for Using the Management Module 2-101


Hitachi Compute Blade 2500 Series Management Module User Guide
Failure of redundant power supply: Maximum supplied power is 7,395 W
If one power supply system fails, the other power supply system supplies
7,395 W.

Summary of operation when the power capacity expansion


functionality is enabled (default)
Normal operation of redundant power supply: Maximum supplied power is
9,480 W
Two power supply systems supply 4,740 W each.

2-102 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Failure of redundant power supply: Maximum supplied power is 9,480 W >
7,395 W (high-speed capping for expanded power)
If one power supply system fails, the other power supply system supplies
9,480 W.
The rated power supply capacity of the power supply module is exceeded,
therefore high-speed capping is applied to the expanded amount of power
supply.

The following shows an example when six power supply modules are
mounted in an N+1 redundant configuration.

Preparations for Using the Management Module 2-103


Hitachi Compute Blade 2500 Series Management Module User Guide
Summary of operation when the power capacity expansion
functionality is disabled
Normal operation of redundant power supply: Maximum supplied power is
12,325 W
Two power supply systems supply 6,162.5 W each.

Failure of redundant power supply: Maximum supplied power is 12,325 W


If a failure occurs on one power supply module, the other power supply
modules supply a total of 12,325 W of power.

Summary of operation when the power capacity expansion


functionality is enabled (default)
Normal operation of redundant power supply: Maximum supplied power is
14,790 W
Two power supply systems supply 7,395W each.

2-104 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Failure of redundant power supply: Maximum supplied power is 14,790 W >
12,325 W (high-speed capping for expanded power)
If a failure occurs on one power supply module, the other power supply
modules supply a total of 14,790 W of power.

The following table describes the consoles used when you set the power
capacity expansion functionality from a management module.

Preparations for Using the Management Module 2-105


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 2-61 Power capacity expansion functionality settings

Operation Web console CLI console LCD touch console

Using the power capacity Y Y --


expansion functionality to
expand the usable power.

Related topics
• Power supply according to the number of installed power supply modules
on page 2-106
• Using surplus power to expand the usable power on page 2-108

Power supply according to the number of installed power supply


modules
The following table shows the number of installed power supply modules and
the amount of the power that can be supplied.

Table 2-62 Power supply in an N+N redundant configuration

Power capacity Power supply for each configuration of power


Power supply status expansion supply modules (N+N)
functionality 2 (1+1) 4 (2+2) 6 (3+3)

Normal operation of Disabled Maximum 2,465 Maximum 4,930 Maximum 7,395


redundant power supply W W W

Enabled Maximum 3,160 Maximum 6,320 Maximum 9,480


W W W

Abnormal operation of Disabled Maximum 2,465 Maximum 4,930 Maximum 7,395


redundant power supply W W W
(when a failure occurs on
one power supply module) Enabled Maximum 2,465 Maximum 6,320 Maximum 9,480
W W W

Abnormal operation of Disabled The system unit Maximum 4,930 Maximum 7,395
redundant power supply is shut down. W W
(when a failure occurs on
two power supply modules) Enabled The system unit Maximum 4,930 Maximum 9,480
is shut down. W W

Abnormal operation of Enabled/Disabled -- Maximum 2,465 Maximum 7,395


redundant power supply W W
(when a failure occurs on
three power supply
modules)

Abnormal operation of Enabled/Disabled -- The system unit Maximum 4,930


redundant power supply is shut down. W
(when a failure occurs on
four power supply modules)

2-106 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Power capacity Power supply for each configuration of power
Power supply status expansion supply modules (N+N)
functionality 2 (1+1) 4 (2+2) 6 (3+3)

Abnormal operation of Enabled/Disabled -- -- Maximum 2,465


redundant power supply W
(when a failure occurs on
five power supply modules)

Abnormal operation of AC Enabled/Disabled Maximum 2,465 Maximum 4,930 Maximum 7,395


power supply (when a W W W
failure occurs on one AC
power supply)

Abnormal operation of AC Enabled/Disabled The system unit The system unit The system unit
power supply (when a is shut down. is shut down. is shut down.
failure occurs on two AC
power supplies)

Legend:
--: Not supported.

Table 2-63 Power supply in an N+1 redundant configuration

Power Power supply for each configuration of power supply


capacity modules (N+1)
Power supply status
expansion
functionality 2 (1+1) 3 (2+1) 4 (3+1) 5 (4+1) 6 (5+1)

Normal operation of Disabled Maximum Maximum Maximum Maximum Maximum


redundant power supply 2,465 W 4,930 W 7,395 W 9,860 W 12,325 W

Enabled Maximum Maximum Maximum Maximum Maximum


3,160 W 6,320 W 9,480 W 12,325 W 14,790 W

Abnormal operation of Enabled/ Maximum Maximum Maximum Maximum Maximum


redundant power supply Disabled 2,465 W 4,930 W 7,395 W 9,860 W 12,325 W
(when a failure occurs on
one power supply module)

Abnormal operation of Enabled/ The Maximum Maximum Maximum Maximum


redundant power supply Disabled system 2,465 W 4,930 W 7,395 W 9,860 W
(when a failure occurs on unit is shut
two power supply down.
modules)

Abnormal operation of Enabled/ -- The Maximum Maximum Maximum


redundant power supply Disabled system 2,465 W 4,930 W 7,395 W
(when a failure occurs on unit is shut
three power supply down.
modules)

Abnormal operation of Enabled/ -- -- The Maximum Maximum


redundant power supply Disabled system 2,465 W 4,930 W
(when a failure occurs on unit is
four power supply shut
modules) down.

Preparations for Using the Management Module 2-107


Hitachi Compute Blade 2500 Series Management Module User Guide
Power Power supply for each configuration of power supply
capacity modules (N+1)
Power supply status
expansion
functionality 2 (1+1) 3 (2+1) 4 (3+1) 5 (4+1) 6 (5+1)

Abnormal operation of Enabled/ -- -- -- The Maximum


redundant power supply Disabled system 2,465 W
(when a failure occurs on unit is
five power supply shut
modules) down.

Abnormal operation of AC Enabled/ The The The The The


power supply Disabled system system system system system
unit is shut unit is shut unit is unit is unit is
down. down. shut shut shut
down. down. down.

Legend:
--: Not supported.

Related topics
• Power capacity expansion functionality on page 2-101

Using surplus power to expand the usable power


To expand usable power by using the power capacity expansion functionality,
use the Web console or the CLI console.
To set the power capacity expansion functionality from the Web
console:
1. From the Systems tree view in the Resources tab, click Power
Management.
2. From the Action pull-down menu, select Power capacity expansion
feature.
Disable or enable the power capacity expansion functionality.
To set the power capacity expansion functionality from the CLI
console:
1. Execute the set power power-expansion command.

Related topics
• set power power-expansion on page 5-140

Displaying monitored electric power values


On management module consoles, you can check information about electric
power values of the entire system unit and server blades.

2-108 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Two types of power consumption data are displayed: the current power
consumption and the history of power consumption. In the history of power
consumption, you can check a maximum of 48 hours of data from the
previous day to the current day.
In an SMP configuration, the total power consumption of all server blades
constituting the SMP configuration is displayed as the power consumption
data for the primary server blade.
The CPU frequency is displayed per server blade. Multiple CPUs in a server
blade have the same frequency.
The following table describes the consoles used when you monitor electric
power values from a management module.

Table 2-64 Displaying monitored electric power values

Operation Web console CLI console LCD touch console

Checking currently used Y -- --


electric energy

Checking power usage Y Y --


history

Related topics
• Checking electric power usage on page 2-109

Checking electric power usage


To check the electric power usage, use either the Web console or the CLI
console.
To check the power usage from the Web console:
1. From the Systems tree view in the Resources tab, click Power
Management.
Displays the current input power and power consumption.
2. To check the history of power usage, from the Action pull-down menu,
select Download chassis power history.
The server chassis power history is downloaded. You can obtain a history
of the 24 hours from the previous day, the most recent 24 hours, or a
maximum of 48 hours from 0:00 of the previous day to the present time.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.

Preparations for Using the Management Module 2-109


Hitachi Compute Blade 2500 Series Management Module User Guide
In such a case, download the file again.
To check the power usage from the CLI console:
1. To check the power usage history, execute the show log power
command.

Related topics
• show log power on page 5-248

Setting the power-off sequence for server blades when the power
capacity is exceeded
If the currently consumed amount of electric power can no longer be supplied
because of a power supply module failure or other reason, the management
module forcibly powers off some server blades to restrict the number of
running server blades to the number for which power can be supplied. Set the
order in which server blades are to be powered off by the management
module.
In the initial settings (the settings at shipping time) of the system unit,
server blades are set to be powered off in the following order: 15, 14, 13, 12,
11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1.
When server blades are in an SMP configuration, set the primary server blade
number.
The following table shows consoles that are used to set the power-off
sequence from a management module.

Table 2-65 Setting the power-off sequence for server blades when the
power capacity is exceeded

Operation Web console CLI console LCD touch console

Setting server blades to be Y Y --


forcibly powered off when
the power that can be
supplied to the system unit
is insufficient

Related topics
• Setting the forced-power-off sequence for server blades when the power
that can be supplied to the system unit is insufficient on page 2-110

Setting the forced-power-off sequence for server blades when the


power that can be supplied to the system unit is insufficient
To set the server blades to be forcibly powered off when the power that can
be supplied to the system unit is insufficient, use the Web console or the CLI
console.

2-110 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To set the forced-power-off sequence for server blades from the Web
console:
1. From the Systems tree view in the Resources tab, click Power
Management.
2. From the Action pull-down menu, click Edit server blade power OFF
sequence.
Set the order in which server blades are to be forcibly powered off when
the power consumption exceeds the power capacity.
To set the forced-power-off sequence for server blades from the CLI
console:
1. Execute the set power blade poweroff order command.

Related topics
• set power blade poweroff order on page 5-137

Specifying all settings for a server chassis by using an


import file
This section describes the import functionality of management modules.

Importing a settings file


The import functionality specifies all settings for a server chassis during initial
setup. A settings file created by this functionality is called an import file.

Preparations for Using the Management Module 2-111


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 2-6 Example of importing a settings file by using an LCD touch
console
The following shows the settings that you can specify by importing a settings
file.
• Time settings
Specify the timezone and daylight saving time settings.
• Protocol settings
Specify the connection permission settings for Telnet, SSH, FTP, HTTP,
and HTTPS.
• Network settings
Specify IP address settings for management modules, server blades, and
switch modules.
The following table describes the consoles used when you import a settings
file from a management module.

Table 2-66 Import of a settings file

LCD touch
Operation Web console CLI console
console

Importing a settings file Y -- Y

Related topics
• Checking the template used to set the import file format on page 2-113
• Importing a settings file on page 2-116

2-112 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Notes on changing the settings for import files on page 2-117
• Example of changing the settings for an import file on page 2-117
• Causes and actions to take if importing of an import file fails on page
2-119

Checking the template used to set the import file format


The following shows the template for import files.
#!begin target=timezone
set time timezone -z "+9:00"
set time dst -v disable
#!end

#!begin target=protocol
set remote-access protocol telnet -a allow -n 0.0.0.0 -s 0.0.0.0 -a6
allow -n6 :: -p6 0
set remote-access protocol ssh -a allow -n 0.0.0.0 -s 0.0.0.0 -a6
allow -n6 :: -p6 0
set remote-access protocol ftp -a allow -n 0.0.0.0 -s 0.0.0.0 -a6
allow -n6 :: -p6 0
set remote-access protocol http -a allow -p 80 -n 0.0.0.0 -s 0.0.0.0
-a6 allow -n6 :: -p6 0
set remote-access protocol https -a allow -p 443 -n 0.0.0.0 -s
0.0.0.0 -a6 allow -n6 :: -p6 0
#!end

#!begin target=network
set mgmt-module mgmt-lan -i 192.168.0.1 -s 255.255.255.0 -g 0.0.0.0 -
d0 0.0.0.0 -d1 0.0.0.0 -d2 0.0.0.0
set blade mgmt-lan 1 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 2 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 3 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 4 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 5 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 6 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 7 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 8 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 9 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 10 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 11 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 12 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 13 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 14 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set blade mgmt-lan 15 -i 0.0.0.0 -s 0.0.0.0 -g 0.0.0.0
set sw-module mgmt-lan 1 -i 192.168.0.31 -s 255.255.255.0 -g 0.0.0.0
set sw-module mgmt-lan 2 -i 192.168.0.32 -s 255.255.255.0 -g 0.0.0.0
#!end

#!begin target=networkv6
set mgmt-module mgmt-v6 address -st enable -i 2001:0DB8::1 -p 64 -gs
enable -g 2001:0DB8::1000
set mgmt-module dns -p ipv4 -v6 2001:0DB8::100
set blade mgmt-v6 address 1 -st enable -i 2001:0DB8::11 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 2 -st enable -i 2001:0DB8::12 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 3 -st enable -i 2001:0DB8::13 -p 64 -gs

Preparations for Using the Management Module 2-113


Hitachi Compute Blade 2500 Series Management Module User Guide
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 4 -st enable -i 2001:0DB8::14 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 5 -st enable -i 2001:0DB8::15 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 6 -st enable -i 2001:0DB8::16 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 7 -st enable -i 2001:0DB8::17 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 8 -st enable -i 2001:0DB8::18 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 9 -st enable -i 2001:0DB8::19 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 10 -st enable -i 2001:0DB8::20 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 11 -st enable -i 2001:0DB8::21 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 12 -st enable -i 2001:0DB8::22 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 13 -st enable -i 2001:0DB8::23 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 14 -st enable -i 2001:0DB8::24 -p 64 -gs
enable -g 2001:0DB8::1000
set blade mgmt-v6 address 15 -st enable -i 2001:0DB8::25 -p 64 -gs
enable -g 2001:0DB8::1000
set sw-module mgmt-v6 address 1 -st enable -i 2001:0DB8::31 -p 64 -
gs enable -g 2001:0DB8::1000
set sw-module mgmt-v6 address 2 -st enable -i 2001:0DB8::32 -p 64 -
gs enable -g 2001:0DB8::1000
#!end

When changing the template settings, use Notepad or another text editor to
directly modify the file, and then save the file to a USB flash drive.

Tip: To import individual settings for multiple server chassis, prepare


individual files for each server chassis. Specify the file names that indicate
individual server chassis so that you can easily distinguish the files when
performing the import operation.
The following shows the import file format.

Time settings
• Time zone: +9:00
• Daylight saving time: disabled

Protocol settings
Connection permission settings for Telnet, SSH, FTP, HTTP, and HTTPS.
• All connections are allowed for all protocols.
• Port number for HTTP: 80
• Port number for HTTPS: 443

2-114 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Network settings for IPv4 connections
Management module IP address setting
• IP address: 192.168.0.1
• Subnet mask: 255.255.255.0
• Default gateway: 0.0.0.0
• DNS server address: 0.0.0.0
Server blade IP address setting (for all server blades)
• IP address: 0.0.0.0
• Subnet mask: 0.0.0.0
• Default gateway: 0.0.0.0
IP address settings for switch modules
The following shows a setting example of switch module 1:
• IP address: 192.168.0.31
• Subnet mask: 255.255.255.0
• Default gateway: 0.0.0.0

Network settings for IPv6 connections


Management module IP address setting
• IP address: 2001:0DB8::1
• Prefix length: 64
• Default gateway: 2001:0DB8::1000
DNS server address setting
• IPv4 settings are preferentially used.
• DNS server address when using IPv6 networks: 2001:0DB8::100
Server blade IP address setting
The following shows an example of a setting for server blade 1:
• IP address: 2001:0DB8::11
• Prefix length: 64
• Default gateway: 2001:0DB8::1000
Switch module IP address setting
The following shows a an example of a setting for switch module 1:
• IP address: 2001:0DB8::31
• Prefix length: 64
• Default gateway: 2001:0DB8::1000

Preparations for Using the Management Module 2-115


Hitachi Compute Blade 2500 Series Management Module User Guide
Note:
• If IPv6 connections are not used, delete the network settings for IPv6
connections (settings from #!begin target=networkv6 to #!end) from
the import file.
• The values of network settings for IPv6 connections in the template are
samples, and make sure that you change the values when you are using
the import file format.
• IPv6 stateless addresses cannot be set.

Importing a settings file


To import a settings file, use the Web console or the LCD touch console.

Operations that you need to perform in advance


• Saving of import files to the system console (for the Web console)
For both the name of the folder in which the files are to be saved and the
import file names, use only half width alphanumeric characters to specify
the names, and ensure that each full path is no more than 200
characters.
• Saving of import files to a USB flash drive (for the LCD touch console)
For both the name of the folder in which the files are to be saved and the
import file names, use only half width alphanumeric characters to specify
the names, and ensure that each full path is no more than 255
characters.
• Connecting of the USB flash drive to which the import files are already
saved to the server chassis (for the LCD touch console)
To import a settings file from the Web console:
1. In the Resources tab, from the tree view under Modules, select
Chassis.
2. From the Action pull-down menu, click Import System Settings.
The Import System Settings dialog box appears.
3. Click the Browse button to select the created import file, and then click
Confirm.
4. Check the message, and then click the OK button.
The file is imported.

Note: If you import a settings file to change the IP address of a


management module, the management module is disconnected. Log in to
the Web console of the management module, and then execute steps 1-2
again.
5. Select Download last import log, and then click the Confirm button.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.

2-116 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.
In such a case, download the file again.
To import a settings file from the LCD touch console:
1. From the System settings menu, touch the Import button.
2. In the Import (Select file) window, touch a settings file to be imported,
and then select Open/OK.
The file is imported.

Note:
• If you touch a file, the background changes to blue.
• The current directory is displayed at the top of the window. If the
directory is longer than the window width, the directory is right-
aligned (and disappears from the left side).
3. Check the import result, and then touch the OK button.

Notes on changing the settings for import files


If you change the settings for an imported file, note the following:
• Strictly follow the template when changing the settings.
If you add a CLI command that is not included in the template to a
settings file or move a command description to another location within a
settings file, the settings file might not be imported correctly.
• From a settings file, delete the description of commands that you do not
need to execute.
• CLI commands are used to specify each setting for an import file. For
details about CLI commands, see Chapter 5, Commands That Can Be
Executed From the CLI Console.

Example of changing the settings for an import file


This section describes examples of changing the protocol and network
settings.

Changing the protocol settings


The following examples show how to change protocol settings written in an
import file:
• To disable the connection permission for HTTP:
set remote-access protocol http -a deny -a6 deny
• To set the port number for HTTP to 80:
set remote-access protocol http -p 80

Preparations for Using the Management Module 2-117


Hitachi Compute Blade 2500 Series Management Module User Guide
• To apply IPv4 connection restrictions to HTTP:
Set the network address to 192.168.0.0 and the subnet mask to
255.255.255.0.
set remote-access protocol http -n 192.168.0.0 -s 255.255.255.0
• To apply IPv6 connection restrictions to HTTP:
Set the network address to 2001:0DB8::/64.
set remote-access protocol http -n6 2001:0DB8:: -p6 64

Note: To set a protocol other than HTTP, change HTTP to Telnet, SSH, FTP,
or HTTPS. For Telnet, SSH, and FTP, you do not need to set a port number.

Changing network settings for IPv4 connections


The following examples show how to change the network settings for IPv4
connections written in an import file:
• Management modules
¢ Set the IP address to 192.168.0.1.
¢ Set the subnet mask to 255.255.255.0.
¢ Set the default gateway to 192.168.0.100.
¢ Set the DNS server address (1st) to 192.168.0.150.
¢ Set the DNS server address (2nd) to 192.168.0.151.
¢ Set the DNS server address (3rd) to 192.168.0.152.
set mgmt-module mgmt-lan -i 192.168.0.1 -s 255.255.255.0 -g
192.168.0.100 -d0
192.168.0.150 -d1 192.168.0.151 -d2 192.168.0.152
• Server blade 1
¢ Set the IP address to 192.168.0.10.
¢ Set the subnet mask to 255.255.255.0.
¢ Set the default gateway to 192.168.0.100.
set blade mgmt-lan 1 -i 192.168.0.10 -s 255.255.255.0 -g
192.168.0.100
• Switch module 1
¢ Set the IP address to 192.168.0.31.
¢ Set the subnet mask to 255.255.255.0.
¢ Set the default gateway to 192.168.0.100.
set sw-module mgmt-lan 1 -i 192.168.0.31 -s 255.255.255.0 -g
192.168.0.100

Network settings for IPv6 connections


The following examples show how to change the network settings for IPv6
connections written in an import file:
• Management modules

2-118 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ Disable IPv6 connections.
set mgmt-module mgmt-v6 address -st disable
¢ Set the IP address to 2001::202:1.
¢ Set the prefix length to 32.
¢ Set the default gateway to 2001::1:1:1.
set mgmt-module mgmt-v6 address -st enable -i 2001::202:1 -p 32 -
gs enable -g 2001::1:1:1
• DNS server address setting
¢ Setting so that DNS server IPv6 addresses are preferentially used
¢ Set the DNS server IPv4 address (1st) to 192.168.0.150.
¢ Set the DNS server IPv6 address (1st) to 2001::1:1:1.
¢ Set the DNS server IPv6 address (2nd) to 2001::2:2:2.
set mgmt-module dns -p ipv6 -v4 192.168.0.150 -v6
2001::1:1:1,2001::2:2:2
• Server blade 1
¢ Disable IPv6 connections.
set blade mgmt-v6 address 1 -st disable
¢ Set the IP address to 2001::202:11.
¢ Set the prefix length to 32.
¢ Set the default gateway to 2001::1:1:1.
set blade mgmt-v6 address 1 -st enable -i 2001::202:11 -p 32 -gs
enable -g 2001::1:1:1
• Switch module 1
¢ Disable IPv6 connections.
set sw-module mgmt-v6 address 1 -st disable
¢ Set the IP address to 2001::202:30.
¢ Set the prefix length to 32.
¢ Set the default gateway to 2001::1:1:1.
set sw-module mgmt-v6 address 1 -st enable -i 2001::202:30 -p 32
-gs enable -g 2001::1:1:1

Causes and actions to take if importing of an import file fails


If the importing of an import file fails, check the cause displayed in the
Import (Result) window. The following explains how to take action according
to the displayed message.

A syntax error occurred.


The import file has a command syntax error. Do the following:
1. Check the content of the import result file (importresult-
yyyymmddhhmmss.txt) stored in the USB flash drive that contains the
import file.

Preparations for Using the Management Module 2-119


Hitachi Compute Blade 2500 Series Management Module User Guide
The following shows an example of the result file.
E9972 : Syntax error. : (4,20(1)) : (2)set time timezone -s +9:00
E9973 : File is invalid.
(1) indicates that an error occurred at the 20th character in the fourth
line of the import file. (2) indicates the fourth line. Therefore, correct the
20th character of the line.
2. Correct the error indicated by the import result file, re-create the import
file, and then import the file again.

Importation was failed.


The failure was caused by an incorrect command setting in the import file or
other cause.
1. Check the content of the import result file (importresult-
yyyymmddhhmmss.txt) stored in the USB flash drive that contains the
import file.
The following shows an example of the result file.
$ #!begin target=network
$ set mgmt-module mgmt-lan -i 192.168.0.100 -s 255.255.255.0 -g
192.168.0.200 -d0
192.168.0.101 -d1 192.168.0.102 -d2 192.168.0.103
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$ set blade mgmt-lan 0 -i 192.168.0.301 -s 255.255.255.0 -g
0.0.0.0- (1)
E0001 : Command was canceled. Parameter was invalid.- (2)
S0005 : Command was invalid.- (3)
S0000 : Command was finished.
Check the content of the command statement indicated by (1) for which
the lines (2) and (3) are displayed. In the line (2), the cause of the error
is indicated after [Command was canceled.].
2. Correct the error indicated by the import result file, re-create the import
file, and then import the file again.

Failed writing to result file.


An attempt to write the import result file (importresult-
yyyymmddhhmmss.txt) in the USB flash drive that contains the import file
failed.
If this error occurs, make sure that the USB flash drive is inserted into the
server chassis. In addition, check the free space in the USB flash drive. The
import result file can be a maximum of 5 KB.

Specified file is not defined.


Again, make sure that the USB flash drive that contains the import file
specified when you performed the import operation is inserted into the server
chassis, and then import the file.

2-120 Preparations for Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Unexpected error occurred.
An error occurred in the controller that executes import operations. Consult
your reseller.

Preparations for Using the Management Module 2-121


Hitachi Compute Blade 2500 Series Management Module User Guide
2-122 Preparations for Using the Management Module
Hitachi Compute Blade 2500 Series Management Module User Guide
3
Efficient Management of Servers Using
the Management Module
This chapter describes how to efficiently manage each system unit using the
functionality provided by the management module.

□ Linkage with the server management software (HCSM)

□ Preparation for running the server blades in a redundant configuration (N


+M cold standby)

□ Configuring an environment for running server blades in a redundant


configuration (N+M cold standby)

□ Failure management through failover from the active to standby server


blade (HA monitor)

□ Viewing the host information of the server blade

□ Managing user account information by using LDAP

□ Managing user account information by using RADIUS

□ Monitoring the operating status of the system unit by using an SNMP


manager

□ Notifying the status of the management module through email

□ Syslog transfer

Efficient Management of Servers Using the Management Module 3-1


Hitachi Compute Blade 2500 Series Management Module User Guide
Linkage with the server management software (HCSM)
This section describes the linkage between the management module and the
server management software (HCSM).

Linkage with HCSM


HCSM is software designed to provide the functionality for operating the
system units installed in a large system.
By using HCSM, the system administrator can manage the hardware
resources used in the system, monitor the operating status of the resources,
place the system in N+M cold standby, implement power management, and
operate hardware devices.
Management modules communicate with HCSM through management
interfaces. You can select either IPv4 or IPv6 communication.

Note:
• If IPv6 communication is selected, specify static addresses for the IPv6
setting of the management interfaces of management modules. In
addition, search for the static addresses of the management modules
from HCSM.
• If IPv6 communication is selected, disable stateless addressing of server
blades and management modules.
These management functionality is provided through communication between
HCSM and the management module.
HCSM and the management module share two communication channels.

• Command communication channel


HCSM uses this communication channel to send a processing request to
the management module.

3-2 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
The command communication uses the HTTPS protocol to prevent
wiretapping or tampering with data sent to the management module.
• Alert communication channel
The management module uses this communication channel to notify
HCSM of the events that occur in the system unit.
The alert communication uses the SSL/TLS protocol to prevent
wiretapping or tampering with data sent to HCSM.
The management module can link with a maximum of four HCSMs.

Note:
• To link a management module with HCSM, you have to enable HTTPS.
• If you set the security level to [High], or if you set the security level to
[Normal] while disabling any communications that do not use TLS 1.2, the
management module cannot connect with HCSM that does not support
TLS 1.2.
For details about the procedures you need to follow when using HCSM,
see the instruction manual or other manuals supplied with HCSM.
• If you edit the HCSM settings and change the port number used for
HTTPS communication to a setting other than 443, set the same port
number for the management module as well.
The following table describes the consoles that you can use to specify linkage
between the management module and HCSM.

Table 3-1 Setting up linkage with HCSM

Operation Web console CLI console LCD touch console

Check the HCSM Y Y --


information registered in
the management module.

Disable the HCSM linkage Y Y --


functionality.

Related topics
• Specifying the HCSM linkage options on page 3-3
• Specifying information regarding HCSM registered in the management
module on page 3-5

Specifying the HCSM linkage options


You can link management modules to HCSM by Discovering and adding
resources from the HCSM user interface after specifying network settings for
the management modules. Other settings for the management modules are
not required.
The following HCSM linkage options are available:

Efficient Management of Servers Using the Management Module 3-3


Hitachi Compute Blade 2500 Series Management Module User Guide
• Suppress the management functionality performed by HCSM.
You can disable the HCSM linkage functionality.
If you enable this option, HCSM will not be able to manage the system
unit. If you perform a resource search from HCSM with the HCSM linkage
functionality disabled, the system unit will not become the management
target.
• Restrict connections based on the IP addresses.
If you enable connection restriction, you can link the management
module with only the HCSM server registered in the management module.
If you perform a resource search from an unregistered HCSM with a
connection restriction enabled, the system unit will not become the
management target.
This option is useful when you want to prevent the system unit from
becoming the management target of an HCSM that was set up by mistake
after the system was configured.

Note: If you want to manage the system unit from a new HCSM when a
connection restriction is enabled, you have to register the IP address of
the new HCSM in the management module before performing a resource
search from that HCSM.
• Set the account and password used for authentication.
When linking with HCSM, the management module performs
authentication using the account and password.
The management module and HCSM share the same default account and
password. This authentication can also be performed using the account
and password specified by the system administrator instead of using the
default account and password.
If you specify the account and password used for authentication, specify
the same account and password for the management module and HCSM.
If the management module and HCSM do not specify the same account
and password, authentication will fail and you will be unable to link the
management module to HCSM.

Note: Alerts to be sent to HCSM have the setting items below. Do not change
these settings by using the Web console or CLI console.
Even if you change the setting values, the changed values are updated to the
following values when you execute Discovering and adding resources from
HCSM:
• Port number to which alerts are to be sent: Port number set from HCSM
• Alert level: failure notifications, warning notifications, and information
notifications
• Alert retry interval: 2 minutes
• Alert retry duration: 10 minutes
The port number to which alerts are to be sent can be set from HCSM. If you
use HCSM to change the port number, re-execute Discovering and adding
resources from HCSM.

3-4 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Linkage with HCSM on page 3-2
• Manual Hitachi Command Suite Compute Systems Manager User Guide

Specifying information regarding HCSM registered in the


management module
HCSM is equipped with functionality (resource search) to search for the
system units that exist within the management target network.
When the system administrator performs a resource search from the HCSM
user interface, all the system units that exist in the network become the
management targets of HCSM. After including the system units as the
management targets, HCSM registers its own information in the management
module that manages each system unit.
You can check or specify the following information from the Web console or
CLI console: connection restrictions based on the IP addresses of the HCSMs
registered in the management module through a resource search.

Note: Suppose that there are four HCSMs registered in the management
module. In this case, if you perform a resource search from an unregistered
HCSM, the system unit in which the management module is registered will
not become a management target of the new HCSM.
To specify information regarding HCSM from the Web console:
1. From the tree view in the Administration tab, select HCSM.
2. On the HCSM Server or HCSM Service tab, check the information
regarding the HCSM linked with the management module.
To specify information regarding HCSM from the CLI console:
1. Depending on the operation you are going to perform, execute one of the
commands listed in the following table.

Table 3-2 Commands used for HCSM linkage

Operation Command

Display the information regarding HCSM. show hcsm setting

Edit the information regarding HCSM. set hcsm manager

Delete the information regarding HCSM. delete hcsm manager

Change the HCSM management set hcsm agent


suppression setting, or change the
connection restriction setting.

Related topics
• Linkage with HCSM on page 3-2
• show hcsm setting on page 5-221

Efficient Management of Servers Using the Management Module 3-5


Hitachi Compute Blade 2500 Series Management Module User Guide
• set hcsm manager on page 5-209
• delete hcsm manager on page 5-202
• set hcsm agent on page 5-209

Preparation for running the server blades in a redundant


configuration (N+M cold standby)
This section describes the functionality you can use to run the server blades
in a redundant configuration.

N+M cold standby


N+M cold standby is functionality through which HCSM receives a notification
of hardware failure in the active server blade (operating server blade),
analyzes the failure, and then enables failover to the standby server blade.
You can prepare a standby server blade for several active server blades so
that when one of the active server blades fails, the standby server blade can
take over and resume the operation. Although a hardware failure causes the
operation to stop temporarily, N+M cold standby offers a labor-saving
solution to managing a hardware failure and resuming operation using limited
hardware resources.
N+M cold standby also supports LPAR manager. Thus, when a hardware
failure occurs in the active server blade on which multiple LPARs are running,
the LPARs are restarted on the standby server blade that takes over for the
active server blade. It is also possible to share a standby server blade
between the active server blade running in basic mode and another active
server blade running in LP mode. For details about LP mode, see Hitachi
Compute Blade 2500 Series Logical partitioning manager User Guide.

3-6 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 3-1 Example of the N+M cold standby configuration

Tip:
• You can specify N+M cold standby for multiple system units.
• The active server blade and the standby server blade do not need to exist
within the same system unit.
• To configure N+M cold standby, you need to have HCSM installed in your
system. For details, contact our sales personnel for assistance. For details
about the HCSM configuration that supports N+M cold standby, see the
Hitachi Compute Systems Manager Function Release Schedule (FRS).
• If you want to switch to the standby server blade when a watchdog timer
timeout occurs, you must configure necessary settings for the
management modules.
• For the onboard CNA, the support level for N+M cold standby differs
depending on the firmware version. For details, see Required unit
configuration for N+M cold standby on page 3-12.
• To connect to HCSM version 8.1.1 or later, you can use the IPv6 network.
However, when configuring N+M cold standby for multiple server chassis,
you need to only use either the IPv4 network or the IPv6 network to
connect to HCSM.

Efficient Management of Servers Using the Management Module 3-7


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Linkage with HCSM on page 3-2
• Enabling the N+M cold standby support functionality on page 3-17

Mechanism of N+M cold standby


This subsection describes the mechanism of N+M cold standby.
This manual refers to the settings inherited as a result of N+M cold standby
as the "server blade settings" or just the "settings". Failover from an active to
standby server blade, on the other hand, is referred to as "N+M failover",
whereas failover from a standby to active server blade is referred to as "N+M
recovery".
With N+M cold standby, when the basic-mode server blade undergoes N+M
failover, the standby server blade inherits the various settings from the active
server blade. This allows the standby server blade to start up from the same
disk (LU) and restart the same OS environment as the active server blade
when the standby server blade takes over for the active server blade.

Figure 3-2 N+M failover of the basic-mode server blades

Note: The active server blade and the standby server blade must have the
same hardware configuration and have the same version of the firmware
installed.

Related topics
• N+M cold standby on page 3-6

3-8 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Notes on N+M cold standby on page 3-9

Notes on N+M cold standby


This subsection describes the precautions to be taken before configuring the
N+M cold standby environment.
• The active server blade and the standby server blade must have the same
hardware configuration. N+M cold standby works only between the server
blades of the same model.
• When using the Emulex network product (LAN or converged network)
with the standby server blade, use a configuration in which the firmware
is updated to its latest version.
For details about the latest version of the firmware, see the firmware
page on the "Support and Download" section of the Hitachi Compute
Blade web site. The firmware page also shows you how to check the
version of the firmware you are currently using.
• When configuring N+M cold standby for multiple server chassis, the
switch modules must also have the same hardware configuration.
• In order for N+M recovery to work, the operation mode (LP mode or basic
mode) of the standby server blade must be the same as that of the active
server blade (operation mode of the active server blade when it was
registered in the N+M group). If you change the operation mode of the
standby server blade after N+M failover, you must reset the operation
mode before performing N+M recovery. If you change the operation mode
of the standby server blade after N+M failover and perform N+M recovery
without resetting the operation mode, the N+M recovery might fail.

Related topics
• N+M cold standby on page 3-6
• Mechanism of N+M cold standby on page 3-8

Settings inherited through N+M cold standby


This subsection describes the server blade settings that are inherited through
N+M cold standby.
With N+M cold standby, when N+M failover occurs in basic mode, the
standby server blade inherits the settings listed in the following table from
the active server blade.

Table 3-3 Settings inherited through N+M cold standby

Category Item

WWN1 World Wide Node Name

World Wide Port Name

MAC MAC address2

Efficient Management of Servers Using the Management Module 3-9


Hitachi Compute Blade 2500 Series Management Module User Guide
Category Item

MAC type3

Server blade settings (UEFI or Time synchronization method and time zone setting
BMC) for the BMC clock

EFI settings4

Boot order

HBA BIOS settings for the Fibre HBA BIOS setting (enabled or disabled)
Channel adapter5
Boot priority setting (enabled or disabled)

Boot target WWN

Boot target LUN

CNA setting6 PXE boot settings7

VLAN information settings7

Bandwidth settings if a port is divided

SR-IOV (when the Multi Channel Support settings


are disabled)

iSCSI setting (if iSCSI is specified as the Personality


setting)

FCoE setting (if FCoE is specified as the Personality


setting)

Server blade settings Power control linkage setting


(management module)
N+M cold standby support functionality setting

OS type (whether LPAR manager is used)

HA monitor setting HA monitor system name

HA monitor port number

HA monitor N+M cold standby support functionality


setting

Settings for the high-speed failover support


functionality for the HA monitor

HA monitor cluster management functionality


settings

Notes:
1. The Optional Physical WWN is inherited.
2. The Optional Physical MAC address is inherited.
3. The MAC address set as the MAC type is used.
4. Only the items specified in the UEFI settings in the Web console of the management
module are inherited.
5. If the Emulex 8Gb/16Gb 2-port Fibre Channel adapter is used, all the items in the
setup menu are inherited.
6. For these settings to be inherited, NIC, iSCSI, FCoE, or RoCE must be specified as
the Personality setting and the same MultiChannel Support setting must be specified

3-10 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Category Item
for both the active and standby server blades. For the onboard CNA, N+M cold
standby for which iSCSI is specified as the Personality setting is not supported. For
details, see the manual Hitachi Compute Blade Emulex Adapter User's Guide for
Hardware.
7. For the onboard CNA, this item is not inherited.

Tip:
• When N+M recovery takes place, the settings inherited by the standby
server blade are returned to the active server blade, which means that
the active server blade reverts back to the state from before the N+M
failover. The standby server blade, on the other hand, retains the settings
inherited from the active server blade. In other words, even after N+M
recovery, it does not revert back to the state from before the N+M
failover. (The WWN and MAC address settings in the standby server
blade, however, revert back to the settings from before the failover.)
• If the Emulex 10Gb CNA is used with the Personality setting set to iSCSI,
the following exception applies: the IP address and subnet mask of the
iSCSI Initiator are cleared to 0 in the active server blade after N+M
failover and in the standby server blade after N+M recovery.

Related topics
• Setting WWNs and MAC addresses on page 2-79
• Setting server blades, switch modules, and Hitachi Fibre Channel adapter
on page 2-61
• Failure management through failover from the active to standby server
blade (HA monitor) on page 3-21
• Time required for the standby server blade to take over for the active
server blade on page 3-11

Time required for the standby server blade to take over for the active
server blade
When a failure occurs in the server blade, the following time is required for
the N+M failover to complete.
Time required for the N+M failover to complete = [wait time for the failover
to start] + [time required for the failover to take place] + [time required for
the OS to start up]

Tip: When a failover takes place in the N+M cold standby environment that
uses HCSM, HCSM monitors the standby server blade to confirm the
completion of OS startup.
If the OS on the standby server blade does not start up within the user-
specified "maximum wait time for the OS startup processing to complete",
the following message appears in the task result display window of HCSM:
the message indicating that the N+M failover has failed (KASV00212-E). This

Efficient Management of Servers Using the Management Module 3-11


Hitachi Compute Blade 2500 Series Management Module User Guide
message appears even when the OS eventually starts up on the standby
server blade.
In other words, even when the N+M failover is successful and the OS starts
up successfully on the standby server blade, the following message might
appear in the task result display window of HCSM: the message indicating
that the N+M failover has failed (KASV00212-E).
Depending on the configuration of the server blade, it might take longer for
the OS startup processing to complete on the standby server blade. Bear this
in mind and specify an appropriate "maximum wait time for the OS startup
processing to complete".

Related topics
• Settings inherited through N+M cold standby on page 3-9

Required unit configuration for N+M cold standby


N+M cold standby requires the following unit configuration:
• SAN boot devices are used.
• Active and standby server blades have equivalent hardware
configurations.
¢ CPU type and the number of CPUs
¢ Amount of installed memory
¢ Mezzanine card and I/O adapter(type and the relative position of each
slot when seen from the server blade)
Failovers can take place even if the CPU type, the number of CPUs, and
the amount of installed memory are different between the active and
standby server blades. However, perform a failover test in advance to
confirm that standby server blades work properly.
• No expansion blades are connected to the active server blade or standby
server blade.
• None of internal HDD or USB Enablement Kit or SD Card Enablement Kit
are installed.
• The server blades must be of the same model in an N+M group.
• The operating conditions for the OS and applications must be satisfied.
• If you configure N+M cold standby using the Emulex 8Gb 2-port Fibre
Channel adapter, all the items in the setup menu of the HBA BIOS
settings are inherited. For this reason, the SAN configuration between the
active server blade and the LU must be the same as the SAN
configuration between the standby server blade and the LU.
¢ Number of cascade stages of the FC switch
¢ Port speed setting for the FC switch
¢ Port speed setting and the topology setting for the disk device
• Specify the settings described below for the CNA installed on the active
server blade and the standby server blade. These settings are mandatory
if you configure N+M cold standby by using the CNA.

3-12 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ The same MultiChannel Support setting must be specified for the
active server blade and the standby server blade.
¢ The same Personality setting must be specified for the active server
blade and the standby server blade.
¢ Specify NIC, iSCSI, FCoE, or RoCE as the Personality setting.
¢ Disable DHCP in the iSCSI setting.
¢ Set a unique iSCSI Initiator IP address.
¢ The iSCSI Target must always be connected.
¢ The number of iSCSI Target sessions must not exceed four sessions
per port.
For details about the MultiChannel Support setting and the Personality
setting, see the manual Hitachi Compute Blade Emulex Adapter User's
Guide for Hardware.

Note: If CB 520X B1 and CB 520H B3 are to inherit the onboard CNA


information, use the following firmware:
• Management module firmware
A0110 or later
• Server blade firmware
CB 520H B3 server blades: 08-16 or later
CB 520X B1 server blades: 07-24 or later
Note that, for the onboard CNA, N+M cold standby for which iSCSI is
specified as the Personality setting is not supported.
When a server blade with firmware other than the above is used on a CB
520X B1 server blade, in N+M cold standby by the onboard CNA, only the
Optional Physical MAC address can be inherited.
When a server blade with firmware other than the above is used on a CB
520X B1 server blade, in N+M cold standby by the onboard CNA, make sure
that the onboard CNA settings are the same for the active and standby server
blades.

Configuring an environment for running server blades in a


redundant configuration (N+M cold standby)
This section describes how to configure an environment for running server
blades in a redundant configuration.

General procedure for configuring N+M cold standby


To set up N+M cold standby, you need to set the Compute Blade, the SAN,
and HCSM, respectively. For details about how to set the SAN and HCSM, see
the instruction manual or other manuals supplied with the SAN or HCSM.
The figure below shows the general procedure for configuring N+M cold
standby. The specific procedures are described in the subsections that follow.

Efficient Management of Servers Using the Management Module 3-13


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 3-3 Configuring N+M cold standby

Related topics
• Collecting the settings for the active server blade (Smart configure) on
page 3-14

Collecting the settings for the active server blade (Smart configure)
In N+M cold standby, the settings for the active server blade need to be
collected and saved to the management module beforehand. When the N+M
failover occurs, the settings saved to the management module are applied to
the standby server blade before the standby server blade starts up. The
functionality to collect the server blade settings in advance is called Smart
configure.
Smart configure requires that the settings in the active server blade be
collected not when the N+M failover occurs but when N+M cold standby is
configured. This is because Smart configure might not work in a faulty server
blade.
Smart configure is either manually or automatically executed to collect and
apply the server blade settings under the following circumstances:
• When Smart configure is executed from the console of the management
module
• When the N+M recovery is executed (by HCSM)
When the N+M recovery takes place, the active server blade that resumes
operation is not subject to Smart configure. The standby server blade, on
the other hand, is subject to Smart configure, which is required to make

3-14 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
the standby server blade ready for a failover. Under this circumstance,
Smart configure is automatically executed by HCSM.
• When the system unit is turned on
When, after N+M cold standby is configured, the system unit is turned off
and then back on again, Smart configure is automatically executed to
resume N+M cold standby.
• When the server blade configuration changes
If the following changes are made to the server blade configuration, the
management module automatically executes Smart configure to update
the settings stored in itself.
¢ A server blade is inserted into the server chassis.
¢ The server blade is turned on.
The following table describes the consoles that you can use to perform
specific operations from the management module.

Table 3-4 Executing Smart configure

Operation Web console CLI console LCD touch console

Execute Smart configure to Y Y --


collect the settings from the
active server blade.

Enable the N+M cold Y Y --


standby support
functionality.

Confirm that a failover has Y -- --


taken place in the N+M cold
standby environment.

Enable the setting that Y -- --


automatically powers up the
active server blade.

Suppress the power-up of Y -- --


the standby server blade.

Related topics
• Settings that must be specified to collect settings from the active server
blade on page 3-16
• Points to be checked before executing Smart configure on page 3-16
• Executing Smart configure to collect the settings from the active server
blade on page 3-16
• Enabling the N+M cold standby support functionality on page 3-17
• Specifying WWN, iSCSI, and FCoE settings in the SAN on page 3-18
• Specifying the necessary settings for the active server blade on page
3-18
• Setting N+M cold standby from HCSM on page 3-18

Efficient Management of Servers Using the Management Module 3-15


Hitachi Compute Blade 2500 Series Management Module User Guide
• Confirming that the standby server blade can take over for the active
server blade on page 3-19
• Notes on changing the settings after starting the N+M cold standby
operation on page 3-19
• Notes on replacing the CNA after starting the N+M cold standby operation
on page 3-20
• Restoring N+M cold standby following recovery from a power failure on
page 3-20

Settings that must be specified to collect settings from the active


server blade
When configuring N+M cold standby, you must disable the internal HDD
installed on the server blades. If the internal HDD is installed on the server
blade, use the UEFI setting to disable the HDD.

Note: In the UEFI setup menu, do not set the EFI Shell to be the first in the
boot priority order.
If the EFI Shell has the highest boot priority, the OS does not start up
properly when N+M failover or N+M recovery takes place.

Related topics
• Setting the UEFI for a server blade on page 2-76

Points to be checked before executing Smart configure


This subsection describes how the server blade behaves when Smart
configure is executed and how much time it takes to execute Smart
configure.
How the server blade behaves when Smart configure is executed
While Smart configure is being executed, the identification LED on the
front of the server blade blinks. While the identification LED is blinking,
the server blade is temporarily powered up. For details about the
identification LED status, see Hitachi Compute Blade 2500 Series Getting
Started Guide.
How much time it takes to execute Smart configure
The time it takes to execute Smart configure varies depending on the
type of the server blade, the number of installed CPUs, the memory, and
the type and number of installed PCI cards. Roughly, it takes
approximately 3 to 15 minutes to execute Smart configure.

Executing Smart configure to collect the settings from the active


server blade
To execute Smart configure, use the Web console or the CLI console.

3-16 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To execute Smart configure on the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. Select the Condition tab, and then from the Server Blade Action menu,
click Run Smart Configure.
To execute Smart configure on the CLI console:
1. Execute the pre-configure blade command.

Related topics
• Points to be checked before executing Smart configure on page 3-16
• pre-configure blade on page 5-37

Enabling the N+M cold standby support functionality


Enable the N+M cold standby support functionality in both the active and
standby server blades. As soon as you enable the N+M cold standby support
functionality, Smart configure is executed for the server blade. By executing
Smart configure, an Optional Physical WWN is set in the Fibre Channel
adapter.
To enable the N+M cold standby support functionality from the Web
console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. In the Settings tab, click the Edit Server Blade settings button.
3. Enable N+M cold standby.
To perform an N+M failover when a watchdog timer timeout occurs, enable
the WDT timeout N+M failover setting. The initial setting (the setting at
shipping time) of the system unit is "Disable".
To enable the WDT timeout N+M failover setting from the Web
console:
1. In the Resources tab, from the tree view under Modules, select Chassis.
2. From the Action pull-down menu, click Setting of an N+M failover due
to WDT timeout.
3. Enable the setting of an N+M failover due to WDT timeout:
To enable the N+M cold standby support functionality on the CLI
console:
1. Execute the set blade preconf command.

Related topics
• N+M cold standby on page 3-6

Efficient Management of Servers Using the Management Module 3-17


Hitachi Compute Blade 2500 Series Management Module User Guide
• Collecting the settings for the active server blade (Smart configure) on
page 3-14
• set blade preconf on page 5-51

Specifying WWN, iSCSI, and FCoE settings in the SAN


If you are using a Fiber Channel connection, specify a WWN and other related
settings in the SAN. Use an Optional Physical WWN as the WWN.
If you are using the iSCSI connection, specify the iSCSI Target and other
related settings in the SAN.
If you are using the FCoE connection, specify the WWN and other related
settings in the SAN or the FCoE switch. Use an Optional Physical WWN as the
WWN.

Related topics
• WWNs and MAC addresses that can be checked in management module
consoles on page 2-84

Specifying the necessary settings for the active server blade


Specify the settings necessary to allow the active server blade to boot from
the SAN.
• Setting the Fibre Channel adapter
¢ Enable both the Fibre Channel adapter BIOS and the boot priority.
¢ Select the boot target LU.
For details about how to configure these settings, see the manual
supplied with the Fibre Channel adapter.
• Setting the CNA (iSCSI)
For details about how to configure this setting, see the manual Hitachi
Compute Blade Emulex Adapter User's Guide for Hardware.
• Setting the CNA (FCoE)
For details about how to configure this setting, see the manual Hitachi
Compute Blade Emulex Adapter User's Guide for Hardware.
• Setting the UEFI
Specify the boot priority order to allow the server blade to boot from the
SAN.
For details about this setting, see Hitachi Compute Blade 2500 Series
UEFI Setup Guide.

Setting N+M cold standby from HCSM


From HCSM, set the N+M cold standby (including the designation of the
active and standby server blades). For details, see the HCSM manual.

3-18 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Confirm that the following settings are specified before using HCSM to specify
the N+M cold standby settings:
• The N+M cold standby support functionality is enabled.
This functionality must be enabled in both the active and standby server
blades.
• The active server blade can boot from the SAN.
After confirming that the above settings are specified, use HCSM to specify
the N+M cold standby settings.

Related topics
• Enabling the N+M cold standby support functionality on page 3-17

Confirming that the standby server blade can take over for the active
server blade
Before starting operation, perform an N+M failover test by using one of the
following methods to confirm that the N+M failover works properly:
• From HCSM, execute the N+M cold standby test.
• Issue a failover test alert from the Web console of the management
module.
You can perform a failover test from the Web console of the management
module by following the procedure described below. To perform a test to
confirm a failover from the active to standby server blade, you have to issue
an alert from HCSM.
To confirm a failover in the N+M cold standby environment from the
Web console:
1. From the tree view in the Administration tab, select HCSM.
2. From the Action pull-down menu, select Send alert.
Select an immediate failover or a delayed failover as the alert type.
A failover alert is issued, and the active server blade is forcibly turned off.

Tip:
• For details about how to configure N+M cold standby and how to execute
the N+M failover, see the HCSM manual.
• In an SMP configuration, issue a failover test alert for the primary server
blade.

Notes on changing the settings after starting the N+M cold standby
operation
If you change the UEFI setting from the Web console of the management
module after configuring N+M cold standby, the new setting is applied the
next time the UEFI starts up. If the N+M failover occurs before the new UEFI

Efficient Management of Servers Using the Management Module 3-19


Hitachi Compute Blade 2500 Series Management Module User Guide
setting is applied, the previous UEFI setting (the setting applied upon the
previous startup of the UEFI) is inherited by the standby server blade.

Notes on replacing the CNA after starting the N+M cold standby
operation
Suppose that, in a configuration where the CNA is used with the Personality
set to iSCSI, the iSCSI setting must be recovered following the replacement
of the CNA. In this case, one of the settings described in the following table
must be specified depending on the N+M cold standby status:

Status Setting

Active server blade before N+M Restore the iSCSI setting of the active server blade
failover from before the CNA was replaced.

Standby server blade before N+M Restore the iSCSI setting of the standby server blade
failover from before the CNA was replaced (setting of the
standby server blade when the iSCSI connection was
terminated).

Active server blade after N+M Restore the iSCSI setting of the standby server blade
failover from before the CNA was replaced (setting of the
standby server blade when the iSCSI connection was
terminated).

Standby server blade after N+M Restore the iSCSI setting of the active server blade
failover from before the CNA was replaced.

Restoring N+M cold standby following recovery from a power failure


If the system unit is connected to the UPS, you can automatically restore N
+M cold standby following recovery from a power failure. To enable this, you
need to suppress automatic power-up of the standby server blade. To
suppress automatic power-up of the standby server blade, follow the
procedure described below.

Note: If you do not need the server blade to start up automatically following
recovery from a power failure, you can omit the procedure described below
even when the system unit is connected to the UPS.
First, you have to enable the setting that automatically powers up the active
server blade following recovery from a power failure.
To enable the power-up setting for the active server blade from the
Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target active server blade.
2. In the Settings tab, click the Edit Server Blade settings button.
3. Set the AC recovery of the server blade to Power ON.
With the above setting enabled, the active server blade automatically
turns on following recovery from a power failure.

3-20 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Next, you have to suppress automatic power-up of the standby server blade.
To enable the power-up suppression setting for the standby server
blade from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target standby server blade.
2. In the Settings tab, click the Edit Server Blade settings button.
3. Set the AC recovery of the server blade to Power OFF.
With the above setting enabled, automatic power-up of the standby
server blade is suppressed during recovery from a power failure.

Tip:
• From the UEFI setup menu, you can enable the setting that automatically
turns on the server blade following recovery from a power failure. Even
when this setting is enabled, however, the server blade might not start up
automatically following recovery from power failure under the following
condition: the N+M cold standby support functionality is enabled. In this
case, you have to set the AC recovery of the server blade to Power ON.
• In an SMP configuration, the settings for a primary server blade are
applied to all server blades constituting the SMP. You do not need to
configure settings for non-primary server blades.

Related topics
• Enabling the N+M cold standby support functionality on page 3-17

Failure management through failover from the active to


standby server blade (HA monitor)
This section describes the failure management functionality provided by the
HA monitor.

HA monitor
The HA monitor enables a failover from one system (including the programs)
to another to improve the reliability and capacity utilization of the system.
The HA monitor ensures that, immediately after a failure occurs in the system
(active system) that is executing the business processing, the system
(standby system) automatically takes over for the faulty server blade. This
improves the reliability and capacity utilization of the system without the
operators having to pay any particular attention to the system. A hot standby
configuration that consists of the active system and the standby system is
called the system failover configuration. For details about the HA monitor, see
the manual supplied with the HA monitor.
The HA monitor that detected a failure might reset to stop the system. At this
time, the HA monitor asks the management module to reset the system on
the server blade. This route to perform the reset is called the reset path.

Efficient Management of Servers Using the Management Module 3-21


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 3-4 Example of the HA monitor configuration
To set the reset path for the management module, use the following console:

Table 3-5 Reset path settings

Operation Web console CLI console LCD touch console

Setting the reset path Y -- --

Related topics
• Setting the reset path on page 3-22

Setting the reset path


Set the reset path for the system failover configuration of the HA monitor. For
the server blade where the system to be reset is running, set the following
items:
• System name*1
• Port number*2
*1
For the setting items of the reset path in the manual supplied with the HA
monitor, this item indicates the item Partition name.
*2
For the setting items of the reset path in the manual supplied with the HA
monitor, this item indicates the item SVP port number.
To set the reset path by using the Web console:
1. Select the Resources tab, and then from the tree view in Systems,
select HA monitor linkage.

3-22 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
2. In the Server blade tab, select the target server blade, and then click
the Apply button.
3. In System name, enter the partition name. In Port number, enter the
SVP port number.

Notes on deciding port numbers for the reset path


1. The reset path is configured by the active and standby systems of the HA
monitor that have the same port number and the management modules
that have the same port number. In the reset path, the port number of
the management modules must be different from the port number of the
active and standby systems. You can set the port number of the
management module for each server blade. Note that when creating
multiple system failover configurations in the same LAN, you need to
specify unique port numbers for each system failover configuration.

Figure 3-5 Example 1 of setting port numbers for the reset path
2. In a virtualization environment, if system failover configurations in which
a virtual machine is used as the active and standby systems are used, the
systems that exist in the same server blade share the reset path.
Therefore, in the reset path, use the same port numbers for the reset
path and the management modules respectively.

Efficient Management of Servers Using the Management Module 3-23


Hitachi Compute Blade 2500 Series Management Module User Guide
Figure 3-6 Example 2 of setting port numbers for the reset path

Related topics
• HA monitor on page 3-21

Highly-reliable HA monitor
By using the functionality provided by the highly-reliable HA monitor
described below, you can further enhance the reliability and capacity
utilization of the system. To use the functionality of the highly-reliable HA
monitor, you need to acquire the Highly-reliable HA Monitor License.
• High-speed failover support functionality
The high-speed failover support functionality is used to reset the faulty
system within a second order, and to enable high-speed failovers to the
standby system to shorten the system downtime.
• Cluster management functionality
For the cluster management functionality, there is no need to specify the
reset priority system for the HA monitor because the cluster manager
manages all reset operations of both systems in a cluster to prevent the
simultaneous reset of the active and standby systems. This enables the
interactive system failover configuration to immediately reset the faulty
system even when a failure occurs in either of the systems.
In the management module, a group of systems that use the reset path
whose port numbers are the same is called a cluster. For each cluster, the
cluster name is automatically assigned. You can set the functionality of
the highly-reliable HA monitor for each cluster.
To set the highly-reliable HA monitor for the management module, use the
following console:

3-24 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 3-6 Setting the highly-reliable HA monitor

Operation Web console CLI console LCD touch console

Enable the high-speed Y -- --


failover support
functionality.

Enable the cluster Y -- --


management functionality.

Related topics
• High-speed failover support functionality on page 3-25
• Cluster management functionality on page 3-26
• Notes on using the high-speed failover support functionality on page
3-26
• Notes on using the cluster management functionality on page 3-26
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27
• Troubleshooting for the cluster management functionality on page 3-28

High-speed failover support functionality


The highly-reliable HA monitor stops processing of the faulty system, and
then performs a failover to the standby system. The high-speed failover
support functionality is used to reset the faulty system within a second order,
and to enable high-speed failovers to the standby system to shorten the
system downtime.
This functionality resets a system in a software reset. If termination of the
system cannot be confirmed after a software reset, this functionality forcibly
resets the system (hardware reset).
The high-speed failover support functionality secures high-speed failover by
performing a hardware reset before it is too late. The use of the high-speed
failover support functionality might be restricted depending on the
configuration. So, if you intend to use the high-speed failover support
functionality, contact our sales personnel for assistance.

Related topics
• Notes on using the high-speed failover support functionality on page
3-26
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27

Efficient Management of Servers Using the Management Module 3-25


Hitachi Compute Blade 2500 Series Management Module User Guide
Cluster management functionality
Both the active and standby systems being reset simultaneously is called a
simultaneous reset of the active and standby systems. If the simultaneous
reset of the active and standby systems occurs, both systems become
unavailable, in which case operation can no longer be continued. The HA
monitor determines in advance which of the two systems is to be reset first
(reset priority system) by using the interactive system failover configuration,
and prevents the simultaneous reset of the active and standby systems by
delaying the reset of the system without priority.
For the cluster management functionality, there is no need to specify the
reset priority system for the HA monitor because the cluster manager
manages all reset operations of both systems in a cluster to prevent the
simultaneous reset of the active and standby systems. This enables the
interactive system failover configuration to immediately reset the faulty
system even when a failure occurs in either of the systems.

Related topics
• Notes on using the cluster management functionality on page 3-26
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27
• Troubleshooting for the cluster management functionality on page 3-28

Notes on using the high-speed failover support functionality


Observe the following precautions when enabling the high-speed failover
support functionality:
• You can use the high-speed failover support functionality for CB 520X
B1/B2 server blades only. Do not enable the high-speed failover support
functionality for CB 520H B3 server blades. If a cluster for which you want
to enable the high-speed failover support functionality contains both CB
520X B1/B2 and CB 520H B3 server blades, re-set the server blades for
separate clusters.
• The high-speed failover support functionality functions only for the server
blades running in basic mode. For the server blades running in LP mode
that belong to a cluster for which the high-speed failover support
functionality is enabled, the high-speed failover support functionality does
not function.

Related topics
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27

Notes on using the cluster management functionality


Observe the following precautions when enabling the cluster management
functionality:

3-26 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Enable the cluster management functionality only for clusters that have
the server blades running in basic mode.
Do not enable the cluster management functionality for the server blades
running in LP mode.
• Use the cluster management functionality in the interactive system
failover configuration. Do not use the cluster management functionality in
a 1-to-1 system failover configuration, 2-to-1 system failover
configuration, multiple standby configuration, or cluster-type system
failover configuration.
• When using the cluster management functionality, specify appropriate
environment settings for all the HA monitors within the system failover
configuration. For details about the environment settings for the HA
monitor, see the manual supplied with the HA monitor.
• When using the cluster management functionality in a configuration
involving multiple system units, enable the cluster management
functionality for the cluster in all the system units.
• You must enable a cluster manager within a cluster. When using the
cluster management functionality in a configuration involving multiple
system units, do not enable multiple cluster managers within a cluster.
• When setting the cluster management functionality, power off all the
server blades within the cluster to be set.

Related topics
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27

Enabling the high-speed failover support functionality for the HA


monitor and the cluster management functionality
To enable the high-sped failover support functionality and the cluster
management functionality, use the Web console.
To enable the high-speed failover support functionality for the HA
monitor and the cluster management functionality from the Web
console:
1. Select the Resources tab, and then from the tree view in Systems,
select HA monitor linkage.
2. In the Cluster tab, click the Add button.
3. In [Port number], from among the port numbers specified in the Server
blade tab, enter the port number for which the high-speed failover
support functionality and the cluster management functionality are to be
enabled.
4. Enable or disable the high-speed failover support functionality and the
cluster management functionality.
5. If you enable the cluster management functionality in a cluster
configuration, set the management setting for the system unit to be run

Efficient Management of Servers Using the Management Module 3-27


Hitachi Compute Blade 2500 Series Management Module User Guide
as the cluster manager to "Enable", and set the management setting for
the other system unit to "Disable".
6. Click the Confirm button.

Tip:
• If you have not purchased the Highly-reliable HA Monitor License, the
Cluster tab is not displayed in the HA monitor window.
• To change the settings, click the Cluster tab, select the cluster, and then
click the Edit button.

Related topics
• Notes on using the high-speed failover support functionality on page 3-26
• Notes on using the cluster management functionality on page 3-26
• Troubleshooting for the cluster management functionality on page 3-28

Troubleshooting for the cluster management functionality


The following table describes how to deal with the potential errors associated
with the cluster management functionality.

Table 3-7 Troubleshooting for the cluster management functionality

No. Item Description

1 Category HA monitor

Error When the HA monitor started, an error was reported by the


description message KAMN478-E indicating CPUDOWN-SYSTEM.

Description The cluster management functionality is enabled for the HA


monitor but disabled for the management module.

Action (a) To use the cluster management functionality, the Highly-


reliable HA Monitor License is required. If you do not have this
license, change the cpudown parameter in the HA monitor
environment settings to either online or standby.
(b) If you are not using the cluster management functionality,
change the cpudown parameter in the environment settings of
the HA monitor that output the message to either online or
standby.
(c) If you are using the cluster management functionality, use
the Web console to enable the cluster management functionality
for the cluster that defines the server blade on which the
message source HA monitor is running.

Note Before changing cluster settings from the Web console, power
off all server blades in the cluster.

2 Category HA monitor

Error When the HA monitor started, an error was reported by the


description message KAMN686-W indicating CLUSTER-MANAGER.

3-28 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
No. Item Description

Description Although the cluster management functionality is enabled for


the HA monitor, one of the following problems exists in the way
the cluster management functionality is used or specified in the
management module:
(a) In a configuration involving multiple system units, the
cluster that defines the server blade on which the message
source HA monitor is running contains a server blade of the
management module for which the cluster management
functionality is disabled.
(b) In a configuration involving multiple system units, the
cluster management functionality is set differently for the cluster
that defines the server blade on which the message source HA
monitor is running.
(c) In a configuration involving multiple system units, more than
one cluster manager is specified for the cluster that defines the
server blade on which the message source HA monitor is
running.
(d) No cluster manager is specified for the cluster that defines
the server blade on which the message source HA monitor is
running.

Action For each of the problems (a) through (d), take the following
corrective action:
(a) The system failover configuration of the HA monitor that
output the message contains a management module that does
not have the Highly-reliable HA Monitor License. Purchase the
Highly-reliable HA Monitor License, or create a system failover
configuration in which the cluster management functionality is
disabled for both the HA monitor and the management module.
(b) For all system units, use the Web console to enable the
cluster management functionality for the cluster that defines the
server blade on which the message source HA monitor is
running.
(d) Use the Web console to change the management settings for
the cluster that defines the server blade on which the message
source HA monitor is running, so that only one cluster manager
from among all system units is set to "Enable". After you change
the settings, in the HA monitor window of the Web console,
click the Cluster tab, select the cluster, and then click the
Resume HA cluster manager button.
(d) Use the Web console to change the management settings for
the cluster that defines the server blade on which the message
source HA monitor is running, so that only one cluster manager
from among all system units is set to "Enable".

Note Problem (d) mentioned above is also detected under the


following circumstance: in a configuration involving multiple
system units, the HA monitor starts up in the server blade of the
system unit for which the cluster manager is not specified before
the system unit for which the cluster manager is specified is up
and running. In this case, the error status is resolved when the
system unit for which the cluster manager is specified is up and
running.

3 Category HA monitor

Efficient Management of Servers Using the Management Module 3-29


Hitachi Compute Blade 2500 Series Management Module User Guide
No. Item Description

Error When the HA monitor started or when you changed the settings
description while the system is running, an error was reported by the
message KAMN624-E indicating SVP-TIMEOUT or REQ-TIMEOUT.

Description The reset path is in the error state due to one of the following
problems associated with the way in which the cluster
management functionality is used or specified in the
management module:
(a) In a configuration involving multiple system units, the
cluster that defines the server blade on which the message
source HA monitor is running contains a server blade of the
management module for which the cluster management
functionality is disabled.
(b) In a configuration involving multiple system units, the
cluster management functionality is set differently for the cluster
that defines the server blade on which the message source HA
monitor is running.
(c) In a configuration involving multiple system units, more than
one cluster manager is specified for the cluster that defines the
server blade on which the message source HA monitor is
running.
(d) No cluster manager is specified for the cluster that defines
the server blade on which the message source HA monitor is
running.

Action For each of the problems (a) through (d), take the following
corrective action:
(a) The system failover configuration of the HA monitor that
output the message contains a management module that does
not have the Highly-reliable HA Monitor License. Purchase the
Highly-reliable HA Monitor License, or create a system failover
configuration in which the cluster management functionality is
disabled for both the HA monitor and the management module.
(b) For all system units, use the Web console to enable the
cluster management functionality for the cluster that defines the
server blade on which the message source HA monitor is
running.
(d) Use the Web console to change the management settings for
the cluster that defines the server blade on which the message
source HA monitor is running, so that only one cluster manager
from among all system units is set to "Enable". After you change
the settings, in the HA monitor window of the Web console,
click the Cluster tab, select the cluster, and then click the
Resume HA cluster manager button.
(d) Use the Web console to change the management settings for
the cluster that defines the server blade on which the message
source HA monitor is running, so that only one cluster manager
from among all system units is set to "Enable".

Note Problem (d) mentioned above is also detected under the


following circumstance: in a configuration involving multiple
system units, the HA monitor starts up in the server blade of the
system unit for which the cluster manager is not specified before
the system unit for which the cluster manager is specified is up
and running. In this case, the error status is resolved when the

3-30 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
No. Item Description
system unit for which the cluster manager is specified is up and
running.

4 Category Web console

Error On the Cluster tab, "Suspended" is displayed as the current


description management status.

Description The cluster management functionality settings specified in the


management module have the following error:
In a configuration involving multiple system units, more than
one cluster manager is specified for the cluster whose status is
"Suspended".

Action Use the Web console to change the management settings for the
cluster whose status is "Suspended", so that only one cluster
manager from among all system units is set to "Enable". After
you change the settings, in the [HA monitor] window of the Web
console, click the Cluster tab, select the cluster, and then click
the Resume HA cluster manager button.

Note When the cluster manager enters the "Suspended" state, the
cluster manager does not restart until it is restarted. The error
status mentioned above might already be resolved even when
the cluster manager is suspended. In this case, simply restart
the cluster manager.
The reset path is in the error state. If a system failure occurs, a
failover cannot be performed.

5 Category Web console

Error On the Cluster tab, "Lost" is displayed as the current


description management status.

Description The cluster manager has disappeared from the cluster whose
status is "Lost". One of the following events occurred:
(a) The system unit containing the management module running
the cluster manager for the cluster whose status is "Lost" was
turned off.
(b) Communication with the management module running the
cluster manager for the cluster whose status is "Lost" was lost.
(c) In the management module running the cluster manager for
the cluster whose status is "Lost", the management setting for
that cluster was disabled.

Action For each of the problems (a) through (c), take the following
corrective action:
(a) Turn on the system unit containing the management module
running the cluster manager for the cluster whose status is
"Lost".
(b) Check for abnormality in the communication path with the
management module running the cluster manager for the
cluster whose status is "Lost".
Use the Web console to change the management settings for the
cluster whose status is "Lost", so that only one cluster manager
from among all system units is set to "Enable" .

Efficient Management of Servers Using the Management Module 3-31


Hitachi Compute Blade 2500 Series Management Module User Guide
No. Item Description

Note The reset path is in the error state. If a system failure occurs, a
failover cannot be performed.

6 Category Web console

Error The Cluster tab displays "Waiting" as the current management


description status.

Description The cluster manager for the cluster whose status is "Waiting"
does not exist. One of the following problems has occurred:
(a) The system unit containing the management module running
the cluster manager for the cluster whose status is "Waiting" is
turned off.
(b) Communication with the management module running the
cluster manager for the cluster whose status is "Waiting" is lost.
(c) This cluster management setting for the system unit whose
cluster status was displayed as "Running" was disabled.

Action For each of the problems (a) through (c), take the following
corrective action:
(a) Turn on the system unit containing the management module
running the cluster manager for the cluster whose status is
"Waiting".
(b) Check for abnormality in the communication path with the
management module running the cluster manager for the
cluster whose status is "Waiting".
Use the Web console to change the management settings for the
cluster whose status is "Waiting", so that only one cluster
manager from among all system units is set to "Enable".

Note The reset path is in the error state. If a system failure occurs, a
failover cannot be performed.

Viewing the host information of the server blade


This section describes how to view the host information of the server blade.

Installing the necessary tool (server installation and monitoring tool)


The server installation and monitoring tool is a tool kit supplied with the
server, which enables automatic installation of the OS and drivers on the
server as well as automatic upgrading of the utilities, drivers, and firmware.
By installing the server installation and monitoring tool in the OS of the
server blade, you can view the OS information (host information) from the
console of the management module.

Host information that can be viewed


The following table describes the host information you can view from the
console of the management module.

3-32 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 3-8 Host information that can be viewed

Information Description Windows Linux

OS#1 Type of the Windows version and The output of /etc/redhat-


OS installed service pack version release is displayed.
on the server Example: Microsoft Example: Red Hat Enterprise
Windows Server 2008 R2 Linux Server release 6.5
Enterprise Service Pack 1 (Santiago)

Host name#2 Host name Computer name The output of the hostname
specified for command is displayed.
the OS
installed on
the server

#1
Special characters included in the OS name are omitted from the OS
name displayed on the console.
#2
Use single-byte alphanumeric characters and symbols to specify a host
name. If you use characters other than single-byte alphanumeric
characters and symbols, the host name is not displayed correctly on the
console.
After the OS starts up and the server installation and monitoring tool is
automatically activated, the host information is saved to the server blade.
Even when you change the host name, it is not immediately applied to the
host name displayed on the console. To apply the new host name, restart the
OS. Even when you shut down the OS, the host information saved to the
server blade is retained. If you perform the following operations, the host
information displayed on the Web console might be different from the actual
OS information:
• Uninstall the server installation and monitoring tool.
• Uninstall the OS from the server and then reinstall the OS supported by
the server installation and monitoring tool on the server without installing
the server installation and monitoring tool.
• Uninstall the OS from the server and then reinstall the OS not supported
by the server installation and monitoring tool on the server.
If this is the case, delete the host information saved to the server blade.
You can delete the host information from the console of the management
module.
The following table describes the consoles that you can use to check or delete
the host information.

Efficient Management of Servers Using the Management Module 3-33


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 3-9 Consoles used to view or delete the host information

Operation Web console CLI console LCD touch console

Display the host Y Y --


information.

Delete the host information. Y Y --

When the server installation and monitoring tool is installed on the active
server blade in the N+M cold standby configuration, the host information is
saved to the standby server blade at the following timing: the N+M failover
occurs and the server installation and monitoring tool starts up on the
standby server blade. Even when the N+M recovery occurs and the active
server blade takes over for the standby server blade, the host information
saved to the standby server blade is retained. You can also delete the host
information saved to the standby server blade by using the host information
deletion functionality.

Related topics
• Notes on viewing the host information on page 3-34
• Displaying the host information on page 3-34
• Deleting the host information on page 3-35

Notes on viewing the host information


Keep the following information in mind when viewing the host information:
• You cannot view the host information unless the server installation and
monitoring tool version X.3.3.6 or later (for ESXi version 4.3.3.3 or later)
is installed in the OS.
• The host information can be displayed for Windows, Linux, and VMware.
• The server installation and monitoring tool does not support displaying of
the host information regarding the guest OS in a virtual environment
(such as Hyper-V, LPAR manager, and VMware).

Displaying the host information


To display the host information, use the Web console or CLI console.
To display the host information from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. On the Hosts tab, check the host information.
To display the host information from the CLI console:
1. Execute the show blade os-info command.

3-34 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• show blade os-info on page 5-75

Deleting the host information


To delete the host information, use the Web console or CLI console. You can
delete the host information only when the server blade is turned off.
To delete the host information from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. On the Hosts tab, click the Clear Host Information button.
The host information (such as the host name and the OS name) collected
from the server blade is cleared.
To delete the host information from the CLI console:
1. Execute the delete blade os-info command.

Related topics
• delete blade os-info on page 5-30

Managing user account information by using LDAP


This section describes how the management module and server blades link
with LDAP server.

LDAP linkage
The CB 2500 can authenticate users by searching an LDAP directory on an
LDAP server through LDAP. This functionality allows you to do the following:
• Log in to the management module and the server blades as a user
registered with the LDAP directory.
• Use group authentication to only allow user accounts belonging to a
certain group in the LDAP directory to log in.
The following modules support LDAP:
• Server blade (SMASH-CLP and WS-Management for BMC)
• Management module
With LDAP linkage, during user authentication, the module determines
whether a user can log in based on the user account information that is
registered in each module or stored in the LDAP directory. You can add the
user account information to the LDAP directory on an LDAP server. This
allows the additional information to become available to all modules that use
the server, eliminating the need for each module to have the account
information.

Efficient Management of Servers Using the Management Module 3-35


Hitachi Compute Blade 2500 Series Management Module User Guide
Also, group authentication allows only user accounts belonging to a group to
log in by looking up group information in the LDAP directory during user
authentication.
If the modules are not linked with an LDAP server, users can only use their
account registered in each module to log into the module.
If the modules are linked with an LDAP server, you can select either of the
following two authentication methods:
• First, users are authenticated by using their accounts registered in each
module. If the authentication fails, users are authenticated by using their
accounts in the LDAP directory.
• Users are authenticated by using their accounts in the LDAP directory
only.
Even if the modules are linked with an LDAP server, the former authentication
method enables users to use their account registered in each module to log
into the module. If the LDAP directory contains the account information that
has the same name as each module, the former authentication method first
uses the information registered in each module for authentication. If
authentication that uses accounts registered in each module fails, accounts in
the LDAP directory are used for authentication.
To set whether the server blades link with an LDAP server, use the Web
console. In addition, to specify the setting to select the authentication
method used when the server blades link with an LDAP server, use the Web
console. To specify the settings from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. From the Edit menu in the BMC tab, select the LDAP item.
3. Specify the following settings: whether the server blades link with an
LDAP server, and the authentication method used when the server blades
link with an LDAP server.
To set whether the management module links with an LDAP server, use the
Web console or the CLI console. To specify the setting to select the
authentication method used when the management module links with an
LDAP server, use the CLI console. To specify the following settings, use the
CLI console to execute the set user ldap server command: whether the
management module links with an LDAP server, and the authentication
method used when the management module links with an LDAP server. To
use the Web console to specify the settings for whether the management
module links with an LDAP server:
1. From the tree view in the Administration tab, select LDAP.
2. From the Edit menu, select Edit LDAP server settings.
3. Disables or enables the LDAP linkage.
You can configure a maximum of three LDAP servers for a module. If a
module has multiple servers configured, during user authentication, it
attempts to connect to those servers, in the order that they were configured.
It searches the LDAP directory on the first LDAP server that it has

3-36 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
successfully connected to, and tries to authenticate the user. If the module
fails to connect to all the configured LDAP servers, user authentication with
the LDAP servers fails.
Supported LDAP servers
The CB 2500 can work with Active Directory included with the following
versions of Windows Server:
¢ Microsoft® Windows Server® 2012 Standard
¢ Microsoft® Windows Server® 2012 Datacenter
¢ Microsoft® Windows Server® 2008 R2 Standard
¢ Microsoft® Windows Server® 2008 R2 Enterprise
¢ Microsoft® Windows Server® 2008 Standard
¢ Microsoft® Windows Server® 2008 Enterprise

Related topics
• set user ldap server on page 5-173
• General procedure for configuring Active Directory on page 3-37

General procedure for configuring Active Directory


This subsection describes the settings necessary to use Active Directory as an
LDAP server. The following figure illustrates the necessary settings.

Figure 3-7 Configuring Active Directory

Related topics
• Registering a server certificate on page 3-38
• Registering a user for connecting to an LDAP server on page 3-38
• Registering a user account for logging into the management module and
server blades on page 3-39
• Registering a group that is used for group authentication on page 3-41

Efficient Management of Servers Using the Management Module 3-37


Hitachi Compute Blade 2500 Series Management Module User Guide
Registering a server certificate
A server certificate must be registered with an Active Directory that is used
as an LDAP server because the system unit communicates everything with an
LDAP server over TLS, excluding the connection start time.
For details about how to register the server certificate, see the documentation
supplied with your Windows Server.
There are two types of server certificates: self-signed certificates and
certificates trusted by an external certificate authority. The system unit can
communicate with Active Directory properly by using either of them.

Registering a user for connecting to an LDAP server


The module must connect to an LDAP server in order to search an LDAP
directory during user authentication. Use either of the following methods to
connect to an LDAP server:
• Connecting to the server by using an LDAP bind DN and password
(recommended)
• Connecting to the server as an Anonymous user

Registering a user account used as a bind DN


Register a user account that is used as an LDAP bind DN to your Windows
Server. For details about how to register the user accounts, see the
documentation supplied with your Windows Server.
Any user account used as an LDAP bind DN must have access to the LDAP
directory used for user authentication.

Registering an Anonymous user


To configure an Anonymous user:
1. Select Start > Run, type mmc, and then click the OK button.
The Microsoft Management Console (MMC) window appears.
2. Select Menu > File > Add/Remove Snap-in, and then in the Add
Standalone Snap-in dialog box, click the Add button.
A list of snap-ins that can be added appears.
3. Select ADSI Edit, click the Add button, and then click the Close button.
4. After ADSI Edit is added in the Add/Remove Snap-in dialog box, click the
OK button.
ADSI Edit is added to Console Root of the MMC window.
5. In the MMC window, point to ADSI Edit and right-click it, and then select
Connect to ....
6. Select Domain for the context of the Active Directory domain to be
connected, and then click the OK button.
7. Right-click ADSI Edit again and select Connect to ....

3-38 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
8. Select Configuration as the context and click the OK button.
9. Point to \ADSI Edit\configuration\CN=Configuration
\DC=DomainBase\CN=Services\CN=Windows NT\CN=Directory
Service on the control and right-click it, and then select Properties.
10. In the Properties dialog box, click dSHeuristics, Edit button, and then
set a value in the edit dialog box.
If this attribute is not set (if <Not Set> is displayed), set it to 0000002. If
the attribute already has a set value, only change the seventh figure from
the left to 2, and do not change the other figures.
11. When you are finished, in the Properties dialog box, click the OK button
to apply your change.

Registering a user account for logging into the management module


and server blades
You can register a user accounts to an LDAP directory by selecting
Administrative Tools > Active Directory Users and Computers. For
details about how to register the user accounts, see the documentation
supplied with your Windows Server.
This subsection describes the restrictions on user names and passwords to be
registered. It also explains how to provide role information that is used after
a user logs into the management module.

User name
The following table describes the available characters and length for the user
name.

Table 3-10 Available characters and length for the user name

Item Available values

Number of characters 1 - 31 characters

Available characters (for the A-Z, a-z


first letter)

Available characters (for the A-Z, a-z, 0-9, hyphen (-), underscore (_), period (.)
second letter and later)

Password
The following table describes the available characters and length for the
password. The complexity of passwords varies depending on the security
policy of your Windows Server.

Efficient Management of Servers Using the Management Module 3-39


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 3-11 Available characters and length for the password

Item Available values

Number of characters 1 - 31 characters

Available characters Printable ASCII characters (0x20-0x7e)

Providing role information


You can define actions available to a logged-in user by providing role
information to that user account registered in the LDAP directory. If no role
information is provided, the logged-in user can only perform the minimum
actions.
To provide the role information:
1. Select Start > Run, type mmc, and then click the OK button.
The Microsoft Management Console (MMC) window appears.
2. Select Menu > File > Add/Remove Snap-in, and then in the Add
Standalone Snap-in dialog box, click the Add button.
A list of snap-ins that can be added appears.
3. Select ADSI Edit, click the Add button, and then click the Close button.
4. After ADSI Edit is added in the Add/Remove Snap-in dialog box, click the
OK button.
Confirm that ADSI Edit is added to Console Root of the MMC window.
5. On the MMC window, point to ADSI Edit and right-click it, and then
select Connect to ....
6. Select Domain for the context of the Active Directory domain to be
connected, and then click the OK button.
7. Expand the ADSI Edit tree, right-click a user account to which you want
to provide with roles in the LDAP directory, and then open Properties.
A list of attributes assigned to that user account is displayed.
8. In the list of attributes, select the attribute whose syntax is set to
Unicode String and whose value is <Not Set>, and then click the Edit
button.
9. Set the roles for the server blades.
Enter a role setting string for server blades in the following format:
ServerBladeRole=XXXXXXXX (where each X indicates 0 or 1)
Each X in the XXXXXXXX string, from the left to right,
represents the following roles.
(1) Login: The user for which this role is assigned will be able
to log in to the server blade BMC.
(2) Administrator: The user for which this role is assigned will
be able to use the functionality of the server blade BMC.
(3) Server Operation (#)
(4) User Account Management (#)
(5) Service Settings (#)
(6) Remote Console (#)
(7) Remote Media (#)

3-40 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
(8) SMASH-CLP: The user for which this role is assigned will be
able to use SMASH-CLP and WS-Management for the server blade
BMC.
#: The role is not available in this unit. Set this value to 0.
10. Set the roles for your management modules.
Enter a role setting string for management modules in the following
format:
ManagementModuleRole=role_name
The role_name variable represents the role name defined in the
management module.

Tip: If you want to enter the role setting strings for both server blades
and management modules in a single line, use a space character to
separate the entries.
Example: ServerBladeRole=11000001
ManagementModuleRole=Administrators
11. After the role settings are entered, click the OK button.
12. After the window returns to the Properties dialog box, click the OK
button.

Registering a group that is used for group authentication


Register a group that is used for group authentication. If you do not use
group authentication, this setting is not required.
To register a group, open Administrative Tools > Active Directory Users
and Computers, and create two groups in the LDAP directory. One group is
allowed to log into server blades. Another group is allowed to log in to the
management module. After you create the groups, register user accounts to
each group that are allowed to log in.
The groups that are allowed to log into the server blades and management
modules can be combined into one group.
For details about how to create a group and register the user accounts to a
group, see the documentation supplied with your Windows Server.

Overview of configuring management modules and server blades for


LDAP linkage
This subsection describes the setting items for management module settings
for LDAP linkage. For details about how to configure a server blade, see the
BMC settings window for each server blade of the management module Web
console.
• Setting whether to enable or disable use of LDAP.
This setting enables you to configure whether the module links with LDAP
server. This functionality is disabled when the system unit is shipped. If
this functionality is enabled, the module searches the LDAP directory on
an LDAP server to attempt authentication.
• Setting the authentication method when LDAP linkage is enabled

Efficient Management of Servers Using the Management Module 3-41


Hitachi Compute Blade 2500 Series Management Module User Guide
For details about the authentication methods with LDAP linkage, see LDAP
linkage on page 3-35.
• LDAP servers registration
You can configure a maximum of three LDAP servers. They can be
specified by using either their IP addresses or host names.
• LDAP server connection settings
¢ Port number
¢ Bind DN and bind password
If you have registered a user account used as a bind DN in
Registering a user for connecting to an LDAP server on page 3-38, set
the DN and password of the registered user account. If you use an
Anonymous user for connection, you do not need to set a bind DN or
bind password.
• LDAP directory search settings
Configure the following settings necessary for searching the LDAP
directory:
¢ Base DN
Set the location from which the LDAP directory search starts.
¢ Attribute that represents a login ID
Set the attribute that has the login ID of a user account.
¢ Attribute that represents a role
If a role is assigned to a user account, specify the attribute that is
used to assign the role.
You can set the following items related to the LDAP directory search:
• Number of inquiry times
For the number of the inquiry times item, set the number of times in
which LDAP servers are traced based on the referral information and
inquired (such as searched) if an LDAP server refers to other LDAP
servers in order to achieve the method that divides and manages the
LDAP directory by using multiple LDAP servers. If you set this setting to
0, each module does not trace the referred LDAP server even if an LDAP
server refers to another LDAP server.
• Group authentication settings
To use group authentication, configure the settings below. If group
authentication is not used, these settings are not required.
¢ Group authentication method
If group authentication is not used, an account registered in each
module or in the LDAP directory is used for user authentication
according to the authentication method setting used when LDAP
linkage is enabled if the module is set to link with an LDAP server.
If you use group authentication, you can select either of the following
two group authentication methods:
- Static group authentication method

3-42 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
- Dynamic group authentication method
The former authentication method performs authentication by
checking whether the user account to be authenticated belongs to the
DN of the group that is allowed to log in that is described later. The
latter authentication method performs authentication by checking
whether the user account to be authenticated is included among all
user accounts that satisfy the conditions set for the search filter that
are described later.
• Group member attribute (management module only)
This setting item is valid when the group authentication method is set to
the static group authentication method.
If this setting item is not specified, the management module checks the
attribute value of the tokenGroups attribute of the user account, and then
checks the attribute value of the objectSid attribute of the DN of the
group that is allowed to log in. Then, depending on whether the two
attribute values match, the management module determines whether the
user account belongs to the DN of the group that is allowed to log in. If
the management module could not acquire the attribute value of the
tokenGroups attribute of the user account, the management module
checks the attribute value of the gidNumber attribute, and then checks
the attribute value of the gidNumber attribute of the DN of the group that
is allowed to log in. Then, depending on whether the two attribute values
match, the management module determines whether the user account
belongs to the DN of the group that is allowed to log in. If none of the
attribute values of the tokenGroups attribute or the gidNumber attribute
can be acquired, authentication fails.
If this setting item is specified, depending on whether the DN of the user
account is set for the attribute value of the attribute that is set for this
setting item of the DN of the group that is allowed to log in, the
management module determines whether the user account belongs to the
DN of the group that is allowed to log in.
If you use the LDAP directory in which the tokenGroups attribute or the
gidNumber attribute can be used to determine whether the user account
belongs to the DN of the group that is allowed to log in, you do not need
to specify this setting item.
¢ DN of the group that is allowed to log in
This setting item is valid when the group authentication method is set
to the static group authentication method.
Specify the DN of the group that is created when the group is
configured.
¢ Role of the DN of the group that is allowed to log in
This setting item is valid when the group authentication method is set
to the static group authentication method.
If this setting item is not specified, use the attribute value of the
attribute that represents the role of the user account to assign a role.
If this setting item is specified, use the setting value to assign a role.
If the role of the setting value does not exist in the role settings for

Efficient Management of Servers Using the Management Module 3-43


Hitachi Compute Blade 2500 Series Management Module User Guide
the management module, the logged-in user can only perform
minimum actions.
¢ Search DN for the dynamic group
This setting item is valid when the group authentication method is set
to the dynamic group authentication method.
Set the location from which the LDAP directory search starts during
dynamic group authentication.
¢ Search filter for the dynamic group
This setting item is valid when the group authentication method is set
to the dynamic group authentication method.
Set the attribute and attribute value conditions used when the LDAP
directory is searched during dynamic group authentication.
¢ Role of the dynamic group
This setting item is valid when the group authentication method is set
to the dynamic group authentication method.
If this setting item is not specified, use the attribute value of the
attribute that represents the role of the user account to assign the
role. If this setting item is specified, use the setting value to assign
the role. If the role of the setting value does not exist in the role
settings for the management module, the user who has logged in to
the management module can only perform minimum actions.
The following table describes the consoles that you can use to perform
specific operations from the management module.

Table 3-12 Consoles used for LDAP linkage settings

Operation Web console CLI console LCD touch console

Configure the settings to Y1 Y2 --


connect to the LDAP server
(LDAP server, port number,
bind DN, and bind
password).

Configure the settings Y1 Y2 --


related to the LDAP
directory search.

Configure the settings to Y1 Y2 --


identify a group in the
management module.

Notes:
1. You can specify the settings for server blades. You can specify some of the settings
for the management module.
2. You can specify the settings for the management module only.

Related topics
• Setting the information to connect to an LDAP server on page 3-45

3-44 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• Configuring the information related to the LDAP directory searches on
page 3-46
• Setting the information to identify a group on page 3-46

Displaying the settings for linking with an LDAP server


To display the settings related to linkage with an LDAP server of the
management module, use the Web console or the CLI console. To display the
LDAP linkage settings in the Web console, from the tree view in the
Administration tab, select LDAP. To use the CLI console to display the
LDAP linkage settings, execute the show user ldap command.
For details about how to configure a server blade, see the BMC settings
window for each server blade of the management module Web console.

Related topics
• show user ldap on page 5-179

Setting the information to connect to an LDAP server


To configure the information for connecting to an LDAP server on the
management module, use the Web console or the CLI console.
1. From the tree view in the Administration tab, select LDAP.
2. From the Edit menu, select Edit LDAP server settings.
3. Configure the settings, such as enabling or disabling LDAP authentication,
the host name of the LDAP server, the port number used to connect to
the LDAP server, the bind DN, and the bind password.
To use the CLI console to configure the settings for connecting to an LDAP
server, depending on the operation you are going to perform, execute one of
the commands listed in the following table.

Table 3-13 Commands used to configure the settings to connect to the


LDAP server

Operation Command

Setting to enable or disable use of LDAP. set user ldap server

Authentication method setting when LDAP linkage is enabled

Register, change, or delete LDAP servers.

Configure the settings used for connecting to an LDAP server


(port number, bind DN, and bind password).

For details about how to configure a server blade, use the Web console. To
specify the settings from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.

Efficient Management of Servers Using the Management Module 3-45


Hitachi Compute Blade 2500 Series Management Module User Guide
2. From the Edit menu in the BMC tab, select the LDAP item.
3. Configure the settings to connect to the LDAP server.

Related topics
• set user ldap server on page 5-173

Configuring the information related to the LDAP directory searches


To configure the information related to the LDAP directory searches on the
management module, use the Web console or the CLI console.
To configure the information necessary to search LDAP directories
from the Web console:
1. From the tree view in the Administration tab, select LDAP.
2. From the Edit menu, select Edit directory search settings.
3. Enter the information, such as a base DN, login ID attribute, and role
attribute.
To configure the information necessary to search LDAP directories from the
CLI console, execute the set user ldap search command.

Table 3-14 Commands used to configure the settings related to the LDAP
directory search.

Operation Command

Set the base DN. set user ldap search

Set the login ID attribute.

Set the role attribute.

Set the number of inquiry times.

For details about how to configure a server blade, use the Web console. To
specify the settings from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. From the Edit menu in the BMC tab, select the LDAP item.
3. Configure the settings to connect to the LDAP server.

Related topics
• set user ldap search on page 5-172

Setting the information to identify a group


To configure the settings to identify a group on the management module, use
the Web console or CLI console.

3-46 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To configure the settings to identify a group by using the Web
console:
1. From the tree view in the Administration tab, select LDAP.
2. From the Edit menu, select Edit group authentication settings.
3. Enter a member attribute, group DN, and other necessary information.
To configure the settings to identify a group by using the CLI console,
execute the set user ldap group command.

Table 3-15 Commands used to configure the settings to identify a group

Operation Command

Specify the setting to enable or disable group authentication and set user ldap group
the setting of the authentication method.

Set the group member attribute.

Register, change, or delete the DN of the group that is allowed


to log in.

Register, change, or delete the role of the DN of the group that


is allowed to log in.

Set the information related to the dynamic group authentication


(search DN, search filter, and role of the dynamic group).

For details about how to configure a server blade, use the Web console. To
specify the settings from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. From the Edit menu in the BMC tab, select the LDAP item.
3. Configure the settings to connect to the LDAP server.

Related topics
• set user ldap group on page 5-169

Initializing the LDAP linkage settings


To initialize the LDAP linkage settings of the management module, use the
CLI console. To use the CLI console to initialize the LDAP linkage settings,
execute the clear user ldap command.

Related topics
• clear user ldap on page 5-162

Managing user account information by using RADIUS


This section describes RADIUS authentication in the management module.

Efficient Management of Servers Using the Management Module 3-47


Hitachi Compute Blade 2500 Series Management Module User Guide
Overview
In this system unit, you can authenticate users by using Remote
Authentication Dial In User Service (abbreviated hereafter to RADIUS).
If RADIUS authentication is used, during user authentication, the
authentication result on the RADIUS server determine whether a user can log
in. If you add information of a user account to the RADIUS server, the added
user account can be used to log in to all modules that use RADIUS
authentication. You do not have to register the user account information in
each module.
The following two authentication methods can be used for RADIUS
authentication:
• Authenticate users by using their accounts registered in each module. If
the authentication fails, users are authenticated by using the RADIUS
server.
• Authenticate users by the RADIUS server only.
You can register a maximum of three RADIUS servers. If you register multiple
RADIUS servers, during user authentication, an attempt is made to connect
to those servers in the order that they were registered. User authentication is
attempted by using the first RADUIS server to which a connection can be
made. If a connection cannot be made to any of the registered RADIUS
servers, the user authentication fails.

Supported RADIUS servers


This system unit supports RADIUS authentication that uses Network Policy
Server or FreeRADIUS of the following versions of Windows Server:
• Microsoft® Windows Server® 2008 R2, Standard
• Microsoft® Windows Server® 2008 R2, Enterprise
• Microsoft® Windows Server® 2008, Standard
• Microsoft® Windows Server® 2008, Enterprise
• Microsoft® Windows Server® 2012, Standard
• Microsoft® Windows Server® 2012, Datacenter

Settings for the RADIUS server


Before using RADIUS authentication, you need to register the management
module as a RADIUS client.
For details about how to register a RADIUS client, see the documentation for
the RADIUS server.

Settings for the management module


You need to configure the following settings for the management module
when using RADIUS authentication.

3-48 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
• RADIUS authentication settings
You can configure whether to perform RADIUS authentication.
The setting is disabled when the system unit is shipped.
If you enable this setting, RADIUS authentication is attempted during
user authentication.

Note: You cannot use LDAP linkage and RADIUS authentication at the
same time.
If you use RADIUS authentication, disable the LDAP linkage settings.
• Setting of the user authentication method when RADIUS authentication is
enabled
For details about the authentication methods used when RADIUS
authentication is performed, see "Overview on page 3-48".
• Roles for the RADIUS-authenticated users
You can specify the roles to be assigned to users who logged in through
user authentication using the RADIUS server.
• RADIUS server registration
You can register a maximum of three RADIUS servers. Specify the
following items for each of the RADIUS servers to be registered.
¢ Server name
You can specify the IP address (IPv4/IPv6) or host name.
¢ Shared Secret
This is the password shared between the RADIUS server and the
management module.
You need to specify the same value as the one set in the RADIUS
server.
We recommend that you use a complex password that is at least 32
characters in length, and contains alphanumeric characters and
symbols.
¢ Authentication method
This is the authentication method used when you perform user
authentication using the RADIUS server.
You can select PAP, CHAP, or MS-CHAPv2.
¢ Port number
Specify the port number used for communication with the RADIUS
server. A communication attempt is made to the port specified here.
¢ Timeout period
During communication with the RADIUS server, if there is no response
from the RADIUS server within the time specified here, the
communication is assumed to have failed. If a value is specified for
retransmit retry, a retransmission attempt is made.
¢ Retransmit retry
If a timeout occurs during communication with the RADIUS server,
retransmission attempts are made for the number of times specified
here. If the RADIUS server does not respond even when

Efficient Management of Servers Using the Management Module 3-49


Hitachi Compute Blade 2500 Series Management Module User Guide
retransmission attempts are made, an attempt is made to connect to
the second RADIUS server that is registered. If communication cannot
be established with any of the registered RADIUS servers, the
authentication fails.

RADIUS server connection confirmation


You can check the connection to the RADIUS server.
An attempt is made to authenticate the users for the RADIUS servers that
were configured during RADIUS server registration, and to display the results.
You need to specify the user account and password when checking the
connection.

Specifying the RADIUS server authentication settings


To specify the RADIUS server authentication settings when performing
RADIUS authentication, use the Web console.
To specify the RADIUS server authentication settings from the Web
console:
1. From the tree view in the Administration tab, select LDAP/RADIUS.
2. From the Edit menu, select Edit RADIUS authentication settings.
Edit the RADIUS authentication settings.

Registering the RADIUS server


To register the RADIUS server, use the Web console.
To register the RADIUS server from the Web console:
1. From the tree view in the Administration tab, select LDAP/RADIUS.
2. From the Edit menu, select Edit RADIUS server settings.
Edit the RADIUS server settings.

Checking the connection to the RADIUS server


To check the connection to the RADIUS server, use the Web console:
To check the connection to the RADIUS server from the Web console:
1. From the tree view in the Administration tab, select LDAP/RADIUS.
2. From the Edit menu, select RADIUS server connection confirmation.
Select the RADIUS server for which you want to check the connection,
and then enter the user account and password to check.

3-50 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Monitoring the operating status of the system unit by using
an SNMP manager
This section describes the SNMP functionality that the management module
provides.

SNMP functionality
The SNMP functionality of the CB 2500 polls the system unit and monitors it
for failures.

Polling
Monitors the system unit from the SNMP manager. The system unit can have
its own Management Information Base (MIB) defined. When the SNMP
manager issues a request for sending the value of a MIB variable to the
system unit, the system unit returns a response that corresponds to the
information defined in the MIB.
The polling functionality only responds to a request with an IP address of
SNMP managers that is registered in the management module.

Traps
The management system sends unprompted messages to an SNMP manager
based on the MIB that is uniquely defined to the system unit. This allows the
SNMP manager to monitor the system unit for failures. The SNMP standard
traps are not supported.

Figure 3-8 Overview of the SNMP functionality

Efficient Management of Servers Using the Management Module 3-51


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Specifications for SNMP functionality on page 3-52

Specifications for SNMP functionality


The following tables list the specifications for each SNMP functionality.

Table 3-16 Specifications for SNMP polling

Item Description

Supported commands SNMPv1, SNMPv2c, and SNMPv3 (Get,


GetNext, and GetBulk)

Maximum number of SNMP managers to be 9


notified simultaneously

Type of supported modules • Server blade


• Management module
• Switch module
• Power supply module
• Fan module

Table 3-17 Specifications for SNMP traps

Item Description

Notification method SNMP (SNMPv2 trap/SNMPv3 trap)

Maximum number of SNMP managers 9


to be notified simultaneously

Notification trigger Triggered by a failure SEL that occurred in the


management module

Values to be First variable Time when the alert was sent


notified binding

Second variable ID of the chassis where the alert occurred


binding

Third variable Level of the alert


binding

Fourth variable ID of the alert


binding

Fifth variable Alert message


binding

Seventh variable Type of the module where the alert occurred


binding

Eighth variable Position of the module where the alert occurred


binding

Ninth variable Name of the module where the alert occurred


binding

3-52 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description

Tenth variable Serial number of the module where the alert


binding occurred

Eleventh variable Event code of the alert


binding

Twelfth variable Expansion event code of the alert


binding

Thirteenth variable Model name of the equipment where the alert


binding occurred

Fourteenth variable Serial number of the equipment where the alert


binding occurred

Fifteenth variable Notification trigger of the alert


binding

Table 3-18 Specifications for SNMPv3 functionality

Item Description

Authentication method (hashing algorithm) MD5/SHA-1

Encryption method DES/AES128

Requirements for the SNMP functionality


The requirements for using the SNMP functionality are as follows:
• SNMP managers that receive SNMP traps must support SNMPv1,
SNMPv2c, and SNMPv3.
• The management module can communicate with management servers
running the SNMP manager through a network.

General procedure for configuring the SNMP functionality


The following figure illustrates how to configure the settings to use the SNMP
functionality in the management module:

Efficient Management of Servers Using the Management Module 3-53


Hitachi Compute Blade 2500 Series Management Module User Guide
The following table describes the consoles available for configuring the
settings in the management module.

Table 3-19 Configuring the SNMP functionality

Operation Web console CLI console LCD touch console

Obtaining a MIB file for Y Y --


managing a system unit

Configuring an SNMP agent Y Y --

Configuring an SNMP Y Y --
manager

Confirming that the SNMP Y Y --


manager can receive traps
correctly

Related topics
• Getting the Management Information Base (MIB) file for managing a
system unit on page 3-55
• Configuring SNMP manager settings on page 3-55
• Setting items necessary for SNMP agents and managers on management
module on page 3-56
• Configuring SNMP agent settings on the management module on page
3-58
• Configuring SNMP manager settings on the management module on page
3-59
• Confirming that the SNMP manager can receive traps correctly on page
3-59

3-54 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Getting the Management Information Base (MIB) file for managing a
system unit
You can export a MIB file for managing a system unit in the console of the
management module.
If the firmware of the management module is updated to a newer version and
a new OID is added, export the MIB file again after the firmware of your
management module is updated. You can also check the version of the MIB
that can be exported from the management module by using the console of
the management module.
To export the MIB file from the Web console:
1. From the tree view in the Administration tab, select SNMP.
The version of the MIB file is displayed.
2. From the MIB tab, click the Download MIB file button.
The MIB file is downloaded.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.
In such a case, download the file again.
To export the MIB file from the CLI console:
1. You can download the MIB file by executing the export snmp mib
command. The show snmp mib command allows you to check the version
of the MIB file.

Related topics
• export snmp mib on page 5-232
• show snmp mib on page 5-238

Configuring SNMP manager settings


You must perform the operations below for your SNMP manager. For details
about how to perform each procedure, see the manual supplied with the
SNMP manager.
• Registering the MIB file
• Registering trap events
• Selecting MIB variables to be polled and configuring the necessary
settings for polling

Efficient Management of Servers Using the Management Module 3-55


Hitachi Compute Blade 2500 Series Management Module User Guide
For details about detailed trap event information and the MIB variables to be
polled, see Hitachi Compute Blade 2500 Series MIB User Guide.

Setting items necessary for SNMP agents and managers on


management module
This subsection provides information about SNMP agent and manager settings
that you configure from the management module console.
The following table describes the setting items for SNMP agent.

Table 3-20 Setting items for SNMP agent

Item Description

SNMP agent Select whether to enable or disable the SNMP agent


functionality.
This setting specifies whether to use the SNMP
functionality.

System administrator Specify the contact information of the system


administrator.
You can use up to 60 alphanumeric characters and
symbols.

System location Specify where the system is located.


You can use up to 60 alphanumeric characters and
symbols.

Port number Specify a port number for the SNMP protocol.


You can use a numeric value from 1 to 65535. The default
value is 161.

Trap level You can select one of the following levels for trap
notifications:
All: Trap notifications at all levels of Failure, Alert, and
Information are sent.
Alert: Trap notifications at levels of Failure or Alert is sent.
Information: Trap notifications at the level of Information
is sent.
Disable: No trap notification is sent.

SNMP version1 Specify the SNMP versions available for the agent.
You can specify either v1/v2c or v1/v2c/v3 value.

Character string for creating (This setting item is enabled only if the SNMP version is
engine ID set to v1/v2c/v3.)
A character string for the generation of an engine ID to be
used by the agent is displayed.
You can use up to 27 alphanumeric characters and
symbols.

Engine ID (This setting item is enabled only if the SNMP version is


set to v1/v2c/v3.)
The engine ID used by the agent is displayed.

3-56 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description
This ID is automatically generated from the character
string for creating the engine ID.

Note:
1. If you set the security level of the management module to [High], specify the SNMP
version to v1/v2c/v3. If the SNMP version is not specified, the module does not
respond to SNMP managers and does not issue any SNMP trap.

The following table describes the setting items for SNMP manager.

Table 3-21 Setting items for SNMP manager

Item Description

Host name Specify an IP address or host name of the SNMP


manager.

Port number Specify a port number on which the SNMP manager


receives traps.
You can use a numeric value from 1 to 65535. The
default value is 162.

SNMP version1 Select the version of SNMP that the SNMP manager
uses.
You can select v1/v2c or v3.

Community name (This setting item is enabled only if the SNMP version is
set to v1/v2c.)
Specify a community name. You can use up to 60
alphanumeric characters and symbols.

User name (This setting item is enabled only if the SNMP version is
set to v3.)
Specifies a user name. You can use up to 32
alphanumeric characters and symbols.

Access type2 (This setting item is enabled only if the SNMP version is
set to v3.)
Select an access type of the SNMP manager. You can
select noAuthnoPriv, AuthnoPriv, or AuthPriv.

Authentication type3 (This setting item is enabled only if the SNMP version is
set to v3 and if the access type is set to AuthnoPriv or
AuthPriv.)
Select an authentication mode in which the SNMP
manager is authenticated. You can select MD5 or SHA.

Authentication password (This setting item is enabled only if the SNMP version is
set to v3 and if the access type is set to AuthnoPriv or
AuthPriv.)
Specify a password used for authentication of the SNMP
manager. You can use at least 8 and up to 64
alphanumeric characters and symbols.

Encryption type4 (This setting item is enabled only if the SNMP version is
set to v3 and if the access type is set to AuthPriv.)

Efficient Management of Servers Using the Management Module 3-57


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description
Specify an encryption method to encrypt
communications with the SNMP manager. You can
select DES or AES.

Encryption password (This setting item is enabled only if the SNMP version is
set to v3 and if the access type is set to AuthPriv.)
Enter a password to encrypt communications with the
SNMP manager. You can use at least 8 and up to 64
alphanumeric characters and symbols.

Notes:
1. If you set the security level of the management module to [High], set the SNMP
version to v3. If the SNMP version is not specified, the module does not respond to
SNMP managers and does not issue any SNMP trap.
2. If you set the security level of the management module to [High], set the access
type to AuthPriv. If the SNMP version is not specified, the module does not respond
to SNMP managers and does not issue any SNMP trap.
3. If you set the security level of the management module to [High], set the
authentication type to SHA. If the SNMP version is not specified, the module does
not respond to SNMP managers and does not issue any SNMP trap.
4. If you set the security level of the management module to [High], set the encryption
type to AES. If the SNMP version is not specified, the module does not respond to
SNMP managers and does not issue any SNMP trap.

Note:
• When registering the SNMP manager with an IPv6 address that uses
SNMPv1 or SNMPv2c, specify the IPv6 address for [Host name] of the
SNMP manager. If you specify the host name, the relevant management
module will not be detected as a node on the SNMP manager.
If you register the SNMP manager with an IPv4 address that uses SNMPv1
or SNMPv2c, you can specify the IPv4 address or the host name.
If you register the SNMP manager that uses SNMPv3, regardless of
whether the SNMP manager uses an IPv4 or IPv6 address, you can
specify the IP address or the host name for [Host name].

Related topics
• Configuring SNMP agent settings on the management module on page
3-58
• Configuring SNMP manager settings on the management module on page
3-59

Configuring SNMP agent settings on the management module


To configure SNMP agent settings on the management module, use the Web
console or the CLI console.
To configure the SNMP agent settings from the Web console:
1. From the tree view in the Administration tab, select SNMP.

3-58 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
2. From the SNMP agent tab, click the Edit button.
Edit SNMP agent settings.
To configure the SNMP agent settings from the CLI console:
1. To see the current SNMP agent settings, execute the show snmp agent
command. To edit the settings, execute the set snmp agent command.

Related topics
• show snmp agent on page 5-235
• set snmp agent on page 5-232

Configuring SNMP manager settings on the management module


To configure SNMP manager settings on the management module, use the
Web console or the CLI console.
To configure the SNMP manager settings from the Web console:
1. From the tree view in the Administration tab, select SNMP.
2. From the SNMP manager tab, select the target SNMP manager and click
the Edit button.
Edit SNMP manager settings.
To configure the SNMP manager from the CLI console:
1. To see the current SNMP manager settings, execute the show snmp
manager command. To edit the settings, execute the set snmp manager
command.

Related topics
• show snmp manager on page 5-236
• set snmp manager on page 5-233

Confirming that the SNMP manager can receive traps correctly


You can use one of the consoles of the management module and test SNMP
trap notifications to confirm that the SNMP manager can receive traps
correctly. If the manager cannot receive the traps, review your network
environment and the settings for the SNMP manager and management
module.
To confirm that the SNMP manager can receive the traps correctly, use the
Web console or the CLI console.
To confirm that the SNMP manager can receive the traps correctly
from the Web console:
1. From the tree view in the Administration tab, select SNMP.
2. From the Action pull-down menu, select Send SNMP trap.

Efficient Management of Servers Using the Management Module 3-59


Hitachi Compute Blade 2500 Series Management Module User Guide
An SNMP trap is sent.
To confirm that the SNMP manager can receive the traps correctly
from the CLI console:
1. Execute the test snmp trap command so that an SNMP trap is to be
sent.

Related topics
• test snmp trap on page 5-238

Notifying the status of the management module through


email
This section describes the email notification functionality provided by the
management module.

Information that can be notified by email


The following email notifications are sent by the email notification
functionality:
• Notification of failure
If a failure occurs in the system unit, the necessary log information is
collected to analyze the failure, and an email message is sent with the log
information attached. The history for notification of failure is stored in the
management module. A maximum of 32 notifications can be stored, the
oldest history record is removed if the maximum limit is exceeded.
• Notification of log dump
When a server blade outputs a log entry, an email message is sent with
the log information attached. This email message provides supplementary
information about a notification of failure.
The notification of log dump can be triggered by a manual log output on
the server blade. In this case, a notification-of-log-dump email message
is not preceded or followed by any notification-of-failure email message.
• Notification of current status (manually triggered)
The information about the current state of the system unit is collected
and an email message is sent with the information attached.
• Notification of history log (manually triggered)
You can resend any history record that you select from the history of the
notifications of failure.
For example, if the system unit fails when your mail server is not running,
and a notification of failure cannot be sent, you can resend the
notification after the server recovery.
The following table describes which console you can use to configure the
email notification functionality from management modules.

3-60 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 3-22 Configuring the email notification functionality

LCD touch
Operation Web console CLI console
console

Configure email settings, Y Y --


such as a sender and
destination address.

Confirm that an email Y Y --


message can be sent
properly.

Related topics
• Requirements for receiving email notification messages on page 3-61
• Specifications for the email notification functionality on page 3-61
• Setting items for the email notification functionality on page 3-63
• Configuring email notification settings on page 3-64
• Confirming that an email message can be sent properly on page 3-65

Requirements for receiving email notification messages


The requirements for using the email notification functionality are as follows:
• In the email notification functionality, the management module as an
email client sends email messages to a mail server (SMTP server).
Therefore, the SMTP server is required.
• The management module must be able to communicate with the mail
server.

Specifications for the email notification functionality


The following table describes the specifications for the email notification
functionality.

Table 3-23 Specifications for the email notification functionality

Item Description

Notification method Email (SMTP-compliant)

Maximum number of destination addresses 4

Maximum number of SMTP servers 1

Notification trigger • Failure


• Log output from server blades
• Manual operation (for notifications
of the current status and failure
history)

Efficient Management of Servers Using the Management Module 3-61


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description

Notification retry The notifications are re-sent if a


notification of failure or notification of
log dump fails.

Notification Notification of Subject [AUTO] Failure report.


details failure
Body Message description: A failure occurred
in the following device:
Chassis information of the server
Failure information (summary)

Attachment1 svpsts-YYYYMMDD-hhmmss.gz
trc-YYYYMMDD-hhmmss.tar.gz2
marlog.gz

Notification of Subject [AUTO] Log dump report.


log dump
Body Message description: A log was output
in the blade server of the following
device:

Attachment1 One of the following files:


hvmdumpN-YYYYMMDD-hhmmss.gz
raslogN-YYYYMMDD-hhmmss.tar.gz

Notification of Subject [MANUAL] Current status report.


current status
(manually Body Message description: This email
triggered) message was sent manually. It contains
log entries that show the current state
of the device.
Chassis information of the server

Attachment1 svpsts-YYYYMMDD-hhmmss.gz
trc-YYYYMMDD-hhmmss.tar.gz2

Notification of Subject [MANUAL] History report.


history log
(manually Body Same as the notification of failure
triggered)
Attachment1 Same as the notification of failure

SMTP authentication method Can be selected from: No


authentication, PLAIN, LOGIN, or CRAM-
MD5

Encryption method Can be selected from: No encryption or


TLS

Notes:
1. Legend for file name. The YYYYMMDD-hhmmss format indicates the start date and
time of a notification.
(YYYY: year, MM: month: DD: day, hh: hour, mm: minute, ss: second, N: server
blade number (from 1 to 15))
2. Files are not attached to any email message with a destination address whose
[Attach Log] is set to [Disable] in the email address settings.

3-62 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
The following table describes the specifications for the attachment enclosed
with a notification message.

Table 3-24 Specifications for the attachment

File name Description

svpsts_en-YYYYMMDD-hhmmss.gz System unit information

trc-YYYYMMDD-hhmmss.tar.gz Management module log information

hvmdumpN-YYYYMMDD-hhmmss.gz Server blade log information (related to


LPAR manager)

raslogN-YYYYMMDD-hhmmss.tar.gz Server blade log information (related to


hardware)

marlog_en.gz Failure information (same information


as in the body of a notification of failure
message)

Setting items for the email notification functionality


This subsection provides information about email notification settings and
email destination settings that you can configure from one of the consoles of
the management module. The email notification settings consist of the
settings for the management module and for the SMTP server. The email
destination settings specify an email address to which notifications are sent.
The following tables describe the setting items for the email notification.

Table 3-25 Email notification settings

Item Description

Email notification Enable or disable the email notification functionality.


functionality

Sender email address Specify an email address from which notifications are sent,
with 64 or fewer characters.
Alphanumeric characters and the following symbols can be
used: ? @ $ # % ^ - + = _ . [ ]
This address is used as the sender (From) address for email
messages.

Host name Specify the fully qualified domain name (FQDN) of the host,
with 64 or fewer characters.

Comment You can add any comment with 32 or fewer characters.

SMTP server Specify an IP address or host name of the SMTP server.


You can enter the FQDN with 64 or fewer characters.

Port number Specify a port number of the SMTP server in the range
from 1 to 65535. The default value is 25 if the setting for
encryption for SMTP path is disabled or set to [TLS].

Efficient Management of Servers Using the Management Module 3-63


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: The management module does not support email notification by using
IPv6 stateless addresses. To communicate with the SNMP server by using
IPv6 addresses, disable the stateless address setting of the management
module.

Table 3-26 SMTP server authentication settings

Item Description

Functionality Select whether to enable or disable the SMTP


authentication.

SMTP authentication Specify the SMTP authentication method. You can select
method one of the following: PLAIN (plain-text authentication),
CRAM-MD5 (challenge or response method), and LOGIN
(plain-text and interactive authentication).

User name Specify a user name for SMTP authentication with 64 or


fewer characters.
Alphanumeric characters and the following symbols can be
used: ? @ $ # % ^ - + = _ . [] You can also specify a
password.
Both the user name and password are required if the STMP
authentication is enabled.

Table 3-27 Email notification encryption settings

Item Description

Encryption for SMTP path Specify the encryption method for the SMTP path from one
of the following: No encryption and TLS.

The following table describes the setting items for destination information for
the email notification functionality.

Table 3-28 Destination information

Item Description

Email address Specify an email address to which notifications are sent, with 64
or fewer characters.
Alphanumeric characters and the following symbols can be
used: ? @ $ # % ^ - + = _ . []

Nickname Specify a nickname for the destination with 15 or fewer


characters.
This name is only used for displaying in the console, and is not
used for notifications.

Attach log file Specify whether to attach a log file to an email message.

Configuring email notification settings


To configure notification-related settings, such as a sender and destination
address for email messages, use the Web console or the CLI console.

3-64 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
To configure the notification-related settings from the Web console:
1. From the tree view in the Administration tab, select Email
Notification.
2. From the Notification Settings or Destinations Settings tab, click the
Edit button.
Set the necessary items.
To configure the notification-related settings from the CLI console:
1. Depending on the operation you are going to perform, execute one of the
commands listed in the following table.

Operation Command

Display the email notification settings show e-mail mgmt-lan

Configure the email notification settings set e-mail mgmt-lan notification

Add and configure an email destination address set e-mail mgmt-lan address

Remove the email destination address delete e-mail mgmt-lan address

Related topics
• Specifications for the email notification functionality on page 3-61
• show e-mail mgmt-lan on page 5-219
• set e-mail mgmt-lan notification on page 5-207
• set e-mail mgmt-lan address on page 5-206
• delete e-mail mgmt-lan address on page 5-202

Confirming that an email message can be sent properly


When you have configured the email notification functionality, send a
notification of current status (manually triggered) message to test email
notification. You can select a destination email address from the list of
configured addresses. You can select a single address or all the addresses.
To check if email messages can be sent properly, use the Web console or the
CLI console.
Keep the following information in mind when you test email transmission:
• It can take several minutes to collect log information.
• If a notification is sent to multiple destinations, failure to send it to one of
the destinations can result in failure to send it to all the destinations.
• If a notification fails, review your environment and settings based on the
notification result message and the following procedures:
¢ Check if the management module can communicate with your mail
server.
If it cannot communicate with the server, check:
- The proper connection of your network cables

Efficient Management of Servers Using the Management Module 3-65


Hitachi Compute Blade 2500 Series Management Module User Guide
- The network configuration of your management module
- The specification of the DNS address in the network configuration of
your management module if the host name is used to specify the mail
server
¢ Check if the SMTP service is running on the SMTP server.
If the SMTP service is not running, start it.
¢ Check if the notification settings and destination settings are properly
configured for the email notification functionality.
To check if an email message can be sent properly from the Web
console:
1. From the tree view in the Administration tab, select Email
Notification.
2. From the Action pull-down menu, select Present condition
notification.
A notification message with the current state is sent.
To check if an email message can be sent properly from the CLI
console:
1. Execute the send e-mail latest mgmt-lan command.

Related topics
• Specifications for the email notification functionality on page 3-61
• send e-mail latest mgmt-lan on page 5-204
• List of messages when sending an email message fails on page 3-66

List of messages when sending an email message fails


The following table lists and describes messages when sending an email
message fails.

Table 3-29 List of messages when sending an email message fails

Code Message Description

E0410 <Address %> Sending e- The destination address is incorrect,


mail notification was or a user corresponding to the
canceled. Address is not set. specified address does not exist.
Make sure that your email destination
is properly configured.

E0411 <Address %> Sending e- An error occurred during


mail notification was communication with the SMTP server.
canceled. A communication Make sure that your LAN connection is
error occurred. correct.

E0412 <Address %> Sending e- The module failed to connect to the


mail notification was SMTP server.

3-66 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
Code Message Description
canceled. Connecting to Review the following setting items to
SMTP server failed. confirm that all of them are correct:
• General notification by email
settings
• State of the SMTP server
• LAN connections
E0413 <Address %> Sending e- The module failed to look up the IP
mail notification was address of the SMTP server for the
canceled. Failed to resolve host name of that server.
host. Review the following setting items to
confirm that all of them are correct:
• Email notification settings
• Network settings (DNS)
• LAN connections

E0414 <Address %> Sending e- The IP address for the SMTP server
mail notification was has an invalid format.
canceled. Configuration is Make sure that your email notification
invalid. settings are correct.

E0415 <Address %> Sending e- The SMTP server does not support the
mail notification was SMTP authentication method specified
canceled. SMTP server does in the email notification settings.
not support requested Make sure that the authentication
authentication type. method in the email notification
settings is correct.

E0416 <Address %> Sending e- The user name or password for SMTP
mail notification was authentication is incorrect.
canceled. SMTP Make sure that the authentication
authentication failed. user and password in the email
notification settings are correct.

E0417 <Address %> Sending e- The SMTP server does not support the
mail notification was encryption method specified in the
canceled. SMTP server does email notification settings.
not support SSL/TLS. Make sure that the encryption method
in the email notification settings is
correct.

E0418 <Address %> Sending e- An unexpected error occurred.


mail notification was Contact your reseller or maintenance
canceled. Program failed. personnel.

E0419 <Address %> Sending e- The destination address is incorrect,


mail notification was or a user corresponding to the
canceled. E-mail address is specified address does not exist.
invalid. Make sure that your email destination
is properly configured.

Efficient Management of Servers Using the Management Module 3-67


Hitachi Compute Blade 2500 Series Management Module User Guide
Syslog transfer
This section describes Syslog transfer function for management modules and
BMC.

Overview
Management modules and BMC can transfer events of user operation,
hereinafter referred to as Audit event, to a syslog server. You can integrate
and manage Audit events in management modules and BMC using the syslog
server.

Note:
• Audit events at user operation with stopping a management module, such
as shutdown, restart, replacement, may not be sent depending on the
timing.
• When you shut down, restart, or switch a management module
immediately after performing some operation, or when the management
module fails immediately after your operation, Audit events may not be
sent depending on the timing.
• Only Audit events can be sent to the syslog server. Events as alert trigger
for HCSM are not sent to the syslog server.
• Audit events in a management module are sent to the syslog server from
the management module. Audit events in BMC are sent to the syslog
server from BMC. You need to configure settings for transfer to the syslog
server in management modules and in BMC respectively.

Audit events to transfer


The audit events that are transferred are the events that are collected as
operation logs or audit logs. See List of operation log and audit log messages
on page 4-13 for details.

Log format
The flowing format is used for operation logs to be transferred to the syslog
server:
[date] [IP address for SVP or BMC] [mm or bmc]: auditevent,[log
message]

The following format is used for audit logs transferred to the syslog server.
[priority]1 [date] [IP address for SVP or BMC] [mm or bmc] -
[message ID] - [log message]

An operation log or an audit log is in [log message]. See List of operation log
and audit log messages on page 4-13, Operation log format on page 4-8,
Format of the audit log on page 4-11 for the format and messages.

3-68 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
"user" is displayed as facility for logs transferred to the syslog server. For
severity, "notice" is displayed as the result in the operation log or an audit log
when an operation fails, and "info" is displayed when the operation result is
other than failure.

Using Syslog transfer


The following flowchart shows the procedure for using Syslog transfer.

(1) Installing the Syslog server


Install a syslog server to transfer Audit events.

(2) Setting Syslog transfer to management modules and BMC


Configure the following settings for the management module and BMC.
• Enabling/disabling Syslog transfer
Enable or disable Syslog transfer. To send Audit events with Syslog
transfer, enable it.
• Sending or not sending Audit events (only for management modules)
Enable or disable Syslog transfer to send Audit events. To send them
using Syslog transfer, enable it.
• Syslog server for destination
Set an IP address or host name for the syslog server for destination. Use
FQDN to set the host name.
• Port number
Set the port number of the destination syslog server.
• Transfer protocol
Set the protocols to be used for syslog transfer. Syslog transfer by using
UDP or TCP is not encrypted.
Syslog transfer using TLS is encrypted.
• TLS Version
Set the TLS version to be used for syslog transfer. You can set the TLS
version if you have specified TLS as the transfer protocol.
• Format
Set the format of the logs to be transferred to the syslog server. You can
select the operation or audit log format.

Note:
• Only one syslog server can be specified as destination.
• Syslog transfer does not support SSL 3.0.

(3) Sending Syslog transfer test message


When you log into the management module CLI console or Web console,
"Logged in to the System Console" or "Logged in to the System Web Console"
is sent. For BMC, "Logged in to the remote console" is sent when you log into

Efficient Management of Servers Using the Management Module 3-69


Hitachi Compute Blade 2500 Series Management Module User Guide
BMC. Check if the message is sent or not. When the message is sent, Syslog
transfer setting is correct.

Editing the Syslog transfer settings of the management module


You can edit the syslog transfer settings of management modules by using
the Web console.
To edit the Syslog transfer settings of the management module from
the Web console:
1. From the tree view in the Administration tab, select Syslog transfer.
2. Click the Edit button.
3. Set the necessary items and execute the processing.

Editing the Syslog transfer settings of BMC


To edit the Syslog transfer settings of BMC, use the Web console.
To edit the Syslog transfer settings of BMC from the Web console:
1. Select the Resources tab, and then from the tree view in Modules,
select the target server blade.
2. From the Edit button in the BMC tab, select the item to be edited.
3. Specify the necessary items, and execute the process.

3-70 Efficient Management of Servers Using the Management Module


Hitachi Compute Blade 2500 Series Management Module User Guide
4
Server Maintenance and Management
by Management Modules
This chapter explains how to maintain and manage a blade server by using
management modules.

□ Log data output by management modules and server blades

□ Updating management module firmware

□ Updating server blade firmware

□ Restoring settings by management modules

□ File management functionality

Server Maintenance and Management by Management Modules 4-1


Hitachi Compute Blade 2500 Series Management Module User Guide
Log data output by management modules and server blades
This section describes log data output by management modules and server
blades.

Logs viewable from management modules


The following table shows the logs viewable from management modules.

Table 4-1 Logs viewable from management modules

Item Description

System event log This records information, warnings, and failure events that
(SEL) occurred on the system unit.

Optional Physical Optional Physical WWN change history.


WWN change log

Optional Physical MAC Optional Physical MAC address change history.


address change log

MAR log MAR is the abbreviation of Maintenance Action Report. This log
records events that caused failure notifications.

Environment log Records the history of the intake and exhaust temperature data
for the system unit.

Dump log Saves the dump log for the system unit. This dump log contains
the settings of the system unit, logs, and internal data for failure
analysis.

Operation log and Records the operation history for management modules and
audit log BMC.

The following table shows consoles that can be used to check the logs for log
data from management modules.

Table 4-2 Checking logs

LCD touch
Operation Web console CLI console
console

Checking the system event Y Y --


log

Checking the Optional Y Y --


Physical WWN change log

Checking the Optional Y Y --


Physical MAC address
change log

Checking the MAR log Y Y --

Checking the environment Y Y --


log

Checking the dump log Y Y Y

4-2 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
LCD touch
Operation Web console CLI console
console

Checking the operation log Y -- --

Checking the audit log Y -- --

Related topics
• Checking the system event log on page 4-3
• Checking the Optional Physical WWN change log on page 4-3
• Checking the Optional Physical MAC address change log on page 4-4
• Checking the MAR log on page 4-4
• Checking the environment log on page 4-5
• Dump log on page 4-5
• Checking the dump log on page 4-7
• Checking the operation log and the audit log on page 4-13

Checking the system event log


To check the system event log, use the Web console or the CLI console.
To check the system event log from the Web console:
1. From the tree view in the Alerts tab, select System Event Log.
The system event log is displayed.

Tip: Only the latest 100 system event log entries are displayed by default. To
display all system event log entries, click the Show all SELs button.

To check the system event log from the CLI console:


1. Execute the show log sel command.

Related topics
• show log sel on page 5-251

Checking the Optional Physical WWN change log


To check the Optional Physical WWN change log, use the Web console or the
CLI console.
To check the Optional Physical WWN change log from the Web
console:
1. From the tree view in the Alerts tab, select Optional Physical WWN
Change Log.
The Optional Physical WWN change log is displayed.

Server Maintenance and Management by Management Modules 4-3


Hitachi Compute Blade 2500 Series Management Module User Guide
To check the Optional Physical WWN change log from the CLI
console:
1. Execute the show log wwn-edit command.

Related topics
• show log wwn-edit on page 5-254

Checking the Optional Physical MAC address change log


To check the Optional Physical MAC address change log, use the Web console
or the CLI console.
To check the Optional Physical MAC address change log from the Web
console:
1. From the tree view in the Alerts tab, select Optional Physical MAC
Change Log.
The Optional Physical MAC address change log is displayed.
To check the Optional Physical MAC address change log from the CLI
console:
1. Execute the show log mac-edit command.

Related topics
• show log mac-edit on page 5-246

Checking the MAR log


To check the MAR log, use the Web console or the CLI console.
To check the MAR log from the Web console:
1. From the tree view in the Alerts tab, select MAR Log.
A list of MAR log entries is displayed.
2. Select a log entry whose details you want to check, and then click the
Show details button.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.
In such a case, download the file again.

4-4 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Tip: Click the Download button to save the MAR log to a file.

To check the MAR log from the CLI console:


1. Execute the show log mar-log command.

Related topics
• show log mar-log on page 5-247

Checking the environment log


To check the environment log, use the Web console or the CLI console.
To check the environment log from the Web console:
1. From the tree view in the Alerts tab, select Environment Log.
Intake and exhaust temperatures for management modules, server
blades, power supply modules, and switch modules are displayed.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.
In such a case, download the file again.

Tip: Click the Download button to save the environment log to a file.

To check the environment log from the CLI console:


1. Execute the show log environment command.

Related topics
• show log environment on page 5-243

Dump log
The dump log contains system unit settings, logs, and internal data for failure
analysis. When a failure occurs on the system unit, collect the dump log and
then contact your reseller or maintenance personnel.
The dump log is a file that is archived with tar. When you decompress the
dump log, the following files are generated.
• raslogA-YYYYMMDD-hhmmss.tar.gz

Server Maintenance and Management by Management Modules 4-5


Hitachi Compute Blade 2500 Series Management Module User Guide
• svpsts_jp-YYYYMMDD-hhmmss.gz
• svpsts_en-YYYYMMDD-hhmmss.gz
• hvmdumpA-YYYYMMDD-hhmmss.tar
• trc-YYYYMMDD-hhmmss.tar.gz
• marlog-YYYYMMDD-hhmmss.tar
• oplog_svp-YYYYMMDD-hhmmss.dmp
In addition to the above files, files might be generated for failure analysis.
The following information is recorded in svpsts_jp-YYYYMMDD-hhmmss.gz
and svpsts_en-YYYYMMDD-hhmmss.gz.
• The system event log at the time the dump log was collected
• The device configuration at the time the dump log was collected
• Important user-settings at the time the dump log was collected
These files are compressed with gzip. Therefore, decompress the files and
view them with a text editor. "svpsts_jp" indicates a Japanese file.
"svpsts_en" indicates an English file.

Note: Press the save button within two minutes after the dialog for selecting
a location for a downloaded file to be saved opens on the browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the message
"Internet Explorer cannot download [IP address] - [File name]. Server
returned invalid or unrecognized response." is returned or the file is
incorrectly saved as a smaller size.
In such a case, download the file again.

Tip:
• Use general-purpose decompression software to decompress tar-archive
and gzip files.
• The log files other than svpsts_jp-YYYYMMDD-hhmmss.gz and svpsts_en-
YYYYMMDD-hhmmss.gz are for failure analysis. The internal format is not
public.
• hvmdumpA-YYYYMMDD-hhmmss.tar is the dump log that LPAR manager
saves to a management module. LPAR manager automatically saves the
LPAR manager dump log when a failure occurs. In addition, you can
manually save the LPAR manager dump log for failure analysis. To
manually save the LPAR manager dump log, you need to use the LPAR
manager screen or an HvmSh command.
• You can collect the LP dump log for a specified server blade. You can
download the LP dump log as a file but it is not saved in the management
module.

Related topics
• Checking the dump log on page 4-7

4-6 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Checking the dump log
To check the dump log, use the Web console, the CLI console, or the LCD
touch console.

Note: If you use the Web console, disable the pop-up blocker in the Internet
option settings of your Web browser.
If the pop-up blocker is enabled, collection of the dump log fails.
To check the dump log from the Web console:
1. Click the Dump Log button of General Tasks, in the lower-left side of the
window.
The dump log is saved to the PC connected to the Web console. To specify
the location where the log is to be saved, follow the instructions displayed
in the window.
To check the dump log from the CLI console:
1. Execute the export log failure command.

To check the dump log from the LCD touch console:


1. In the home window, touch the Output dump log button.
2. The dump log window appears.

Related topics
• export log failure on page 5-241

Notes on using the operation log and the audit log


The operation log and the audit log record the operation history of the system
unit. Note the following when you use the operation log and the audit log:
• If you replace a management module while management modules are
used in a redundant configuration, the collected operation log entries and
audit log entries for management modules are deleted.
• If you replace a server blade, the collected operation log entries and audit
log entries for the server blade are deleted.
• Operation log messages and audit log messages might differ depending
on the firmware version.

Related topics
• Specifications of the operation log and the audit log on page 4-8
• Operation log format on page 4-8
• Checking the operation log and the audit log on page 4-13
• List of operation log and audit log messages on page 4-13

Server Maintenance and Management by Management Modules 4-7


Hitachi Compute Blade 2500 Series Management Module User Guide
Specifications of the operation log and the audit log
The following table shows the specifications of the operation log and the audit
log.

Table 4-3 Specifications of the operation log and the audit log

Server blade operation log Management module operation log


Category
and audit log and audit log

Recording Operation events are classified by operation event categories, and their
method operation results are recorded as "Success", "Failure", or "Occurrence".

Recorded The following operations are recorded: operations to start and stop the
operation system unit, authentication operations, operations to change settings, and
maintenance operations.

Number of 2,048 for each server blade For operations that can be performed
recorded log (maximum) with server blade privileges: 2,048 for
entries If the number of recorded log each server blade (maximum)
entries exceeds the maximum For other operations: 2,048 (maximum)
on each server blade, the If the number of recorded log entries
oldest log entry is overwritten. exceeds the maximum on each server
blade, the oldest log entry is overwritten.

Download Downloaded by using a management module console.


method Format: Variable length CSV file (delimiter: comma (,))
Character encoding: Shift-JIS

Number of 2,048 (maximum) When a server blade is selected: 2,048


downloaded (maximum)
log entries When a server chassis is selected: 18,432
(maximum) (2,048 log entries per server
blade x 8 server blades + 2,048 log
entries for other than server blades)

Operation log format


The following table shows the format of the operation log. The format of the
management module operation log is the same as that of the server blade
operation module.

Table 4-4 Operation log format

Item Size Description Remarks

Sequence 1 to 10 This records a number used to identify the --


number order of log entries.
(seq_no) A value in the range from 1 to
9999999999 is assigned. After
9999999999, the sequence number loops
back to 1.

Date and 29 This records the date, time, and time zone --
time when the operation was logged.
(date)

4-8 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Size Description Remarks
YYYY-MM-DDThh:mi:ss.SSS±h2:m2:
YYYY; year, MM; month, DD; date, T; fixed
(delimiter), hh; hour, mi; minute, ss;
second, SSS; millisecond (fixed to 000)
h2: time zone offset hour, m2: time zone
offset minute
The time zone offset is recorded as an
offset from UTC.

Server 1 • Server blade operation log: If a user logs in


blade This records the number of the server with server blade
number blade where the operation event privileges, only
(par_no) occurred. operation log
entries for server
• Management module operation log: blades that the user
For operations that can be performed can operate are
with server blade privileges: This provided.
records the server blade number in
the range from 1 to 15. For other
operations: This records 16.

Equipment 7 to 17 This records the name of the equipment --


name that was used for the operation.
(compid) • Server blade operation log:
Server Blade
• Management module operation log:
Management Module

Location 15 to 40 This records the host name of the --


(place) equipment that was used for the
operation.
• Server blade operation log:
IP address for the server blade
• Management module operation log:
IP address for the management
module

Operation 7 to 19 This records the name of the category to See Table 4-5 Table
category which the operation was classified. of operation event
(categ) categories on page
4-10.

Operation 7 to 10 This records the operation result (Success, See Table 4-6 Table
result Failure, or Occurrence). of operation event
(result) results on page
4-10.

Operator 10 to 14 This records the operator type. --


type • User operation: User Operation
(subjtype) • System process operation: System
Process

Operator 1 to 32 This records the operator. --


(subject) • User operation: Login account name

Server Maintenance and Management by Management Modules 4-9


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Size Description Remarks
• System process operation: System
process identifier

Session ID 3 to 32 This records information to identify the "N/A" is displayed


(sessionid) operator when two or more operators log for an operation
in with the same login account. that was not
(hexadecimal) performed by a
user logged in with
the same login
account as another
user (for example,
for an operation by
system processing).

Message ID 4 This records the message ID. --


(msgid) (hexadecimal)

Message 1 to 240 Operation messages are recorded. --


(message)

Note:
• Each item is recorded in variable length format.
• Items are divided by a comma (,), and each line is terminated by a
linefeed code (CR or LF).
• The message is enclosed in double quotation marks (").
• The character encoding of the recorded message is Shift-JIS.

Table 4-5 Table of operation event categories

Recorded item Description

StartStop Indicates a Start/Stop operation event.

Authentication Indicates an Identification or Authentication


operation event.

ConfigurationAccess Indicates a Configuration Access operation


event.

Maintenance Indicates a Maintenance operation event.

Table 4-6 Table of operation event results

Recorded item Description

Success Indicates that the operation event finished successfully.

Failure Indicates that the operation event failed.

Occurrence Indicates that an operation event (an event that is not


classified as Success or Failure) occurred.

4-10 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Format of the audit log
The following table shows the format of the audit log.

Table 4-7 Format of the audit log

Item Description Remarks

Common identifier Fixed to CELFSS --


(CommonSpecID)

Common 2 --
specifications
revision number
(Rev)

Sequence number This records a number used to This corresponds to the seq_no
(SequenceNum) identify the order of log entries. item of the operation log.
A value in the range from 1 to
9999999999 is assigned. After
9999999999, the sequence
number loops back to 1.

Message ID This records the message ID. This corresponds to the msgid
(MessageID) item of the operation log.

Date and time This records the date, time, and This corresponds to the date
(DateTime) time zone when the operation item of the operation log.
was logged.
YYYY-MM-DDThh:mi:ss.S
±h2:m2: YYYY; year, MM;
month, DD; date, T; fixed
(delimiter), hh; hour, mi;
minute, ss; second, S;
millisecond (fixed to 0)
h2: time zone offset hour, m2:
time zone offset minute
The time zone offset is recorded
as an offset from UTC.

Detection entity This records the name of the --


(EntityInfo) equipment that was used for the
operation.
Management module audit log:
ManagementModule

Detection location This records the host name of This corresponds to the place
(Location) the equipment that was used for item of the operation log.
the operation.
Management module audit log:
IP address for management
modules

Operation type This records the name of the See Table 4-5 Table of operation
(Category) category to which the operation event categories on page 4-10.
was classified. This corresponds to the categ
item of the operation log.

Server Maintenance and Management by Management Modules 4-11


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description Remarks

Operation result This records the operation result --


(Result) (Success, Failed, or
Occurrence).

Operator This records the operator. This corresponds to the subject


(SubjectID) • User operation: Login item of the operation log.
account name
• System process operation:
System process identifier

Hardware This records the serial number of --


identification the equipment that was used for
information the operation.
(HardwareID)

Location Management module audit log: If a user logs in with server


information For operations that can be blade privileges, only operation
(LocInfo) performed with server blade log entries for server blades that
privileges: This records the the user can operate are
server blade number in the provided. This corresponds to
range from 1 to 15. the par_no item of the operation
log.
For other operations: This
records 16.

Location This information is not recorded --


identification in this equipment.
information (LocID)

FQDN (FQDN) This information is not recorded --


in this equipment.

Redundancy This information is not recorded --


identification in this equipment.
information (HaID)

Agent information This information is not recorded --


(AgentInfo) in this equipment.

Request source This information is not recorded --


host in this equipment.
(ReqSourceHost)

Request source port This information is not recorded --


number in this equipment.
(ReqSourcePort)

Request destination This information is not recorded --


host (ReqDestHost) in this equipment.

Request destination This information is not recorded --


port number in this equipment.
(ReqDestPort)

Batch operation This information is not recorded --


identifier (BatchID) in this equipment.

Log type This information is not recorded --


information in this equipment.
(LogCateg)

4-12 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Item Description Remarks

Application This information is not recorded --


identification in this equipment.
information (AppID)

Reserved area This information is not recorded --


(Reserv) in this equipment.

Message (Message) Operation messages are This corresponds to the message


recorded. item of the operation log.

Note:
• Each item is recorded in variable length format.
• Items are divided by a comma (,), and each line is terminated by a
linefeed code (CR or LF).
• The message is enclosed in double quotation marks (").

Checking the operation log and the audit log


To check the operation log and the audit log, use the Web console.
To check the operation log and the audit log from the Web console:
1. From the tree view in the Alerts tab, select Operation Log.
2. Select the log to be checked. If you select the operation log, click the
Download operation log button. If you select the audit log, click the
Download audit log.

Note: Press the save button within two minutes after the dialog for
selecting a location for a downloaded file to be saved opens on the
browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the
message "Internet Explorer cannot download [IP address] - [File name].
Server returned invalid or unrecognized response." is returned or the file
is incorrectly saved as a smaller size.
In such a case, download the file again.

Related topics
• List of operation log and audit log messages on page 4-13

List of operation log and audit log messages


The following tables show the operation log and audit log messages for
management modules and server blades.

Server Maintenance and Management by Management Modules 4-13


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 4-8 List of management module operation log messages

Operation
ID event Collection trigger Message
categories

0802 Start/Stop Request to operate a On Management module N,


management module requested operation.
Channel: xxx Method: xxx

0803 Failure of a request to On Management module N, failed


operate a management to requested operation.
module Channel: xxx Method: xxx

0804 Request to shut down On Server chassis, requested


the server chassis shutdown.
Channel: xxx

0805 Failure of a request to On Server chassis, failed to


shut down the server requested shutdown.
chassis Channel: xxx

0806 Request to operate a On Switch module N, requested


switch module operation.
Channel: xxx Method: xxx

0807 Failure of a request to On Switch module N, failed to


operate a switch module requested operation.
Channel: xxx Method: xxx

0808 Request to operate a On Server blade N, requested


server blade operation.
Channel: xxx Method: xxx

0809 Failure of a request to On Server blade N, failed to


operate a server blade requested operation.
Channel: xxx Method: xxx

1800 Identification or Successful login to the Logged in to the System Console.


Authentication system console Username: xxx Session ID: xxx
Source IP address: xxx

1801 Failed login to the Failed to login to the System


system console Console.
Username: xxx Source IP address:
xxx Cause: xxx

1802 Logout from the system Logged out from the System
console Console.
Username: xxx Session ID: xxx
Source IP address: xxx Cause: xxx

1803 Successful login to the Logged in to the System Web


Web console Console.
Username: xxx Session ID: xxx
Source IP address: xxx

4-14 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories

1804 Failed login to the Web Failed to login to the System Web
console Console.
Username: xxx Source IP address:
xxx Cause: xxx

1805 Logout from the Web Logged out from the System Web
console Console.
Username: xxx Session ID: xxx
Source IP address: xxx Cause: xxx

1806 Failed login to the Failed to login to the Console.


system console or the Cause: xxx
Web console

1810 Successful On Server blade N, disconnect


disconnection from the from the BMC Session.
BMC session Channel: xxx Category: xxx Value:
xxx

1811 Failed disconnection On Server blade N, failed to


from the BMC session disconnect the BMC Session.
Channel: xxx Category: xxx Value:
xxx

1812 Login after the Permitted to log in to the Console


password expiration (for changing password).
Username:xxx Cause:xxx

3803 Configuration Change to the settings On Power supply module, setting is


Access of the power supply changed.
module Channel: xxx Category: xxx Detail:
xxx Value: xxx

3804 Change to the settings On Power supply module N, setting


of the power supply is changed.
module Channel: xxx Category: xxx Detail:
xxx Value: xxx

3806 Change to the settings Management LAN setting is


of the management LAN changed.
of a management Channel: xxx Category: xxx Value:
module xxx

3808 Change to the settings On Switch module N, LAN setting


of the switch module's is changed.
management LAN Channel: xxx Category: xxx Value:
xxx

3809 Change to the settings On Switch module N, LAN setting


of the switch module's is changed. (Apply Management
management LAN module setting)
Channel: xxx Category: xxx Value:
xxx

Server Maintenance and Management by Management Modules 4-15


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories

380E Change to the VLAN VLAN setting is changed. (Move


settings port)
Channel: xxx Target: xxx
Partition: xxx Switch module: xxx
VLAN ID: xxx

380F Change to the VLAN VLAN setting is changed. (Move


settings port)
Channel: xxx Target: xxx Server
blade: xxx Switch module: xxx
VLAN ID: xxx

3810 Change to the VLAN VLAN setting is changed. (Delete


settings port)
Channel: xxx VLAN ID: xxx

3821 Request to restore the Reset management module to


management module factory default setting.
settings to the initial Channel: xxx Category: xxx
settings (the settings at
shipping time)

382B Change to the email E-mail setting is changed.


settings Channel: xxx Category: xxx Detail:
xxx Value: xxx

382E Change to the SNMP SNMP setting is changed.


settings Channel: xxx Category: xxx Detail:
xxx Value: xxx

382F Removal of SNMP SNMP setting is removed


settings Channel: xxx Category: xxx
Number: xxx

3830 Change to the security xxx service setting is changed.


settings Channel: xxx Category: xxx Value:
xxx

3832 Creation of an SSH host SSH host key pair is created.


key pair Channel: xxx

3834 Saving an SSH host key SSH host key pair is backed up.
pair Channel: xxx File: xxx

3836 Restoration of an SSH SSH host key pair is restored.


host key pair Channel: xxx File: xxx

3838 Creation of an SSL SSL private key and self signed


private key and self certificate are created.
signed certificate Channel: xxx Category: xxx Detail:
xxx

383A Creation of a CSR SSL private key and certificated


signing request (CSR) are created.

4-16 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories
Channel: xxx Category: xxx Detail:
xxx

383C Importing a certificate Certificate is imported.


Channel: xxx File: xxx Certificate
file type: xxx

383E Copying a certificate A certificate was copied.


Channel: xxx File: xxx Certificate
file type: xxx

3840 Backup of a certificate Certificate is backed up.


Channel: xxx File: xxx

3842 Restoration of a Certificate is restored.


certificate Channel: xxx File: xxx

3844 Saving of the Management module setting is


management module backed up.
settings Channel: xxx File: xxx

3845 Restoration of a Management module setting is


management module restored.
settings Channel: xxx File: xxx

384B Change to the LDAP LDAP setting is changed.


settings Channel: xxx Category: xxx Detail:
xxx Value: xxx

384C Change to the LDAP LDAP setting is changed.


settings Channel: xxx Category: xxx Detail:
xxx

3850 Change to the power Power saving setting is changed.


saving settings Channel: xxx Category: xxx Detail:
xxx Value: xxx

3853 Change to the power On Server blade N, Power saving


saving settings setting is changed.
Channel: xxx Category: xxx Detail:
xxx Value: xxx

385A Change to the date and On Management module, date and


time time is changed.
Channel: xxx Category: xxx Detail:
xxx Value: xxx

3861 Change to the server On Server blade N, N+M cold


blade information standby partition information
settings, based on N+M setting is changed.
cold standby Channel: xxx

3862 Change to the server On Server blade N, setting is


blade settings changed.

Server Maintenance and Management by Management Modules 4-17


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories
Channel: xxx Category: xxx Detail:
xxx Value: xxx

3863 Change to the server On Server blade N, setting is


blade settings changed.
Channel: xxx Category: xxx

3864 Change to the settings On Server blade N, LAN setting is


of the server blade's changed.
management LAN Channel: xxx Category: xxx Value:
xxx

3867 Change to the Optional Additional WWN is changed.


Physical WWN settings Channel: xxx Server blade: xxx

3868 Change to the Optional Additional WWN is changed.


Physical WWN settings Channel: xxx Server blade: xxx
Card: xxx Slot: xxx

3869 Change to the Optional Additional WWN is initialized.


Physical WWN settings Channel: xxx Server blade: xxx

386A Change to the Optional Additional WWN is initialized.


Physical WWN settings Channel: xxx Server blade: xxx
Card: xxx Slot: xxx

386B Change to the Optional Additional MAC is changed.


Physical MAC settings Channel: xxx Server blade: xxx

386C Change to the Optional Additional MAC is changed.


Physical MAC settings Channel: xxx Server blade: xxx
Card: xxx Slot: xxx

386D Change to the Optional Additional MAC is initialized.


Physical MAC settings Channel: xxx Server blade: xxx

386E Change to the Optional Additional MAC is initialized.


Physical MAC settings Channel: xxx Server blade: xxx
Card: xxx Slot: xxx

3870 Restoration of server Reset Server blade N to factory


blade settings to the default setting.
initial settings (the Channel: xxx Category: xxx
settings at shipping
time)

3873 Backup of the settings On Server blade N, setting (xxx) is


of a server blade backed up.
Channel: xxx Bkup time: xxx File:
xxx

3874 Restoration of the On Server blade N, setting (xxx) is


settings of a server restored.
blade Channel: xxx Bkup time: xxx

4-18 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories

3875 Removal of the backup On Server blade N, setting (xxx) is


data of a server blade removed.
Channel: xxx

3876 Backup of the settings On Server blade N, setting (xxx) is


of a server blade (HBA) backed up.
Channel: xxx Category: xxx Slot:
xxx Bkup time: xxx File: xxx

3877 Restoration of the On Server blade N, setting (xxx) is


settings of a server restored.
blade (HBA) Channel: xxx Category: xxx Slot:
xxx Bkup time: xxx

3878 Removal of the backup On Server blade N, setting (xxx) is


data of a server blade removed.
(HBA) Channel: xxx Category: xxx Slot:
xxx

3879 Backup of the settings On Server blade N, setting (xxx) is


of a server blade backed up.
Channel: xxx File: xxx

387A Restoration of the On Server blade N, setting (xxx) is


settings of a server restored.
blade Channel: xxx File: xxx

387D Backup of the settings On Server blade N, setting (xxx) is


of a server blade backed up.
Channel: xxx Category: xxx Slot:
xxx

387E Restoration of the On Server blade N, setting (xxx) is


settings of a server restored.
blade Channel: xxx Category: xxx Slot:
xxx

387F Removal of the settings On Server blade N, setting (xxx) is


of a server blade removed.
Channel: xxx Category: xxx Slot:
xxx

3880 Creation of an account An account is created.


Channel: xxx Account: xxx Status:
xxx Role: xxx

3881 Change to an account An account is changed.


Channel: xxx Account: xxx Status:
xxx Role: xxx

3882 Removal of an account An account is removed.


Channel: xxx Account: xxx

3885 Removal of a role A role is removed.

Server Maintenance and Management by Management Modules 4-19


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories
Channel: xxx Role: xxx

3886 Change to a role A role is changed.


Channel:xxx Role:xxx
Server1-15:xxx Switch1-2:xxx
Net:xxx Chassis:xxx Account:xxx

3887 Creation of a role A role is created.


Channel:xxx Role:xxx
Server1-15:xxx Switch1-2:xxx
Net:xxx Chassis:xxx Account:xxx

3890 Creation of an email E-mail setting is created.


setting (an email Channel: xxx
address)

3891 Change to an email E-mail setting is changed.


setting (an email Channel: xxx
address)

3892 Removal of an email E-mail setting is removed.


setting (an email Channel: xxx
address)

3898 Change to the settings On Switch module N, setting is


of a switch module changed.
Channel: xxx Category: xxx Detail:
xxx Value: xxx

3899 Change to the settings On Switch module N, setting is


of a switch module changed.
Channel: xxx Port#: xxx Category:
xxx Detail: xxx Value: xxx

389A Change to the password LCD touch console password is


for the LCD touch changed.
console Channel: xxx

389B Initialization of the LCD touch console password is


password for the LCD initialized.
touch console Channel: xxx

389D Clearing the host Host information on the server


information for a server blade n has been cleared.
blade Channel: xxx

3900 Change to the settings HCSM setting is changed.


of the HCSM linkage Means: xxx; Type: xxx; Changes:
functionality by using an xxx; After changed: xxx
HCSM command

3901 Addition of HCSM server HCSM management server setting


settings by using an is added.
HCSM command Means: xxx; IP address: xxx; Alert
port number: xxx; Alert level: xxx;

4-20 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories
Retry interval: xxx; Retry
duration: xxx

3902 Change to the HCSM HCSM management server setting


server settings by using is changed.
an HCSM command Means: xxx; IP address: xxx;
Type: xxx; Before changed: xxx;
After changed: xxx

3903 Change to the HCSM HCSM management server setting


server settings by using is changed.
an HCSM command Means: xxx; IP address: xxx;
Changes: xxx; After changed: xxx

3904 Deletion of HCSM server HCSM management server setting


settings by using an is deleted.
HCSM command Means: xxx; IP address: xxx

3905 Disconnection of the HCSM management server is


HCSM server session by disconnected.
using an HCSM Means: xxx; IP address: xxx
command

3907 Send to the HCSM test On Server BladeN, HCSM send test
alert alert(N+M cold standby)
Channel:xxx Category:xxx

3910 Change to the security On Management module, security


strength of a configuration is changed.
management module Channel: xxx Detail: xxx Value:
xxx

3911 Change to the security On Server Blade N, security


strength of a server configuration is changed.
blade Channel: xxx Detail: xxx Value:
xxx

3912 Change to the TLS/SSL On Management module, TLS/SSL


version of the version is changed.
management module Channel: xxx Detail: xxx Value:
xxx

3913 Change to the syslog Syslog transfer setting is changed.


transfer settings Channel:xxx Detail:xxx Value:xxx

3916 Change to the server On Server bladeN, setteing is


blade settings changed.
Channel:xxx Category:xxx
Value:xxx

391A Change to the login Login banner setting is changed.


banner settings Channel:xxx Value:xxx

391B Creation of the login Login banner message is


banner message registered.

Server Maintenance and Management by Management Modules 4-21


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories
Channel:xxx

391C Change to the login Login banner message is changed.


banner message Channel:xxx

391D Removal of the login Login banner message is deleted.


banner message Channel:xxx

391E Change to the Web Web console (mgmt-lan) setting is


console (mgmt-lan) changed.
settings Channel:xxx Value:xxx

391F Change to the Web Web console (mnt-lan) setting is


console (mnt-lan) changed. Channel:xxx Value:xxx
settings

3926 Change to the settings Management LAN setting is


of the management LAN changed.
of a management Channel: xxx Category: xxx Value:
module xxx

3927 Change to the settings On Server blade N, LAN setting is


of the server blade's changed.
management LAN Channel: xxx Category: xxx Value:
xxx

3928 Change to the security xxx service setting is changed.


settings Channel: xxx Category: xxx Value:
xxx

3929 Change to the settings On Switch module N, LAN setting


of the switch module's is changed.
management LAN Channel: xxx Category: xxx Value:
xxx

392B Change to the password Password policy setting is changed.


policy settings Channel:xxx Category:xxx
Detail:xxx Value:xxx

392C Change to the BMC user BMC user account setting is


account settings changed.
Channel:xxx ServerBlade:xxx
Account:xxx Use:xxx Name:xxx

392D Change to the IPMI user IPMI user account setting is


account settings changed.
Channel:xxx ServerBlade:xxx
Account:xxx Use:xxx Name:xxx
Role:xxx

392E Change to the USB setting is changed.


USB(Management Channel:xxx Category:xxx
module) settings Detail:xxx Value:xxx

4-22 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories

3930 Change to the server On Server bladeN, setting is


blade settings changed.
Channel:xxx Category:xxx
Assign:xxx Redundancy:xxx

3931 Change to the RADIUS Setting of RADIUS was changed.


settings Channel:xxx Category:xxx
Detail:xxx Value:xxx

3932 Change to the RADIUS Setting of RADIUS serverN was


server settings changed.
Channel:xxx Category:xxx
Detail:xxx Value:xxx

393A Change to the SVP-LP Management module - LP


management communication setting was
communication settings changed.
Channel:xxx Category:xxx
Detail:xxx Value:xxx

393B Change to the server On Server blade N, setting is


blade settings changed.
Channel: xxx Category: xxx Detail:
xxx Value: xxx

393C Change to the server On Server blade N, setting is


blade settings changed.
Channel: xxx Category: xxx Detail:
xxx Value: xxx

393D Change to the server On Server blade N, setting is


blade settings changed.
Channel: xxx Category: xxx Detail:
xxx Value: xxx

8800 Maintenance Change to the operation On Server chassis, changed into


mode of the server maintenance mode from normal
chassis from normal mode.
mode to maintenance Channel: xxx
mode

8801 Change to the operation On Server chassis, changed into


mode of the server normal mode from maintenance
chassis from mode.
maintenance mode to Channel: xxx
normal mode

8802 Change to the operation On Server blade N, changed into


mode of a server blade maintenance mode from normal
from normal mode to mode.
maintenance mode Channel: xxx

8803 Change to the operation On Server blade N, changed into


mode of a server blade normal mode from maintenance
mode.

Server Maintenance and Management by Management Modules 4-23


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories
from maintenance mode Channel: xxx
to normal mode

8804 Change to the operation On Switch module N, changed into


mode of a switch maintenance mode from normal
module from normal mode.
mode to maintenance Channel: xxx
mode

8805 Change to the operation On Switch module N, changed into


mode of a switch normal mode from maintenance
module from mode.
maintenance mode to Channel: xxx
normal mode

8806 Change to the operation On Management module N,


mode of a management changed into maintenance mode
module from normal from normal mode.
mode to maintenance Channel: xxx
mode

8807 Change to the operation On Management module N,


mode of a management changed into normal mode from
module from maintenance mode.
maintenance mode to Channel: xxx
normal mode

8810 Request to update the On Server blade N, requested


firmware of a server server blade firmware update.
blade Channel: xxx

8811 Request to update LPAR Requested Hitachi Virtualization


manager firmware Manager firmware update.
Channel: xxx Bank#: xxx1

8812 Request to remove Requested Hitachi Virtualization


LPAR manager firmware Manager firmware removed.
Channel: xxx Bank#: xxx1

8813 Request to update the On Switch module N, requested


firmware of a switch firmware update.
module Channel: xxx

8814 Request to update the On Management module,


firmware of a requested firmware update.
management module Channel: xxx

8815 Request to update the On Management module,


firmware of a requested firmware update (Copy
management module and Update).

8816 Request to update LPAR Requested Logical Partitioning


manager firmware Manager firmware update.
Channel:xxx Bank#:xxx1

4-24 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories

8817 Request to remove Requested Logical Partitioning


LPAR manager firmware Manager firmware removed.
Channel:xxx Bank#:xxx1

8819 Mounting an ISO image On server blade, mounted ISO


file to a server blade image file.
Channel: xxx File: xxx

881A Unmounting an ISO On server blade, unmounted ISO


image file from a server image file.
blade Channel: xxx File: xxx

881C Change to the sync EFI On Server bladexxx, Sync EFI time
time settings setting is changed.
Channel:xxx Value:xxx

Note:
1. A bank number indicates an area number. For details, see the Hitachi Compute
Blade 2500 Series Logical partitioning manager User Guide.

Table 4-9 List of server blade operation log and audit log messages

Operation
ID event Collection trigger Message
categories

1001 Identification Successful login to the Logged in to the remote console.


or remote console Username: xxx Source IP
Authentication address: xxx User authentication
method: xxx

1002 Logout from the Logged out from the remote


remote console console.
Username: xxx Source IP
address: xxx Cause: xxx

1003 Failed login to the Failed to login to the remote


remote console console.
Username: xxx Source IP
address: xxx Cause: xxx

1008 Successful login to the Logged in to the server blade web


server blade Web console.
console Username: xxx Source IP
address: xxx User authentication
method: xxx

1009 Logout from the server Logged out from the server blade
blade Web console Web console.
Username: xxx Source IP
address: xxx Cause: xxx

Server Maintenance and Management by Management Modules 4-25


Hitachi Compute Blade 2500 Series Management Module User Guide
Operation
ID event Collection trigger Message
categories

100A Failed login to the Failed to login to the server blade


server blade Web web console.
console Username: xxx Source IP
address: xxx Cause: xxx

Updating management module firmware


This section explains how to update management module firmware.

Firmware that can be updated on management modules


Firmware is software that is embedded in a device and provides basic
hardware control. Multiple firmware programs are embedded in the CB 2500.
You can update the following firmware from a management module. For
details on how to update server blade firmware, see the next section. For
details on how to update LPAR manager firmware, see the Hitachi Compute
Blade 2500 Series Logical partitioning manager User Guide.

Table 4-10 Firmware type

Name Description

Management module firmware Firmware that runs on management modules.

Dictionary Data file that is saved in management modules


and converts log messages. 1

Server blade firmware Firmware that runs on server blades. This


firmware consists of BMC and UEFI.

LPAR manager firmware Firmware that is used for running LPAR


manager on server blades.

Note:
1. This is not exactly firmware but is updated from management modules like
firmware. For convenience of explanation, we list this data file in this table.

Related topics
• Updating server blade firmware on page 4-34

Points to check before updating management module firmware


You can update the management module firmware and dictionary at once
from a management module console or HCSM.

4-26 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 4-11 List of firmware programs to be updated

Required The management The firmware can


Firmware to be
time module be updated while
updated
(minutes) is rebooted? the system runs?

Management module 25 to 30 Yes1 Yes2


firmware

Dictionary 5 to 10 No Yes

Notes:
1. When management module firmware is updated, the management module
automatically reboots. If the management module is in a redundant configuration,
the active management module starts to reboot and the standby management
module becomes active. When the management module completely reboots, the
other management module starts to reboot. Then, the originally active management
module becomes active.
2. Before you update management module firmware during system operation, make
sure that you read through the limitations below.

The following limitations exist when you update management module


firmware:
If the management module is in a redundant configuration, you can update
management module firmware while server blades are running. However, the
limitations below exist. Make sure that you check the contents of the
limitations and understand risks before you update management module
firmware.
• Do not update the management module firmware or dictionary from a
different console or HCSM while management module firmware or a
dictionary is being updated. If you do so, the management module
firmware or dictionary might fail to be updated.
If the update fails, retry the update operation.
• While management module firmware is being upgraded, management
modules temporarily stop. Do not perform the operations below on the
system unit. These operations might fail due to a temporary network
disconnection. After the management module firmware is completely
upgraded, retry these operations.
Operations prohibited during an upgrade
• N+M cold standby manual failover or restoration (If this operation
failed, you might need to re-configure the N+M environment for
restoration.)
• Login to a management module console
• HCSM operation
• Establishing or changing the HA monitor cluster configuration
• Use of the remote console (if the management server blade is
installed on the server chassis, you cannot open the HCSM console
window.)

Server Maintenance and Management by Management Modules 4-27


Hitachi Compute Blade 2500 Series Management Module User Guide
• LPAR manager operation
• Update of the server blade firmware
• Update of the LPAR manager firmware
¢ N+M cold standby manual failover or restoration (If this operation
failed, you might need to re-configure the N+M environment for
restoration.)
¢ Login to a management module console
¢ HCSM operation
¢ Establishing or changing the HA monitor cluster configuration
¢ Use of the remote console (if the management server blade is
installed on the server chassis, you cannot open the HCSM console
window.)
¢ LPAR manager operation
¢ Update of the server blade firmware
¢ Update of the LPAR manager firmware
• If you upgrade management module firmware while a server blade or the
server chassis is being powered on or off, the upgrade might not finish
normally. When you update management module firmware, do not power
on or off server blades and the server chassis.
• If you do so, any of the alert messages below might be reported while the
management module firmware is being upgraded. (These alert messages
are just for checking during work procedures and do not affect the system
behavior.)

Alert type Content

Warning Redundancy for FD78h module is lost. (Error part:


Management LAN Port0)

Redundancy for FD78h module is lost. (Error part:


Management LAN Port1)

Redundancy for FD78h module is lost. (Error part:


Management LAN Port)

Information Redundancy for the module is recovered. (Error part:


Management LAN Port0)

Redundancy for the module is recovered. (Error part:


Management LAN Port1)

Redundancy for the module is recovered. (Error part:


Management LAN Port)

Other information alerts might be reported but do not affect the system
behavior.
• If you perform this operation while using LPAR manager, an LPAR
manager screen indicating "SVP Access Failure" might appear due to a
temporary network disconnection. This does not cause a problem because
abnormalities in communications are automatically restored.

4-28 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
• If the HA monitor (including the cluster manager) is installed, depending
on the timing, a reset path failure message (KAMN624-E or KAMN399-E)
might be output by the HA monitor while management module firmware
is being upgraded, and the HA monitor will stop monitoring.
Upgrade management module firmware in an environment where the
system status can be monitored. These messages might be output due to
a factor other than the upgrade of management module firmware (for
example, a hardware error). Make sure that you confirm that the path
status is in normal (status is OK) by executing the monrp command, and
perform the operation to restart monitoring of the reset path.
(If status is not OK, a failure due to a factor other than the upgrade of
management module firmware is assumed and automatic failover might
be impossible. In such a case, ask maintenance personnel to take
appropriate actions.
• If the SNMP polling functionality performs alive-status monitoring, a
communication failure might occur due to a temporary network
disconnection. This does not cause a problem because abnormalities in
communications are automatically restored.
• Upgrade the management module firmware during a period in which any
impact on production operations is small. Delays in responses to the
management module might occur during the upgrade.
• If a management module is switched while management module firmware
is being upgraded, the upgrade fails. Remove the cause of the failure, and
retry.
• If you use HCSM to update management module firmware, click Refresh
after the update finishes, and then check the version of the management
module firmware.
• If you need to downgrade the management module firmware, contact
your reseller or maintenance personnel.

General procedure for updating the management module firmware


and dictionary
The following figure shows the general procedure for updating the
management module firmware and dictionary and how to update them.

Server Maintenance and Management by Management Modules 4-29


Hitachi Compute Blade 2500 Series Management Module User Guide
The following table shows update operations on a management module and
availability of each console.

Table 4-12 Update of the management module firmware and dictionary

Operation Web console CLI console LCD touch console

Checking the current Y Y Y


versions of the
management module
firmware and dictionary,
and the system states
(active and standby) of
management modules

Updating the management Y Y Y


module firmware and
dictionary

Confirming that the Y Y Y


management module
firmware and dictionary
were updated

Note:
• For details on how to use HCSM to update the management module
firmware and dictionary, see the HCSM manual.

Related topics
• Obtaining the management module firmware and dictionary on page
4-31
• Checking the current versions of the management module firmware and
dictionary, and the system states (active and standby) of management
modules on page 4-31
• Updating the management module firmware and dictionary on page 4-32
• Confirming that the management module firmware and dictionary were
updated on page 4-34

4-30 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Obtaining the management module firmware and dictionary
Contact your reseller for details on where to download the latest
management module firmware and dictionary.
You need to download the following files: After you download the files,
decompress them.

Firmware to be
File to be downloaded Result of decompression
updated

Management CB 2500 management module svpfw.AXXXX-X-XXXX.update


module firmware firmware readme.txt

Dictionary CB 2500 dictionary dict.AXXXX.update readme.txt

Note:
• Do not change the names of downloaded files.
If you change the name of a downloaded file, management modules
cannot recognize the file as a firmware file.
• Files for other system units (e.g. CB 2000) cannot be applied.

Checking the current versions of the management module firmware


and dictionary, and the system states (active and standby) of
management modules
Check that the versions of the obtained management module firmware and
dictionary are later than the current versions. If you update the management
module firmware, connections will be lost because the management module
reboots. After the management module firmware and dictionary are updated,
check the system states (active and standby) of the management modules. If
the system states are the same before and after the update, connections with
management modules have been established normally.
To use the Web console to check the current versions of the
management module firmware and dictionary, and the system states
(active and standby) of management modules:
1. Click the Resources tab. From the Modules tree view, select
Management Modules.
Before you update management module firmware, check the system
states of management modules 1 and 2.
2. Click the number of the management module whose system state is
displayed as active in the management module information.
The current versions of the management module firmware and dictionary
are displayed in the [Firmware version] and [Dictionary version] fields.
To use the CLI console to check the current versions of the
management module firmware and dictionary, and the system states
(active and standby) of management modules:
1. Execute the show mgmt-module firmware command.

Server Maintenance and Management by Management Modules 4-31


Hitachi Compute Blade 2500 Series Management Module User Guide
To use the LCD touch console to check the current versions of the
management module firmware and dictionary, and the system states
(active and standby) of management modules:
1. From the Maintenance menu, touch the Management Module (MM)
button.
The management module window appears.

Related topics
• show mgmt-module firmware on page 5-97

Updating the management module firmware and dictionary


Use the Web console, the CLI console, or the LCD touch console to update
the management module firmware and dictionary.

Operations to complete in advance


Store the obtained update file onto the hard disk of the system console. If
you need to update multiple firmware programs, store all files used for
updating the firmware programs.
To use the Web console to update the management module firmware
and dictionary
1. Click the Resources tab. From the Modules tree view, select
Management Modules.
2. From the Action pull-down menu, select Update Firmware.
3. In the Update Firmware dialog box, select the check boxes for the
firmware to be updated. Click the Browse button and select the update
file.
4. In the Update Firmware dialog box, click the Confirm button.
5. Check that an update file is displayed for each firmware to be updated,
and then click the OK button.
First, upload of the firmware files starts. When the upload progress bar
reaches the right end, the firmware update starts and the update
progress bar appears. On the update progress bar, a message for the
operation in progress is displayed. Wait for about 10 minutes or more
until the update finishes.
6. When the update progress bar reaches the right end, the update finishes.
Click the Close button.
The displayed window differs depending on whether you specify an
update of the management module firmware.
If you specify an update of the management module firmware, the
following window appears.

4-32 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: Before the above message appears, the active management
module might reboot due to completion of the update. In such a case, the
message "Request timed out" is displayed on the Web console window. If
this message appeared, wait for about 10 minutes and check the
firmware versions. If you can confirm that the firmware programs have
been updated to intended versions, there is no problem. If you cannot
connect to the Web console, contact your reseller or maintenance
personnel.
If you do not specify the update of management module firmware, the
following window appears.

7. If you specify an update of the management module firmware and


connections are lost because of the reboot of the active management
module, close the browser.
If you perform a firmware update without specifying the update file for
management module firmware, you do not need to close the browser.
To use the CLI console to update the management module firmware
and dictionary
1. Execute the update mgmt-module firmware command.

To use the LCD touch console to check the current versions of the
management module firmware and dictionary, and the system states
(active and standby) of management modules:
1. From the Maintenance menu, touch the Management Module (MM)
button.
The management module window appears.
2. From the pull-down menu, select Firmware update.
3. The F/W update window appears.

Note: You can update the management module firmware and dictionary at
one time or separately.

Server Maintenance and Management by Management Modules 4-33


Hitachi Compute Blade 2500 Series Management Module User Guide
If the management module is in a redundant configuration, the firmware
update is performed for both systems even if you select either of the
management modules on the management module window.

Related topics
• update mgmt-module firmware on page 5-114

Confirming that the management module firmware and dictionary


were updated
To confirm that the management module firmware and dictionary were
updated correctly, use the Web console, the CLI console, or the LCD touch
console.
To use the Web console to confirm that the management module
firmware and dictionary were updated:
1. Click the Resources tab. From the Modules tree view, select
Management Modules.
If you can confirm in the management module information that the
system states of the management modules after the update are the same
as those before the update, the update of the management module
firmware is complete. Check the system states of management modules 1
and 2.
2. Check that intended versions are displayed and then click the
management module whose system state is displayed as active in the
management module information.
The current versions of management module firmware and dictionary are
displayed in [Firmware version] and [Dictionary version] fields. Confirm
that versions after the update are displayed.
To use the CLI console to confirm that the management module
firmware and dictionary were updated:
1. Execute the show mgmt-module firmware command.

To use the LCD touch console to confirm that the management


module firmware and dictionary were updated:
1. From the Maintenance menu, touch the Management Module (MM)
button.
The management module window appears.

Related topics
• show mgmt-module firmware on page 5-97

Updating server blade firmware


This section explains how to update server blade firmware.

4-34 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Points to check before updating server blade firmware
Server blade firmware can be updated from a management module console
or HCSM.
Server blade firmware consists of BMC and UEFI. If you update server blade
firmware, both BMC and UEFI are updated at the same time.
You can also use the Web console and the CLI console to update firmware for
multiple server blades of the same type in the same server chassis at once.
Update of server blade firmware starts in background after the operation to
update the firmware on a management module console. The operation on a
management module console is complete for about 5 to 10 minutes. Then,
update of server blade firmware is processed in background for about 10 to
30 minutes.

Limitations on updating server blade firmware


The following limitations exist when you update server blade firmware:
• Power off server blades before you update server blade firmware.
• Update of server blade firmware over multiple types of server blades is
not supported.
Firmware for a single type of server blades can be updated at the same
time.
On the Web console, you can check the server blade type in Product
name of the Hardware tab for the server blade.
To update firmware for multiple types of server blades, do for one type of
server blades. After you confirm that the update is complete, do for
another type of server blades.
• Because BMC restarts while server blade firmware is being updated,
communication with management modules might be lost. In that case,
the following warning SEL is collected but there is no problem.
Server blade: SVP-BMC communication error (IPMI over LAN)
• While server blade firmware is being updated, do not remove and operate
server blades.
• If you update server blade firmware while server blades are running, the
update of the UEFI in the firmware of each server blade is applied when
the server blades are powered on the next time. In that case, the time
required to power on the server blades takes longer than usual.
• If you attempt to power on a server blade while server blade firmware is
being updated, the server blade is powered on after the update
processing is complete.
• Do not power off a server blade during the first Post after background
processing. If you do so, depending on timing, the server blade might not
start normally.
• If a failover of management modules occurs while server blade firmware
is being updated from a management module console, the update fails.
Remove the failure factor and retry.

Server Maintenance and Management by Management Modules 4-35


Hitachi Compute Blade 2500 Series Management Module User Guide
• In an SMP configuration, if you select a primary server blade, the
firmware for all server blades constituting the SMP is updated.
• For non-primary server blades, if you update the firmware in an SMP
configuration and then release the SMP configuration, the time required to
start up the non-primary server blade is greater than usual.

Related topics
• General procedure for updating server blade firmware on page 4-36

General procedure for updating server blade firmware


The following figure shows the general procedure for updating server blade
firmware and how to update it.

The following table shows update operations on a management module and


availability of each console.

Table 4-13 Updating server blade firmware

Operation Web console CLI console LCD touch console

Checking the current Y Y Y


version of server blade
firmware

Updating server blade Y Y Y


firmware

Confirming that server Y Y Y


blade firmware was updated

Note:
• For details on how to use HCSM to update management module firmware
and dictionary, see the HCSM manual.

4-36 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• Obtaining server blade firmware on page 4-37
• Checking the current version of server blade firmware on page 4-37
• Updating server blade firmware on page 4-38
• Confirming that server blade firmware was updated on page 4-39

Obtaining server blade firmware


Contact your reseller for details on where to download the latest
management module firmware and dictionary.
After the firmware file is downloaded, decompress the files.

Note:
• If you use the firmware file for a different model to update the firmware,
the update fails. In such a case, use an appropriate file and retry to
update the firmware.
• Do not change the file name. If you change the name of a downloaded
file, management modules cannot recognize the file as a firmware file.
• Files for other system units (e.g. CB 2000) cannot be applied.

Checking the current version of server blade firmware


Before you update server blade firmware, check that the version of the
obtained update server blade firmware is later than the current version.
To check the current version of server blade firmware from the Web
console:
1. Click the Resources tab. From the Systems tree view, select Firmware.
Total version of the Server Blade tab displays the current firmware
version for each server blade. For all server blades whose firmware is to
be updated, check that the version of the update server blade firmware is
later than the current version.
To check the current version of server blade firmware from the Web
console:
1. Execute the show blade firmware command.

To check the current version of server blade firmware from the LCD
touch console:
1. From the Maintenance menu, touch the Server Blade (SB) button.
2. In the Server blade window, select a target server blade.
3. From the pull-down menu, select Detail information.
4. The Detail information window appears.

Server Maintenance and Management by Management Modules 4-37


Hitachi Compute Blade 2500 Series Management Module User Guide
Related topics
• show blade firmware on page 5-59

Updating server blade firmware


Use the Web console, the CLI console, or the LCD touch console to update
server blade firmware.
To update server blade firmware from the Web console:
1. Click the Resources tab. From the Systems tree view, select Firmware.
2. Select the server blades whose firmware is to be updated. With the server
blades selected, click the Update Server Blade firmware button.
3. Click the Browse button in the Update Firmware dialog box and select
the update file.
Follow the OS procedure to open the file.
4. In the Update Firmware dialog box, click the Confirm button.
5. Confirm that the selected update file is displayed for Server Blade
Firmware and all target server blades are displayed for Server Blade,
and then click the OK button.
6. The firmware upload starts. When the upload progress bar reaches the
right end, firmware update starts and the update progress bar appears.
The update progress bar indicates the update progress for all target
server blades. Wait for few minutes until the update finishes.
7. The firmware update result is displayed for each target server blade.
Confirm that the firmware for all target server blades has been
successfully updated, and then click the Close button.
8. Update processing starts in the background. Check the progress. In
Modules of the Resources panel, click All Modules.
9. In Modules of All Modules, click [Server Blades].
10. Wait for about 10 to 30 minutes until Status in Server Blades
Information changes from Normal (updating) to Normal for all target
server blades.

Note:
• Because the contents of the Status tab is not automatically updated,
you need to click the Refresh button periodically to update the
display.
• The SEL "Server blade: SVP-BMC communication error (IPMI over
LAN)" might be collected. If this SEL was collected, "Warning
(updating)" might be displayed for Status in Server Blades
information. Even in this case, if Status changes to "Normal", the
update finished.
The update finished if Status changes to Normal.

To update server blade firmware from the CLI console:


1. Execute the update blade firmware bulk command.

4-38 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
To update server blade firmware from the LCD touch console:
1. From the Maintenance menu, touch the Server Blade (SB) button.
The Server blade window appears.
2. From the pull-down menu, select Firmware update.
3. The Updating firmware window appears.

Note: Server blade firmware must be stored in the USB device that is
connected to a USB connection port on the front panel of the server chassis.

Note: If the user directory for management modules does not have sufficient
capacity, an attempt to update the server blade firmware might fail. If the
update of the server blade firmware fails, use the file management
functionality to check files in the user directory, delete unnecessary files, and
then retry the update operation.

Related topics
• update blade firmware bulk on page 5-86
• Deleting a file from a management module on page 4-44

Confirming that server blade firmware was updated


To confirm that management module firmware and dictionary were updated
correctly, use the Web console, the CLI console, or the LCD touch console.
To confirm that server blade firmware was updated, from the Web
console:
1. Click the Resources tab. From the Systems tree view, select Firmware.
2. Total version of the Server Blade tab displays the current firmware
version for each server blade.
For all server blades whose firmware was to be updated, check that the
updated version is displayed.
To confirm that server blade firmware was updated, from the CLI
console:
1. Execute the show blade firmware command.

To confirm that server blade firmware was updated, from the LCD
touch console:
1. From the Maintenance menu, touch the Server Blade (SB) button.
2. In the Server blade window, select a target server blade.
3. From the pull-down menu, select Detail information.
4. The Detail information window appears.

Related topics
• show blade firmware on page 5-59

Server Maintenance and Management by Management Modules 4-39


Hitachi Compute Blade 2500 Series Management Module User Guide
Restoring settings by management modules
This section explains how to restore settings by management modules.

Information that can be restored by management modules


The following table shows settings that can be restored by management
modules and availability of each console.

Table 4-14 Information that can be saved or restored by management


modules

Operation Web console CLI console LCD touch console

Saving management Y -- --
module settings

Restoring Y -- --
management module
settings

Saving LPAR Y -- --
manager settings

Restoring LPAR Y -- --
manager settings

For details on how to restore LPAR manager settings, see the Hitachi
Compute Blade 2500 Series Logical partitioning manager User Guide.

Related topics
• Saving management module settings on page 4-40
• Restoring management module settings on page 4-41

Saving management module settings


Use the Web console to save management module settings.
It takes few minutes to save the settings.

Note: If you change the settings from a console or change server blade's
power status during processing to save the settings, saving the settings
might fail. Save management module settings under the state in which these
changes do not occur.
To save management module settings from the Web console
1. Click the Resources tab. From the Modules tree view, select
Management Modules.
2. From the Action pull-down menu, select Backup Settings.
The backup of the management module configuration information is
downloaded.

4-40 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: Press the save button within two minutes after the dialog for selecting
a location for a downloaded file to be saved opens on the browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the message
"Internet Explorer cannot download [IP address] - [File name]. Server
returned invalid or unrecognized response." is returned or the file is
incorrectly saved as a smaller size.
In such a case, download the file again.

Restoring management module settings


Use the Web console to restore management module settings.
It takes few minutes to restore management module settings. When the
restoration is complete, management modules reboot.

Note:
• Because management modules reboot after their settings are restored,
management modules stops. Do not restore management module settings
while server blades are running.
• If you restore management module settings, LPAR manager settings are
also restored to the settings that were saved when management module
settings were backed up.
• If the current version of management module firmware is later than the
version of the management module firmware used when management
module settings were collected in a backup file and you use the backup
file to restore management module settings, functionality that was not
supported when the backup file was generated are set to their default
values.
To restore management module settings from the Web console:
1. Click the Resources tab. From the Modules tree view, select
Management Modules.
2. From the Action pull-down menu, select Restore settings.
The backup is used to restore management module settings.

File management functionality


This section describes the file management functionality.

About the file management functionality


This functionality allows you to use the Web console to view a list of the files
(firmware manual, attachments, etc.) that are stored in the user directory for
management modules. You can perform the following operations for files:
• Uploading a file to a management module
• Downloading a file from a management module

Server Maintenance and Management by Management Modules 4-41


Hitachi Compute Blade 2500 Series Management Module User Guide
• Copying a file from the active management module to the standby
management module

Note: Note that the operation to copy files from the active management
module to the standby management module is only for maintenance work. Do
not perform this operation.
The following items can be displayed by using the Web console:
• A maximum of 1,024 files are displayed.
• A maximum of 1,024 characters are displayed for a directory path. A
maximum of 256 characters are displayed for a file name. Directory paths
and file names that exceed the maximum number of characters are not
displayed.

Related topics
• Structure of the user directory for management modules on page 4-42
• Uploading a file to a management module on page 4-43
• Downloading a file from a management module on page 4-43
• Deleting a file from a management module on page 4-44

Structure of the user directory for management modules


The structure of the user directory for management modules is as follows:
/iusb
/attached
/fw
/iso
/manual

At shipping time, attachments and manuals are stored in the following


directories.
Attachments: /iusb/attached

Manuals: /iusb/manual

Note: Files stored in the directories below are used for maintenance work.
Note that the attachments and manuals are excluded.
Do not perform any operations (e.g., deletion) on the documents.
• /iusb/attached
• /iusb/fw
• /iusb/iso
• /iusb/manual

Related topics
• About the file management functionality on page 4-41

4-42 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
• Uploading a file to a management module on page 4-43
• Downloading a file from a management module on page 4-43
• Deleting a file from a management module on page 4-44

Uploading a file to a management module


To upload a file to a management module, use the Web console.
To upload a file by using the Web console:
1. From the Systems tree view in the Resources tab, click File
Management.
2. Click the Upload file button.
3. In the File upload dialog box, select the directory to which the file is to
be uploaded from the pull-down menu. Click the Browse button and
select the file to be uploaded.
4. In the File upload dialog box, click the Confirm button.

Tip:
• A maximum of 256 directories are displayed as upload destination
directories.
• The uploaded file is saved in both the active and standby management
modules.

Related topics
• About the file management functionality on page 4-41

Downloading a file from a management module


To download a file from a management module, use the Web console.
To download a file by using the Web console:
1. From the Systems tree view in the Resources tab, click File
Management.
2. Click the file to be downloaded. With the file selected, click the
Download file button.
The file is saved to the PC that is connected to the Web console. To
specify the location where the file is to be saved, follow the instructions
displayed in the window.

Tip: You can download manuals from the Web console menu.

To download a manual from the Web console menu:


1. In the Web console menu, select Help and User's guide, and then click
the user's guide that you want to read.

Server Maintenance and Management by Management Modules 4-43


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: Press the save button within two minutes after the dialog for selecting
a location for a downloaded file to be saved opens on the browser.
If Internet Explorer is used and you press the button after two or more
minutes pass, the file is not saved as the correct size. Instead, the message
"Internet Explorer cannot download [IP address] - [File name]. Server
returned invalid or unrecognized response." is returned or the file is
incorrectly saved as a smaller size.
In such a case, download the file again.

Related topics
• About the file management functionality on page 4-41

Deleting a file from a management module


To delete a file from a management module, use the Web console.
To delete a file by using the Web console:
1. From the Systems tree view in the Resources tab, click File
Management.
2. Click the file to be deleted. With the file selected, click the Delete file
button to delete the file.

Tip: If a file that has the same name as the file to be deleted exists in the
standby management module, delete the file from the standby management
module.

Note: Files stored in the directories below are used for maintenance work.
Note that the attachments and manuals are excluded.
Do not perform any operations (e.g., deletion) on the documents.
• /iusb/attached
• /iusb/fw
• /iusb/iso
• /iusb/manual

Related topics
• About the file management functionality on page 4-41

4-44 Server Maintenance and Management by Management Modules


Hitachi Compute Blade 2500 Series Management Module User Guide
5
Commands That Can Be Executed From
the CLI Console
This chapter describes the commands that can be executed from the CLI
console and how to use them.

□ Command input format

□ Commands to manage the server chassis

□ Commands to manage server blades

□ Commands to manage management modules

□ Commands to manage management LAN modules

□ Commands to manage I/O adapters

□ Commands to manage switch modules

□ Commands for power supply management

□ Commands to manage fan modules

□ Commands for fan control module management

□ Commands to manage the LCD touch console

□ Commands for user management

□ Commands for time settings

Commands That Can Be Executed From the CLI Console 5-1


Hitachi Compute Blade 2500 Series Management Module User Guide
□ Commands for language setting

□ Commands for security settings

□ Commands for remote access management

□ Commands for SNMP management

□ Commands for LPAR manager management

□ Commands to collect log data

□ Commands to obtain backups

□ Commands for console management

□ Commands to identify parts

5-2 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Command input format
This section describes the input format of the commands that can be
executed from the CLI console.

Command conventions
The following table explains the command conventions that are used in this
manual.

Table 5-1 Command conventions

Convention Description
< > Indicates a parameter value that is specified by the user.
For details about the parameter values to be specified, see "Parameters"
for each command.
[ ] Indicates a parameter that can be omitted.
[ ¦ ] Indicates that you can either select one of the parameters from within
the square brackets or omit all parameters.
You cannot select multiple parameters from within the curly brackets. A
vertical bar (¦) is used to separate parameters.
Example: [-h¦-s]
In this example, you can select either -h or -s, or you can omit both
parameters.
{ ¦ } Indicates that you can select one of the parameters from within the curly
brackets. You cannot select multiple parameters from within the curly
brackets.
A vertical bar (¦) is used to separate parameters.
Example: {-a¦-f <file_name>}
In this example, you can select either -a or -f <file_name>.

notes on using commands


This section describes points that you should check before executing
commands, such as the formats for specifying numbers and full-width blades.

When you specify multiple numbers


To specify multiple numbers for a command, use either of the following two
formats:

Specification format Example

Use commas to separate the If you specify "0,2,3" for a command, command
numbers. processing is performed for 0, 2, and 3.

Specify a range of values by If you specify "1-7" for a command, command


using a hyphen. processing is performed for 1, 2, 3, 4, 5, 6, and 7.

Commands That Can Be Executed From the CLI Console 5-3


Hitachi Compute Blade 2500 Series Management Module User Guide
You cannot use both commas and hyphens when specifying multiple
numbers.
You can specify multiple numbers for the following parameters:
• Server blade number
• Switch module number
• Management module number
• Management LAN module number
• Fan module number
• Fan control module number
• I/O adapter number
• Address number to which notifications are to be sent by email
Server blade numbers refer to the server blade slot numbers on the server
chassis. For details about the slot configuration of the server chassis, see CB
2500 Startup Guide.

To specify all numbers:


For some commands, if you specify all instead of a number (such as a slot
number of a server blade), command processing is performed for all slot
numbers. Depending on the command, you might not be able to specify all
instead of a slot number. For details, see the explanation for each command.

Tip: A command cannot be executed for a slot in which no server blade is


installed. If such a slot exists and if you execute a command with all
specified, the following message appears even if the command ends
successfully for all other slots in which server blades are installed:
S0004 : Command succeeded partially.

To specify a full-width blade:


A full-width blade uses two server blade slots. To specify a full-width blade as
a server blade for a CLI command, specify the smaller of the two slot
numbers (the odd number) used for the full-width blade.

To set the character encoding


Set utf-8 for the character encoding.

Commands to manage the server chassis


This section describes the commands to confirm and change the server
chassis settings.

set chassis id
Changes the chassis ID.

5-4 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
set chassis id -c <cid> [-F]

Privilege
Chassis privilege

Parameters
-c <cid>
Chassis ID
You can use a maximum of 20 characters.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the chassis ID to SERVER1:
set chassis id -c SERVER1

set chassis maintenance-mode


Sets maintenance mode for the chassis when maintenance work for the
modules below is performed. Do not use this command for normal operation
because this command is used for maintenance work.
• Power supply modules
• Fan modules
• Fan control modules
If you set maintenance mode, the remaining time for maintenance mode is
set to 120 minutes.

Syntax
set chassis maintenance-mode -m <mnt_mode> [-F]

Privilege
Chassis privilege

Parameters
-m <mnt_mode>
Maintenance mode
¢ enable: Sets maintenance mode
¢ disable: Cancels maintenance mode
-F

Commands That Can Be Executed From the CLI Console 5-5


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set maintenance mode for the chassis:
$ set chassis maintenance-mode -m enable -F
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set chassis usb validity


Enables or disables a USB port of the active management module.

Syntax
set chassis usb validity -p <usb_port> -v <validity> [-F]

Privilege
Chassis privilege

Parameters
-p <usb_port>
USB port number
You can specify a value from 1 to 2.
-v <validity>
Setting to enable or disable a USB port
¢ enable: Enables the USB port.
¢ disable: Disables the USB port.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To disable USB port 1:
$ set chassis usb validity -p 1 -v disable
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

5-6 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set mac additional
Sets the Optional Physical MAC addresses of the mezzanine card, onboard
LAN, and I/O adapter that are installed in the server blade.

Syntax
set mac additional -b <blade_no> -c <card_type> -n <card_no> -co
<controller> -p <port> -m <mac> [-F]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-c <card_type>
Card type
¢ mezzanine: Mezzanine card
¢ iobd: I/O adapter
-n <card_no>
Card number
You can specify a value in the following range:
¢ For the mezzanine card: 1 to 4
¢ For the I/O adapter: 01A to 16B (Although no I/O board exists in
server blade 15, a value 15A, 15B, 16A, or 16B is also displayed.)
-co <controller>
Controller number of the card
-p <port>
Port number of the controller
-m <mac>
MAC address
¢ XX:XX:XX:XX:XX:XX: XX indicates a hexadecimal number.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the Optional Physical MAC addresses of mezzanine card 1, controller 0,
and port 1 for server blade 1:

Commands That Can Be Executed From the CLI Console 5-7


Hitachi Compute Blade 2500 Series Management Module User Guide
$ set mac additional -b 1 -c mezzanine -n 1 -co 0 -p 1 -m
12:34:56:78:9a:bc
Confirm? (y/[n]):y
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
To specify settings for onboard LAN 1, use mezzanine card 1 to specify the
following: -c mezzanine -n 1.

set wwn additional


Sets the Optional Physical WWN information of the mezzanine card, onboard
LAN, and I/O adapters that are installed in the server blade.

Syntax
set wwn additional -b <blade_no> -c <card_type> -n <card_no> -p
<port> -wp <wwpn> -wn <wwnn> [-F]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-c <card_type>
Card type
¢ mezzanine : Mezzanine card
¢ iobd: I/O adapter
-n <card_no>
Card number
You can specify a value in the following range:
¢ For the mezzanine card: 1 to 4
¢ For the I/O adapter: 01A to 16B (Although no I/O adapter exists in
server blade 15, a value 15A, 15B, 16A, or 16B is also displayed.)
-p <port>
Port number of the card
You can specify a value in the range from 0 to 3.
-wp <wwpn>
WWPN

5-8 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ XX:XX:XX:XX:XX:XX:XX:XX: XX indicates a hexadecimal number.
-wn <wwnn>
WWNN
¢ XX:XX:XX:XX:XX:XX:XX:XX : XX indicates a hexadecimal number
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the Optional Physical WWNs of mezzanine card 1 and port 1 for server
blade 1:
$ set wwn additional -b 1 -c mezzanine -n 1 -p 1 -wp
12:34:56:78:9a:bc:de:f0
-wn 0f:ed:cb:a9:87:65:43:21
Confirm? (y/[n]):y
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
To specify settings for onboard LAN 1, use mezzanine card 1 to specify the
following: -c mezzanine -n 1.

show chassis maintenance-mode


Displays whether maintenance work for the following modules is performed:
• Power supply modules
• Fan modules
• Fan control modules
The following information is displayed:
• Maintenance mode settings
• Remaining time for maintenance mode

Syntax
show chassis maintenance-mode

Privilege
Chassis privilege

Parameters
None

Commands That Can Be Executed From the CLI Console 5-9


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the maintenance mode of the chassis:
$ show chassis maintenance-mode
-- Chassis maintenance mode --
Maintenance mode : enable
Remaining time (min) : 115
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-2 Chassis maintenance mode

Displayed item Description


Maintenance mode Maintenance mode
• enable: Maintenance work is performed
• disable: Maintenance work is not performed
Remaining time (min) Remaining time for maintenance mode (minutes)
• 0 to 120: The remaining time for maintenance mode
(minutes)
• -----: Maintenance work is not performed.

show chassis setting


Displays the server chassis settings.

Syntax
show chassis setting

Privilege
Chassis privilege

Parameters
None

Execution example
To display the server chassis settings:
$ show chassis setting
-- chassis setting --
Chassis ID : CID
Maintenance classification : long
WDT time-out N+M switch : enable

5-10 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-- chassis FRU setting --
Part/model number : XXXXXXXX
Serial number : XXXXXXXX
Model ID : 00
Midplane ID : 00
First WWN : 0011223344556677
-- Weight --
Weight [kg] : 103.90
-- chassis sensor information --
-- Watt --
PresentAC Power : 247.00
PresentDC Power : 44.00
-- Temp --
Present Ambient : 25.00
-- Flow --
PresentAir Flow : 7.75
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-3 chassis setting

Displayed item Description


Chassis ID Chassis ID
A maximum of 20 characters are displayed.
Maintenance classification Long-life support service setting
• normal: Normal service
• long: Long-life support service
WDT time-out N+M switch WDT timeout N+M failover setting
• enable: A WDT timeout N+M failover is
performed.
• disable: A WDT timeout N+M failover is
not performed.

Table 5-4 chassis FRU setting

Displayed item Description


Part/model number Equipment model name
A maximum of 32 characters are displayed.
Serial number Serial number of the chassis
A maximum of 27 characters are displayed.
Model ID Chassis type
Midplane ID Midplane type
First WWN First Optional Physical WWN

Commands That Can Be Executed From the CLI Console 5-11


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
The smallest number among the 512
Optional Physical WWNs assigned to the
server chassis
The 11-byte information that consists of 3-
byte attribute information and 8-byte WWN
information is displayed in hexadecimal
format.

Table 5-5 Weight

Displayed item Description


Weight [kg] Weight (kg)
Includes the installed modules.

Table 5-6 chassis sensor information

Displayed item Description


Watt Lists the power sensor names and sensor
values for the server chassis.
Temp Lists the thermal sensor names and sensor
values for the server chassis.
Flow Lists the air flow sensor names and sensor
values for the server chassis.

show chassis status


Displays the server chassis status.

Syntax
show chassis status

Privilege
Chassis privilege

Parameters
None

Execution example
[To display the server chassis status:]
$ show chassis status
-- Chassis status --
Power : On
Fail : Normal

5-12 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Warning : Normal
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-7 Chassis status

Displayed item Description


Power Power supply status of the module
• Off : The module is powered off.
• On : The module is powered on.
If all server blades in the chassis are
powered off, Off is displayed.
Fail Failure status of the module
• Normal: The status of the module is
normal.
• FAIL: A failure occurred on the module.
Warning Warning status of the module
• Normal: The status of the module is
normal.
• WARNING : A warning was issued for
the module.

show chassis usb validity


Displays the status of each USB port (enabled or disabled) of the active
management module.

Syntax
show chassis usb validity

Privilege
Chassis privilege

Parameters
None

Execution example
To display the setting to enable or disable USB ports:
$ show chassis usb validity
-- Chassis USB validity --

Commands That Can Be Executed From the CLI Console 5-13


Hitachi Compute Blade 2500 Series Management Module User Guide
USB port : 1
Validity : enable
-- Chassis USB validity --
USB port : 2
Validity : enable
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
Table 5-8 Chassis USB validity

Displayed item Description


USB port USB port number
This is a value from 1 to 2.
Validity Setting to enable or disable a USB port
• enable: Enables the USB port.
• disable: Disables the USB port.

show mac additional


Displays the Optional Physical MAC addresses of the server blades.
• In an SMP configuration:
If you specify the primary server blade or non-primary server blades, the
MAC addresses of the specified server blades are displayed.
¢ Command specification format: show mac additional -b server-
blade-numbers
When specifying the -p parameter, use the -b parameter to specify the
primary server blade. The MAC addresses of all server blades that
constitute an SMP configuration are displayed.
¢ Command specification format: show mac additional -b primary-
server-blade-number -p
• In a non-SMP configuration:
The MAC addresses of the server blades specified for the -b parameter
are displayed.
Even if you specify the -p parameter, the displayed information does not
change.
The following items are displayed:
¢ Card type
¢ Card number
¢ Controller number of the card
¢ Port number of the controller
¢ Whether editing is performed

5-14 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ Whether a MAC address is duplicated
¢ MAC address

Syntax
show mac additional [-b <blade_no>] [-p]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
If you specify this parameter, the MAC addresses of all server blades that
constitute an SMP configuration are displayed. In an SMP configuration,
use the -b parameter to specify the primary server blade. In a non-SMP
configuration, the MAC addresses of the individual server blades are
displayed.

Execution example
To display the Optional Physical MAC addresses of server blade 1:
$ show mac additional -b 1
-- Additional MAC List --
Slot : 1
Card Num Controller Port M C MAC address
----------- --- ---------- ---- - - -----------------
mezzanine 1 0 0 * ! XX:XX:XX:XX:XX:XX
mezzanine 1 0 1 XX:XX:XX:XX:XX:XX
:
:
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-9 Additional MAC List

Displayed item Description


Slot Server blade number

Commands That Can Be Executed From the CLI Console 5-15


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
This is a value from 1 to 15.
Card Card type
• mezzanine : Mezzanine card
• IOBD: I/O adapter
Num Card number
This is a value in the following range:
• Mezzanine card : 1 to 4
• I/O adapter: 01A to 16A, or 01B to
16B (Although no I/O adapter exists in
server blade 15, a value 15A, 15B,
16A, or 16B is also displayed.)
Controller Controller number of the card
Port Port number of the controller
M Whether editing is performed
• Blank: No editing is performed.
• *: Editing is performed.
C Whether a MAC address is duplicated
• Blank: Not duplicated
• !: Duplicated
MAC address MAC address
• XX:XX:XX:XX:XX:XX : Optional
Physical MAC address

Rules
In an SMP configuration, if you specify -p and a non-primary server blade,
the command displays the following message instead of MAC addresses:
E0640 : <Blade %1$d> Command was canceled. Specified blade is not
the primary blade of SMP.

show mac current


Displays the MAC addresses used by the onboard LANs, mezzanine cards, or
I/O adapters that are installed in the server blades.
• In an SMP configuration:
If you specify the primary server blade or non-primary server blades, the
MAC addresses for the specified server blades are displayed.
¢ Command specification format:show mac current -b server-blade-
numbers
When specifying the -p parameter, use the -b parameter to specify the
primary server blade. The MAC addresses of all server blades that
constitute an SMP configuration are displayed.

5-16 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ Command specification format:show mac current -b primary-server-
blade-number -p
• In a non-SMP configuration:
The MAC addresses for the server blades that are specified in the -b
parameter are displayed.
Even if you specify the -p parameter, the displayed information does not
change.

Syntax
show mac current [-b <blade_no>] [-p]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
Displays the MAC addresses for all server blades constituting an SMP
configuration. In an SMP configuration, specify the primary server blades
in the -b parameter. In a non-SMP configuration, the MAC address for
each server blade is displayed.

Execution example
To display the MAC addresses used by the onboard LANs, mezzanine cards,
or I/O adapters that are installed in server blade 1:
$ show mac current -b 1
-- Current MAC List --
Slot : 1
MAC type : additional
Card Num Controller Port MAC address
----------- --- ---------- ---- ------------------
mezzanine 1 0 0 XX:XX:XX:XX:XX:XX
mezzanine 1 0 1 XX:XX:XX:XX:XX:XX
:
:
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-17


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-10 Current MAC List

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
MAC type MAC address type
• original: Default Physical MAC address
• additional: Optional Physical MAC address
Card Card type
• mezzanine: Mezzanine card
• Onboard LAN: Onboard LAN
• IOBD: I/O adapter
Num Card number
• Mezzanine card: 1 to 4
• Onboard LAN: 1
• I/O adapter: 01A to 14B
Controller Controller number of the card
Port Port number of the controller
MAC address MAC address
• XX:XX:XX:XX:XX:XX:XX:XX: Default Physical MAC address
or Optional Physical MAC address

show mac original


Displays the Default Physical MAC addresses used by the onboard LANs,
mezzanine cards, or I/O adapters that are installed in the server blades.
• In an SMP configuration:
If you specify the primary server blade or non-primary server blades, the
MAC addresses for the specified server blades are displayed.
¢ Command specification format:show mac original -b server-blade-
numbers
If you specify the -p parameter, use the -b parameter to specify the
primary server blade. The Default Physical MAC addresses for all server
blades constituting an SMP configuration are displayed.
¢ Command specification format:show mac original -b primary-
server-blade-number -p
• In a non-SMP configuration:
The MAC addresses for the server blades that are specified in the -b
parameter are displayed.
Even if you specify the -p parameter, the displayed information does not
change.

5-18 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
show mac original [-b <blade_no>] [-p]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
Displays the MAC addresses for all server blades constituting SMP. In an
SMP configuration, specify the primary server blades in the -b parameter.
In a non-SMP configuration, the MAC address for each server blade is
displayed.

Execution example
To display the Default Physical MAC addresses for the cards installed in server
blade 1:
$ show mac original -b 1
-- Original MAC List --
Slot : 1
Card Num Controller Port MAC address
----------- --- ---------- ---- ------------------
mezzanine 1 0 0 XX:XX:XX:XX:XX:XX
mezzanine 1 0 1 XX:XX:XX:XX:XX:XX
:
:
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-11 Default Physical MAC List

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Card Card type
• mezzanine: Mezzanine card
• Onboard LAN: Onboard LAN

Commands That Can Be Executed From the CLI Console 5-19


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• IOBD: I/O adapter
Num Card number
• Mezzanine card: 1 to 4
• Onboard LAN: 1
• I/O adapter: 01A to 14B
Controller Controller number of the card
Port Port number of the controller
MAC address MAC address
• XX:XX:XX:XX:XX:XX:XX:XX: Default Physical MAC
address

Rules
• In an SMP configuration, if you execute this command with -p and a non-
primary server blade specified, the following message appears and the
MAC address is not displayed:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.

show wwn additional


Displays the Optional Physical WWNs of the server blades.
• In an SMP configuration:
If you specify the primary server blade or non-primary server blades, the
WWNs of the specified server blades are displayed.
Command specification format: show wwn additional -b server-blade-
numbers
When specifying the -p parameter, use the -b parameter to specify the
primary server blade. The WWNs of all server blades that constitute an
SMP configuration are displayed in order.
Command specification format: show wwn additional -b primary-
server-blade-number -p
• In a non-SMP configuration:
The WWNs of the server blades specified for the -b parameter are
displayed.
Even if you specify the -p parameter, the displayed information does not
change.
The following items are displayed:
• Card type
• Card number
• Port number of the card
• Whether editing is performed

5-20 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
• Whether WWPN is duplicated
• WWPN
• Whether WWNN is duplicated
• WWNN

Syntax
show wwn additional [-b <blade_no>] [-p]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
If you specify this parameter, the WWNs of all server blades that
constitute an SMP configuration are displayed. In an SMP configuration,
use the -b parameter to specify the primary server blade. In a non-SMP
configuration, the WWNs of the individual server blades are displayed.

Execution example
To display the Optional Physical WWNs when mezzanine card 1 is installed in
server blade 1:

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-21


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-12 Additional WWN List

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Card Card type
• mezzanine: Mezzanine card
• IOBD: I/O adapter
Num Card number
This is a value in the following range:
• Mezzanine card: 1 to 4
• I/O adapter installed in the I/O adapter slot:
01A to 16B (Although no I/O adapter exists in
server blade 15, a value from 15A to 16B is
also displayed.)
Port Port number of the card
M Whether editing is performed
• Blank: No editing is performed.
• *: Editing is performed. (* is displayed if
WWPN, WWNN, or both are changed from the
initial values.)
C Whether WWPN is duplicated
• Blank: Not duplicated
• !: Duplicated
World wide port name WWPN
• XX:XX:XX:XX:XX:XX:XX:XX : Additional
WWN
C Whether WWNN is duplicated
• Blank: Not duplicated
• !: Duplicated
World wide node name WWNN
• XX:XX:XX:XX:XX:XX:XX:XX : Additional
WWN

Rules
• In an SMP configuration, if you specify -p and a non-primary server
blade, this command displays the following message and does not display
WWNs:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.
• If an onboard LAN is installed, the Optional Physical WWN for which a
mezzanine is displayed as the card type and 1 is displayed as the card
number is assigned to the onboard LAN.

5-22 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
show wwn current
Displays the WWNs used by the onboard LANs, mezzanine cards, or I/O
adapters that are installed in the server blades.
• In an SMP configuration:
If you specify the primary server blade or non-primary server blades, the
WWNs for the specified server blades are displayed.
¢ Command specification format:show wwn current -b server-blade-
numbers
If you specify the -p parameter, use the -b parameter to specify the
primary server blade. The WWNs for all server blades constituting an SMP
configuration are displayed.
¢ Command specification format:show wwn current -b primary-server-
blade-number -p
• In a non-SMP configuration:
The WWNs for the server blades that are specified in the -b parameter
are displayed.
Even if you specify the -p parameter, the displayed information does not
change.

Syntax
show wwn current [-b <blade_no>] [-p]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
Displays the WWNs for all server blades constituting an SMP
configuration. In an SMP configuration, specify the primary server blades
in the -b parameter. In a non-SMP configuration, the WWN for each
server blade is displayed.

Execution example
To display the WWNs used by the cards installed in server blade 1:

Commands That Can Be Executed From the CLI Console 5-23


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
Table 5-13 Current WWN List

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
WWN type WWN type
• original: Default Physical WWN
• additional: Optional Physical WWN

Card Card type


• mezzanine: Mezzanine card
• Onboard LAN: Onboard LAN
• IOBD: I/O adapter
Num Card number
• Mezzanine card: 1 to 4
• Onboard LAN: 1
• I/O adapter: 01A to 14B
Port Port number of the card
World wide port WWPN
name
• XX:XX:XX:XX:XX:XX:XX:XX: Default Physical WWN or
Optional Physical WWN
World wide node WWNN
name
• XX:XX:XX:XX:XX:XX:XX:XX: Default Physical WWN or
Optional Physical WWN

Rules
In an SMP configuration, if you execute this command with -p and a non-
primary server blade specified, the following message appears and the WWN
is not displayed:
E0640 : <Blade %1$d> Command was canceled. Specified blade is not
the primary blade of SMP.

5-24 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
show wwn original
Displays the Default Physical WWNs used by the onboard LANs, mezzanine
cards, or I/O adapters that are installed in the server blades.
• In an SMP configuration:
If you specify the primary server blade or non-primary server blades, the
WWNs for the specified server blades are displayed.
¢ Command specification format: show wwn original -b server-blade-
numbers
If you specify the -p parameter, use the -b parameter to specify the
primary server blade. The Default Physical WWNs for all server blades
constituting an SMP configuration are displayed.
¢ Command specification format: show wwn original -b primary-
server-blade-number -p
• In a non-SMP configuration:
The WWNs for the server blades that are specified in the -b parameter
are displayed.
Even if you specify the -p parameter, the displayed information does not
change.

Syntax
show wwn original [-b <blade_no>] [-p]

Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
Displays the WWNs for all server blades constituting an SMP
configuration. In an SMP configuration, specify the primary server blades
in the -b parameter. In a non-SMP configuration, the WWN for each
server blade is displayed.

Execution example
To display the Default Physical WWNs used by the cards installed in server
blade 1:

Commands That Can Be Executed From the CLI Console 5-25


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-14 Default Physical WWN List

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Card Card type
• mezzanine: Mezzanine card
• Onboard LAN: Onboard LAN
• IOBD: I/O adapter
Num Card number
• Mezzanine card: 1 to 4
• Onboard LAN: 1
• I/O adapter: 01A to 14B
Port Port number of the card
World wide port name WWPN
• XX:XX:XX:XX:XX:XX:XX:XX: Default Physical WWN
World wide node name WWNN
• XX:XX:XX:XX:XX:XX:XX:XX: Default Physical WWN

shutdown chassis
Shuts down the server chassis.

Syntax
shutdown chassis [-F]

Privilege
Chassis privilege

5-26 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To shut down the server chassis:
shutdown chassis

Rules
When execution of this command finishes, sessions with management
modules are closed.

Commands to manage server blades


This section describes the commands to confirm and change server blade
settings.

assign blade hvm firmware


Assigns the LPAR manager firmware to a server blade.
In an SMP configuration, if you specify a primary server blade, the LPAR
manager firmware that is to be used by all server blades constituting an SMP
configuration is assigned.
If you specify a non-primary server blade, the LPAR manager firmware is
assigned to the non-primary server blade but this does not affect the
behavior of the non-primary server blade. In this case, the following message
appears to notify you that the LPAR manager firmware was assigned but does
not affect the behavior of the server blade:
W0031 : <Blade X> Set data is not used. Specified blade is not the
primary blade of SMP. (X indicates the specified server blade
number.)

Syntax
assign blade hvm firmware <blade_no> {-b <hvm_bank_no>¦-d} [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.

Commands That Can Be Executed From the CLI Console 5-27


Hitachi Compute Blade 2500 Series Management Module User Guide
-b <hvm_bank_no>
Area number for the LPAR manager firmware that is to be assigned to the
server blade
You can specify a value from 0 to 3.
-d
Releases the LPAR manager firmware assignment for the server blade.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To assign the LPAR manager firmware in area 0 to server blade 1:
assign blade hvm firmware 1 -b 0

To release the LPAR manager firmware assignment for server blade 1:


assign blade hvm firmware 1 -d

bmc-reset blade
Resets the BMCs of the server blades.
The following are methods for resetting BMC:
• Powering on the sub-power supply of a server blade
• Restarting the BMC of a server blade
• Restarting the BMC of a server blade constituting an SMP configuration

Syntax
bmc-reset blade [<blade_no>] [-h¦-s¦-sb] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-h
Restarts the BMC by powering off and then powering on the sub-power
supply of a server blade.
If you omit both the -h and -s parameters, this command assumes that -
h is specified.

5-28 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Note: Executing this command while a server blade is powered on powers off
the server blade.

-s
Restarts the BMC. You can omit this parameter.
In an SMP configuration, specify the server blade numbers of primary
server blades. The BMCs of all server blades constituting the SMP
configuration are sequentially restarted.
-sb
Restarts the BMC of the specified server blade only.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To power on the sub-power supply of server blade 1:
bmc-reset blade 1

To restart the BMCs of all server blades:


bmc-reset blade all -s

Rules
• If the BMCs of all server blades constituting the SMP configuration are not
restarted at the same time, the initialization might fail. If you specify the
-sb parameter and only some of the server blades constituting the SMP
configuration, the following warning message about the possibility of an
initialization failure appears:
W0032 : <Blade X> A part of the blades of the SMP is specified.
Initialize may not complete. (X indicates the specified server
blade number.)
• In an SMP configuration, if you execute this command with the -h or -s
parameter and a non-primary server blade specified, the following
message appears, the sub-power supply is not powered on, and the BMC
is not restarted:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.

clear blade hvm


Initializes the LPAR manager settings for the server blades.
In an SMP configuration, if you specify a primary server blade, the settings of
the LPAR manager that is used by all server blades constituting the SMP
configuration are initialized. If you specify a non-primary server blade, the
LPAR manager settings for the server blade are initialized but they do not
affect the behavior of the non-primary server blade.

Commands That Can Be Executed From the CLI Console 5-29


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
clear blade hvm [<blade_no>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To initialize the LPAR manager settings for server blade 1:
clear blade hvm 1

delete blade os-info


Clears the host information (host name, OS) stored in the management
modules that is acquired from the server blade.
If the actual host information and the host information displayed on the
console differ, use this command to delete the host information.

Syntax
delete blade os-info <blade_no> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-30 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To clear the host information for server blade 1:
$ delete blade os-info 1 -F
I0117 : <Blade 1> Clearing host information was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

disconnect blade bmc session


Closes all remote console sessions connected to the specified server blade.
In an SMP configuration, specify the primary server blade. Closes remote
console sessions connected to the primary server blade.

Syntax
disconnect blade bmc session <blade_no>[-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To close all remote console sessions connected to server blade 1:
disconnect blade bmc session 1

Rules
In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and the sessions are
not closed:
E0640 : <Blade %1$d> Command was canceled. Specified blade is not
the primary blade of SMP.

export blade efi setting


Exports the EFI setting values of the server blade to a file.

Commands That Can Be Executed From the CLI Console 5-31


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
export blade efi setting <blade_no>

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To export the EFI setting values of server blade 1 to a file:
$ export blade efi setting 1
Confirm? (y/[n]):y
I0108 : <Blade 1> Writing EFI settings to file was completed.
I0009 : File name is "eficonf-1-20150301-090000.txt".
S0002 : Command succeeded.
S0000 : Command was finished.
$

import blade efi setting


Imports the EFI setting values of the server blade into a file.

Syntax
import blade efi setting <blade_no> -f <file_name> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-f<file_name>
Name of the file to which the EFI setting values are written.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-32 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To import the EFI setting values of server blade 1 into a file:
$ import blade efi setting 1 -f xxx.txt -F
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
• Before executing the command, you need to use the FTP protocol to send
the file to which the EFI setting values are written.
• To create a file in which the EFI setting values are written, as a base, use
the file output by the export blade efi setting command.
• If the model of the server blade is different from the one used when EFI
setting values are exported, an attempt to import the EFI setting values
will fail.

init blade bmc setting


Initializes the BMC configuration information for the server blades.
Regardless of whether the specified server blades constitute an SMP
configuration, the BMC configuration information for each specified server
blade is initialized.

Syntax
init blade bmc setting [<blade_no>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To initialize the BMC configuration information of server blade 1:
init blade bmc setting 1

Commands That Can Be Executed From the CLI Console 5-33


Hitachi Compute Blade 2500 Series Management Module User Guide
Rules
• When you execute this command, the BMC automatically starts. The SEL
entry "Server blade: SVP-BMC communication error (IPMI over LAN)"
might be collected, but this is not a problem.
• In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and the sessions
are not closed:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.

init blade efi setting


Initializes the UEFI configuration information for the server blades.
Regardless of whether the specified server blades constitute an SMP
configuration, the UEFI configuration information for each specified server
blade is initialized.

Syntax
init blade efi setting [<blade_no>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To initialize the EFI configuration information of server blade 1:
init blade efi setting 1

Rules
In an SMP configuration, if you execute this command with a non-primary
server blade specified, the command processing finishes normally but the
configuration information for the server blade is not initialized.

5-34 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
If you execute this command for CB 520X B1/B2, BMC automatically restarts
and the SEL entry "Server blade: SVP-BMC communication error (IPMI over
LAN)" might be collected. However, this does not cause any problems.
While the server blade is powered on, this command displays the following
message and is not executed:
E0620 : <Blade X> Command was canceled. Response from BMC was
abnormal.

If the above message appears while the server blade is powered off, contact
your reseller or maintenance personnel.

poweroff blade
Powers off the server blades. The following are two methods for powering off
server blades:
• Forced power-off
• Power-off
Select the method for powering off the server blade by specifying a
parameter. Specify either -h or -s.

In an SMP configuration, specify primary server blades. All server blades


constituting the SMP configuration are powered off.

Syntax
poweroff blade [<blade_no>] [-h¦-s] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-h
Forcibly powers off the specified server blade.
-s
Shuts down the OS running on the specified server blade and then powers
off the server blade. Note that, depending on the settings of the OS
running on the server blade, the server blade might not be powered off.
Before you use this command, check the OS settings.
If you omit both the -h and -s parameters, this command assumes that -s is
specified.

Commands That Can Be Executed From the CLI Console 5-35


Hitachi Compute Blade 2500 Series Management Module User Guide
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To shut down the OS running on server blade 1:
poweroff blade 1

To forcibly power off all server blades:


poweroff blade all -h

Rules
In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and the server blade is
not powered off:
E0640 : <Blade %1$d> Command was canceled. Specified blade is not
the primary blade of SMP.

poweron blade
Powers on the server blades.
In an SMP configuration, specify primary server blades. All server blades
constituting an SMP configuration are powered on.

Syntax
poweron blade [<blade_no>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To power on server blade 1:
poweron blade 1

5-36 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Rules
• If the OS operation mode is LP and no LP license is set, you cannot power
on the server blade.
• In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and the server
blade is not powered on:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.

pre-configure blade
Executes Smart configure for the server blades.
In an SMP configuration, specify primary server blades. Smart configure is
executed for all server blades constituting the SMP configuration.

Syntax
pre-configure blade [<blade_no>] -m <preconf_mode> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-m
Smart configure execution mode
get: Forced acquisition
maint: Diagnosis
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To execute Pre-configure for server blade 1:
pre-configure blade 1 -m get

Rules
In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and Smart configure is
not executed:

Commands That Can Be Executed From the CLI Console 5-37


Hitachi Compute Blade 2500 Series Management Module User Guide
E0640 : <Blade %1$d> Command was canceled. Specified blade is not
the primary blade of SMP.

reset blade
Resets the server blades. The following are two methods for resetting the
server blade:
• Hard reset
• NMI issuance
In an SMP configuration, specify primary server blades. The server blades
constituting the SMP configuration are reset.

Syntax
reset blade [<blade_no>] [-h¦-s] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-h
Executes hard reset for the specified server blade.
If you omit both the -h and -s parameters, this command assumes that -
h is specified.
-s
Issues an NMI (Non-Maskable Interrupt) for the OS running on the
specified server blade.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To reset server blade 1:
reset blade 1

To issue an NMI for all server blades:


reset blade all -s

5-38 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Rules
In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and the server blade is
not reset:
E0640 : <Blade %1$d> Command was canceled. Specified blade is not
the primary blade of SMP.

set blade ac-recovery


Changes the settings for the operation to be performed when power is
restored to the server blades.
In an SMP configuration, if you specify a primary server blade, the settings
for the operation to be performed when power is restored to all server blades
constituting the SMP configuration are changed. If you specify non-primary
server blades, the setting values are changed but they do not affect the
behavior of the non-primary server blades.

Syntax
set blade ac-recovery [<blade_no>] [-a <ac_recovery>] [-w
<wait_time>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-a <ac_recovery>
Operation to be performed when the power supply is restored
¢ stay: Keeps the server blade powered off even when power is supplied
to the server chassis.
¢ pon: Powers on the server blade when power is supplied to the server
chassis.
¢ last: Returns the power status of the server blade to its previous
status (right before the server chassis was powered off) when power
is supplied to the server chassis.
-w <wait_time>
Wait time after power is restored (in minutes).
You can specify a value from 0 to 60.
-F

Commands That Can Be Executed From the CLI Console 5-39


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To power on server blade 1, 10 minutes after power is supplied to the server
chassis:
set blade ac-recovery 1 -a pon -w 10

To power on server blade 1 immediately when power is supplied to the server


chassis:
set blade ac-recovery 1 -a pon -w 0

To keep server blade 1 powered off when power is supplied to the server
chassis:
set blade ac-recovery 1 -a stay

To return the power status of server blade 2 to its previous status (right
before the server chassis was powered off) when power is supplied to the
server chassis:
set blade ac-recovery 2 -a last

Rules
If you execute this command with a non-primary server blade specified, the
following warning message appears because the setting values do not affect
the behavior of the non-primary server blade:
W0031 : <Blade X> Set data is not used. Specified blade is not the
primary blade of SMP. (X indicates the specified server blade
number.)

set blade bmc account


Sets a BMC user account whose BMC user account number of the server
blade is in the range from 1 to 4.
Regardless of whether an SMP configuration is used, the BMC user account of
the specified server blade is set.
Set the following items:
• Whether to enable or disable the BMC user account
• User name
• Password

Syntax
set blade bmc account <blade_no> -a <account_no> [-u <account_use>]
[-n <user_name>] [-p <password>] [-F]

Privilege
Server blade privileges

5-40 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-a <account_no>
BMC user account number.
You can specify a value from 1 to 4. You cannot specify multiple values.
-u <account_use>
Whether to enable or disable the BMC user account
¢ enable: Enables the BMC user account.
¢ disable: Disables the BMC user account.
If you omit this parameter, the setting (enable or disable) is not changed.
You cannot disable the BMC user account number 1.
-n <user_name>
User name
You can enter a character string of 1 to 16 characters. The string can
contain alphanumeric characters and the following symbols: . _ $ - = + *
% ? @ / \ ' ! ~ ; ^ ( ) [ ] { } | , ` The symbols <, >, &, #, ", and spaces
cannot be used.
The first character must be an alphanumeric character.
If you omit this parameter, the user name is not changed.
You cannot register the same user name as another BMC user account. In
addition, you cannot register the same user name as an IPMI user
account.
-p <password>
Password
You can enter a character string of 1 to 20 characters. The string can
contain alphanumeric characters and the following symbols: . _ $ - = + *
% ? : @ / \ ' ! ~ ; ^ ( ) [ ] { } | , ` The symbols <, >, &, #, ", and
spaces cannot be used.
If you omit this parameter, the password is not changed.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable a BMC user account whose BMC user account number is 1, for the
server blade number 1:
$ set blade bmc account 1 -a 1 -u enable -n bmcuser -p password
Confirm? (y/[n]):y
I0037 : <Blade 0> Setting was completed.
S0002 : Command succeeded.

Commands That Can Be Executed From the CLI Console 5-41


Hitachi Compute Blade 2500 Series Management Module User Guide
S0000 : Command was finished.
$

Rules
You cannot disable the BMC user account number 1 for each server blade.

set blade bmc time local


Changes the BMC clock of the server blade.
Regardless of whether the specified server blade constitutes an SMP
configuration, the BMC clock of the specified server blade is changed.

Syntax
set blade bmc time local <blade_no> -d <date_time> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-d <date_time>
Date and time
The format is YYYY-MM-DD hh:mm:ss.
Separate the date and the time with a space character. Enclose the entire
value in double quotation marks, because this value contains a space
character.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the BCM clock of server blade 1:
set blade bmc time local 1 -d "2012-05-01 15:00:00" -F

Rules
• This command cannot be used to change the BMC time for the CB 520H
B3, if the BMC time adjustment method for the server blade is set to
Synchronize time to the management module using NTP.
If Synchronize time to the management module using NTP is
specified and this command is executed, the BMC time is not changed.

5-42 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
However, the following message indicating that the command finished
normally is displayed:
I0037 : <Blade X> Setting was completed. (X: Server blade number)
• This command cannot change the BMC time for the other server blades.
Executing this command does not change the BMC time. However, the
following message indicating that the command finished normally is
displayed:
I0037 : <Blade X> Setting was completed. (X: Server blade number)

set blade ipmi account


Sets an IPMI user account for the server blade. You can set an IPMI user
account whose number is in the range from 2 to 9.
Regardless of whether an SMP configuration is used, the IPMI user account of
the specified server blade is set.
Set the following items:
• Whether to enable or disable the IPMI user account
• User name
• Password
• Privilege

Syntax
set blade ipmi account <blade_no> -a <account_no> [-u <account_use>]
[-n <user_name>] [-p <password>] [-l <privilege_level>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-a <account_no>
IPMI user account number.
You can specify a value from 2 to 9. You cannot specify multiple values.
You cannot set the IPMI user account number 1.
-u <account_use>
Whether to enable or disable the IPMI user account
¢ enable: Enables the IPMI user account
¢ disable: Disables the IPMI user account
If you omit this parameter, the setting (enable or disable) is not
changed.

Commands That Can Be Executed From the CLI Console 5-43


Hitachi Compute Blade 2500 Series Management Module User Guide
-n <user_name>
User name
You can enter a character string of 1 to 16 characters. The string can
contain alphanumeric characters and the following symbols: . _ $ - = + *
% ? @ / \ ' ! ~ ; ^ ( ) [ ] { } | , ` The symbols <, >, &, #, ", and spaces
cannot be used.
The first character must be an alphanumeric character.
If you omit this parameter, the user name is not changed.
You cannot register the same user name as another IPMI user account..
In addition, you cannot register the same user name as an BMC user
account.
-p <password>
Password
You can enter a character string of 1 to 20 characters. The string can
contain alphanumeric characters and the following symbols: . _ $ - = + *
% ? : @ / \ ' ! ~ ; ^ ( ) [ ] { } | , ` The symbols <, >, &, #, ", and
spaces cannot be used.
If you omit this parameter, the password is not changed.
-l <privilege_level>
Privilege
You can select from the following privilege levels:
¢ administrator: Administrator
¢ operator: Operator
¢ user: User
¢ callback: Callback
¢ noaccess: NO ACCESS
If you omit this parameter, the privilege is not changed. The initial
value is NO ACCESS.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable the IPMI user account whose account number is 3, for the server
blade number 1:
$ set blade ipmi account 1 -a 3 -u enable -n ipmiuser -p password -l
operator
Confirm? (y/[n]):y
I0037 : <Blade 0> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

5-44 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set blade led
Turns the identification LED indicators of the server blades on or off.
Regardless of whether the specified server blades constitute an SMP
configuration, the identification LED indicator for each specified server blade
is turned on or off.

Syntax
set blade led [<blade_no>] -l <led_type> -t <led_on_off> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-l <led_type>
LED indicator type
lid: Identification LED indicator
-t <led_on_off>
LED indicator status
on: Turns the LED indicator on.
off: Turns the LED indicator off.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To turn on the identification LED indicator of server blade 1:
set blade led 1 -l lid -t on

To turn off the identification LED indicator of server blade 1:


set blade led 1 -l lid -t off

set blade maintenance-mode


Sets maintenance mode for the server blade when maintenance work for the
server blade is performed. Do not use this command for normal operations
because this command is used for maintenance work.

Commands That Can Be Executed From the CLI Console 5-45


Hitachi Compute Blade 2500 Series Management Module User Guide
If you set maintenance mode, the remaining time for maintenance mode is
set to 120 minutes.

Syntax
set blade maintenance-mode <blade_no> -m <mnt_mode> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-m <mnt_mode>
Maintenance mode
• enable: Sets maintenance mode.
• disable: Cancels maintenance mode.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set maintenance mode for server blade 1:
$ set blade maintenance-mode 1 -m enable
Confirm? (y/[n]):y
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set blade lom license


Registers the LOM license for the server blade.
You must specify either -k <lom_key> or -f <key_file> as a parameter for
which the LOM license key is specified.

Syntax
set blade lom license <blade_no> -l <lom_license> {-k <lom_key>¦-f
<key_file>} [-F]

Privilege
Server blade privileges

5-46 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-l <lom_license>
Information about whether LOM is used
¢ enable: LOM is used
¢ disable: LOM is not used
-k <lom_key>
LOM license key
You can use a maximum of 256 characters.
-f <key_file>
LOM license key file name
You can use a maximum of 256 characters.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the LOM license of server blade 1:
$ set blade lom license 1 -l enable -k XXXXXXXXXXXXXXXXXXXXXXXX
Confirm? (y/[n]):y
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
If you specify the LOM license key file name, before executing this command,
use the FTP protocol to send the LOM license key file.
If you send the LOM license key file while executing this command to register
the LOM license key, registration of the LOM license key might fail.

set blade mgmt-lan


Changes the following management LAN settings for the server blade.
• IP address (IPv4)
• Subnet mask
• Default gateway
Regardless of whether the specified server blade constitutes an SMP
configuration, the management LAN settings for the specified server blade
are changed.

Commands That Can Be Executed From the CLI Console 5-47


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
set blade mgmt-lan <blade_no> [-i <ip_addr>] [-s <subnet_mask>] [-g
<default_gateway>] [-F]

Privilege
Network privilege

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-i <ip_addr>
IP address
-s <subnet_mask>
Subnet mask
-g <default_gateway>
Default gateway
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the IP address, subnet mask, and default gateway for the
management LAN of server blade 1:
set blade mgmt-lan 1 -i 192.168.0.50 -s 255.255.255.0 -g 192.168.0.1

To change the IP address for the management LAN of server blade 1:


set blade mgmt-lan 1 -i 192.168.0.60

set blade mgmt-v6 address


Sets the management LAN (IPv6) for the server blade.
You can set a static address. To set a static address, enter the following
items:
• IP address (IPv6)
• Prefix length
• Whether to enable use of the default gateway
• Default gateway

Syntax
set blade mgmt-v6 address <blade_no> -st <setting> [-i <ip_address>]
[-p <prefix_len>] [-gs <dgw_setting>] [-g <default_gateway>] [-F]

5-48 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Network privilege

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-st <setting>
Specify whether to enable use of a static address.
¢ enable: Enabled.
¢ disable: Disabled.
You cannot omit this parameter.
-i <ip_address>
IP address (IPv6)
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.

-p <prefix_len>
Prefix length
Specify a value from 1 to 128.
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.

-gs <dgw_setting>
Specify whether to enable use of the default gateway (IPv6).
¢ enable: Enabled.
¢ disable: Disabled.
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.
If you want to specify the default gateway (-g), specify enable.

-g <default_gateway>
Default gateway (IPv6)
If you entered -st enable or -gs enable, this item is required.
If you entered -st disable or -gs disable, or if you omitted -gs, omit
this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the static address for server blade 1 in the management LAN settings
(IPv6):

Commands That Can Be Executed From the CLI Console 5-49


Hitachi Compute Blade 2500 Series Management Module User Guide
set blade mgmt-v6 address 1 -st enable -i fe80::200:87ff:feb2:c24 -p
64 -gs enable -g fe80::200:87ff:feb2:c20

Rules
• A duplication check is not performed for the specified address.
• For the default gateway, you can specify only an address that is reachable
from the address for the server blade.
• You cannot set the loopback address (::1/128).

set blade os-mode


Changes the OS operation modes of the server blades.
In an SMP configuration, if you specify a primary server blade, the OS
operation modes of all server blades constituting the SMP configuration are
changed. If you specify non-primary server blades, the setting values are
changed but they do not affect the behavior of the non-primary server
blades.

Syntax
set blade os-mode [<blade_no>] -m <os_mode> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-m <os_mode>
OS operation mode
¢ basic: Starts the OS that runs when LPAR manager is disabled.
¢ hvm: Starts LPAR manager.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable LPAR manager on server blade 1:
set blade os-mode 1 -m hvm

To disable LPAR manager on server blade 2:

5-50 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set blade os-mode 2 -m basic

Rules
If you execute this command with a non-primary server blade specified, the
following warning message appears because the setting values do not affect
the behavior of the non-primary server blade:
W0031 : <Blade X> Set data is not used. Specified blade is not the
primary blade of SMP. (X indicates the specified server blade
number.)

set blade preconf


Changes the Smart configure settings for the server blades.
In an SMP configuration, if you specify a primary server blade, the Smart
configure settings for the server blades constituting the SMP configuration are
changed. If you specify non-primary server blades, the setting values are
changed but they do not affect the behavior of the non-primary server
blades.

Syntax
set blade preconf [<blade_no>] [-n <n+m>] [-w <wwn_type>] [-m
<mac_type>] [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-n <n+m>
N+M cold standby setting
¢ enable: Enables N+M cold standby.
¢ disable: Disables N+M cold standby.
-w <wwn_type>
WWN type
¢ original: Default Physical WWN
¢ additional: Optional Physical WWN
-m <mac_type>
MAC type

Commands That Can Be Executed From the CLI Console 5-51


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ original: Default Physical MAC
¢ additional: Optional Physical MAC
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable N+M cold standby and to set both the WWN type and the MAC type
to Optional Physical for server blade 1:
set blade preconf 1 -n enable -w additional -m additional -F
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
• When N+M cold standby is enabled, even if you specify Default Physical
WWN, Optional Physical WWN will be used.
• If you execute this command with a non-primary server blade specified,
the following warning message appears because the setting values do not
affect the behavior of the non-primary server blade:
W0031 : <Blade X> Set data is not used. Specified blade is not
the primary blade of SMP. (X indicates the specified server
blade number.)

set blade smp construction


Sets SMP configurations for the server blades.
You can use this command to specify SMP configuration patterns. You need to
select an SMP configuration pattern for each of the server blade slot number
ranges from 1 to 8 and from 9 to 15. You can separately specify an SMP
configuration pattern for slots 1 to 8 and for slots 9 to 15. The following table
describes SMP configuration patterns.

Description of SMP configuration Character string specified in the


patterns parameter

All server blades are used in non-SMP 1-1-1-1


configurations

The lower two tiers (slot number: 1 to 4 or 2-1-1


9 to 12) are used in a 2-blade SMP
configuration
The upper two tiers (slot number: 5 to 8 or
13 to 15) are used in a non-SMP
configuration

The middle two tiers (slot number: 3 to 6 1-2-1


or 11 to 14) are used in a 2-blade SMP
configurations

5-52 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Description of SMP configuration Character string specified in the
patterns parameter
The lowest tier (slot number: 1 and 2, or 9
and10) and the highest tier (slot number:
7 and 8, or 15) are used in non-SMP
configurations

The upper two tiers (slot number: 5 to 8 or 1-1-2


13 to 15) are used in 2-blade SMP
configurations
The lower two tiers (slot number: 1 to 4 or
9 to 12) are used in non-SMP
configurations

The lower two tiers (slot number: 1 to 4 or 2-2


9 to 12) are used in a 2-blade SMP
configuration
The upper two tiers (slot number: 5 to 8 or
13 to 15) are used in a 2-blade SMP
configuration

All tiers are used in 4-blade SMP 4


configurations

Syntax
set blade smp construction [-l <smp_pattern>] [-u <smp_pattern>] [-F]

Privilege
Chassis privilege

Parameters
-l <smp_pattern>
SMP configuration pattern to be set for slots 1 to 8
-u <smp_pattern>
SMP configuration pattern to be set for slots 9 to 15
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To use slots 1 to 8 in non-SMP configurations and the upper two tiers (slot
number: 13 to 15) in 2-blade SMP configurations:
set blade smp construction -l 1-1-1-1 -u 1-1-2

Rules
You can set configurations including SMP configuration settings only if either
of the following conditions is satisfied:

Commands That Can Be Executed From the CLI Console 5-53


Hitachi Compute Blade 2500 Series Management Module User Guide
• Server blades that support SMP configurations are installed into all slots
for which SMP is to be configured, and SMP connect boards appropriate
for SMP configurations are installed.
• No server blades are installed in the slots for which SMP is to be
configured.
When you configure a non-SMP configuration, you can ignore the installation
statuses of server blades and SMP connection boards.
You cannot change the SMP configuration settings of server blades when the
server blades to be changed are powered on, or are being powered on or off.

set blade tpm license


Registers the TPM license for the server blade.

Syntax
set blade tpm license <blade_no> -k <tpm_key> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-k <tpm_key>
TPM license key
You can use a maximum of 127 characters.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the TPM license of server blade 1:
$ set blade tpm license 1 -k XXXXXXXXXXXXXXXXXXXXXXXX
Confirm? (y/[n]):y
I0037 : <Blade 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

show blade bmc account


Displays the BMC user account of the server blade. Regardless of whether an
SMP configuration is used, the BMC user account of the specified server blade

5-54 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
is displayed. For a server blade, BMC user accounts whose BMC user account
number is in the range from 1 to 4 are displayed.
The following items are displayed:
• BMC user account number of the server blade.
• Whether to enable or disable the user account
• User name
The password is not displayed.

Syntax
show blade bmc account [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the BMC user accounts of server blade number 1:
$ show blade bmc account 1
-- BMC user account information --
Slot : 1
-- BMC user account --
User account number : 1
Use : enable
User name : user
-- BMC user account --
User account number : 2
Use : disable
User name :
-- BMC user account --
User account number : 3
Use : disable
User name :
-- BMC user account --
User account number : 4
Use : disable
User name :
S0002 : Command succeeded.
S0000 : Command was finished.
$

Commands That Can Be Executed From the CLI Console 5-55


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-15 BMC user account information

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.

Table 5-16 BMC user account

Displayed item Description


User account number BMC user account number.
The range is from 1 to 4.
Use Whether to enable or disable the BMC user
account
• enable: Enabled.
• disable: Disabled.
User name User name

show blade bmc session


Displays the following information about the remote console sessions
connected to the server blades:
• Session number
• Session type
• Session ID
• IP address type
• Connection-source IP address
• Connected user name
• Session start time
In an SMP configuration, specify primary server blades. The remote console
session information for the primary server blade is displayed.

Syntax
show blade bmc session [<blade_no>]

Privilege
Server blade privileges

5-56 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display information about the remote console session for server blade 1:
show blade bmc session 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-17 BMC session

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.

Session Count Number of sessions

Table 5-18 BMC session detail

Displayed item Description


Number Remote console session number
Session kind Remote console session type
Remote Console: Remote console
Session ID Remote console session ID
IP kind Remote console session IP address type
IPv4: IPv4
IPv6: IPv6
IP address Remote console session IP address
User name Remote console session user name
Session start time Remote console session start time
The format is YYYY/MM/DD hh:mm:ss.

Rules
• User name might not be displayed.

Commands That Can Be Executed From the CLI Console 5-57


Hitachi Compute Blade 2500 Series Management Module User Guide
• In an SMP configuration, if you execute this command with a non-primary
server blade specified, the following message appears and the session
information is not displayed:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.

show blade bmc time local


Displays the BMC clocks of the server blades.
Regardless of whether the specified server blades constitute an SMP
configuration, the BMC clock for each specified server blade is displayed.

Syntax
show blade bmc time local [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the BMC clock of server blade 1:
show blade bmc time local 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-19 BMC local time

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Date Date
The date format is YYYY-MM-DD.
For YYYY, a value from 1970 to 2037 is
displayed. For MM, a value from 01 to 12 is
displayed. For DD, a value from 01 to 31 is
displayed.

5-58 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Time Time
The time format is hh:mm:ss.
hh is a value from 00 to 23. mm is a value from
00 to 59. ss is a value from 00 to 59.

show blade firmware


Displays the following firmware version information for the server blades:
• Server blade firmware version
• BMC version
• EFI version
• LPAR manager firmware version
• LPAR manager firmware area number
For each of the above items, the current version and the version to be used
during the next startup are displayed. The current LPAR manager firmware
version is displayed when LPAR manager firmware is assigned to the server
blade and the OS operation mode is LP. The version to be used during the
next startup is displayed when LPAR manager firmware is assigned to the
server blade.

Syntax
show blade firmware [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the firmware version information for server blade 1:
show blade firmware 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-59


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-20 Server blade firmware version

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.

Table 5-21 Total version

Displayed item Description


Current version Current server blade firmware version
Next version Server blade firmware version to be used during
the next startup

Table 5-22 BMC version

Displayed item Description


Current version Current BMC version
Next version BMC version to be used during the next startup

Table 5-23 EFI version

Displayed item Description


Current version Current EFI version
Next version EFI version to be used during the next startup

Table 5-24 LPAR manager firmware

Displayed item Description


Current version Current LPAR manager firmware version
Current bank Area number of the current LPAR manager
firmware
Next version LPAR manager firmware version to be used
during the next startup
Next bank Area number of the LPAR manager firmware to
be used during the next startup

show blade hardware


Displays the following hardware information for the server blade:
• Hardware information
• FRU information
• Sensor information

5-60 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
show blade hardware [<blade_no>] [-h] [-f] [-s]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-h
Displays the hardware information for the specified server blade.
-f
Displays the FRU information for the specified server blade.
-s
Displays the sensor information for the specified server blade.
You must specify at least one of -h, -f, and -s parameters.

Execution example
To display the hardware information, FRU information, and sensor information
for server blade 5 (primary server blade) when server blades 5 and 7
constitute an SMP configuration:
$ show blade hardware 5 -h -f -s
-- Server blade hardware information --
Slot : 5
-- Server blade --
Product name : XXXXXXXX
Model name : XXXXXXXX
Serial number : XXXXXXXX
-- CPU --
Name : XXXXXXXX
Installed : 2
Slots : 2
-- CPU (SMP configuration) --
Installed : 4
Slots : 4
-- Memory (SMP configuration) --
Memory [MB] : 32768
-- I/O card --
Mezzanine 1 : -----
Mezzanine 2 : XXXXXXXX
Mezzanine 3 : -----
Mezzanine 4 : -----
PCI 0 : -----
PCI 1 : -----
Daughter card 0 : -----

Commands That Can Be Executed From the CLI Console 5-61


Hitachi Compute Blade 2500 Series Management Module User Guide
-- OnBoard LAN 1 --
Type : -----
-- LP license --
LP model : -----
Upper bound of version : -----
-- Power --
Nameplate power [W] : 268
-- Weight --
Weight [kg] : 6.700
-- UUID --
UUID : XXXXXXXX-XXXX-XXXX-XXXX-
XXXXXXXXXXXX
-- BMC MAC address --
BMC MAC address 0 : 00:00:87:22:ba:20
BMC MAC address 1 : 00:00:87:22:ba:21
-- LOM type --
LOM : enable
-- SMP configuration --
Product name : 2-blade SMP connect board
Primary blade : 6
Blade list : 4,6
-- Server blade FRU information --
-- Board Information --
Manufacture : XXXXXXXX
Product Name : XXXXXXXX
Serial Number : XXXXXXXX
Part/Model Number : XXXXXXXX
-- Product Information --
Manufacture : XXXXXXXX
Product Name : XXXXXXXX
Part/Model Number : XXXXXXXX
Product Version : XXXXXXXX
Serial Number : XXXXXXXX
Asset Tag : XXXXXXXX
-- MultiRecord Information --
Manufacture ID : 000074
Module Type 1 : 00
Module Type 2 : 71
OEM Type : 02000000
E Type : 01
BMC LAN#0 MAC Addr. : 00:00:87:22:ba:20
BMC LAN#1 MAC Addr. : 00:00:87:22:ba:21
BMC USB#0 MAC Addr. : 00:00:87:22:ba:22
BMC USB#1 MAC Addr. : 00:00:87:22:ba:23
Nameplate : 268
Product Part/Model Number for Maintenance : XXXXXXXX
UUID : XXXXXXXX-XXXX-XXXX-XXXX-
XXXXXXXXXXXX
BMC LAN Connection : 00
LOM Type : 00
LOM#1 MAC for Port#0 : 00:00:87:22:ba:20
LOM#1 MAC for Port#1 : 00:00:87:22:ba:21
LOM#2 MAC for Port#0 : 00:00:87:22:ba:22
LOM#2 MAC for Port#1 : 00:00:87:22:ba:23
10GbE LOM Compatibility : 00
Weight : 6.700
-- Mezzanine FRU Information --
Mezzanine number : 2
-- Product area Information --
Manufacture : XXXXXXXX

5-62 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Product Name : XXXXXXXX
Part/Model Number : XXXXXXXX
Serial Number : XXXXXXXX
-- Server blade sensor information --
-- Temp --
Inlet 1 Temp : 25.00
Inlet 2 Temp : 25.00
VInlet 1 Temp : 25.00
VInlet 2 Temp : 23.00
VInlet 3 Temp : 23.00
-- Volt --
MB VBAT : 2.96
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.
Common displayed items (items displayed when -h, -f, or -s is specified)

Table 5-25 Server blade hardware information

Displayed item Description


Slot Slot number
Regardless of which parameter (-h, -s, or -f)
you specified, the slot number for each server
blade is displayed first.

Hardware information displayed items (items displayed when -h is specified)

Table 5-26 Server blade

Displayed item Description


Product name Name
Model name Model name
Serial number Serial number

Table 5-27 CPU

Displayed item Description


Name Name
Installed Number of installed CPUs (value for target
server blades)
Slots Total number of slots (value for target
server blades)

Commands That Can Be Executed From the CLI Console 5-63


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-28 CPU(SMP configuration)

Displayed item Description


Installed Number of installed CPUs (total number
of CPUs that are installed in all server
blades constituting an SMP configuration)
Slots Total number of slots (total number of
slots for all server blades constituting an
SMP configuration)

Tip: This item is displayed only for primary server blades in an SMP
configuration.

Table 5-29 Memory

Displayed item Description


Memory [MB] Memory (MB) (total memory capacity of
the target server blade)

Tip: This item is displayed only for server blades in a non-SMP


configuration or for non-primary server blades in an SMP configuration.

Table 5-30 Memory (SMP configuration)

Displayed item Description


Memory [MB] Memory (MB) (total memory capacity of
all server blades constituting an SMP
configuration)

Tip: This item is displayed only for primary server blades in an SMP
configuration.

Table 5-31 I/O card

Displayed item Description


Mezzanine 1 Mezzanine name
Mezzanine 2 Mezzanine name
Mezzanine 3 Mezzanine name
Mezzanine 4 Mezzanine name
PCI 0 PCI card name
PCI 1 PCI card name
Daughter card 0 Daughter card name

5-64 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
If an internal SD card is installed, the
name of the internal SD card is displayed.

Table 5-32 OnBoard LAN 1

Displayed item Description


Type Type
LOM#1 MAC for Port#0 MAC address for port 0
LOM#1 MAC for Port#1 MAC address for port 1
LOM#1 MAC for Port#2 MAC address for port 2
LOM#1 MAC for Port#3 MAC address for port 3

Tip: LOM#1 MAC for Port#0, LOM#1 MAC for Port#1, LOM#1 MAC for
Port#2, and LOM#1 MAC for Port#3 are displayed only when an Onboard
LAN is installed.

Table 5-33 PCI expansion blade

Displayed item Description


full height connection kit Whether the PCI expansion blade is
installed
• installed(PCI expansion blade x16
full height card adapter): The PCI
expansion blade ((x16 FH 1slot)) is
installed.
• installed(PCI expansion blade x8 full
height card adapter): The PCI
expansion blade ((x8 FH 2slot)) is
installed.
low profile connection kit Whether the PCI expansion blade
connection kit is installed
• installed(PCI expansion blade x8 low
profile card adapter): The PCI
expansion blade connection kit ((x8
LP 2slot)) is installed.
• installed(PCI expansion blade x4 low
profile card adapter): The PCI
expansion blade connection kit ((x4
LP 4slot)) is installed.
• not installed: The PCI expansion
blade connection kit is not installed.

Tip: The above items are displayed only if a PCI expansion blade is
installed.

Commands That Can Be Executed From the CLI Console 5-65


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-34 LP license

Displayed item Description


LP model LP model
Upper bound of version Upper bound of the available version
range

Table 5-35 Power

Displayed item Description


Nameplate power [W] Rated power (W)

Table 5-36 Weight

Displayed item Description


Weight [kg] Weight (kg)

Table 5-37 UUID

Displayed item Description


UUID UUID

Table 5-38 BMC MAC address

Displayed item Description


BMC MAC address 0 MAC address 0 for BMC
BMC MAC address 1 MAC address 1 for BMC

Table 5-39 Expansion blade

Displayed item Description


Product name Product name
The name of the expansion blade is displayed.
Model name Model name
The model name of the expansion blade is
displayed.
Serial number Serial number
The serial number of the expansion blade is
displayed.

Tip: The above items are displayed only if an expansion blade is installed.

5-66 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-40 LOM type

Displayed item Description


LOM LOM type
Whether LOM support of the server blade is enabled
is displayed.
• enable: Enabled
• disable: Disabled
• -----: The information about whether LOM
support is enabled is not set.

Table 5-41 SMP configuration

Displayed item Description


Product name SMP connection board name
Primary blade Primary server blade number
Displays the primary server blade
number for the SMP configuration.
This is a value from 1 to 15.
Blade list List of server blades
Displays the numbers for all server
blades constituting an SMP
configuration.
This is a value from 1 to 15.

FRU information displayed items (items displayed when -f is specified)

Table 5-42 Server blade FRU information

Displayed item Description


Board Information Lists the FRU board information items
for the server blade.
Product Information Lists the FRU product information
items for the server blade.
MultiRecord Information Lists the FRU MultiRecord information
items for the server blade.

Table 5-43 Mezzanine FRU Information

Displayed item Description


Mezzanine number Mezzanine number

Tip: This item is displayed only when a mezzanine card is installed.

Commands That Can Be Executed From the CLI Console 5-67


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-44 Product area Information

Displayed item Description


Manufacture Manufacturer code
Product Name Product name
Part/Model Number Model name
Serial Number Serial number

Table 5-45 Extension blade FRU Information

Displayed item Description


Board Information The board information about the FRUs
of the expansion blade is displayed.
Product Information The product information about the
FRUs of the expansion blade is
displayed.
MultiRecord Information The multi-record information about
the FRUs of the expansion blade is
displayed.

Tip: The above items are displayed only if an expansion blade is installed.

Sensor information displayed items (items displayed when -s is specified)

Table 5-46 Server blade sensor information

Displayed item Description


Temp Lists the thermal sensor names and
sensor values for the server blade.
Volt Lists the voltage sensor names and
sensor values for the server blade.

show blade hvm setting


Displays the following LPAR manager settings for the server blades:
• LPAR manager model
• Available LPAR manager firmware version
In an SMP configuration, if you specify primary server blades or non-primary
server blades, the LPAR manager settings for the specified server blades are
displayed. If you specify non-primary server blades, the setting values are
shown in parentheses.

5-68 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
In a non-SMP configuration, the LPAR manager settings for the specified
server blades are displayed.

Syntax
show blade hvm setting [<blade_no>] [-p]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-p
Displays the LP licenses to be used in an SMP configuration. In an SMP
configuration, specify primary server blades. In a non-SMP configuration,
the LP license for each server blade is displayed.

Execution example
To display the LPAR manager settings for server blade 1:
show blade hvm setting 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-47 LPAR manager setting

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
LPAR manager license Model LPAR manager model
Type
• Essential: Essential model
• Advanced: Advanced model
• -----: Displayed when no server blade is
installed, the LP license is not set, or the slot
number is the larger of the two slot numbers
(the even number) used for the full-width blade.
LPAR manager license Enable Available LPAR manager firmware version
Version

Commands That Can Be Executed From the CLI Console 5-69


Hitachi Compute Blade 2500 Series Management Module User Guide
show blade ipmi account
Displays the IPMI user account of the server blade.
Regardless of whether an SMP configuration is used, the IPMI user account of
the specified server blade is displayed. For a server blade, IPMI user accounts
whose IPMI user account number is in the range from 2 to 9 are displayed.
The following items are displayed:
• IPMI user account number of the server blade.
• Whether to enable or disable the IPMI user account
• User name
• Privilege
The password is not displayed.

Syntax
show blade ipmi account [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the IPMI user accounts of server blade number 1:
$ show blade ipmi account 1
-- IPMI user account information --
Slot : 1
-- IPMI user account --
User account number : 2
Use : enable
User name : user
Privilege : Administrator
-- IPMI user account --
User account number : 3
Use : disable
User name :
Privilege :
(omitted)
-- IPMI user account --
User account number : 9
Use : disable
User name :

5-70 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege :
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-48 IPMI user account information

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.

Table 5-49 IPMI user account

Displayed item Description


User account number IPMI user account number.
This is a value from 2 to 9.
Use Whether to enable or disable the IPMI user
account
• enable: Enabled.
• disable: Disabled.
User name User name
Privilege Privilege
You can display the following privilege levels:
• Administrator
• Operator
• User
• Callback
• NO ACCESS

show blade maintenance-mode


Displays whether maintenance work for the server blades is performed.
The following information is displayed:
• Maintenance mode settings
• Remaining time for maintenance mode
• The IP address for the Maintenance LAN

Syntax
show blade maintenance-mode [<blade_no>]

Commands That Can Be Executed From the CLI Console 5-71


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Server blade privilege

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the maintenance mode for server blade 1:
$ show blade maintenance-mode 1
-- Blade maintenance mode --
Slot : 1
Maintenance mode : enable
Remaining time (min) : 115
IP address : 192.168.254.11
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-50 Blade maintenance mode

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Maintenance mode Maintenance mode
• enable: Maintenance work is performed.
• disable: Maintenance work is not performed.
Remaining time (min) Remaining time for maintenance mode (minutes)
• 0-120: The remaining time for maintenance
mode (minutes)
• -----: Maintenance work is not performed.
IP address Maintenance LAN's IP address
• -----: Not set

show blade mgmt-lan


Displays the following management LAN settings for the server blades:

5-72 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
• IP address
• Subnet mask
• Default gateway
Regardless of whether the specified server blades constitute SMP, the
management LAN settings for each specified server blade are displayed.

Syntax
show blade mgmt-lan [<blade_no>]

Privilege
Network privilege

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the management LAN settings for server blade 1:
show blade mgmt-lan 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-51 Blade management LAN setting

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
IP address IP address
Subnetmask Subnet mask
Default gateway Default gateway

show blade mgmt-v6 setting


Displays the management LAN settings for server the blades.
The following information is displayed:
• IPv6 address configuration information for the server blade

Commands That Can Be Executed From the CLI Console 5-73


Hitachi Compute Blade 2500 Series Management Module User Guide
• Static address of the server blade

Syntax
show blade mgmt-v6 setting [<blade_no>]

Privilege
Network privilege

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the management LAN settings (IPv6) for server blade 1:
show blade mgmt-v6 setting 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-52 Blade management LAN setting (IPv6)

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.

Table 5-53 IPv6 address setting

Displayed item Description


Allocation Address setting method
Displays the address allocation method.
• Static address: Static address
Status Status
Displays whether address settings are enabled.
• enable: Enabled.
• disable: Disabled.
IP address IP address (IPv6)
Prefix len Prefix length
This is a value from 1 to 128.

5-74 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Default gateway Default gateway (IPv6)

show blade os-info


Displays host information including the host name and OS that obtained from
the server blade.

Syntax
show blade os-info [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the host information for server blade 1:
$ show blade os-info 1
-- Blade hosts information --
Slot : 1
Host name : Server-1
OS : Microsoft Windows Server 2012 R2 Standard
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-54 Blade hosts information

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Host name Host name obtained from the server blade

Commands That Can Be Executed From the CLI Console 5-75


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• ----- : Displayed when host name is not
obtained, or the OS operation mode of the
server blade is LP mode.
OS OS name obtained from the server blade
• LP : Displayed when the OS operation mode
of the server blade is LP mode.
• ----- : Displayed when host name is not
obtained.

show blade setting


Displays the following settings for the server blades:
• Operation to be performed when the power supply is restored
• Wait time after power is restored
• N+M cold standby setting
• WWN type
• MAC type
• OS operation mode
In an SMP configuration, if you specify a primary server blade, the settings
for all server blades constituting the SMP configuration are displayed. If you
specify non-primary server blades, the setting values are shown in
parentheses. The setting values do not affect the behavior of the non-primary
server blades.

Syntax
show blade setting [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the settings for server blade 1:
$ show blade setting 1
-- Blade setting --
Slot : 1

5-76 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-- Blade AC recovery setting --
AC recovery : stay
Wait time(min) : 10
-- Blade pre-configure setting --
N+M : enable
WWN type : additional
MAC type : additional
-- OS mode --
OS mode : basic
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-55 Blade setting

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.

Table 5-56 Blade AC recovery setting

Displayed item Description


AC recovery Operation to be performed when the power supply
is restored.
• stay: Keeps the server blade powered off even
when power is supplied to the server chassis.
• pon: Powers on the server blade when power
is supplied to the server chassis.
• last: Returns the power status of the server
blade to its previous status (right before the
server chassis was powered off) when power
is supplied to the server chassis.
In an SMP configuration, the settings for non-
primary server blades are shown in parentheses.
The values enclosed with parentheses do not affect
the behavior of the non-primary server blades.
Wait time(min) Wait time after power is restored
In an SMP configuration, the settings for non-
primary server blades are shown in parentheses.
The values enclosed with parentheses do not affect
the behavior of the non-primary server blades.

Table 5-57 Blade Smart configure setting

Displayed item Description


N+M N+M cold standby setting

Commands That Can Be Executed From the CLI Console 5-77


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• enable: N+M cold standby is enabled.
• disable: N+M cold standby is disabled.
In an SMP configuration, the settings for non-
primary server blades are shown in parentheses.
The values enclosed with parentheses do not affect
the behavior of the non-primary server blades.
WWN type WWN type
• original: Default Physical
• additional: Optional Physical
In an SMP configuration, the settings for non-
primary server blades are shown in parentheses.
The values enclosed with parentheses do not affect
the behavior of the non-primary server blades.
MAC type MAC type
• original: Default Physical
• additional: Optional Physical
In an SMP configuration, the settings for non-
primary server blades are shown in parentheses.
The values enclosed with parentheses do not affect
the behavior of the non-primary server blades.

Table 5-58 OS mode

Displayed item Description


OS mode OS operation mode
• basic: The OS that runs when LPAR manager is
disabled starts.
• hvm: LPAR manager starts.
In an SMP configuration, the settings for non-
primary server blades are shown in parentheses.
The values enclosed with parentheses do not affect
the behavior of the non-primary server blades.

show blade smp construction


Displays the SMP configuration patterns for server blades.
An SMP configuration pattern is displayed for each of the server blade slot
number ranges from 1 to 8 and from 9 to 15. The following table describes
SMP configuration patterns.

Description of SMP configuration Character string displayed as an


patterns execution result

All server blades are used in non-SMP 1-1-1-1


configurations

5-78 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Description of SMP configuration Character string displayed as an
patterns execution result

The lower two tiers (slot number: 1 to 4 or 2-1-1


9 to 12) are used in a 2-blade SMP
configuration
The upper two tiers (slot number: 5 to 8 or
13 to 15) are used in a non-SMP
configuration

The middle two tiers (slot number: 3 to 6 1-2-1


or 11 to 14) are used in a 2-blade SMP
configurations
The lowest tier (slot number: 1 and 2, or 9
and10) and the highest tier (slot number:
7 and 8, or 15) are used in a non-SMP
configuration

To use the upper two tiers (slot number: 5 1-1-2


to 8 or 13 to 15) in 2-blade SMP
configurations
To use the lower two tiers (slot number: 1
to 4 or 9 to 12) in non-SMP configurations

The lower two tiers (slot number: 1 to 4 or 2-2


9 to 12) are used in a 2-blade SMP
configuration
The upper two tiers (slot number: 5 to 8 or
13 to 15) are used in a 2-blade SMP
configuration

All tiers are used in a 4-blade SMP 4


configurations

Syntax
show blade smp construction

Privilege
Chassis privilege

Parameters
None

Execution example
To display the SMP configuration for the server chassis:
show blade smp construction

Commands That Can Be Executed From the CLI Console 5-79


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
Table 5-59 SMP construction

Displayed item Description


Slot 1-8 SMP configuration pattern for slots 1 to 8
Slot 9-15 SMP configuration pattern for slots 9 to 15

show blade status


Displays the statuses of the server blades.

Syntax
show blade status [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the status of server blade 1:
$ show blade status 1
-- Blade status --
Slot : 1
Install : installed
Initialize : Init comp
Power detail : Off
Power : Off
Fail : Normal
Warning : Normal
Mass(kg) : 13.400
-- Power On suppression --
Status : disable
-- LED status --
LED type : POWER
Light : off
LED type : FAULT
Light : off
LED type : ERROR LOG
Light : off
LED type : LID
Light : off

5-80 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-- SMP connect board status --
Install : not installed
SMP type : -----
-- N+M cold standby status --
Last result : Don't care
Status : Not get
CNA Information Status : Not backed up
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-60 Blade status

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
In an SMP configuration, the server blade type (primary
server blade or non-primary server blade) is displayed
next to the server blade number.
• Example: When the server blade is the primary
server blade:
Slot : 1 (primary)
• Example: When the server blade is a non-primary
server blade:
Slot : 3 (non primary)
Install Whether the server blade is installed
• installed: The server blade is installed.
• not installed: The server blade is not installed.
• -----: Indicates that the larger of the two slot
numbers (the even number) is used for the full-
width blade.
Regardless of whether the specified server blades
constitute an SMP configuration, whether or not each
specified server blade is installed is displayed.
Initialize The initialization status of the server blade
The initialization status of the server blade is displayed.
After initialization successfully ends, you can perform
operations such as a power supply operation.
• Not install: The server blade is not installed.
• Not initialize: The server blade is not initialized.
• Init executing: The server blade is now being
initialized.
• Init comp: The server blade was successfully
initialized.

Commands That Can Be Executed From the CLI Console 5-81


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• Reinitializing: The server blade was successfully
initialized and is now being reinitialized (BMC
restart, server blade firmware update, etc.).
• Init comp NG: Initialization of the server blade
failed.
• -----: Indicates the larger of the two slot numbers
(the even number) used for the full-width blade.
In an SMP configuration, if you specify a primary server
blade, the initialization status of the entire SMP
configuration is displayed. The following are initialization
statuses of the entire SMP configuration:
• Not install: No server blades constituting an SMP
configuration are installed.
• Not install: At least one server blade constituting an
SMP configuration is installed and the BMC
initialization has not started yet.
• Init executing: In the SMP configuration, there are
some server blades whose BMCs are being
initialized.
• Init comp: The BMCs of all server blades
constituting an SMP configuration were successfully
initialized.
• Reinitializing: In an SMP configuration, there are
some server blades whose BMCs are being
reinitialized after they were successfully initialized.
• Init comp NG: In an SMP configuration, there are
some server blades that failed to be initialized. This
status is set if initialization is performed when only
some of the server blades constituting an SMP
configuration or only some of the SMP connect
boards are installed.
• -----: Indicates the larger of the two slot numbers
(the even number) used for the full-width blade.
In an SMP configuration, if you specify a non-primary
server blade, the initialization status of the server blade
is displayed. The following are initialization statuses for a
server blade:
• Not install: The server blade is not installed.
• Not initialize: The server blade is not initialized.
• Init executing: The server blade is now being
initialized.
• Init comp: The server blade was successfully
initialized.
• Init comp NG: Initialization of the server blade
failed.
• -----: Indicates the larger of the two slot numbers
(the even number) used for the full-width blade.
Power detail Detailed power supply status of the server blade
• Off: The server blade is powered off.

5-82 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• Reserve: The server blade is in a reservation
standby state and is waiting to be powered on.
• Powering on: The blade server is now powering on.
• Reserve: The server blade is powered on.
• Powering on: The blade server is now powering off.
• Error: Acquisition of the information failed.
• -----: Indicates no server blade installed, a non-
primary server blade in an SMP configuration, or the
larger of the two slot numbers (the even number)
used for the full-width blade.
In an SMP configuration, if you specify a primary server
blade, the detailed power supply status of the entire
SMP configuration is displayed.
Power Power supply status of the server blade
• Off: The server blade is powered off.
• On: The server blade is powered on.
• -----: Indicates no server blade installed, a non-
primary server blade in an SMP configuration, or the
larger of the two slot numbers (the even number)
used for the full-width blade.
In an SMP configuration, if you specify a primary server
blade, the detailed power supply status of the entire
SMP configuration is displayed.
Fail Failure status of the server blade
• Normal: The status of the server blade is normal.
• FAIL: A failure occurred for the server blade.
• -----: Indicates no server blade installed, or the
larger of the two slot numbers (the even number)
used for the full-width blade.
Regardless of whether the specified server blades
constitute an SMP configuration, the status of each
specified server blade is displayed.
Warning Warning status of the server blade
• Normal: The status of the server blade is normal.
• WARNING: A warning was issued for the server
blade.
• -----: Indicates that no server blade is installed, or
the larger of the two slot numbers (the even
number) is used for the full-width blade.
Regardless of whether the specified server blades
constitute an SMP configuration, the warning status of
each specified server blade is displayed.
Mass (kg) Weight of the server blade
The weight is given in kilograms (kg).
Regardless of whether the specified server blades
constitute an SMP configuration, the weight of each
specified server blade is displayed.

Commands That Can Be Executed From the CLI Console 5-83


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
TPM License TPM License
• enable: Enabled
• disable: Disabled
Regardless of whether the specified server blades
constitute an SMP configuration, the TPM license of each
specified server blade is displayed. This item is not
displayed when no server blade is installed, or the server
blade slot is the larger of the two slot numbers (the even
number) used for the full-width blade. This item is not
displayed when TPM license management function is
disabled.

Table 5-61 Power On suppression

Displayed item Description


Status Power-on suppression status
• enable: The power-on suppression status is
enabled.
• disable: The power-on suppression status is
disabled.
• -----: Indicates that no server blade is installed, a
non-primary server blade is in an SMP
configuration, or the larger of the two slot numbers
(the even number) is used for the full-width blade.
In an SMP configuration, if you specify a primary server
blade, the power-on suppression status of the entire
SMP configuration is displayed.

Table 5-62 LED status

Displayed item Description


LED type LED indicator type
If the server blade is not installed, this item is not
displayed.
• POWER: LED indicator for the power button
• FAULT: Failure detection LED indicator
• ERROR LOG: Error log LED indicator
• LID: Identification LED indicator
• PRIMARY: Primary LED indicator. This item is
displayed only for CB 520X B1/B2 server blades.
Regardless of whether the specified server blades
constitute SMPs, the LED indicator type for each
specified server blade is displayed.
Light LED indicator status
If the server blade is not installed, this item is not
displayed.
• on: The LED indicator is lit.

5-84 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• off: The LED indicator is unlit.
Regardless of whether the specified server blades
constitute an SMP configuration, the LED indicator
status for each specified server blade is displayed.

Table 5-63 SMP connect board status

Displayed item Description


Install Installation status of the SMP connect board
• installed: The SMP connect board is installed.
• not installed: The SMP connect board is not
installed.
SMP type Type of the SMP connect board
• 1SMP: The 1-blade SMP connect board is
installed.
• 2SMP: The 2-blade SMP connect board is
installed.
• 4SMP: The 4-blade SMP connect board is
installed.
• -----: No SMP connect board is installed, or the
SMP connect board type is unknown.

Table 5-64 N+M cold standby status

Displayed item Description


Last result The last execution result of N+M cold standby
The execution result when Smart configure was last
executed is displayed.
• OK: The last execution completed normally. You
can use the server blade as is.
• NG: The last execution failed. According to the
condition, execute Smart configure or power on
the server blade.
• Don't care: Pre-configure is disabled.
• -----: Indicates that no server blade is installed, a
non-primary server blade is in an SMP
configuration, or the larger of the two slot
numbers (the even number) is used for the full-
width blade.
In an SMP configuration, if you specify a primary
server blade, the last execution result of N+M cold
standby for the entire SMP configuration is displayed.
Status N+M cold standby status
• Not get: The information is not collected. This
indicates that Smart configure has not been
executed since the server chassis was powered on
or the server blade configuration was changed.

Commands That Can Be Executed From the CLI Console 5-85


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• Getting: The information will be collected. This
indicates that Smart configure is either manually
or automatically executed.
• Valid: The information is valid. This indicates that
the execution of Smart configure finishes.
• Not set: The information is not set. This indicates
that although the N+M cold standby failover
occurred, the failover or recovery destination
server blade is not started. This status
temporarily occurs during the N+M cold standby
failover or recovery.
• -----: Indicates that no server blade is installed, a
non-primary server blade is in an SMP
configuration, or the larger of the two slot
numbers (the even number) is used for the full-
width blade.
In an SMP configuration, if you specify a primary
server blade, the N+M cold standby status of the
entire SMP configuration is displayed.
CNA Information Status CNA information status
• Not backed up: The information is not backed up.
• Backed up: The information is backed up.
• Waiting for restore: The information is waiting to
be restored.
• Waiting for clear: The information is waiting to be
cleared.
• -----: Indicates that no server blade is installed, a
non-primary server blade is in an SMP
configuration, or the larger of the two slot
numbers (the even number) is used for the full-
width blade.
In an SMP configuration, if you specify a primary
server blade, the CNA information status of the entire
SMP configuration is displayed.

update blade firmware bulk


Updates the firmware for the server blades.
In an SMP configuration, you need to update the firmware for all server
blades constituting the SMP configuration at the same time. Because of this,
specify the numbers of all server blades constituting an SMP configuration.

Syntax
update blade firmware bulk [<blade_no>] -f <fw_file_name> [-F]

Privilege
Server blade privileges

5-86 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-f <fw_file_name>
Name of the firmware update file
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To update the firmware of server blade 1:
$ update blade firmware bulk 1 -f xxx.update
W0012 : BMC restart automatically.
W0013 : New EFI firmware will be used the next time EFI is booted.
Confirm? (y/[n]):y
I0107 : <Blade 1> Update firmware was started.
I0042 : <Blade 1> Update firmware was completed.
I0015 : Update firmware was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
• You must send the firmware update file via FTP before executing this
command.
If you send a firmware update file while this command is running, the
firmware update might fail. If the firmware update fails, retry the update
operation.
• If you specify only some of the server blades constituting an SMP
configuration, the following message appears and the update is not
performed:
E0655 : <Blade X> Command was canceled. Only a part of the
blades of the SMP is specified. (X indicates the specified
server blade number.)

Commands to manage management modules


This section describes the commands to confirm and change the settings for
management modules.

clear mgmt-module boot-disable


Clears the boot disable status for a management module.

Commands That Can Be Executed From the CLI Console 5-87


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
clear mgmt-module boot-disable <mgmt_no> [-F]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You cannot specify multiple values.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To clear the boot disable status for management module 1:
clear mgmt-module boot-disable 1

Rules
If you clear the boot disable status for the management module that you are
connecting to, when execution of this command finishes, sessions with
management modules will close.

delete mgmt-module file


Deletes files under the user directories for management modules.

Syntax
delete mgmt-module file {-a¦-f <file_name>} [-F]

Privilege
Chassis privilege

Parameters
-a
Deletes all files.
-f <file_name>
File name
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-88 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To delete all files under the user directories for management modules:
delete mgmt-module file -a

To delete the file readme.txt under the user directories for management
modules:
delete mgmt-module file -f readme.txt

restart mgmt-module
Restarts management modules.

Syntax
restart mgmt-module [<mgmt_no>] [-a] [-s] [-F]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management modules.
-a
Restarts the active management module. You can omit this parameter.
-s
Restarts the standby management module. You can omit this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To restart management module 1:
restart mgmt-module 1

To restart the active management module:


restart mgmt-module -a

To restart the standby management module:


restart mgmt-module -s

Commands That Can Be Executed From the CLI Console 5-89


Hitachi Compute Blade 2500 Series Management Module User Guide
Rules
If you restart the management module that you are connecting to, when
execution of this command finishes, sessions with management modules will
close.

set mgmt-module led


Turns the LID lamps of management modules on or off.

Syntax
set mgmt-module led [<mgmt_no>] [-a] [-s] -l <led_type> -t
<led_on_off> [-F]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management modules.
-a
Operates the active management module. You can omit this parameter.
-s
Operates the standby management module. You can omit this parameter.
-l <led_type>
LED indicator type
lid: Identification LED indicator
-t <led_on_off>
LED indicator status
on: Turns the LED indicator on.
off: Turns the LED indicator off.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To turn on the LID lamp for management module 1:
set mgmt-module led 1 -l lid -t on

To turn off the LID lamp for management module 1:

5-90 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set mgmt-module led 1 -l lid -t off

set mgmt-module dns


Sets the DNS to be used in the management LAN for management modules.
You can set the following information:
• Information about whether to prioritize IPv4 DNS settings or IPv6 DNS
settings
• IPv4 DNS settings (a maximum of three addresses)
• IPv6 DNS settings (a maximum of three addresses)

Syntax
set mgmt-module dns -p <priority> [-v4 <ipv4_addr>] [-v6
<ipv6_addr>] [-F]

Privilege
Network privilege

Parameters
-p <priority>
Priority
Specify whether to access IPv4 DNS servers first or to access IPv6 DNS
servers first.
¢ ipv4: Gives priority to IPv4 DNS servers.
¢ ipv6: Gives priority to IPv6 DNS servers.
You cannot omit this parameter.
-v4 <ipv4_addr>
IP address for a DNS server (IPv4)
You can specify a maximum of three IPv4 addresses separated by
commas. Do not enter a space character between a comma and an
address.
The IP addresses of the current IPv4 DNS servers will be replaced with
the entered addresses. Specify the IP addresses for all DNS servers that
you want to use.
If you omit this parameter, all IPv4 DNS server settings will be deleted.
-v6 <ipv6_addr>
DNS server IP address (IPv6)
You can specify a maximum of three IPv6 addresses separated by
commas. Do not enter a space character between a comma and an
address.
The addresses of the current IPv6 DNS servers will be replaced with the
entered addresses. Specify the IP addresses for all DNS servers that you
want to use.

Commands That Can Be Executed From the CLI Console 5-91


Hitachi Compute Blade 2500 Series Management Module User Guide
If you omit this parameter, all IPv6 DNS server settings will be deleted.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set one set of IPv4 DNS servers and two sets of IPv6 DNS servers, and to
give priority to the IPv6 DNS servers:
set mgmt-module dns -p ipv6 -v4 192.168.20.101 -v6
fe80::200:87ff:feb2:c24,fe80::200:87ff:feb2:c20

Rules
• A duplication check is not performed for the specified address.
• For the default gateway, you can specify an address that is reachable
from the address for management modules.
• For the IP addresses of IPv6 DNS server, you cannot set the loopback
address (::1/128).
• For the IP addresses of IPv4 DNS servers, you can specify only an
address that has a value in the range from 1 to 126 or from 128 to 223 in
the top field.
• You cannot set a broadcast address, which is an address that has all 0s or
1s in the host field.

set mgmt-module maintenance-mode


Sets the maintenance mode for the management module when maintenance
work for the modules below is performed. Do not use this command for
normal operations because this command is used for maintenance work.
• Management module
• Management LAN module
If you set maintenance mode, the remaining time for maintenance mode is
set to 120 minutes.

Syntax
set mgmt-module maintenance-mode <mgmt_no> -m <mnt_mode> [-F]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number

5-92 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
You can specify either 1 or 2 as the value. You cannot specify multiple
values.
-m <mnt_mode>
Maintenance mode
¢ enable: Sets maintenance mode.
¢ disable: Cancels maintenance mode.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the maintenance mode for management module 1:
$ set mgmt-module maintenance-mode 1 -m enable
Confirm? (y/[n]):y
I0062 : <Management module 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set mgmt-module mgmt-lan


Sets the management LAN for management modules.

Syntax
set mgmt-module mgmt-lan [-i <ip_addr>] [-s <subnet_mask>] [-g
<default_gateway>] [-d0 <dns>] [-d1 <dns>] [-d2 <dns>] [-F]

Privilege
Network privilege

Parameters
-i <ip_addr>
IP address
-s <subnet_mask>
Subnet mask
-g <default_gateway>
Default gateway
-d0 <dns>
DNS server address (1st)
-d1 <dns>
DNS server address (2nd)

Commands That Can Be Executed From the CLI Console 5-93


Hitachi Compute Blade 2500 Series Management Module User Guide
-d2 <dns>
DNS server address (3rd)
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the management LAN for management modules:
set mgmt-module mgmt-lan -i 192.168.0.20 -s 255.255.255.0 -g
192.168.0.70 -F

Rules
• If you do not specify any parameters, configuration of the settings fails.
• To configure the DNS settings, use the command set mgmt-module dns.

set mgmt-module mgmt-v6 address


Sets the management LAN (IPv6) for management modules.
You can set a static address. To set a static address, enter the following
items:
• IP address (IPv6)
• Prefix length
• Whether to enable use of the default gateway
• Default gateway

Syntax
set mgmt-module mgmt-v6 address -st <setting> [-i <ip_address>] [-p
<prefix_len>] [-gs <dgw_setting>] [-g <default_gateway>] [-F]

Privilege
Network privilege

Parameters
-st <setting>
Specify whether to enable use of a static address.
¢ enable: Enabled.
¢ disable: Disabled.
You cannot omit this parameter.
-i <ip_address>
IP address (IPv6)

5-94 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.

-p <prefix_len>
Prefix length
Specify a value from 1 to 128.
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.

-gs <dgw_setting>
Specify whether to enable use of the default gateway (IPv6).
¢ enable: Enabled.
¢ disable: Disabled.
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.
If you want to specify the default gateway (-g), specify enable.

-g <default_gateway>
Default gateway (IPv6)
If you entered -st enable or -gs enable, this item is required.
If you entered -st disable or -gs disable, or if you omitted -gs, omit
this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set a static address in the management LAN settings (IPv6) for
management modules:
set mgmt-module mgmt-v6 address -st enable -i
fe80::200:87ff:feb2:c24 -p 64 -gs enable -g fe80::200:87ff:feb2:c20

Rules
• A duplication check is not performed for the specified address.
• For the default gateway, you can specify an address that is reachable
from the address for management modules.
• You cannot set the loopback address (::1/128).

set mgmt-module int-lan


Sets the internal LAN for management modules.

Syntax
set mgmt-module int-lan -i <ip_addr> [-F]

Commands That Can Be Executed From the CLI Console 5-95


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Network privilege

Parameters
-i <ip_addr>
IP address
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the internal LAN for management modules:
$ set mgmt-module int-lan -i 192.168.253.0
W0001 : If confirm, this connect is lost.
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
The subnet mask is fixed to 255.255.255.0.
After you set the internal LAN, the management modules are restarted and
the sessions are closed.

set mgmt-module serial-port


Changes the serial port settings for management modules.

Syntax
set mgmt-module serial-port [-b <baud_rate>] [-F]

Privilege
Chassis privilege

Parameters
-b <baud_rate>
Baud rate
Specify one of the following values: 9,600, 19,200, 38,400, 57,600, or
115,200. You can omit this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-96 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To set the baud rate for the management module serial port to 9,600 bps:
set mgmt-module serial-port -b 9600

show mgmt-module firmware


Displays the management module firmware version.

Syntax
show mgmt-module firmware

Privilege
Chassis privilege

Parameters
None

Execution example
To display the management module firmware version:
show mgmt-module firmware

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-65 Management module firmware

Displayed item Description


Slot Management module number
This is a value 1 or 2.
Behavior System status of the management module
• active: Active system
• standby: Standby system

Table 5-66 Solo bank firmware

Displayed item Description


UEFI UEFI version
The maximum length is 8 characters.
FPGA FPGA version
The maximum length is 8 characters.
CPLD CPLD version

Commands That Can Be Executed From the CLI Console 5-97


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
The maximum length is 8 characters.

Table 5-67 Dual bank firmware

Displayed item Description


Bank Bank number
This is a value from 0 to 1.
Status Bank status
• active: Bank in use
• alternate: Alternative bank
Revision Firmware version
The maximum length is 32 characters.
FW_A FW_A version
The maximum length is 8 characters.
FW_B FW_B version
The maximum length is 8 characters.
FW_C FW_C version
The maximum length is 8 characters.
MIB MIB version
The maximum length is 5 characters.

Table 5-68 Dictionary

Displayed item Description


Revision Dictionary version
The maximum length is 5 characters.

show mgmt-module hardware


Displays the information about the hardware of management modules.
• Hardware information
Displayed if you specify the -h parameter.
• FRU information
Displayed if you specify the -f parameter.
• Sensor information
Displayed if you specify the -s parameter.

You need to specify at least one of the following parameters: -h, -f, and -s.
If you omit all the parameters, the management module information is not
displayed. You can specify all of the parameters. The information that you

5-98 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
specify by using the parameters is displayed for each management module,
in order of hardware information, FRU information, and sensor information.
You can specify multiple management module numbers. If you do not specify
a number, the information of all management modules is displayed.

Syntax
show mgmt-module hardware [<mgmt_no>] [-h] [-f] [-s]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management modules.
-h
Displays the hardware information for the specified management
modules.
-f
Displays the FRU information for the specified management modules.
-s
Displays the sensor information for the specified management modules.

Execution example
To display the hardware information, FRU information, and sensor information
for management module 1:
$ show mgmt-module hardware 1 -h -f -s
-- Management module hardware information --
Slot : 1
-- Management module --
Product name : Management Module
MAC address (Management LAN port) : 00:00:00:00:00:00
MAC address (Maintenance LAN port) : 00:00:00:00:00:01
-- Management module FRU information --
-- Board Information --
Manufacture : XXXX
Product name : XXXXXXXX
Serial Number : XXXXXXXX
-- Product Information --
Manufacture : HITACHI
Product name : Management Module
Product Version : XXXXXXXX
-- MultiRecord Information --
Manufacture ID : 000074
Module Type 1 : 04

Commands That Can Be Executed From the CLI Console 5-99


Hitachi Compute Blade 2500 Series Management Module User Guide
Module Type 2 : 00
Chassis Product Part/Model Number : XXXXXXXX
Chassis Serial Number : XXXXXXXX
Midplane ID : 00
Chassis Product Part/Model Number for Maintenance : XXXXXXXX
Model ID : 00
Additional WWN : 2400000087000000
SVP Model Type for MUI : 00
SVP Model Type for Web-Console Logo : 00
SVP Model Type for Corporate Logo : 00
System Logo : XXXXXXXX
OEM Type : 00
Part code system ID : 00
Additional MAC : 00:00:87:78:A8:00
LP Type : 00
-- Management module sensor information --
-- Temp --
Temperature : 23.00
-- Volt --
12.0V : 12.18
5.0V : 4.98
3.3V : 3.28
2.5V : 2.50
1.8V : 1.78
1.5V : 1.50
1.35V : 1.34
1.2V : 1.20
1.1V : 1.09
1.0V0 : 0.99
1.0V1 : 0.98
VCC : 0.82
VNN : 1.00
VDDQ : 1.32
VTT : 0.66
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.
• Common displayed items (items displayed when -h, -f, or -s is specified)

Table 5-69 Management module hardware information

Displayed item Description


Slot Management module number
This is a value 1 or 2.

• Hardware information displayed items (items displayed when -h is


specified)

5-100 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-70 Management module

Displayed item Description


Product name Name
• -----: The management module is not installed.

MAC address(Management LAN MAC address of the management LAN port


port) • -----: The management module is not installed.

MAC address(Maintenance LAN MAC address of the maintenance LAN port


port) • -----: The management module is not installed.

• FRU information displayed items (items displayed when -f is specified)


This information is not displayed if the management module is not
installed.

Table 5-71 Board Information

Displayed item Description


Manufacture Manufacturer code
Product name Product name
Serial Number Serial number

Table 5-72 Product Information

Displayed item Description


Manufacture Manufacturer code
Product name Product name
Product Version Product version

Table 5-73 MultiRecord Information

Displayed item Description


Manufacture ID Code for Hitachi
Module Type 1 Module type code 1
Module Type 2 Module type code 2
Chassis Product Part/Model Equipment model name
Number

Chassis Serial Number Serial number of the chassis


Midplane ID Midplane type
Chassis Product Part/Model Maintenance component code
Number for Maintenance

Model ID Chassis type

Commands That Can Be Executed From the CLI Console 5-101


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Additional WWN Additional WWN
SVP Model Type for MUI System name after you log in to the SVP system
console, and the system name displayed in the title
bar of the Web console browser
SVP Model Type for Web- Product logo displayed in the Web console
Console Logo

SVP Model Type for Corporate logo displayed in the Web console
Corporate Logo

System Logo System logo


OEM Type Type code related to the sales territory and channel
Part code system ID Component code (maintenance component model
name) system
Additional MAC Optional Physical MAC address
LP Type Code for distinguishing between the names for inside
and outside Japan

• Sensor information displayed items (items displayed when -s is specified)


This information is not displayed if the management module is not
installed.

Table 5-74 Management module sensor information

Displayed item Description


Temp Lists the thermal sensor names and sensor values for
the management module
Volt Lists the voltage sensor names and sensor values for
the management module

show mgmt-module int-lan


Displays the internal LAN settings of management modules.

Syntax
show mgmt-module int-lan

Privilege
Chassis privilege

Parameters
None

5-102 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the internal LAN settings of management modules:
$ show mgmt-module int-lan
-- Management module internal LAN setting --
IP address : 192.168.253.0
Subnetmask : 255.255.255.0
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-75 Management module internal LAN setting

Displayed item Description


IP address IP address
Subnetmask Subnet mask

show mgmt-module maintenance-mode


Displays whether maintenance work for the following modules is performed:
• Management modules
• Management LAN modules
The following information is displayed:
• Maintenance mode settings
• Remaining time for maintenance mode

Syntax
show mgmt-module maintenance-mode [<mgmt_no>]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management modules.

Commands That Can Be Executed From the CLI Console 5-103


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the maintenance mode for management module 1:
$ show mgmt-module maintenance-mode 1
-- Management module maintenance mode --
Slot : 1
Maintenance mode : enable
Remaining time (min) : 115
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-76 Management module maintenance mode

Displayed item Description


Slot Management module number
This is a value 1 or 2.
Maintenance mode Maintenance mode
• enable: Maintenance work is performed.
• disable: Maintenance work is not performed.

Remaining time(min) Remaining time for maintenance mode (minutes)


• 0-120: The remaining time for maintenance
mode (minutes)
• -----: Maintenance work is not performed.

show mgmt-module mgmt-lan


Displays the management LAN settings for management modules.

Syntax
show mgmt-module mgmt-lan

Privilege
Network privilege

Parameters
None

Execution example
To display the management LAN settings for management modules:
show mgmt-module mgmt-lan

5-104 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-77 Management module LAN interface setting

Displayed item Description


IP address IP address
Subnetmask Subnet mask
Default gateway Default gateway

Table 5-78 Management module DNS setting

Displayed item Description


DNS <number> DNS server address
<number> is a value from 0 to 2.

show mgmt-module mgmt-v6 setting


Displays the management LAN settings for management modules.
The following information is displayed:
• IPv6 address setting information for management modules
¢ Static address (IPv6 address, prefix, and default gateway)
• DNS server address information
¢ Information about whether to prioritize IPv4 DNS servers or IPv6 DNS
servers
¢ IPv4 DNS server addresses (a maximum of three addresses)
¢ IPv6 DNS server addresses (a maximum of three addresses)

Syntax
show mgmt-module mgmt-v6 setting

Privilege
Network privilege

Parameters
None

Execution example
To display the management LAN settings (IPv6) for management modules:
show mgmt-module mgmt-v6 setting

Commands That Can Be Executed From the CLI Console 5-105


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-79 IPv6 address setting

Displayed item Description


Allocation Address setting method
Displays the address allocation method.
• Static address: Static address
Status Status
Whether the address settings are enabled
• enable: Enabled.
• disable: Disabled.
IP address IP address (IPv6)
Prefix len Prefix length
This is a value from 1 to 128.
Default gateway Default gateway (IPv6)

Table 5-80 Management module DNS setting

Displayed item Description


Priority Priority
Displays whether to access IPv4 DNS servers first or
to access IPv6 DNS servers first.
• IPv4: IPv4 DNS servers have higher priority.
• IPv6: IPv6 DNS servers have higher priority.

Table 5-81 Management module DNS setting (IPv4)

Displayed item Description


DNS0 IP address for DNS server 0 (IPv4)
DNS1 IP address for DNS server 1 (IPv4)
DNS2 IP address for DNS server 2 (IPv4)

Table 5-82 Management module DNS setting (IPv6)

Displayed item Description


DNS0 IP address for DNS server 0 (IPv6)
DNS1 IP address for DNS server 1 (IPv6)
DNS2 IP address for DNS server 2 (IPv6)

5-106 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
show mgmt-module mnt-lan
Displays the maintenance LAN settings for management modules.

Syntax
show mgmt-module mnt-lan

Privilege
Network privilege

Parameters
None

Execution example
To display the maintenance LAN settings for management modules:
show mgmt-module mnt-lan

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-83 Management module maintenance LAN setting

Displayed item Description


IP address 1 IP address for management module slot 1
IP address 2 IP address for management module slot 2
Subnetmask Subnet mask

Table 5-84 Static route

Displayed item Description


Network address Network address
Subnetmask Subnet mask
Router IP address Router's IP address

show mgmt-module serial-port


Displays the serial port settings for management modules.
Displays only the baud rate and does not display the connection destination.

Syntax
show mgmt-module serial-port

Commands That Can Be Executed From the CLI Console 5-107


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Chassis privilege

Parameters
None

Execution example
To display the serial port settings for management modules:
show mgmt-module serial-port

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-85 Serial console setting

Displayed item Description


Baud rate(bps) Baud rate
9600, 38400, or 115200

show mgmt-module status


Displays the statuses of the management modules.

Syntax
show mgmt-module status [<mgmt_no>]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management modules.

Execution example
To display the status of management module 1:
$ show mgmt-module status 1
-- Management module status --
Slot : 1
Install : installed

5-108 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Behavior : active
Power : on
Fail : normal
Warning : normal
Condition : active
Mass(kg) : 20
-- LED status --
LED : Location Led
Light : on
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-86 Management module status

Displayed item Description


Slot Management module number
This is a value 1 or 2.
Install Whether the module is installed
• installed: The module is installed.
• not installed: The module is not installed.
Behavior System status of the management module
• active: Active system
• standby: Standby system
Power Power supply status of the module
• off: The module is powered off.
• on: The module is powered on.
Fail Failure status of the module
• normal: The status of the module is normal.
• fail: A failure occurred on the module.
Warning Warning status of the module
• normal: The status of the module is normal.
• warning: A warning was issued for the module.
Condition Status of the management module
• normal: Normal
• booting: Booting
• shutting down: Shutting down
• boot disable: Boot disable
• FAIL: A failure occurred.
Mass(kg) Weight of the module
The weight is given in kilograms (kg).

Commands That Can Be Executed From the CLI Console 5-109


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-87 LED status

Displayed item Description


LED type LED indicator type
Location Led: Identification LED indicator
Light LED indicator status
• on: The LED indicator is lit.
• off: The LED indicator is unlit.

shutdown mgmt-module
Shuts down management modules.
You can simultaneously specify the following parameters that specify the
management modules to shut down: <mgmt_no>, -a, and -s. If you omit all
of these parameters, all management modules are shut down.

Syntax
shutdown mgmt-module [<mgmt_no>] [-a] [-s] [-F]

Privilege
Chassis privilege

Parameters
<mgmt_no>
Management module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management modules.
-a
Shuts down the active management module.
-s
Shuts down the standby management module.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To shut down management module 1:
$ shutdown mgmt-module 1
W0001 : If confirm, this connect is lost.
Confirm? (y/[n]):y
I0068 : <Management module 1> Shutdown was completed.

5-110 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
If you shut down the management module that you are connecting to,
sessions with management modules are closed when the execution of this
command finishes.

switch mgmt-module behavior


Performs a failover between the active management module and the standby
management module.

Syntax
switch mgmt-module behavior [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To perform a failover between the active management module and the
standby management module:
switch mgmt-module behavior

Rules
When execution of this command finishes, sessions with management
modules are closed.

sync mgmt-module firmware


Copies the management module firmware and dictionary of the active
management module to the standby management module, and then updates
the firmware of the standby management module. This operation restarts the
standby management module.
You execute this command to match the firmware version of the standby
management module to the firmware version of the active management
module, after you replaced the management module in a maintenance
operation. Do not use this command in usual operation.

Commands That Can Be Executed From the CLI Console 5-111


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
sync mgmt-module firmware [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To synchronize the firmware of the active management module with the
firmware of the standby management module:
sync mgmt-module firmware

Rules
Under the following conditions, you cannot execute this command:
• Only one management module is installed.
• The standby management module is not placed in the BootDisable status.
• The management module firmware and dictionary are currently being
updated.

sync mgmt-module fru


Copies the equipment information that is recorded in the FRU of the active
management module to the standby management module.
You execute this command to synchronize the FRU information of the standby
management module with the FRU information of the active management
module. Do not use this command in usual operation.

Syntax
sync mgmt-module fru [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-112 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To synchronize the FRU settings of the active management module with the
FRU settings of the standby management module:
sync mgmt-module fru

Rules
Under the following conditions, you cannot execute this command:
• Only one management module is installed.
• Communication with the standby management module is impossible.

sync mgmt-module int-lan


Synchronizes the internal LAN settings of the active management module
with the internal LAN settings of the standby management module. This
operation restarts the standby management module.
You need to execute this command to synchronize the internal network
settings of the standby management module with the internal network
settings of the active management module. Do not use this command in
usual operation.

Syntax
sync mgmt-module int-lan [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To synchronize the internal LAN settings of the active management module
with the internal LAN settings of the standby management module:
sync mgmt-module int-lan

Rules
Under the following conditions, you cannot execute this command:
• Only one management module is installed.
• The standby management module is not placed in the BootDisable status.
• The management module firmware and dictionary are currently being
updated.

Commands That Can Be Executed From the CLI Console 5-113


Hitachi Compute Blade 2500 Series Management Module User Guide
update mgmt-module firmware
Updates the management module firmware.

Syntax
update mgmt-module firmware [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To update the management module firmware:
update mgmt-module firmware

Rules
You must send the firmware update file via FTP before executing this
command. When execution of this command finishes, sessions with
management modules are closed. Do not send the firmware update file while
this command is updating the firmware.
If you do, the firmware update might fail. If the update fails, retry the update
operation.

Commands to manage management LAN modules

set mgmt-lan-module led


Turns on or off the identification LED indicator for management LAN modules.

Syntax
set mgmt-lan-module led [<mgmt_lan_no>] -l <led_type> -t
<led_on_off> [-F]

Privilege
Chassis privilege

Parameters
<mgmt_lan_no>

5-114 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Management LAN module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management LAN modules.
-l <led_type >
LED indicator type
lid: Identification LED indicator
-t <led_on_off>
LED indicator status
¢ on: Turns the LED indicator on.
¢ off: Turns the LED indicator off.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To turn on the identification LED indicator of management module 1:
set mgmt-lan-module led 1 -l lid -t on

show mgmt-lan-module hardware


Displays the following hardware information for management LAN modules:
• Hardware information
• FRU information
• Sensor information

Syntax
show mgmt-lan-module hardware [<mgmt_lan_no>] [-h] [-f] [-s]

Privilege
Chassis privilege

Parameters
<mgmt_lan_no>
Management LAN module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management LAN modules.
-h

Commands That Can Be Executed From the CLI Console 5-115


Hitachi Compute Blade 2500 Series Management Module User Guide
Displays the hardware information for specified management LAN
modules.
-f
Displays the FRU information for specified management LAN modules.
-s
Displays the sensor information for specified management LAN modules.
You must specify at least one of -h, -f, and -s parameters.

Execution example
To display the hardware information, FRU information, sensor information for
management LAN module 1:
show mgmt-lan-module hardware 1 -h -f -s

Execution results
The following tables show the items that are displayed as the execution
results of this command.
Common displayed items (items displayed when -h, -f, or -s is specified)

Table 5-88 Management LAN module hardware information

Displayed item Description


Slot Management LAN module number
This is a value 1 or 2.

Hardware information displayed items (items displayed when -h is specified)

Table 5-89 Management LAN module

Displayed item Description


Module type Management LAN module is displayed.

Power consumption Rated power consumption


Weight [kg] Weight (kg)

FRU information displayed items (items displayed when -f is specified)

Table 5-90 Board Information

Displayed item Description


Manufacture Manufacturer code
Product Name Product name
Serial Number Serial number

5-116 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-91 Product Information

Displayed item Description


Product Name Product name
Displays Management LAN Module.

Manufacture Company name


Displays HITACHI.

Table 5-92 MultiRecord Information

Displayed item Description


Manufacture ID Code for Hitachi
Module Type1 Module type code 1
Module Type2 Module type code 2
Product Part/Model Number for Maintenance component code
Maintenance

Sensor information displayed items (items displayed when -s is specified)

Table 5-93 Management LAN module Sensor information

Displayed item Description


Volt Lists the names of the voltage sensors of the
management LAN modules and the values
obtained from the sensors. The sensor name
is either 3.3V or 1.2V.

show mgmt-lan-module status


Displays the statuses of management LAN modules.
The following information is displayed:
• Installation status
• Power supply status
• Operating status (failure or warning)
• LED status

Syntax
show mgmt-lan-module status [<mgmt_lan_no>]

Privilege
Chassis privilege

Commands That Can Be Executed From the CLI Console 5-117


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<mgmt_lan_no>
Management LAN module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all management LAN modules.

Execution example
To display the status of management LAN module 1:
show mgmt-lan-module status 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-94 Management LAN module status

Displayed item Description


Slot Management LAN module number
This is a value 1 or 2.
Install Whether the module is installed
• installed: The module is installed.
• not installed: The module is not installed.
Power Power supply status of the module
• off: The module is powered off.
• on: The module is powered on.
Fail Failure status of the module
• normal: The status of the module is normal.
• fail: A failure occurred on the module.
Warning Warning status of the module
• normal: The status of the module is normal.
• fail: A warning was issued for the module.

Table 5-95 LED status

Displayed item Description


LED type LED indicator type
• PWR/WRN: Power supply/warning LED indicator
• LID: Identification LED indicator
Light LED indicator status
• on: The LED indicator is lit.
• off: The LED indicator is unlit.

5-118 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• blink: The LED indicator is blinking.
• unknown: The lightning status of the LED
indicator is unknown.
Color LED indicator color
• blue: Blue
• green: Green
• yellow: Yellow
• unknown: Information about the color of the LED
indicator could not be retrieved.
• -----: The LED indicator is unlit.
The color for each LED indicator type is as
follows: Green or yellow for PWR/WRN, and blue
for LID.

Commands to manage I/O adapters

set iobd led


Turns the identification LED indicators of I/O adapters on or off.

Syntax
set iobd led -i <iobd_no> -l <led_type> -t <led_on_off> [-F]

Privilege
Chassis privilege

Parameters
-i <iobd_no>
I/O adapter number
You can specify a value from 01A to 14A or from 01B to 14B. You can
specify multiple values separated by commas. You cannot omit this
parameter.
-l <led_type >
LED indicator type
lid: Identification LED indicator
-t <led_on_off>
LED indicator status
¢ on: Turns the LED indicator on.
¢ off: Turns the LED indicator off.
-F

Commands That Can Be Executed From the CLI Console 5-119


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To turn on the identification LED indicator of I/O adapter 01A:
set iobd led -i 01A -l lid -t on

show iobd hardware


Displays the following hardware information for I/O adapters:
• Hardware information
• FRU information

Syntax
show iobd hardware -i <iobd_no> [-h] [-f]

Privilege
Chassis privilege

Parameters
-i <iobd_no>
I/O adapter number
You can specify a value from 01A to 14A or from 01B to 14B. You can
specify multiple values separated by commas. You cannot omit this
parameter.
-h
Displays the hardware information for the specified I/O adapters.
-f
Displays the FRU information for the specified I/O adapters.
You must specify either of the parameters -h and -f.

Execution example
To display the FRU information for I/O adapter 01A:
$ show iobd hardware -i 01A -f
-- I/O board module hardware information --
Slot : 01A
-- I/O board module FRU information --
-- Board information --
Manufacture : XXXXXXXX
Product Name : XXXXXXXX
Serial Number : XXXXXXXXXXXX
-- Product information --
Product Name : I/O Board Module
Manufacture : HITACHI

5-120 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-- MultiRecord information --
Manufacture ID : 00000074
Module Type1 : XX
Module Type2 : XX
Product Part/Model Number for Maintenance : XXXXXXXXXX
Product ID : 0200
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.
Common displayed items (items displayed when -h or -f is specified)

Table 5-96 I/O adapter hardware information

Displayed item Description


Slot I/O adapter number
This is a value from 01A to 14A or from 01B to
14B.

Hardware information displayed items (items displayed when -h is specified)

Table 5-97 I/O adapter

Displayed item Description


I/O board type I/O adapter type
The type of the I/O adapter installed in the I/O
adapter.
• unknown: Information about the I/O adapter
type could not be retrieved.

FRU information displayed items (items displayed when -f is specified)

Table 5-98 Board information

Displayed item Description


Manufacture Manufacturer code
Product Name Product name
Serial Number Serial number

Table 5-99 Product information

Displayed item Description


Product Name Product name

Commands That Can Be Executed From the CLI Console 5-121


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Displays I/O Board Module.

Manufacture Company name


Displays HITACHI.

Table 5-100 MultiRecord information

Displayed item Description


Manufacture ID Code for Hitachi
Module Type1 Module type code 1
Module Type2 Module type code 2
Product Part/Model Number for Maintenance component code
Maintenance

show iobd status


Displays the statuses of the I/O adapters.
The following information is displayed:
• Installation status
• Power supply status
• Operating status (failure or warning)
• LED status
• Whether a card is installed

Syntax
show iobd status -i <iobd_no>

Privilege
Chassis privilege

Parameters
-i <iobd_no>
I/O adapter number
You can specify a value from 01A to 14A or from 01B to 14B. You can
specify multiple values separated by commas. You cannot omit this
parameter.

Execution example
To display the status of I/O adapter 01A:

5-122 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
show iobd status -i 01A

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-101 I/O adapter status

Displayed item Description


Slot I/O adapter slot number
This is a value from 01A to 14A or from 01B to 14B.
Install Whether the module is installed
• installed: The module is installed.
• not installed: The module is not installed.
Power Power supply status of the module
• off: The module is powered off.
• on: The module is powered on.
Fail Failure status of the module
• normal: The status of the module is normal.
• fail: A failure occurred on the module.
Warning Warning status of the module
• normal: The status of the module is normal.
• fail: A warning was issued for the module.

Table 5-102 LED status

Displayed item Description


LED type LED indicator type
• POWER: Power/warning LED indicator, indicating
that the module status is normal.
• ATTENTION: Attention LED indicator
• LID: Identification LED indicator
Light LED indicator status
• on: The LED indicator is lit.
• off: The LED indicator is unlit.
• blink: The LED indicator is blinking.
Color LED indicator color
• blue: Blue
• green: Green
• red: Red
• amber: Amber
• unknown: Information about the color of the LED
indicator could not be retrieved.

Commands That Can Be Executed From the CLI Console 5-123


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• -----: The LED indicator is unlit.

Table 5-103 Card status

Displayed item Description


Install Whether a card is installed
• installed: A card is installed.
• not installed: No card is installed.

Commands to manage switch modules


This section describes the commands to confirm and change the switch
module settings.

poweroff sw-module
Powers off the switch module.

Syntax
poweroff sw-module [<sw_no>] [-F]

Privilege
Switch module privileges

Parameters
<sw_no>
Switch module number
You can specify a value from 1 to 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To power off the switch module 1:
$ poweroff sw-module 1
Confirm? (y/[n]):y
I0054 : <Switch module 1> Power off was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

5-124 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
poweron sw-module
Powers on the switch module. If you specify the diagnostic level, the switch
module is powered on with the diagnosis.
The specified diagnostic level is enabled for both the 1/10Gb LAN switch
module and the DCB switch module.

Syntax
poweron sw-module [<sw_no>] [-dl <diag_level>] [-F]

Privilege
Switch module privileges

Parameters
<sw_no>
Switch module number
You can specify a value from 1 to 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.
-dl <diag_level>
Diagnostic level
¢ standard: Standard
¢ full: Full
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To power on the switch module 1:
$ poweron sw-module 1
Confirm? (y/[n]):y
I0053 : <Switch module 1> Power on was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set sw-module led


Turns the LID lamps of switch modules on or off.

Syntax
set sw-module led [<sw_no>] -l <led_type> -t <led_on_off> [-F]

Commands That Can Be Executed From the CLI Console 5-125


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Switch module privilege

Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.
-l <led_type>
LED indicator type
lid: Identification LED indicator
-t <led_on_off>
LED indicator status
¢ on: Turns the LED indicator on.
¢ off: Turns the LED indicator off.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To turn on the LID lamp for switch module 1:
set sw-module led 1 -l lid -t on

To turn off the LID lamp for switch module 1:


set sw-module led 1 -l lid -t off

set sw-module maintenance-mode


Sets maintenance mode of the chassis when maintenance work for the switch
module is performed. Do not use this command for usual operation because
this command is used for maintenance work. If you set maintenance mode,
the remaining time for maintenance mode is set to 120 minutes.

Syntax
set sw-module maintenance-mode <sw_no> -m <mnt_mode> [-F]

Privilege
Switch module privileges

Parameters
<sw_no>

5-126 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Switch module number
You can specify a value from 1 to 2. You cannot specify multiple values.
-m <mnt_mode>
Maintenance mode
¢ enable: Sets maintenance mode.
¢ disable: Cancels maintenance mode.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set maintenance mode for switch module 1:
$ set sw-module maintenance-mode 1 -m enable
Confirm? (y/[n]):y
I0052 : <Switch module 1> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set sw-module mgmt-lan


Changes the management LAN settings for a switch module.

Syntax
set sw-module mgmt-lan <sw_no> [-i <ip_addr>] [-s <subnet_mask>] [-g
<default_gateway>] [-F]

Privilege
Network privilege

Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You cannot specify multiple values.
-i <ip_addr>
IP address
-s <subnet_mask>
Subnet mask
-g <default_gateway>
Default gateway
-F

Commands That Can Be Executed From the CLI Console 5-127


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To connect switch module 1 to the management LAN network:
set sw-module mgmt-lan 1 -i 192.168.0.10 -s 255.255.255.0 -g
192.168.0.1

set sw-module mgmt-v6 address


Sets the management LAN settings (IPv6) for a switch module.
You can set a static address. To set a static address, enter the following
items:
• IP address (IPv6)
• Prefix length
• Whether to enable use of the default gateway
• Default gateway

Syntax
set sw-module mgmt-v6 address <sw_no> -st <setting> [-i
<ip_address>] [-p <prefix_len>] [-gs <dgw_setting>] [-g
<default_gateway>] [-F]

Privilege
Network privilege

Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You cannot specify multiple values.
-st <setting>
Specify whether to enable use of a static address.
¢ enable: Enabled.
¢ disable: Disabled.
You cannot omit this parameter.
-i <ip_address>
IP address (IPv6)
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.

-p <prefix_len>
Prefix length

5-128 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify a value from 1 to 128.
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.

-gs <dgw_setting>
Specify whether to enable use of the default gateway (IPv6).
¢ enable: Enabled.
¢ disable: Disabled.
If you entered -st enable, this item is required. If you entered -st
disable, omit this parameter.
If you want to specify the default gateway (-g), specify enable.

-g <default_gateway>
Default gateway (IPv6)
If you entered -st enable or -gs enable, this item is required.
If you entered -st disable or -gs disable, or if you omitted -gs, omit
this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the static address for switch module management LAN 1 (IPv6) and
enable use of the default gateway:
set sw-module mgmt-v6 address 1 -st enable -i
fe80::200:87ff:feb2:c24 -p 64 -gs enable -g fe80::200:87ff:feb2:c20

Rules
• A duplication check is not performed for the specified address.
• For the default gateway, you can specify an address that is reachable
from the address for switch modules.
• You cannot set the loopback address (::1/128).

show sw-module firmware


Displays the firmware versions of switch modules.

Syntax
show sw-module firmware [<sw_no>]

Privilege
Switch module privilege

Commands That Can Be Executed From the CLI Console 5-129


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.

Execution example
To display the firmware version of switch module 1:
show sw-module firmware 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-104 Switch module firmware version

Displayed item Description


Slot Switch module number
This is a value 1 or 2.
Firmware version Firmware version
Displays the firmware version of the switch module.

show sw-module hardware


Displays the following hardware information for switch modules:
• Hardware information
• FRU information
• Sensor information

Syntax
show sw-module hardware [<sw_no>] [-h] [-f] [-s]

Privilege
Switch module privilege

Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.

5-130 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-h
Hardware information for the specified switch modules.
-f
FRU information for the specified switch modules.
-s
Sensor information for the specified switch modules.
You must specify at least one of -h, -f, and -s parameters.

Execution example
To display the firmware information for switch module 1:
show sw-module hardware 1 -h

Execution results
The following table shows the items that are displayed as the execution
results of this command.
Common displayed items (items displayed when -h, -f, or -s is specified)

Table 5-105 Switch module hardware information

Displayed item Description


Slot Switch module number
This is a value 1 or 2.
Regardless of the specified parameter (-h, -s, or -
f), the slot number for each switch module is
displayed first.

Hardware information displayed items (items displayed when -h is specified)

Table 5-106 Switch module

Displayed item Description


Product name Product name
Model name Model name
Serial number Serial number
Nameplate power [W] Rated power (W)

FRU information displayed items (items displayed when -f is specified)

Table 5-107 Board Information

Displayed item Description


Serial number Serial number

Commands That Can Be Executed From the CLI Console 5-131


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-108 Product Information

Displayed item Description


Product Name Product name
Part/Model Number Model name

Table 5-109 MultiRecord Information

Displayed item Description


Manufacture ID Code for Hitachi
Module Type 1 Module type code 1
Module Type 2 Module type code 2
Product Part/Model Number for Maintenance component code
Maintenance

Product ID IANA Product ID


Hardware Address MAC address for the hardware device

Sensor information displayed items (items displayed when -s is specified)

Table 5-110 Switch module sensor information

Displayed item Description


Temp Name and value of the thermal sensor for the
switch module

show sw-module maintenance-mode


Displays whether the switch module is performing maintenance work.
The following information is displayed:
• Maintenance mode setting
• Remaining time for maintenance mode
• Maintenance LAN's IP address

Syntax
show sw-module maintenance-mode [<sw_no>]

Privilege
Chassis privilege

5-132 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<sw_no>
Switch module number
You can specify a value from 1 to 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.

Execution example
To display maintenance mode for switch module 1:
$ show sw-module maintenance-mode 1
-- Switch module maintenance mode --
Slot : 1
Maintenance mode : on
Remaining time (min) : 120
IP address : 192.168.254.10
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-111 Switch module maintenance mode

Displayed item Description


Slot Switch module number
This is a value 1 or 2.
Maintenance mode Maintenance mode
• enable: Maintenance work is performed.
• disable: Maintenance work is not performed.
Remaining time (min) Remaining time for maintenance mode (minutes)
• 0-120: The remaining time for maintenance mode
(minutes)
• -----: Maintenance work is not performed.
IP address Maintenance LAN's IP address
• -----: Not set

show sw-module mgmt-lan


Displays the management LAN settings for switch modules.

Syntax
show sw-module mgmt-lan [<sw_no>]

Commands That Can Be Executed From the CLI Console 5-133


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Network privilege

Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.

Execution example
To display management LAN settings for switch module 1:
show sw-module mgmt-lan 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-112 Switch module management LAN setting

Displayed item Description


Slot Switch module number
This is a value 1 or 2.
IP address IP address
Subnetmask Subnet mask
Default gateway Default gateway

show sw-module mgmt-v6 setting


Displays the management LAN settings for switch modules.
The following information is displayed:
• IPv6 address setting information of switch modules
• Static addresses for switch modules

Syntax
show sw-module mgmt-v6 setting [<sw_no>]

Privilege
Network privilege

5-134 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.

Execution example
To display management LAN settings (IPv6) for switch module 1:
show sw-module mgmt-v6 setting 1

Execution results
Table 5-113 Switch module management LAN setting (IPv6)

Displayed item Description


Slot Switch module number
This is a value 1 or 2.

Table 5-114 IPv6 address setting

Displayed item Description


Allocation Address setting method
Displays the address allocation method.
Static address: Static address
Status Status
Whether the address settings are enabled
• enable: Enabled.
• disable: Disabled.
IP address IP address (IPv6)
Prefix len Prefix length
This is a value from 1 to 128.
Default gateway Default gateway (IPv6)

show sw-module status


Displays the following items that indicate the statuses of switch modules:
• Installation status
• Power supply status
• Operating status (booting, failure, or warning)
• LID lamp status

Commands That Can Be Executed From the CLI Console 5-135


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
show sw-module status [<sw_no>]

Privilege
Switch module privilege

Parameters
<sw_no>
Switch module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all switch modules.

Execution example
To display the status of switch module 1:
show sw-module status 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-115 Switch module status

Displayed item Description


Slot Switch module number
This is a value 1 or 2.
Install Whether the module is installed
Displays the installation status of the switch module.
• installed: The switch module is installed.
• not installed: The switch module is not installed.
Power Power supply status
Displays the power supply status.
• on: The switch module is powered on.
• off: The switch module is powered off.
• -----: The switch module is not installed.
Booting Booting status
Displays whether the switch module is currently being
initialized.
• on: The switch module is currently being
initialized.
• off: The switch module is not being initialized.
• -----: The switch module is not installed.

5-136 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Fail Failure status
Displays whether a failure occurred on the switch
module.
• normal: The status of the switch module is
normal.
• fail: A failure occurred on the switch module.
Check the details of the failure in the system
event log.
• -----: The switch module is not installed.
Warning Warning status
Displays whether a warning was issued for the switch
module.
• normal: The status of the switch module is
normal.
• warning: A warning was issued for the switch
module. Check the details of the warning in the
system event log.
• -----: The switch module is not installed.

Table 5-116 LED status

Displayed item Description


LED type LED indicator type
• Location Led: LID lamp (identification LED
indicator)
• -----: The switch module is not installed.
Light LED indicator status
• on: The LED indicator is lit.
• off: The LED indicator is unlit.
• -----: The switch module is not installed.

Commands for power supply management


This section describes the commands to confirm and change the power supply
settings for the system unit.

set power blade poweroff order


Sets the order in which server blades are to be powered off when power
consumption exceeds the power capacity. Specify all server blade slot
numbers from 1 to 15.
In an SMP configuration, this command sets the order in which primary
server blades are to be powered off. The order in which non-primary server

Commands That Can Be Executed From the CLI Console 5-137


Hitachi Compute Blade 2500 Series Management Module User Guide
blades are to be powered off does not affect the behavior of the non-primary
server blades but specify all server blade slot numbers in the -o parameter.

Syntax
set power blade poweroff order -o <blade_off_order> [-F]

Privilege
Chassis privilege

Parameters
-o <blade_off_order>
The order in which server blades are to be powered off when power
consumption exceeds the power capacity
Specify server blade slot numbers separated by commas. Specify slot
numbers in the order in which they are to be powered off, starting with
the first slot to be powered off.
You must enter all fifteen slot numbers from 1 to 15, and you cannot
specify a number twice.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the order in which server blades are to be powered off to 15, 14, 13,
12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1:
set power blade poweroff order -o
15,14,13,12,11,10,9,8,7,6,5,4,3,2,1 -F

set power capping


Changes the APC setting items for server blades.
In an SMP configuration, if you specify a primary server blade, the APC
setting items for all server blades constituting the SMP configuration are
changed. If you specify a non-primary server blade, the APC setting items are
changed but this setting change does not affect the behavior of the non-
primary server blade.

Syntax
set power capping -b <blade_no> [-a <blade_power_apc>] [-F]

Privilege
Chassis privilege

5-138 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-a <blade_power_apc>
APC
¢ enable: Limits the power consumption by using APC.
¢ disable: Does not limit the power consumption by using APC.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To limit the power consumption of server blade 1, by using APC:
set power capping -b 1 -a enable

Rules
• If you specify a non-primary server blade, the following warning message
appears and the setting values do not affect the behavior of the non-
primary server blade.
W0031 : <Blade X> Set data is not used. Specified blade is not
the primary blade of SMP. (X indicates the specified server
blade number.)
• You cannot execute this command for DCMI mode.

set power dcmi-mode


Sets DCMI mode for the entire server chassis.
DCMI mode is applied for server blades in the server chassis.
If you set DCMI mode, the upper limit for electric power consumption of
server blades is specified by the DCMI commands. If a server blade does not
support DCMI commands, the server blade will consume the rated power
consumption.

Syntax
set power dcmi-mode -m <dcmi_mode> [-F]

Privilege
Chassis privilege

Commands That Can Be Executed From the CLI Console 5-139


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-m <dcmi_mode>
Setting to enable or disable DCMI mode
¢ enable: Enable (change to DCMI mode)
¢ disable: Disable (change to APC mode)
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable DCMI mode
$ set power dcmi-mode -m enable -F
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set power power-expansion


Changes the settings for expanding the power capacity.

Syntax
set power power-expansion -e <expansion> [-F]

Privilege
Chassis privilege

Parameters
-e <expansion>
Power capacity expansion settings
¢ enable: Enables the power capacity expansion feature.
¢ disable: Disables the power capacity expansion feature.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable the power capacity expansion feature:
set power power-expansion -e enable

5-140 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set power ps-module
Changes the power settings.

Syntax
set power ps-module [-r <redundancy>] [-a1 <power_ac_recovery>] [-a2
<power_ac_recovery>] [-a3 <power_ac_recovery>] [-a4
<power_ac_recovery>] [-a5 <power_ac_recovery>] [-a6
<power_ac_recovery>] [-F]

Privilege
Chassis privilege

Parameters
-r <redundancy>
Power supply module redundancy
¢ n+n: N + N
¢ n+1: N + 1
-a1 <power_ac_recovery>
Power supply linkage settings for the power supply module
¢ enable: Links with the power supply for the power supply module.
¢ disable: Does not link with the power supply for the power supply
module.
-a2 <power_ac_recovery>
Power supply linkage settings for the power supply module
¢ enable: Links with the power supply for the power supply module.
¢ disable: Does not link with the power supply for the power supply
module.
-a3 <power_ac_recovery>
Power supply linkage settings for the power supply module
¢ enable: Links with the power supply for the power supply module.
¢ disable: Does not link with the power supply for the power supply
module.
-a4 <power_ac_recovery>
Power supply linkage settings for the power supply module
¢ enable: Links with the power supply for the power supply module.
¢ disable: Does not link with the power supply for the power supply
module.
-a5 <power_ac_recovery>
Power supply linkage settings for the power supply module

Commands That Can Be Executed From the CLI Console 5-141


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ enable: Links with the power supply for the power supply module.
¢ disable: Does not link with the power supply for the power supply
module.
-a6 <power_ac_recovery>
Power supply linkage settings for the power supply module
¢ enable: Links with the power supply for the power supply module.
¢ disable: Does not link with the power supply for the power supply
module.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the power supply module redundancy to N+N:
set power ps-module -r n+n

To disable the server blade power supply restoration operation even if power
is supplied to power supply module 1:
set power ps-module -a1 disable

show power ps-module


Displays the power settings.

Syntax
show power ps-module

Privilege
Chassis privilege

Parameters
None

Execution example
To display the power settings:
show power ps-module

Execution results
The following table shows the items that are displayed as the execution
results of this command.

5-142 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-117 Power supply setting

Displayed item Description


Redundancy Power supply module redundancy
• n+n: N + N
• n+1: N + 1

Table 5-118 Power supply AC recovery setting

Displayed item Description


Slot Power supply module number
This is a value from 1 to 6.
AC recovery Power supply linkage settings for the power supply
module
• enable: Linkage with the power supply for the
power supply module is enabled.
• disable: Linkage with the power supply for the
power supply module is disabled.

show power setting


Displays the power capacity expansion settings and power-capping settings
for the server blade, as shown below.
• Power capacity expansion settings
• DCMI mode
• APC mode
• The order in which server blades are to be powered off when power
consumption exceeds the power capacity
In an SMP configuration, the settings of Power Capping that runs on all server
blades constituting the SMP configuration are displayed for primary server
blades. For non-primary server blades, the setting values are shown in
parentheses. The values enclosed with parentheses do not affect the behavior
of the non-primary server blades.

Syntax
show power setting

Privilege
Chassis privilege

Parameters
None

Commands That Can Be Executed From the CLI Console 5-143


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the power capacity expansion settings and power-capping settings
for the server blade:
$ show power setting
-- Power setting --
Power capacity expansion : enable
DCMI mode : disable
-- Blade power setting --
Slot : 1
Accurate power control (APC) : enable
-- Blade power setting --
Slot : 2
Accurate power control (APC) : enable
(omitted)
-- Blade power setting --
Slot : 15
Accurate power control (APC) : enable
-- Order of blade to power off --
Slot : 1
Order : 1
-- Order of blade to power off --
Slot : 2
Order : 4
(omitted)
-- Order of blade to power off --
Slot : 15
Order : 5
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-119 Power setting

Displayed item Description


Power capacity expansion Power capacity expansion settings
• enable: The power capacity expansion feature
is enabled.
• disable: The power capacity expansion feature
is disabled.
DCMI mode DCMI mode
• enable: Indicates DCMI mode.
• disable: Indicates APC mode.

Table 5-120 Blade power setting

Displayed item Description


Slot Server blade number

5-144 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
This is a value from 1 to 15.
Accurate power control (APC) APC
• enable: Power consumption limitation by APC is
enabled.
• disable: Power consumption limitation by APC
is disabled.
In an SMP configuration, the values for non-primary
server blades are shown in parentheses. The values
enclosed with parentheses do not affect the
behavior of the non-primary server blades.

Tip: These items are displayed only for APC mode.

Table 5-121 Order of blade to power off

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Order The order in which server blades are to be powered
off when power consumption exceeds the power
capacity
Displays the order in which server blades are to be
powered off. You can specify a value from 1 to 15.
In an SMP configuration, the values for non-primary
server blades are shown in parentheses. The values
enclosed with parentheses do not affect the
behavior of the non-primary server blades.

show ps-module hardware


Displays the information about the hardware of power supply modules.
• Hardware information
Displayed if you specify the -h parameter.
• FRU information
Displayed if you specify the -f parameter.
• Sensor information
Displayed if you specify the -s parameter.

You need to specify at least one of the following parameters: -h, -f, and -s. If
you omit all the parameters, the power supply module information is not
displayed. You can specify all of the parameters. The information that you
specify by using the parameters is displayed for each power supply module,
in order of hardware information, FRU information, and sensor information.

Commands That Can Be Executed From the CLI Console 5-145


Hitachi Compute Blade 2500 Series Management Module User Guide
You can specify multiple power supply module numbers. If you do not specify
a number, the information of all power supply modules is displayed.

Syntax
show ps-module hardware [<ps-module_no>] [-h] [-f] [-s]

Privilege
Chassis privilege

Parameters
<ps-module_no>
Power supply module number
You can specify a value from 1 to 6. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all power supply modules.
-h
Displays the hardware information for the specified power supply
modules.
-f
Displays the FRU information for the specified power supply modules.
-s
Displays the sensor information for the specified power supply modules.

Execution example
To display the hardware information for power supply module 1:
$ show ps-module hardware 1 -h -f -s
-- Power supply module hardware information --
Slot : 1
-- Power supply module --
Nameplate power [W] : XXX
-- Power supply module FRU information --
-- Board Information --
Manufacture : XXXX
Product Name : XXXXXXXX
Serial Number : XXXXXXXX
-- Product Information --
Product Name : XXXXXXXX
Manufacture : XXXX
Product Version : XXXXXXXX
-- MultiRecord Information --
Manufacture ID : XXXXXXXX
Module Type 1 : XX
Module Type 2 : XX
Product Part/Model Number for Maintenance : XXXXXXXX
-- Power supply module sensor information --
-- Temp --
Inlet : XXXXXXXX
Outlet : XXXXXXXX

5-146 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-- Tachometer --
FAN : XXXXXXXX
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.
• Common displayed items (items displayed when -h, -f, or -s is specified)

Table 5-122 Power supply module hardware information

Displayed item Description


Slot Power supply module number
This is a value from 1 to 6.

• Hardware information displayed items (items displayed when -h is


specified)

Table 5-123 Power supply module

Displayed item Description


Nameplate power Rated power (W)
• ----- : The power supply module is not
installed.

• FRU information displayed items (items displayed when -f is specified)

Table 5-124 Board Information

Displayed item Description


Manufacture Manufacturer code
Product Name Product name
Serial Number Serial number

Table 5-125 Product Information

Displayed item Description


Product Name Product name
Manufacture Manufacturer code
Product Version Product version

Commands That Can Be Executed From the CLI Console 5-147


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-126 MultiRecord Information

Displayed item Description


Manufacture ID Code for Hitachi
Module Type 1 Module type code 1
Module Type 2 Module type code 2
Product Part/Model Number for Maintenance component code
Maintenance

• Sensor information displayed items (items displayed when -s is specified)

Table 5-127 Power supply module sensor information

Displayed item Description


Temp Lists the thermal sensor names and sensor
values for the power supply module
Tachometer Lists the rotation speed sensor names and
sensor values for the power supply module

show ps-module status


Displays the statuses of power supply modules.

Syntax
show ps-module status [<ps-module_no>]

Privilege
Chassis privilege

Parameters
<ps-module_no>
Power supply module number
You can specify a value from 1 to 6. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all power supply modules.

Execution example
To display the status of power supply module 1:
$ show ps-module status 1
-- Power supply module status --
Slot : 1
Install : installed
Power : On
Fail : Normal

5-148 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Warning : Normal
AC Input : 200[V]
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-128 Power supply module status

Displayed item Description


Slot Power supply module number
This is a value from 1 to 6.
Install Whether the power supply module is installed
• installed: The power supply module is installed.
• not installed: The power supply module is not
installed.
Power Power supply status of the module
• Off : The module is powered off.
• On : The module is powered on.
• -----: The module is not installed.
Fail Failure status of the module
• Normal : The status of the module is normal.
• FAIL : A failure occurred on the module.
• -----: The module is not installed.
Warning Warning status of the module
• Normal : The status of the module is normal.
• WARNING: A warning was issued for the
module.
• -----: The module is not installed.
AC Input AC input
• Unknown: The voltage is unknown.
• 200 (V): The voltage is 200 (V).
• None: There is no input.
• -----: The module is not installed.

Commands to manage fan modules


This section describes the commands to confirm the fan module settings.

Commands That Can Be Executed From the CLI Console 5-149


Hitachi Compute Blade 2500 Series Management Module User Guide
show fan-module status
Displays the statuses of fan modules.

Syntax
show fan-module status [<fan_no>]

Privilege
Chassis privilege

Parameters
<fan_no>
Fan module number
You can specify a value from 1 to 10. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all fan modules.

Execution example
To display the status of fan module 1:
show fan-module status 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-129 Fan module status

Displayed item Description


Slot Fan module number
This is a value from 1 to 10.
Install Whether the module is installed
• installed: The module is installed.
• not installed: The module is not installed.
Power Power supply status of the module
• off: The module is powered off.
• on: The module is powered on.
Fail Failure status of the module
• normal: The status of the module is normal.
• fail: A failure occurred on the module.
Tachometer(rpm) Rotation speed of the fan

5-150 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Commands for fan control module management
This section describes the commands to confirm and change the fan control
module settings.

show fan-control-module hardware


Displays the hardware information for fan control modules.
The following information is displayed:
• FRU information

Syntax
show fan-control-module hardware [<fan_control_no>] [-f]

Privilege
Chassis privilege

Parameters
<fan_control_no>
Fan control module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all fan control modules.
-f
FRU information for the specified fan control modules.

Execution example
To display the FRU information for a fan control module:
show fan-control-module hardware 1 -f

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-130 Fan control module hardware information

Displayed item Description


Slot Fan control module number
This is a value 1 or 2.

Commands That Can Be Executed From the CLI Console 5-151


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-131 Board Information

Displayed item Description


Manufacture Manufacturer code
Product Name Product name
Serial Number Serial number

Table 5-132 Product Information

Displayed item Description


Product Name Product name
Manufacture Manufacturer code
Product Version Product version

Table 5-133 MultiRecord Information

Displayed item Description


Manufacture ID Code for Hitachi
Module Type 1 Module type code 1
Module Type 2 Module type code 2
Product Part/Model Number for Maintenance component code
Maintenance

show fan-control-module status


Displays the statuses of fan control modules.
The following information is displayed:
• Installation status
• Power supply status
• Operating status (failure or warning)
• LED status

Syntax
show fan-control-module status [<fan_control_no>]

Privilege
Chassis privilege

Parameters
<fan_control_no>

5-152 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Fan control module number
You can specify a value 1 or 2. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all fan control modules.

Execution example
To display the status of fan control module 1:
show fan-control-module status 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-134 Fan control module status

Displayed item Description


Slot Fan control module number
This is a value 1 or 2.
Install Whether the module is installed
• installed: The module is installed.
• not installed: The module is not installed.
Power Power supply status of the module
• off: The module is powered off.
• on: The module is powered on.
Fail Failure status of the module
• normal: The status of the module is normal.
• fail: A failure occurred on the module.
Warning Warning status of the module
• normal: The status of the module is normal.
• fail: A warning was issued for the module.

Table 5-135 LED status

Displayed item Description


LED type LED indicator type
• PWR: Power LED indicator
• ALM: Alarm LED indicator
Light LED indicator status
• on: The LED indicator is lit.
• off: The LED indicator is unlit.
• blink: The LED indicator is blinking.
Color LED indicator color

Commands That Can Be Executed From the CLI Console 5-153


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• green: Green
• amber: Amber
• unknown: Information about the color of the LED
indicator could not be retrieved.
• -----: The LED indicator is unlit.

Commands to manage the LCD touch console


This section describes the commands to confirm and change the LCD touch
console settings.

clear lcd password


Initializes the LCD touch console password.

Syntax
clear lcd password [-F]

Privilege
Account privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To initialize the LCD touch console password:
$ clear lcd password
Confirm? (y/[n]):y
I0210 : Initializing a PIN for the LCD touch console was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

set lcd validity


Enables or disables the LCD touch console.

Syntax
set lcd validity -v <tc_valid> [-F]

5-154 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Chassis privilege

Parameters
-v <tc_valid>
Enables or disables the LCD touch console.
¢ enable: Enabled.
¢ disable: Disabled.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable the LCD touch console:
set lcd validity -v enable

show lcd setting


Displays information about the LCD touch console settings.

Syntax
show lcd setting

Privilege
Chassis privilege

Parameters
None

Execution example
To display information about the LCD touch console settings:
show lcd setting

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-136 LCD touch console setting

Displayed item Description


Validity Whether the LCD touch console is enabled

Commands That Can Be Executed From the CLI Console 5-155


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• enable: Enabled.
• disable: Disabled.

Commands for user management


This section describes the commands to confirm and change information for
user management.

add user account


Adds an account.
Specify an unregistered account name. You cannot specify an account name
that is already registered. Before creating an account, create a role to be
used. If you do not specify a password, you will be asked to enter a
password. (See the execution example below.)

Syntax
add user account -i <user_id> [-s <status>] -r <role_id> [-l
<language>] [-c <cli_prompt>] [-t <logout_time>] [-p <password>] [-F]

Privilege
Account privilege

Parameters
-i <user_id>
Account name
Specify an account name. You can use a maximum of 31 alphanumeric
characters, hyphens (-), periods (.), and underscores (_). You can
specify only an alphanumeric character for the first character. You cannot
omit this parameter.
-s <status>
Status
Specifies whether to enable the account. If you enable the account, the
account can be used to log in. If you disable the account, the account
cannot be used to log in.
¢ enable: Enabled.
¢ disable: Disabled.
If you omit this parameter, the account is enabled.
-r <role_id>
Role name
Sets the name of the role to be assigned to the account.

5-156 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
You can use a maximum of 31 alphanumeric characters. Specify an
alphabetic character for the first character. You cannot omit this
parameter.
-l <language>
Language.
Specify the language to be used when a user logs in with this account.
You can select Japanese, English, or the language specified by the system
settings. If you select Japanese or English, the selected language will be
used regardless of the system settings. If you select the language
specified by the system settings, the system language set by using the
command set language system will be used.
¢ japanese: Japanese
¢ english: English
¢ system: Uses the language specified by the system settings
If you omit this parameter, the language specified by the system
settings is set.
-c <cli_prompt>
CLI console prompt
Specify the display format of the CLI console prompt. You can select to
display either "$" (fixed) or "chassis-ID(management-module-slot-
number)$".
If you are using the CLI to manage multiple systems units, by displaying
the chassis ID in the prompt, you can identify the system unit on which
you are operating.
¢ $: "$" fixed
¢ chassis-ID(slot-number)$: "chassis-ID(management-module-slot-
number)$"
If you omit this parameter, "chassis-ID(management-module-slot-
number)$" is set as the display format.
-t <logout_time>
Session timeout period (in minutes).
Specify the maximum period of inactivity after which the user will be
automatically logged out of the CLI console. You can specify a value from
0 to 1,440 minutes for the session timeout period. If you specify 0
minutes, automatic logout is not performed. For the Web console,
sessions are automatically closed after 30 minutes regardless of the value
of this setting.
¢ 0: Automatic logout is not performed.
¢ 1 to 1440: Maximum period of inactivity (in minutes) after which
automatic logout is performed.
If you omit this parameter, the session timeout period is set to 5 minutes.
-p <password>
Password

Commands That Can Be Executed From the CLI Console 5-157


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify the password to be used in login. The value of this setting is not
displayed in the account information. For this reason, store this password
in a safe place. You can specify a maximum of 31 characters.
However, you cannot use space characters.
If you do not specify a password, you will be asked to enter a password.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To add the account name accountname with a password specified in the
command line:
$ add user account -i accountname -s enable -r chassis -l japanese -
c $ -t 10 -p password
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To add the account name accountname without specifying a password in the


command line:
$ add user account -i accountname -s enable -r chassis -l japanese -
c $ -t 10
Confirm? (y/[n]):y
Password : ... Enter the password. The entered characters are
not displayed.
Retype password : ... Re-enter the password. The entered characters
are not displayed.
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
To assign the privileges for the server blades constituting an SMP
configuration to the account, specify the role to which the privileges for all
server blades constituting the SMP configuration are assigned.

add user role


Adds a role.
Specify an unregistered role name. You cannot specify a name that is already
registered. Specify all privileges to be assigned.

Syntax
add user role -i <role_id> [-b <blade_no>] [-s <switch_no>] [-n] [-
c] [-a] [-r] [-k] [-F]

5-158 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Account privilege

Parameters
-i <role_id>
Role name
Specify the role name to be added. You can use a maximum of 31
alphanumeric characters. Specify an alphabetic character for the first
character. You cannot omit this parameter.
-b <blade_no>
Server blade privileges
Specify the server blade privileges to be assigned to the role. Specify the
number of the server blade for which privileges are to be assigned to the
role.
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all, privileges for all server blades are assigned to the role.
If you specify the -b parameter, you must either specify a number or all
after it. If you omit the -b parameter, the role is not assigned privileges
for any of the server blades.
-s <switch_no>
Switch module privileges.
Specify the switch module privileges to be assigned to the role. Specify
the number of the switch module for which the privileges are to be
assigned to the role.
You can specify a value 1 or 2. You can specify multiple values.
If you specify all, privileges for all switch modules are assigned to the
role. If you specify the -s parameter, you must specify a number or all
after it. If you omit the -s parameter, the role is not assigned privileges
for any of the switch modules.
-n
Network privilege
Specify whether to assign the network privilege to the role. If you specify
this parameter, the network privilege is assigned to the role. If you omit
this parameter, the network privilege is not assigned to the role.
-c
Server chassis privilege
Specify whether to assign the server chassis privilege to the role. If you
specify this parameter, the server chassis privilege is assigned to the role.
If you omit this parameter, the server chassis privilege is not assigned to
the role.
-a
Account privilege

Commands That Can Be Executed From the CLI Console 5-159


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify whether to assign the account privilege to the role. If you specify
this parameter, the account privilege is assigned to the role. If you omit
this parameter, the account privilege is not assigned to the role.
-r
Read privilege only.
If you specify this parameter, only the read privilege is assigned to the
role. If you omit this parameter, read, setting, and operation privileges
are assigned to the role.
-k
Denies permission to execute remote consoles and OS consoles.
Specify this parameter to deny permission to execute remote consoles
and OS consoles. If you specify this parameter, the role is not allowed to
execute the remote consoles and OS consoles of server blades even if the
role has the server blade privileges for the server blades. If you omit this
parameter, the role is allowed to execute the remote consoles and OS
consoles of the server blades for which server blade privileges are
assigned to the role.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To create the role bladeandchassis and assign it reading, setting, and
operation privileges for all server blades and for the server chassis:
$ add user role -i bladeandchassis -b all -c
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To create the role bladereadonly and assign it only read privileges for server
blades 1 to 3:
$ add user role -i bladereadonly -b 1-3 -r
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
When server blades are in an SMP configuration, assign the privileges for all
server blades constituting the SMP configuration to the role.

change-password user account


Changes the password for an account.

5-160 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify an account name that is already registered. Change the password for
the specified account. If you do not enter a password, you will be asked to
enter a password. (See the execution example below.)

Syntax
change-password user account -i <user_id> [-p <password>] [-F]

Privilege
Account privilege
Users who do not have the account privilege can change the password for
their own account only.

Parameters
-i <user_id>
Account name
Specify the name of the account whose password is to be changed. You
can use a maximum of 31 alphanumeric characters, hyphens (-), periods
(., and underscores (_). You can specify only an alphanumeric character
for the first character. You cannot omit this parameter.
-p <password>
Password
Specify the password to be used for login. The value of this setting is not
displayed in the account information. For this reason, store this password
in a safe place. You can specify a maximum of 31 characters.
If you do not specify a password, you will be asked to enter a password.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. If you do not enter a password, you will be asked
to enter a password even if you specify -F.

Execution example
To change the password for the account accountname with a password
specified in the command line:
$ change-password user account -i accountname -p password
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To change the password for an account accountname without specifying a


password in the command line:
$ change-password user account -i accountname
Confirm? (y/[n]):y
Old password : ... Enter the old password. The entered characters
are not displayed.

Commands That Can Be Executed From the CLI Console 5-161


Hitachi Compute Blade 2500 Series Management Module User Guide
New Password : ... Enter a new password. The entered characters
are not displayed.
Retype password : ... Re-enter the new password. The entered
characters are not displayed.
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

clear user ldap


Initializes the LDAP settings. Initializes all LDAP server, LDAP directory
search, and LDAP group authentication settings.

Syntax
clear user ldap [-F]

Privilege
Account privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To initialize the LDAP settings:
clear user ldap

delete user account


Deletes an account created by the user. You cannot delete an account that is
predefined by the system.
Specify a user name that is already registered. Delete the specified account.

Syntax
delete user account -i <user_id> [-F]

Privilege
Account privilege

Parameters
-i <user_id>
Account name

5-162 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify the name of the account to be deleted. You can use a maximum
of 31 alphanumeric characters, hyphens (-), periods (., and underscores
(_). You can specify only an alphanumeric character for the first
character. You cannot omit this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To delete the account accountname:
$ delete user account -i accountname
Confirm? (y/[n]):y
I0027 : Deleting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

delete user role


Deletes a role.
Specify a role name that is already registered. Delete the specified role. You
cannot delete a role that is used by an account.

Syntax
delete user role -i <role_id> [-F]

Privilege
Account privilege

Parameters
-i <role_id>
Role name
Specify the name of the role to be deleted You can use a maximum of 31
alphanumeric characters. Specify an alphabetic character for the first
character. You cannot omit this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To delete the role rolename:
$ delete user role -i rolename
Confirm? (y/[n]):y
I0027 : Deleting was completed.

Commands That Can Be Executed From the CLI Console 5-163


Hitachi Compute Blade 2500 Series Management Module User Guide
S0002 : Command succeeded.
S0000 : Command was finished.
$

disconnect user session


Closes a session established by a user logged in to the management module.

Syntax
disconnect user session -i <user_ses_id> [-F]

Privilege
Account privilege

Parameters
-i <user_ses_id>
Session ID.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To close the user session whose session ID is 107170000:
disconnect user session -i 107170000

modify user account


Changes the settings for an account.
Specify an account name that is already registered. Change the settings for
the specified account. When you change settings, changes to the settings for
language and CLI console prompt, are applied to the CLI console to which the
user is currently logged in. When using the Web console, to apply the
changed language settings, you need to log out. You can use the changed
password and session timeout period the next time you log in. You cannot
change the status or role of an account that is currently logged in. You cannot
change the status or role name for your own account.

Syntax
modify user account -i <user_id> [-s <status>] [-r <role_id>] [-l
<language>] [-c <cli_prompt>] [-t <logout_time>] [-p <password>] [-e
<expired_login>] [-F]

Privilege
Account privilege

5-164 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Users who do not have the account privilege can change the password for
their own account only.

Parameters
-i <user_id>
Account name
Specify the name of the account whose password is to be changed. You
can use a maximum of 31 alphanumeric characters, hyphens (-), periods
(., and underscores (_). You can specify only an alphanumeric character
for the first character. You cannot omit this parameter.
-s <status>
Status
Specify whether to enable the account. If you enable the account, the
account can be used to log in. If you disable the account, the account
cannot be used to log in. If you disable the account, you can temporarily
terminate the account and do not need to delete the account.
¢ enable: Enabled.
¢ disable: Disabled.
If you omit this parameter, the status is not changed. You cannot change
the status of your own account.
-r <role_id>
Role name
You can use a maximum of 31 alphanumeric characters. Specify an
alphabetic character for the first character. If you omit this parameter,
the role name is not changed. You cannot change the role name for your
own account.
-l <language>
Language.
Displays the language used when a user logs in with this account. You can
select Japanese, English, or the language specified by the system
settings. If you select Japanese or English, the selected language is used
regardless of the system settings. If you select the language specified by
the system settings, the system language set by using the command set
language system will be used.
¢ japanese: Japanese
¢ english: English
¢ system: Uses the language specified by the system settings
If you omit this parameter, the language is not changed.
-c <cli_prompt>
CLI console prompt
Specify the display format of the CLI console prompt. The prompt displays
in either of the following formats: "$" (fixed) and "chassis-
ID(management-module-slot-number)$".

Commands That Can Be Executed From the CLI Console 5-165


Hitachi Compute Blade 2500 Series Management Module User Guide
If you are using the CLI to manage multiple systems units, by displaying
the chassis ID in the prompt, you can identify the system unit on which
you are operating.
¢ $: "$" fixed
¢ chassis-ID(slot-number)$: "chassis-ID(management-module-slot-
number)$"
The actual chassis ID and slot number will be displayed in the prompt.
The space character at the end of the chassis ID will not be displayed
in the prompt.
If you omit this parameter, the display format of the CLI console prompt
will not be changed.
-t <logout_time>
Session timeout period (in minutes).
Specify the maximum period of inactivity after which the user will be
automatically logged out of the CLI console. You can specify a value from
0 to 1,440 minutes for the session timeout period. If you specify 0
minutes, automatic logout is not performed. For the Web console,
sessions are automatically closed after 30 minutes regardless of the value
of this setting.
¢ 0: Automatic logout is not performed.
¢ 1 to 1440: Maximum period of inactivity (in minutes) after which
automatic logout is performed.
If you omit this parameter, the session timeout period is set to 5 minutes.
-e <expired_login>
Change of the expired password
Set the operation when the password expires. You can enable this
parameter regardless of whether the password has expired.
¢ enable: Can change the expired password to log in.
¢ disable: Cannot log in.
-p <password>
Password
Specify the password to be used for login. The value of this setting is not
displayed in the account information. For this reason, store this password
in a safe place. You can specify a maximum of 31 characters.
If you omit this parameter, the password is not changed.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To make the account accountname temporarily unavailable:
$ modify user account -i accountname -s disable
Confirm? (y/[n]):y

5-166 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To change the CLI prompt to "chassis-ID(management-module-slot-number)


$" and disable automatic logout during periods of inactivity:
$ modify user account -i accountname -c chassis -t 0
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
• To assign the privileges for the server blades constituting an SMP
configuration to the account, specify the role to which the privileges for all
server blades constituting the SMP configuration are assigned.

modify user role


Changes the settings for a role.
Specify a role name that is already registered. Change the settings for the
specified role. Specify all privileges to be assigned to the role after the
changing the settings. You cannot change a role that is used by an account.

Syntax
modify user role -i <role_id> [-b <blade_no>] [-s <switch_no>] [-n]
[-c] [-a] [-r] [-k] [-F]

Privilege
Account privilege

Parameters
-i <role_id>
Role name
Specify the name of the role to be changed. You can use a maximum of
31 alphanumeric characters. Specify an alphabetic character for the first
character. You cannot omit this parameter.
-b <blade_no>
Server blade privileges
Specify the server blade privileges to be assigned to the role. Specify the
number of the server blade for which privileges are to be assigned to the
role.
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all, privileges for all server blades are assigned to the role.
If you specify the -b parameter, you must either specify a number or all

Commands That Can Be Executed From the CLI Console 5-167


Hitachi Compute Blade 2500 Series Management Module User Guide
after it. If you omit the -b parameter, the role is not assigned privileges
for any of the server blades.
-s <switch_no>
Switch module privileges
Specify the switch module privileges to be assigned to the role. Specify
the number of the switch module for which the privileges are to be
assigned to the role.
You can specify a value 1 or 2. You can specify multiple values.
If you specify all, privileges for all switch modules are assigned to the
role. If you specify the -s parameter, you must specify a number or all
after it. If you omit the -s parameter, the role is not assigned privileges
for any of the switch modules.
-n
Network privilege
Specify whether to assign the network privilege to the role. If you specify
this parameter, the network privilege is assigned to the role. If you omit
this parameter, the network privilege is not assigned to the role.
-c
Server chassis privilege
Specify whether to assign the server chassis privilege to the role. If you
specify this parameter, the server chassis privilege is assigned to the role.
If you omit this parameter, the server chassis privilege is not assigned to
the role.
-a
Account privilege
Specify whether to assign the account privilege to the role. If you specify
this parameter, the account privilege is assigned to the role. If you omit
this parameter, the account privilege is not assigned to the role.
-r
Read privilege only.
If you specify this parameter, only the read privilege is assigned to the
role. If you omit this parameter, read, setting, and operation privileges
are assigned to the role.
-k
Denies permission to execute remote consoles and OS consoles.
Specify this parameter to deny permission to execute remote consoles
and OS consoles. If you specify this parameter, the role is not allowed to
execute the remote consoles and OS consoles of server blades even if the
role has the server blade privileges for the server blades. If you omit this
parameter, the role is allowed to execute the remote consoles and OS
consoles of the server blades for which server blade privileges are
assigned to the role.
-F

5-168 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To assign the operation privilege for all server blades and for the server
chassis to the role bladeandchassis:
$ modify user role -i bladeandchassis -b all -c
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
When server blades are in an SMP configuration, assign the privileges for all
server blades constituting the SMP configuration to the role.

set user ldap group


Sets up the LDAP group authentication. This command does not change the
settings for parameters that are not specified.

Syntax
set user ldap group [-a <group_auth>] [-m <ldap_member_attr>] [-g0
<ldap_group_dn>] [-r0 <group_role>] [-g1 <ldap_group_dn>] [-
r1<group_role>] [-g2 <ldap_group_dn>] [-r2<group_role>] [-g3
<ldap_group_dn>] [-r3<group_role>] [-g4 <ldap_group_dn>] [-
r4<group_role>] [-dg <dynamic_dn>] [-df <dynamic_filter>] [-
dr<dynamic_role>] [-F]

Privilege
Account privilege

Parameters
-a <group_auth>
Authentication method
¢ none: Group authentication is not performed.
¢ static: Static group
¢ dynamic: Dynamic group
-m <ldap_member_attr>
Group member attribute
You can use from 1 to 64 ASCII characters. You cannot use a space
character for the first and last characters. You can use alphanumeric
characters (uppercase A to Z, lowercase a to z, and 0 to 9). Note,
however, that the first character must be an alphabetic character.

Commands That Can Be Executed From the CLI Console 5-169


Hitachi Compute Blade 2500 Series Management Module User Guide
If you specify only space characters, an empty string is set.
-g0 <ldap_group_dn>
DN of the group whose login is to be permitted (1st)
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, the DN of the applicable group will
be deleted.
-r0 <group_role>
Role of the group DN (1st)
¢ user-entry: Uses the user entry role.
¢ role-name: Uses a role that is registered in the management module.
(Specify one role name.)
-g1 <ldap_group_dn>
DN of the group whose login is to be permitted (2nd).
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, the DN of the applicable group will
be deleted.
-r1 <group_role>
Role of the group DN (2nd)
¢ user-entry: Uses the user entry role.
¢ role-name: Uses a role that is registered in the management module.
(Specify one role name.)
-g2 <ldap_group_dn>
DN of the group whose login is to be permitted (3rd).
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, the DN of the applicable group will
be deleted.
-r2 <group_role>
Role of the group DN (3rd)
¢ user-entry: Uses the user entry role.
¢ role-name: Uses a role that is registered in the management module.
(Specify one role name.)
-g3 <ldap_group_dn>
DN of the group whose login is to be permitted (4th).
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, the DN of the applicable group will
be deleted.

5-170 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-r3 <group_role>
Role of the group DN (4th)
¢ user-entry: Uses the user entry role.
¢ role-name: Uses a role that is registered in the management module.
(Specify one role name.)
-g4 <ldap_group_dn>
DN of the group whose login is to be permitted (5th).
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, the DN of the applicable group will
be deleted.
-r4 <group_role>
Role of the group DN (5th)
¢ user-entry: Uses the user entry role.
¢ role-name: Uses a role that is registered in the management module.
(Specify one role name.)
-dg <dynamic_dn>
Search DN for the dynamic group
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, an empty string is set to the search
DN for the dynamic group.
-df <dynamic_filter>
Search filter for the dynamic group
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, an empty string is set to the search
filter for the dynamic group.
-dr <dynamic_role>
Role of the dynamic group
¢ user-entry: Uses the user entry role.
¢ role-name: Uses a role that is registered in the management module.
(Specify one role name.)
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set up the LDAP group authentication:
set user ldap group -m xxxxx -g0 xxxxx

Commands That Can Be Executed From the CLI Console 5-171


Hitachi Compute Blade 2500 Series Management Module User Guide
set user ldap search
Sets up the functionality for searching the LDAP directory. This command
does not change the settings for parameters that are not specified.

Syntax
set user ldap search [-b <ldap_base_dn>] [-l <ldap_login_attr>] [-r
<ldap_role_attr>] [-f <referral>] [-F]

Privilege
Account privilege

Parameters
-b <ldap_base_dn>
Base DN
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, an empty string is set.
-l <ldap_login_attr>
Login ID attribute
You can use from 1 to 64 ASCII characters. You cannot use a space
character for the first and last characters. You can use alphanumeric
characters (uppercase A to Z, lowercase a to z, and 0 to 9). Note,
however, that the first character must be an alphabetic character.
If you specify only space characters, an empty string is set.
-r <ldap_role_attr>
Role attribute
You can use from 1 to 64 ASCII characters. You cannot use a space
character for the first and last characters. You can use alphanumeric
characters (uppercase A to Z, lowercase a to z, and 0 to 9). Note,
however, that the first character must be an alphabetic character.
If you specify only space characters, an empty string is set.
-f <referral>
Number of referrals
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set up the functionality for searching the LDAP directory:
set user ldap search -b basedn -l loginattr -r roleattr

5-172 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set user ldap server
Sets up the LDAP server connection information. This command does not
change the settings for parameters that are not specified.

Syntax
set user ldap server [-v <ldap_valid>] [-u <user_auth>] [-h0
<ldap_hostname>] [-h1 <ldap_hostname>] [-h2 <ldap_hostname>] [-p
<ldap_port>] [-b <ldap_bind_dn>] [-w <ldap_password>] [-F]

Privilege
Account privilege

Parameters
-v <ldap_valid>
Enables or disables use of LDAP.
¢ enable: Enables use of LDAP.
¢ disable : Disables use of LDAP.
-u <user_auth>
User authentication method
¢ ldap: Uses only the LDAP server for authentication.
¢ local: Local and LDAP servers are used for authentication.
-h0 <ldap_hostname>
IP address for the LDAP server (1st).
This item is an FQDN, IPv4 address, or IPv6 address (a maximum of 127
characters).
A space character cannot be used for the first or last characters. For
FQDN, this item consists of alphanumeric characters (uppercase A to Z,
lowercase a to z, and 0 to 9), hyphens (-), and periods (.).
If you specify only space characters, the IP address of the applicable
server will be deleted.
-h1 <ldap_hostname>
IP address for the LDAP server (2nd).
This item is an FQDN, IPv4 address, or IPv6 address (a maximum of 127
characters).
A space character cannot be used for the first or last characters. For
FQDN, this item consists of alphanumeric characters (uppercase A to Z,
lowercase a to z, and 0 to 9), hyphens (-), and periods (.).
If you specify only space characters, the IP address of the applicable
server will be deleted.
-h2 <ldap_hostname>
IP address for the LDAP server (3rd).

Commands That Can Be Executed From the CLI Console 5-173


Hitachi Compute Blade 2500 Series Management Module User Guide
This item is an FQDN, IPv4 address, or IPv6 address (a maximum of 127
characters).
A space character cannot be used for the first or last characters. For
FQDN, this item consists of alphanumeric characters (uppercase A to Z,
lowercase a to z, and 0 to 9), hyphens (-), and periods (.).
If you specify only space characters, the IP address of the applicable
server will be deleted.
-p <ldap_port>
Port number for the LDAP server.
Specify a value from 1 to 65535.
-b <ldap_bind_dn>
Bind DN for the LDAP server.
You can use from 1 to 256 ASCII characters. You cannot use a space
character for the first and last characters.
If you specify only space characters, anonymous binding is enabled. If
you specify a character string, anonymous binding is disabled.
-w <ldap_password>
Bind password
You can use from 1 to 32 ASCII characters. You can use space characters.
If you do not specify a password after -w, data is registered without using
a bind password.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set an LDAP server (0th):
set user ldap server -v enable -h0 xxx.xxx.xxx.xxx -p 20001 -b
xxxxxxxx -w pass

To disable use of the LDAP server:


set user ldap server -v disable

set user password policy


Sets the password policy.
Set the following items:
• Management of password expiration dates
• Password expiry period (day)
• Operation when the password expires.
The operation when the password expires is either of the following two types:
(1) A user cannot log in

5-174 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
The management module disconnects the console without allowing login.
Note that a user who has the account privilege can change the password
to log in.
(2) A user can change the expired password to log in.
When a user attempts to log in, a window for changing the password
appears. After changing the password, the user can log in.

Syntax
set user password policy [-m <management>] [-p <expiry_period>] [-e
<expired_login>] [-F]

Privilege
Account privilege

Parameters
-m <management>
Management of password expiration dates
Whether to set the expiration date for a password to control availability of
login or to enable login without any conditions is displayed.
¢ enable: Sets the expiration date for a password to control availability
of login.
¢ disable: Enables login without any conditions.
If you omit this parameter, the setting value is not changed.
-p <expiry_period>
Password expiry period (day)
Specify a value from 1 to 365.
¢ 1-365: Password expiry period (day)
If you enable management of password expiration dates, you cannot
omit this parameter.
If you disable management of password expiration dates, the
specified value is not applied even if you specify a value.
If management of password expiration dates is enabled, the setting
value is not changed if you omit this parameter.
-e <expired_login>
Operation when the password expires.
¢ enable: Can change the expired password to log in.
¢ disable: Cannot log in.
You can omit this parameter regardless of whether management of
password expiration dates is enabled or disabled.
If management of password expiration dates is disabled, the specified
value is not applied even if you specify a value.

Commands That Can Be Executed From the CLI Console 5-175


Hitachi Compute Blade 2500 Series Management Module User Guide
If management of password expiration dates is enabled, the setting value
is not changed if you omit this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the password expiry period to 60 days and to specify the setting so
that the password is changed during login when the password expires:
$ set user password policy -m enable -p 60 -e enable
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
If you enable management of password expiration dates, the expiration date
of each account is set as follows: from the time when the password is set for
the account to the number of days set for the password expiry period.
If you change the value of the password expiry period (day), the expiration
date of each account is set as follows: from the time when the password is
set for the account to the number of days set for the password expiry period.
Even if login is disabled when the password expires, a user who has the
account privilege can log in by changing the password during login.
For users whose last updated time of the password is not set, the time when
management of password expiration dates is enabled is set as the last
updated time of the password.

show user account


Displays the configuration information for the specified account. If you do not
specify an account name, configuration information for all accounts will be
displayed.

Syntax
show user account [-i <user_id>]

Privilege
Account privilege
Users who do not have the account privilege can view information for their
own account only.

5-176 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-i < user_id >
Account name
Specify the name of the account whose configuration information is to be
displayed. If you do not specify an account name, configuration
information for all accounts will be displayed. Users who do not have the
account privilege can view information for their own account only.
You can use a maximum of 31 alphanumeric characters, hyphens (-),
periods (., and underscores (_). You can specify only an alphanumeric
character for the first character.

Execution example
To view information about the account abcd:
$ show user account -i abcd
-- User account --
User ID : abcd (Account name: abcd)
Status : enable (Status: Enable)
Role : rolename (Role name: rolename)
Language : japanese (Language: Japanese)
CLI prompt : $ (CLI prompt: Fixed to "$")
CLI Inactive Time (min) : 10
-- Password information --
Password remaining days : 10 (10 days remain until the
password expiration date.)
Change expired password : disable (Login is disabled when the
password expires.)
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-137 User account

Displayed item Description


User ID Account name
Displays the account name. This item consists of a
maximum of 31 alphanumeric characters, hyphens (-),
periods (.), and underscores (_). Only an alphanumeric
character can be specified for the first character.
Status Status
Whether the account is enabled If the account is
enabled, it can be used to log in. If the account is
disabled, it cannot be used to log in.
• enable: Enabled.
• disable: Disabled.

Commands That Can Be Executed From the CLI Console 5-177


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Role Role name
Displays the name of the role assigned to the account.
The maximum length is 31 alphanumeric characters.
Language Language
Displays the language used when a user logs in with this
account. You can select Japanese, English, or the
language specified by the system settings. If you select
Japanese or English, the selected language is used
regardless of the system settings. If you select the
language specified by the system settings, the system
language set by using the command set language
system will be used.
• japanese: Japanese
• english: English
• Follows the system settings: Uses the language
specified by the system settings
CLI prompt CLI console prompt
Specify the display format of the CLI console prompt.
The prompt displays in either of the following formats:
"$" (fixed) and "chassis-ID(management-module-slot-
number)$".
• $: "$" fixed
• chassis-ID(slot-number)$: "chassis-
ID(management-module-slot-number)$"
The actual chassis ID and slot number will be
displayed in the prompt. The space character at the
end of the chassis ID will not be displayed in the
prompt.
CLI Inactive Time (min) Session timeout period (in minutes)
Specify the maximum period of inactivity after which the
user will be automatically logged out of the CLI console.
The session timeout period is a value from 0 to 1440
minutes If 0 minutes are specified, automatic logout is
not performed. For the Web console, sessions are
automatically closed after 30 minutes regardless of the
value of this setting.
• 0: Automatic logout is not performed.
• 1 to 1440: Maximum period of inactivity (in
minutes) after which automatic logout is performed.

Table 5-138 Password information

Displayed item Description


Password remaining days Password expiry period (remaining days)
The number of days until the last day on which you can
use the current password to log in is displayed.

5-178 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• 0-365: The number of days until the password
expiration date (0 is displayed if the password
expires at 24:00 on that day.)
• expired: The password has expired.
• infinite: The password can be used for infinite time.
• -----: The account status is invalid.
Change expired password Change of the expired password
The operation for login when the password expires is
displayed. You can enable this parameter regardless of
whether the password has expired.
• enable: Can change the expired password to log in.
• disable: Cannot log in.
• -----: The account status is invalid.

show user ldap


Displays LDAP settings.

Syntax
show user ldap

Privilege
Account privilege

Parameters
None

Execution example
To display LDAP settings:
show user ldap

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-139 Connection setting

Displayed item Description


LDAP Whether LDAP is enabled
• enable: Enables use of LDAP.
• disable: Disables use of LDAP.

Commands That Can Be Executed From the CLI Console 5-179


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Authentication User authentication method
• ldap: Only the LDAP server is used for
authentication.
• local: Local and LDAP servers are used for
authentication.
LDAP server IP address for the LDAP server
A maximum of three IP addresses can be registered.
This item is an FQDN, IPv4 address, or IPv6 address (a
maximum of 127 characters).
A space character cannot be used for the first or last
characters.
For FQDN, this item consists of alphanumeric
characters (uppercase A to Z, lowercase a to z, and 0
to 9), hyphens (-), and periods (.).
Port number Port number for the LDAP server
Specify a value from 1 to 65535.
Bind DN Bind DN for the LDAP server
This item consists of 1 to 256 ASCII characters.
If space characters are displayed, anonymous binding
is enabled. If a character string is displayed,
anonymous binding is disabled.

Table 5-140 Directory search setting

Displayed item Description


Base DN Base DN
This item consists of 1 to 256 ASCII characters. You
cannot use a space character for the first and last
characters.
Login attribute Login ID attribute
You can use from 1 to 64 ASCII characters. You cannot
use a space character for the first and last characters.
You can use alphanumeric characters (uppercase A to
Z, lowercase a to z, and 0 to 9). Note, however, that
the first character must be an alphabetic character.
Role attribute Role attribute
You can use from 1 to 64 ASCII characters. You cannot
use a space character for the first and last characters.
You can use alphanumeric characters (uppercase A to
Z, lowercase a to z, and 0 to 9). Note, however, that
the first character must be an alphabetic character.

Timeout [sec] Search timeout period (in seconds)


This item is not supported.

Referral Number of referrals

5-180 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-141 Group authentication setting

Displayed item Description

Group authentication Authentication method


• none: Group authentication is not performed.
• static: Static group
• dynamic: Dynamic group
Member attribute Group member attribute
You can use from 1 to 64 ASCII characters. You
cannot use a space character for the first and last
characters. You can use alphanumeric characters
(uppercase A to Z, lowercase a to z, and 0 to 9).
Note, however, that the first character must be an
alphabetic character.
Group DN DN of the groups whose login is to be permitted.
A maximum of five DNs can be registered. This item
consists of 1 to 256 ASCII characters. You cannot use
a space character for the first and last characters.

Group role Role of the group DN


A maximum of five DNs can be registered.
• user-entry: The user entry role is used.
• role-name: A role whose name is registered in
the management module is used.

Dynamic group DN Search DN for the dynamic group


This item consists of 1 to 256 ASCII characters. A
space character cannot be used for the first or last
characters. If only space characters are specified, the
search DN for the dynamic group is deleted.

Dynamic group filter Search filter for the dynamic group


This item consists of 1 to 256 ASCII characters. A
space character cannot be used for the first or last
characters. If only space characters are specified, the
search filter for the dynamic group is deleted.

Dynamic group role Role of the dynamic group


• user-entry: The user entry role is used.
• role-name: A role whose name is registered in
the management module is used.

show user password policy


Displays the password policy.
The following items are displayed:
• Management of password expiration dates
• Password expiry period (day)
• Operation when the password expires.

Commands That Can Be Executed From the CLI Console 5-181


Hitachi Compute Blade 2500 Series Management Module User Guide
The operation when the password expires is either of the following two types:
(1) A user cannot log in
The management module disconnects the console without allowing login.
Note that a user who has the account privilege can change the password
to log in.
(2) A user can change the expired password to log in.
When a user attempts to log in, a window for changing the password
appears. After changing the password, the user can log in.

Syntax
show user password policy

Privilege
Account privilege

Parameters
None

Execution example
To display the password policy:
$ show user password policy
-- Password policy --
Management of password expiration : enable
Password expiry period : 30
Change expired password : enable
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-142 Password policy

Displayed item Description

Management of password Management of password expiration dates


expiration Whether to set the expiration date for a password to
control availability of login or to enable login without
any conditions is displayed.
• enable: Sets the expiration date for a password
to control availability of login.
• disable: Enables login without any conditions.
Password expiry period Password expiry period (day)
Specify a value from 1 to 365.

5-182 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• 1-365: Password expiry period (day)
• -----: Indicates that management of password
expiration dates is disabled (users can log in
without any conditions.).
Change expired password Operation when the password expires.
• enable: Can change the expired password to log
in.
• disable: Cannot log in.
• -----: Indicates that management of password
expiration dates is disabled.

Rules
This command displays the settings for the following items: management of
password expiration dates, the password expiry period for the entire system,
and the operation when the password expires. You can use the account
information display command (show user account) to check the number of
the remaining days until the password expiration date of each account.

Related topics
• show user account on page 5-176

show user role


Displays the configuration information for the specified role. If you do not
specify a role name, the configuration information for all roles is displayed.

Syntax
show user role -i <role_id>

Privilege
Account privilege

Parameters
-i <role_id>
Role name
Specify the name of the role to be displayed. You can use a maximum of
31 alphanumeric characters. You can specify only an alphanumeric
character for the first character. You cannot omit this parameter.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Commands That Can Be Executed From the CLI Console 5-183


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the configuration information for the role bladeoperator:
$ show user role -i bladeoperator
-- User role --
Role ID : bladeoperator
Server blade 1 : enable
Server blade 2 : enable
Server blade 3 : enable
Server blade 4 : enable
Server blade 5 : enable
Server blade 6 : enable
Server blade 7 : enable
Server blade 8 : enable
Server blade 9 : enable
Server blade 10 : enable
Server blade 11 : enable
Server blade 12 : enable
Server blade 13 : enable
Server blade 14 : enable
Server blade 15 : enable
Switch module 1 : disable
Switch module 2 : disable
Network : disable
Chassis : disable
Account : disable
Read/Write : read write
Remote disable : off
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-143 Execution results of the command show user role

Displayed item Description


Role ID Role name
Displays the role name. The maximum length is 31
alphanumeric characters.
Server blade 1 Privilege for server blade 1
Displays whether the privilege for server blade 1 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 2 Privilege for server blade 2
Displays whether the privilege for server blade 2 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.

5-184 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Server blade 3 Privilege for server blade 3
Displays whether the privilege for server blade 3 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 4 Privilege for server blade 4
Displays whether the privilege for server blade 4 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 5 Privilege for server blade 5
Displays whether the privilege for server blade 5 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 6 Privilege for server blade 6
Displays whether the privilege for server blade 6 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 7 Privilege for server blade 7
Displays whether the privilege for server blade 7 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 8 Privilege for server blade 8
Displays whether the privilege for server blade 8 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 9 Privilege for server blade 9
Displays whether the privilege for server blade 9 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 10 Privilege for server blade 10
Displays whether the privilege for server blade 10 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 11 Privilege for server blade 11

Commands That Can Be Executed From the CLI Console 5-185


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Displays whether the privilege for server blade 11 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 12 Privilege for server blade 12
Displays whether the privilege for server blade 12 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 13 Privilege for server blade 13
Displays whether the privilege for server blade 13 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 14 Privilege for server blade 14
Displays whether the privilege for server blade 14 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Server blade 15 Privilege for server blade 15
Displays whether the privilege for server blade 15 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Switch module 1 Privilege for switch module 1
Displays whether the privilege for switch module 1 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Switch module 2 Privilege for switch module 2
Displays whether the privilege for switch module 2 is
assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Network Network privilege
Displays whether the network privilege is assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Chassis Server chassis privilege
Displays whether the server chassis privilege is
assigned.
• enable: The privilege is assigned.

5-186 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• disable: The privilege is not assigned.
Account Account privilege
Displays whether the account privilege is assigned.
• enable: The privilege is assigned.
• disable: The privilege is not assigned.
Read/Write Displays which privilege is assigned: the read privilege
only or the privilege for reading, setting, and
operating.
• read only: The read privilege only
• read write: The privilege for reading, setting, and
operating
Remote disable Whether permission to execute remote consoles and
OS consoles is denied
Displays whether permission to execute remote
consoles and OS consoles is denied. If on is set, the
role is not allowed to execute the remote consoles and
OS consoles of the server blades even if the server
blade privileges for the server blades are assigned to
the role.
• on: Connection to remote consoles and OS
consoles is not allowed.
• off: Connection to remote consoles and OS
consoles is allowed.

show user session


Displays information about sessions established by users logged in to
management modules.

Syntax
show user session

Privilege
Account privilege

Parameters
None

Execution example
To display information about user sessions:
show user session

Commands That Can Be Executed From the CLI Console 5-187


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-144 User session

Displayed item Description


Session ID Session ID
Remote IP address Connection-source IP address
Displays an IPv4 address or an IPv6 address.
Console Connection console
• web: Connects through the Web console.
• cli: Connects through the CLI console.
Protocol Connection protocol
• serial: Connects via a serial port
• telnet: Connects via telnet.
• ssh: Connects via SSH.
• http: Connects via HTTP.
• https: Connects via HTTPS.
Account Login account
Role Role
Login attribute Login time

Commands for time settings


This section describes the commands to confirm and change the time
settings.

set time dst


Changes the daylight saving time settings for management modules.

Syntax
set time dst -v <dst_valid> [-sm <dst_month>] [-sd <dst_day>] [-sh
<hour>] [-sn <minute>] [-em <dst_month>] [-ed <dst_day>] [-eh
<hour>] [-en <minute>] [-F]

Privilege
Chassis privilege

Parameters
-v <dst_valid>

5-188 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Enables or disables daylight saving time.
¢ enable: Enables daylight saving time.
¢ disable: Disables daylight saving time.
-sm <dst_month>
Start month of daylight saving time
Specify a value from 1 to 12.
-sd <dst_day>
Start day of daylight saving time
Specify this item in one of the following formats.
¢ Value: Specify a value from 1 to 31.
¢ "lastDDD": The last day of the week (DDD) of the month "DDD" is
"Sun", "Mon", "Tue", "Wed", "Thu", "Fri" or "Sat".
¢ "DDD>=Y": The first day of the week (DDD) after a certain date (Y)
"DDD" is "Sun", "Mon", "Tue", "Wed", "Thu", "Fri" or "Sat". "Y" is a
value from 1 to 31.
¢ "DDD<=Y": The last day of the week (DDD) before a certain date (Y)
"DDD" is "Sun", "Mon", "Tue", "Wed", "Thu", "Fri" or "Sat". "Y" is a
value from 1 to 31.
-sh <hour>
Start hour of daylight saving time
Specify a value from 0 to 23.
-sn <minute>
Start minute of daylight saving time
Specify a value from 0 to 59.
-em <dst_month>
End month of daylight saving time
Specify a value from 1 to 12.
-ed <dst_day>
End day of daylight saving time
Specify this item in one of the following formats.
¢ Value: Specify a value from 1 to 31.
¢ "lastDDD": The last day of the week (DDD) of the month "DDD" is
"Sun", "Mon", "Tue", "Wed", "Thu", "Fri" or "Sat".
¢ "DDD>=Y": The first day of the week (DDD) after a certain date (Y)
"DDD" is "Sun", "Mon", "Tue", "Wed", "Thu", "Fri" or "Sat". "Y" is a
value from 1 to 31.
¢ "DDD<=Y": The last day of the week (DDD) before a certain date (Y)
"DDD" is "Sun", "Mon", "Tue", "Wed", "Thu", "Fri" or "Sat". "Y" is a
value from 1 to 31.
-eh <hour>

Commands That Can Be Executed From the CLI Console 5-189


Hitachi Compute Blade 2500 Series Management Module User Guide
End hour of daylight saving time
Specify a value from 0 to 23.
-en <minute>
End minute of daylight saving time
Specify a value from 0 to 59.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the period from 12:00 on May 10 to 15:00 on August 24 as daylight
saving time:
set time dst -v enable -sm 5 -sd 10 -sh 12 -sn 0 -em 8 -ed 24 -eh 15
-en 0

To set the period from 12:00 on the last Sunday in May to 15:00 on the last
Wednesday in August as daylight saving time:
set time dst -v enable -sm 5 -sd lastSun -sh 12 -sn 0 -em 8 -ed
lastWed -eh 15 -en 0

To set the period from 12:00 on the first Monday after May 10 to 15:00 on
the first Saturday before August 9 as daylight saving time:
set time dst -v enable -sm 5 -sd Mon>=10 -sh 12 -sn 0 -em 8 -ed
Sat<=9 -eh 15 -en 0

To disable daylight saving time for management modules:


set time dst -v disable

set time local


Changes time settings for management modules.

Syntax
set time local -d <date_time> [-F]

Privilege
Chassis privilege

Parameters
-d <date_time>
Date and time
The format is YYYY-MM-DD hh:mm:ss.
Enter a space character between the date and the time.
Enclose the entire value in double quotation marks, because this value
includes a space character.
If you omit this parameter, the current time is set.

5-190 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the time settings for management modules:
set time local -d "2012-05-01 15:00:00"

set time timezone


Changes the time zone settings for management modules.

Syntax
set time timezone -z <timezone> [-F]

Privilege
Chassis privilege

Parameters
-z<timezone>
Time zone
Specify a time zone from -24:00 to +24:00.
If you specify a minus sign (-), enclose the entire value in double
quotation marks.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the time zone settings for management modules:
set time timezone -z +09:00

show time dst


Displays the daylight saving time settings for management modules.

Syntax
show time dst

Privilege
Chassis privilege

Commands That Can Be Executed From the CLI Console 5-191


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
None

Execution example
To display the daylight saving time settings for management modules:
show time dst

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-145 Daylight saving time

Displayed item Description


DST Whether daylight saving time is enabled
• enable: Daylight saving time is enabled.
• disable: Daylight saving time is disabled.

Table 5-146 DST start time

Displayed item Description


Month Start month of daylight saving time
This is a month from January to December.
Day Start day of daylight saving time
This item is displayed in one of the following
formats.
• Value: A value from 1 to 31.
• "lastDDD": The last day of the week (DDD) of
the month "DDD" is "Sun", "Mon", "Tue",
"Wed", "Thu", "Fri" or "Sat".
• "DDD>=Y": The first day of the week (DDD)
after a certain date (Y) "DDD" is "Sun", "Mon",
"Tue", "Wed", "Thu", "Fri" or "Sat". "Y" is a
value from 1 to 31.
• "DDD<=Y": The last day of the week (DDD)
before a certain date (Y) "DDD" is "Sun",
"Mon", "Tue", "Wed", "Thu", "Fri" or "Sat". "Y"
is a value from 1 to 31.
Time Start time of daylight saving time
The format is hh:mm.

Table 5-147 DST end time

Displayed item Description


Month End month of daylight saving time

5-192 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
This is a month from January to December.
Day End day of daylight saving time
This item is displayed in one of the following
formats.
• Value: A value from 1 to 31.
• "lastDDD": The last day of the week (DDD) of
the month "DDD" is "Sun", "Mon", "Tue",
"Wed", "Thu", "Fri" or "Sat".
• "DDD>=Y": The first day of the week (DDD)
after a certain date (Y) "DDD" is "Sun", "Mon",
"Tue", "Wed", "Thu", "Fri" or "Sat". "Y" is a
value from 1 to 31.
• "DDD<=Y": The last day of the week (DDD)
before a certain date (Y) "DDD" is "Sun",
"Mon", "Tue", "Wed", "Thu", "Fri" or "Sat". "Y"
is a value from 1 to 31.
Time End time of daylight saving time
The format is hh:mm.

show time local


Displays the time settings for management modules.

Syntax
show time local

Privilege
Chassis privilege

Parameters
None

Execution example
To display the time settings for management modules:
show time local

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-193


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-148 Local time

Displayed item Description


Date Date
The date format is YYYY-MM-DD.
YYYY is a value from 1970 to 2037. MM is a value
from 01 to 12. DD is a value from 01 to 31.

Time Time
The time format is hh:mm:ss.
hh is a value from 00 to 23. mm is a value from 00
to 59. ss is a value from 00 to 59.

show time timezone


Displays the time zone settings for management modules.

Syntax
show time timezone

Privilege
Chassis privilege

Parameters
None

Execution example
To display the time zone settings for management modules:
show time timezone

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-149 Timezone

Displayed item Description


Timezone Time zone
This is a value from -24:00 to +24:00.

5-194 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Commands for language setting
This section describes the commands to confirm or change the language
setting.

set language system


Changes the language setting for management modules.

Syntax
set language system -l <language> [-F]

Privilege
Chassis privilege

Parameters
-l <language>
Language setting
¢ english: English
¢ japanese: Japanese
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the language setting for management modules to Japanese:
set language system -l japanese

show language system


Displays the language setting for management modules.

Syntax
show language system

Privilege
Chassis privilege

Parameters
None

Commands That Can Be Executed From the CLI Console 5-195


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the language setting for management modules:
show language system

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-150 System language

Displayed item Description


Language Language setting
• english: English
• japanese: Japanese

Commands for security settings


This section describes the commands to strength the security of the system
unit.

set security strength


Sets the security strength.
Specify the security strength for management modules and server blades.
If you set the security strength for management modules, management
modules will be restarted.

Syntax
set security strength [-m] [-b <blade_no>] -s <security_strength> [-
F]

Privilege
Chassis privilege

Parameters
-m
Management modules
Specify the security strength for management modules.
-b<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.

5-196 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
If you specify all, command processing is performed for all server
blades.
-s <security_strength>
Security strength
¢ high: High
¢ default: Default
This parameter is used to set values for both management modules and
server blades.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the security strength for management modules to "high":
$ set security strength -m -s high
W0006 : If confirm, management module restart and this connect is
lost.
Confirm? (y/[n]):y
I0067 : <Management module> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To set the security strength for server blades 2 and 3 to "default":


$ set security strength -b 2,3 -s default
Confirm? (y/[n]):y
I0037 : <Blade 2> Setting was completed.
I0037 : <Blade 3> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To set the security strength for management modules and all server blades to
"high":
$ set security strength -m -b all -s high
W0006 : If confirm, management module restart and this connect is
lost.
Confirm? (y/[n]):y
I0037 : <Blade 1> Setting was completed.
I0037 : <Blade 2> Setting was completed.
I0037 : <Blade 3> Setting was completed.
I0037 : <Blade 4> Setting was completed.
I0037 : <Blade 5> Setting was completed.
I0037 : <Blade 6> Setting was completed.
I0037 : <Blade 7> Setting was completed.
I0037 : <Blade 8> Setting was completed.
I0037 : <Blade 9> Setting was completed.
I0037 : <Blade 10> Setting was completed.
I0037 : <Blade 11> Setting was completed.
I0037 : <Blade 12> Setting was completed.
I0037 : <Blade 13> Setting was completed.
I0037 : <Blade 14> Setting was completed.

Commands That Can Be Executed From the CLI Console 5-197


Hitachi Compute Blade 2500 Series Management Module User Guide
I0037 : <Blade 15> Setting was completed.
I0067 : <Management module> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
If you set the security strength for management modules, after the command
is executed, management modules will be restarted and the sessions with
management modules will be closed.
If you set the security strength for management modules to "high", the TLS
versions for management modules will be enabled or disabled as follows:
• TLS 1.2: Enabled
• TLS 1.1: Disabled
• TLS 1.0: Disabled
If you set the security strength for management modules to "default", the
TLS versions for management modules will be enabled or disabled as follows:
• TLS 1.2: Enabled
• TLS 1.1: Enabled
• TLS 1.0: Enabled

set security tls mgmt-module


Enables or disables the TLS versions for management modules.
Of the versions TLS 1.2, TLS 1.1, and TLS 1.0, specify which versions to
enable.
If you omit a version, that TLS version will be disabled.

Syntax
set security tls mgmt-module -v <tls_version> [-F]

Privilege
Chassis privilege

Parameters
-v <tls_version>
TL version
Enables the specified TLS versions. Disables the versions that are not
specified. To specify versions, use the following strings:
¢ 1.2: TLS 1.2
¢ 1.1: TLS 1.1
¢ 1.0: TLS 1.0

5-198 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ all: All versions
To enable multiple versions, separate strings by using commas. Do not
enter space characters between commas and versions.
You can specify versions in any order.
You cannot disable all TLS versions. Enter at least one TLS version.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable TLS 1.2, and to disable TLS 1.1, and TLS 1.0:
$ set security tls mgmt-module -v 1.2
Confirm? (y/[n]):y
I0067 : <Management module> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

To enable TLS 1.2, TLS 1.1, and TLS 1.0:


$ set security tls mgmt-module -v 1.2,1.1,1.0
Confirm? (y/[n]):y
I0067 : <Management module> Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Rules
You cannot disable all TLS versions.
If the security strength for management modules is "high", you cannot
change the setting to enable or disable TLS versions. (You can use only TLS
1.2.)
If you execute this command, the following message appears:
E0559 : Command was canceled. TLS version is not editable when security
strength is high.
To enable multiple versions, specify the -v parameter and separate the
versions by using commas. Do not enter space characters between commas
and versions.

show security setting


Displays the configuration information about security strength and enabled
TLS versions.
The following information is displayed:
• Security strength for management modules and information about
whether TLS versions are enabled

Commands That Can Be Executed From the CLI Console 5-199


Hitachi Compute Blade 2500 Series Management Module User Guide
• Security strength for server blades

Syntax
show security setting

Privilege
Chassis privilege

Parameters
None

Execution example
To display the security strength and TLS version configuration information:
This execution example assumes the installation status and the security
strength of server blades are as follows:
Slots 1 and 2: Full-width blade, and security strength supported
Slot 3: No blade installed
Slot 4: Half-wide blade, and security strength not supported
Slot 5: Half-wide blade, and security strength supported
Slot 6: Half-wide blade, and security strength supported
Slot 7: Half-wide blade, and security strength supported
Slot 8: No blade installed
$ show security setting
-- Management module security setting --
Security strength : high
TLS 1.2 : enable
TLS 1.1 : disable
TLS 1.0 : disable
-- Server blade security setting --
Slot : 1
Security strength : high
-- Server blade security setting --
Slot : 2 (not install)
Security strength : high
-- Server blade security setting --
Slot : 3 (not install)
Security strength : high
-- Server blade security setting --
Slot : 4 (not supported)
Security strength : high
-- Server blade security setting --
Slot : 5
Security strength : high
-- Server blade security setting --
Slot : 6
Security strength : high

5-200 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-- Server blade security setting --
Slot : 7
Security strength : high
-- Server blade security setting --
Slot : 8 (not install)
Security strength : high
:
:
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-151 Management module security setting

Displayed item Description


Security strength Security strength for management modules
Displays the security strength for management
modules.
• high: High
• default: Default
TLS 1.2 Whether TLS 1.2 is enabled
Displays whether TLS 1.2 is enabled.
• enable: Enabled.
• disable: Disabled.
TLS 1.1 Whether TLS 1.1 is enabled
Displays whether TLS 1.1 is enabled.
• enable: Enabled.
• disable: Disabled.
TLS 1.0 Whether TLS 1.0 is enabled
Displays whether TLS 1.0 is enabled.
• enable: Enabled.
• disable: Disabled.

Table 5-152 Server blade security setting

Displayed item Description


Slot Server blade slot number
This is a value from 1 to 15.
• 0 to 15: Slots in which a server blade whose
BCM supports security strength is installed
• 0 (not supported) to 15 (not supported):
Slots in which a server blade whose BCM

Commands That Can Be Executed From the CLI Console 5-201


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
does not support security strength is
installed
• 1 (not installed) to 15 (not installed): Slots
in which no server blade is installed
Security strength Security strength for server blades
• high: High
• default: Default

Commands for remote access management


This section describes the commands to manage remote access to the system
unit.

delete e-mail mgmt-lan address


Deletes an email notification destination setting.

Syntax
delete e-mail mgmt-lan address -ae <email_address> [-F]

Privilege
Chassis privilege

Parameters
-ae <email_address>
Address to which notifications are to be sent by email
Specify a maximum of 64 characters.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To delete an address to which notifications are sent by email:
delete e-mail mgmt-lan address -ae [email protected]

delete hcsm manager


Deletes HCSM.

Syntax
delete hcsm manager -i <hcsm_ip_addr> [-F]

5-202 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Chassis privilege

Parameters
-i <hcsm_ip_addr>
HCSM IP address
An IPv4 address or an IPv6 address.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To delete HCSM:
delete hcsm manager -i 192.168.0.20

delete hitrack manager


Deletes the HiTrack management server.

Syntax
delete hitrack manager -i <hitrack_ip_addr> [-F]

Privilege
Chassis privilege

Parameters
-i <hitrack_ip_addr>
IP address of HiTrack management server.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
Deletes the HiTrack management server:
delete hitrack manager -i 192.168.0.20

disconnect hcsm session


Disconnects an HCSM session.

Syntax
disconnect hcsm session -i <hcsm_ses_id> [-F]

Commands That Can Be Executed From the CLI Console 5-203


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Chassis privilege

Parameters
-i <hcsm_ses_id>
Session ID
Specify a decimal number.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To disconnect an HCSM session:
disconnect hcsm session -i 1420427160

send e-mail latest mgmt-lan


Sends the most recent failure log data by email.

Syntax
send e-mail latest mgmt-lan [-a <email_addr_no>] [-F]

Privilege
Chassis privilege

Parameters
-a <email_addr_no>
Address number to which notifications are to be sent by email
You can specify a value from 0 to 3. You can specify multiple values.
If you specify all or omit this parameter, email notifications are sent for
all addresses.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To send the most recent log data by email:
send e-mail latest mgmt-lan -a 0

5-204 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
send e-mail select mgmt-lan
Sends past failure log data (selected from the failure notification history) by
email.
For the failure notification history number, specify a log ID that is displayed
by the show log error command.

Syntax
send e-mail select mgmt-lan -n <email_history_num> [-a
<email_addr_no>] [-F]

Privilege
Chassis privilege

Parameters
-n <email_history_num>
Failure notification history number
You can specify a value from 3 to 34. You can check valid failure
notification history numbers from log IDs displayed by the show log
error command.

-a <email_addr_no>
Address to which notifications are to be sent by email
You can specify a value from 0 to 3. You can specify multiple values.
If you specify all or omit this parameter, email notifications are sent for
all addresses.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To send a failure history notification by email:
send e-mail select mgmt-lan -n 3 -a 0

send hcsm alert


Sends an alert to HCSM for a failover test in the N+M cold standby
configuration.
This command only requests for an alert to be sent.

Syntax
send hcsm alert -b <blade_no> -t <alert_type> [-F]

Commands That Can Be Executed From the CLI Console 5-205


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Chassis privilege

Parameters
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You cannot specify multiple values.
-t <alert_type>
Alert type
Specify the type of test alert to be sent.
¢ immediate: Sends an alert to HCSM to perform a failover immediately
after receiving the alert.
¢ delayed: Sends an alert to HCSM to perform a failover a while after
receiving the alert.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To send an alert to HCSM to perform a failover immediately after receiving
this alert:
send hcsm alert -b 1 -t immediate -F

set e-mail mgmt-lan address


Changes the destination to which email notifications are sent.

Syntax
set e-mail mgmt-lan address -ae <email_address> [-an
<email_nickname>] [-aa <email_attach>] [-F]

Privilege
Chassis privilege

Parameters
-ae <email_address>
Address to which notifications are to be sent by email
Specify a maximum of 64 characters.
-an <email_nickname>
Nickname of the notification destination
Specify a maximum of 15 characters.

5-206 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-aa <email_attach>
Specify whether logs are attached to the email notifications.
¢ yes: Attached.
¢ no: Not attached.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the destination to which notifications are sent by email:
set e-mail mgmt-lan address -ae [email protected] -an nickname -aa
yes

set e-mail mgmt-lan notification


Changes the email notification authentication settings.

Syntax
set e-mail mgmt-lan notification [-nn <email_notify>] [-na
<email_addr>] [-nh <email_host>] [-nc <email_comment>] [-ss
<email_smtp>] [-sp <email_port>] [-aa <email_auth>] [-au
<email_user>] [-ap <email_pass>] [-am <email_method>] [-ee
<email_encrypt>] [-ep <email_protocol>] [-F]

Privilege
Chassis privilege

Parameters
-nn <email_notify>
Enables or disables the email notification functionality.
¢ enable: Enabled.
¢ disable: Disabled.
-na <email_addr>
Email address for the administrator
Specify a maximum of 64 characters.
-nh <email_host>
Host name (FQDN)
Host name for management modules
Specify a maximum of 64 characters.
-nc <email_comment>
Comments to identify customers
Specify a maximum of 32 characters.

Commands That Can Be Executed From the CLI Console 5-207


Hitachi Compute Blade 2500 Series Management Module User Guide
-ss <email_smtp>
SMTP server
IPv4 address, IPv6 address, or host name for the SMTP server.
Specify a maximum of 64 characters.
-sp <email_port>
Port number for the SMTP server
Specify a value from 1 to 65535.
-aa <email_auth>
Enables or disables the SMTP authentication functionality.
¢ enable: Enabled.
¢ disable: Disabled.
-au <email_user>
Account name used for SMTP authentication
The maximum is 64 characters.
-ap <email_pass>
Password used for SMTP authentication
The maximum is 64 characters.
-am <email_method>
SMTP authentication method
¢ plain: Uses plain-text authentication. The account name and password
are sent together.
¢ login: Uses plain-text authentication. The account name and password
are sent separately.
¢ cram-md5: Uses challenge/response authentication. MD5 is used to
create a message digest.
-ee <email_encrypt>
Enables or disables the encryption functionality.
¢ enable: Enabled.
¢ disable: Disabled.
-ep <email_protocol>
Protocol used when the encryption functionality is enabled.
¢ tls: TLS (Transport Layer Security)
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change email notification settings:

5-208 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
set e-mail mgmt-lan notification -nn enable -na [email protected]
-nh tokyo.hitachi.com-nc comment -ss smtp.hitach.com -sp 25 -aa
enable -au user_name -ap password -am plain -ee enable -ep tls

set hcsm agent


Sets HCSM linkage.

Syntax
set hcsm agent -c <hcsm_permit_con> -o <hcsm_permit_other> [-F]

Privilege
Chassis privilege

Parameters
-c <hcsm_permit_con>
HCSM linkage functionality
¢ enable: Enables the HCSM linkage functionality.
¢ disable: Disables the HCSM linkage functionality.
-o <hcsm_permit_other>
Connection restrictions
¢ enable: Permits only connections from registered HCSM instances.
¢ disable: Permits connections from all HCSM instances.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To enable the HCSM linkage functionality and the connection restriction
setting:
set hcsm agent -c enable -o enable

set hcsm manager


Sets HCSM.
If no IP address is registered, this command registers the information. If an
IP address is already registered, this command updates the information.
This command does not change the settings for parameters that are not
specified.

Commands That Can Be Executed From the CLI Console 5-209


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
set hcsm manager -i <hcsm_ip_addr> [-ap <alert_port>] [-al
<alert_policy>] [-ai <alert_retry_interval>] [-at
<alert_retry_time>] [-F]

Privilege
Chassis privilege

Parameters
-i <hcsm_ip_addr>
HCSM IP address
An IPv4 address or an IPv6 address.
-ap <alert_port>
Port number to which alerts are to be sent
This is the number of the port where HCSM receives alerts. Specify a
value from 1 to 65535.
Do not specify this parameter to change the setting value.
The port number can be set from HCSM. If you use HCSM to change the
port number, re-execute Discovering and adding resources from HCSM.
-al <alert_policy>
Level of alerts that are to be sent to HCSM
Do not specify this parameter to change the setting value.
¢ all: All notifications (failure notifications, warning notifications, and
information notifications)
¢ warning: Warning notifications (failure notifications and warning
notifications)
¢ alert: Failure notifications
¢ disable: No notifications
-ai <alert_retry_interval>
Retry interval (in minutes) when an alert notification cannot be sent
Specify a value from 1 to 4.
Do not specify this parameter to change the setting value.
-at <alert_retry_time>
Time period (in minutes) during which the sending of alert notifications is
to be retried
Specify a value from 4 to 15.
Do not specify this parameter to change the setting value.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-210 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To set an HCSM IP address to restrict connections based on the IP address:
set hcsm manager -i 192.168.0.20

Related topic
• Manual Hitachi Command Suite Compute Systems Manager User Guide

set hitrack agent


Sets the HiTrack agent.

Syntax
set hitrack agent -c <hitrack_permit_con> [-F]

Privilege
Chassis privilege

Parameters
-c <hitrack_permit_con>
HiTrack Enable or Disable
¢ enable : HiTrack enable
¢ disable : HiTrack disable
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
Sets the HiTrack agent:
set hitrack agent -c enable

set hitrack manager


Sets the HiTrack management server.
Adds server when IP address is not registered and updates the setting when
registered.

Syntax
set hitrack manager -i <hitrack_ip_addr> [-F]

Privilege
Chassis privilege

Commands That Can Be Executed From the CLI Console 5-211


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-i <hitrack_ip_addr>
IP address of HiTrack management server
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
set hitrack manager -i 192.168.0.20

set remote-access protocol ftp


Changes the FTP connection permission settings.

Syntax
set remote-access protocol ftp [-a <allow>] [-n <network_addr>] [-s
<subnet_mask>] [-a6 <allow>] [-n6 <network_addr>] [-p6 <prefix_len>]
[-F]

Privilege
Chassis privilege

Parameters
-a <allow>
IPv4 connection permission
¢ allow: Permits IPv4 connections.
¢ deny: Prohibits IPv4 connections.
-n <network_addr>
Network address
To limit the IPv4 addresses from which FTP connections are permitted,
specify the network address that indicates the range of IPv4 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-s <subnet_mask>
Subnet mask
To limit the IPv4 addresses from which FTP connections are permitted,
specify the subnet mask that indicates the range of IPv4 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-a6 <allow>
IPv6 connection permission

5-212 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ allow: Permits IPv6 connections.
¢ deny: Prohibits IPv6 connections.
-n6 <network_addr>
Network address
To limit the IPv6 addresses from which FTP connections are permitted,
specify the network address that indicates the range of IPv6 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "::".
-p6 <prefix_len>
Prefix length
To limit the IPv6 addresses from which FTP connections are permitted,
specify the prefix length that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0".
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To permit FTP connections from 192.168.0.0 to192.168.0.255:
set remote-access protocol ftp -a allow -n 192.168.0.0 -s
255.255.255.0

To prohibit all FTP connections:


set remote-access protocol ftp -a deny

set remote-access protocol http


Changes the HTTP connection permission settings.

Syntax
set remote-access protocol http [-a <allow>] [-p <protocol_port>] [-
n <network_addr>] [-s <subnet_mask>] [-a6 <allow>] [-n6
<network_addr>] [-p6 <prefix_len>] [-F]

Privilege
Chassis privilege

Parameters
-a <allow>
IPv4 connection permission
¢ allow: Permits IPv4 connections.

Commands That Can Be Executed From the CLI Console 5-213


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ deny: Prohibits IPv4 connections.
-p <protocol_port>
Protocol number
Specify a value from 1 to 65535.
-n <network_addr>
Network address
To limit the IPv4 addresses from which HTTP connections are permitted,
specify the network address that indicates the range of IPv4 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-s <subnet_mask>
Subnet mask
To limit the IPv4 addresses from which HTTP connections are permitted,
specify the subnet mask that indicates the range of IPv4 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-a6 <allow>
IPv6 connection permission
¢ allow: Permits IPv6 connections.
¢ deny: Prohibits IPv6 connections.
-n6 <network_addr>
Network address
To limit the IPv6 addresses from which HTTP connections are permitted,
specify the network address that indicates the range of IPv6 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "::".
-p6 <prefix_len>
Prefix length
To limit the IPv6 addresses from which HTTP connections are permitted,
specify the prefix length that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0".
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

5-214 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To set the HTTP port number to 80 and to permit HTTP connections from
192.168.0.0 to 192.168.0.255:
set remote-access protocol http -p 80 -a allow -n 192.168.0.0 -s
255.255.255.0

To prohibit all HTTP connections:


set remote-access protocol http -a deny

set remote-access protocol https


Changes the HTTPS connection permission settings.

Syntax
set remote-access protocol https [-a <allow>] [-p <protocol_port>] [-
n <network_addr>] [-s <subnet_mask>] [-a6 <allow>] [-n6
<network_addr>] [-p6 <prefix_len>] [-F]

Privilege
Chassis privilege

Parameters
-a <allow>
IPv4 connection permission
¢ allow: Permits IPv4 connections.
¢ deny: Prohibits IPv4 connections.
-p <protocol_port>
Protocol number
Specify a value from 1 to 65535.
-n <network_addr>
Network address
To limit the IPv4 addresses from which HTTPS connections are permitted,
specify the network address that indicates the range of IPv4 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-s <subnet_mask>
Subnet mask
To limit the IPv4 addresses from which HTTPS connections are permitted,
specify the subnet mask that indicates the range of IPv4 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-a6 <allow>

Commands That Can Be Executed From the CLI Console 5-215


Hitachi Compute Blade 2500 Series Management Module User Guide
IPv6 connection permission
¢ allow: Permits IPv6 connections.
¢ deny: Prohibits IPv6 connections.
-n6 <network_addr>
Network address
To limit the IPv6 addresses from which HTTPS connections are permitted,
specify the network address that indicates the range of IPv6 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "::".
-p6 <prefix_len>
Prefix length
To limit the IPv6 addresses from which HTTPS connections are permitted,
specify the prefix length that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0".
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To set the HTTPS port number to 443 and to permit HTTPS connections from
192.168.0.0 to 192.168.0.255:
set remote-access protocol https -p 443 -a allow -n 192.168.0.0 -s
255.255.255.0

To prohibit all HTTPS connections:


set remote-access protocol https -a deny

set remote-access protocol ssh


Changes the SSH connection permission settings.

Syntax
set remote-access protocol ssh [-a <allow>] [-n <network_addr>] [-s
<subnet_mask>] [-a6 <allow>] [-n6 <network_addr>] [-p6 <prefix_len>]
[-F]

Privilege
Chassis privilege

Parameters
-a <allow>

5-216 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
IPv4 connection permission
¢ allow: Permits IPv4 connections.
¢ deny: Prohibits IPv4 connections.
-n <network_addr>
Network address
To limit the IPv4 addresses from which SSH connections are permitted,
specify the network address that indicates the range of IPv4 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-s <subnet_mask>
Subnet mask
To limit the IPv4 addresses from which SSH connections are permitted,
specify the subnet mask that indicates the range of IPv4 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-a6 <allow>
IPv6 connection permission
¢ allow: Permits IPv6 connections.
¢ deny: Prohibits IPv6 connections.
-n6 <network_addr>
Network address
To limit the IPv6 addresses from which SSH connections are permitted,
specify the network address that indicates the range of IPv6 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "::".
-p6 <prefix_len>
Prefix length
To limit the IPv6 addresses from which SSH connections are permitted,
specify the prefix length that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0".
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To permit SSH connections from 192.168.0.0 to 192.168.0.255:

Commands That Can Be Executed From the CLI Console 5-217


Hitachi Compute Blade 2500 Series Management Module User Guide
set remote-access protocol ssh -a allow -n 192.168.0.0 -s
255.255.255.0

To prohibit all SSH connections:


set remote-access protocol ssh -a deny

set remote-access protocol telnet


Changes the Telnet connection permission settings.

Syntax
set remote-access protocol telnet [-a <allow>] [-n <network_addr>] [-
s <subnet_mask>] [-a6 <allow>] [-n6 <network_addr>] [-p6
<prefix_len>] [-F]

Privilege
Chassis privilege

Parameters
-a <allow>
IPv4 connection permission
¢ allow: Permits IPv4 connections.
¢ deny: Prohibits IPv4 connections.
-n <network_addr>
Network address
To limit the IPv4 addresses from which Telnet connections are permitted,
specify the network address that indicates the range of IPv4 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-s <subnet_mask>
Subnet mask
To limit the IPv4 addresses from which Telnet connections are permitted,
specify the subnet mask that indicates the range of IPv4 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0.0.0.0".
-a6 <allow>
IPv6 connection permission
¢ allow: Permits IPv6 connections.
¢ deny: Prohibits IPv6 connections.
-n6 <network_addr>
Network address

5-218 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
To limit the IPv6 addresses from which Telnet connections are permitted,
specify the network address that indicates the range of IPv6 addresses to
be permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "::".
-p6 <prefix_len>
Prefix length
To limit the IPv6 addresses from which Telnet connections are permitted,
specify the prefix length that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which connections are
permitted, specify "0".
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To permit Telnet connections from 192.168.0.0 to 192.168.0.255:
set remote-access protocol telnet -a allow -n 192.168.0.0 -s
255.255.255.0

To prohibit all Telnet connections:


set remote-access protocol telnet -a deny

show e-mail mgmt-lan


Displays the email notification settings.

Syntax
show e-mail mgmt-lan

Privilege
Chassis privilege

Parameters
None

Execution example
To display the email notification settings:
show e-mail mgmt-lan

Commands That Can Be Executed From the CLI Console 5-219


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-153 E-mail notification setting

Displayed item Description


Notification Whether the email notification functionality is
enabled
• enable: Enabled.
• disable: Disabled.
Address Email address for the administrator
The maximum length is 64 characters.
Host (FQDN) Host name (FQDN)
Host name for management modules
The maximum length is 64 characters.
Comment Comments to identify customers
The maximum length is 32 characters.
SMTP server SMTP server
IPv4 address, IPv6 address, or host name for the
SMTP server.
The maximum length is 64 characters.
Port number Port number for the SMTP server
This is a value from 1 to 65535.

Table 5-154 E-mail authentication setting

Displayed item Description


Authentication Enables or disables the SMTP authentication
functionality.
• enable: Enabled.
• disable: Disabled.
Name Account name used for SMTP authentication
This item consists of alphanumeric characters
(uppercase A to Z, lowercase a to z, and 0 to 9),
hyphens (-), underscores (_), and periods (.).
The maximum length is 64 characters.
Method SMTP authentication method
• plain: Uses plain-text authentication. The
account name and password are sent
together.
• login: Uses plain-text authentication. The
account name and password are sent
separately.

5-220 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• cram-md5: Uses challenge/response
authentication. MD5 is used to create a
message digest.

Table 5-155 E-mail encryption setting

Displayed item Description


Encryption Enables or disables the encryption functionality.
• enable: Enabled.
• disable: Disabled.
Protocol Protocol used when the encryption functionality is
enabled
• tls: TLS (Transport Layer Security)

Table 5-156 E-mail address

Displayed item Description


Number Email notification destination number
This is a value from 0 to 3.
Nickname Nickname of the notification destination
The maximum length is 15 characters.
Address Address to which notifications are to be sent by
email
The maximum length is 64 characters.
Attach Whether logs are attached to the email notifications
• yes: Attached.
• no: Not attached.

show hcsm setting


Displays the HCSM settings.

Syntax
show hcsm setting

Privilege
Chassis privilege

Parameters
None

Commands That Can Be Executed From the CLI Console 5-221


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the HCSM settings:
show hcsm setting

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-157 HCSM agent setting

Displayed item Description


Server cooperation HCSM linkage functionality
• enable: The HCSM linkage functionality is
enabled.
• disable: The HCSM linkage functionality is
disabled.
Access control Connection restrictions
• enable: Only connections from registered HCSM
instances are permitted.
• disable: Connections from all HCSM instances
are permitted.

Table 5-158 HCSM management server setting

Displayed item Description


IP address HCSM IP address
Displays an IPv4 address or an IPv6 address.
Alert port Port number to which alerts are sent
This is a value from 1 to 65535.
Alert level Level of alerts that are to be sent to HCSM
• all: All notifications (failure notifications,
warning notifications, and information
notifications)
• warning: Warning notifications (failure
notifications and warning notifications)
• alert: Failure notifications
• disable: No notifications
Alert retry interval (min) Retry interval (in minutes) when an alert notification
cannot be sent
This is a value from 1 to 4.
Alert retry duration (min) Time period (in minutes) during which the sending
of alert notifications is to be retried
This is a value from 4 to 15.

5-222 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-159 HCSM session

Displayed item Description


Connection status Connection status
• connect: A connection is established.
• disconnect: No connection is
established.
Session ID Session ID
Displays the session ID as a decimal
number.

show hitrack setting


Shows the setting of HiTrack setting.

Syntax
show hitrack setting

Privilege
Chassis privilege

Parameters
None

Execution example
Shows the setting of HiTrack:
show hitrack setting

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-160 HiTrack agent setting

Displayed item Description


Server cooperation HiTrack Enable or Disable
• enable : HiTrack enable
• disable : HiTrack disable

Commands That Can Be Executed From the CLI Console 5-223


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-161 HiTrack management server setting

Displayed item Description


IP address IP address of HiTrack management
server.

show remote-access protocol ftp


Displays the FTP connection permission settings.

Syntax
show remote-access protocol ftp

Privilege
Chassis privilege

Parameters
None

Execution example
To display the FTP connection permission settings:
show remote-access protocol ftp

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-162 FTP setting

Displayed item Description


Allow IPv4 connection permission
• allow: IPv4 connections are permitted.
• deny: IPv4 connections are prohibited.
Network address Network address
If there is a limit on the IPv4 addresses from
which FTP connections are permitted, the
network address indicating the range of
permitted IPv4 addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.
Subnetmask Subnet mask

5-224 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
If there is a limit on the IPv4 addresses from
which FTP connections are permitted, the subnet
mask indicating the range of permitted IPv4
addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.

Table 5-163 FTP setting (IPv6)

Displayed item Description


Allow IPv6 connection permission
• allow: IPv6 connections are permitted.
• deny: IPv6 connections are prohibited.
Network address Network address
If there is a limit on the IPv6 addresses from
which FTP connections are permitted, the
network address indicating the range of
permitted IPv6 addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "::" is displayed.
Prefix len Prefix length
If there is a limit on the IPv6 addresses from
which FTP connections are permitted, the prefix
length indicating the range of permitted IPv6
addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "0" is displayed.

show remote-access protocol http


Displays the HTTP connection permission settings.

Syntax
show remote-access protocol http

Privilege
Chassis privilege

Parameters
None

Execution example
To display the HTTP connection permission settings:
show remote-access protocol http

Commands That Can Be Executed From the CLI Console 5-225


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-164 HTTP setting

Displayed item Description


Port number Protocol number
This is a value from 1 to 65535.
Allow IPv4 connection permission
• allow: IPv4 connections are permitted.
• deny: IPv4 connections are prohibited.
Network address Network address
If there is a limit on the IPv4 addresses from which
HTTP connections are permitted, the network
address indicating the range of permitted IPv4
addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.
Subnetmask Subnet mask
If there is a limit on the IPv4 addresses from which
HTTP connections are permitted, the subnet mask
indicating the range of permitted IPv4 addresses is
displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.

Table 5-165 HTTP setting (IPv6)

Displayed item Description


Allow IPv6 connection permission
• allow: IPv6 connections are permitted.
• deny: IPv6 connections are prohibited.
Network address Network address
If there is a limit on the IPv6 addresses from which
HTTP connections are permitted, the network
address indicating the range of permitted IPv6
addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "::" is displayed.
Prefix len Prefix length
To limit the IPv6 addresses from which HTTP
connections are permitted, specify the prefix length
that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which
connections are permitted, specify "0".

5-226 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
show remote-access protocol https
Displays the HTTP connection permission settings.

Syntax
show remote-access protocol https

Privilege
Chassis privilege

Parameters
None

Execution example
To display the HTTP connection permission settings:
show remote-access protocol https

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-166 HTTPS setting

Displayed item Description


Port number Protocol number
This is a value from 1 to 65535.
Allow IPv4 connection permission
• allow: IPv4 connections are permitted.
• deny: IPv4 connections are prohibited.
Network address Network address
If there is a limit on the IPv4 addresses from which
HTTPS connections are permitted, the network address
indicating the range of permitted IPv4 addresses is
displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.
Subnetmask Subnet mask
If there is a limit on the IPv4 addresses from which
HTTPS connections are permitted, the subnet mask
indicating the range of permitted IPv4 addresses is
displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.

Commands That Can Be Executed From the CLI Console 5-227


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-167 HTTPS setting (IPv6)

Displayed item Description


Allow IPv6 connection permission
• allow: IPv6 connections are permitted.
• deny: IPv6 connections are prohibited.
Network address Network address
If there is a limit on the IPv6 addresses from which
HTTPS connections are permitted, the network
address indicating the range of permitted IPv6
addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "::" is displayed.
Prefix len Prefix length
To limit the IPv6 addresses from which HTTPS
connections are permitted, specify the prefix length
that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from
which connections are permitted, specify "0".

show remote-access protocol ssh


Displays the SSH connection permission settings.

Syntax
show remote-access protocol ssh

Privilege
Chassis privilege

Parameters
None

Execution example
To display the SSH connection permission settings:
show remote-access protocol ssh

Execution results
The following table shows the items that are displayed as the execution
results of this command.

5-228 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-168 SSH setting

Displayed item Description


Allow IPv4 connection permission
• allow: IPv4 connections are permitted.
• deny: IPv4 connections are prohibited.
Network address Network address
If there is a limit on the IPv4 addresses from which
SSH connections are permitted, the network address
indicating the range of permitted IPv4 addresses is
displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.
Subnetmask Subnet mask
If there is a limit on the IPv4 addresses from which
SSH connections are permitted, the subnet mask
indicating the range of permitted IPv4 addresses is
displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.

Table 5-169 SSH setting (IPv6)

Displayed item Description


Allow IPv6 connection permission
• allow: IPv6 connections are permitted.
• deny: IPv6 connections are prohibited.
Network address Network address
If there is a limit on the IPv6 addresses from which
SSH connections are permitted, the network address
indicating the range of permitted IPv6 addresses is
displayed.
If there is no limit on the addresses from which
connections are permitted, "::" is displayed.
Prefix len Prefix length
To limit the IPv6 addresses from which SSH
connections are permitted, specify the prefix length
that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which
connections are permitted, specify "0".

show remote-access protocol telnet


Displays the Telnet connection permission settings.

Commands That Can Be Executed From the CLI Console 5-229


Hitachi Compute Blade 2500 Series Management Module User Guide
Syntax
show remote-access protocol telnet

Privilege
Chassis privilege

Parameters
None

Execution example
To display the Telnet connection permission settings:
show remote-access protocol telnet

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-170 TELNET setting

Displayed item Description


Allow IPv4 connection permission
• allow: IPv4 connections are permitted.
• deny: IPv4 connections are prohibited.
Network address Network address
If there is a limit on the IPv4 addresses from
which Telnet connections are permitted, the
network address indicating the range of permitted
IPv4 addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.
Subnetmask Subnet mask
If there is a limit on the IPv4 addresses from
which Telnet connections are permitted, the
subnet mask indicating the range of permitted
IPv4 addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "0.0.0.0" is displayed.

Table 5-171 TELNET setting (IPv6)

Displayed item Description


Allow IPv6 connection permission
• allow: IPv6 connections are permitted.
• deny: IPv6 connections are prohibited.

5-230 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Network address Network address
If there is a limit on the IPv6 addresses from which
Telnet connections are permitted, the network
address indicating the range of permitted IPv6
addresses is displayed.
If there is no limit on the addresses from which
connections are permitted, "::" is displayed.
Prefix len Prefix length
To limit the IPv6 addresses from which Telnet
connections are permitted, specify the prefix length
that indicates the range of IPv6 addresses to be
permitted.
If you do not want to limit the addresses from which
connections are permitted, specify "0".

Commands for SNMP management


This section describes the commands to use the SNMP functionality.

delete snmp manager


Deletes the SNMP manager settings.

Syntax
delete snmp manager -n <snmp_mgr_num> [-F]

Privilege
Chassis privilege

Parameters
-n <snmp_mgr_num>
SNMP manager number
You can specify a value from 0 to 8. You cannot specify multiple values.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To delete SNMP manager 8:
$ delete snmp manager -n 8
Confirm? (y/[n]):y
I0027 : Deleting was completed.
S0002 : Command succeeded.

Commands That Can Be Executed From the CLI Console 5-231


Hitachi Compute Blade 2500 Series Management Module User Guide
S0000 : Command was finished.
$

export snmp mib


Outputs the MIB file.

Syntax
export snmp mib [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To output the MIB file:
export snmp mib

set snmp agent


Changes the SNMP agent settings.

Syntax
set snmp agent [-v <snmp_valid>] [-c <snmp_contact>] [-l <snmp_loc>]
[-p <snmp_port>] [-t <snmp_trap>] [-s <snmp_version>] [-e
<snmp_engine_str>] [-F]

Privilege
Chassis privilege

Parameters
-v <snmp_valid>
Enables or disables the SNMP agent.
¢ Enable: Enables the SNMP agent.
¢ Disable: Disables the SNMP agent.
-c <snmp_contact>
Name of the administrator
Specify a maximum of 60 characters.
-l <snmp_loc>

5-232 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Location
Specify a maximum of 60 characters.
-p <snmp_port>
Port number that is used by the SNMP agent
Specify a value from 1 to 65535.
-t <snmp_trap>
Levels for which notifications are to be sent by SNMP traps
¢ Disable: Does not send notifications.
¢ Alert: Sends notifications when the level is non-recoverable-level or
serious.
¢ Information: Sends notifications when the level is information.
¢ ALL: Sends notifications for all levels.
-s <snmp_version>
SNMP version
¢ v1/v2c: SNMPv1 or SNMPv2c
¢ v3: SNMPv3
-e <snmp_engine_str>
Character string for creating an engine ID
Specify a value consisting of 1 to 27 characters.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the SNMP agent settings:
set snmp agent -v enable -c contact_name -l location -p 161 -t
information -s v1/v2c

set snmp manager


Changes the SNMP manager settings.

Syntax
set snmp manager -n <snmp_mgr_num> [-s <snmp_version>] [-h
<snmp_mgr_host_name>] [-p <snmp_mgr_port>] [-c
<snmp_mgr_community_name>] [-u <snmp_mgr_user_name>] [-a
<snmp_mgr_access_type>] [-at <snmp_mgr_auth_type>] [-ap
<snmp_mgr_auth_password>] [-et <snmp_mgr_encrypt_type>] [-ep
<snmp_mgr_encrypt_password>] [-F]

Privilege
Chassis privilege

Commands That Can Be Executed From the CLI Console 5-233


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-n <snmp_mgr_num>
SNMP manager number
You can specify a maximum of nine numbers.
Specify a value from 0 to 8.
-s <snmp_version>
SNMP version
-h <snmp_mgr_host_name>
Domain name (FQDN), or the IPv4 address or IPv6 address for the SNMP
manager.
Specify a maximum of 255 characters.
-p <snmp_mgr_port>
SNMP manager port number
This value is not the same as the port number for the SNMP agent.
Specify a value from 1 to 65535.
-c <snmp_mgr_community_name>
Community name for the SNMP manager
Specify a maximum of 60 characters.
This item is valid only for SNMPv1 and SNMPv2c.
-u <snmp_mgr_user_name>
SNMP manager user name
Specify a value consisting of 1 to 32 characters.
This item is valid only for SNMPv3.
-a <snmp_mgr_access_type>
SNMP manager access type
¢ noauth-nopriv: Disables authentication and encryption.
¢ auth-nopriv: Enables authentication but disables encryption.
¢ auth-priv: Enables authentication and encryption.
This item is valid only for SNMPv3.
-at <snmp_mgr_auth_type>
Authentication method
¢ md5: MD5 method
¢ sha: SHA method
This item is valid only when the SNMP version is v3 and the access type is
auth-nopriv or auth-priv.
-ap <snmp_mgr_auth_password>
Authentication password
This item is valid only when the SNMP version is v3 and the access type is
auth-nopriv or auth-priv.

5-234 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-et <snmp_mgr_encrypt_type>
Encryption algorithm
¢ des: DES algorithm
¢ aes: AES algorithm
This item is valid only when the SNMP version is v3 and the access type is
auth-priv.
-ep <snmp_mgr_encrypt_password>
Encryption password
This item is valid only when the SNMP version is v3 and the access type is
auth-priv.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the SNMP manager settings (for SNMPv1 and SNMPv2c):
set snmp manager -n 0 -s v1/v2c -h 192.168.0.0 -p 162 -c
community_name

To change the SNMP manager settings (for SNMPv3):


set snmp manager -n 0 -s v3 -h 192.168.0.0 -p 162 -u user_name -a
auth-priv -at md5 -ap password -et des -ep password

show snmp agent


Displays the SNMP agent settings.

Syntax
show snmp agent

Privilege
Chassis privilege

Parameters
None

Execution example
To display the SNMP agent settings:
show snmp agent

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-235


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-172 SNMP agent setting

Displayed item Description


Agent Whether the SNMP agent is enabled
• Enable: The SNMP agent is enabled.
• Disable: The SNMP agent is disabled.
Contact name Name of the administrator
The maximum length is 60 characters.
Location Location
Specify a maximum of 60 characters.
Port number Port number used by the SNMP agent
This is a value from 1 to 65535.
Trap level Levels for which notifications are to be sent by
SNMP traps
• Disable: Notifications are not sent.
• Alert: Notifications are not sent when the
level is non-recoverable-level or serious.
• Information: Notifications are not sent when
the level is information.
• ALL: All-levels notifications are sent.
SNMP version SNMP version
• v1/v2c: SNMPv1 or SNMPv2c
• v3: SNMPv3
Engine ID string Character string for creating an engine ID
This is a value consisting of 1 to 27 characters.
Engine ID Engine ID
This is a value consisting of 12 to 64 characters.

show snmp manager


Displays the SNMP manager settings.

Syntax
show snmp manager [-n <snmp_mgr_num>]

Privilege
Chassis privilege

Parameters
-n <snmp_mgr_num>
SNMP manager number
You can specify a maximum of nine numbers.

5-236 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify a value from 0 to 8.

Execution example
To display the SNMP manager settings:
show snmp manager -n 0

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-173 SNMP Manager setting

Displayed item Description


SNMP version SNMP version
Host name Domain name (FQDN), or the IPv4 address
or IPv6 address for the SNMP manager.
The maximum length is 255 characters.
Port number Port number for the SNMP manager
This value is not the same as the port
number for the SNMP agent.
This is a value from 1 to 65535.
Community name Community name for the SNMP manager
The maximum length is 60 characters.
This item is valid only for SNMPv1 and
SNMPv2c.
User name User name for the SNMP manager
This is a value consisting of 1 to 32
characters.
This item is valid only for SNMPv3.
Access type Access type for the SNMP manager
• noauth-nopriv: Disables authentication
and encryption.
• auth-nopriv: Enables authentication
but disables encryption.
• auth-priv: Enables authentication and
encryption.
This item is valid only for SNMPv3.
Authentication type Authentication method
• md5: MD5 method
• sha: SHA method
This item is valid only when the SNMP
version is v3 and the access type is auth-
nopriv or auth-priv.
Encrypt type Encryption algorithm

Commands That Can Be Executed From the CLI Console 5-237


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• des: DES algorithm
• aes: AES algorithm
This item is valid only when the SNMP
version is v3 and the access type is auth-
priv.

show snmp mib


Displays the MIB file version.

Syntax
show snmp mib

Privilege
Chassis privilege

Parameters
None

Execution example
To display the MIB file version:
show snmp mib

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-174 MIB information

Displayed item Description


Version MIB version

test snmp trap


Sends SNMP test traps.

Syntax
test snmp trap [-F]

Privilege
Chassis privilege

5-238 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To send an SNMP test trap:
test snmp trap

Commands for LPAR manager management


This section describes commands to manage LPAR manager firmware
information.

delete hvm firmware


Deletes the LPAR manager firmware that was installed for the management
modules.

Syntax
delete hvm firmware -b <bank_no> [-F]

Privilege
Chassis privilege

Parameters
-b <bank_no>
Bank number
You can specify a value from 0 to 3. You can specify multiple values.
If you specify all or omit this parameter, all of the LPAR manager
firmware instances are deleted.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To delete the LPAR manager firmware that was installed for bank 0:
$ delete hvm firmware -b 0
Confirm? (y/[n]):y
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

Commands That Can Be Executed From the CLI Console 5-239


Hitachi Compute Blade 2500 Series Management Module User Guide
show hvm firmware
Displays the area number and version of the LPAR manager firmware that
was installed for the management modules.

Syntax
show hvm firmware

Privilege
Chassis privilege

Parameters
None

Execution example
To display the area number and version of the LPAR manager firmware:
show hvm firmware

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-175 LPAR manager firmware

Displayed item Description


Bank LPAR manager firmware area number
This is a value from 0 to 3.
Version LPAR manager firmware version
This is the LPAR manager firmware version that
was installed in the area of the corresponding
number.

update hvm firmware


Updates the LPAR manager firmware.

Syntax
update hvm firmware -f <fw_file_name> -b <hvm_bank_no> [-F]

Privilege
Chassis privilege

5-240 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-f <fw_file_name>
Name of the firmware update file
-b <hvm_bank_no>
LPAR manager firmware area number
Specify a value from 0 to 3.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To update the LPAR manager firmware installed in area 0 by using the file
fw.update:
update hvm firmware -f fw.update -b 0

Rules
You must send the firmware update file via FTP before executing this
command.
If you send the firmware update file while this command is running, the
firmware update might fail.
If the firmware update fails, retry the operation.

Commands to collect log data


This section describes commands to collect log data.

export log failure


Obtains dump log data.

Syntax
export log failure [-d] [-F]

Privilege
Chassis privilege

Parameters
-d
The dump log is output to the home directory for management modules.
Even if you omit this parameter, the behavior of this command is the
same as if this parameter is specified.

Commands That Can Be Executed From the CLI Console 5-241


Hitachi Compute Blade 2500 Series Management Module User Guide
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To obtain dump log data:
export log failure -d

export log mar-log all


Outputs all MAR log data.

Syntax
export log mar-log all [-d] [-F]

Privilege
Chassis privilege

Parameters
-d
The MAR log is output to the home directory for management modules.
Even if you omit this parameter, the behavior of this command is the
same as if this parameter is specified.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To output all MAR log data to the home directory for management modules:
export log mar-log all -d

export log mar-log latest


Outputs the latest MAR log data.

Syntax
export log mar-log latest [-d] [-F]

Privilege
Chassis privilege

5-242 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Parameters
-d
The MAR log is output to the home directory for management modules.
Even if you omit this parameter, the behavior of this command is the
same as if this parameter is specified.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To output the latest MAR log data to the home directory for management
modules:
export log mar-log latest -d

show log environment


Displays the history items listed below for server blades, management
modules, or power supply modules.
For each of the following items, the daily values for past seven days are
displayed:
• Intake temperature
¢ Daily average, maximum, and minimum values
¢ Hourly averages (for the last 24 hours)
• Exhaust temperature
¢ Daily average, maximum, and minimum values
¢ Hourly averages (for the last 24 hours)

Syntax
show log environment -m <log_env_module> [-s <log_env_slot_no>]

Privilege
Chassis privilege

Parameters
-m <log_env_module>
Type of the module whose environment log data is to be displayed
¢ blade: Server blade
¢ mgmt: Management module
¢ ps: Power supply module
¢ switch: Switch module

Commands That Can Be Executed From the CLI Console 5-243


Hitachi Compute Blade 2500 Series Management Module User Guide
-s <log_env_slot_no>
Number of the module whose environment log data is to be displayed
¢ Serve blade: Specify a value from 1 to 15.
¢ Management module: Specify a value 1 or 2.
¢ Power supply module: Specify a value from 1 to 6.
¢ Switch module: Specify a value 1 or 2.

Execution example
To display environment log data for server blade 1:
show log environment -m blade -s 1

To display environment log data for management module 1:


show log environment -m mgmt -s 1

To display environment log data for power supply module 1:


show log environment -m ps -s 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-176 module-name.slot-number.environment monitoring log

Displayed item Description


Date Environment log collection date
intake temperature[C] Intake temperature
Displays the daily average, maximum, and
minimum values, as well as the hourly averages
for the last 24 hours.
exhaust temperature[C] Exhaust temperature
Displays the daily average, maximum, and
minimum values, as well as the hourly averages
for the last 24 hours.

show log error


Displays the error notification history.
Use this command to check the log ID to be specified for the send e-mail
select mgmt-lan command.

Syntax
show log error

5-244 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Privilege
Chassis privilege

Parameters
None

Execution example
To display the failure notification history:
show log error

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-177 Error log and E-mail notification history

Displayed item Description


Timestamp Date and time when the log entry was generated
ID Log ID
System event log System event log (SEL)

show log hcsm-log


Displays HCSM log data.

Syntax
show log hcsm-log

Privilege
Chassis privilege

Parameters
None

Execution example
To display HCSM log data:
show log hcsm-log

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-245


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-178 HCSM log

Displayed item Description


Timestamp Registration time
ID Log ID (alert ID)
Level Alert level
• Info: Information level
• WARNING: Warning level
• FAIL: Failure level
Message Event message

show log mac-edit


Displays the following Optional Physical MAC change log data:
• Time when the log was collected
• Information about the port whose MAC address was changed (server
blade number, card number, and port number on the card)
• MAC addresses before and after the change
• Source that sent a change request

Syntax
show log mac-edit

Privilege
Chassis privilege

Parameters
None

Execution example
To display Optional Physical MAC change log data:
show log mac-edit

Execution results
The following table shows the items that are displayed as the execution
results of this command.

5-246 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-179 Execution results of the command show log mac-edit

Displayed item Description


Timestamp Time when the log was collected
P Server blade slot number
This is a value from 1 to 15.
In an SMP configuration, this item displays the slot
numbers for primary server blades.
S Server blade slot number
This is a value from 1 to 15.
Card Card type
• MCx: Mezzanine card x is the card slot number.
• IOxx: I/O adapter. xx is the slot number for the
I/O adapter.
Controller Controller number of the card
Port Port number of the controller
Before MAC before the change
After MAC after the change
From Source of the change request
• hcsmx: Change request from HCSM x is the HCSM
number.
• console: Change request from the console

show log mar-log


Displays MAR log data.

Syntax
show log mar-log

Privilege
Chassis privilege

Parameters
None

Execution example
To display MAR log data:
show log mar-log

Commands That Can Be Executed From the CLI Console 5-247


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-180 MARLOG INDEX

Displayed item Description


Timestamp Date and time when the log entry was generated
ID Log ID
Reason Reason message

show log power


Displays the following electric power history items for the server chassis and
server blades:
For the server chassis:
• Date and time when the power supply status of the chassis was collected
• Moving average value for electric power consumption (AC) for the past
three minutes
• Highest value for electric power consumption (AC) within the past three
minutes
• Lowest value for electric power consumption (AC) within the past three
minutes
• Integrated value for electric power consumption (AC) for the past three
minutes
• Moving average value for electric power consumption (DC) for the past
three minutes
• Upper limit of electric power consumption set by the APC
• Highest value for the upper limit of electric power consumption set by the
APC within the past three minutes
• Lowest value for the upper limit of electric power consumption set by the
APC within the past three minutes
• Air flow
• Intake temperature
For server blades:
• Date and time when the power supply status for the server blade was
collected
• Moving average value for electric power consumption (DC) for the past
three minutes
• Upper limit of electric power consumption set by the APC
• Highest value for the upper limit of electric power consumption set by the
APC within the past three minutes

5-248 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
• Lowest value for the upper limit of electric power consumption set by the
APC within the past three minutes
• CPU frequency (average)
• CPU frequency (maximum)
• Highest value for electric power consumption (DC) within the past three
minutes
• Lowest value for electric power consumption (DC) within the past three
minutes
In an SMP configuration, if you specify a primary server blade, the electric
power value items display the sum of the values for all server blades
constituting the SMP configuration, and the CPU frequency items display the
record of primary server blades. If you specify a non-primary server blade,
the electric power value items display -------, and the CPU frequency items
display the record of non-primary server blades.

Syntax
show log power -m <log_power_module> [-b <blade_no>] [-t
<log_power_trend>]

Privilege
Chassis privilege

Parameters
-m <log_power_module>
Type of module whose power supply status history data is to be displayed
¢ chassis: Server chassis
¢ blade: Server blade
-b <blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-t <log_power_trend>
Time period for which to display log data
¢ last: Displays log history data for the last 24 hours.
¢ yesterday: Displays log history data for the 24 hours of the previous
day.
¢ If you omit this parameter: Displays the log history data from 0:00 of
the previous day to the current time.

Commands That Can Be Executed From the CLI Console 5-249


Hitachi Compute Blade 2500 Series Management Module User Guide
Execution example
To display the log history data for the power supply status of the server
chassis:
show log power -m chassis

To display the log history data for the power supply status of server blade 1:
show log power -m blade -b 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-181 Chassis power monitoring log

Displayed item Description


Date Date and time when the power supply status of
the chassis was collected
ac_ave Moving average value for electric power
consumption (AC) for the past three minutes
ac_max Highest value for electric power consumption
(AC) within the past three minutes
ac_min Lowest value for electric power consumption
(AC) within the past three minutes
ac_sum Integrated value for electric power consumption
(AC) for the past three minutes
dc_ave Moving average value for electric power
consumption (DC) for the past three minutes
apc_up Upper limit of electric power consumption set
by the APC
apc_max Highest value for the upper limit of electric
power consumption set by the APC within the
past three minutes
apc_min Lowest value for the upper limit of electric
power consumption set by the APC within the
past three minutes
airflow Air flow
in_temp Intake temperature

Table 5-182 Blade <slot> power monitoring log

Displayed item Description


Date Date and time when the power supply status
for the server blade was collected
dc_ave Moving average value for electric power
consumption (DC) for the past three minutes

5-250 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
apc_up Upper limit of electric power consumption set
by the APC
apc_max Highest value for the upper limit of electric
power consumption set by the APC within the
past three minutes
apc_min Lowest value for the upper limit of electric
power consumption set by the APC within the
past three minutes
ave_frq CPU frequency (average)
max_frq CPU frequency (maximum)
dc_max Highest value for electric power consumption
(DC) within the past three minutes
dc_min Lowest value for electric power consumption
(DC) within the past three minutes

show log sel


Displays the following items of the system event log (SEL):
• Sequence number
• Time stamp
• SEL level
• Module
• XID
• Code
• Message
In an SMP configuration, the numbers of each server blade where SEL entries
are generated are displayed for Module.

Syntax
show log sel [-f <filter>] [-l <level>]

Privilege
Chassis privilege

Parameters
-f <filter>
Filter
¢ B: All server blades
¢ Bn: One server blade (n is a number from 1 to 15.)

Commands That Can Be Executed From the CLI Console 5-251


Hitachi Compute Blade 2500 Series Management Module User Guide
¢ M: All management modules
¢ Mn: One management module (n is 1 or 2.)
¢ SW: All switch modules
¢ SWn: One switch module (n is 1 or 2.)
¢ FAN: All fan modules
¢ FANn: One fan module (n is a number from 1 to 10.)
¢ PS: All power supply modules
¢ PSn: One power supply module (n is a number from 1 to 6.)
¢ MLAN: All management LAN modules.
¢ MLANn: One management LAN module (n is 1 or 2.)
¢ FANCTRL: All fan control modules
¢ FANCTRLn: One fan control module (n is 1 or 2.)
-l <level>
SEL level
¢ 0: All levels
¢ 1: CAUTION, WARNING, and FAIL levels
¢ 2: WARNING and FAIL levels
¢ 3: FAIL level

Execution example
To display system event log (SEL) data:
show log sel

To display system event log (SEL) data for server blade 1:


show log sel -f B1

To display system event log (SEL) data for all server blades:
show log sel -f B

To display FAIL-level system event log (SEL) data:


show log sel -l 3

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-183 System event log

Displayed item Description


Seq Sequence number
Timestamp Registration time
Level SEL level

5-252 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
• Info: Information level
• Caution: Caution level
• WARNING: Warning level
• FAIL: Fail level
Module Module
• Bn: Server blade (n is a number from 1 to
15).
• Mn: Management module (n is a number 1
or 2).
• SWn: Switch module (n is a number 1 or 2).
• FANn: Fan module (n is a number from 1 to
10).
• PSn: Power supply module (n is a number
from 1 to 6).
• MLANn: Management LAN module (n is a
number 1 or 2).
• FANCTRLn: Fan control module (n is a
number 1 or 2).
XID XID
System event log Code
Message Message
The maximum length is 255 characters.

show log svpsts


Displays the SVP status.

Syntax
show log svpsts [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To display the SVP status:
show log svpsts

Commands That Can Be Executed From the CLI Console 5-253


Hitachi Compute Blade 2500 Series Management Module User Guide
show log wwn-edit
Displays the following items of the Optional Physical WWN change log:
• Time when the log was collected
• Information about the port whose WWN was changed (server blade
number, card number, and port number on the card).
• Type (WWNN or WWPN) of the changed WWN
• WWNs before and after the change
• Source of the change request

Syntax
show log wwn-edit

Privilege
Chassis privilege

Parameters
None

Execution example
To display the Optional Physical WWN change log:
show log wwn-edit

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-184 Execution results of the command show log wwn-edit

Displayed item Description


Timestamp Time when the log was collected
P Server blade slot number
This is a value from 1 to 15.
In an SMP configuration, this item displays the
slot numbers for primary server blades.
S Server blade slot number
This is a value from 1 to 15.
Card Card type
• MCx: Mezzanine card x is the card slot
number.
• IOxx: I/O adapter. xx is the slot number for
the I/O adapter.

5-254 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Displayed item Description
Port Port number on the card
WWN WWN type
• wwnn : World Wide Node Name
• wwpn : World Wide Port Name
Before WWN before the change
After WWN after the change
From Source of the change request
• hcsmx: Change request from HCSM. x is
the HCSM number.
• console: Change request from the console

Commands to obtain backups


This section describes the commands to obtain backups.

restore blade bmc


Restores the BMC settings to a server blade by using the backup data stored
in the management modules.
By specifying the number of a bank in which the backup is stored, you can
restore the backup of the generation.
Regardless of whether the specified server blade constitutes an SMP
configuration, the BMC settings for the specified server blade are restored.

Syntax
restore blade bmc <blade_no> -n <bank_no> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
Specify a value from 1 to 15. You cannot specify multiple values.
-n <bank_no>
Saving bank number
Specify a value from 0 to 4.
-F

Commands That Can Be Executed From the CLI Console 5-255


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To restore the BMC settings of server blade 1:
restore blade bmc 1 -n 0

restore blade efi


Restores the UEFI settings to a server blade by using the backup data stored
in the management modules.
By specifying the number of the bank where the backup is stored, you can
restore the backup data for that generation.
Regardless of whether the specified server blade constitutes an SMP
configuration, the UEFI settings for the specified server blade are restored.

Syntax
restore blade efi <blade_no> -n <bank_no> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
Specify a value from 1 to 15. You cannot specify multiple values.
-n <bank_no>
Saving bank number
Specify a value from 0 to 4.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To restore the UEFI settings of server blade 1:
restore blade efi 1 -n 0

restore blade fc-hba


Restores the Hitachi Fibre Channel adapter settings for the I/O adapter to be
connected to a server blade, by using the backup data stored in the
management modules.

5-256 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
By specifying the number of a bank in which the backup is stored, you can
restore the backup of the generation.
When a Hitachi Fibre Channel adapter (8 Gb or 16 Gb) is installed, you can
perform the restoration.
For the Hitachi Fibre Channel adapter:
Depending on the server blade number, the range of specifiable I/O
adapter numbers varies as shown below. If you specify the number of an
I/O adapter that is not to be connected to the server blade, the
restoration is not performed.

Server blade Half-width blade slot


Full-width blade slot number
number number

1 01A, 01B 01A, 01B, 02A, 02B

2 02A, 02B --

3 03A, 03B 03A, 03B, 04A, 04B

4 04A, 04B --

: : :
: : :

13 13A, 13B 13A, 13B, 14A, 14B

14 14A, 14B --

15 Cannot be specified. Cannot be specified.

Syntax
restore blade fc-hba <blade_no> -i <iobd_no> -n <bank_no> [-F]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
Specify a value from 1 to 15. You cannot specify multiple values.
-i <iobd_no>
I/O adapter number
Specify a value from 01A to 14B. You cannot specify multiple values.
-n <bank_no>
Saving bank number
Specify a value from 0 to 4.
-F

Commands That Can Be Executed From the CLI Console 5-257


Hitachi Compute Blade 2500 Series Management Module User Guide
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To restore the I/O adapter HBA settings of server blade 1 by using the
backup data stored in bank 2:
$ restore blade fc-hba 1 -i 01A -n 2
Confirm? (y/[n]):y
I0045 : <Blade 1> Restore was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$

restore factory
Restores the management module settings to their initial settings (the
settings at shipping time).

Syntax
restore factory [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To restore the management module settings to their initial settings (the
setting at shipping time):
restore factory

show blade bmc backup


Displays the backup data of the BMC settings for a server blade. All
generations are displayed. A maximum of five backups are automatically
saved in the management modules.
The following items are displayed:
• Saving bank number
• Saving time

5-258 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Regardless of whether the specified server blades constitute an SMP
configuration, the backup data of the BMC settings for specified server blades
is displayed.

Syntax
show blade bmc backup [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the saving status of the BMC settings for server blade 1:
show blade bmc backup 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-185 Blade bmc backup info

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Bank<number> Saving time
The format is YYYY/MM/DD hh:mm:ss.
<number> is the saving bank number.
This is a value from 0 to 4.

show blade efi backup


Displays the backup data of the UEFI settings for a server blade. All
generations are displayed. A maximum of five backups are automatically
saved in the management modules.
The following items are displayed:
• Saving bank number
• Saving time

Commands That Can Be Executed From the CLI Console 5-259


Hitachi Compute Blade 2500 Series Management Module User Guide
Regardless of whether the specified server blades constitute an SMP
configuration, the backup data of the UEFI settings for specified server blades
is displayed.

Syntax
show blade efi backup [<blade_no>]

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.

Execution example
To display the saving status of the UEFI settings for server blade 1:
show blade efi backup 1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-186 Blade efi backup info

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
Bank<number> Saving time
The format is YYYY/MM/DD hh:mm:ss.
<number> is the saving bank number.
This is a value from 0 to 4.

show blade fc-hba backup


Displays the backup data for the settings of the Hitachi Fibre Channel board
installed in the I/O adapter to be connected to a server blade. All generations
are displayed. A maximum of five backups are automatically saved in the
management modules.
The following items are displayed:
• Saving bank number

5-260 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
• Saving time
The above items can be displayed when a Hitachi Fibre Channel adapter (8
Gb or 16 Gb) is installed.
Regardless of whether the specified server blades constitute an SMP
configuration, the backup data of the I/O adapter that is to be connected to
the specified server blades is displayed.
For the Hitachi Fibre Channel adapter:
Depending on the server blade number, the range of specifiable I/O
adapter numbers varies as shown below. If you specify the number of an
I/O adapter that is not to be connected to the server blade, backup data
is not displayed.

Server blade Half-width blade slot


Full-width blade slot number
number number

1 01A, 01B 01A, 01B, 02A, 02B

2 02A, 02B --

3 03A, 03B 03A, 03B, 04A, 04B

4 04A, 04B --

: : :
: : :

13 13A, 13B 13A, 13B, 14A, 14B

14 14A, 14B --

15 Cannot be specified. Cannot be specified.

Syntax
show blade fc-hba backup [<blade_no>] -i <iobd_no>

Privilege
Server blade privileges

Parameters
<blade_no>
Server blade number
You can specify a value from 1 to 15. You can specify multiple values.
If you specify all or omit this parameter, command processing is
performed for all server blades.
-i <iobd_no>
I/O adapter number
You can specify a value from 01A to 14B. You can specify multiple values
separated by commas. You cannot specify all. You cannot omit this
parameter.

Commands That Can Be Executed From the CLI Console 5-261


Hitachi Compute Blade 2500 Series Management Module User Guide
If you specify the number of an I/O adapter that is not to be connected to
the server blade, backup data is not displayed.

Execution example
To display the saving status of the HBA settings for I/O adapter 01A that is to
be connected to server blade 1:
$ show blade fc-hba backup 1 -i 01A
-- Blade fc-hba backup info --
Slot : 1
IOBD : 01A
Bank 0 : 2009/01/26 08:00:27
Bank 1 : 2009/01/27 18:08:44
Bank 2 : 2009/01/28 09:45:30
Bank 3 : 2009/01/29 22:03:57
Bank 4 : 2009/01/30 20:26:49
S0002 : Command succeeded.
S0000 : Command was finished.
$

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-187 Blade fc-hba backup info

Displayed item Description


Slot Server blade number
This is a value from 1 to 15.
IOBD The number of the I/O adapter to be connected
to the server blade
This is a value from 01A to 14B.
This item is displayed for I/O adapter backup
data.
Bank<number> Saving time
The format is YYYY/MM/DD hh:mm:ss.
<number> is the saving bank number.
This is a value from 0 to 4.

Rules
Because Hitachi Fibre Channel mezzanine cards cannot be installed, you
cannot specify a mezzanine card.

Commands for console management


This section describes the commands that are used to configure settings and
for end processing for the console.

5-262 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
change console
Changes the connection destination of the console to a switch module or to
the OS console.
In an SMP configuration, specify a primary server blade. The OS console for
the primary server blade is connected.

Syntax
change console {-s <sw_no>¦-b <blade_no>} [-F]

Privilege
Connection to a switch module: Switch module privilege
Connection to a server blade: Server blade privilege

Parameters
-s <sw_no>
Switch module number
Specify a value 1 or 2.
You cannot specify multiple values.
-b<blade_no>
Server blade number
Specify a value from 1 to 15. You cannot specify multiple values.
Specify this parameter to connect the console to the OS console of the
server blade.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To change the connection destination of the console to the OS console of
server blade 1:
change console -b 1

To change the connection destination of the console to switch module 1:


change console -s 1

Rules
• In an SMP configuration, if you specify a non-primary server blade, the
following message appears and the OS console is not connected:
E0640 : <Blade %1$d> Command was canceled. Specified blade is
not the primary blade of SMP.
• The user who denies permission to execute remote consoles and OS
consoles cannot connect the OS console for server blades.

Commands That Can Be Executed From the CLI Console 5-263


Hitachi Compute Blade 2500 Series Management Module User Guide
exit
Ends the CLI console.

Syntax
exit

Privilege
All privileges

Parameters
None

Execution example
To end the CLI console:
exit

set web-console function


Specifies whether to enable use of the Web console.
Set the following items:
• Whether to enable use of the Web console from the management LAN
Set whether to enable use of the Web console when the system console is
connected to management LAN port 1 (MGMT1) or management LAN port
2 (MGMT2) for management modules.
• Whether to enable use of the Web console from the maintenance LAN
Set whether to enable use of the Web console when the system console is
connected to the maintenance LAN port (MAINT) for management
modules.

Syntax
set web-console function [-mg <function>] [-mn <function>] [-F]

Privilege
Chassis privilege

Parameters
-mg <function>
Specifies whether to enable use of the Web console from the
management LAN.
¢ enable: Enabled.
¢ disable: Disabled.

5-264 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
-mn <function>
Specifies whether to enable use of the Web console from the maintenance
LAN.
¢ enable: Enabled.
¢ disable: Disabled.
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To disable use of the Web console from the management LAN:
set web-console function -mg disable

Rules
If use of the Web console is disabled, users cannot newly log in to the Web
console. Users who are currently logged in can continue to use the Web
console until they log out.

show web-console function


Displays whether use of the Web console is enabled.
The following items are displayed:
• Whether to enable use of the Web console from the management LAN
• Whether to enable use of the Web console from the maintenance LAN

Syntax
show web-console function

Privilege
Chassis privilege

Parameters
None

Execution example
To display whether use of the Web console is enabled:
show web-console function

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Commands That Can Be Executed From the CLI Console 5-265


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-188 Web console functionality

Displayed item Description


Web console (mgmt-lan) Whether to enable use of the Web console from the
management LAN
• enable: Enabled.
• disable: Disabled.
Web console (mnt-lan) Whether to enable use of the Web console from the
maintenance LAN
• enable: Enabled.
• disable: Disabled.

Commands to identify parts


This section describes the commands to manage the part name identification
database.

show parts-db list


Displays the list of unit mnemonics used in the part name identification
database.

Syntax
show parts-db list

Privilege
Chassis privilege

Parameters
None

Execution example
To display data from the part name identification database:
show parts-db list

Execution results
The following table shows the items that are displayed as the execution
results of this command.

5-266 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
Table 5-189 Parts DB

Displayed item Description


Unit Unit mnemonic used in the part name identification
database

show parts-db unit


Displays unit information from the part name identification database.

Syntax
show parts-db unit -m <pdb_unit_mnemonic>

Privilege
Chassis privilege

Parameters
-m <pdb_unit_mnemonic>
Unit mnemonic used in the part name identification database

Execution example
To display information about the SRV1 unit from the part name identification
database:
show parts-db unit -m SRV1

Execution results
The following table shows the items that are displayed as the execution
results of this command.

Table 5-190 Parts DB unit information

Displayed item Description


Status Installation status of the component
• installed: Installed.
• not installed: Not installed.
Mnemonic FRU mnemonic
Name Part name
Drawing number Component code
Serial number Serial number

Commands That Can Be Executed From the CLI Console 5-267


Hitachi Compute Blade 2500 Series Management Module User Guide
update parts-db
Updates the part name identification database.

Syntax
update parts-db [-F]

Privilege
Chassis privilege

Parameters
-F
Specify this parameter to execute the command without displaying a
confirmation dialog box. You can omit this parameter.

Execution example
To update the part name identification database:
update parts-db

5-268 Commands That Can Be Executed From the CLI Console


Hitachi Compute Blade 2500 Series Management Module User Guide
A
Software license information
This appendix describes software license information of management module.

□ Software license information

Software license information A-1


Hitachi Compute Blade 2500 Series Management Module User Guide
Software license information
The management module firmware uses the software developed or created
by Hitachi and the open-source software below in accordance with the
software license agreement for each open-source software product. For
details on the open-source software used in the management module
firmware and the license agreement for the open-source software, see the
table below.
In response to customer requests, Hitachi provides the customers with
recording media (CD-ROM or DVD) that contains the source code of the
software licensed under the license agreement conditions that impose an
obligation to provide the source code, such as the conditions of the GNU
General Public License (GPL). Please note that we charge customers for the
cost of the recording media, shipping fees, and service charges. When
requesting the source code, check the version of the management module
firmware via a management module console and provide this information to
our sales personnel when asking for assistance.
For the following open-source software, contact our sales personnel for
assistance.

Table A-1 Open-source software

Software
Software license agreement
name

acl GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

alsa-lib GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

apr Apache License Version 2.0


For details on the license, access the following page:
http://www.apache.org/licenses/

Apache Portable Runtime


Copyright (c) 2009 The Apache Software Foundation.

This product includes software developed by The Apache Software


Foundation (http://www.apache.org/).

Portions of this software were developed at the National Center for


Supercomputing Applications (NCSA) at the University of Illinois at
Urbana-Champaign.

This software contains code derived from the RSA Data Security Inc. MD5
Message-Digest Algorithm.

This software contains code derived from UNIX V7, Copyright(C)


Caldera International Inc.

apr-util Apache License Version 2.0

A-2 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
For details on the license, access the following page:
http://www.apache.org/licenses/

Apache Portable Runtime Utility Library


Copyright (c) 2009 The Apache Software Foundation.

This product includes software developed by


The Apache Software Foundation (http://www.apache.org/).

Portions of this software were developed at the National Center for


Supercomputing Applications (NCSA) at the University of Illinois at
Urbana-Champaign.

This software contains code derived from the RSA Data Security Inc. MD5
Message-Digest Algorithm, including various modifications by Spyglass
Inc., Carnegie Mellon University, and Bell Communications Research, Inc
(Bellcore).

arptables_jf GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

atk GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

attr GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

audit GNU General Public License version2


GNU Lesser General Public License version2.1
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/lgpl-2.1.html

augeas GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

autoconf GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

automake GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

avahi GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

Software license information A-3


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

bash GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

bind GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

busybox GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

bzip2 This program, "bzip2", the associated library "libbzip2", and all
documentation, are copyright (C) 1996-2007 Julian R Seward. All rights
reserved.

Redistribution and use in source and binary forms, with or without


modification, are permitted provided that the following conditions are
met:

1. Redistributions of source code must retain the above copyright notice,


this list of conditions and the following disclaimer.

2. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software in a
product, an acknowledgment in the product documentation would be
appreciated but is not required.

3. Altered source versions must be plainly marked as such, and must not
be misrepresented as being the original software.

4. The name of the author may not be used to endorse or promote


products derived from this software without specific prior written
permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY


EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Julian Seward,[email protected]
bzip2/libbzip2 version 1.0.5 of 10 December 2007

cairo GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

cdrkit GNU General Public License version2

A-4 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

checkpolicy GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

chkconfig GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

cloog GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

coreutils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

cracklib GNU Lesser General Public License version2.1


For details on the license, access the following page:
http://www.gnu.org/licenses/lgpl-2.1.html

cups GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

cURL COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1996 - 2009, Daniel Stenberg, <[email protected]>.

All rights reserved.

Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY


KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO
EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall


not be used in advertising or otherwise to promote the sale, use or other
dealings in this Software without prior written authorization of the
copyright holder.

cyrus-sasl CMU libsasl


Tim Martin
Rob Earhart

Software license information A-5


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Rob Siemborski

Copyright (c) 1998-2003 Carnegie Mellon University. All rights reserved.

Redistribution and use in source and binary forms, with or without


modification, are permitted provided that the following conditions are
met:

1. Redistributions of source code must retain the above copyright notice,


this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright


notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

3. The name "Carnegie Mellon University" must not be used to endorse or


promote products derived from this software without prior written
permission. For permission or any other legal details, please contact
Office of Technology Transfer
Carnegie Mellon University
5000 Forbes Avenue
Pittsburgh, PA 15213-3890
(412) 268-4387, fax: (412) 268-7395
[email protected]

4. Redistributions of any form whatsoever must retain the following


acknowledgment: "This product includes software developed by
Computing Services at Carnegie Mellon University (http://www.cmu.edu/
computing/)."

CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH


REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE
MELLON UNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.

db4 GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

dbus-glib GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

ISC dhcp Copyright (c) 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
Copyright (c) 1995-2003 by Internet Software Consortium

Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

A-6 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.

Internet Systems Consortium, Inc.


950 Charter Street
Redwood City, CA 94063
<[email protected]>
https://www.isc.org/

docbook- GNU General Public License version2


dtds For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

docbook- GNU General Public License version2


style-dsssl For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

docbook- GNU General Public License version2


style-xsl For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

docbook-utils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

dosfsutils GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

dracut GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

e2fsprogs GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

efiver GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

elfutils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

Software license information A-7


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

ethtool GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

expat Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
and Clark Cooper
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Expat maintainers.

Permission is hereby granted, free of charge, to any person obtaining a


copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY


KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

findutils GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

fuse-sshfs GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

gamin GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

gdbm GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

giflib GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

glib2 GNU Library General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

glibc GNU General Public License version2


GNU Lesser General Public License version2.1

A-8 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/lgpl-2.1.html

GMP GNU General Public License version2


GNU Lesser General Public License version3
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/lgpl.html

GnuTLS GNU General Public License version2


GNU Lesser General Public License version3
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/lgpl.html

groff GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

grubby GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

gtk2 GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

gtk-doc GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

gzip GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

hicolor-icon- GNU General Public License version2


theme For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

httpd Apache License Version 2.0


For details on the license, access the following page:
http://www.apache.org/licenses/

Apache HTTP Server


Copyright 2012 The Apache Software Foundation.

This product includes software developed at The Apache Software


Foundation (http://www.apache.org/).

Software license information A-9


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Portions of this software were developed at the National Center for
Supercomputing Applications (NCSA) at the University of Illinois at
Urbana-Champaign.

This software contains code derived from the RSA Data Security Inc. MD5
Message-Digest Algorithm, including various modifications by Spyglass
Inc., Carnegie Mellon University, and Bell Communications Research, Inc
(Bellcore).

Regular expression support is provided by the PCRE library package,


which is open source software, written by Philip Hazel, and copyright by
the University of Cambridge, England. The original software is available
from
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

hwdata GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

initscripts GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

iproute GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

iptables GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

iputils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

keyutils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

krb5 Copyright (C) 1985-2012 by the Massachusetts Institute of Technology.


All rights reserved.
Export of software employing encryption from the United States of
America may require a specific license from the United States
Government. It is the responsibility of any person or organization
contemplating export to obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
distribute this software for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and
that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of M.I.T. not be used in
advertising or publicity pertaining to distribution of the software without
specific, written prior permission. Furthermore if you modify this software

A-10 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
you must label your software as modified software and not distribute it in
such a fashion that it might be confused with the original MIT software.
M.I.T. makes no representations about the suitability of this software for
any purpose. It is provided "as is" without express or implied warranty.
Documentation components of this software distribution are licensed
under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
(`http://creativecommons.org/licenses/by-sa/3.0/') Individual
source code files are copyright MIT, Cygnus Support, Novell, OpenVision
Technologies, Oracle, Red Hat, Sun Microsystems, FundsXpress, and
others.
Project Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos, Moira,
and Zephyr are trademarks of the Massachusetts Institute of Technology
(MIT). No commercial use of these trademarks may be made without prior
written permission of MIT.
"Commercial use" means use of a name in a product or other for-profit
manner. It does NOT prevent a commercial firm from referring to the MIT
trademarks in order to convey information (although in doing so,
recognition of their trademark status should be given).
-------------------
The following copyright and permission notice applies to the OpenVision
Kerberos Administration system located in `kadmin/create', `kadmin/
dbutil', `kadmin/passwd', `kadmin/server', `lib/kadm5', and portions of
`lib/rpc':
Copyright, OpenVision Technologies, Inc., 1993-1996, All Rights Reserved
WARNING: Retrieving the OpenVision Kerberos Administration system
source code, as described below, indicates your acceptance of the
following terms. If you do not agree to the following terms, do not
retrieve the OpenVision Kerberos administration system.
You may freely use and distribute the Source Code and Object Code
compiled from it, with or without modification, but this Source Code is
provided to you "AS IS" EXCLUSIVE OF ANY WARRANTY, INCLUDING,
WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE, OR ANY OTHER WARRANTY,
WHETHER EXPRESS OR IMPLIED. IN NO EVENT WILL OPENVISION HAVE
ANY LIABILITY FOR ANY LOST PROFITS, LOSS OF DATA OR COSTS OF
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY
SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF
THIS AGREEMENT, INCLUDING, WITHOUT LIMITATION, THOSE
RESULTING FROM THE USE OF THE SOURCE CODE, OR THE FAILURE OF
THE SOURCE CODE TO PERFORM, OR FOR ANY OTHER REASON.
OpenVision retains all copyrights in the donated Source Code. OpenVision
also retains copyright to derivative works of the Source Code, whether
created by OpenVision or by a third party. The OpenVision copyright
notice must be preserved if derivative works are made based on the
donated Source Code.
OpenVision Technologies, Inc. has donated this Kerberos Administration
system to MIT for inclusion in the standard Kerberos 5 distribution. This
donation underscores our commitment to continuing Kerberos technology
development and our gratitude for the valuable work which has been
performed by MIT and the Kerberos community.
-------------------

Software license information A-11


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Portions contributed by Matt Crawford `<[email protected]>' were work
performed at Fermi National Accelerator Laboratory, which is operated by
Universities Research Association, Inc., under contract DE-
AC02-76CHO3000 with the U.S. Department of Energy.
-------------------
Portions of `src/lib/crypto' have the following copyright:
Copyright (C) 1998 by the FundsXpress, INC.
All rights reserved.
Export of this software from the United States of America may require a
specific license from the United States Government. It is the responsibility
of any person or organization contemplating export to obtain such a
license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation, and that the name
of FundsXpress. not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
FundsXpress makes no representations about the suitability of this
software for any purpose. It is provided "as is" without express or implied
warranty.
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
-------------------
The implementation of the AES encryption algorithm in `src/lib/crypto/
builtin/aes' has the following copyright:
Copyright (C) 2001, Dr Brian Gladman `<[email protected]>',
Worcester, UK. All rights reserved.
LICENSE TERMS
The free distribution and use of this software in both source and binary
form is allowed (with or without changes) provided that:
1. distributions of this source code include the above copyright notice, this
list of conditions and the following disclaimer;
2. distributions in binary form include the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or
other associated materials;
3. the copyright holder's name is not used to endorse products built using
this software without specific written permission.
DISCLAIMER
This software is provided 'as is' with no explcit or implied warranties in
respect of any properties, including, but not limited to, correctness and
fitness for purpose.
-------------------
Portions contributed by Red Hat, including the pre-authentication plug-in
framework and the NSS crypto implementation, contain the following
copyright:

A-12 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright (C) 2006 Red Hat, Inc. Portions copyright (C) 2006
Massachusetts Institute of Technology All Rights Reserved. Redistribution
and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of Red Hat, Inc., nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------
The bundled verto source code is subject to the following license:
Copyright 2011 Red Hat, Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-------------------
The implementations of GSSAPI mechglue in GSSAPI-SPNEGO in `src/lib/
gssapi', including the following files:
lib/gssapi/generic/gssapi_err_generic.et
lib/gssapi/mechglue/g_accept_sec_context.c
lib/gssapi/mechglue/g_acquire_cred.c
lib/gssapi/mechglue/g_canon_name.c

Software license information A-13


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
lib/gssapi/mechglue/g_compare_name.c
lib/gssapi/mechglue/g_context_time.c
lib/gssapi/mechglue/g_delete_sec_context.c
lib/gssapi/mechglue/g_dsp_name.c
lib/gssapi/mechglue/g_dsp_status.c
lib/gssapi/mechglue/g_dup_name.c
lib/gssapi/mechglue/g_exp_sec_context.c
lib/gssapi/mechglue/g_export_name.c
lib/gssapi/mechglue/g_glue.c
lib/gssapi/mechglue/g_imp_name.c
lib/gssapi/mechglue/g_imp_sec_context.c
lib/gssapi/mechglue/g_init_sec_context.c
lib/gssapi/mechglue/g_initialize.c
lib/gssapi/mechglue/g_inquire_context.c
lib/gssapi/mechglue/g_inquire_cred.c
lib/gssapi/mechglue/g_inquire_names.c
lib/gssapi/mechglue/g_process_context.c
lib/gssapi/mechglue/g_rel_buffer.c
lib/gssapi/mechglue/g_rel_cred.c
lib/gssapi/mechglue/g_rel_name.c
lib/gssapi/mechglue/g_rel_oid_set.c
lib/gssapi/mechglue/g_seal.c
lib/gssapi/mechglue/g_sign.c
lib/gssapi/mechglue/g_store_cred.c
lib/gssapi/mechglue/g_unseal.c
lib/gssapi/mechglue/g_userok.c
lib/gssapi/mechglue/g_utils.c
lib/gssapi/mechglue/g_verify.c
lib/gssapi/mechglue/gssd_pname_to_uid.c
lib/gssapi/mechglue/mglueP.h
lib/gssapi/mechglue/oid_ops.c
lib/gssapi/spnego/gssapiP_spnego.h
lib/gssapi/spnego/spnego_mech.c
and the initial implementation of incremental propagation, including the
following new or changed files:
include/iprop_hdr.h
kadmin/server/ipropd_svc.c
lib/kdb/iprop.x lib/kdb/kdb_convert.c
lib/kdb/kdb_log.c lib/kdb/kdb_log.h
lib/krb5/error_tables/kdb5_err.et
slave/kpropd_rpc.c
slave/kproplog.c

A-14 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
are subject to the following license:
Copyright (C) 2004 Sun Microsystems, Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Kerberos V5 includes documentation and software developed at the
University of California at Berkeley, which includes this copyright notice:
Copyright (C) 1983 Regents of the University of California.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
-------------------
Portions contributed by Novell, Inc., including the LDAP database
backend, are subject to the following license:
Copyright (C) 2004-2005, Novell, Inc.
All rights reserved.

Software license information A-15


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* The copyright holder's name is not used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------
Portions funded by Sandia National Laboratory and developed by the
University of Michigan's Center for Information Technology Integration,
including the PKINIT implementation, are subject to the following license:
COPYRIGHT (C) 2006-2007
THE REGENTS OF THE UNIVERSITY OF MICHIGAN
ALL RIGHTS RESERVED
Permission is granted to use, copy, create derivative works and
redistribute this software and such derivative works for any purpose, so
long as the name of The University of Michigan is not used in any
advertising or publicity pertaining to the use of distribution of this
software without specific, written prior authorization. If the above
copyright notice or any other identification of the University of Michigan is
included in any copy of any portion of this software, then the disclaimer
below must also be included.
THIS SOFTWARE IS PROVIDED AS IS, WITHOUT REPRESENTATION FROM
THE UNIVERSITY OF MICHIGAN AS TO ITS FITNESS FOR ANY PURPOSE,
AND WITHOUT WARRANTY BY THE UNIVERSITY OF MICHIGAN OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE REGENTS OF THE UNIVERSITY OF MICHIGAN
SHALL NOT BE LIABLE FOR ANY DAMAGES, INCLUDING SPECIAL,
INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WITH RESPECT
TO ANY CLAIM ARISING OUT OF OR IN CONNECTION WITH THE USE OF
THE SOFTWARE, EVEN IF IT HAS BEEN OR IS HEREAFTER ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
-------------------
The pkcs11.h file included in the PKINIT code has the following license:

A-16 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright 2006 g10 Code GmbH
Copyright 2006 Andreas Jellinghaus
This file is free software; as a special exception the author gives unlimited
permission to copy and/or distribute it, with or without modifications, as
long as this notice is preserved.
This file is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY, to the extent permitted by law; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Portions contributed by Apple Inc. are subject to the following license:
Copyright 2004-2008 Apple Inc.
All Rights Reserved.
Export of this software from the United States of America may require a
specific license from the United States Government. It is the responsibility
of any person or organization contemplating export to obtain such a
license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation, and that the name
of Apple Inc. not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
Apple Inc. makes no representations about the suitability of this software
for any purpose. It is provided "as is" without express or implied
warranty.
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
The implementations of UTF-8 string handling in src/util/support and
src/lib/krb5/unicode are subject to the following copyright and permission
notice:
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation
("Software"), with or without modification, are permitted provided that
the following conditions are met:
1. Redistributions in source form must retain copyright statements and
notices,
2. Redistributions in binary form must reproduce applicable copyright
statements and notices, this list of conditions, and the following disclaimer
in the documentation and/or other materials provided with the
distribution, and
3. Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each
revision is distinguished by a version number. You may use this Software
under terms of this license revision or under the terms of any subsequent
revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS
CONTRIBUTORS "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES,

Software license information A-17


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITS
CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The names of the authors and copyright holders must not be used in
advertising or otherwise to promote the sale, use or other dealing in this
Software without specific, written prior permission. Title to copyright in
this Software shall at all times remain with copyright holders.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
Copyright 1999-2003 The OpenLDAP Foundation, Redwood City,
California, USA. All Rights Reserved. Permission to copy and distribute
verbatim copies of this document is granted.
Marked test programs in src/lib/krb5/krb have the following copyright:
Copyright (C) 2006 Kungliga Tekniska Hogskolan
(Royal Institute of Technology, Stockholm, Sweden).
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of KTH nor the names of its contributors may be used
to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY KTH AND ITS CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL KTH OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
-------------------
Portions of the RPC implementation in src/lib/rpc and src/include/gssrpc
have the following copyright and permission notice:

A-18 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright (C) 2010, Oracle America, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the "Oracle America, Inc." nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------
Copyright (C) 2006,2007,2009 NTT (Nippon Telegraph and Telephone
Corporation). All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer as the first lines of this
file unmodified.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY NTT "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL NTT BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
-------------------

Software license information A-19


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright 2000 by Carnegie Mellon University
All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in supporting
documentation, and that the name of Carnegie Mellon University not be
used in advertising or publicity pertaining to distribution of the software
without specific, written prior permission.
CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE
MELLON UNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
-------------------
Copyright (C) 2002 Naval Research Laboratory (NRL/CCS)
Permission to use, copy, modify and distribute this software and its
documentation is hereby granted, provided that both the copyright notice
and this permission notice appear in all copies of the software, derivative
works or modified versions, and any portions thereof.
NRL ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION
AND DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
-------------------
Portions extracted from Internet RFCs have the following copyright notice:
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions contained
in BCP 78, and except as set forth therein, the authors retain all their
rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY
AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-------------------
Copyright (C) 1991, 1992, 1994 by Cygnus Support.
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in supporting
documentation. Cygnus Support makes no representations about the
suitability of this software for any purpose. It is provided "as is" without
express or implied warranty.
-------------------

A-20 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright (C) 2006 Secure Endpoints Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-------------------
Portions of the implementation of the Fortuna-like PRNG are subject to
the following notice:
Copyright (C) 2005 Marko Kreen
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
Copyright (C) 1994 by the University of Southern California
EXPORT OF THIS SOFTWARE from the United States of America may
require a specific license from the United States Government. It is the
responsibility of any person or organization contemplating export to
obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to copy, modify, and distribute
this software and its documentation in source and binary forms is hereby

Software license information A-21


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
granted, provided that any documentation or other materials related to
such distribution or use acknowledge that the software was developed by
the University of Southern California.
DISCLAIMER OF WARRANTY. THIS SOFTWARE IS PROVIDED "AS IS". The
University of Southern California MAKES NO REPRESENTATIONS OR
WARRANTIES, EXPRESS OR IMPLIED. By way of example, but not
limitation, the University of Southern California MAKES NO
REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE. The University of Southern California
shall not be held liable for any liability nor for any direct, indirect, or
consequential damages with respect to any claim by the user or
distributor of the ksu software.
-------------------
Copyright (C) 1995 The President and Fellows of Harvard University
This code is derived from software contributed to Harvard by Jeremy
Rassen.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by the University of California,
Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
-------------------
Copyright (C) 2008 by the Massachusetts Institute of Technology.
Copyright 1995 by Richard P. Basch. All Rights Reserved.
Copyright 1995 by Lehman Brothers, Inc. All Rights Reserved.
Export of this software from the United States of America may require a
specific license from the United States Government. It is the responsibility

A-22 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
of any person or organization contemplating export to obtain such a
license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation, and that the name
of Richard P. Basch, Lehman Brothers and M.I.T. not be used in
advertising or publicity pertaining to distribution of the software without
specific, written prior permission. Richard P. Basch, Lehman Brothers and
M.I.T. make no representations about the suitability of this software for
any purpose. It is provided "as is" without express or implied warranty.
-------------------
The following notice applies to `src/lib/krb5/krb/strptime.c':
Copyright (C) 1997, 1998 The NetBSD Foundation, Inc.
All rights reserved.
This code was contributed to The NetBSD Foundation by Klaus Klein.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by the NetBSD Foundation, Inc.
and its contributors.
4. Neither the name of The NetBSD Foundation nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------
The following notice applies to Unicode library files in `src/lib/krb5/
unicode':
Copyright 1997, 1998, 1999 Computing Research Labs, New Mexico State
University

Software license information A-23


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
COMPUTING RESEARCH LAB OR NEW MEXICO STATE UNIVERSITY BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
-------------------
The following notice applies to `src/util/support/strlcpy.c':
Copyright (C) 1998 Todd C. Miller <[email protected]>
Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE
OR PERFORMANCE OF THIS SOFTWARE.
-------------------
The following notice applies to `src/util/profile/argv_parse.c' and `src/
util/profile/argv_parse.h':
Copyright 1999 by Theodore Ts'o.
Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies. THE
SOFTWARE IS PROVIDED "AS IS" AND THEODORE TS'O (THE AUTHOR)
DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
THE USE OR PERFORMANCE OF THIS SOFTWARE. (Isn't it sick that the
U.S. culture of lawsuit-happy lawyers requires this kind of disclaimer?)
-------------------
The following notice applies to SWIG-generated code in `src/util/profile/
profile_tcl.c':

A-24 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright (C) 1999-2000, The University of Chicago
This file may be freely redistributed without license or fee provided this
copyright message remains intact.
-------------------
The following notice applies to portiions of `src/lib/rpc' and `src/include/
gssrpc':
Copyright (C) 2000 The Regents of the University of Michigan. All rights
reserved.
Copyright (C) 2000 Dug Song <[email protected]>. All rights
reserved, all wrongs reversed.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------
Implementations of the MD4 algorithm are subject to the following notice:
Copyright (C) 1990, RSA Data Security, Inc. All rights reserved.
License to copy and use this software is granted provided that it is
identified as the "RSA Data Security, Inc. MD4 Message Digest Algorithm"
in all material mentioning or referencing this software or this function.
License is also granted to make and use derivative works provided that
such works are identified as "derived from the RSA Data Security, Inc.
MD4 Message Digest Algorithm" in all material mentioning or referencing
the derived work.
RSA Data Security, Inc. makes no representations concerning either the
merchantability of this software or the suitability of this software for any
particular purpose. It is provided "as is" without express or implied
warranty of any kind.
These notices must be retained in any copies of any part of this
documentation and/or software.
-------------------

Software license information A-25


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Implementations of the MD5 algorithm are subject to the following notice:
Copyright (C) 1990, RSA Data Security, Inc. All rights reserved.
License to copy and use this software is granted provided that it is
identified as the "RSA Data Security, Inc. MD5 Message- Digest
Algorithm" in all material mentioning or referencing this software or this
function.
License is also granted to make and use derivative works provided that
such works are identified as "derived from the RSA Data Security, Inc.
MD5 Message-Digest Algorithm" in all material mentioning or referencing
the derived work.
RSA Data Security, Inc. makes no representations concerning either the
merchantability of this software or the suitability of this software for any
particular purpose. It is provided "as is" without express or implied
warranty of any kind.
These notices must be retained in any copies of any part of this
documentation and/or software.
-------------------
The following notice applies to `src/lib/crypto/crypto_tests/t_mddriver.c':
Copyright (C) 1990-2, RSA Data Security, Inc. Created 1990. All rights
reserved.
RSA Data Security, Inc. makes no representations concerning either the
merchantability of this software or the suitability of this software for any
particular purpose. It is provided "as is" without express or implied
warranty of any kind.
These notices must be retained in any copies of any part of this
documentation and/or software.
-------------------
Portions of `src/lib/krb5' are subject to the following notice:
Copyright (C) 1994 CyberSAFE Corporation.
Copyright 1990,1991,2007,2008 by the Massachusetts Institute of
Technology.
All Rights Reserved.
Export of this software from the United States of America may require a
specific license from the United States Government. It is the responsibility
of any person or organization contemplating export to obtain such a
license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation, and that the name
of M.I.T. not be used in advertising or publicity pertaining to distribution
of the software without specific, written prior permission. Furthermore if
you modify this software you must label your software as modified
software and not distribute it in such a fashion that it might be confused
with the original M.I.T. software. Neither M.I.T., the Open Computing
Security Group, nor CyberSAFE Corporation make any representations
about the suitability of this software for any purpose. It is provided "as is"
without express or implied warranty.
-------------------

A-26 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Portions contributed by PADL Software are subject to the following
license:
Copyright (c) 2011, PADL Software Pty Ltd. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of PADL Software nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY PADL SOFTWARE AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL PADL SOFTWARE OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
-------------------
The bundled libev source code is subject to the following license:
All files in libev are Copyright (C)2007,2008,2009 Marc Alexander
Lehmann.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Software license information A-27


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Alternatively, the contents of this package may be used under the terms
of the GNU General Public License ("GPL") version 2 or any later version,
in which case the provisions of the GPL are applicable instead of the
above. If you wish to allow the use of your version of this package only
under the terms of the GPL and not to allow others to use your version of
this file under the BSD license, indicate your decision by deleting the
provisions above and replace them with the notice and other provisions
required by the GPL in this and the other files of this package. If you do
not delete the provisions above, a recipient may use your version of this
file under either the BSD or the GPL.

libart_lgpl GNU LIBRARY GENERAL PUBLIC LICENSE Version 2


For details on the license, access the following page:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

libcap Unless otherwise *explicitly* stated, the following text describes the
licensed conditions under which the contents of this libcap release may be
used and distributed:

-------------------------------------------------------------------------
Redistribution and use in source and binary forms of libcap, with or
without modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain any existing copyright


notice, and this entire permission notice in its entirety, including the
disclaimer of warranties.

2. Redistributions in binary form must reproduce all prior and current


copyright notices, this list of conditions, and the following disclaimer in
the documentation and/or other materials provided with the distribution.

3. The name of any author may not be used to endorse or promote


products derived from this software without their specific prior written
permission.

ALTERNATIVELY, this product may be distributed under the terms of the


GNU General Public License, in which case the provisions of the GNU GPL
are required INSTEAD OF the above restrictions. (This clause is necessary
due to a potential conflict between the GNU GPL and the restrictions
contained in a BSD-style copyright.)

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED


WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR(S) BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
-------------------------------------------------------------------------

libcap-ng GNU General Public License version2

A-28 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libdaemon GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libee GNU Lesser General Public License version2.1


For details on the license, access the following page:
http://www.gnu.org/licenses/lgpl-2.1.html

libestr GNU Lesser General Public License version2.1


For details on the license, access the following page:
http://www.gnu.org/licenses/lgpl-2.1.html

libgcc GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libgcrypt GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

libgomp GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libgpg-error GNU General Public License version2


GNU Lesser General Public License version2.1
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/lgpl-2.1.html

libidn GNU General Public License version2


GNU Lesser General Public License version2.1
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/lgpl-2.1.html

libmcrypt GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libmudflap GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libnih GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

Software license information A-29


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

libnl GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libpcap License: BSD

Redistribution and use in source and binary forms, with or without


modification, are permitted provided that the following conditions are
met:

1. Redistributions of source code must retain the above copyright notice,


this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The names of the authors may not be used to endorse or promote
products derived from this software without specific prior written
permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS


OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.

libpng This copy of the libpng notices is provided for your convenience. In case
of any discrepancy between this copy and the notices in the file png.h
that is included in the libpng distribution, the latter shall prevail.

COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:

If you modify libpng you may insert additional notices immediately


following this sentence.

This code is released under the libpng license.

libpng versions 1.2.6, August 15, 2004, through 1.2.49, March 29, 2012,
are Copyright (c) 2004, 2006-2009 Glenn Randers-Pehrson, and are
distributed according to the same disclaimer and license as libpng-1.2.5
with the following individual added to the list of Contributing Authors

Cosmin Truta

libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
distributed according to the same disclaimer and license as libpng-1.0.6
with the following individuals added to the list of Contributing Authors

Simon-Pierre Cadieux
Eric S. Raymond
Gilles Vollant

and with the following additions to the disclaimer:

There is no warranty against interference with your enjoyment of the


library or against infringement. There is no warranty that our efforts or
the library will fulfill any of your particular purposes or needs. This library

A-30 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
is provided with all faults, and the entire risk of satisfactory quality,
performance, accuracy, and effort is with the user.

libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are distributed
according to the same disclaimer and license as libpng-0.96, with the
following individuals added to the list of Contributing Authors:

Tom Lane
Glenn Randers-Pehrson
Willem van Schaik

libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright
(c) 1996, 1997 Andreas Dilger Distributed according to the same
disclaimer and license as libpng-0.88, with the following individuals added
to the list of Contributing Authors:

John Bowler
Kevin Bracey
Sam Bushell
Magnus Holmgren
Greg Roelofs
Tom Tanner

libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright
(c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.

For the purposes of this copyright and license, "Contributing Authors" is


defined as the following set of individuals:

Andreas Dilger
Dave Martindale
Guy Eric Schalnat
Paul Schmidt
Tim Wegner

The PNG Reference Library is supplied "AS IS". The Contributing Authors
and Group 42, Inc. disclaim all warranties, expressed or implied,
including, without limitation, the warranties of merchantability and of
fitness for any purpose. The Contributing Authors and Group 42, Inc.
assume no liability for direct, indirect, incidental, special, exemplary, or
consequential damages, which may result from the use of the PNG
Reference Library, even if advised of the possibility of such damage.

Permission is hereby granted to use, copy, modify, and distribute this


source code, or portions hereof, for any purpose, without fee, subject to
the following restrictions:

1. The origin of this source code must not be misrepresented.

2. Altered versions must be plainly marked as such and must not be


misrepresented as being the original source.

3. This Copyright notice may not be removed or altered from any source
or altered source distribution.

Software license information A-31


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
The Contributing Authors and Group 42, Inc. specifically permit, without
fee, and encourage the use of this source code as a component to
supporting the PNG file format in commercial products. If you use this
source code in a product, acknowledgment is not required but would be
appreciated.

A "png_get_copyright" function is available, for convenient use in "about"


boxes and the like:

printf("%s",png_get_copyright(NULL));

Also, the PNG logo (in PNG format, of course) is supplied in the files
"pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).

Libpng is OSI Certified Open Source Software. OSI Certified Open Source
is a certification mark of the Open Source Initiative.

Glenn Randers-Pehrson
glennrp at users.sourceforge.net
March 29, 2012

libsemanage GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libsepol GNU Lesser General Public License version2.1


For details on the license, access the following page:
http://www.gnu.org/licenses/lgpl-2.1.html

libstdc++ GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libtalloc GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

libtasn1 GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

libtdb GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

libtevent GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

libthai GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

A-32 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

libtool GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libusb GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libutempter GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

libxml2 Except where otherwise noted in the source code (e.g. the files hash.c,
list.c and the trio files, which are covered by a similar licence but with
different Copyright notices) all the files are:

Copyright (C) 1998-2003 Daniel Veillard. All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining a


copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is fur- nished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY


KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FIT- NESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE DANIEL
VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CON- NECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of Daniel Veillard shall not be
used in advertising or otherwise to promote the sale, use or other deal-
ings in this Software without prior written authorization from him.

Linux Kernel GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

lm_sensors GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

log4cpp GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

logrotate GNU General Public License version2


For details on the license, access the following page:

Software license information A-33


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
http://www.gnu.org/licenses/gpl-2.0.html

make GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

MAKEDEV GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

mcelog GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

mingetty GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

module-init- GNU General Public License version2


tools For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

mpfr GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

mtools GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

nano GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

ncurses Copyright (c) 1998-2004,2006 Free Software Foundation, Inc.

Permission is hereby granted, free of charge, to any person obtaining a


copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, distribute with
modifications, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to the
following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY


KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE ABOVE
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR

A-34 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name(s) of the above copyright


holders shall not be used in advertising or otherwise to promote the sale,
use or other dealings in this Software without prior written authorization.

netcf GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

net-SNMP Berkeley Software Distribution License like


For details on the license, access the following page:
http://www.net-snmp.org/about/license.html

Nettle GNU Lesser General Public License version2.1


For details on the license, access the following page:
http://www.gnu.org/licenses/lgpl-2.1.html

net-tools GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

newt GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

nfs-utils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

nkf zlib License


For details on the license, access the following page:
http://zlib.net/zlib_license.html

nmap GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

nspr MOZILLA PUBLIC LICENSE VERSION 2.0


For details on the license, access the following page:
http://mozilla.org/MPL/2.0/

nss MOZILLA PUBLIC LICENSE VERSION 2.0


For details on the license, access the following page:
http://mozilla.org/MPL/2.0/

ntp Copyright (c) David L. Mills 1992-2009

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose with or without fee is hereby granted,
provided that the above copyright notice appears in all copies and that
both the copyright notice and this permission notice appear in supporting

Software license information A-35


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
documentation, and that the name University of Delaware not be used in
advertising or publicity pertaining to distribution of the software without
specific, written prior permission. The University of Delaware makes no
representations about the suitability this software for any purpose. It is
provided "as is" without express or implied warranty.

OpenLDAP The OpenLDAP Public License


Version 2.8, 17 August 2003

Redistribution and use of this software and associated documentation


("Software"), with or without modification, are permitted provided that
the following conditions are met:

1. Redistributions in source form must retain copyright statements and


notices,

2. Redistributions in binary form must reproduce applicable copyright


statements and notices, this list of conditions, and the following disclaimer
in the documentation and/or other materials provided with the
distribution, and

3. Redistributions must contain a verbatim copy of this document.

The OpenLDAP Foundation may revise this license from time to time.
Each revision is distinguished by a version number. You may use this
Software under terms of this license revision or under the terms of any
subsequent revision of the license.

THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS


CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP
FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S)
OF THE SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The names of the authors and copyright holders must not be used in
advertising or otherwise to promote the sale, use or other dealing in this
Software without specific, written prior permission.
Title to copyright in this Software shall at all times remain with copyright
holders.

OpenLDAP is a registered trademark of the OpenLDAP Foundation.

Copyright 1999-2003 The OpenLDAP Foundation, Redwood City,


California, USA. All Rights Reserved. Permission to copy and distribute
verbatim copies of this document is granted.

openslp The following copyright and license is applicable to the entire OpenSLP
project (libslp, slpd, and related documentation):

A-36 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Copyright (C) 2000 Caldera Systems, Inc
All rights reserved.

Redistribution and use in source and binary forms, with or without


modification, are permitted provided that the following conditions are
met:

Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice,


this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

Neither the name of Caldera Systems nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND


CONTRIBUTORS `AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE CALDERA SYSTEMS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

openssh Berkeley Software Distribution License like


For details on the license, access the following page:
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/LICENCE?
rev=HEAD

openssl OpenSSL License


SSLeay license
For details on the license, access the following URL:
http://www.openssl.org/source/license.html

openssl_tpm GNU General Public License version2


_engine For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

oprofile GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

pam GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

Software license information A-37


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

pam_krb5 GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

pam_ldap GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

pango GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

pcre PCRE LICENCE


------------
PCRE is a library of functions to support regular expressions whose syntax
and semantics are as close as possible to those of the Perl 5 language.
Release 7 of PCRE is distributed under the terms of the "BSD" licence, as
specified below. The documentation for PCRE, supplied in the "doc"
directory, is distributed under the same terms as the software itself.
The basic library functions are written in C and are freestanding. Also
included in the distribution is a set of C++ wrapper functions.
THE BASIC LIBRARY FUNCTIONS
---------------------------
Written by: Philip Hazel
Email local part: ph10
Email domain: cam.ac.uk
University of Cambridge Computing Service, Cambridge, England.
Copyright (c) 1997-2008 University of Cambridge
All rights reserved.
THE C++ WRAPPER FUNCTIONS
-------------------------
Contributed by: Google Inc.
Copyright (c) 2007-2008, Google Inc.
All rights reserved.
THE "BSD" LICENCE
-----------------
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

A-38 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
* Neither the name of the University of Cambridge nor the name of
Google Inc. nor the names of their contributors may be used to endorse
or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

perl This program is free software; you can redistribute it and/or modify it
under the terms of either:
a) the GNU General Public License as published by the Free Software
Foundation; either version 1, or (at your option) any later version, or
b) the "Artistic License" which comes with this Kit.
This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General
Public License or the Artistic License for more details.
You should have received a copy of the Artistic License with this Kit, in the
file named "Artistic". If not, I'll be glad to provide one.
You should also have received a copy of the GNU General Public License
along with this program in the file named "Copying". If not, write to the
Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA or visit their web page on the internet at http://
www.gnu.org/copyleft/gpl.html.
For those of you that choose to use the GNU General Public License, my
interpretation of the GNU General Public License is that no Perl script falls
under the terms of the GPL unless you explicitly put said script under the
terms of the GPL yourself. Furthermore, any object code linked with perl
does not automatically fall under the terms of the GPL, provided such
object code only adds definitions of subroutines and variables, and does
not otherwise impair the resulting interpreter from executing any
standard Perl script. I consider linking in C subroutines in this manner to
be the moral equivalent of defining subroutines in the Perl language itself.
You may sell such an object file as proprietary provided that you provide
or offer to provide the Perl source, as specified by the GNU General Public
License. (This is merely an alternate way of specifying input to the
program.) You may also sell a binary produced by the dumping of a
running Perl script that belongs to you, provided that you provide or offer
to provide the Perl source as specified by the GPL. (The fact that a Perl
interpreter and your code are in the same binary file is, in this case, a
form of mere aggregation.) This is my interpretation of the GPL. If you
still have concerns or difficulties understanding my intent, feel free to

Software license information A-39


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
contact me. Of course, the Artistic License spells all this out for your
protection, so you may prefer to use that.

php-pear Copyright (c) 1997-2009,


Stig Bakken <[email protected]>,
Gregory Beaver <[email protected]>,
Helgi Tormar Torbjornsson <[email protected]>,
Tomas V.V.Cox <[email protected]>,
Martin Jansen <[email protected]>.
All rights reserved.

Redistribution and use in source and binary forms, with or without


modification, are permitted provided that the following conditions are
met:

* Redistributions of source code must retain the above copyright notice,


this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND


CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

pkgconfig GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

plymouth GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

policycoreutil GNU General Public License version2


s For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

popt GNU General Public License version2


For details on the license, access the following page:

A-40 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
http://www.gnu.org/licenses/gpl-2.0.html

portmap Copyright (c) 1990 The Regents of the University of California.


All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by the University of California, Berkeley and its
contributors.
4. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.

Sun RPC is a product of Sun Microsystems, Inc. and is provided for


unrestricted use provided that this legend is included on all tape
media and as a part of the software program in whole or part. Users may
copy or modify Sun RPC without charge, but are not authorized to license
or distribute it to anyone else except as part of a product or program
developed by the user.

SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND


INCLUDING THE WARRANTIES OF DESIGN, MERCHANTIBILITY AND
FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF
DEALING, USAGE OR TRADE PRACTICE.

Sun RPC is provided with no support and without any obligation on the
part of Sun Microsystems, Inc. to assist in its use, correction, modification
or enhancement.

SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO


THE INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS
BY SUN RPC OR ANY PART THEREOF.

Software license information A-41


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
In no event will Sun Microsystems, Inc. be liable for any lost revenue or
profits or other special, indirect and consequential damages, even if Sun
has been advised of the possibility of such damages.

Sun Microsystems, Inc.


2550 Garcia Avenue
Mountain View, California 94043

portreserve GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

ppl GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

procps GNU General Public License version2


GNU Library General Public License version2
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

psmisc GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

Qt/ GNU Lesser General Public License version2.1


Embedded For details on the license, access the following page:
http://www.gnu.org/licenses/lgpl-2.1.html

readline GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

rng-tools GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

rpm GNU General Public License version2


GNU Library General Public License version2
For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

rsyslogd GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

LCD driver GNU General Public License version2


S1D13U11 For details on the license, access the following page:
Linux 2.6.35

A-42 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
Framebuffer http://www.gnu.org/licenses/gpl-2.0.html
and
Touchscreen
driver
(2011-01-05
)

sed GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

sgml- GNU General Public License version2


common For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

shadow-utils GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

slang GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

squashfs- GNU General Public License version2


tools For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

ssmtp GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

strongswan GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

syslinux GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

SysVinit GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

tar GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

tcp_wrapper TCP wrapper license


s For details on the license, access the following URL:
ftp://ftp.porcupine.org/pub/security/tcp_wrappers_license/

tcpdump The BSD 3-Clause License

Software license information A-43


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
License: BSD
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The names of the authors may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.

telnet GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

tftp Copyright (c) 1983, 1993


The Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms, with or without


modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by the University of California,
Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS


``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.

A-44 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

tslib GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

tzdata GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

udev GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

upstart GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

util-linux-ng GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

uuid COPYRIGHT AND LICENSE

Copyright (c) 2004-2008 Ralf S. Engelschall <[email protected]>


Copyright (c) 2004-2008 The OSSP Project <http://www.ossp.org/>

This file is part of OSSP uuid, a library for the generation of UUIDs which
can found at http://www.ossp.org/pkg/lib/uuid/

Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR


IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS AND
COPYRIGHT HOLDERS AND THEIR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

HOME AND DOCUMENTATION

The documentation and latest release can be found on

• http://www.ossp.org/pkg/lib/uuid/
• ftp://ftp.ossp.org/pkg/lib/uuid/

vsftpd GNU General Public License version2


For details on the license, access the following page:

Software license information A-45


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
http://www.gnu.org/licenses/gpl-2.0.html

which GNU General Public License version3


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-3.0.html

Xinetd ORIGINAL LICENSE:


This software is

(c) Copyright 1992 by Panagiotis Tsirigotis

The author (Panagiotis Tsirigotis) grants permission to use, copy, and


distribute this software and its documentation for any purpose and
without fee, provided that the above copyright notice extant in files in this
distribution is not removed from files included in any redistribution and
that this copyright notice is also included in any redistribution.

Modifications to this software may be distributed, either by distributing


the modified software or by distributing patches to the original software,
under the following additional terms:

1. The version number will be modified as follows:


a. The first 3 components of the version number
(i.e <number>.<number>.<number>) will remain unchanged.
b. A new component will be appended to the version number to indicate
the modification level. The form of this component is up to the author of
the modifications.

2. The author of the modifications will include his/her name by appending


it along with the new version number to this file and will be responsible
for any wrong behavior of the modified software.

The author makes no representations about the suitability of this software


for any purpose. It is provided "as is" without any express or implied
warranty.

Modifications:
Version: 2.1.8.7-current
Copyright 1998-2001 by Rob Braun

Sensor Addition
Version: 2.1.8.9pre14a
Copyright 2001 by Steve Grubb

This is an exerpt from an email I recieved from the original author,


allowing xinetd as maintained by me, to use the higher version numbers:

I appreciate your maintaining the version string guidelines as specified in


the copyright. But I did not mean them to last as long as they did.

So, if you want, you may use any 2.N.* (N >= 3) version string for future
xinetd versions that you release. Note that I am excluding the 2.2.* line;
using that would only create confusion. Naming the next release 2.3.0
would put to rest the confusion about 2.2.1 and 2.1.8.*.

A-46 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name

xz GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

zlib zlib License


For details on the license, access the following page:
http://zlib.net/zlib_license.html

igb driver GNU General Public License version2


For details on the license, access the following page:
http://www.gnu.org/licenses/gpl-2.0.html

xmlrpc-c XML-RPC For C/C++ License


Copyright (C) 2001 by First Peer, Inc. All rights reserved.
Copyright (C) 2001 by Eric Kidd. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
Expat License
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd

Permission is hereby granted, free of charge, to any person obtaining a


copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

Software license information A-47


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
ABYSS Web Server License
Copyright (C) 2000 by Moez Mahfoudh <[email protected]>. All rights
reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.

Python 1.5.2 License


Copyright 1991, 1992, 1993, 1994 by Stichting Mathematisch Centrum,
Amsterdam, The Netherlands.
All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in supporting
documentation, and that the names of Stichting Mathematisch Centrum or
CWI or Corporation for National Research Initiatives or CNRI not be used
in advertising or publicity pertaining to distribution of the software without
specific, written prior permission.
While CWI is the initial source for this software, a modified version is
made available by the Corporation for National Research Initiatives
(CNRI) at the Internet address ftp://ftp.python.org.

A-48 Software license information


Hitachi Compute Blade 2500 Series Management Module User Guide
Software
Software license agreement
name
STICHTING MATHEMATISCH CENTRUM AND CNRI DISCLAIM ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
EVENT SHALL STICHTING MATHEMATISCH CENTRUM OR CNRI BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
THE USE OR PERFORMANCE OF THIS SOFTWARE.

Software license information A-49


Hitachi Compute Blade 2500 Series Management Module User Guide
A-50 Software license information
Hitachi Compute Blade 2500 Series Management Module User Guide
B
HCSM alert log message
This appendix describes HCSM alert log message.

□ HCSM alert log message

HCSM alert log message B-1


Hitachi Compute Blade 2500 Series Management Module User Guide
HCSM alert log message
Format of alert log messages
[ID]
The message ID
[Level]
The level of the message: Info (information message), WARNING (warning
message), or FAIL (error message)
[Message]
A message is shown."X","Y" in a message stands for characters.

Table B-1 Message list

ID Level Message
Description

FD00 WARNING Temperature of chassis became warning


level.(Temp(X),Location:Y)

[Meaning] The temperature at the part shown in Y is beyond the warning level. X shows
"Upper" or "Lower".
[Action] Although the device can keep running, the high temperature can cause a fault.
Thus, check if something prevents it from cooling down, such as failure in air
conditioners or in fan modules of the unit, and inlet ports covered with dust.

FD01 FAIL Temperature of chassis became error level.


(Temp(X),Location:Y)

[Meaning] The temperature at the part shown in Y is exceedingly high. X shows "Upper"
or "Lower".
[Action] The module with high temperature may stop working to protect hardware.
Consult your reseller or maintenance personnel.
Check if something prevents it from cooling down, such as failure in air conditioners or in
fan modules of the unit, and inlet ports covered with dust.

FD02 Info Temperature of chassis has been restored


to a normal level.(Temp(X),Location:Y)

[Meaning] The temperature at the part shown in Y is back to the normal level. X shows
"Upper" or "Lower".
[Action] No particular action required.

FD03 WARNING Temperature of CPU became warning level.


(Temp(X),Location:Y)

[Meaning] The temperature of CPU at the part shown in Y is exceedingly high. X shows
"Upper" or "Lower".
[Action] Although the device can keep running, the high temperature can cause a fault
(the message ID: FD04). Thus, check if something prevents it from cooling down, such
as failure in air conditioners or in fan modules of the unit, and inlet ports covered with
dust.

B-2 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

FD04 FAIL Temperature of CPU became error level.


(Temp(X),Location:Y)

[Meaning] The temperature of CPU at the part shown in Y is beyond the warning level. X
shows "Upper" or "Lower".
[Action] The module with high temperature may stop working to protect hardware.
Consult your reseller or maintenance personnel.
Check if something prevents it from cooling down, such as failure in air conditioners or in
fan modules of the unit, and inlet ports covered with dust.

FD05 Info Temperature of CPU has been restored to a


normal level.(Temp(X),Location:Y)

[Meaning] The temperature of CPU at the part shown in Y is back to the normal level. X
shows "Upper" or "Lower".
[Action] No particular action required.

FD10 WARNING Voltage became warning level.


(Voltage(X),Location:Y)

[Meaning] The voltage at the part shown in Y is beyond the warning level. X shows
"Upper" or "Lower".
[Action] Although the device can keep running, the voltage level can cause a fault (the
message ID: FD11). Consult your reseller or maintenance personnel.

FD11 FAIL Voltage became error level.


(Voltage(X),Location:Y)

[Meaning] The voltage at the part shown in Y is exceedingly high. X shows "Upper" or
"Lower".
[Action] The module with high voltage may stop working to protect hardware. Consult
your reseller or maintenance personnel.

FD12 Info Voltage has been restored to a normal


level.(Voltage(X),Location:Y)

[Meaning] The voltage at the part shown in Y is back to the normal level. X shows
"Upper" or "Lower".
[Action] No particular action required.

FD21 FAIL Current became error level.


(Current(Upper),Location:Y)

[Meaning] The current of the component indicated in Y reached the failure level.
[Action] To protect the hardware, the reported module might stop working. Contact your
reseller or maintenance personnel.

FD22 Info Current has been restored to a normal


level.(Current(Upper),Location:Y)

[Meaning] The current of the component indicated in Y has recovered and returned to a
normal level.
[Action] No action is required because this message is reporting a recovery.

FD30 Info Module is installed.(Location:X)

[Meaning] A module at the part shown in X is inserted.

HCSM alert log message B-3


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description
[Action] Nothing is required.

FD31 Info Module is removed.(Location:X)

[Meaning] A module shown at the part in X is removed.


[Action] Nothing is required.

FD38 FAIL Watchdog timer has expired.(Location:X)

[Meaning] Watchdog timeout at the part shown in X is detected.


[Action] Consult your reseller or maintenance personnel.

FD40 WARNING On server, an warning event occurred.


(Location:X,Event:Y)

[Meaning] A warning event in the server blade at the part shown in X is occurred. Y
shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD41 FAIL On server, an error event occurred.


(Location:X,Event:Y)

[Meaning] An error event in the server blade at the part shown in X is occurred. Y shows
the event type.
[Action] Consult your reseller or maintenance personnel.

FD42 Info Server has been restored to a normal level.


(Location:X,Event:Y)

[Meaning] The server blade at the part shown in X is back to the normal level. Y shows
the event type.
[Action] No particular action required.

FD43 WARNING On physical partition, a warning event


occurred.(Location:X,Event:Y)

[Meaning] A warning event in the server blade at the part shown in X is occurred. Y
shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD44 FAIL On physical partition, an error event


occurred.(Location:X,Event:Y)

[Meaning] An error event in the server blade at the part shown in X is occurred. Y shows
the event type.
[Action] Consult your reseller or maintenance personnel.

FD45 Info Physical partition has been restored to a


normal level.(Location:X,Event:Y)

[Meaning] The server blade at the part shown in X is back to the normal level. Y shows
the event type.
[Action] No particular action required.

FD46 WARNING On power supply, a warning event


occurred.(Location:X,Event:Y)

B-4 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] A warning event in the power supply module at the part shown in X is
occurred. Y shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD47 FAIL On power supply, an error event occurred.


(Location:X,Event:Y)

[Meaning] An error event in the power supply module at the part shown in X is occurred.
Y shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD48 Info Power supply has been restored to a normal


level.(Location:X,Event:Y)

[Meaning] The power supply module at the part shown in X is back to the normal level. Y
shows the event type.
[Action] No particular action required.

FD4A FAIL On cooling fan, an error event occurred.


(Location:X,Event:Y)

[Meaning] An error event in the cooling fan module at the part shown in X is occurred. Y
shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD4B Info Cooling fan has been restored to a normal


level.(Location:X,Event:Y)

[Meaning] The cooling fan module at the part shown in X is back to the normal level. Y
shows the event type.
[Action] No particular action required.

FD4C WARNING On switch module, a warning event


occurred.(Location:X,Event:Y)

[Meaning] A warning event in the switch module at the part shown in X is occurred. Y
shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD4D FAIL On switch module, an error event occurred.


(Location:X,Event:Y)

[Meaning] An error event in the switch module at the part shown in X is occurred. Y
shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD4E Info Switch module has been restored to a


normal level.(Location:X,Event:Y)

[Meaning] The switch module at the part shown in X is back to the normal level. Y shows
the event type.
[Action] No particular action required.

FD50 FAIL On disk, an error event occurred.


(Location:X,Event:Y)

HCSM alert log message B-5


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] An error event in the disk at the part shown in X is occurred. Y shows the
event type.
[Action] Consult your reseller or maintenance personnel.

FD51 Info Disk has been restored to a normal level.


(Location:X,Event:Y)

[Meaning] The disk at the part shown in X is back to the normal level. Y shows the event
type.
[Action] No particular action required.

FD52 WARNING On management module, a warning event


occurred.(Location:X,Event:Y)

[Meaning] A warning event in the management module at the part shown in X is


occurred. Y shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD53 FAIL On management module, an error event


occurred.(Location:X,Event:Y)

[Meaning] An error event in the management module at the part shown in X is occurred.
Y shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD54 Info Management module has been restored to a


normal level.(Location:X,Event:Y)

[Meaning] The management module at the part shown in X is back to the normal level. Y
shows the event type.
[Action] No particular action required.

FD58 WARNING On other module, a warning event


occurred.(Location:X,Event:Y)

[Meaning] A warning event in other module (except server blade, power supply module,
fan module, switch module, disk, and management module) at the part shown in X is
occurred. Y shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD59 FAIL On other module, an error event occurred.


(Location:X,Event:Y)

[Meaning] An error event in other module (except server blade, power supply module,
fan module, switch module, disk, and management module) at the part shown in X is
occurred. Y shows the event type.
[Action] Consult your reseller or maintenance personnel.

FD60 WARNING The cooling fan rotation speed is


abnormally high or low.(Location:X)

[Meaning] The cooling fan rotation speed is abnormally high or low. X shows the part
that event occurred.
[Action] Consult your reseller or maintenance personnel.

FD61 Info The cooling fan rotation speed has been


restored a normal level.(Location:X)

B-6 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] The cooling rotation speed is restored the normal level. X shows the part that
event occurred.
[Action] No particular action required.

FD64 WARNING On chassis, an AC input is lost.(Location:X)

[Meaning] An AC input is lost in the power supply module at the part shown in X.
[Action] Check if something wrong is in the power supply to devices. If nothing wrong is
detected, consult your reseller or maintenance personnel.

FD65 Info On chassis, the AC input error has been


corrected.(Location:X)

[Meaning] The AC input error is corrected. X shows the part that error occurred.
[Action] No particular action required.

FD68 FAIL Uncorrectable CPU error occurred.


(Location:X)

[Meaning] Uncorrectable CPU error is occurred. X shows the part that error occurred.
[Action] Consult your reseller or maintenance personnel.

FD69 WARNING Corrected CPU error threshold exceeded.


(Location:X)

[Meaning] Although uncorrectable CPU error is corrected, corrected CPU error threshold
is exceeded. X shows the part that error occurred.
[Action] Although the device can keep running, fault may be occurred. Consult your
reseller or maintenance personnel.

FD6B FAIL Uncorrectable memory error occurred.


(Location:X)

[Meaning] Uncorrectable memory error is occurred. X shows the part that error occurred.
[Action] Consult your reseller or maintenance personnel.

FD6C WARNING Corrected memory error threshold


exceeded.(Location:X)

[Meaning] Although uncorrectable memory error is corrected, corrected CPU error


threshold is exceeded. X shows the part that error occurred.
[Action] Although the device can keep running, fault may be occurred. Consult your
reseller or maintenance personnel.

FD70 WARNING CPU is disabled.(Location:X)

[Meaning] CPU at the part shown in X is degraded.


[Action] Although the device can keep running, CPU performance is degraded. Consult
your reseller or maintenance personnel.

FD71 WARNING Memory is disabled.(Location:X)

[Meaning] Memory at the part shown in X is degraded.


[Action] Although the device can keep running, memory performance is degraded.
Consult your reseller or maintenance personnel.

FD78 WARNING Module lacks redundancy.(Location:X)

HCSM alert log message B-7


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] A module at the part shown in X has no longer redundancy.


[Action] Although the device can keep running, redundancy is lost. Consult your reseller
or maintenance personnel.

FD79 Info Module restored redundancy.(Location:X)

[Meaning] A module at the part shown in X has redundancy.


[Action] No particular action required.

FD7F FAIL Event is logged.(Location:X,Event:Y)

[Meaning] Event at the part shown in X is logged. Y shows the event type.
[Action] No particular action required.

FD85 WARNING On server, power-on is inhibited.


(Location:X)

[Meaning] Power of server blade at the part shown in X is inhibited. The problem may be
caused by following reasons:
Construction and setting have problem. (Combination of hardware is invalid/power
shortage)
Working state of maintenance. (Power operation for maintenance module/failure
module)
[Action] Eliminate the course of inhibition. If you cannot find course, consult your
reseller or maintenance personnel.

FD90 Info Server is powered on.(Location:X)

[Meaning] A server blade at the part shown in X is powered on.


[Action] No particular action required.

FD91 Info Server is powered off.(Location:X)

[Meaning] A server blade at the part shown in X is powered off.


[Action] No particular action required.

FD92 Info Server is reset.(Location:X)

[Meaning] A server blade at the part shown in X is reset.


[Action] No particular action required.

FD93 FAIL Server failed to power-on.(Location:X)

[Meaning] A server blade at the part shown in X is failed to power-on.


[Action] Consult your reseller or maintenance personnel.

FD9C Info Switch module is powered on.(Location:X)

[Meaning] A switch module at the part shown in X is powered on.


[Action] No particular action required.

FD9D Info Switch module is powered off.(Location:X)

[Meaning] A switch module at the part shown in X is powered off.


[Action] No particular action required.

B-8 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

FD9F FAIL Switch module failed to power-on.


(Location:X)

[Meaning] A switch module at the part shown in X is failed to power-on.


[Action] Consult your reseller or maintenance personnel.

FDA8 Info Power supply is powered on.(Location:X)

[Meaning] A power supply module at the part shown in X is powered on.


[Action] No particular action required.

FDA9 Info Power supply is powered off.(Location:X)

[Meaning] A power supply module at the part shown in X is powered off.


[Action] No particular action required.

FDAB FAIL Power supply failed to power-on.


(Location:X)

[Meaning] A power supply module at the part shown in X is failed to power-on.


[Action] Consult your reseller or maintenance personnel.

FDAC WARNING Power supply failed to power-off.


(Location:X)

[Meaning] A power supply module at the part shown in X is failed to power-off.


[Action] Consult your reseller or maintenance personnel.

FDAE Info Management module is powered on.


(Location:X)

[Meaning] A management module at the part shown in X is powered on.


[Action] No particular action required.

FDAF Info Management module is powered off.


(Location:X)

[Meaning] A management module at the part shown in X is powered off.


[Action] No particular action required.

FDBA Info Panel button was pressed, and NMI was


issued.(Location:X)

[Meaning] In a server blade at the part shown in X, NMI is issued.


[Action] No particular action required.

FDBB Info NMI was issued.(Location:X)

[Meaning] In a server blade at the part shown in X, NMI is issued.


[Action] No particular action required.

FDC0 Info Time is updated.(Location:X)

[Meaning] Time of module at the part shown in X is changed.


[Action] No particular action required.

FDC8 Info Updating firmware has started.(Location:X)

HCSM alert log message B-9


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] In a server blade at the part shown in X, firmware update has started.
[Action] No particular action required.

FDC9 Info Updating firmware has completed.


(Location:X)

[Meaning] In a server blade at the part shown in X, firmware update has completed.
[Action] No particular action required.

FDD0 WARNING Warning about the system configuration is


detected.

[Meaning] Device configuration has problem.


[Action] If you change the device configuration before this message appeared, check if
something wrong is in the configuration. If there is no problem in the configuration,
consult your reseller or maintenance personnel.

FDD1 FAIL System configuration error is detected.

[Meaning] Device configuration has problem.


[Action] If you change the device configuration before this message appeared, check if
something wrong is in the configuration. If there is no problem in the configuration,
consult your reseller or maintenance personnel.

FDD2 WARNING System power activation is deterred for


system configuration error.(Location:X)

[Meaning] Power of server blade at the part shown in X is inhibited for device
configuration error. The problem may be caused by following reasons:
Construction and setting have problem. (Combination of hardware is invalid/power
shortage)
Working state of maintenance. (Power operation for maintenance module/failure
module)
[Action] Eliminate the course of inhibition. If you cannot find course, consult your
reseller or maintenance personnel.

FDD3 FAIL Power supply capacity is insufficient.

[Meaning] Power supply capacity is insufficient.


[Action] Check if power supply modules are correctly installed. Consult your reseller or
maintenance personnel.

FDD5 FAIL The total number of cooling fan modules is


insufficient.

[Meaning] The total number of cooling fan modules is insufficient.


[Action] Check if cooling fan modules are correctly installed. Consult your reseller or
maintenance personnel.

FF05 Info LAN port <X> has switched to another port.

[Meaning] When redundancy of LAN port at the part shown in X is available, the LAN
port has switched to another port.
[Action] No particular action required when only this message appeared, because of
keeping redundancy. If the message ID: FD78 appeared with this message, check if the
specified LAN port is connected.

B-10 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

FF06 Info LAN port <X> has recovered from an error.

[Meaning] The LAN port route is restored from the changed route of message ID: FF05.
[Action] No particular action required.

FF08 WARNING The synchronization of time is not


performed.(Location:X)

[Meaning] In a device at the part shown in X, the time synchronization is not available
using NTP server.
[Action] Check if communication between the management module and NTP server is
available. Also check the configuration of management module and NTP server.
Check if the specified parts time is correct, correct the time as needed.

FF09 Info The synchronization of time is resumed.


(Location:X)

[Meaning] In a device at the part shown in X, the time synchronization is resumed using
NTP server.
[Action] Check if the specified parts time is correct, correct the time as needed.

FF0B FAIL Support center report failed.(Report:X)

[Meaning] Support center report is not available due to failure in report function x.
[Action] Contact your reseller or call for maintenance personnel.

FF0E WARNING A report is failed.(Report:X)

[Meaning] A report at the part shown in X failed.


[Action] Check if communication between the information addressee and management
module is available. Also check the report configuration, and correct the configuration as
needed. If the problem persists, consult your reseller or maintenance personnel.

FF0F Info A report is resumed.(Report:X)

[Meaning] A report at the part shown in X is resumed.


[Action] No particular action required.

FF10 Info Power saving event was occurred.


(Location:X,Event:Y)

[Meaning] In a device at the part shown in X, power saving event is logged. Y shows the
event type.
[Action] No particular action required.

FF11 WARNING Power saving <warning> event was


occurred.(Location:X,Event:Y)

[Meaning] In a device at the part shown in X, power saving event as warning level is
logged. Y shows the event type.
[Action] Check if the power saving configuration is correct, correct the configuration as
needed.

FF18 Info On <X>, maintenance mode is started.

[Meaning] In a device at the part shown in X, maintenance mode is started.


This message may be appeared several times depending on the maintenance type.

HCSM alert log message B-11


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description
[Action] No particular action required.

FF19 Info On <X>, maintenance mode is ended.

[Meaning] In a device at the part shown in X, maintenance mode is ended.


This message may be appeared several times depending on the maintenance type.
[Action] No particular action required.

FF22 FAIL On <X>, a failure occurred in <Y> during


smart configure.

[Meaning] In the server blade at the part shown in X, a failure occurred during a Smart
Configure process in the component indicated by Y.
[Action] Contact your sales or service representative.

FF23 WARNING On <X>, an invalid setting was found in


<Y> during smart configure.

[Meaning] A Smart Configure process in the server blade at the part shown in X, failed
because the component indicated by Y was set up incorrectly.
[Action] Y is an HBA slot number or a port number. Review and amend the HBA BIOS
settings for the specified slot, and then manually run the Smart Configure process. If the
same message appears again, contact your sales or service representative.

FF24 FAIL On <X>, a smart configure error was


detected.

[Meaning] A failure was detected in a Smart Configure process running on the server
blade at the part shown in X.
[Action] Contact your sales or service representative.

FF25 WARNING On <X>, an error occurred when smart


configure was being performed.

[Meaning] An error occurred during execution of a Smart Configure process on the


server blade at the part shown in X.
[Action] Contact your sales or service representative.

FF28 Info On <X>, error alert (immediate


replacement) is sent by the user request
operation.

[Meaning] A test of the N+M cold standby function (immediate failover) was performed
on the partition indicated by X.
[Action] No particular action is required as the message relates to a test.

FF29 Info On <X>, error alert is sent by the user


request operation.

[Meaning] A test of the N+M cold standby function (other than immediate failover) was
performed on the partition indicated by X.
[Action] No particular action is required as the message relates to a test.

FF2A FAIL On <X>, a failure requiring an immediate


failover occurred.

B-12 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] A failure which is subject to immediate failover by the N+M cold standby
function occurred on the server blade indicated by X. The affected server blade will now
fail over to its counterpart in the standby system.
[Action] Contact your sales or service representative.

FF2B FAIL On <X>, a failure requiring a failover


occurred.

[Meaning] A failure which is subject to delayed failover by the N+M cold standby function
occurred on the server blade indicated by X. The affected server blade will now fail over
to its counterpart in the standby system.
[Action] Contact your sales or service representative.

FF30 FAIL Unknown SEL detected.

[Meaning] A SEL that is not registered in the dictionary was collected.


[Action] Update the dictionary to the latest version.

FF40 WARNING The scheduling mode for a NIC assigned to


an LPAR was changed. (Location: <X>,
Event: <Y>)

[Meaning] Indicates that the scheduling mode of a NIC that was assigned to an LPAR
was changed. X indicates the location. Y indicates the event that occurred.
[Action] Because safe mode is enabled, review NIC assignment to LPARs and then exit
safe mode.

FF41 FAIL An error event on a management NIC was


detected. (Location: <X>, Event: <Y>)

[Meaning] Indicates that a failure-level event was detected on the specified management
NIC. X indicates the location. Y indicates the event that occurred.
[Action] If the location is "-", no action needs to be taken. If the location is not "-",
check the following:
• Check whether the management NIC is correctly specified.
• If the management NIC is correctly specified, check whether a NIC that supports
shared mode is installed in the location.
If you cannot find any problems with the items above, the location might be damaged.
Contact your reseller or maintenance personnel.

FF42 WARNING A warning event on a management NIC was


detected. (Location: <X>, Event: <Y>)

[Meaning] Indicates that a warning event was detected on the specified management
NIC. X indicates the location. Y indicates the event that occurred.
[Action] If the location is "-", no action needs to be taken. If the location is not "-",
check the following:
• Check whether the management NIC is correctly specified.
• If the management NIC is correctly specified, check whether a NIC that supports
shared mode is installed in the location.
If you cannot find any problems with the items above, the location might be damaged.
Contact your reseller or maintenance personnel.

HCSM alert log message B-13


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

FF43 Info LP started with the specified ports set as


the LP management NIC ports.
(Location:<X>)

[Meaning] Indicates that LPAR manager started on the LPAR manager management NIC
that was specified by the user. <X> indicates the location.
[Action] No particular action required.

FF44 FAIL An error event occurred on a management


NIC port. Location: <X>, Event: <Y>)

[Meaning] A failure was detected on the active port of a management NIC. X indicates
the location. Y indicates the event that occurred.
[Action] Check the following:
• Check whether cables and switches connecting the port of the management NIC
specified in the location and management modules are correctly set and are running
normally. After you check, immediately update the communication status of the
management NIC.
• If management NIC redundancy is not configured or if this event occurred on both
ports of the management NIC, check whether a management module failure
occurred. If a failure occurred on a management module, take recovery actions.
If you cannot find any problems with the items above, the location might be damaged.
Contact your reseller or maintenance personnel.

FF45 WARNING A warning event occurred on a


management NIC port. (Location: <X>,
Event: <Y>)

[Meaning] A failure was detected on the standby port of a management NIC. X indicates
the location. Y indicates the event that occurred.
[Action] Check the following:
• Check whether cables and switches connecting the port of the management NIC
specified in the location and management modules are correctly configured and are
running normally. After you check, immediately update the communication status of
the management NIC.
• If management NIC redundancy is not configured or if this event occurred on both
ports of the management NIC, check whether a management module failure
occurred. If a failure occurred on a management module, take recovery actions.
If you cannot find any problems with the items above, the location might be damaged.
Contact your reseller or maintenance personnel.

FF46 Info An event occurred on a management NIC


port. (Location: <X>, Event: <Y>)

[Meaning] Indicates that an event occurred on a management NIC. X indicates the


location. Y indicates the event that occurred.
If the event is "Changed Active/Standby port", the redundancy of management NICs or
ports might be removed. If a failure-level alert on a management NIC occurred, take
appropriate action.
If the event is not "Changed Active/Standby port", no action needs to be taken.
[Action] No particular action required.

B-14 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

FF47 WARNING The function is unavailable owing to port


number duplication. (Location:<X>,
Function:<Y>)

[Meaning] The LPAR manager functions are unavailable owing to port number
duplication. <X> indicates the location, and <Y> indicates the event that occurred.
[Action] Check the port number settings, and reassign the port numbers.

FF48 Info The port number(s) for the function was


recovered from duplication. (Location:<X>,
Function:<Y>)

[Meaning] The port numbers for the LPAR manager function were recovered from port
duplication. <X> indicates the location, and <Y> indicates the event that occurred.
[Action] No action is required.

FFC0 Info Management Module sent a connection


request alert.

[Meaning] The management module issued a connection request to the HCSM.


[Action] No particular action required.

FFC1 Info Management Module sent a connection


establishment alert.

[Meaning] The connection between the management module and HCSM is established.
[Action] No particular action required.

FFC2 Info Management Module sent a keep-alive


alert.

[Meaning] This message is an alert for confirming connection between the management
module and HCSM.
[Action] No particular action required.

FFC3 Info On <X>, smart configure started (Data Y


procedure).

[Meaning] A Smart Configure process is begun in the server blade indicated by X. Y


indicates the type of smart configuration being performed.
acquisition: Smart Configure for acquiring information from a server blade
setting: Smart Configure for setting information on a server blade
diagnosis: Smart Configure for testing a server blade
[Action] No particular action is required.

FFC4 Info On <X>, smart configure succeeded (Data


Y procedure).

[Meaning] Smart configuration is succeeded on the server blade at the part shown in X.
Y indicates the type of smart configuration being performed. (See the message ID:
FFC3)
[Action] No particular action required.

FFC5 Info On <X>, smart configure failed (Data Y


procedure).

HCSM alert log message B-15


Hitachi Compute Blade 2500 Series Management Module User Guide
ID Level Message
Description

[Meaning] Smart configuration is failed on the server blade at the part shown in X. Y
indicates the type of smart configuration being performed. (See the message ID: FFC3)
[Action] Other alert message appeared for indicating the reason for failure. Follow the
procedure in this alert message.

FFCA Info The IP address of the management module


changed.

[Meaning] The IP address of the management module has been changed.


[Action] No particular action required.

FFCB Info Module information of <X> changed.

[Meaning] The module information has been changed. X indicates the module name.
[Action] No particular action required.

FFCC Info Module information (constitution setting) of


<X> changed.

[Meaning] The module information has been changed. X indicates the module name.
[Action] No particular action required.

FFCD Info System information changed.

[Meaning] The device information has been changed.


[Action] No particular action required.

B-16 HCSM alert log message


Hitachi Compute Blade 2500 Series Management Module User Guide
Glossary
This section explains the terminology you need to know when using the CB2500.

A
active blade
When using the N+M cold standby function, the active blade is the server blade that is
actively running your applications.

APC (Accurate Power Control)


A function that uses power capping to limit the power consumption of the system unit.
The APC function reduces power consumption by controlling the CPU clock rate of the
system unit when power consumption exceeds a predetermined level.

B
BIOS
Basic Input/Output System

BMC (Baseboard Management Controller)


A controller that monitors and controls the status of server blades. The BMC monitors
and controls server blades by connecting to the system console and the management
module.

C
CNA
Converged Network Adapter

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-1
Hitachi Compute Blade 2500 Series Management Module User Guide
CSR
Certificate Signing Request

D
DCMI
Data Center Manageability Interface

Deployment Manager
Software provided as part of Compute Systems Manager. Deployment Manager is a
function that allows you to back up and restore the disk data of a server blade as an
image file. You can also use a backed up image file to replicate the environment of a
managed resource on another managed resource.

DHCP
Dynamic Host Configuration Protocol

F
FC
Fibre Channel

FCoE
Fibre Channel over Ethernet

FPGA
Field Programmable Gate Array

FQDN
Fully Qualified Domain Name

FRU
Field-Replaceable Unit

FTP
File Transfer Protocol

H
HA
High Availability

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-2
Hitachi Compute Blade 2500 Series Management Module User Guide
HDD
Hard Disk Drive

HTTP
HyperText Transfer Protocol

HTTPS
HyperText Transfer Protocol Secure

I
IP
Internet Protocol

IPMI
Intelligent Platform Management Interface

iSCSI
Internet Small Computer System Interface

K
KVM
Keyboard, Video and Mouse

L
LAN
Local Area Network

LCD
Liquid Crystal Display

LDAP
Lightweight Directory Access Protocol

LED
Light Emitting Diode

LFT
Link Fault Tolerance

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-3
Hitachi Compute Blade 2500 Series Management Module User Guide
LID (Location IDentifier lamp)
An LED lamp that you can use to identify the location of server chassis and modules. By
controlling the LIDs of a server blade or server chassis remotely from the system
console or Hitachi Compute Systems Manager, you can easily identify a managed
resource in the system unit.

logical partitioning
A function that uses Hitachi's server logical partitioning framework to logically partition
a blade server composed of one or several server blades. Each logical partition can then
be used to create a discrete server environment.

LPAR (Logical PARtition)


When using logical partitioning, an LPAR is the term for each logical partition that can
accommodate a discrete server environment.

LPAR manager (Logical PARtitioning manager)


A function of logical partitioning. A component that manages LPARs on a blade server.

LUN
Logical Unit Number

M
MAC
Media Access Control

management module
A module that monitors and configures the system unit as a whole. The management
module allows you to centrally manage the server blades and modules in the system
unit.

memory dump
A file containing the memory contents of a server at a particular time. When a failure
occurs in the OS, you can use a memory dump to diagnose the nature of the failure.

MIB
Management Information Base

MSR
Model Specific Register

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-4
Hitachi Compute Blade 2500 Series Management Module User Guide
N
N+M cold standby
When a failure occurs in a server, the N+M cold standby function allows the server to
failover to a machine that is in standby with power off. When a failure occurs in an
active server blade, failover to the standby blade takes place automatically. The server
that is actively running applications is called the "active blade". The server blade that is
in standby is called the "standby blade".

NIC
Network Interface Card

NMI (Non-Maskable Interrupt)


A hardware interrupt issued to the CPU from an external device. An NMI can be used,
for example, to collect OS dump files.

NTP
Network Time Protocol

O
OID
Object IDentifier

P
PCI
Peripheral Component Interconnect

PXE
Preboot eXecution Environment

R
remote console
Software provided with the CB2500. You can use the remote console to remotely control
the server OS and LPARs on a server blade.

ROM
Read Only Memory

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-5
Hitachi Compute Blade 2500 Series Management Module User Guide
S
SAN
Storage Area Network

server chassis
A frame in which server blades and modules are mounted.

SFTP
SSH File Transfer Protocol

SMP
Symmetric Multi Processor

SMTP
Simple Mail Transfer Protocol

SNMP
Simple Network Management Protocol

SR-IOV
Single Root IO Virtualization

SSH
Secure SHell

SSL
Secure Sockets Layer

standby blade
When using the N+M cold standby function, the standby blade remains in standby with
its power off until a failover occurs from a failed active blade.

system console
A computer from which a user monitors and configures the CB2500 system unit.

switch module
A module that connects the system unit to LANs, SANs, and other networks.

T
TCP
Transmission Control Protocol

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-6
Hitachi Compute Blade 2500 Series Management Module User Guide
terminal software
Software that allows a user to operate a remote host computer from a terminal
computer. The CB2500 remote console can be operated using generic terminal
software.

U
UEFI
Unified Extensible Firmware Interface

UPS
Uninterruptible Power Supply

URL
Uniform Resource Locator

USB
Universal Serial Bus

UTC
Coordinated Universal Time

UTP
Unshielded Twist Pair

V
VGA
Video Graphics Array

virtual media
An image file that contains the data recorded on media such as a CD or DVD. By
converting the installation media for the OS and other software to virtual media, you
can make the software available for installation on a server blade.

VLAN
Virtual Local Area Network

W
WDT
WatchDog Timer

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-7
Hitachi Compute Blade 2500 Series Management Module User Guide
Web console
A console that runs in a Web browser. You can use the Web console to view hardware
information for a server chassis or server blade, or to control the hardware remotely.

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-8
Hitachi Compute Blade 2500 Series Management Module User Guide
Index
A checking electric power usage 2-109
checking session information 2-57
accurate power control (APC) functionality 2-90
clear blade hvm 5-29
add user account 5-156
clear lcd password 5-154
add user role 5-158
clear mgmt-module boot-disable 5-87
APC 2-90
clear user ldap 5-162
assign blade hvm firmware 5-27
CLI console 1-2
audit log 4-2
initial window 1-9
format 4-11
login 1-8
notes 4-7
logout 1-10
specifications 4-8
cluster management functionality 3-24, 3-26
commands
B collecting log data 5-241
console management 5-262
BMC setting items 2-62 conventions 5-3
BMC time synchronization 2-7 fan module control management 5-151
bmc-reset blade 5-28 identifying parts 5-266
language settings 5-195
LCD touch console management 5-154
C LPAR manager management 5-239
causes and actions to take if importing of import management of fan modules 5-149
file fails 2-119 management of I/O adapters 5-119
change console 5-263 management of management LAN modules
change-password user account 5-160 5-114
chassis ID management of management modules 5-87
overview 2-28 management of switch modules 5-124
setting procedure 2-29 obtaining backups 5-255
checking power supply management 5-137
currently used MAC addresses 2-87 remote access management 5-202
Default Physical MAC address 2-86 security settings 5-196
Default Physical WWN 2-85 server blade management 5-27
Optional Physical MAC address 2-87 server chassis management 5-4
Optional Physical WWN 2-86 SNMP management 5-231
checking currently used WWN 2-86 time settings 5-188

Index-1
Hitachi Compute Blade 2500 Series Management Module User Guide
user management 5-156 delete user account 5-162
commands for console management 5-262 delete user role 5-163
commands for fan control module management dictionary 4-26
5-151 general procedure for updating 4-29
commands for language setting 5-195 digital certificates
commands for LPAR manager management 5-239 overview 2-24
commands for power supply management 5-137 procedure to use certificates signed by
commands for remote access management 5-202 certificate authority 2-27
commands for security settings 5-196 procedure to use self-signed certificates 2-26
commands for SNMP management 5-231 specifications 2-25
commands for time settings 5-188 disabling functionality (LCD touch console) 2-37
commands for user management 5-156 disabling Web console functionality 2-23
commands to collect log data 5-241 disconnect blade bmc session 5-31
commands to identify parts 5-266 disconnect hcsm session 5-203
commands to manage fan modules 5-149 disconnect user session 5-164
commands to manage I/O adapters 5-119 disconnecting session 2-57
commands to manage management LAN modules displaying monitored electric power values 2-108
5-114 DST 2-4
commands to manage management modules 5-87 dump log 4-5
commands to manage server blades 5-27 checking 4-7
commands to manage switch modules 5-124
commands to manage the LCD touch console 5-154
commands to manage the server chassis 5-4 E
commands to obtain backups 5-255 email notification functionality 3-60
configuring notification settings 3-64 configuring notification settings 3-64
configuring SNMP manager settings 3-55 error messages 3-66
connecting to LDAP server 3-38 notification test 3-65
connection to the server chassis (LCD touch requirements 3-61
console) 1-11 setting items 3-63
conventions 5-3 specifications 3-61
currently used MAC addresses environment log 4-2
checking 2-87 checking 4-5
error messages (email notification functionality)
3-66
D
example of changing settings for import file 2-117
dashboard 1-5 exit 5-264
DCMI 2-96 export blade efi setting 5-31
list of supported DCMI commands 2-98 export log failure 5-241
Default Physical MAC address 2-79 export log mar-log all 5-242
checking 2-86 export log mar-log latest 5-242
Default Physical WWN 2-79 export snmp mib 5-232
checking 2-85
delete e-mail mgmt-lan address 5-202
delete hcsm manager 5-202 F
delete hitrack manager 5-203 file management functionality 4-41
delete hvm firmware 5-239 firmware 4-26
delete mgmt-module file 5-88
delete snmp manager 5-231

Index-2
Hitachi Compute Blade 2500 Series Management Module User Guide
G information that can be restored by management
modules 4-40
general procedure (SNMP functionality) 3-53
information to identify LDAP server 3-45
general procedure for configuring Active Directory
init blade bmc setting 5-33
3-37
init blade efisetting 5-34
general procedure for configuring(N+M cold
initial account settings (settings at shipping time)
standby) 3-13
2-32
general procedure for updating
initial settings (settings at shipping time) of IP
dictionary 4-29
addresses 2-40
management module firmware 4-29
initial window (CLI console) 1-9
initializing Optional Physical WWNs and Optional
H Physical MAC addresses 2-82
initializing or changing
HA monitor 3-21 Optional Physical MAC address 2-83
setting the reset path 3-22 Optional Physical WWN 2-82
HCSM 3-2 initializing PIN 2-36
specifying information regarding HCSM 3-5 internal network 2-38
HCSM linkage changing IP address 2-39
alert communication channel 3-3 IP address
command communication channel 3-2 initial settings (settings at shipping time) 2-40
specifying options 3-3
high-speed failover support functionality 3-24, 3-25
highly-reliable HA monitor 3-24 L
cluster management functionality 3-24, 3-26
language settings 2-3
high-speed failover support functionality 3-24,
LCD touch console 1-2
3-25
connection to the server chassis 1-11
troubleshooting for cluster management
disabling functionality 2-37
functionality 3-28
initializing PIN 2-36
Hitachi Fibre Channel adapter
setting PIN 2-36
setting items 2-77
specifications 1-11
settings 2-77
USB flash drive 1-11
user management 2-35
I LDAP linkage 3-35
connecting to LDAP server 3-38
I/O adapter displaying settings for linking with LDAP server
identification lamp 2-51 3-45
identification lamp general procedure for configuring Active
I/O adapter 2-51 Directory 3-37
management LAN module 2-50 information related to LDAP directory searches
management module 2-49 3-46
server blade 2-51 information to identify LDAP server 3-45
switch module 2-52 initializing LDAP linkage settings 3-47
identification lamps registering group 3-41
overview 2-48 registering server certificate 3-38
import blade efi setting 5-32 registering user account 3-39
import file format 2-114 setting information to identify a group 3-46
importing settings file 2-111, 2-116 setting LDAP linkage 3-41
Link Fault Tolerance 2-46

Index-3
Hitachi Compute Blade 2500 Series Management Module User Guide
setting procedure 2-48 support functionality 3-17
login (CLI console) 1-8 time required for failover 3-11
login (Web console) 1-2 N+M failover 3-8
login banner 2-21 N+M failover test 3-19
logout (CLI console) 1-10 N+M recovery 3-8
logs notes (before configuring N+M cold standby) 3-9
dump log 4-5 note on changing settings for import file 2-117
environment log 4-5 notes on using commands 5-3
logs viewable from management modules 4-2 notification test 3-65
MAR log 4-4 NTP server 2-6
Optional Physical MAC address change log 4-4
Optional Physical WWN change log 4-3
system event log 4-3 O
LPAR manager firmware 4-26
operation log 4-2
checking 4-13
format 4-8
M
notes 4-7
Management Information Base (MIB) 3-55 specifications 4-8
management LAN module operation log messages
identification lamp 2-50 list 4-13
management module procedure
identification lamp 2-49 time settings 2-5
redundancy 2-45 Optional Physical MAC address 2-79
restoring settings 4-41 checking 2-87
saving settings 4-40 initializing or changing 2-83
management module firmware 4-26 Optional Physical MAC address change log 4-2
general procedure for updating 4-29 checking 4-4
points to check before update 4-26 Optional Physical WWN 2-79
management modules 1-2 checking 2-86
management network 2-37 initializing or changing 2-82
MAR log 4-2 Optional Physical WWN change log 4-2
checking 4-4 checking 4-3
MIB 3-55 OS console 2-58
modify user account 5-164 notes 2-59
modify user role 5-167 OS serial port 2-58
modules that can be operated from management starting 2-59
module 2-61 overview
chassis ID 2-28
digital certificates 2-24
N
N+M cold standby 3-6
P
general procedure for configuring 3-13
mechanism 3-8 points to check before update
precautions to be taken before configuring 3-9 management module firmware 4-26
procedure for executing Smart configure 3-16 polling 3-51
required unit configuration 3-12 power capacity expansion 2-101
settings inherited 3-9 power control functionality 2-88
Smart configure (overview) 3-14

Index-4
Hitachi Compute Blade 2500 Series Management Module User Guide
power-off sequence setting for server blades when functionality provided by management modules
power capacity is exceeded 2-110 2-8
poweroff blade 5-35 functionality usable with SNMP v3 2-15
poweroff sw-module 5-124 functionality usable with SSH 2-14
poweron blade 5-36 functionality usable with TLS 2-12
poweron sw-module 5-125 IP address restriction (overview) 2-17
pre-configure blade 5-37 FTP connection setting procedure 2-19
notes HTTP connection setting procedure 2-20
OS console 2-59 HTTPS connection setting procedure 2-21
privileges assignable to roles 2-29 SSH/SFTP connection setting procedure 2-20
procedure for executing Smart configure 3-16 Telnet connection setting procedure 2-18
procedure to use certificates signed by certificate procedure for configuring TLS version settings
authority 2-17
digital certificates 2-27 procedure for setting security strength 2-15
procedure to use self-signed certificates security strength 2-10
digital certificates 2-26 TLS version settings (overview) 2-16
send e-mail latest mgmt-lan 5-204
send e-mail select mgmt-lan 5-205
R send hcsm alert 5-205
server blade
registering group 3-41
BMC setting items 2-62
registering server certificate 3-38
host information that can be viewed 3-32
registering user account 3-39
how to disable power control 2-93
relation between N+M cold standby and WWN and
identification lamp 2-51
MAC address 2-81
notes on viewing host information 3-34
remote console 2-56
power supply operation 2-53
checking session information 2-57
overview of disabling power control 2-93
disconnecting session 2-57
setting BMC 2-62
starting 2-56
setting UEFI 2-76
requirements
SMP configuration 2-54
SNMP functionality 3-53
viewing host information 3-32
requirements (email notification functionality) 3-61
server blade firmware 4-26
reset blade 5-38
general procedure for updating 4-36
restart mgmt-module 5-89
points to check before update 4-35
restore blade bmc 5-255
restore blade efi 5-256 server installation and monitoring tool 3-32
set blade ac-recovery 5-39
restore blade fc-hba 5-256
set blade bmc account 5-40
restore factory 5-258
set blade bmc time local 5-42
restoring settings 4-41
set blade ipmi account 5-43
role setting procedure 2-30
set blade led 5-45
set blade lom license 5-46
S set blade maintenance-mode 5-45
set blade mgmt-lan 5-47
saving settings 4-40 set blade mgmt-v6 address 5-48
security setting set blade os-mode 5-50
notes 2-11 set blade preconf 5-51
security settings set blade smp construction 5-52
functionality provided by BMC 2-9 set blade tpm license 5-54
set chassis id 5-4

Index-5
Hitachi Compute Blade 2500 Series Management Module User Guide
set chassis maintenance-mode 5-5 setting items
set chassis usb validity 5-6 Hitachi Fibre Channel adapter 2-77
set e-mail mgmt-lan address 5-206 setting items (email notification functionality) 3-63
set e-mail mgmt-lan notification 5-207 setting items necessary for SNMP agents and
set hcsm agent 5-209 managers on management module 3-56
set hcsm manager 5-209 setting PIN 2-36
set hitrack agent 5-211 setting procedure
set hitrack manager 5-211 chassis ID 2-29
set iobd led 5-119 setting reset the path (HA monitor) 3-22
set language system 5-195 setting UEFI 2-76
set lcd validity 5-154 settings
set mac additional 5-7 Hitachi Fibre Channel adapter 2-77
set mgmt-lan-module led 5-114 switch module 2-77
set mgmt-module dns 5-91 user accounts 2-32
set mgmt-module int-lan 5-95 settings for SNMP agents on management module
set mgmt-module led 5-90 3-58
set mgmt-module maintenance-mode 5-92 settings for SNMP managers on management
set mgmt-module mgmt-lan 5-93 module 3-59
set mgmt-module mgmt-v6 address 5-94 settings inherited (N+M cold standby) 3-9
set mgmt-module serial-port 5-96 show blade bmc account 5-54
set power blade poweroff order 5-137 show blade bmc backup 5-258
set power capping 5-138 show blade bmc session 5-56
set power dcmi-mode 5-139 show blade bmc time local 5-58
set power power-expansion 5-140 show blade efi backup 5-259
set power ps-module 5-141 show blade fc-hba backup 5-260
set remote-access protocol ftp 5-212 show blade firmware 5-59
set remote-access protocol http 5-213 show blade hardware 5-60
set remote-access protocol https 5-215 show blade hvm setting 5-68
set remote-access protocol ssh 5-216 show blade ipmi account 5-70
set remote-access protocol telnet 5-218 show blade maintenance-mode 5-71
set security strength 5-196 show blade mgmt-lan 5-72
set security tls mgmt-module 5-198 show blade mgmt-v6 setting 5-73
set snmp agent 5-232 show blade setting 5-76
set snmp manager 5-233 show blade smp construction 5-78
set sw-module led 5-125 show blade status 5-80
set sw-module maintenance-mode 5-126 show chassis maintenance-mode 5-9
set sw-module mgmt-lan 5-127 show chassis setting 5-10
set sw-module mgmt-v6 address 5-128 show chassis status 5-12
set time dst 5-188 show chassis usb validity 5-13
set time local 5-190 show e-mail mgmt-lan 5-219
set time timezone 5-191 show fan-control-module hardware 5-151
set user ldap group 5-169 show fan-control-module status 5-152
set user ldap search 5-172 show fan-module status 5-150
set user ldap server 5-173 show hcsm setting 5-221
set user password policy 5-174 show hitrack setting 5-223
set web-console function 5-264 show hvm firmware 5-240
set wwn additional 5-8 show iobd hardware 5-120
setting a password expiration date 2-33 show iobd status 5-122
setting BMC 2-62 show language system 5-195

Index-6
Hitachi Compute Blade 2500 Series Management Module User Guide
show lcd setting 5-155 show user ldap 5-179
show log environment 5-243 show user password policy 5-181
show log error 5-244 show user role 5-183
show log hcsm-log 5-245 show user session 5-187
show log mac-edit 5-246 show web-console function 5-265
show log mar-log 5-247 show wwn additional 5-20
show log power 5-248 show wwn current 5-23
show log sel 5-251 show wwn original 5-25
show log svpsts 5-253 shutdown chassis 5-26
show log wwn-edit 5-254 shutdown mgmt-module 5-110
show mac additional 5-14 Smart configure
show mac current 5-16 points to be checked before executing 3-16
show mac original 5-18 Smart configure (overview) 3-14
show mgmt-lan-module hardware 5-115 SMP configuration 2-54
show mgmt-lan-module status 5-117 SNMP functionality 3-51
show mgmt-module firmware 5-97 configuring SNMP manager settings 3-55
show mgmt-module hardware 5-98 general procedure 3-53
show mgmt-module int-lan 5-102 polling 3-51
show mgmt-module maintenance-mode 5-103 requirements 3-53
show mgmt-module mgmt-lan 5-104 setting items necessary for SNMP agents and
show mgmt-module mgmt-v6 setting 5-105 managers on management module 3-56
show mgmt-module mnt-lan 5-107 settings for SNMP agents on management
show mgmt-module serial-port 5-107 module 3-58
show mgmt-module status 5-108 settings for SNMP managers on management
show parts-db list 5-266 module 3-59
show parts-db unit 5-267 specifications 3-52
show power ps-module 5-142 testing SNMP trap notifications 3-59
show power setting 5-143 traps 3-51
show ps-module hardware 5-145 software license information A-2
show ps-module status 5-148 specifications
show remote-access protocol ftp 5-224 digital certificates 2-25
show remote-access protocol http 5-225 SNMP functionality 3-52
show remote-access protocol https 5-227 specifications (email notification functionality) 3-61
show remote-access protocol ssh 5-228 specifications (LCD touch console) 1-11
show remote-access protocol telnet 5-229 specifying all settings for server chassis by using
show security setting 5-199 import file 2-111
show snmp agent 5-235 starting
show snmp manager 5-236 OS console 2-59
show snmp mib 5-238 remote console 2-56
show sw-module firmware 5-129 switch mgmt-module behavior 5-111
show sw-module hardware 5-130 switch module
show sw-module maintenance-mode 5-132 identification lamp 2-52
show sw-module mgmt-lan 5-133 settings 2-77
show sw-module mgmt-v6 setting 5-134 sync mgmt-module firmware 5-111
show sw-module status 5-135 sync mgmt-module fru 5-112
show time dst 5-191 sync mgmt-module int-lan 5-113
show time local 5-193 system event log 4-2
show time timezone 5-194 checking 4-3
show user account 5-176

Index-7
Hitachi Compute Blade 2500 Series Management Module User Guide
T
template of import files 2-113
test snmp trap 5-238
testing SNMP trap notifications 3-59
time setting
NTP server 2-6
time settings 2-3
BMC time synchronization 2-7
DST 2-4
procedure 2-5
traps 3-51
troubleshooting for cluster management
functionality 3-28

U
update blade firmware bulk 5-86
update mgmt-module firmware 5-114
update parts-db 5-268
USB flash drive 1-11
user account
password expiration date 2-33
user accounts 2-31
settings 2-32
user management 2-29
privileges assignable to roles 2-29
role setting procedure 2-30
user management (LCD touch console) 2-35

W
Web console 1-2
dashboard 1-5
login 1-2
window components 1-3
what you can check in change log of Optional
Physical WWNs and MAC addresses 2-87
window components 1-3
WWN and MAC address
selecting (Basic mode) 2-80
selecting (LP mode) 2-81
WWNs and MAC addresses 2-79
WWNs and MAC addresses that can be checked in
management module consoles 2-84

Index-8
Hitachi Compute Blade 2500 Series Management Module User Guide
Hitachi Compute Blade 2500 Series Management Module User Guide
Hitachi Data Systems

Corporate Headquarters
2845 Lafayette Street
Santa Clara, California 95050-2639
U.S.A.
www.hds.com

Regional Contact Information

Americas
+1 408 970 1000
[email protected]

Europe, Middle East, and Africa


+44 (0)1753 618000
[email protected]

Asia Pacific
+852 3189 7900
[email protected]

MK-99CB2500004-04

You might also like