Cb25000044 2500 Series Managment Module User Guide
Cb25000044 2500 Series Managment 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.
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
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
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
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
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
□ 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 2, Preparations for Using Describes the basic configuration for operating the
the Management 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.
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
< > 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.
Preface xvii
Hitachi Compute Blade 2500 Series Management Module User Guide
Convention Description
Logical storage capacity values (for example, logical device capacity) are
calculated based on the following values:
xviii Preface
Hitachi Compute Blade 2500 Series Management Module User Guide
Logical capacity unit Value
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
Note: If you changed the IP address or port number for the management
modules, enter the URL that matches the changed settings.
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
Area (Menu or
Item Description
Pane)
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.
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.
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.
Icon Description
Table 1-3 Summary of chassis statuses (located to the right of the chassis
image)
Icon Description
Power summary
Displays the input power value and the power consumption value.
Item Description
Input power (AC) Present input power Displays the amount of power (AC)
that is currently being supplied to the
system unit.
Power supply (DC) Maximum power supply Displays the maximum power supply
of the system unit.
Item Description
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.
Slot Displays the number of the slot where the module is installed.
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
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.
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
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.
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
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
Item Specifications
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
Related topics
• Connecting the LCD touch console to the server chassis on page 1-11
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
□ Language settings
□ Time settings
□ Network settings
□ Setting server blades, switch modules, and Hitachi Fibre Channel adapter
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.
Table 2-1 Time information that can be set in the management module
LCD touch
Operation Web console CLI console
console
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
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
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.
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
SSH4 22 Ciphertext Y1 Y2 -- Y
SFTP 22 Ciphertext Y1 Y2 -- Y
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.
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.
Table 2-5 Setting security strength for management modules and BMC
Checking the Y Y --
security strength
settings for
management
modules and BMC
Changing the Y Y --
security strength
settings for
management
modules and BMC
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
Related topics
• Security strength for management modules and BMC on page 2-10
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
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.
RSA1024 N N N N
RSA2048 Y Y Y Y
RSA4096 N N N N
DSA1024 N N N N
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
RSA1024 N N N N
RSA2048 Y Y Y Y
RSA4096 N N N N
DSA1024 Y N Y N
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
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
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
DES Y N
AES128 Y Y
MD5 Y N
SHA1 Y Y
Related topics
• Security strength for management modules and BMC on page 2-10
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
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
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
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
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
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
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.
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
Related topics
• Setting the display of a login banner on page 2-22
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
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 or enabling Y Y --
a USB port
Related topics
• Disabling or enabling a USB port on page 2-23
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
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.
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
Item Description
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
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
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
Related topics
• Digital certificates on page 2-24
• Specifications for using digital certificates on page 2-25
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.
Related topics
• Chassis ID on page 2-28
• show chassis setting on page 5-10
• set chassis id on page 5-4
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.
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.
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
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.
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
Status Enabled
Role Administrators
Password password
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.
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.
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
Table 2-19 Initial settings (settings at shipping time) for the management
of the password expiration dates
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.
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
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
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
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
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
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.
Management network
The management network is configured to enable operations from the
management module to each module.
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
Related topics
• Changing the IP address of the internal network on page 2-39
Related topics
• Internal network on page 2-38
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.
Default
Module IP address Subnet mask
gateway
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.
Related topics
• IP address setting items on page 2-41
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.
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.
Related topics
• Setting the IP addresses of management modules, server blades, and
switch modules on page 2-42
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.
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
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
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
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.
Related topics
• Changing the monitoring time for the management network on page
2-48
Related topics
• Improving failure handling by configuring management networks in a
redundant configuration on page 2-46
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.
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
Related topics
• Identification lamp on page 2-48
• show mgmt-module status on page 5-108
• set mgmt-module led on page 5-90
Related topics
• Identification lamp on page 2-48
Related topics
• Identification lamp on page 2-48
• show blade status on page 5-80
• set blade led on page 5-45
Related topics
• Identification lamp on page 2-48
• show iobd status on page 5-122
• set iobd led on page 5-119
Related topics
• Identification lamp on page 2-48
• show sw-module status on page 5-135
• set sw-module led on page 5-125
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.
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
Configuring SMP Y Y --
configurations for server
blades.
Related topics
• Configuring SMP configurations for server blades on page 2-55
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
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.
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
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
Related topics
• Remote console on page 2-56
• show blade bmc session on page 5-56
Related topics
• Remote console on page 2-56
• disconnect blade bmc session on page 5-31
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
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
Item Settings
Port COM2
Data 8 bits
Parity None
Stop 1 bit
For Linux:
Item Settings
/etc/sysconfig/kudzu setting Change to SAFE=yes. (If this setting does not exist,
add it.)
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
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
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.
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.
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
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
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 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 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
Item Description
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.
Item Description
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
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.
Item Description
HTTPS port number Port number of the server blade Web console.
Shows 443. The port number cannot be changed.
Item Description
Item Description
SMASH (WS-Management)
Table 2-43 SMASH (WS-Management)
Port number Enter the port number for receiving connection requests from WS-
Management clients.
SMASH (CLP)
Table 2-44 SMASH (CLP)
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
Message You can enter a maximum 100 lines or 1600 characters for the
message displayed in the login banner. Displayable ASCII
characters are available.
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
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).
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.
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.
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.
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.
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.
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 3
Role of group DN 3
Group DN 4
Role of group DN 4
Group DN 5
Role of group DN 5
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
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).
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.
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
Certificate settings
Table 2-51 Certificate settings - Current certificate information
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
Expiration date of the certificate Displays the expiration date of the certificate.
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.
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
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.
Related topics
• change console on page 5-263
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
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.
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
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
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.
Table 2-54 Commands used for setting WWNs and MAC addresses in Basic
mode
Related topics
• WWNs and MAC addresses on page 2-79
• show blade setting on page 5-76
• set blade preconf on page 5-51
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
Related topics
• Preparation for running the server blades in a redundant configuration (N
+M cold standby) on page 3-6
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
Related topics
• Initializing Optional Physical WWNs and Optional Physical MAC addresses
on page 2-82
• set wwn additional on page 5-8
Related topics
• Initializing Optional Physical WWNs and Optional Physical MAC addresses
on page 2-82
• set mac additional on page 5-7
LCD touch
Item Web console CLI console
console
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.
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
Related topics
• show wwn original on page 5-25
Related topics
• show wwn additional on page 5-20
Related topics
• show wwn current on page 5-23
Related topics
• show mac original on page 5-18
Related topics
• show mac additional on page 5-14
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,
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
Item Description
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.
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.
Related topics
• Setting the upper limit on power consumption during system unit
operation on page 2-90
Related topics
• Server blade operation for when the upper limit on power consumption
during system unit operation is set on page 2-91
Related topics
• Setting the upper limit on power consumption during system unit
operation on page 2-90
Related topics
• Disabling power control for server blades on page 2-93
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
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:
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.
Related topics
• Enabling and disabling the DCMI mode on page 2-97
• Manual Hitachi Compute Blade 2500 Series Getting Started Guide
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
Table 2-60
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
The following shows an example when six power supply modules are
mounted in an N+1 redundant configuration.
The following table describes the consoles used when you set the power
capacity expansion functionality from a management module.
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
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 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.
Legend:
--: Not supported.
Related topics
• Power capacity expansion functionality on page 2-101
Related topics
• set power power-expansion on page 5-140
Related topics
• Checking electric power usage on page 2-109
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.
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
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
Related topics
• set power blade poweroff order on page 5-137
LCD touch
Operation Web console CLI console
console
Related topics
• Checking the template used to set the import file format on page 2-113
• Importing a settings file on page 2-116
#!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
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.
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
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.
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.
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.
□ Syslog transfer
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.
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.
Related topics
• Specifying the HCSM linkage options on page 3-3
• Specifying information regarding HCSM registered in the management
module on page 3-5
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.
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.
Operation Command
Related topics
• Linkage with HCSM on page 3-2
• show hcsm setting on page 5-221
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.
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
Related topics
• N+M cold standby on page 3-6
• Mechanism of N+M cold standby on page 3-8
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)
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
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
Related topics
• Settings inherited through N+M cold standby on page 3-9
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
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
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
Related topics
• Points to be checked before executing Smart configure on page 3-16
• pre-configure blade on page 5-37
Related topics
• N+M cold standby on page 3-6
Related topics
• WWNs and MAC addresses that can be checked in management module
consoles on page 2-84
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
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.
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.
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
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.
Related topics
• Setting the reset path on page 3-22
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.
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:
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
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
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
Related topics
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27
Related topics
• Enabling the high-speed failover support functionality for the HA monitor
and the cluster management functionality on page 3-27
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
1 Category HA monitor
Note Before changing cluster settings from the Web console, power
off all server blades in the cluster.
2 Category HA monitor
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".
3 Category HA monitor
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".
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.
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" .
Note The reset path is in the error state. If a system failure occurs, a
failover cannot be performed.
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.
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.
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
Related topics
• delete blade os-info on page 5-30
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.
Related topics
• set user ldap server on page 5-173
• General procedure for configuring Active Directory on page 3-37
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
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
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.
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.
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
Related topics
• show user ldap on page 5-179
Operation Command
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.
Related topics
• set user ldap server on page 5-173
Table 3-14 Commands used to configure the settings related to the LDAP
directory search.
Operation Command
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
Operation Command
Specify the setting to enable or disable group authentication and set user ldap group
the setting of the authentication method.
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
Related topics
• clear user ldap on page 5-162
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
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.
Item Description
Item Description
Item Description
Configuring an SNMP Y Y --
manager
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
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
Item Description
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.
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.
Item Description
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.)
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
Related topics
• show snmp agent on page 5-235
• set snmp agent on page 5-232
Related topics
• show snmp manager on page 5-236
• set snmp manager on page 5-233
Related topics
• test snmp trap on page 5-238
LCD touch
Operation Web console CLI console
console
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
Item Description
Attachment1 svpsts-YYYYMMDD-hhmmss.gz
trc-YYYYMMDD-hhmmss.tar.gz2
marlog.gz
Attachment1 svpsts-YYYYMMDD-hhmmss.gz
trc-YYYYMMDD-hhmmss.tar.gz2
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.
Item Description
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.
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].
Item Description
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).
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.
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: ? @ $ # % ^ - + = _ . []
Attach log file Specify whether to attach a log file to an email message.
Operation Command
Add and configure an email destination address set 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
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
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.
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.
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.
Note:
• Only one syslog server can be specified as destination.
• Syslog transfer does not support SSL 3.0.
Item Description
System event log This records information, warnings, and failure events that
(SEL) occurred on the system unit.
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.
LCD touch
Operation Web console CLI console
console
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
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.
Related topics
• show log sel on page 5-251
Related topics
• show log wwn-edit on page 5-254
Related topics
• show log mac-edit on page 5-246
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
• show log mar-log on page 5-247
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.
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
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
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.
Related topics
• export log failure on page 5-241
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
Table 4-3 Specifications of the operation log and the 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.
Date and 29 This records the date, time, and time zone --
time when the operation was logged.
(date)
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.
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.
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 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.
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 (").
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
Operation
ID event Collection trigger Message
categories
1802 Logout from the system Logged out from the System
console Console.
Username: xxx Session ID: xxx
Source IP address: xxx Cause: xxx
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
3834 Saving an SSH host key SSH host key pair is backed up.
pair Channel: xxx File: xxx
3907 Send to the HCSM test On Server BladeN, HCSM send test
alert alert(N+M cold standby)
Channel:xxx Category: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
1009 Logout from the server Logged out from the server blade
blade Web console Web console.
Username: xxx Source IP
address: xxx Cause: xxx
Name Description
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
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.
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.
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
Firmware to be
File to be downloaded Result of decompression
updated
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.
Related topics
• show mgmt-module firmware on page 5-97
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.
Related topics
• update mgmt-module firmware on page 5-114
Related topics
• show mgmt-module firmware on page 5-97
Related topics
• General procedure for updating server blade firmware on page 4-36
Note:
• For details on how to use HCSM to update management module firmware
and dictionary, see the HCSM manual.
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.
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.
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.
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
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
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
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.
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.
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
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
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
Tip: You can download manuals from the Web console menu.
Related topics
• About the file management functionality on page 4-41
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
Command conventions
The following table explains the command conventions that are used in this
manual.
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>.
Use commas to separate the If you specify "0,2,3" for a command, command
numbers. processing is performed for 0, 2, and 3.
set chassis id
Changes the chassis ID.
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
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
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.
$
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.
$
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:
Rules
To specify settings for onboard LAN 1, use mezzanine card 1 to specify the
following: -c mezzanine -n 1.
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
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.
Syntax
show chassis maintenance-mode
Privilege
Chassis privilege
Parameters
None
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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 --
Execution results
Table 5-8 Chassis USB validity
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.
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.
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.
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.
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.
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.
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.
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:
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.
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:
shutdown chassis
Shuts down the server chassis.
Syntax
shutdown chassis [-F]
Privilege
Chassis privilege
Execution example
To shut down the server chassis:
shutdown chassis
Rules
When execution of this command finishes, sessions with management
modules are closed.
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.
Execution example
To assign the LPAR manager firmware in area 0 to server blade 1:
assign blade hvm firmware 1 -b 0
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.
-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
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.
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
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.
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.
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.
$
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.
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.
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
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.
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.
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.
Execution example
To shut down the OS running on server blade 1:
poweroff blade 1
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
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:
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
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
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 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.)
Syntax
set blade bmc account <blade_no> -a <account_no> [-u <account_use>]
[-n <user_name>] [-p <password>] [-F]
Privilege
Server blade privileges
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.
Rules
You cannot disable the BMC user account number 1 for each server blade.
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.
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.
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.
$
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
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.
$
Syntax
set blade lom license <blade_no> -l <lom_license> {-k <lom_key>¦-f
<key_file>} [-F]
Privilege
Server blade privileges
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.
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
Syntax
set blade mgmt-v6 address <blade_no> -st <setting> [-i <ip_address>]
[-p <prefix_len>] [-gs <dgw_setting>] [-g <default_gateway>] [-F]
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):
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).
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
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.)
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
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.)
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:
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.
$
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.
$
Syntax
show blade bmc session [<blade_no>]
Privilege
Server blade privileges
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.
Rules
• User name might not be 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.
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.
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 : -----
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)
Tip: This item is displayed only for primary server blades in an SMP
configuration.
Tip: This item is displayed only for primary server blades in an SMP
configuration.
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.
Tip: The above items are displayed only if a PCI expansion blade is
installed.
Tip: The above items are displayed only if an expansion blade is installed.
Tip: The above items are displayed only if an expansion blade is installed.
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.
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 :
Execution results
The following table shows the items that are displayed as the execution
results of this command.
Syntax
show blade maintenance-mode [<blade_no>]
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.
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.
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.
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.
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
Syntax
update blade firmware bulk [<blade_no>] -f <fw_file_name> [-F]
Privilege
Server blade privileges
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.)
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.
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.
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
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
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.
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.
Syntax
set mgmt-module maintenance-mode <mgmt_no> -m <mnt_mode> [-F]
Privilege
Chassis privilege
Parameters
<mgmt_no>
Management module number
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.
$
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)
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.
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)
-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).
Syntax
set mgmt-module int-lan -i <ip_addr> [-F]
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.
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.
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.
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
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
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)
SVP Model Type for Corporate logo displayed in the Web console
Corporate Logo
Syntax
show mgmt-module int-lan
Privilege
Chassis privilege
Parameters
None
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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
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
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.
Syntax
show mgmt-module serial-port
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.
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
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.
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.
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.
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.
Rules
Under the following conditions, you cannot execute this command:
• Only one management module is installed.
• Communication with the standby management module is impossible.
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.
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.
Syntax
set mgmt-lan-module led [<mgmt_lan_no>] -l <led_type> -t
<led_on_off> [-F]
Privilege
Chassis privilege
Parameters
<mgmt_lan_no>
Execution example
To turn on the identification LED indicator of management module 1:
set mgmt-lan-module led 1 -l lid -t on
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
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)
Syntax
show mgmt-lan-module status [<mgmt_lan_no>]
Privilege
Chassis privilege
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.
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
Execution example
To turn on the identification LED indicator of I/O adapter 01A:
set iobd led -i 01A -l lid -t on
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
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)
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:
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
$
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.
$
Syntax
set sw-module led [<sw_no>] -l <led_type> -t <led_on_off> [-F]
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
Syntax
set sw-module maintenance-mode <sw_no> -m <mnt_mode> [-F]
Privilege
Switch module privileges
Parameters
<sw_no>
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.
$
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
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
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
-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).
Syntax
show sw-module firmware [<sw_no>]
Privilege
Switch module privilege
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.
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.
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)
Syntax
show sw-module maintenance-mode [<sw_no>]
Privilege
Chassis privilege
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.
Syntax
show sw-module mgmt-lan [<sw_no>]
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.
Syntax
show sw-module mgmt-v6 setting [<sw_no>]
Privilege
Network privilege
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)
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.
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
Syntax
set power capping -b <blade_no> [-a <blade_power_apc>] [-F]
Privilege
Chassis privilege
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.
Syntax
set power dcmi-mode -m <dcmi_mode> [-F]
Privilege
Chassis privilege
Execution example
To enable DCMI mode
$ set power dcmi-mode -m enable -F
I0001 : Setting was completed.
S0002 : Command succeeded.
S0000 : Command was finished.
$
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
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
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
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.
Syntax
show power setting
Privilege
Chassis privilege
Parameters
None
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
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
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)
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
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.
Syntax
show fan-control-module status [<fan_control_no>]
Privilege
Chassis privilege
Parameters
<fan_control_no>
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.
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.
$
Syntax
set lcd validity -v <tc_valid> [-F]
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
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.
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.
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.
$
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.
Syntax
add user role -i <role_id> [-b <blade_no>] [-s <switch_no>] [-n] [-
c] [-a] [-r] [-k] [-F]
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
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.
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.
$
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
Syntax
delete user account -i <user_id> [-F]
Privilege
Account privilege
Parameters
-i <user_id>
Account name
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.
$
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.
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
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
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)$".
Execution example
To make the account accountname temporarily unavailable:
$ modify user account -i accountname -s disable
Confirm? (y/[n]):y
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.
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
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.
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.
Execution example
To set up the LDAP group authentication:
set user ldap group -m xxxxx -g0 xxxxx
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
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).
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
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.
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.
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.
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.
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.
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.
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
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.
Execution results
The following table shows the items that are displayed as the execution
results of this command.
Syntax
show user session
Privilege
Account privilege
Parameters
None
Execution example
To display information about user sessions:
show user session
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>
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
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.
Execution example
To change the time settings for management modules:
set time local -d "2012-05-01 15:00:00"
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
Syntax
show time dst
Privilege
Chassis privilege
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.
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.
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.
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.
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
Syntax
show language system
Privilege
Chassis privilege
Parameters
None
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
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 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.
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
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
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.
$
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.
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
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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]
Syntax
delete hcsm manager -i <hcsm_ip_addr> [-F]
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
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
Syntax
disconnect hcsm session -i <hcsm_ses_id> [-F]
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
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
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
Syntax
send hcsm alert -b <blade_no> -t <alert_type> [-F]
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
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.
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
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.
Execution example
To change email notification settings:
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
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.
Related topic
• Manual Hitachi Command Suite Compute Systems Manager User Guide
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
Syntax
set hitrack manager -i <hitrack_ip_addr> [-F]
Privilege
Chassis privilege
Execution example
set hitrack manager -i 192.168.0.20
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
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
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.
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>
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
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>
Execution example
To permit SSH connections from 192.168.0.0 to 192.168.0.255:
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
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
Syntax
show e-mail mgmt-lan
Privilege
Chassis privilege
Parameters
None
Execution example
To display the email notification settings:
show e-mail mgmt-lan
Syntax
show hcsm setting
Privilege
Chassis privilege
Parameters
None
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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.
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.
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
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.
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.
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.
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.
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
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>
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
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
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
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.
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.
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.
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.
Syntax
test snmp trap [-F]
Privilege
Chassis privilege
Execution example
To send an SNMP test trap:
test snmp trap
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.
$
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.
Syntax
update hvm firmware -f <fw_file_name> -b <hvm_bank_no> [-F]
Privilege
Chassis privilege
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.
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.
Execution example
To obtain dump log data:
export log failure -d
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
Syntax
export log mar-log latest [-d] [-F]
Privilege
Chassis privilege
Execution example
To output the latest MAR log data to the home directory for management
modules:
export log mar-log latest -d
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
Execution example
To display environment log data for server blade 1:
show log environment -m blade -s 1
Execution results
The following table shows the items that are displayed as the execution
results of this command.
Syntax
show log error
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.
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.
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.
Syntax
show log mar-log
Privilege
Chassis privilege
Parameters
None
Execution example
To display MAR log data:
show log mar-log
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.
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.
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.)
Execution example
To display system event log (SEL) data:
show log sel
To display system event log (SEL) data for all server blades:
show log sel -f B
Execution results
The following table shows the items that are displayed as the execution
results of this command.
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
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.
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
Execution example
To restore the BMC settings of server blade 1:
restore blade bmc 1 -n 0
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
2 02A, 02B --
4 04A, 04B --
: : :
: : :
14 14A, 14B --
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
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
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.
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.
2 02A, 02B --
4 04A, 04B --
: : :
: : :
14 14A, 14B --
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.
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.
Rules
Because Hitachi Fibre Channel mezzanine cards cannot be installed, you
cannot specify a mezzanine card.
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
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.
Syntax
exit
Privilege
All privileges
Parameters
None
Execution example
To end the CLI console:
exit
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.
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.
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.
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.
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.
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
Software
Software license agreement
name
This software contains code derived from the RSA Data Security Inc. MD5
Message-Digest Algorithm.
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).
bzip2 This program, "bzip2", the associated library "libbzip2", and all
documentation, are copyright (C) 1996-2007 Julian R Seward. All rights
reserved.
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.
Julian Seward,[email protected]
bzip2/libbzip2 version 1.0.5 of 10 December 2007
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.
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.
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.
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
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).
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:
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.
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
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.
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.
3. This Copyright notice may not be removed or altered from any source
or altered source distribution.
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
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:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of 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.
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
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
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.
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.
openslp The following copyright and license is applicable to the entire OpenSLP
project (libslp, slpd, and related documentation):
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
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.
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
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.
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.
• http://www.ossp.org/pkg/lib/uuid/
• ftp://ftp.ossp.org/pkg/lib/uuid/
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
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.*.
ID Level Message
Description
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[Meaning] The cooling rotation speed is restored the normal level. X shows the part that
event occurred.
[Action] No particular action required.
[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.
[Meaning] The AC input error is corrected. X shows the part that error occurred.
[Action] No particular action required.
[Meaning] Uncorrectable CPU error is occurred. X shows the part that error occurred.
[Action] Consult your reseller or maintenance personnel.
[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.
[Meaning] Uncorrectable memory error is occurred. X shows the part that error occurred.
[Action] Consult your reseller or maintenance personnel.
[Meaning] Event at the part shown in X is logged. Y shows the event type.
[Action] No particular action required.
[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.
[Meaning] In a server blade at the part shown in X, firmware update has started.
[Action] No particular action required.
[Meaning] In a server blade at the part shown in X, firmware update has completed.
[Action] No particular action required.
[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.
[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.
[Meaning] The LAN port route is restored from the changed route of message ID: FF05.
[Action] No particular action required.
[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.
[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.
[Meaning] Support center report is not available due to failure in report function x.
[Action] Contact your reseller or call for maintenance personnel.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[Meaning] The connection between the management module and HCSM is established.
[Action] No particular action required.
[Meaning] This message is an alert for confirming connection between the management
module and HCSM.
[Action] No particular action required.
[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.
[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.
[Meaning] The module information has been changed. X indicates the module name.
[Action] No particular action required.
[Meaning] The module information has been changed. X indicates the module name.
[Action] No particular action required.
A
active blade
When using the N+M cold standby function, the active blade is the server blade that is
actively running your applications.
B
BIOS
Basic Input/Output System
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.
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
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
Americas
+1 408 970 1000
[email protected]
Asia Pacific
+852 3189 7900
[email protected]
MK-99CB2500004-04