HP XC System Software Installation Guide Version 3.2

3. Copy the MCS template file into a file called mcs.ini:
# cp mcs_template.ini mcs.ini
4. Use the text editor of your choice to populate the mcs.ini file with site-specific MCS device
information. A sample of the mcs.ini file is shown in Example 3-3 (page 84).
The following list describes the parameters in the mcs.ini file:
mcs_units Specifies each MCS device name separated by a comma.
mcs_server_units Specifies the name of each MCS device that controls one or more
service nodes, separated by a comma
name Specifies the name of the MCS device.
ipaddr Specifies the IP address of the MCS device.
location Specifies the cabinet that contains the nodes that are under control
of the MCS device
nodes Defines the range of nodes under control of the MCS device. The
node range is specified in the format node_prefix[n-n].
status Lists the status of the MCS device. Valid values are offline or
online.
Nagios monitors only the MCS devices that are in the online
state. For more information about MCS device status, see
manage_mcs_status(8).
Before you change the device status to online, make sure the
MCS devices are online and operating correctly.
5. Save the changes to the file and exit the text editor.
Example 3-3 Sample mcs.ini File
# mcs.ini file for cluster penguin
[global]
mcs_units=mcs1,mcs2,mcs3,mcs4,mcs5
mcs_server_units=mcs5
[mcs1]
name=mcs1
ipaddr=172.23.0.1
location=Cab CBB1
nodes=n[1-36]
status=offline
[mcs2]
name=mcs2
ipaddr=172.23.0.2
location=Cab CBB2
nodes=n[37-72]
status=offline
[mcs3]
name=mcs3
ipaddr=172.23.0.3
location=Cab CBB3
nodes=n[73-108]
status=offline
[mcs4]
name=mcs4
ipaddr=172.23.0.4
location=Cab CBB4
nodes=n[109-144]
84 Configuring and Imaging the System