3.1.3 System That is Configured with Multiple Host Nodes and a Remote Power Distribution Unit
3.1.3 System That is Configured with Multiple Host Nodes and a Remote Power Distribution Unit
This section describes how to configure the remote power management by using a system that is configured with four SPARC M10-4 systems and a remote power distribution unit.
The basic process is the same as written in "3.1.1 System That is Configured with a Host Node and an I/O Node."
The basic process is the same as written in "3.1.1 System That is Configured with a Host Node and an I/O Node."
- Collect necessary information for a management file and create the file.
Collect the IP address and MAC address of the device where the remote power 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.
- When connecting multiple host nodes, up to two master host nodes can be set. This helps to increase redundancy.
- If "Off" is specified to the Linkage setting between a host node and master node, the power-off actions are not interlocked.
To enable the interlocking between the power-on actions of the host nodes, set "0x01: Enable (On)" to the Linkage setting. The operation does not change if "0x03: Enable (On + Off)" is set.
To disable the interlocking between power on actions in the SPARC M10 systems, set "0x00: Disable" to the Linkage setting. The operation does not change if "0x02: Enable (Off)" is set.
- In the following, how to configure the remote power management is described based on the configuration below.- Use only XSCF-LAN#0 of SPARC M10-4.- Set the first and second SPARC M10-4 systems as master host nodes.- Use one I/O device by connecting it to a remote power distribution unit.
The I/O device can be shared by the connected SPARC M10-4 systems.- Interlock between power-on and power-off actions (only interlocking between power-on actions can be enabled for the host nodes).
|
Item | Setting Value | Remarks |
---|---|---|
GroupID | 1 | |
NodeID | 1 | |
NodeType | 0x01 | Master host node |
NodeIdentName | 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:38:4a | |
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 |
Item | Setting Value | Remarks |
---|---|---|
GroupID | 1 | |
NodeID | 2 | |
NodeType | 0x01 | Master host node |
NodeIdentName | 0123456789abcdef0000000000000002 | 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.2 | |
Slave0-0 | 0x20 | Fixed value |
MAC0-0 | b0:99:28:98:38:4b | |
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 |
Item | Setting Value | Remarks |
---|---|---|
GroupID | 1 | |
NodeID | 3 | |
NodeType | 0x00 | Host node |
NodeIdentName | 0123456789abcdef0000000000000003 | 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.3 | |
Slave0-0 | 0x20 | Fixed value |
MAC0-0 | b0:99:28:98:38:4c | |
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 |
Item | Setting Value | Remarks |
---|---|---|
GroupID | 1 | |
NodeID | 4 | |
NodeType | 0x00 | Host node |
NodeIdentName | 0123456789abcdef0000000000000004 | 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.4 | |
Slave0-0 | 0x20 | Fixed value |
MAC0-0 | b0:99:28:98:38:4d | |
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 |
Item | Setting Value | Remarks |
---|---|---|
GroupID | 1 | |
NodeID | 5 | |
NodeType | 0x20 | Remote power distribution unit |
NodeIdentName | 0123456789abcdef0000000000000005 | 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 | 0x00 | IPMI |
User | Blank | |
Password | Blank | |
IP0-0 | 10.24.101.5 |
|
Slave0-0 | 0x20 | Fixed value |
MAC0-0 | c0:ff:75:b8:14:c8 | |
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 |
- The management file is created as follows.
1,1,0x01,0123456789abcdef0000000000000001,0x01,0x00,,,10.24.101.1, 0x20,b0:99:28:98:38:4a,,,,,,,,,, 1,2,0x01,0123456789abcdef0000000000000002,0x01,0x00,,,10.24.101.2, 0x20,b0:99:28:98:38:4b,,,,,,,,,, 1,3,0x00,0123456789abcdef0000000000000003,0x01,0x00,,,10.24.101.3, 0x20,b0:99:28:98:38:4c,,,,,,,,,, 1,4,0x00,0123456789abcdef0000000000000004,0x01,0x00,,,10.24.101.4, 0x20,b0:99:28:98:38:4d,,,,,,,,,, 1,5,0x20,0123456789abcdef0000000000000005,0x03,0x00,,,10.24.101.5, 0x20,c0:ff:75:b8:14:c8,,,,,,,,,, |
- Enable the IPMI service that is to be used for the remote power management function.Execute it by logging into the XSCF shell of all the host nodes and master host nodes where the remote power management is configured.
XSCF> setpacketfilters -c ipmi_port enable |
- Configure a remote power management group using the created management file.a. Execute the showremotepwrmgmt command to confirm that the remote power management is not configured.Check the above by logging into the XSCF shell of all the host nodes and master host nodes where the remote power management is configured. When configuring the remote power management for the first time, it is normally assumed that the remote power management is not set.
- In the following example, the remote power management is not set.
XSCF> showremotepwrmgmt -a Remote power management group is not configured. |
- If the existing settings for the remote power management are valid, initialize the settings according to the following process.
XSCF> clearremotepwrmgmt -a All remote power management group informations are cleared.Continue? [y|n]: y |
- b. Execute the setremotepwrmgmt command to set a remote power management group.Execute this step by logging into the XSCF shell of either a host node or master host node in the remote power management group.
- Download the management file created in step 1 with the setremotepwrmgmt command of the XSCF firmware.
- Execute the following steps to download the management file of the remote power management group to a USB memory stick.1) Insert a USB memory stick into the USB port, on which "MAINTENANCE ONLY" is printed, on the back panel of the XSCF unit.The USB memory stick must be FAT32 format.The management file can be downloaded by using a USB memory stick or by specifying an http, https, or ftp server.2) Execute the setremotepwrmgmt command to set a remote power management group.If the settings of the downloaded management file are correct, enter "y" for "Continue? [y|n]:" to apply them.
XSCF> setremotepwrmgmt -c config file:///media/usb_msd/path/rpmgroup-1.conf Mounted USB device Download successful: 29184Byte at 1016.857KB/s Checking file... The following Remote Power Management Group setting will be applied: GroupID :01 NodeID NodeType NodeIdentName PowerLinkage Operation ------ ----------- -------------------------------- ---------------------- ----------- 001 Master HOST 0123456789abcdef0000000000000001 Enable(Power-On Link) IPMI 002 Master HOST 0123456789abcdef0000000000000002 Enable(Power-On Link) IPMI 003 HOST 0123456789abcdef0000000000000003 Enable(Power-On Link) IPMI 004 HOST 0123456789abcdef0000000000000004 Enable(Power-On Link) IPMI 005 PwrLinkBox 0123456789abcdef0000000000000005 Enable IPMI ------ ----------- -------------------------------- ---------------------- ----------- Continue? [y|n]: y The command completed successfully. XSCF> |
- Execute the setremotepwrmgmt command to enable the remote power management function.Execute this step for all host nodes and master host nodes where the remote power management is set.
XSCF> setremotepwrmgmt -c enable Remote power management is enabled. Continue? [y|n]: y The command completed successfully. |
- Current setting details can be checked with the showremotepwrmgmt command.
XSCF> showremotepwrmgmt [Remote Power Management Group#01 Information] Remote Power Management Status :[Enable] NodeID NodeType NodeIdentName Power PowerLinkage Operation ------ ----------- -------------------------------- ----- ---------------------- ----------- 001 Master HOST 0123456789abcdef0000000000000001 OFF Enable(Power-On Link) IPMI 002 Master HOST 0123456789abcdef0000000000000002 OFF Enable(Power-On Link) IPMI 003 HOST 0123456789abcdef0000000000000003 OFF Enable(Power-On Link) IPMI 004 HOST 0123456789abcdef0000000000000004 OFF Enable(Power-On Link) IPMI 005 PwrLinkBox 0123456789abcdef0000000000000005 OFF Enable IPMI ------ ----------- -------------------------------- ----- ---------------------- ----------- |
< Previous Page | Next Page >