Once CSM cluster hardware and networking is configured as required, CSM software must be installed and configured to enable remote power functions. The CSM installms command installs the required csm.server package, including the /opt/csm/bin/rpower remote power command, on the management server. For detailed CSM installation instructions, see the IBM CSM for Linux: Software Planning and Installation Guide. For detailed command usage information, see the installms, definenode, and rpower man pages or the IBM CSM for Linux: Administration Guide.
The CSM management server communicates with hardware control points through the IBM Distributed Management Server (DMS) resource manager (IBM.DMSRM). The DMS resource manager supports IBM hardware control libraries and customized programs or scripts. IBM hardware control libraries manage the IBM RSA hardware control point. Customized programs or scripts are required to manage other hardware control points. Each library (or script) is responsible for communicating to the hardware control point and making the request for the hardware action. The library or script returns the action request results to the DMS resource manager, which returns the information to the user.
To configure remote power, the default hardware control point user IDs and passwords must be changed using the utility disks and documentation provided with the hardware. For MPs and MPAs the default user ID shipped with the system is "USERID" and the default password is "PASSW0RD" (P-A-S-S-W-zero-R-D). When a user runs the rpower command, the user ID and password information is automatically retrieved and decrypted. The rpower command is run from the management server only to restrict remote power to users with root access.
The MP and MPA user IDs and passwords stored for nodes on the management server must match the nodes' physical user IDs and passwords in the hardware. The systemid command must be run once for each MP and MPA to encrypt password information on the management server. Password files generated by the systemid command have the following properties:
Directory location: /etc/opt/csm/system_config File permissions (owner/group and permissions): root/root read-only. For example, -r------- 1 root root 20 May 3 12:31 9.111.111.11 Naming convention: IP Address of host (if resolvable). For example, 9.111.111.11; otherwise, the node ID specified (for example, node01).
The following examples show how to create system IDs on the management server (all examples will prompt for a valid password):
systemid clsn05.pok.ibm.com USERID
systemid clsn07 USERID
systemid
Output should be similar to:
9.001.001.01 USERID clsn06.pok.ibm.com USERID
The remote power PowerMethod library type provided with CSM for
Linux is netfinity. The HWControlNodeID attribute
must contain the value shown in Table 2 based on the PowerMethod library type used:
Table 2. Hardware control attribute values
HWControlPoint attribute | HWControlNodeID attribute | PowerMethod library |
---|---|---|
host name of the IBM xSeries RSA PCI MPA | text ID associated with MP or MPA | netfinity |
The following example shows how to change a management processor (MP) hardware text ID, user ID, and password using a Web browser session. For detailed information on the Cluster 1300 see the IBM Linux clusters hardware Web site listed in Related information. To change the text ID, user ID, and password of an MP in a cluster node:
User Name: USERID Password: PASSW0RD (P-A-S-S-W-zero-R-D)
User Name: USERID Password: PASSW0RD (P-A-S-S-W-zero-R-D)
To change log in information for an IBM RSA management processor adapter (MPA), perform the above steps but skip steps 3 and 4.
CSM remote power functions require attributes to be defined in the CSM database for the specific hardware control points used in the cluster. When new nodes are defined in a cluster using the definenode command, the required PowerMethod, HWControlPoint, and HWControlNodeID attributes are created in the CSM database. See the IBM CSM for Linux: Software Planning and Installation Guide or the man page for definenode command examples.
Setting a node's HWControlNodeID attribute to the short host name of the node can simplify the node definition process. The following definenode command example defines the node short host names as the HWControlNodeID attribute values. If the HWControlNodeID attribute values were not set to the node short host names, then the nodedef file would be used to specify each attribute value. If a node's HWControlNodeID is the short host name, then the following command can be run once to define all nodes attached to the hardware control point:
definenode -n clsn01.pok.ibm.com -c 20 -H mgtn03.pok.ibm.com:10,- mgtn04.pok.ibm.com:10 \ -C mgtn02.pok.ibm.com:1:0:16 mgtn05.pok.ibm.com:2:0:16 PowerMethod=netfinity ConsoleMethod=esp.
All HWControlNodeID node attribute values attached to a hardware control point must be unique. For xSeries 330 and 342 nodes, the HWControlNodeID value must match the text ID set in the hardware. If HWControlNodeID values are changed to the short host names of the nodes, then the systemid command must be subsequently run to correctly set the new user ID and password information in the CSM database.
If a hardware control point other than those listed in Table 2 is used, then additional software and configuration is required to enable remote power functions. Each hardware control point must have an associated Perl or shell command for communicating with the management server. The PowerMethod attribute for a node must be set accordingly by the definenode command when the node is defined. A corresponding PowerMethod_power command must also be provided. For example, if the PowerMethod attribute on a node is set to vendor1, then rpower will attempt to access a vendor1_power command to carry out remote power requests. Each node's HWControlPoint attribute must be set to the value expected by the PowerMethod_power command using the definenode command. For command usage examples see the definenode man page and the IBM CSM for Linux: Software Planning and Installation Guide.
To use remote power with other hardware control points, the following steps are required. In this example, vendor1 is used as the PowerMethod node attribute value:
To ensure the cluster is configured correctly, all CSM remote power hardware control functions should be tested before using them in a production environment. The rpower command should be run with the query, power on, power off, reboot, resetsp_host, and resetsp_hcp options to verify that all nodes are configured correctly and are responding accordingly. See the rpower man page or the IBM CSM for Linux: Administration Guide for examples.
Node power status is determined by polling. The PowerStatus attribute value is the status returned from polling MPs and MPAs: on, off, or unknown. The polling interval is set to 300 seconds by default, but can be changed if required using the chrsrc command.
The following examples provide some methods for testing remote power configuration:
lsnode -l
Output for each node in the cluster is similar to:
ManagementServer = csmlinux.pok.ibm.com Mode = PreManaged Name = clsn02.pok.ibm.com NodeNameList = {csmlinux.pok.ibm.com} PowerMethod = esp PowerStatus = on Status = on UniversalId = 0 UpdatenodeFailed = 0 ------------------- Hostname = clsn03.pok.ibm.com AllowManageRequest = 0 (no) CSMVersion = ConfigChanged = 0 (no) ConsoleMethod = esp ConsolePortNum = ConsoleServerName = clsn03.ppd.pok.ibm.com ConsoleServerNumber = HWControlNodeId = clsn03_NODEID HWControlPoint = clsn03.ppd.pok.ibm.com HWModel = HWSerialNum = HWType = InstallAdapterDuplex = InstallAdapterMacaddr = 00:00:00:00:00:00 InstallAdapterSpeed = InstallAdapterType = InstallCSMVersion = 1.2.0 InstallDisk = InstallDiskType = InstallDistributionName = RedHat InstallDistributionVersion = 7.2 InstallKernelVersion = InstallMethod = kickstart InstallOSName = Linux InstallPkgArchitecture = i386 LParID = LastCFMUpdateTime = ManagementServer = csmlinux.pok.ibm.com Mode = PreManaged Name = clsn03.pok.ibm.com NodeNameList = {csmlinux.pok.ibm.com} PowerMethod = esp PowerStatus = on Status = on UniversalId = 0 UpdatenodeFailed = 0
rpower -n clsn01,clsn07,clsn13,clsn20 on
chrsrc -s 'Name=="clsn07.pok.ibm.com"' IBM.HwCtrlPoint PollingInterval=30
The following examples show problems and solutions for specific instances of using remote power:
Management processor adapters (MPAs) and management processors (MPs) can be controlled through a telnet session or Web browser. To access an MPA or MP using a telnet or Web connection, the http server must be installed and running, and the telnet session or Web browser must be targeted to the host name or IP address of the hardware control point. The physical login process for telnet and Web connections is the same as that shown in Figure 1. User IDs and passwords are required, and appropriate security measures should be implemented to restrict remote power control to users on the management VLAN, as described in CSM hardware and network requirements. Telnet and Web access provide alternative interfaces for tasks such as debugging.
Log files are generated by specifying the -v flag on hardware control commands such as rpower. For example, the command:
rpower -v
could produce log files similar to the following examples:
An example trace file:
-------- Wed May 15 06:43:36 EDT 2002 06:43:36 CLASSPATH=/opt/csm/codebase:/opt/csm/codebase/asmlibrary.jar:/opt/csm/codebase/sniacimom.jar: \ /opt/csm/codebase/xerces.jar 06:43:36 LIBPATH=/opt/csm/lib 06:43:36 hardware control point -> clsn01.pok.ibm.com (9.111.111.111) 06:43:36 using default userid/password 06:43:36 connect(9.111.111.111,USERID,********) 06:43:36 >>>>> connect : 274 ms 06:43:36 connect() returns 0 06:43:36 invoke_method (query,clsn01.pok.ibm.com,clsn09) 06:43:36 using default userid/password 06:43:36 searching for clsn09 06:43:36 8 nodes found: 06:43:36 clsn01 06:43:36 clsn02 06:43:36 clsn03 06:43:36 clsn04 06:43:36 clsn05 06:43:36 cl2n06-> found on 485 bus 06:43:37 >>>>> connect485 : 1030 ms 06:43:37 send_command (query,clsn01.pok.ibm.com,clsn09) 06:43:37 c5n64 state = 4 06:43:38 >>>>> query : 474 ms 06:43:38 query() returns 0
An example error file:
[9.111.111.11]: com.ibm.sysmgt.lib.exception.DestinationInvalidException at com.ibm.sysmgt.lib.comm.IP.DCSocketBase.openDestinationHelper(DCSocketBase.java:178) at com.ibm.sysmgt.lib.comm.IP.DCSocketBase.logon(DCSocketBase.java:335) at com.ibm.csm.hcnetfinity.Netfinity.connect(Netfinity.java:1443)
Command usage with output to stdout:
rpower -v -n clsn05.pok.ibm.com query clsn05.pok.ibm.com on resource class: IBM.NodeHwCtrl response for: query mc_errnum = 0x00000000 mc_ffdc_id = mc_error_msg = SD value is : Element 0: type=8, value=clsn05.pok.ibm.com Element 1: type=3, value=0 Element 2: type=8, value=on