Fujitsu M12, M10 User Manual

Fujitsu SPARC M12 and

Fujitsu M10/SPARC M10

RCIL User Guide

Manual Code: C120-E718-07EN March 2019

and/or its affiliates provided technical input and review on portions of this material.

Oracle

and/or its affiliates and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document, and such products,

technology and this document are protected by copyright laws, patents, and other intellectual property laws and international treaties.

document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of such

This product or technology, or of this document, may be reproduced in any form by any means without prior written authorization of Oracle and/or its affiliates and Fujitsu Limited, and their applicable licensors, if any. The furnishings of this document to you does not give you any rights or licenses, express or implied, with respect to the product or technology to which it pertains, and this document does not contain or represent any commitment of any kind on the part of Oracle or Fujitsu Limited or any affiliate of either of them. This

document and the product and technology described in this document may incorporate third-party intellectual property copyrighted by and/or licensed from the suppliers to

Oracle and/or its affiliates and Fujitsu Limited, including software and font technology.

the terms of the GPL or LGPL, a copy of the source code governed by the GPL or LGPL, as applicable, is available upon request by the End User. Please contact Oracle and/or its

Per affiliates or Fujitsu Limited. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California.

registered trademark of The Open Group.

UNIX

is a

Oracle

and Java are registered trademarks of Oracle and/or its affiliates.

Fujitsu

and the Fujitsu logo are registered trademarks of Fujitsu Limited.

SPARC

Enterprise, SPARC64, SPARC64 logo and all SPARC trademarks are trademarks or registered trademarks of SPARC International, Inc. in the United States and other

countries and used under license.

names may be trademarks of their respective owners.

Other If

this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S.

GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered

U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,

use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. Disclaimer: expressly set forth in the license agreement pursuant to which the product or technology is provided. EXCEPT WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCH PRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Unless otherwise expressly set forth in such agreement, to the extent allowed by applicable law, in no event shall Oracle or Fujitsu Limited, and/or any of their affiliates have any liability to any third party under any legal theory for any loss of revenues or profits, loss of use or data, or business interruptions, or for any indirect, special, incidental or consequential damages, even if advised of the possibility of such damages. DOCUMENTATION WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright Oracle Oracle même, ces produits, technologies et ce document sont protégés par des lois sur le droit d’auteur, des brevets, et d'autres lois sur la propriété intellectuelle et des traités internationaux. Ce Aucune partie de ce produit, de ces technologies ou de ce document ne peut être reproduite sous quelque forme que ce soit, par quelque moyen que ce soit, sans l'autorisation écrite préalable d'Oracle et/ou ses affiliés et de Fujitsu Limited, et de leurs éventuels concédan ts de licence. Ce document, bien qu'il vous ait été fourni, ne vous confère aucun droit et aucune licence, exprès ou tacites, concernant le produit ou la technologie auxquels il se rapporte. Par ailleurs, il ne contient ni ne représente aucun engagement, de quelque type que

Ce licence par des fournisseurs à Oracle et/ou ses sociétés affiliées et Fujitsu Limited, y compris des logiciels et des technologies relatives aux polices de caractère s. Conformément Veuillez contacter Oracle et/ou ses affiliés ou Fujitsu Limited. Cette distribution peut comprendre des composants développés par des parties tierces. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. UNIX Oracle Fujitsu SPARC dans d'autres pays. Tout Si compte du Gouvernement des Etats-Unis, la notice suivante s'applique : U.S.

use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. Avis produit ou toute technologie décrits dans les présentes correspondent aux garanties expressément stipulées dans le contrat de licence régissant le produit ou la technologie fournis. SAUF ENTITE DECLINENT TOUT ENGAGEMENT OU GARANTIE, QUELLE QU'EN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CE PRODUIT, CETTE TECHNOLOGIE OU CE DOCUMENT, LESQUELS SONT FOURNIS EN L'ETAT. EN OUTRE, TOUTES LES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON, SONT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE. Sauf mention contraire expressément stipulée dans ce contrat, dans la mesure autorisée par la loi applicable, en aucun cas Oracle ou Fujitsu Limited et/ou l'une ou l'autre de leurs sociétés affiliées ne sauraient être tenues responsables envers une quelconque partie tierce, sous quelque théorie juridique que ce soit, de tout manque à gagner ou de perte de profit, de problèmes d'utilisation ou de perte de données, ou d'interruptions d'activités, ou de tout dommage indirect, spécial, secondaire ou consécutif, même si ces entités ont été préalablement informées d'une telle éventualité. LA EXCLUE, DANS LA MESURE AUTORISEE PAR LA LOI EN VIGUEUR, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE,

