CSM Cluster-Wide Configuration Parameters

Modify any parameters and click on Change.  The text in the Value that is in parentheses is just description and can be removed when editing the value.

Attribute Value Description
AddUnrecognizedNodes Specifies if the CSM management server should accept unexpected requests from systems, to manage them and allow them to join the CSM cluster.  It is only necessary to set this to 1 if for some reason you need to initiate a join from the node (using the mgmtsvr command directly) instead of from the management server (using installnode or updatenode).
ClusterSNum Sets the cluster serial number to this string. This value is used for service and is unrelated to the serial numbers of any of the hardware.
ClusterTM Sets the cluster type and model to this string. This value is used for service, and should be in the form ####-###.
DeviceStatusFrequency Specifies the number of seconds between heartbeat messages sent to a non-node device.
DeviceStatusSensitivity Specifies the number of missed heartbeat messages sent to a non-node device to declare that the device is unreachable.
ExpDate $values{ExpDate} The expiration date for the current try-and-buy license key.  This value will be blank if a full license has been installed.  This attribute cannot be set. Use the csmconfig –L command to install a full license key.
HAMode $values{HAMode} This attribute is used by the optional CSM High Availability Management Server feature and should not be modified.
HeartbeatFrequency Number of seconds between heartbeat messages sent to a node.  The default is 12 seconds.  Along with the default of 8 for HeartbeatSensitivity, this means that it will be at least 96 seconds after a node goes down before the CSM node Status attribute reflects that fact.  The reason the default is so long is to prevent false downs caused by network traffic or node load.  If you want the Status attribute to be more responsive, lower either of these values.  Lowering HeartbeatFrequency will slightly increase network traffic.
HeartbeatSensitivity Number of missed heartbeat messages sent to a node before that node is declared unreachable.  The default is 8 times.  Lowering this value will make the node Status attribute more responsive, but runs the risk of an occasional false down.
MaxNumNodesInDomain $values{MaxNumNodesInDomain} Specifies the maximum number of nodes allowed in this CSM cluster. This could be affected by the license key that is installed using the csmconfig –L command, but currently all licenses are unlimited.
PowerStatusMode Sets the mode the HWCTRLRM uses to retrieve and maintain the PowerStatus attribute in the ManagedNode table for all of the nodes. Valid values are:
  • mixed - either poll or use events depending on the best method for each hardware control point (HCP) type.
  • polling - periodically query the power status of each node.  Since each query is logged in the RSA/MM log, this can cause the log to fill up eventually.  The frequency of polling is an attribute of the IBM.HwCtrlPoint resource class.  It can be display using lsrsrc -t IBM.HwCtrlPoint .  It can be changed for all of the HCPs of a particular type using chrsrc -s "PowerMethod='xseries' " IBM.HwCtrlPoint PollingInterval=400 , although this value will not be remembered across restarts of the HWCTRLRM.
  • events - use only events to have the HWCTRLRM notified when the power status of a node changes.  Currently, the events from all types of HCPs are not completely reliable.
  • none - do not maintain the PowerStatus attribute.  The rpower -n nodes query will still return the correct values.
RegSyncDelay Delay in seconds between the time the cluster and node data is updated in memory and when it is written onto the disk.  Increase this value to improve the performance of definenode, chnode, rmnode, and nodegrp in large clusters.
RemoteCopyCmd Specifies the remote copy command that the dcp command will use when copying files. The default is /usr/bin/scp.
RemoteShell Specifies the path of the remote shell command that CSM and dsh should use to run commands on the nodes. The default is /usr/bin/ssh.
SetupKRB5 Specifies automatic security setup instructions for Kerberos Remote Command Authorization. The default value is 0 (no setup). Values are from 0 to 15 as follows:
  • 0: None.
  • 1: Set up a Kerberos Version 5 server. Not valid on Linux.
  • 2: Set up a Kerberos Version 5 client on all Managed nodes.
  • 4: Generate the CSM Kerberos Version 5 principal and keytab, and update the root user’s .k5login file on all Managed nodes with the CSM principal. This value also directs CSM scripts to obtain a Kerberos ticket-granting ticket for the CSM principal before running remote commands. Choose a value of 4 or greater to enable Kerberos Version 5 remote commands. Although automatic setup of Kerberos Version 5 is not supported on SUSE LINUX Enterprise Server, if Kerberos is set up by the administrator CSM commands will run with Kerberos Remote Commands when 4 is specified.
  • 8: Generate a host Kerberos Version 5 principal and keytab for each Managed node, and automatically update the krb5.keytab file on the node.
To combine any of the above specifications, simply add the SetupKRB5 set up values together. For example, to set up Kerberos Version 5 clients and generate the CSM Kerberos Version 5 principal and keytab, then use SetupKRB5=6 (2 + 4). For complete Kerberos setup, use SetupKRB5=15. For complete Kerberos setup on a Red Hat™ Linux management server, use SetupKRB5=14.
SetupRemoteShell Indicates whether CSM should try to automatically set up security for the remote shell specified in the RemoteShell cluster attribute. Currently this is only supported for /usr/bin/ssh and /usr/bin/rsh.  (In order for rsh set up to be successful, rexec must already be enabled on each of the nodes.)

Tip:  The csmconfig command that is used to display and change these values is described in CSM Command and Technical Reference.