The only warranties granted by Oracle and Fujitsu Limited, and/or any affiliate in connection with this document or any product or technology described herein are those

EXPRESSLY SET FORTH IN SUCH AGREEMENT, ORACLE OR FUJITSU LIMITED, AND/OR THEIR AFFILIATES MAKE NO REPRESENTATIONS OR

PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED

et/ou ses affiliés ont fourni et vérifié des données techniques de certaines parties de ce composant. et/ou ses affiliés et Fujitsu Limited détiennent et contrôlent chacun des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document. De

document, le produit et les technologies afférents sont exclusivement distribués avec des licences qui en restreignent l'utilisation, la copie, la distribution et la décompilation.

soit, de la part d'Oracle ou de Fujitsu Limited, ou des sociétés affiliées de l'une ou l'autre entité.

document, ainsi que les produits et technologies qu'il décrit, peuvent inclure des droits de propriété intellectuelle de parties tierces protégés par le droit d’auteur et/ou cédés sous

aux conditions de la licence GPL ou LGPL, une copie du code source régi par la licence GPL ou LGPL, selon le cas, est disponible sur demande par l'Utilisateur Final.

est une marque déposée de The OpenGroup.

Java sont des marques déposées d'Oracle Corporation et/ou de ses affiliés.

logo Fujitsu sont des marques déposées de Fujitsu Limited.

et le

Enterprise, SPARC64, le logo SPARC64 et toutes les marques SPARC sont utilisées sous licence et sont des marques déposées de SPARC International, Inc., aux Etats-Unis et

autre nom mentionné peut correspondre à des marques appartenant à leurs propriétaires respectifs.

logiciel, ou la documentation qui l'accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l'utilise pour le

GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered

U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,

non-responsabilité : les seules garanties octroyées par Oracle et Fujitsu Limited et/ou toute société affiliée de l'une ou l'autre entité en rapport avec ce document ou tout

MENTION CONTRAIRE EXPRESSEMENT STIPULEE AU DIT CONTRAT, ORACLE OU FUJITSU LIMITED ET/OU LES SOCIETES AFFILIEES A L'UNE OU L'AUTRE

DOCUMENTATIO N EST FOURNIE "EN L'ETAT" ET TOUTE AUTRE CONDITION, DECLARATION ET GARANTIE, EXPRESSE OU TACITE, EST FORMELLEMENT

L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.

Preface　v

Chapter 1　Overview of the Remote Power Management Function of SPARC

M12 and SPARC M10　1

1.1　About the Remote Power Management Function for SPARC M12 and

SPARC M10　1

1.2　Understanding the Forms of Connection for Remote Power

Management　3

1.3　Remote Power Management Mechanism　5

Chapter 2　Basic Flow

2.1　Before Configuring Remote Power Management　9

2.2　Steps for Configuring Remote Power Management　9

2.2.1　Creating a Management File　9

for Configuring Remote Power Management　9

2.2.2　Enabling/Disabling the IPMI Service Used for the Remote Power

Management Function　11

2.2.3　Checking the Remote Power Management Settings　12

2.2.4　Initializing the Remote Power Management

2.2.5　Enabling/Disabling the Remote Power Management Function

2.2.6　Setting a Remote Power Management Group　12

2.2.7　Acquiring the setting information on a remote power management

group　13

Settings　12

iii

Chapter 3　Examples of Remote Power Management Configuration　15

3.1　Configuring the Remote Power Management for the First Time　15

3.1.1　System That is Configured with a Host Node and an I/O Node

3.1.2　System That is Configured with a Host Node and a Remote

Power Distribution Unit　28

3.1.3　System That

Remote Power Distribution Unit　36

Configured with Multiple Host Nodes and a

3.1.4　System That is Configured with Host Nodes, in Which Physical

Partitions (PPARs) are Specified as Subnodes, and a Remote

Power Distribution Unit　43

3.1.5　System in Which Multiple Remote Power Management Groups

are Set　50

3.2　Adding or Removing a Node in an Existing Remote Power Management

Group　58

3.2.1　Adding an I/O Node　59

3.2.2　Adding a Host Node　64

3.2.3　Removing an I/O Node　69

3.2.4　Removing a Host Node　73

3.3　Maintaining an I/O Node　78

3.3.1　Maintaining an ETERNUS　78

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 2019iv

Preface

This document provides information on the Remote Cabinet Interface over LAN (referred to below as RCIL) function used to manage the power supply of I/O devices from SPARC M12 and SPARC M10 from Fujitsu, such as the Fujitsu storage system ETERNUS. It is recommend to read the Fujitsu SPARC M12 and

Operation and Administration Guide to better understand the contents of this document.

Fujitsu M10 is sold as SPARC M10 Systems by Fujitsu in Japan. Fujitsu M10 and SPARC M10 Systems are identical products.

This preface includes the following sections:

■

Audience

■

Notes on Safety

Read the following documents thoroughly before using or handling the SPARC M12/M10.

■

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Important Legal and Safety Information

■

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Safety and Compliance Guide

Text Conventions

This manual uses the following fonts and symbols to express specific types of information.

Font/Symbol Meaning Example

aBbCc123

AaBbCc123

Italic Indicates the name of a reference manual. See the Fujitsu M10-1/SPARC M10-1

" " Indicates the names of chapters, sections, items,

What you type, when contrasted with on-screen computer output. This font is used to indicate an example of command input.

The names of commands, files, and directories; on-screen computer output. This font is used to indicate an example of command output in the frame.

buttons, or menus.

XSCF>

XSCF> User Name: Privileges:

Installation Guide.

See "Chapter 2 Network Connection."

adduser jsmith

showuser -P

jsmith useradm auditadm

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 2019viii

Command Syntax in the Text

While the XSCF commands have a section number of (8) or (1), it is omitted from the text. For details on the commands, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual.

Syntax of the Command-Line Interface (CLI)

The command syntax is as follows:

■

A variable that requires the input of a value is in Italics.

■

An optional element is enclosed in [].

■

A group of options for an optional keyword is enclosed in [] and delimited by |.

Document Feedback

If you have any comments or requests regarding this document, please take a moment to share them with us. Along with the manual code, manual title, and page number, state your points specifically at one of the following websites:

■

Global site

http://www.fujitsu.com/global/contact/

■

Japanese site

http://www.fujitsu.com/jp/products/computing/servers/unix/sparc/contact/

Preface ix

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 2019x

Chapter 1

Overview of the Remote Power Management Function of SPARC M12 and SPARC M10

This chapter provides an overview and the mechanism of the remote power management function that can be used in SPARC M12 and SPARC M10.

■

About the Remote Power Management Function for SPARC M12 and SPARC M10

■

Understanding the Forms of Connection for Remote Power Management

■

Remote Power Management Mechanism

1.1 About the Remote Power Management

Function for SPARC M12 and SPARC M10

The remote power management function for SPARC M12 and SPARC M10 (Remote Cabinet Interface over LAN: RCIL) is an interface which controls the remote power management function for the power supply between SPARC M12 and SPARC M10 systems or I/O devices. An original interface based on IPMI over LAN is used. following functions among the typical IPMI functions are supported, then the hardware and operating systems to be controlled can be incorporated as the targets for the remote power management without having to consider differences between them.

■

Power on and off: Chassis Control

■

Obtaining the power status: Get Chassis Status

Table 1-1 shows the terms and definitions that are used with the remote power

management function for SPARC M12 and SPARC M10.

the

Table 1-1

Term Definition

Terms and Definitions Used for Remote Power Management

Host node Server that supports the remote power management function for SPARC

M12 and SPARC M10. SPARC M12-1, M12-2, M12-2S, M10-1, M10-4, and M10-4S support the remote power management function for SPARC M12 and SPARC M10.

Subnode Physical partition in SPARC M12 and SPARC M10.

I/O node I/O devices that support the remote power management

SPARC M12 and SPARC M10, such as the ETERNUS, and remote power distribution units.

Remote power management group

Group obtained from the grouping of remote power management targets, such as a host node, subnode, and I/O node. A unique group ID is assigned to a remote power management group.

function for

If the remote power management function is used, create a remote power management

group in combination with power-interlocked nodes. You can control remote power management per created remote power management group.

Note -

Each host node, sub node, or I/O node can be set in only one remote power management

group.

Figure 1-1

Example of a Remote Power Management Group of SPARC M12

and SPARC M10

Remote power management

Host Node #0 (Master)

Sub Node PPAR/Logical domain

Controller BB#1 Slave XSCF

Controller BB#0 Master XSCF

RCIL commands

Host Node #1 I/O Node #0

Controller BB#1 Slave XSCF

Controller BB#0 Master XSCF

Controller

I/O Node #1

Controller

IPMI over LAN

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 20192

1.2 Understanding the Forms of

Connection for Remote Power Management

Connect through a LAN the host nodes, sub nodes, and I/O nodes that support the remote power management function for SPARC M12 and SPARC M10.

The following table lists the connection specifications.

Table 1-2

Item Description

Forms of connection

Transmission speed

Internet protocol IPv4

DHCP Unsupported

Connection protocol

*1 The supported IPMI version is IPMI 2.0. In SPARC M12 and SPARC M10, IPMI can be used only by the remote power management function. IPMI cannot be used by ipmitool or any function other than the remote power management function for SPARC M12 and SPARC M10.

Power Control Connection Specifications

LAN connection The connection takes either of the following forms:

- Using XSCF-LAN#0

- Using XSCF-LAN#0 and XSCF-LAN#1

100 Mbps or more

If the remote power management function for SPARC M12 and SPARC M10 is used, you must set a fixed IP address for a connection target.

IPMI

(*1) over LAN

(Intelligent Platform Management Interface)

Standard connection for remote power management

Connect through an identical LAN the host nodes, sub nodes, and I/O nodes that are equipped with a controller that supports the remote power management function for SPARC M12 and SPARC M10.

Figure 1-2

Host Node #0

PPAR

Host Node #1

PPAR

Chapter 1　Overview of the Remote Power Management Function of SPARC M12 and SPARC M10 3

Standard Forms of Connection for Remote Power Management

I/O Node #0

Controller

NIC

HUB/router

LAN

Controller

NIC

I/O Node #1

Controller

NIC

Connection when the controllers are duplicated

If the host node controllers are duplicated, each controller can be connected to the same LAN. Operation of the remote power management is performed from the master XSCF.

Figure 1-3

Host Node #0

PPAR

Host Node #1

PPAR

Note -

Forms of Connection for the Remote Power Management when the Controllers are Duplicated

I/O Node #0

Controller

NIC

Controller 0

NIC

Controller 1

NIC

For the I/O nodes that can be set as a takeover IP address between the controllers, we

HUB/router

LAN

Controller

NIC

I/O Node #1

Controller #0

NIC

Controller #1

NIC

recommend setting a takeover IP address. In such cases, set controllers 0 and 1 to the same IP address in the management file for configuring a remote power management group. For details on

specific settings, see "3.1.1 System That is Configured with a Host Node and

an I/O Node."

Connection when paths are duplicated

The paths of the remote power management connection can be duplicated under the following conditions.

■

Two LAN cards can be mounted on the controllers of all nodes.

■

Two LAN cards can be mounted on the controllers of the host nodes, and I/O nodes have either of the following configurations.

- The controllers of the I/O nodes are duplicated.

- Two LAN cards can be mounted on the controllers of the I/O nodes.

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 20194

Figure 1-4

Host Node #0

PPAR

Forms of Connection for the Remote Power Management when Paths are Duplicated

I/O Node #0

Controller #0

NIC #0

NIC #1

Controller #1

NIC #0

NIC #1

HUB/router

LAN #0

Controller #0

NIC

Controller #1

NIC

Host Node #0

PPAR

Controller #0

NIC #0

NIC #1

HUB/router

LAN #1

I/O Node #1

Controller #0

NIC #0

NIC #1

1.3 Remote Power Management

Mechanism

Remote power management for SPARC M12 and SPARC M10 is controlled per remote power management group.

Of the host nodes in a group, the host nodes with the remote power management function enabled are targeted for remote power management. The power supply status of a remote power management group is determined node status in the group.

■

On state The power is on to one of the host nodes in the remote power management group.

■

Off state The power is off to all the host nodes in the remote power management group.

This section describes the mechanism of interlocking when powering on and off, with the following settings assumed.

depending on the host

LAN #0 system

LAN #1 system

Chapter 1　Overview of the Remote Power Management Function of SPARC M12 and SPARC M10 5

Table 1-3

Setting Item Host Node #0 Host Node #1 Host Node #2 I/O Node #0 I/O Node #1

Interlocking setting

Master node Yes No Yes Setting

Remote Power Management Mechanism (Example)

Disable Enable Enable Setting

disabled

Setting disabled

Mechanism of interlocking when powering on

If any of the host nodes in a remote power management group is powered on, then all of the host nodes, subnodes, and I/O nodes in the group are powered on. They are powered on in the order of host node and I/O node.

Note -

You can set the length of time that the host node waits until I/O node devices are accessible. For this setting, use the setpowerupdelay command of the XSCF firmware For details, see "4.2.2 Setting/Checking the Wait Time for Air Conditioning" in the Fujitsu

SPARC M12 and Fujitsu M10/SPARC M10 System

If the length of time that the host node waits is not set, the host node may be unsuccessful in accessing an I/O node device and fail to start the system. In addition, replacing an I/O node or changing the settings of an I/O node may change the time taken until the relevant device becomes accessible. This change in time may prevent the host node from accessing the device. When an I/O node has been replaced or the settings of an I/O node have been changed, use the setpowerupdelay command to set the length of time that the host node

Operation and Administration Guide.

waits, again.

Mechanism of interlocking when powering off

After all the host nodes in a remote power management group are powered off, all I/O nodes in the group are powered off.

Remote power management using Wake on LAN

Generally, the target nodes of the remote power management function for SPARC M12 and SPARC M10 are the hosts and I/O devices on which a controller is mounted. The controller allows IPMI communication even while the power of the hosts and I/O devices are turned off. When all of the following controller are not mounted can also perform power supply interlocking using the remote power management function for SPARC M12 and SPARC M10.

■

Device conditions

- Wake on LAN is supported. Power-on is performed with Wake on LAN.

- IPMI communication can be performed. After power-on using Wake on LAN, IPMI communication through the LAN is used for performing power-off and obtaining the power state.

Note -

A host node with the Wake on LAN setting cannot be the master node.

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

conditions are satisfied, those devices on which such a

･

March 20196

Note -

Wake on LAN cannot be set for SPARC M12 and SPARC M10. Therefore, Wake on

LAN cannot be used to power on SPARC M12 and SPARC M10.

Note -

The Wake on LAN setting varies depending on the node. See the respective node

manuals.

Interlocking at the failure recovery time

If a node in a remote power management group cannot communicate when recovered from a failure or other problem, operation is as follows.

■

For an I/O node failure If the power to the remote power management group is on, the master host node issues a power-on instruction.

■

For a host node failure Even if the power of a remote power management group is on, the master host node does not issue a power-on instruction.

Chapter 1　Overview of the Remote Power Management Function of SPARC M12 and SPARC M10 7

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 20198

Chapter 2

Basic Flow for Configuring Remote Power Management

This section describes how to configure the remote power management function and how to use commands.

■

Before Configuring Remote Power Management

■

Steps for Configuring Remote Power Management

2.1 Before Configuring Remote Power Management

Before configuring remote power management, you need to connect the LAN cables, and make the network settings for the XSCF-LAN and the I/O devices for which remote power management is to be employed.

2.2 Steps for Configuring Remote Power Management

This section describes the steps for configuring remote power management. Configure the remote power management function by combining these steps. For an explanation of the actual configuration process for specific cases, see "Chapter 3

Examples of Remote Power Management Configuration."

2.2.1 Creating a Management File

A management file for configuring remote power management is created in CSV format for each remote power management group. You can create a management file

at a

storage location accessible by a URL with http, https, ftp, or file scheme.

The management file script format is as follows.

1,1,0x01,8a041209b35947899e7bfa5d578dbd3f,0x01,0x00,default,,10.24.0.0,0x10, xx:xx:xx:xx:xx:xx,,,,,,,,,,"4,5,6,7,8,9,10,11,12" 1,2,0x00,8a041209b35947899e7bfa5d578dbd40,0x03,0x00,default,,10.24.0.0,0x10, xx:xx:xx:xx:xx:xx,,,,,,,,,, 1,3,0x10,8a041209b35947899e7bfa5d578dbd41,0x03,0x00,default,,10.24.0.0,0x10, xx:xx:xx:xx:xx:xx,,,,,,,,,, (Omitted) 1,128,0x20,8a041209b35947899e7bfa5d578dbd42,0x03,0x00,default,,10.24.0.0,0x10, xx:xx:xx:xx:xx:xx,,,,,,,,,,

GroupID, NodeID, NodeType, NodeIdentName, Linkage, Operation, User, Password, IP0-0, Slave0-0, MAC0-0, IP0-1, Slave0-1, MAC0-1, IP1-0, Slave1-0, MAC1-0, IP1-1, Slave1-1, MAC1-1, and SubNode are specified on each line in the order shown.

The following table describes the setting items in detail.

Table 2-1

Item Description

GroupID Group ID of a remote power management group

NodeID Node ID of an interlocking device for power supply

NodeType Node type of an interlocking device for power supply

NodeIdentName Identifier of an interlocking device for power supply

Linkage Value (hexadecimal) representing power-on interlocking

Operation Value representing the power-on method

User IPMI user name

Setting Items of a Management File

Specify an integer value (decimal) from 1 to 32. All group IDs in one management file must be the same.

Specify an integer value (decimal) from 1 to 128. Each node ID in one management

Specify any of the following values: 0x00: Host node, 0x01: Mater host node, 0x10: I/O node 0x20: Remote power distribution unit

Specify the system GUID or a unique arbitrary character string. For the the example. The value is handled as a hexadecimal number in a case-insensitive fashion. For the arbitrary character string, specify a hexadecimal number with up

to 32

Specify any of the following values: 0x00: Disable, 0x03: Enable (On + Off)

Specify either of the following values: 0x00: IPMI, 0x01: WakeOnLAN

Specify nothing, and leave this field blank. If the field is not blank, the operation cannot be guaranteed.

file must be unique.

system GUID, specify a string of 32 consecutive digits as shown in

digits.

0x01: Enable (On), 0x02: Enable (Off),

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 201910

Table 2-1

Item Description

Password IPMI password

IPAddress (IP0-0/IP0-1/IP10/IP1-1)

SlaveAddress (Slave0-0/ Slave0-1/Slave10/Slave1-1)

MAC Address (MAC0-0/ MAC0-1/MAC10/MAC1-1)

SubNodeID Character string representing the ID of the controlled subnode

Setting Items of a Management File (continued)

Specify nothing, and leave this field blank.

IP address of the IPMI port of a controller Specify an IPv4 address value with a character string.

Value (hexadecimal) representing the IPMI slave address of a controller Specify "0x20".

MAC address of the IPMI port of a controller Specify

a MAC address value with a character string. Example: b0:99:28:98:18:2e A value must be set even though host nodes do not support power-on via Wake on LAN. In this case, a dummy value like the following may be used: Example: 00:00:00:00:00:00

The field is Delimit the target subnode IDs (in decimal) with a comma (,), and enclose all of them in double quotation marks ("). A blank field indicates control of the whole node.

a value from 0 to 31 or is left blank.

2.2.2 Enabling/Disabling the IPMI Service Used for the Remote Power Management Function

When the remote power management function is to be used, the IPMI service must

enabled. The IPMI service can be used only by the remote power management function. Use the setpacketfilters of the XSCF firmware to enable/disable the IPMI service.

XSCF>

To enable the IPMI service, specify the -c ipmi_port enable option. service, specify the -c ipmi_port disable option. The default value is disable.

Note -

For XCP 2280 or earlier, the IPMI service has been enabled as a fixed setting and cannot be disabled. The settings for the IPMI service are as follows when the firmware is updated from XCP 2280 or

earlier to XCP 2290 or later.

- When the remote power management function is used: Enable

- When the remote power management function is unused: Disable

setpacketfilters -c ipmi_port {enable|disable}

To disable the

The setting for enabling/disabling the IPMI service is supported by XCP 2290 or later.

Chapter 2　Basic Flow for Configuring Remote Power Management 11

2.2.3 Checking the Remote Power Management Settings

To check the contents of the remote power management settings, use the showremotepwrmgmt command of the XSCF firmware.

XSCF>

To check all the remote power management settings, specify -a. To indicate a remote power management group, specify -G groupid. To indicate a node in a remote power management group, specify -N gnodeid.

showremotepwrmgmt [-a|-G

groupid

[-N

gnodeid

]]

2.2.4 Initializing the Remote Power Management Settings

To initialize the contents of the remote power management settings, use the clearremotepwrmgmt command of the XSCF firmware.

]

2.2.5

XSCF>

To initialize the settings of all the remote power management groups, specify -a. To indicate a remote power management group, specify a group ID with the -G option.

If -a

clearremotepwrmgmt

and -G options

are omitted, then the -a option is used by default.

[-a|

-G

groupid

Enabling/Disabling the Remote Power Management

Function

To enable/disable the remote power management function, use the setremotepwrmgmt

command of the XSCF firmware.

XSCF>

You can enable or disable the remote power management function. To enable the remote power management function, specify the -c enable option. To disable, specify the -c disable option.

setremotepwrmgmt -c enable|disable

2.2.6 Setting a Remote Power Management Group

To configure a remote power management group, use the setremotepwrmgmt command of the XSCF firmware.

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 201912

XSCF>

You can specify -c config if you configure a remote power management group. For configuration_file, specify the management file used for the settings.

setremotepwrmgmt -c config

configuration_file

2.2.7 Acquiring the setting information on a remote power management group

To acquire the setting information on a remote power management group, use the getremotepwrmgmt command of the XSCF firmware.

XSCF>

For groupid, you can specify the ID of a remote power management group whose setting information is obtained. For configuration_file, specify the name of the management file for saving the acquired setting

getremotepwrmgmt -G

groupid configuration_file

information.

Chapter 2　Basic Flow for Configuring Remote Power Management 13

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 201914

Chapter 3

Examples of Remote Power Management Configuration

This section describes how to configure the remote power management in the following cases.

■

Configuring the Remote Power Management for the First Time

■

Adding or Removing a Node in an Existing Remote Power Management Group

■

Maintaining an I/O Node

3.1 Configuring the Remote Power Management for the First Time

The following shows how to configure the remote power management for the first time.

Note -

If the existing settings for the remote power management are valid, initialize the

settings.

To create a management file, collect the necessary information on the host nodes, the

and MAC addresses of I/O nodes, etc. in advance (see Table 3-1).

Figure 3-1

Flow of Configuring the Remote Power Management for the First Time

Create management file

Enable the IPMI service used by the remote power

management function

Set a remote power management group

Enable the remote power management function

Note -

The setting for enabling/disabling the IPMI service is supported by XCP 2290 or later.

In the following sections, how to configure the remote power management is described by using the system configurations below as examples.

■

System That is Configured with a Host Node and an I/O Node

■

System That is Configured with a Host Node and a Remote Power Distribution Unit

■

System That is Configured with Multiple Host Nodes and a Remote Power Distribution Unit

■

System That is Configured with Host Nodes, in Which Physical Partitions (PPARs) are Specified as Subnodes, and a Remote Power Distribution Unit

■

System in Which Multiple Remote Power Management Groups are Set

3.1.1 System That is Configured with a Host Node and I/O Node

This section describes how to configure the remote power management by using a system that is configured with one SPARC M10-1 as a host node and one ETERNUS DX80 S2 as an I/O node as an example.

Collect necessary information for a management file and create the file.

1. Collect the IP management will be configured. Based on the collected information, create a management file in CSV format for each remote power management group. The line feed code is LF or CR+LF.

ETERNUS DX80 S2 supports multiple controllers. The system can be

setting a different or same IP address per controller. We recommend setting the same IP address. There are restrictions when a different IP address is set per controller. (See "

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

address and MAC address of the device where the remote power

operated

Restrictions when a different IP address is set per controller

March 201916

･

.")

To operate the system with the same IP address set for multiple controllers, set the same IP address to IP0-0 and IP1-0 or IP0-1 and IP1-1. For details on how to check the ETERNUS controller configuration and IP addresses, see the ETERNUS manuals.

However, in either configuration, IP0-1 cannot be set Similarly, IP1-1 cannot be set without setting IP1-0. Select IP0-0/IP0-1 or IP1-0/IP1-1 based on the LAN port of the SPARC M10 system to be connected

and the type of controller used in the ETERNUS. For example, when connecting

LAN#0 of the XSCF, set the LAN of CM#0

IP1-0.

without setting IP0-0.

IP0-0 and the LAN of CM#1 to

Restrictions when a different IP address is set per controller

"IO Node power resumed" may be registered in the error log when an error occurs in the network and CM#0 cannot respond.

Furthermore, if the network is unstable, the "IO Node power resumed"

registered repeatedly.

error will

The "IO Node power resumed" error usually indicates that an I/O node was powered on again since being powered off. However, if a different IP address is set per controller, the "IO Node power resumed" error may be registered even though no I/O node has been

powered off. This issue is caused by the network.

- Configure the settings as follows when using only ETERNUS DX80 CM#0.

Figure 3-2

System Using Only ETERNUS DX80 CM#0

Remote power management group

SPARC M10-1

XSCF

LAN#0

IP: 10.24.101.1 MAC: b0:99:28:98:18:2e

Table 3-1

Item Setting Value Remarks

GroupID 1

NodeID 1

NodeType 0x01 Master host node

Setting Values of the Management File (SPARC M10-1)

LAN#1

Switching hub

MNT

CM#1

ETERNUS

DX80 S2

CM#0

MNT

IP:10.24.101.2 MAC:00:ff:75:b8:14:bd

CM: Controller module

Chapter 3　Examples of Remote Power Management Configuration 17

Table 3-1

Item Setting Value Remarks

NodeIdentName

Setting Values of the Management File (SPARC M10-1) (continued)

0123456789abcdef0000000000000001

Unique ID that consists of a hexadecimal number with 32 digits, such as System GUID

Linkage 0x01 Interlocking power-on actions

Operation 0x00 IPMI

User Blank

Password Blank

IP0-0 10.24.101.1

Slave0-0 0x20 Fixed value

MAC0-0 b0:99:28:98:18:2e

IP0-1 Blank

Slave0-1 Blank

MAC0-1 Blank

IP1-0 Blank

Slave1-0 Blank

MAC1-0 Blank

IP1-1 Blank

Slave1-1 Blank

MAC1-1 Blank

SubNode Blank

Table 3-2

Item Setting Value Remarks

Setting Values of the Management File (ETERNUS DX80 S2)

GroupID 1

NodeID 2

NodeType 0x10 I/O node

NodeIdentName

0123456789abcdef0000000000000002

Unique ID that consists of a hexadecimal number with 32 digits, such as System GUID

Linkage 0x03 Interlocking power-on and power-off actions

Operation 0x01 Wake On LAN

User Blank

Password Blank

IP0-0 10.24.101.2

Slave0-0 0x20 Fixed value

MAC0-0 00:ff:75:b8:14:bd

IP0-1 Blank

Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide

･

March 201918

Table 3-2

Item Setting Value Remarks

Setting Values of the Management File (ETERNUS DX80 S2) (continued)

Slave0-1 Blank

MAC0-1 Blank

IP1-0 Blank

Slave1-0 Blank

MAC1-0 Blank

IP1-1 Blank

Slave1-1 Blank

MAC1-1 Blank

SubNode Blank

The management file is created as follows.

1,1,0x01,0123456789abcdef0000000000000001,0x01,0x00,,,10.24.101.1, 0x20,b0:99:28:98:18:2e,,,,,,,,,, 1,2,0x10,0123456789abcdef0000000000000002,0x03,0x01,,,10.24.101.2, 0x20,00:ff:75:b8:14:bd,,,,,,,,,,

Chapter 3　Examples of Remote Power Management Configuration 19

+ 65 hidden pages

Fujitsu M12, M10 User Manual

Contents

Preface

Audience

Related Documentation

Notes on Safety

Text Conventions

Command Syntax in the Text

Syntax of the Command-Line Interface (CLI)

Document Feedback

About the Remote Power Management Function for SPARC M12 and SPARC M10

2.1 Before Configuring Remote Power Management

2.2 Steps for Configuring Remote Power Management

2.2.1 Creating a Management File

2.2.2 Enabling/Disabling the IPMI Service Used for the Remote Power Management Function

2.2.3 Checking the Remote Power Management Settings

2.2.4 Initializing the Remote Power Management Settings

2.2.6 Setting a Remote Power Management Group

2.2.7 Acquiring the setting information on a remote power management group

3.1 Configuring the Remote Power Management for the First Time

System That is Configured with a Host Node and an I/O Node