Clusterworx System Administrators Guide.book - Abel Keogh

Clusterworx 3.4.2
System Administrator’s Guide
A guide to reducing the total cost of cluster ownership by
simplifying, streamlining, and automating all aspects of
cluster management.
DOC-CWX3XSA-A
03.16.07

Notice
i
Notice
This manual and the product(s) described herein are furnished under license and may be used or copied only
in accordance with the terms of such license. The content of this manual is furnished for informational use
only, is subject to change without notice, and should not be construed as a commitment or obligation by
Linux Networx, Inc. Linux Networx, Inc. assumes no responsibility or liability for any errors or inaccuracies
that may appear in this manual, but invites users to contact us with any discrepancies or for additional
clarification.
Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval
system, or transmitted, in any form or by any means, electronic, mechanical, or otherwise, without the prior
written permission of Linux Networx, Inc.
Linux Networx, the cube logo, and Clusterworx are registered trademarks of Linux Networx, Inc. LS-1 and
Icebox are trademarks of Linux Networx, Inc. Linux is a trademark of Linus Torvalds. Other company
product names and service names may be trademarks or service marks of other companies or individuals.
© 2007 Linux Networx, Inc. All rights reserved.
Linux Networx, Inc.
14944 Pony Express Road
Bluffdale, Utah 84065
USA
801.562.1010
Part number: DOC-CWX3XSA-A
Revision: 03.16.07
Clusterworx System Administrator’s Guide

Preface
Introduction
The Clusterworx System Administrator's Guide is written in modular style where
each section builds upon another to deliver progressively advanced scenarios and
configurations. Depending on your system configuration and implementation, certain sections of this guide
may be optional, but warrant your attention as the needs of your system evolve. This guide assumes that you,
the reader, have a working knowledge of Linux.
Audience
This guide's intended audience is the system administrator who will be working with the Clusterworx
software to manage and control the cluster system.
Linux Networx Documentation on the Web
This and all Linux Networx technical documentation is available via the Linux Networx support website at
http://www.linuxnetworx.com. Access to documentation is limited to Linux Networx customers only.
Related Documentation
Please refer to the following for information on related Linux Networx products:
Icebox User's Guide
Note
SUSE Linux documentation is available on http://www.novell.com/documentation/suse.html.
Feedback
Linux Networx welcomes your feedback. If you have any questions, comments, or requests concerning this
document, please e-mail us at writer@lnxi.com. Please include the document's title, part number, and revision
information.
Clusterworx System Administrator’s Guide
ii

Introduction
Annotations
iii
Annotations
This guide uses the following annotations throughout the text:
Electric Shock!
Indicates impending danger. Ignoring these messages may result in serious injury or death.
Warning!
Warns users about how to prevent equipment damage and avoid future problems.
Note
Informs users of related information and provides details to enhance or clarify user activities.
Tip
Identifies techniques or approaches that simplify a process or enhance performance.
Clusterworx System Administrator’s Guide

Customer Education
Customer Education
Training from Linux Networx provides system administrators, developers, and other IT professionals with
the education, skill, and tools needed to successfully manage Linux supercomputing cluster systems. Courses
help increase productivity and allow your technical team to train in a Linux cluster environment at our stateof-the-art
Solutions Center.
Linux Networx training helps keep you abreast of new technology, teaches you how to integrate systems into
your existing infrastructure, and can even provide you with the ability to learn the intricacies of your system
before it arrives at your site—this allows you to develop the skills necessary to maximize your technology
investment from day one.
For details regarding course availability and enrollment, please visit www.linuxnetworx.com.
Technical Support
Linux Networx support technicians are available on the phone or online to answer any questions you have
about your system. Our online support database includes thousands of articles created by certified Linux
Networx support professionals to resolve customer issues. This database is subject to regular updates and is
expanded and refined to ensure that you have access to the very latest information. From our online support
you can also find updates, download patches, or post specific questions about your system.
Support Options
Linux Networx offers three levels of support:
Priority Support Supplies basic support needs including unlimited online support and upgrades.
Priority-plus Support Upgraded basic support including regular system checks and reviews.
Premium Support The most comprehensive support package. Includes training, qualified kernel updates,
and round-the-clock phone support.
To learn more about our support options, or visit www.linuxnetworx.com.
To upgrade or add support, contact Linux Networx at www.linuxnetworx.com.
Contact Information
Linux Networx Technical Support:
1-800-459-7138
(6:00 a.m.—6:00 p.m. MST)
www.linuxnetworx.com
Clusterworx System Administrator’s Guide
iv

Technical Support
Contact Information
v
Clusterworx System Administrator’s Guide

Table of Contents
Notice .............................................................................................................................. i
Preface ..........................................................................................................................ii
Introduction ....................................................................................................................ii
Audience .....................................................................................................................ii
Linux Networx Documentation on the Web ..........................................................ii
Related Documentation.............................................................................................ii
Feedback .....................................................................................................................ii
Annotations................................................................................................................iii
Customer Education .................................................................................................... iv
Technical Support ........................................................................................................ iv
Support Options ........................................................................................................ iv
Contact Information ................................................................................................. iv
Chapter 1
Getting Started ............................................................................................................ 1
System Requirements .................................................................................................1
Hardware Requirements ........................................................................................... 1
Operating System Requirements ............................................................................. 2
Software Requirements ............................................................................................. 2
Upgrades .......................................................................................................................3
Installing Clusterworx ..................................................................................................4
Setting Up a Clusterworx Master Host.................................................................... 4
Migration Utility....................................................................................................... 13
Clusterworx Services ............................................................................................... 14
Chapter 2
Licensing .................................................................................................................... 15
Overview ..................................................................................................................... 15
License Installation .................................................................................................... 15
License Authentication ............................................................................................. 17
License Administration ............................................................................................. 17
Clusterworx System Administrator’s Guide
vi

Table of Contents
vii
License Viewer..........................................................................................................17
Chapter 3
Introduction to Clusterworx ...................................................................................... 19
Overview ..................................................................................................................... 19
Comprehensive System Monitoring.......................................................................19
Version Controlled Image Management................................................................19
Fast Multicast Provisioning.....................................................................................20
Clusterworx Interface ................................................................................................ 21
Customizing the Interface .......................................................................................22
Chapter 4
Host Administration .................................................................................................. 23
Clustered Environments ........................................................................................... 23
Host Configuration .................................................................................................... 23
Hosts ........................................................................................................................... 25
Add a Host .................................................................................................................25
Edit a Host .................................................................................................................28
Disable a Host ...........................................................................................................30
Delete a Host .............................................................................................................31
Partitions .................................................................................................................... 32
Add a Partition..........................................................................................................32
Edit a Partition ..........................................................................................................34
Disable a Partition ....................................................................................................35
Delete a Partition ......................................................................................................35
Regions ....................................................................................................................... 36
Add a Region .............................................................................................................36
Edit a Region .............................................................................................................38
Delete a Region .........................................................................................................39
Instrumentation ......................................................................................................... 40
States ..........................................................................................................................40
Clusterworx Message Log........................................................................................41
Menu Controls ..........................................................................................................41
General Tab ...............................................................................................................42
CPU Tab.....................................................................................................................45
Memory Tab ..............................................................................................................45
Disk Tab .....................................................................................................................46
Network Tab..............................................................................................................46
Kernel Tab .................................................................................................................47
Load Tab ....................................................................................................................47
Temperature Tab ......................................................................................................48
Chapter 5
User Administration ................................................................................................... 49
Working Environment ................................................................................................ 49
Default User Administration Settings .................................................................... 51
User Configuration...................................................................................................51
Clusterworx System Administrator’s Guide

Roles ........................................................................................................................... 52
Add a Role................................................................................................................. 52
Edit a Role ................................................................................................................. 54
Delete a Role ............................................................................................................. 55
Privileges ................................................................................................................... 56
Groups .........................................................................................................................57
Add a Group.............................................................................................................. 57
Edit a Group.............................................................................................................. 60
Delete a Group.......................................................................................................... 61
Users ........................................................................................................................... 62
Add a User................................................................................................................. 62
Edit a User Account ................................................................................................. 64
Disable a User Account ........................................................................................... 65
Delete a User Account ............................................................................................. 66
Chapter 6
Power Control ............................................................................................................ 67
Icebox Administration ............................................................................................... 67
Add an Icebox........................................................................................................... 68
Power Management ................................................................................................. 77
Hosts Subtab ............................................................................................................. 77
Iceboxes Subtab........................................................................................................ 80
Chapter 7
Imaging ...................................................................................................................... 83
Overview ..................................................................................................................... 83
Payload Management ............................................................................................... 84
Linux Distributions .................................................................................................. 84
Create a Payload....................................................................................................... 85
Add a Package to an Existing Payload .................................................................. 92
Remove a Payload Package .................................................................................... 94
Payload Authentication Management................................................................... 98
Payload Local User and Group Account Management.....................................101
Payload File Configuration...................................................................................106
Edit a Payload File with the Text Editor .............................................................107
Add and Update Payload Files or Directories ....................................................108
Delete Payload Files...............................................................................................109
Delete a Payload.....................................................................................................109
Install Clusterworx into the Payload ...................................................................110
Kernel Management ................................................................................................ 112
Create a Kernel.......................................................................................................112
Edit a Kernel ...........................................................................................................117
Delete a Kernel from VCS .....................................................................................119
Image Management ................................................................................................ 120
Create an Image......................................................................................................120
Delete an Image from VCS....................................................................................123
Managing Partitions...............................................................................................124
RAID Partitions.......................................................................................................127
Table of Contents
Clusterworx System Administrator’s Guide
viii

Table of Contents
ix
Edit a Partition ....................................................................................................... 129
Delete a Partition ................................................................................................... 131
User-Defined File Systems ................................................................................... 132
Diskless Hosts ........................................................................................................ 135
RAM Disk................................................................................................................ 138
Plug-ins for the Boot Process ............................................................................... 140
Version Control System (VCS) ...............................................................................144
Version Branching................................................................................................. 144
Version Control Check-in ..................................................................................... 146
Version Control Check-out................................................................................... 147
VCS Management .................................................................................................. 148
Version Status ........................................................................................................ 149
VCS Host Compare................................................................................................ 150
Chapter 8
Provisioning ............................................................................................................. 153
Overview ...................................................................................................................153
Selecting an Image ..................................................................................................154
Advanced Provisioning Options.......................................................................... 156
Configuring DHCP................................................................................................. 158
Provisioning Channels .............................................................................................160
DistributionService.profile................................................................................... 161
Chapter 9
Runner ...................................................................................................................... 163
Overview ...................................................................................................................163
Connect to a Host ...................................................................................................164
View Host Output ....................................................................................................166
Execute Commands on Hosts ...............................................................................167
Disconnect from a Host ..........................................................................................169
Chapter 10
Instrumentation Service .......................................................................................... 171
Clusterworx Monitoring and Event Subsystem ..................................................171
Monitors ....................................................................................................................172
Custom Monitors ................................................................................................... 172
Metrics .......................................................................................................................175
Metric Selector....................................................................................................... 176
Listeners and Loggers ............................................................................................179
Listeners.................................................................................................................. 179
Loggers .................................................................................................................... 181
Chapter 11
Command-Line Interface ......................................................................................... 185
Command-Line Syntax and Conventions .............................................................185
CLI Commands ...................................................................................................... 186
Clusterworx System Administrator’s Guide

ccp .............................................................................................................................. 192
conman ..................................................................................................................... 193
cwhost ...................................................................................................................... 196
cwpower ................................................................................................................... 204
cwprovision .............................................................................................................. 206
cwuser ....................................................................................................................... 209
dbix ............................................................................................................................ 215
dbx ............................................................................................................................. 216
imgr ............................................................................................................................ 217
kmgr ........................................................................................................................... 218
Example 1................................................................................................................218
Example 2................................................................................................................218
pdcp ........................................................................................................................... 219
pdsh ........................................................................................................................... 222
pmgr .......................................................................................................................... 225
powerman ................................................................................................................. 226
vcs .............................................................................................................................. 228
xms ............................................................................................................................ 231
Glossary ....................................................................................................................233
Appendix ..................................................................................................................237
Pre-configured Metrics ............................................................................................ 237
CPU ..........................................................................................................................237
Disk ..........................................................................................................................239
Icebox ......................................................................................................................240
Image .......................................................................................................................240
Kernel ......................................................................................................................240
Load .........................................................................................................................241
LinuxBIOS...............................................................................................................241
LS-1 1950i and 1435a ............................................................................................242
LS-1 2950i................................................................................................................243
LS-1 1435a Only .....................................................................................................243
Memory ...................................................................................................................244
Network ...................................................................................................................246
OS.............................................................................................................................247
Payload ....................................................................................................................248
Index .........................................................................................................................249
Clusterworx End User License Agreement ..............................................................259
Table of Contents
Clusterworx System Administrator’s Guide
x

Table of Contents
xi
Clusterworx System Administrator’s Guide

System Requirements
Operating System Requirements
2
Operating System Requirements
Warning!
Please consult Linux Networx before upgrading your Linux distribution or kernel. Upgrading to a
distribution or kernel not approved for use on your system may render Clusterworx inoperable or
otherwise impair system functionality. Technical Support is not provided for unapproved system
configurations.
Clusterworx Hosts
This version of Clusterworx runs on the following operating systems and architectures:
SUSE LINUX ENTERPRISE SERVER 10
64-bit AMD64/EM64T hardware.
SUSE LINUX ENTERPRISE SERVER 9 (SP1-3)
32-bit x86 Intel or AMD hardware.
64-bit AMD64/EM64T hardware.
REDHAT ENTERPRISE LINUX 4 (UPDATES 1-4)
32-bit x86 Intel or AMD hardware.
64-bit AMD64/EM64T hardware.
REDHAT ENTERPRISE LINUX 3 (UPDATES 1-8)
32-bit x86 Intel or AMD hardware.
64-bit AMD64/EM64T hardware.
WINDOWS XP
32-bit x86 Intel or AMD Hardware (Clusterworx client only).
WINDOWS 2000
32-bit x86 Intel or AMD Hardware (Clusterworx client only).
Clusterworx Clients
For Linux client installations, Clusterworx uses the same platforms supported by host installations. Windows
installations use Windows 2000 or Windows XP only.
Clusterworx Kernel Support
Linux Networx recommends using the kernel that shipped with your version of Linux.
Software Requirements
Clusterworx requires the installation of the following RPM packages:
DHCP (included with your distribution)
Mkelfimage (available on the Clusterworx CD or via ftp://ftp.lnxi.com/)
If you require PXE Boot support, you must also install:
TFTP
Clusterworx System Administrator’s Guide

Upgrades
Why should I upgrade my version of Clusterworx?
Improvements to monitoring, provisioning (formerly cloning), and image management.
New host status monitors and events.
User, group, and role management.
Cluster partitions and regions for host organization.
Version-controlled image management.
Free updates for eligible customers (see list of requirements below).
How do I qualify for a free Clusterworx upgrade?
You have a current support contract and are in good financial standing with Linux Networx.
You purchased the previous version of Clusterworx.
You are willing to upgrade to a supported distribution.
Your system meets the minimum system requirements (see System Requirements on page 1).
Meet minimum network requirements (Multicast, Etherboot).
Should I update my version of Linux?
Upgrades
Software Requirements
For many companies, updating a production system may not be cost-effective. However, updated drivers and
libraries may significantly increase performance over older Linux releases.
Note
If you are running third-party software applications, contact the application manufacturers about
support for newer versions of Linux.
Clusterworx System Administrator’s Guide
3

Installing Clusterworx
Setting Up a Clusterworx Master Host
4
Installing Clusterworx
With your Linux distribution installed and your hardware and software qualified, you are ready to begin
installing Clusterworx. (See Operating System Requirements on page 2 for a list of supported distributions.)
Note
To upgrade your version of Clusterworx, see Migration Utility on page 13.
Setting Up a Clusterworx Master Host
Warning!
A Clusterworx Master Host installation requires that you install the mkelfimage package. This package is
available in RPM, SRPM, and source packages and may be obtained from your Clusterworx CD or the
Linux Networx FTP site:
ftp://ftp.lnxi.com/pub/mkelfImage
1. Generate or convert the /etc/hosts file for the servers and the compute hosts, then place this file on all
management hosts.
2. Install Clusterworx on the primary and secondary management hosts:
A. Log into Linux as the root user on the Clusterworx Master Host, then Insert the Clusterworx CD. If
the installation does not begin automatically after inserting the CD, enter run:
/install.sh from the command line.
Clusterworx System Administrator’s Guide

Installing Clusterworx
Setting Up a Clusterworx Master Host
B. Select Clusterworx Server, then enter the install directory (by default, /opt/cwx) and Master Host
name. The Master Host name (e.g., cwxhost) must be on the cluster management network and be
identified in /etc/hosts. For information on changing the name of the Master Host, see Rename the
Clusterworx Master Host on page 29.
Warning!
To prevent accidentally overwriting Clusterworx, install Clusterworx on a local file system that is not
shared with any other hosts.
C. Run /install.sh on each secondary management host (or on the Master Host
if your system uses only one management host) and install each Clusterworx component.
D. Select Server (cwxhost), install directory (/opt/cwx), and enter the name of the new host. Click
Next.
Note
If you have only one management host on your cluster, install the Clusterworx Server option. Following
installation, Clusterworx will ask you to install the Server option on the same host. Select Yes. If more
than one management host is installed on your cluster, install the Clusterworx Server option on the
Clusterworx System Administrator’s Guide
5

Installing Clusterworx
Setting Up a Clusterworx Master Host
6
primary management host. Then install Server on each additional management host. Use the primary
host name as the Clusterworx Server
Note
If the management network is something other than 192.168.0.0 following an installation or upgrade, you
will need to update it in the /opt/cwx/dhcp/dhcpd.conf.template file.
Clusterworx System Administrator’s Guide

E. Select the options to install on this host.
Tip
Installing Clusterworx
Setting Up a Clusterworx Master Host
To modify any unwanted items, modify /opt/cwx/etc/Clusterworx.profile and set any unwanted items
(e.g., Version Control Server) to false.
F. If the management network is different from 192.168.0.xxx, change the /opt/cwx/dhcp/
dhcpd.conf.template file.
3. Install mkelfImage
A. Download file ftp://ftp.lnxi.com/pub/mkelfImage/mkelfImage-2.5-0.i386.rpm
B. Install rpm -ivh
4. Log out and log in again on all host management machines on which you installed part of Clusterworx.
Note
Failure to log out and log in may prevent Clusterworx from launching.
5. Install the software license obtained from Linux Networx on the Master Host by running deploy
license.jar /opt/cwx. Verify that there were no errors.
6. After deploying the license, run the cwxlicense utility program to verify that all of the cluster’s MAC
addresses are in the license.
Clusterworx System Administrator’s Guide
7

Installing Clusterworx
Setting Up a Clusterworx Master Host
8
7. Log in as “root” and use “root” as the password. The License Viewer appears. The list of licensed MAC
addresses appears under Authorized Hosts (this list should match the MAC Address list you gathered
previously).
Note
If you find a discrepancy in your Authorized Hosts list (MAC Addresses), contact Linux Networx
Technical Support.
8. Run the /etc/init.d/cwx status command to verify that the following services are running:
AuthenticationService
DHCPService
DNA.
DatabaseService
FileService.
HostAdministrationService.
IceboxAdministrationService
ImageAdministrationService
InstrumentationService
KernelAdministrationService
LicenseAdministrationService
LicenseUpdateService.
NotificationService
Clusterworx System Administrator’s Guide

PayloadAdministrationService
ProvisioningService
RNA
SynchronizationService
VersionService
VersionService.
Installing Clusterworx
Setting Up a Clusterworx Master Host
9. Import configuration files from the backup configuration or from the new configuration files produced
by Linux Networx. You may also set up hosts, Iceboxes, users, and other related information (including
partitions, regions, groups, and roles) manually through the Clusterworx GUI.
Note
You must obtain a copy of the converter script from Linux Networx—this utility creates output that you
can import into Clusterworx using the dbix utility.
A. Import files to dbix:
Icebox.conf (Converts the icebox.conf file to icebox.dbix)
converter -i= -o=dbix > /tmp/icebox.dbix
Example: converter -i=/opt/lnxi/var/cwx/icebox.conf -o=dbix > /tmp/icebox.dbix
cluster.xml (Converts the cluster.xml file to cluster.uber)
converter -c= -o=uber > /tmp/cluster.uber
Example: converter -c=/etc/cluster.xml -o=uber > /tmp/cluster.uber
powerman.conf (Converts the cluster.uber file to powerman.conf)
converter -u= -o=powerman > /tmp/powerman.conf
Example: converter -u=/tmp/cluster.uber -o=powerman > /tmp/powerman.conf
conman.conf (Converts the cluster.uber file to conman.conf)
converter -u= -o=conman > /tmp/conman.conf
Example: converter -u=/tmp/cluster.uber -o=conman > /tmp/conman.conf
/etc/hosts (Converts the cluster.uber file to /etc/hosts)
converter -u= -o=hosts > /tmp/hosts
Example: converter -u=/tmp/cluster.uber -o=hosts > /tmp/hosts
rhosts (Converts the cluster.uber file to rhosts)
converter -u= -o=rhosts > /tmp/rhosts
Example: converter -u=/tmp/cluster.uber -o=rhosts > /tmp/rhosts
nodes.conf
converter -n= -o=dbix > /tmp/nodes.dbix
Example: converter -n=/opt/lnxi/var/netboot/nodes.conf -o=dbix > /tmp/nodes.dbix
B. Update Clusterworx. Verify the integrity of all converted files before importing into the dbix database.
If the data does not import as expected, delete the imported data through the Clusterworx
GUI and try again.
Run the dbix utility, passing the recently created dbix files:
dbix < /tmp/icebox.dbix
dbix < /tmp/cluster.dbix
Note
Running this step on the nodes.dbix file is not always required if you have imported from the cluster.dbix
file. Log on to Clusterworx and check your hosts. If they do not exist, run dbix < /tmp/nodes.dbix.
Clusterworx System Administrator’s Guide
9

Installing Clusterworx
Setting Up a Clusterworx Master Host
10
C. Update configuration files.
(Verify the integrity of all converted files before implementing.)
/etc/hosts
back up original file
cp /etc/hosts /tmp/hosts.orig
install converted file
cp /etc/hosts
powerman.conf
back up original file
cp /etc/powerman/powerman.conf /tmp/powerman.conf.orig
install converted file
cp /etc/powerman/powerman.conf
conman.conf
back up original file
cp /etc/conman.conf /tmp/conman.conf.orig
install converted file
cp /etc/conman.conf
Note
It is important to note that, by default, the Clusterworx password is “root”. For information on how to
change this password, see Edit a User Account on page 64. Furthermore, when you provision a host,
Clusterworx sets up a root account for your hosts.
10. Type cwx to launch the Clusterworx client software, then log in as “root” using “root” as the password.
Tip
To run Clusterworx from a remote share, map the network drive where you installed Clusterworx and
create a copy of the shortcut on your local machine.
Clusterworx System Administrator’s Guide

Client Installation
Installing Clusterworx
Setting Up a Clusterworx Master Host
Select the Client installation option to allow access to Clusterworx from a local PC that is not part of the
cluster. The client install offers superior performance because it significantly reduces network traffic.
However, the client should be able to connect to every host and must be on the cluster’s internal network.
Tip
A VPN offers secure remote access to the cluster. VPN options include D-Link, Cisco, and software
(Pptp). For information about specific VPN capabilities, please contact technical support.
LINUX CLIENT
1. Select Client from the installation options dialog.
2. Specify the Installation Directory and Host Name, then click Next.
Note
The name of the installation directory may not contain spaces (e.g., “C:\Program Files”).
Furthermore, the Clusterworx Server or Master Host must use a valid host name that is resolvable
through name resolution (i.e., DNS, /etc/hosts). For information on changing the name of the Master
Host, see Rename the Clusterworx Master Host on page 29.
Clusterworx System Administrator’s Guide
11

Installing Clusterworx
Setting Up a Clusterworx Master Host
12
WINDOWS CLIENT
1. Insert the Clusterworx CD in your CD/DVD-ROM drive and allow the Clusterworx installer to launch. If
the installer does not start automatically, launch the autorun.cmd:
d:\autorun.cmd
2. Select Client from the installation options dialog.
3. Specify the Installation Directory and Host Name, then click Next.
4. After the installation is complete, use Explorer to navigate to the installation directory.
5. Copy the Clusterworx shortcut to your desktop. You will use this shortcut to launch Clusterworx.
Tip
You may also start Clusterworx from the command-line interface. For example:
c:\cwx\bin\cloak.exe c:\cwx\bin\cwx.cmd
or
c:\cwx.cmd
Clusterworx System Administrator’s Guide

Migration Utility
Note
When upgrading to a new version of Clusterworx, you must also upgrade any Client and Payload
installations to prevent abnormal operations.
Upgrading to Clusterworx 3.4.2
Warning!
Installing Clusterworx
Migration Utility
If you are using Third-party IPMI metrics and are upgrading to Clusterworx 3.4.2, you must de-select all
custom IPMI metrics from the Metrics Selector dialog. After upgrading, re-populate the Metrics.profile.
Upgrading from Clusterworx 3.3.x
The process of upgrading to the latest version of Clusterworx is almost completely automatic. However, to
prevent data loss or disruption of activity on your cluster, please back up the following before installing
Clusterworx:
Your Clusterworx database and all system data located in CWXHOME$/etc.
InstrumentationMonitors.profile, InstrumentationListeners.profile, Logging.profile, and
DistributionService.profile from /opt/cwx/etc.
Note
After installing Clusterworx, you may apply any special modifications or enhancements you made to
these profiles.
Upgrading from Clusterworx 3.1.x to Clusterworx 3.3.0
Warning!
If you are upgrading from Clusterworx 3.1.2 to 3.3.0, you must change the default ramdisk block size in
any kernels you will continue to use. Change this variable from 4096 to 1024
(i.e., ramdisk_blocksize=1024). To change this variable, see To Edit a Kernel on page 117.
When upgrading Clusterworx, do not run the installation script from the current installation directory.
To upgrade the Payload or Client, you must delete the installation directory (i.e., /opt/cwx) prior to reinstalling.
1. Open a console as the root user.
2. Back up your Clusterworx settings by entering the following from the command line:
dbix -x > cwx-3.1.2.db
3. Stop the Clusterworx services on the host:
/etc/init.d/cwx stop
4. Move the bin, lib, and sys directories:
mkdir /tmp/cwx.old
mv /opt/cwx/bin /tmp/cwx.old
Clusterworx System Administrator’s Guide
13

Installing Clusterworx
Clusterworx Services
14
mv /opt/cwx/lib /tmp/cwx.old
mv /opt/cwx/etc /tmp/cwx.old
5. Perform the CD installation procedure for the Clusterworx Server Installation (see Setting Up a
Clusterworx Master Host on page 4).
6. Re-import your original settings:
cwmigration3_3_0 cwx-3.1.2.db > cwx-3.3.0.db
dbix -d
dbix -i < cwx-3.3.0.db
Warning!
Executing the dbix -d command will delete your database. Back up cwx.3.1.2.db and cwx.3.3.0.db before
proceeding.
7. Deploy a new license.jar (obtained from Technical Support).
8. Upgrade Clusterworx in the payload:
A. Remove (or move) the Clusterworx directory from the payload.
B. Perform a standard payload installation (see Install Clusterworx into the Payload on page 110).
cd /opt/cwx/imaging//payloads//
/mnt/cdrom/install.sh
C. Check-in the changes (if desired) and re-provision the hosts.
Note
If you are upgrading from Clusterworx 3.0 to Clusterworx 3.3.0, you must first migrate your system from
3.0 to 3.1.x. After moving to 3.1.x, you may safely upgrade to 3.3.0.
Tip
If you are upgrading from 3.2.1 to 3.3.0, remove all users’ license-administration privileges from the
database by entering the following commands from the CLI:
for user in `dbix -x privilege-roles.license-administration | cut -c40- | cut -d. -f1 | uniq`; do dbix -d roleprivileges.$user.license-administration;
done
dbix -d privilege-roles.license-administration
Clusterworx Services
Linux employs several services that perform a variety of tasks and act as the nucleus of the system. These
services are started and stopped from scripts that usually exist in /etc/init.d, but the services themselves may
exist in other locations. Clusterworx, typically installed in /opt/cwx, is controlled by one of these services—
this allows you to manage Clusterworx services using standard Linux tools such as chkconfig and service.
Standard functions for services include start, stop, restart, and status. For example:
cd /etc/init.d; ./cwx status
/etc/init.d/cwx stop
/etc/init.d/cwx start
chkconfig --list cwx
Clusterworx System Administrator’s Guide

Chapter 2
Licensing
Overview
The Clusterworx system license is a digitally signed file containing details about what modules are installed
in your system, each module's feature set, license expiration settings (if defined), the hosts available to the
cluster, and the customer for whom the license was created. The Licensing module serves three primary
functions:
License Installation
License Authentication
License Administration
License Installation
The license is packaged as a Clusterworx-deployable Java Archive (JAR) file and is usually named license.jar.
This self-extracting and installable file is deployed into the Clusterworx home directory through the same
process used to install other modules; however, Clusterworx and the LicenseAdministrationService must be
running on the Master Host at the time the you deploy the license file.
Note
If you are upgrading from a previous version of Clusterworx, a new license is required.
To Install the License
1. Open a console to the Master Host.
2. Verify that the Clusterworx services are running on the Master Host, noting that the
LicenseAdministrationService is in the list of running services:
# /etc/init.d/cwx status
(Alternatively, you could also enter service cwx status)
3. If Clusterworx is stopped, you can start it by running the following command as root:
# /etc/init.d/cwx start
(Alternatively, you could also enter service cwx start)
Clusterworx System Administrator’s Guide
15

License Installation
16
4. Deploy the license.jar file to the Clusterworx home directory:
/opt/cwx (usually)
Note
If you need to reinstall the license, enter the following:
# deploy license.jar /opt/cwx
5. Verify your output to ensure the license was successfully installed (see License Viewer on page 17).
Clusterworx System Administrator’s Guide

License Authentication
License Authentication
License Viewer
When you deploy a new license, Clusterworx verifies that the new license contains a valid Linux Networx
signature.
License Administration
After installing a license, you may view license details with the License Viewer. The License Viewer is a GUI
application that provides a visual representation of the Clusterworx system license. The License Viewer does
not allow you to edit license data.
License Viewer
To launch the viewer, enter the following command as root from a console prompt:
# cwxlicense
Clusterworx System Administrator’s Guide
17

License Administration
License Viewer
18
Clusterworx System Administrator’s Guide

Chapter 3
Introduction to
Clusterworx
Overview
Clusterworx reduces the total cost of cluster ownership by streamlining and simplifying all aspects of cluster
management. Through a single point of control, you can automate repetitive installation and configuration
tasks. Clusterworx automates problem determination and system recovery, and monitors and reports health
information and resource utilization.
Clusterworx provides administrators with increased power and flexibility in controlling cluster system
resources, and improved scalability and performance allows Clusterworx to manage cluster systems of any
size. Version-controlled provisioning allows administrators to easily install the operating system (OS) and
applications to all hosts in the cluster and facilitates changes to an individual host or group of hosts. Changes
are saved automatically.
Comprehensive System Monitoring
Clusterworx uses multiple monitoring features to improve system efficiency. These monitors allow you to
examine system functionality from individual host components to the application level and help track system
health, trends, and bottlenecks. With the information collected through these monitors, you can more easily
plan for future computing needs—the more efficiently your cluster system operates, the more jobs it can run.
Over the life of your system, you can accelerate research and time-to-market.
Clusterworx provides results in near real-time and uses only a minute amount of the CPU. All data is
displayed in a portable and easy-to-deploy Java-based GUI that runs on both Linux and Windows. Monitoring
values include CPU usage, disk I/O, file system usage, kernel and operating system information, CPU load,
memory usage, network information and bandwidth, and swap usage. Administrators may also write plug-ins
to add functionality or monitor a specific device or application.
Version Controlled Image Management
Until recently, version-controlled image management was unavailable for cluster systems. Version control
greatly simplifies the task of cluster administration by allowing system administrators to track upgrades and
changes to the system image. If a problem arises with a system image, system administrators can even revert
to a previous, more robust version of the image. By allowing system administrators to update the operating
Clusterworx System Administrator’s Guide
19

Overview
Fast Multicast Provisioning
20
system and other applications both quickly and efficiently, version control ensures that organizations
receive the highest return on their cluster system investment.
Fast Multicast Provisioning
Thanks to fast multicast provisioning, Clusterworx can add or update new images in a matter of minutes—no
matter how many hosts your system contains. This saves time by allowing system administrators to quickly
provision and incrementally update the cluster system as needed; and since updates take only a few minutes,
this means less down-time and fewer system administration headaches.
Clusterworx System Administrator’s Guide

Clusterworx Interface
Clusterworx Interface
Fast Multicast Provisioning
The Clusterworx interface is composed primarily of a navigation tree and a series of tabbed dialogs that
allow you to navigate and configure the cluster.
Server Name
Navigation
Tree
Server Name The name of the server on which Clusterworx is running.
Navigation Tree The navigation tree contains an expandable list of cluster elements (e.g., hosts, partitions,
groups, users, images). Because the tree is tab-specific, it displays only those elements that pertain to the
selected tab.
Tabs Tabs appear along the top of a pane and allow you to navigate and configure cluster elements.
Subtabs Subtabs perform the same function as tabs but appear along the bottom of a pane.
Upper/Lower Panes The upper and lower panes allow you to view cluster information in a structured
environment.
Tabs
Subtabs
(Upper Pane)
(Lower Pane)
Clusterworx System Administrator’s Guide
21

Clusterworx Interface
Customizing the Interface
22
Customizing the Interface
Clusterworx supports the use of the native Java LookAndFeel for each of the supported platforms. This
allows you to configure Clusterworx to look like other applications already running on your system (i.e., the
GTK look and feel for Linux users or the standard Windows interface for Windows users). By default,
Clusterworx uses the MetalLookAndFeel and a custom Linux Networx color scheme for all platforms.
Tip
Using the default look and feel reduces memory consumption and improves performance.
To Configure the GTK Look and Feel
1. Open your user profile:
$CWXHOME/etc/user-.profile
2. Add the following line to your user profile:
ui.manager: com.sun.java.swing.plaf.gtk.GTKLookAndFeel
To Configure the Windows Look and Feel
1. Open your user profile:
$CWXHOME/etc/user-.profile
2. Add the following line to your user profile:
ui.manager: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Note
The interface look and feel can be set globally by commenting out the ui.manager setting contained in
$CWXHOME/etc/system-Clusterworx.profile and adding one of the above lines to the profile. However, it
is recommended that interface customizations be configured on a per-user basis.
To override global settings for an individual user, add a new ui.manager configuration to the user profile.
Clusterworx System Administrator’s Guide

Chapter 4
Host Administration
Clustered Environments
In a clustered environment, there is always at least one host that acts as the master of the remaining hosts
(for large systems, multiple masters may be required). This host, commonly referred to as the Clusterworx
Master Host, is reserved exclusively for managing the cluster and is not typically available to perform tasks
assigned to the remaining hosts.
To manage the use of the remaining hosts in the cluster, you can divide the hosts (as needed) into partitions
and regions. Partitions include a strict set of hosts that may not be shared with other partitions. Regions are a
subset of a partition and may share any hosts that belong to the same partition. Hosts contained within a
partition may belong to a single region or may be shared with multiple regions. Dividing up the system can
help simplify cluster management and allows you to have different privileges on various parts of the system.
Clusters Partitions
Regions Hosts
Host Configuration
Shared
Hosts
Clusterworx provides configuration, power management, and real-time monitoring (instrumentation) for all
hosts in the cluster. The Host tab allows you to:
Add hosts to partitions and regions.
Define each host (including the Clusterworx Master Host).
Assign hosts to Iceboxes (see Power Control on page 67).
Edit an existing host.
Clusterworx System Administrator’s Guide
23

Host Configuration
24
Delete a host(s).
Define, edit, and delete partitions.
Define partition relationships to regions and hosts.
Define, edit, and delete regions.
Define region relationships to groups (see User Administration on page 49).
View statistical data for the system (see Instrumentation on page 40).
Clusterworx System Administrator’s Guide

Hosts
The following sections outline the fundamentals of adding, editing, and deleting hosts.
Add a Host
Adding a host is as simple as describing it to Clusterworx. To add a host, you must provide the host name,
description, MAC address, IP address, and the partition and region to which the host belongs. Hosts may be
added only after you have set up a Master Host (see Setting Up a Clusterworx Master Host on page 4).
To Add a Host
1. Select the Hosts tab, then select the Configuration subtab.
2. Select New Host from the File menu or right-click on the cluster icon in the navigation tree and select
New Host. A new host pane appears.
3. Enter the name of the new host in the Name field.
4. (Optional) Enter a description of the new host in the Description field.
5. (Optional) Select the name of the partition to which this host belongs from the drop-down menu.
6. Create Regions, Interfaces, and Icebox assignments as needed, then click Apply to create the new host or
click Close to abort this action.
Clusterworx System Administrator’s Guide
Hosts
Add a Host
25

Hosts
Add a Host
26
ASSIGN REGIONS
The Regions subtab allows you to identify any regions to which the host belongs.
1. (Optional) Select the Regions subtab and click Add. The Select Regions dialog appears.
2. Select the region to which the host belongs. To select multiple regions, use the Shift or Ctrl keys.
3. Click OK.
CREATE INTERFACES
The Interfaces subtab allows you to create new interfaces and assign management responsibilities.
1. Click the Interfaces subtab at the bottom of the host pane. The New Interface dialog appears.
2. Enter the host’s MAC and IP addresses.
Tip
To find the MAC address of a new, un-provisioned host, you must watch the output from the serial
console. Etherboot displays the host’s MAC address on the console when the host first boots. For
example:
Etherboot 5.1.2rc5.eb7 (GPL) Tagged ELF64 ELF (Multiboot) for EEPRO100]
Relocating _text from: [000242d8,00034028) to [17fdc2b0,17fec000)
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal?
Probing net...
Probing pci...Found EEPRO100 ROM address 0x0000
Clusterworx System Administrator’s Guide

[EEPRO100]Ethernet addr: 00:02:B3:11:03:77
Searching for server (DHCP)...
(*If conman is set up and working, this information is also contained in the conman file.)
To find the MAC address on a host that is already running, enter ifconfig -a from the CLI and look for the
HWaddr of the management interface.
3. If Clusterworx will use this interface to manage the host (i.e., provisioning will use this interface and
monitoring data will transmit from this interface) check the Management option.
4. Click OK.
ICEBOX PORT ASSIGNMENTS
1. (Optional) Select the Iceboxes subtab and click Add to assign which Icebox will control the host (you can
select only one Icebox at a time). The Icebox Selection dialog appears.
2. Specify the port (1–10) through which the host is attached to the Icebox.
3. (Optional) Select Primary if the host is connected to multiple Iceboxes. Clusterworx uses the serial access
and temperature from the primary connection.
4. Click OK.
Clusterworx System Administrator’s Guide
Hosts
Add a Host
27

Hosts
Edit a Host
28
Edit a Host
Editing hosts allows you to change information previously saved about a host, edit host configurations, or
move hosts in and out of partitions and regions.
To Edit a Host
1. Select the Hosts tab, then select the Configuration subtab.
2. Select a host from the navigation tree. To select multiple hosts, use the Shift or Ctrl keys.
3. Select Edit from the Edit menu or right-click on the host(s) in the navigation tree and select Edit.
Clusterworx displays the host pane for each selected host. From this view, you can make changes to the
host(s).
Warning!
Changing the name of the Master Host may prevent the cluster from functioning correctly. For
information on changing the name of the Master Host, see Rename the Clusterworx Master Host on
page 29.
4. Click Apply to accept the changes or click Close to abort this action.
Clusterworx System Administrator’s Guide

RENAME THE CLUSTERWORX MASTER HOST
Changing the name of the Clusterworx Master Host may prevent applications such as Clusterworx and Host
Failover from operating correctly. Before changing the name of the Master Host, you should always consider
any applications that require the use of this name (i.e., job schedulers, mpi “machines” files, and other thirdparty
software). In some cases, you may need to consult with application vendors regarding special
instructions on changing the host name.
When you change the host name, all Clusterworx services, hosts, and clients must be able to resolve the new
name. To ensure that your system functions properly after renaming the Master Host, you must update the
host name in several files.
Note
Before you begin, enter /etc/init.d/cwx stop to shut down Clusterworx on the system.
1. On the Master Host, edit the following files:
/opt/cwx/@genesis.profile (host & system.rna.host)
/etc/sysconfig/network/profiles/*
Tip
If you are running a version of Clusterworx older than 3.3.x, you must also edit the Activator profile:
/opt/cwx/etc/Activator.profile (*.host=)
2. On the compute hosts, in payloads, and on clients:
/opt/cwx/@genesis.profile (system.rna.host)\
3. Additionally, the new host name must be resolvable. This means that the local /etc/hosts or DNS settings
must be updated on all Clusterworx servers, hosts, payloads, clients, and other vendor-specific
configuration files that contain host name information.
Clusterworx System Administrator’s Guide
Hosts
Edit a Host
29

Hosts
Disable a Host
30
Disable a Host
Disabling a host allows you to render the host temporarily inoperative without removing it from the cluster.
To Disable a Host
1. Select the Hosts tab, then select the Configuration subtab.
2. Select a host from the navigation tree.
3. Select Edit from the Edit menu or right-click on the host in the navigation tree and select Edit.
Clusterworx displays the host pane.
4. Check the Disable Host option.
Clusterworx System Administrator’s Guide

Delete a Host
Deleting a host will remove it from the cluster.
To Delete a Host
1. Select the Hosts tab, then select the Configuration subtab.
2. Select the host you want to delete from the navigation tree. To select multiple hosts, use the Shift or Ctrl
keys.
3. Select Delete from the File menu or right-click on the host(s) in the navigation tree and select Delete.
Clusterworx asks you to confirm your action.
4. Click OK to remove the host(s) or click Cancel to abort this action.
Note
To recover a host deleted from a cluster, see Add a Host on page 25. To disable a host temporarily, see
Disable a Host on page 30.
Hosts
Delete a Host
Clusterworx System Administrator’s Guide
31

Partitions
Add a Partition
32
Partitions
The following sections outline the fundamentals of adding, editing, and deleting partitions.
Add a Partition
Partitions are used to separate clusters into non-overlapping collections of hosts. Hosts that belong to a
partition may not be used by anyone who is not authorized to access the partition. Within the partition, host
access may be shared between regions of users.
To Add a Partition
1. Select the Hosts tab, then select the Configuration subtab.
2. Select New Partition from the File menu or right-click the cluster icon in the navigation tree and select
New Partition. A new partition pane appears.
3. Enter the name of the new partition in the Name field.
4. (Optional) Enter a description of the new partition in the Description field.
Clusterworx System Administrator’s Guide

5. Select the Regions tab and click Add. The Select Regions dialog appears.
6. Select region(s) you want to include in this partition and click OK. Use the Shift and Ctrl keys to select
multiple regions.
7. Select the Hosts tab and click Add to display the Select Hosts dialog.
8. Select a host(s) to add to this partition and click OK. Use the Shift and Ctrl keys to select multiple hosts.
9. Click Apply to accept the changes or click Close to abort this action.
Partitions
Add a Partition
Clusterworx System Administrator’s Guide
33

Partitions
Edit a Partition
34
Edit a Partition
Editing a partition allows you to change previously saved information about a partition. You can edit or
remove regions, alter partition configurations, disable partitions, or remove partitions from the host.
To Edit a Partition
1. Select the Hosts tab, then select the Configuration subtab.
2. Select a partition from the navigation tree. To select multiple partitions, use the Shift or Ctrl keys.
3. Select Edit from the Edit menu or right-click on the partition(s) in the navigation tree and select Edit.
Clusterworx displays the partition pane. From this view, you may make changes to the partition.
4. Click Apply to accept the changes or click Close to abort this action.
Clusterworx System Administrator’s Guide

Disable a Partition
Partitions
Disable a Partition
Temporarily disabling a partition allows you to take the partition out of service without returning the hosts
associated with it to the default partition.
To Disable a Partition
1. Select the Hosts tab, then select the Configuration subtab.
2. Select a partition from the navigation tree.
3. Select Edit from the Edit menu or right-click on the partition in the navigation tree and select Edit.
Clusterworx displays the partition pane.
4. Check the Disable Partition option.
5. Click Apply to accept the changes or click Close to abort this action.
Delete a Partition
Deleting a partition allows you to remove unused partitions from the system. In some cases, you may prefer
to temporarily disable a partition.
Note
If you delete a partition, all regions and hosts associated with the partition will move to the default
partition. To delete regions and hosts, refer to Regions on page 36 and Hosts on page 25.
To Delete a Partition
1. Select the Hosts tab, then select the Configuration subtab.
2. Select the partition you want to delete from the navigation tree. To select multiple partitions, use the Shift
or Ctrl keys.
3. Select Delete from the File menu or right-click on the partition(s) in the navigation tree and select Delete.
Clusterworx asks you to confirm your action.
Clusterworx System Administrator’s Guide
35

Regions
Add a Region
36
Regions
The following sections outline the fundamentals of adding, editing, and deleting regions.
Add a Region
A region is a subset of a partition and may share any hosts that belong to the same partition—even if the hosts
are currently used by another region. Adding a region(s) allows you to more closely allocate resources to
specific groups and users.
To Add a Region
1. Select the Hosts tab, then select the Configuration subtab.
2. Select New Region from the File menu or right-click on a partition in the navigation tree and select New
Region. A new region pane appears.
3. Enter the name of the new region in the Name field.
4. (Optional) Enter a description of the new region in the Description field.
5. (Optional) Select the name of the partition to which to assign the region from the drop-down menu.
Note
Regions not assigned to a partition become part of the default or unassigned partition.
6. Select the Hosts subtab, then click Add to assign a host(s) to the region. The Select Hosts dialog appears.
Clusterworx System Administrator’s Guide

7. Select the host(s) you want to add to the region from the Select Hosts dialog (use the Shift or Ctrl keys to
select multiple hosts).
8. Click OK to add the host(s) or click Cancel to abort this action.
9. Select the Groups subtab, then click Add. The Select Groups dialog appears.
Regions
Add a Region
10. From the Select Groups dialog, select the group(s) you want to add to the region (use the Shift or Ctrl keys
to select multiple groups). Adding groups to the region defines which users may access the hosts assigned
to the region.
11. Click OK to add the group(s) or click Cancel to abort this action.
Tip
A common mistake made when defining regions is forgetting to assign groups to the region. If you forget
to assign groups, the hosts appear to be non-existent.
12. Click Apply to add the new region or click Close to abort this action.
Clusterworx System Administrator’s Guide
37

Regions
Edit a Region
38
Edit a Region
Editing regions allows you to change previously saved information about a region or to modify region
memberships by adding or removing groups or hosts.
To Edit a Region
1. Select the Hosts tab, then select the Configuration subtab.
2. Select a region from the navigation tree. To select multiple regions, use the Shift or Ctrl keys.
3. Select Edit from the Edit menu or right-click on the region(s) in the navigation tree and select Edit. The
region pane appears.
4. From this view, you may make changes to the Region(s).
5. Click Apply to accept the changes or click Close to abort this action.
Clusterworx System Administrator’s Guide

Delete a Region
Deleting a region allows you to remove unused regions from the system.
To Delete a Region
1. Select the Hosts tab, then select the Configuration subtab.
Regions
Delete a Region
2. Select the region you want to delete from the navigation tree. To select multiple regions, use the Shift or
Ctrl keys.
3. Select Delete from the File menu or right-click on the region(s) in the navigation tree and select Delete.
Clusterworx asks you to confirm your action.
4. Click OK to remove the region(s) or click Cancel to abort this action.
Note
If you delete a region, all hosts associated with the region return to the partition (or parent region) to
which the region belonged. If the region was not part of a partition, the hosts move to the default
partition.
Clusterworx System Administrator’s Guide
39

Instrumentation
States
40
Instrumentation
The Clusterworx instrumentation service provides the ability to monitor system health and activity for every
host in the cluster. Hosts may be monitored collectively to provide a general system overview, or individually
to allow you to view the configuration of a particular host (useful when diagnosing problems with a
particular host or configuration). From the Instrumentation tab, you can view statistical data for the
following areas:
General
CPU
Memory
Disk
Network
Kernel
Load
Temperature
Tip
When using the Clusterworx client by exporting an X session over an SSH connection, enabling the
gradient fill and anti-aliasing options for instrumentation may adversely affect the performance of the
GUI. This is common on slower systems. To improve system performance, disable the Gradient Fill and
Anti-Aliasing options under the View menu. For best performance, install a Clusterworx Client.
States
Clusterworx uses the following icons to provide visual cues about system status. These icons appear next to
each host viewed with the instrumentation service or from the navigation tree. Similar icons appear next to
clusters, partitions, and regions to indicate the status of hosts contained therein.
States
Healthy
Unknown
Off
Provisioning
Disabled
Logging
Clusterworx System Administrator’s Guide
Healthy Informational Warning Critical Error

Clusterworx Message Log
Instrumentation
Clusterworx Message Log
Clusterworx also tracks messages logged for each host in the cluster. The Clusterworx message log is located
on the instrumentation overview screen. If you select multiple hosts (or a container such as a cluster,
partition, or region), the log shows messages for any host in the selection. If you select a single host, the
message log shows messages for this host only. Messages have three severity levels: error, warning, and
information. For details on instrumentation event monitoring, see Instrumentation Service on page 171.
Menu Controls
The output for the instrumentation service is easily configured and displayed using menu controls. These
controls are divided between the Edit and View menus.
Edit Menu
Interval Set the frequency (in seconds) with which to gather and display data—10, 5, or 1.
Metrics Select and display custom metrics defined for your system—this option is not available to all tab
views. See Metrics on page 175 for information on defining metrics.
Filter List hosts that are in specific states (general tab only).
View Menu
Overview Display all statistical data for the selected host(s).
Thumbnail Display a simplified, graphical status for the selected host(s). Each thumbnail includes CPU,
memory, and disk statistics.
List View pre-configured and user-defined metrics for the selected host(s) in tabular form.
Sort Organize and display statistical data according to the name or state of the host(s).
Size Change the display size of thumbnails (Small, Medium, Large).
Anti-Aliasing Apply smoothing to line graphs.
Gradient Fill Apply fill colors to line graphs.
Clusterworx System Administrator’s Guide
41

Instrumentation
General Tab
42
General Tab
The General tab provides details about the health, system configuration, and resource utilization of the
host(s) selected in the navigation tree. You may compile and display system data into an overview, thumbnail
view, or list view by selecting the corresponding option from the View menu.
Overview
The Overview option displays the overall status of the selected host(s), including system health, usage
statistics, and any messages generated by the host(s). See States on page 40 for a list of system health
indicators and Clusterworx Message Log on page 41 for information regarding generated messages.
Clusterworx System Administrator’s Guide

Instrumentation
General Tab
THUMBNAIL VIEW
The Thumbnail view is available only for the General tab and displays a graphical representation of the
system health, CPU usage, memory availability, and disk space. From this view you may sort the hosts by
name or state (from the View menu), or define a filter in the Edit menu to display only those hosts that are in
a specific state. See States on page 40 for a list of system health indicators.
Clusterworx System Administrator’s Guide
43

Instrumentation
General Tab
44
LIST VIEW
Available only for the General tab, the List view displays all pre-configured and custom metrics being
observed by the instrumentation service. To add metrics, see Instrumentation Service on page 171.
Tip
You may copy and paste the contents of list view tables for use in other applications.
Clusterworx System Administrator’s Guide

CPU Tab
Select the CPU tab to monitor the CPU utilization for the selected host(s).
Memory Tab
Select the Memory tab to monitor the physical and virtual memory utilization for the selected host(s).
Instrumentation
CPU Tab
Clusterworx System Administrator’s Guide
45

Instrumentation
Disk Tab
46
Disk Tab
Select the Disk tab to monitor the disk I/O and usage for the selected host(s).
Network Tab
Select the Network tab to monitor packet transmissions and errors for the selected host(s).
Clusterworx System Administrator’s Guide

Kernel Tab
Select the Kernel tab to monitor the kernel information for the selected host(s).
Load Tab
Select the Load tab to monitor the load placed on the selected host(s).
Instrumentation
Kernel Tab
Clusterworx System Administrator’s Guide
47

Instrumentation
Temperature Tab
48
Temperature Tab
Select the Temperature tab to view the temperature readings for the selected host(s). Each temperature
summary contains up to five temperature readings—four processor temperatures followed by the ambient
host temperature. On hosts that support IPMI, these temperature readings differ slightly—two processor
temperatures, two power supply temperatures, and the ambient host temperature
Note
The processor temperature readings for IPMI-based hosts indicate the amount of temperature change
that must occur before the CPU’s thermal control circuitry activates to prevent damage to the CPU.
These are not actual CPU temperatures.
Clusterworx System Administrator’s Guide

Chapter 5
User Administration
Working Environment
Clusterworx allows you to configure groups, users, roles, and privileges to establish a working environment
on the cluster. A group refers to an organization with shared or similar needs that is structured using specific
roles (permissions and privileges) and region access that may be unique to the group or shared with other
groups. Members of a group (users) inherit all rights and privileges defined for the group(s) to which they
belong.
Groups
Group
Roles
Users
Regions
Clusterworx System Administrator’s Guide
49

Working Environment
50
For example, a user assigned to multiple groups (as indicated by the following diagram) has different rights
and privileges within each group. This flexibility allows you to establish several types of user roles: full
administration, group administration, user, or guest.
Multi-Group Users
Note
Clusterworx currently supports adding users and groups to payloads only—it does not support the
management of local users and groups on the Master Host. Users with local Unix accounts do not
automatically have Clusterworx accounts, and this information cannot be imported into Clusterworx.
If you are using local authentication in your payloads and intend to add Clusterworx users or groups,
ensure that the user and group IDs (UIDs and GIDs, respectively) match up between the accounts on the
Master Host and Clusterworx. Otherwise, NFS and Runner may not work properly.
Clusterworx System Administrator’s Guide

Default User Administration Settings
Clusterworx implements the following structure during the installation process:
The root and guest user accounts are created.
The root, guest, power, and users groups are created.
The root and user roles are created.
All privileges allowed by the installed license are created.
User Configuration
The Configuration subtab allows users to:
Create, modify, or delete groups.
Create, modify, or delete users.
Create modify, or delete roles.
Assign or delete privileges.
Default User Administration Settings
User Configuration
Clusterworx System Administrator’s Guide
51

Roles
Add a Role
52
Roles
The following sections outline the fundamentals of adding, editing, and deleting roles. Roles are associated
with groups and privileges, and define the functionality assigned to each group. Several groups can use the
same role.
Add a Role
Adding a role to Clusterworx allows you to define and grant system privileges to groups.
To Add a Role
1. Select the Users tab.
2. Select New Role from the File menu or right-click on the Roles icon in the navigation tree and select New
Role. A new role pane appears.
3. Enter the name of the new role in the Name field.
4. (Optional) Enter a description of the role in the Description field.
5. Click Apply to save the role or click Close to abort this action.
Note
Adding or revoking privileges will not affect users that are currently logged into Clusterworx. Changes
will take effect only after the users reboot.
Clusterworx System Administrator’s Guide

GRANT PRIVILEGES
The privileges tab allows you to assign permissions to a role. Any user with the role will have these
permissions in the system. See Privileges on page 56.
1. To add privileges to a role(s), select the Privileges subtab and click Add.
2. Select the privilege(s) to grant the current role (use the Shift or Ctrl keys to select multiple privileges).
3. Click OK to apply the privileges to the role or click Cancel to abort this action.
ASSIGN ROLES TO GROUPS
Clusterworx allows you to assign a role(s) to multiple groups. This permits users to have varied levels of
access throughout the system.
1. To assign a role(s) to a group, click Add.
2. Select the group(s) to which to assign the role(s). Use the Shift or Ctrl keys to select multiple roles.
3. Click OK to apply the role to the group(s) or click Cancel to abort this action.
Clusterworx System Administrator’s Guide
Roles
Add a Role
53

Roles
Edit a Role
54
Edit a Role
Editing roles allows you to modify privileges defined for a group.
To Edit a Role
1. Select the Users tab.
2. Select a role from the navigation tree. To select multiple roles, use the Shift or Ctrl keys.
3. Select Edit from the Edit menu or right-click on the role(s) in the navigation tree and select Edit.
Clusterworx displays the role pane for each selected role.
4. From this view, you may make changes to the role.
5. Click Apply to accept the changes or click Close to abort this action.
Note
Deleting a role will not affect the privileges of a user that is currently logged into Clusterworx. Changes
will take effect only after you restart the Clusterworx client.
Clusterworx System Administrator’s Guide

Delete a Role
Deleting a role removes user privileges assigned to the role.
To Delete a Role
1. Select the Users tab.
2. Select the role you want to delete from the navigation tree. To select multiple roles, use the Shift or Ctrl
keys.
3. Select Delete from the File menu or right-click on the role(s) in the navigation tree and select Delete.
Clusterworx asks you to confirm your action.
4. Click OK to remove the role(s) or click Cancel to abort this action.
Note
Deleting a role will not affect the privileges of a user that is currently logged into Clusterworx. Changes
will take effect only after you restart the Clusterworx client.
Roles
Delete a Role
Clusterworx System Administrator’s Guide
55

Roles
Privileges
56
Privileges
Privileges are permissions or rights that grant varying levels of access to system users. Clusterworx allows
you to assign privileges as part of a role, then assign the role to specific user groups. Users assigned to
multiple groups will have different roles and access within each group. This flexibility allows you to establish
several types of roles you can assign to users: full administration, group administration, user, or guest. See
User Administration on page 49. The following table lists the privileges established for various Clusterworx
modules at the function and sub-function levels:
Module Name Description
Host Administration Ability to administer cluster resources.
Charting Ability to configure cluster historical charting.
Configuration Ability to configure resource partition, region, and host settings.
Instrumentation Ability to configure cluster monitors.
Power Ability to manage the cluster power settings.
Shell Ability to execute parallel remote commands.
Icebox Administration Ability to manage the cluster Iceboxes.
Charting Ability to configure Icebox historical charting.
Configuration Ability to configure cluster Iceboxes.
Instrumentation Ability to configure Icebox monitors.
Power Ability to manage the Icebox power settings.
Shell Ability to manage Icebox remote connections.
Image Administration Ability to manage host images.
Provisioning Ability to deploy host images.
User Administration Ability to administer users.
Configuration Ability to configure user settings, groups, and roles.
Clusterworx System Administrator’s Guide

Groups
The following sections outline the fundamentals of adding, editing, and deleting groups.
Add a Group
Adding a group creates a collection of users with shared or similar needs (e.g., an engineering, testing, or
administrative group).
To Add a Group
1. Select the Users tab.
2. Select New Group from the File menu or right-click on the Groups icon in the navigation tree and select
New Group. A new group pane appears.
3. Enter the group name in the Name field.
4. (Optional) Clusterworx assigns a system-generated Group ID. Enter any changes to the ID in the Group
ID field.
5. (Optional) Enter a description for the group in the Description field.
6. After making all configurations, click Apply to add the group or click Close to abort this action.
Clusterworx System Administrator’s Guide
Groups
Add a Group
57

Groups
Add a Group
58
ADD USERS
The Users subtab allows you to identify the users that belong to the current group. Users are allowed to be
part of any number of groups, but granting access to multiple groups may allow users unnecessary privileges
to various parts of the system. See Roles on page 52.
1. To add a user to the group, click Add. The Add Users dialog appears.
2. Select the user(s) to add to the group (use the Shift or Ctrl keys to select multiple users).
3. Click OK to add the user to the group(s) or click Cancel to abort this action.
ASSIGN ROLES
The Roles subtab allows you to assign specific roles to the group.
1. To assign a role(s) to the group, click Add. The Add Roles dialog appears.
2. Select the role(s) to assign the group (use the Shift or Ctrl keys to select multiple users).
3. Click OK to assign the role(s) to the group or click Cancel to abort this action.
Clusterworx System Administrator’s Guide

ASSIGN REGIONS
The Regions subtab allows you to grant a group access to specific regions of the system. See Host
Administration on page 23.
1. To assign a region(s) to the group, click Add. The Add Regions dialog appears.
2. Select the region(s) to assign the group (use the Shift or Ctrl keys to select multiple regions).
3. Click OK to assign the region(s) to the group or click Cancel to abort this action.
Clusterworx System Administrator’s Guide
Groups
Add a Group
59

Groups
Edit a Group
60
Edit a Group
Editing a group allows you to change previously saved information about a group or modify group
memberships by adding or removing users.
To Edit a Group
1. Select the Users tab.
2. Select a group from the navigation tree. To select multiple groups, use the Shift or Ctrl keys.
3. Select Edit from the Edit menu or right-click on the group(s) in the navigation tree and select Edit.
Clusterworx displays the group pane for each selected group.
4. From this view, you may make changes to the Group.
5. Click Apply to accept the changes or click Close to abort this action.
Clusterworx System Administrator’s Guide

Delete a Group
Deleting a group allows you to remove unused groups from the system.
To Delete a Group
1. Select the Users tab.
2. Select the group you want to delete from the navigation tree. To select multiple groups, use the Shift or
Ctrl keys.
3. Select Delete from the File menu or right-click on the group(s) in the navigation tree and select Delete.
Clusterworx asks you to confirm your action.
4. Click OK to remove the group(s) or click Cancel to abort this action.
Groups
Delete a Group
Clusterworx System Administrator’s Guide
61

Users
Add a User
62
Users
The following sections outline the fundamentals of adding, editing, and deleting users.
Add a User
Adding a user to Clusterworx creates an account for the user and grants access to the system.
To Add a User
1. Select the Users tab.
2. Select New User from the File menu or right-click a region and select New User. A new user pane
appears.
3. Enter the user’s login name in the User Name field.
4. (Optional) Clusterworx assigns a system-generated user ID. Enter any changes to the ID in the User ID
field.
5. Enter the user’s first and last name in the Full Name field.
6. Enter a new password for the user in the Password field.
7. Re-enter the password in the Confirm Password field.
8. (Optional) Specify the user’s home directory in the Home Directory field (e.g., /home/username).
9. (Optional) Enter a shell for this user or click the drop-down menu to select an existing shell. By default,
Clusterworx uses /bin/bash.
10. After making all configurations, click Apply to make the changes or click Close to abort this action.
Clusterworx System Administrator’s Guide

GROUPS SUBTAB
The groups tab allows you to identify the groups to which the user belongs. Users are allowed to be part of
any number of groups, but granting access to multiple groups may allow users unnecessary privileges to
various parts of the system. See Roles on page 52.
1. To add the user to a group(s), click Add.
2. Select the group(s) to which to assign the user (use the Shift or Ctrl keys to select multiple groups).
3. Click OK to add the user to the group(s) or click Cancel to abort this action.
EDIT BUTTON
Use the Edit button to change a group to be the primary group.
PRIMARY GROUP
Each user must have a single primary group. If you do not specify a primary group, Clusterworx
automatically assigns the user to the “users” group. If the “Create a private group for the user” checkbox is
selected, Clusterworx adds a new group with the same name as the user. If you are using third-party power
controls, the power group must be the primary group for at least one user.
DISABLE ACCOUNT
This check box indicates whether or not the user can log into this account. Selecting this option signifies that
the user account will not be available for inclusion in payloads. This allows you to temporarily disable the
user account without deleting it from Clusterworx.
Clusterworx System Administrator’s Guide
Users
Add a User
63

Users
Edit a User Account
64
Edit a User Account
Editing a user account allows you to change information previously saved about a user.
To Edit a User
1. Select the Users tab.
2. Select a user from the navigation tree. To select multiple users, use the Shift or Ctrl keys.
3. Select Edit from the Edit menu or right-click on the user(s) in the navigation tree and select Edit.
Clusterworx displays a user pane for each user selected. From this view, you may make changes to the
user account.
4. Click Apply to accept the changes or click Close to abort this action.
Clusterworx System Administrator’s Guide

Disable a User Account
Disabling a user account allows you to render the account temporarily inoperative without removing it.
To Disable a User Account
1. Select the Users tab.
2. Select a user from the navigation tree.
3. Select Edit from the Edit menu or right-click on the user in the navigation tree and select Edit.
Clusterworx displays the user pane.
4. Check the Disable Account option.
5. Click Apply. The user icon in the navigation tree changes status to disabled.
Users
Disable a User Account
Clusterworx System Administrator’s Guide
65

Users
Delete a User Account
66
Delete a User Account
Deleting a user allows you to remove unused user accounts from the system. To temporarily disable a user
account, see Disable a User Account on page 65.
To Delete a User
1. Select the Users tab.
2. Select the user you want to delete from the navigation tree. To select multiple users, use the Shift or Ctrl
keys.
3. Select Delete from the File menu or right-click on the user(s) in the navigation tree and select Delete.
Clusterworx asks you to confirm your action.
4. Click OK to remove the user(s) or click Cancel to abort this action.
Clusterworx System Administrator’s Guide

Chapter 6
Power Control
Icebox Administration
The Icebox administration feature provides you with the ability to add an Icebox, view or edit the Icebox
configuration, and control Icebox functions. Clusterworx is integrated with the Icebox to provide power
management, remote reset, architecture-independent temperature monitoring, and serial access for each host
installed in the cluster. For specific information about the Icebox, please refer to the Icebox User's Guide (see
Linux Networx Documentation on the Web on page ii).
Note
Ensure that the Icebox is at least version 3.1, build 53 (or higher). To verify your version and build, use
the version command on the Icebox. Refer to the Icebox User's Guide for details.
The following is a list of common site-specific configuration items referenced in this section of the guide:
IP Address
Host name
Netmask
SSH
Clusterworx System Administrator’s Guide
67

Icebox Administration
Add an Icebox
68
Add an Icebox
To Add an Icebox
1. Select the Power Control tab.
2. Select the Configuration subtab.
3. Select New Icebox from the File menu or right-click on the cluster icon in the navigation tree and select
New Icebox. An Icebox pane appears.
4. Enter the name of the new Icebox in the Name field.
5. (Optional) Enter a description of the Icebox in the Description field.
6. Enter a new password for the Icebox in the Password field (this is the administrative password).
7. Re-enter the password in the Confirm Password field.
8. Enter the IP address for the Icebox in the Address field.
Clusterworx System Administrator’s Guide

9. Enter the MAC address for the Icebox in the MAC field.
Tip
After entering a name and an IP address, click Connect to connect to the Icebox. Clusterworx sets the
MAC address for you.
Note
When gathering data from an Icebox, you must first connect to the Icebox by clicking Connect.
Otherwise, you are communicating only with the Clusterworx database.
Icebox Administration
Add an Icebox
10. Click Connect. A group of subtabs appears along the bottom of the Icebox pane.
11. Use the subtabs to configure the Icebox. When finished, click Apply to add the Icebox or click Close to
abort this action.
Clusterworx System Administrator’s Guide
69

Icebox Administration
Add an Icebox
70
GENERAL SUBTAB
The Configuration General subtab allows you to select various Icebox settings. These include enabling port
history, enabling port authentication, enabling concurrent ports, and enabling temperature shutdowns.
Enable Port History Instructs the Icebox to automatically output the last 16k of data transferred on the
console port. If you connect to any of the console ports (1-10 or Aux 1-2), the Icebox outputs the last 16k of
data rather than simply display a blank screen. This is beneficial if you want to display boot messages when
you connect to a port. For information on how to view a history of all console port activity, see the Icebox
User’s Guide.
Enable Port Authentication Select this option to increase security for remote access to console ports. With
this option enabled, users that connect to consoles by Telnetting to a specific TCP port must authenticate
before gaining access to the console. If this option is disabled, users gain immediate access to the console and
are not required to enter a password. The need to use this setting depends on your specific application and
how you typically access hosts in your system. If you use Conman and are behind a secure network, you may
elect to leave this option disabled.
Enable Concurrent Ports Select this option to enable multiple simultaneous connections to a serial port. See
the Icebox User’s Guide for additional information.
Enable Temperature Shutdown Enables the ability to shut down hosts whose temperature readings exceed
the temperature thresholds setting (strongly recommended). See Temperature Thresholds on page 72.
Note
Icebox temperature shutdown settings do not apply to IPMI-based hosts.
Clusterworx System Administrator’s Guide

PORTS SUBTAB
Icebox Administration
Add an Icebox
The Configuration Ports subtab allows you to change port settings. This feature, originally configured in host
administration, also allows you to view which ports are connected to which hosts (see Add a Host on
page 25).
To edit port settings, double-click the port or select a port and click Edit. The Edit Port dialog appears.
Clusterworx System Administrator’s Guide
71

Icebox Administration
Add an Icebox
72
Note
The Edit Port dialog does not allow you to edit a host-port association designated as a Serial port. See Add
a Host on page 25 to modify these settings.
Auto Power On This option allows you to configure any of the host ports (1-10) to power on automatically
when the Icebox is turned on. For example, if the system loses power, all ports with Auto Power On enabled
turn on once power is restored. Otherwise, you must manually restore power to the ports.
Enable Flow Control Configure the hardware flow control setting for each of the 10 host and 2 auxiliary
console ports. Hardware flow control allows the transaction receiver to tell the transmitter to stop sending
data (e.g., if the receiver’s buffer is getting too full). This can eliminate dropped data due to buffer overflow.
When this option is enabled, it is important to ensure that the host’s control software is configured to support
it. Typically, this option is disabled unless critical data is transmitting at the fastest baud rate (115200).
Baud Rate Configure the baud rate for each of the 10 host and 2 auxiliary console ports. In order to
establish proper console communication with hosts, this setting must match on both the Icebox port and the
host. In situations where third party peripherals such as switches and UPS equipment function only at a
slower baud rate, lower the baud setting to match. The fastest setting (115200) is recommended whenever
supported.
Note
Baud settings must be the same for the kernel, the Icebox, and LinuxBIOS.
Temperature Thresholds This option allows you to set up to five temperature thresholds for each host (four
processor temperatures followed by the ambient host temperature). Should the host’s temperature exceed
any of these thresholds, the Icebox will shut off power to the host (i.e., a hard power off). This option requires
that Enable Temperatures Shutdown is enabled (see Enable Temperature Shutdown on page 70).
Temperatures are monitored internally.
Note
Icebox temperature thresholds do not apply to IPMI-based hosts.
Clusterworx System Administrator’s Guide

NETWORK SUBTAB
Icebox Administration
Add an Icebox
The Configuration Network subtab allows you to view the Icebox network settings (e.g., the DHCP status,
address, and gateway).
1. If the DHCP Status is OFF, the Icebox uses locally stored static IP information to configure its network.
You can change this information by editing the address, netmask, and gateway settings in the upper and
lower panes.
2. If the DHCP Status is ON, the Icebox requests its IP configuration from the DHCP server—otherwise, you
must modify these settings from the Hosts Administration tab or directly from the Icebox.
3. After making changes to the configuration, click Apply to save changes or click Close to abort this action.
Clusterworx System Administrator’s Guide
73

Icebox Administration
Add an Icebox
74
SNMP SUBTAB
The Configuration SNMP subtab allows you to view or modify Icebox SNMP settings. The Simple Network
Management Protocol (SNMP) allows you to monitor and control all managed devices through a common
interface. The protocol consists of Get, Set, and Trap operations on the Management Information Base (MIB).
The MIB is a tree-shaped information structure that defines what sort of data can be manipulated via SNMP.
1. To modify SNMP settings or traps, click the respective checkbox to enable or disable each item.
2. Click Apply to save changes to these settings or click Cancel to abort this action.
Clusterworx System Administrator’s Guide

FILTERS SUBTAB
Icebox Administration
Add an Icebox
The Configuration Filters subtab allows you to set the Icebox filter settings. IP filtering allows you to grant or
deny an IP address (or range of addresses) access to a particular service on the Icebox. By default,
Clusterworx provides all connections with access to any available services.
1. To modify the Filter Policy, click the pull-down menu and select Deny or Allow filtering.
Warning!
Deny applies to all filtering policies. If you select Deny but do not apply any rules, you can accidentally
lock yourself out of your Iceboxes. To regain access, you must connect to the Icebox directly through a
serial cable.
2. To add a filter, click New to launch the Add Filter dialog.
3. Select a filter service—available services include Dport, NIMP, SNMP, SSH, and Telnet.
Clusterworx System Administrator’s Guide
75

Icebox Administration
Add an Icebox
76
4. Enter the IP address of the Icebox.
5. Click the Mask pull-down menu to select the Net Mask.
6. Click OK to save changes to these settings or click Cancel to abort this action.
7. If you are finished configuring the Icebox, click Apply to save these settings or click Close to abort this
action.
Clusterworx System Administrator’s Guide

Power Management
Power Management
Hosts Subtab
The Power Management feature provides you with the ability to remotely reset, power up, power down, and
cycle power on various hosts in the system. The Power Management subtab uses the Host and Icebox views
to examine and modify Icebox power administration.
Hosts Subtab
The Power Management Hosts subtab allows you to control power for each host connected to the Icebox (the
controls in this pane are essentially the same as they are when you connect directly to the Icebox). To modify
hosts associated with Icebox ports, see Hosts on page 25.
Host Controls
To begin using this feature, select a host(s) from the navigation tree (use the Shift and Ctrl keys to select
multiple hosts). A power icon appears for each selected host.
BEACON ON
To identify a specific host in a cluster for troubleshooting purposes, click Beacon On to flash a light from the
host. The host indicator on your screen display flashes red.
Note
When you turn on a beacon for an IPMI-supported host, the beacon will flash for only a few seconds. To
extend the beacon duration, see cwpower on page 204.
Clusterworx System Administrator’s Guide
77

Power Management
Hosts Subtab
78
BEACON OFF
Turn off the beacon.
ON
Turn on power to the host.
Note
If you are unable to power a host on or off, the port may be locked. See the Icebox User’s Guide for
information on port locking.
OFF
Immediately turn off power to the host.
RESET
Send a signal to the motherboard to perform a soft boot of the host.
CYCLE
Turn the power off, then on. This is especially useful for multiple hosts.
Note
The different colors of Icebox ports on your screen signify the following:
Bright green Port is on.
Dark green Port is off.
Red Beacon is flashing.
Grayed out Status unavailable. The host may be connected to an auxiliary port.
SHUTDOWN
Halt all applications and services running on the host and, if the hardware allows, power the host off. If you
have used the /sbin/shutdown command to successfully shut down and reboot hosts at the next power cycle,
you should be safe to enable this option. To enable shutdown, set the shutdown.button.enable option in
HostAdministrationService.profile to true.
Warning!
Using the shutdown option requires that the BIOS is enabled to support boot at power up—the default
behavior for LinuxBIOS. This setting, also referred to as Power State Control or Power On Boot, is
typically enabled for most server-type motherboards.
If you do not enable this BIOS setting, hosts that are shut down may become unusable until you press the
power button on each host. For the location of your host power switch, please consult your host
installation documentation.
Note
The power connection to the host remains active unless you click Off.
Clusterworx System Administrator’s Guide

Tip
To return the host to normal operational status, cycle the power.
REBOOT
Shuts down and restarts all applications and services on the host.
Power Management
Hosts Subtab
Clusterworx System Administrator’s Guide
79

Power Management
Iceboxes Subtab
80
Iceboxes Subtab
The Power Management Iceboxes subtab allows you to control power for each port on the Icebox (the
controls in this pane are essentially the same as they are when you connect directly to the Icebox). To begin
using this feature, select an Icebox from the navigation tree. A power icon appears for each port on the
Icebox.
BEACON ON
To identify a host connected to a particular port on the Icebox, select the port and click Beacon On. The host
flashes a beacon light and the port indicator on screen flashes red.
Note
The beacon function works only if the hardware installed in your cluster supports Icecards. Hosts
without Icecards do not support beacons.
BEACON OFF
Turn off the beacon.
ON
Turn on power to the host.
OFF
Turn off power to the host.
Clusterworx System Administrator’s Guide

RESET
Send a signal to the motherboard to perform a soft boot of the host.
CYCLE
Turn the power off, then on. This is especially useful for multiple hosts.
Note
The different colors of Icebox ports on your screen signify the following:
Bright green Port is on.
Dark green Port is off.
Red Beacon is flashing.
Grayed out Status unavailable.
Power Management
Iceboxes Subtab
Clusterworx System Administrator’s Guide
81

Power Management
Iceboxes Subtab
82
Clusterworx System Administrator’s Guide

Chapter 7
Imaging
Overview
Clusterworx version-controlled image management allows you to create and store images that can be used to
install and configure hosts in your system. An image may contain file system information, utilities used for
provisioning, one payload, and one kernel—although you may create and store many payloads and kernels.
The payload contains the operating system, applications, libraries, configuration files, locale and time zone
settings, file system structure, selected local user and group accounts (managed by Clusterworx), and any
centralized user authentication settings to install on each host (e.g., NIS, LDAP, and Kerberos). The kernel is
the Linux kernel.
Note
For a list of Clusterworx-supported operating systems, see Operating System Requirements on page 2.
+
=
Payload
Kernel
Image
Stored
payloads
Stored
kernels
Image
This chapter provides both GUI and command-line interface directions to assist you in building and
configuring an image. The image configuration process allows you to select a kernel and payload, and also
configures the boot utilities and partition layout. Once the new image is complete, you can use provisioning
to apply the image to the host(s). See Provisioning on page 153.
Clusterworx System Administrator’s Guide
83

Payload Management
Linux Distributions
84
Payload Management
Payloads are stored versions of the operating system and any applications installed on the hosts. Payloads are
compressed and transferred to the hosts via multicast during the provisioning process.
Linux Distributions
Before you can begin working with payloads, you must first ensure that your Linux distribution is installed
and available for use:
Red Hat Installations
1. Mount disk 1 and copy the contents of the entire disk to a location on the hard drive:
mount /mnt/cdrom
or
mount -o loop RHEL4-x86_64-WS-disc1.iso /mnt/cdrom
mkdir /mnt/redhat
cp -r /mnt/cdrom/* /mnt/redhat
2. Mount disk 2 and copy the *.rpm files from the RPMS directory to the RPMS directory on the hard drive:
cp /mnt/cdrom/RedHat/RPMS/*.rpm /mnt/redhat/RedHat/RPMS
3. Repeat this process with all other binary CD-ROMs.
SuSE Linux Enterprise Server Installations
1. Mount disk 1 and copy the contents of the entire disk to a location on the hard drive:
mount /media/cdrom
or
mount -o loop SLES-9-x86-64-CD1.iso /media/cdrom
mkdir /mnt/suse
cp -r /media/cdrom/* /mnt/suse
2. Mount disk 2 and copy the SuSE directory that contains the RPMs to the SuSE directory on the hard
drive:
cp -r /media/cdrom/suse/* /mnt/suse/suse
3. Repeat this process with all other binary CD-ROMs.
Clusterworx System Administrator’s Guide

Create a Payload
Payload Management
Create a Payload
Payloads are initially created using a supported Linux distribution installation media (CD-ROM, FTP, NFS) to
build a base payload (see Operating System Requirements on page 2 for a list of supported distributions) or by
importing a payload from a previously provisioned host. Additions and changes are applied by adding or
removing packages, or by editing files through the GUI or CLI. Changes to the Payload are managed by the
Clusterworx Version Control System (VCS). Package information and files are stored and may be browsed
through Clusterworx.
Warning!
Please consult Linux Networx before upgrading your Linux distribution or kernel. Upgrading to a
distribution or kernel not approved for use on your system may render Clusterworx inoperable or
otherwise impair system functionality. Technical Support is not provided for unapproved system
configurations.
To Create a New Payload
To create a new payload from a Linux distribution, do the following:
1. Select the Imaging tab.
2. Select New Payload from the File menu or right-click on the Payloads entry in the navigation tree and
select New Payload. A new payload pane appears.
Note
To create a new payload from an existing host, see To Create a Payload from an Existing Host on page 90.
Clusterworx System Administrator’s Guide
85

Payload Management
Create a Payload
86
3. Enter the name of the new payload in the Name field.
4. (Optional) Enter a description of the new payload in the Description field.
5. Click select to display the Package Source dialog.
6. Select the Scheme desired.
7. Enter the Location of the top level directory for the Linux distribution or, if the File scheme is selected,
click Browse to locate the directory.
Tip
If you are creating multiple payloads from the same distribution source, it may be faster and easier to
copy the distribution onto the hard drive. This also prevents you from having to switch CD-ROMs during
the payload creation process. See Red Hat Installations on page 84 and SuSE Linux Enterprise Server
Installations on page 84 for specific details on installing these distributions.
8. (Optional) Enter a Host (only if the selected scheme is http:// or ftp://).
9. (Optional) Enter Username and Password (only if you selected Use Authentication).
10. Click OK to continue or click Cancel to abort this action.
Clusterworx System Administrator’s Guide

Payload Management
Create a Payload
11. As the distribution loads, the Task Progress dialog appears. This dialog displays the status of the payload
and identifies any errors that occur during the load process.
Tip
Select Hide on Completion to close the Task Progress dialog if no errors or warnings occur.
Note
If Clusterworx is unable to detect payload attributes, the Distribution Unknown dialog appears. From this
dialog, select the distribution type that most closely resembles your distribution and Clusterworx will
attempt to create your payload.
12. (Optional) Modify the Architecture field.
13. (Optional) Set the Locale and Time Zone.
14. Click the Packages subtab.
Clusterworx System Administrator’s Guide
87

Payload Management
Create a Payload
88
15. (Optional) Click Add. The Select Categories dialog appears.
16. Select which payload categories to install or remove by clicking the checkbox next to the package.
Note
When you select a “core” category to include in a payload, Clusterworx automatically selects packages
that are essential in allowing the capability to run. However, you may include additional packages at any
time. See Add a Package to an Existing Payload on page 92.
17. Click OK to continue or click Cancel to abort this action.
Clusterworx System Administrator’s Guide

Payload Management
Create a Payload
18. Click Apply to save changes and build the payload. Click Revert or Close to abort this action. The payload
progress dialog appears.
Tip
If an RPM installation error occurs during the payload creation process, Clusterworx enables the Details
button and allows you to view which RPM produced the error.
To view error information about a failed command, click the command description field. You may copy
the contents of this field and run it from the CLI to view specific details about the error.
19. Click Check In to import the new payload into VCS. See also Version Control System (VCS) on page 144.
20. (Optional) Select the Authentication subtab to add configurations for centralized authentication services.
See Payload Authentication Management on page 98 for more information.
Clusterworx System Administrator’s Guide
89

Payload Management
Create a Payload
90
To Create a Copy of an Existing Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree, then right-click on the payload and select Copy.
Tip
You may also open a payload for editing, then click the Copy button.
3. Clusterworx prompts you for the name of the new payload.
4. Enter the name of the new payload and click OK. Click Cancel to abort this action.
To Create a Payload from an Existing Host
Creating a payload from an existing host is helpful in situations where a specific host is already configured
the way you want it. This feature allows you to create new payloads that use the configuration and distribute
the image to other hosts.
Note
On RHEL4, temporarily disable SE Linux while importing the payload. If you do not require SE Linux,
you may want to leave it disabled.
To disable SE Linux:
1. Navigate to the Imaging tab.
2. Select the kernel you are using and edit the kernel parameters.
3. Add selinux=0 as a parameter.
4. Reboot the host and import the payload.
1. Select the Imaging tab.
2. Click Import Payload from the File menu. The Create Payload from Existing Installation dialog appears.
3. Enter the name of the host to use to create a payload or select a host from the pull-down menu.
4. Enter a name for the payload in the Name field.
Clusterworx System Administrator’s Guide

5. (Optional) Enter a description of the payload in the Description field.
Payload Management
Create a Payload
6. (Optional) Review the Excluded Files list and remove any files you want to include in the payload (use the
Shift or Ctrl keys to select multiple files).
Warning!
If you include a symlink when creating a payload, excluding the target produces a dangling symbolic link.
This link may cause an exception and abort payload creation when Clusterworx attempts to repair
missing directories.
7. (Optional) Enter the location of any file you want to exclude from the payload and click Add. Click
Browse to locate a file on your system.
8. Click OK to create the payload or click Cancel to abort this action.
Clusterworx System Administrator’s Guide
91

Payload Management
Add a Package to an Existing Payload
92
Add a Package to an Existing Payload
Adding a package to a payload allows you to make additions or changes to the default Linux installation. For
a list of supported distributions, see Operating System Requirements on page 2.
To Add a Package to an Existing Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Click the Packages subtab.
5. Click Add. The Package Source dialog appears.
6. Select the Scheme desired.
7. Enter the Location of the top level directory for the Linux distribution, a directory containing RPM
packages, or the location of an individual package. If you selected the File scheme, click Browse to locate
the package.
Note
If the browse button does not launch a dialog, a DNS name resolution error may exist. The DNSresolvable
server name must be specified in the client—not the IP address.
If you have several packages in a directory, select the directory. Clusterworx displays all packages in the
directory—from here, you can choose which packages you want to install (see page 93). Clusterworx
resolves package dependencies (see Payload Package Dependency Checks on page 96)
8. (Optional) Enter a Host (only if the selected scheme is http:// or ftp://).
9. (Optional) Enter Username and Password (only if you selected Use Authentication).
10. Click OK to continue (or click Cancel to abort this action and return to the Payload pane).
Clusterworx System Administrator’s Guide

11. The Select Packages dialog appears.
12. Select which package(s) to install by clicking the checkbox next to the package.
13. Click OK to continue or click Cancel to abort this action.
14. Click Apply to save changes. Click Revert or Close to abort this action.
Note
Payload Management
Add a Package to an Existing Payload
Before adding the package, Clusterworx performs a package dependency check. See Payload Package
Dependency Checks on page 96 for information about dependency errors.
15. Click Check In to check the payload into VCS.
16. Update the image to use the new payload
17. Re-provision the hosts with the new image.
Clusterworx System Administrator’s Guide
93

Payload Management
Remove a Payload Package
94
Remove a Payload Package
The Packages subtab provides a view into the current packages installed in the payload. See also Payload
Package Dependency Checks on page 96.
To Remove a Payload Package
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Click the Packages subtab.
5. From the package list, select a package group(s) or expand the group to view individual packages. To
select multiple items, use the Shift or Ctrl keys.
Tip
To view individual packages instead of package groups, change the View Packages By option.
6. Click Delete.
Clusterworx System Administrator’s Guide

7. Clusterworx asks you to confirm your action.
8. Click OK to remove the package(s) or click Cancel to abort this action.
9. Click Apply to save changes. Click Revert or Close to abort this action.
Note
Payload Management
Remove a Payload Package
Before adding the package, Clusterworx performs a package dependency check. See Payload Package
Dependency Checks on page 96 for information about dependency errors.
Clusterworx System Administrator’s Guide
95

Payload Management
Remove a Payload Package
96
Payload Package Dependency Checks
Before performing package addition, update, or removal, Clusterworx performs a package dependency
check. Any failures identified through the dependency check are displayed in the Resolve Dependency
Failures dialog. From this dialog, you can choose a course of action to address the failure(s).
ADDING A PACKAGE
When adding a package, you may correct dependency failures by selecting one of the following options:
Add packages needed to resolve dependency failures.
Ignore packages that have dependency failures.
Force package installation, ignoring dependency failures.
Clusterworx System Administrator’s Guide

REMOVING A PACKAGE
Payload Management
Remove a Payload Package
When removing a package, you may correct dependency failures by selecting one of the following options:
Ignore packages that have dependency failures.
Force package deletion, ignoring dependency failures.
Clusterworx System Administrator’s Guide
97

Payload Management
Payload Authentication Management
98
Payload Authentication Management
The Payload Authentication subtab manages the authentication settings for the payload. This tab allows you
to enable, disable, or modify the settings for supported remote authentication schemes. Clusterworx supports
the following remote authentication schemes:
Network Information Service (NIS)
Lightweight Directory Access Protocol (LDAP)
Kerberos (a network authentication protocol)
To Configure NIS Authentication
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Authentication subtab.
5. Select the NIS tab.
6. Click the Use NIS option.
7. Enter the NIS domain.
8. (Optional) Enter the NIS Server.
9. Click Apply to save changes. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide

To Configure LDAP Authentication
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
Payload Management
Payload Authentication Management
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Authentication subtab.
5. Select the LDAP tab.
6. Click the Use LDAP option.
7. Enter the LDAP Base DN (Distinguished Name).
8. Enter the LDAP Server.
9. (Optional) Click Use SSL connections if you want to connect to the LDAP server via SSL.
10. Click Apply to save changes. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide
99

Payload Management
Payload Authentication Management
100
To Configure Kerberos Authentication
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Authentication subtab.
5. Select the Kerberos tab.
6. Click the Use Kerberos option.
7. Enter the Kerberos Realm.
8. Enter the Kerberos KDC (Key Distribution Center).
9. Enter the Kerberos Server.
10. Click Apply to save changes. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide

Payload Local User and Group Account Management
Payload Management
Payload Local User and Group Account Management
The Local Accounts payload management tab provides a means for managing local accounts in payloads.
This tab allows you to:
Add a local user or group account known to Clusterworx to the payload (see User Administration on
page 49).
Delete a local user or group account from the payload.
Note
Local account management does not support moving local accounts from the host.
Local user and group accounts that are reserved for system use do not display and cannot be added or
deleted. The root account is added automatically. Clusterworx handles group dependencies.
Tip
Software that requires you to add groups (e.g., Myrinet Group) can be managed through user accounts.
Add a Local User Account to a Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Local Accounts subtab.
5. Select the Users tab.
Clusterworx System Administrator’s Guide
101

Payload Management
Payload Local User and Group Account Management
102
6. Click Add. The Add User dialog appears.
7. Select the user(s) to add to the payload (use the Shift or Ctrl keys to select multiple users).
8. Click OK to add the user(s) or click Cancel to abort this action.
9. Click Apply to complete the process. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide

Delete a Local User Account from a Payload
1. Select the Imaging tab.
2. Select a payload in the navigation tree.
Payload Management
Payload Local User and Group Account Management
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Local Accounts subtab.
5. Select the Users tab.
6. Select the user(s) to remove from the payload (use the Shift or Ctrl keys to select multiple users).
7. Click Delete to remove the user(s).
8. Click Apply to complete the process. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide
103

Payload Management
Payload Local User and Group Account Management
104
Add a Group User Account to a Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Local Accounts subtab.
5. Select the Groups tab.
6. Click Add. The Add Group dialog appears.
7. Select the group(s) to add to the payload (use the Shift or Ctrl keys to select multiple users).
8. Click OK to add the group(s) or click Cancel to abort this action.
9. Click Apply to complete the process. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide

Delete a Group User Account from a Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
Payload Management
Payload Local User and Group Account Management
3. Select Edit from the Edit menu or right-click on the payload in navigation tree and select Edit.
4. Select the Local Accounts subtab.
5. Select the Groups tab.
6. Select the group(s) to remove from the payload (use the Shift or Ctrl keys to select multiple groups).
7. Click Delete to remove the group(s).
8. Click Apply to complete the process. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide
105

Payload Management
Payload File Configuration
106
Payload File Configuration
The Configuration tab allows you to set up configuration options when creating or editing a payload
including DHCP Network, Network, Serial Console, Virtual Console, and more. When you click Apply, the
scripts that correspond to the selected item(s) run on the payload. It is important to note that the selected
script(s) run at the time you click Apply—this list is not an indication of scripts that have run at some point on
the system.
Note
The list of options available is based on the distribution selected. The options displayed in the example
below are SuSE-based distributions (SuSE Linux Enterprise Server 9).
To Configure a Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload in the navigation tree and select Edit.
4. Select the Configuration subtab
5. Click the check box by each option you want to configure.
6. Click Apply to complete the configuration. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide

Edit a Payload File with the Text Editor
Payload Management
Edit a Payload File with the Text Editor
Clusterworx allows you to edit payload files with a text editor. Files edited in this manner are treated as plain
text and only basic editing tools such as insert, cut, and paste are available.
To Edit a Payload File with the Text Editor
1. Select the Imaging Tab.
2. Select and load a payload from the navigation tree.
3. Select Edit file from the Edit menu. The Remote File Chooser appears.
4. Select the file to edit and click Open. The text editor window appears.
5. Edit the file as necessary, then click OK to save changes or click Cancel to abort this action.
6. Click Apply to complete the configuration. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide
107

Payload Management
Add and Update Payload Files or Directories
108
Add and Update Payload Files or Directories
Adding and updating payload files allows you to select a file or directory from the local file system and copy it
into the payload.
To Add or Update a Payload File or Directory
1. Select the Imaging Tab.
2. Select a payload from the navigation tree.
3. Select Edit from the Edit menu or right-click on the payload and select Edit.
4. Select Add File from the Edit menu. The Add File or Directory dialog appears.
5. Enter the source for the new file in the Source field or click Browse to locate the source.
6. Enter the destination for the new file in the Destination field or click Browse to select the destination.
Note
The destination specified is relative to the payload root.
7. Click OK to save changes or click Cancel to abort this action.
8. Click Apply to complete the process. Click Revert or Close to abort this action.
Tip
If a working copy of a payload is available, you can enter the payload directory and make changes to the
payload manually from the CLI. Working copies of payloads are stored at:
/opt/cwx/imaging//payloads/
From this directory, enter chroot to change the directory to your root (/) directory. After making changes,
check the payload into VCS.
Clusterworx System Administrator’s Guide

Delete Payload Files
Deleting a payload file allows you to exclude a specific file(s) from a payload.
To Delete a File from a Payload
1. Select the Imaging Tab.
2. Select a payload from the navigation tree.
3. Select Delete File(s) from the Edit menu. The Remote File Chooser appears.
Payload Management
Delete Payload Files
4. Select the file(s) you want to remove, then click Delete to remove the files or Cancel to abort this action.
5. Click Apply to complete the process. Click Revert or Close to abort this action.
Delete a Payload
To Delete a Working Copy of a Payload
1. Select the Imaging tab.
2. Select a payload from the navigation tree.
3. Select Delete from the File menu or right-click on the payload in the navigation tree and select Delete.
Tip
Once you check the payload into VCS, you may remove the directory from within your working user
directory (e.g., to save space):
/opt/cwx/imaging///
To verify that your changes were checked in, use the VCS status option. See Version Control System
(VCS) on page 144 for details on using the version control system.
Clusterworx System Administrator’s Guide
109

Payload Management
Install Clusterworx into the Payload
110
Install Clusterworx into the Payload
When working with payloads, Clusterworx requires that each payload contain some basic Clusterworx
services. These services allow Clusterworx to control various parts of the system, including instrumentation
services.
Warning!
Installing a Clusterworx payload in a RedHat Enterprise Linux 3 update 3 or 4 environment produces an
out-of-memory error. To correct this issue, you must install the prefinalize script contained in the /misc
directory. See To Install the Clusterworx Prefinalize Script on page 143.
To Install Clusterworx into the Payload
1. Access the payload’s root directory:
cd/opt/cwx/imaging//payloads/
2. Run the install script from the Clusterworx Installation CD (e.g., /mnt/cdrom/install.sh).
3. Select the Payload option.
4. Enter the name of the Clusterworx Server.
Note
The Clusterworx Server must be a valid host name that is resolvable through name resolution (i.e., DNS,
/etc/hosts).
Clusterworx System Administrator’s Guide

5. Enter the installation directory (e.g., /opt/cwx).
6. Click Next.
Tip
Payload Management
If the hosts will communicate with one another, you may prefer to use host names (e.g., n1, n2, n3) rather
than IP addresses (i.e., 192.168.0.1, 192.168.0.2, 192.168.0.3). Computers use “name resolution” to convert
between numbers and names—most commonly through a local /etc/hosts file or with a Domain Name
Service (DNS).
For typical Clusterworx users, the local /etc/hosts file already exists on the Master Host. To make this file
available to all hosts, copy the file into the payload (or simply edit the file in the payload). If you need to
create this file, use the dbx command to create an /etc/hosts formatted list of the hosts in your cluster. To
save this list, redirect the output to a file:
dbx -f:hosts
Clusterworx System Administrator’s Guide
111

Kernel Management
Create a Kernel
112
Kernel Management
Kernels may be customized for particular applications and used on specific hosts to achieve optimal system
performance. Clusterworx uses VCS to help you manage kernels used on your system.
Create a Kernel
The following sections review the steps necessary to create a kernel for use in provisioning your cluster.
To Create a Kernel Using an Existing Binary
Note
For information on building a new kernel from source, see To Build a New Kernel from Source on
page 114.
1. Select the Imaging tab.
2. Select New Kernel from the File menu or right-click on the Kernels entry in the navigation tree and
select New Kernel. A new kernel pane appears.
3. Enter the name of the Kernel.
4. (Optional) Enter a description of the kernel.
5. Select the hardware architecture.
Clusterworx System Administrator’s Guide

6. Enter the location of the kernel binary or click Browse to open the Remote File Chooser.
Kernel Management
Create a Kernel
7. Specify the location of the modules directory (e.g., /lib/modules) or click Browse to open the Remote File
Chooser.
8. Click Apply to create the kernel. Click Revert or Close to abort this action.
9. (Optional) Click Check In to import the kernel into VCS.
10. Click Close.
Clusterworx System Administrator’s Guide
113

Kernel Management
Create a Kernel
114
To Create a Copy of an Existing Kernel
1. Select the Imaging tab.
2. Select a kernel from the navigation tree, then right-click on the payload and select Copy.
Tip
You may also open a kernel for editing, then click the Copy button.
3. Clusterworx prompts you for the name of the new kernel.
4. Enter the name of the new kernel and click OK. Click Cancel to abort this action.
To Build a New Kernel from Source
If you want to use a stock vendor kernel already loaded on your system, see To Create a Kernel Using an
Existing Binary on page 112. Otherwise, use the following procedure to build a new kernel from source:
Warning!
Please consult Linux Networx before upgrading your Linux distribution or kernel. Upgrading to a
distribution or kernel not approved for use on your system may render Clusterworx inoperable or
otherwise impair system functionality. Technical Support is not provided for unapproved system
configurations.
1. Obtain and install the kernel source RPM for your distribution from your distribution CD-ROMs or distribution
vendor. This places the kernel source code under /usr/src, typically in a directory named
linux-2..- (if building a Red Hat Enterprise Linux 4 kernel, Clusterworx places
the source code into /usr/src/kernels/2..-).
Tip
Because you don’t need the kernel source RPM in your payload, install the RPM on the host.
2. If present, review the README file inside the kernel source for instructions on how to build and
configure the kernel.
Note
It is highly recommended the you use, or at least base your configuration on one of the vendor’s standard
kernel configurations.
Clusterworx System Administrator’s Guide

Kernel Management
Create a Kernel
3. Typically, a standard configuration file is installed in the /boot directory, usually as
config-2..-. You may also use a stock configuration file installed as .config in
the kernel source directory or available in a sub-directory (typically /configs) of the kernel source
directory.
Tip
To use a stock configuration, copy it to the kernel source directory and run make oldconfig.
4. Build the kernel and its modules using the make bzImage && make modules command. If your
distribution uses the Linux 2.4 kernel, use make dep && make bzImage && make modules but DO NOT
install the kernel.
5. Open Clusterworx.
6. Select the Imaging tab.
7. Select Source Kernel from the File menu.
8. Enter the name of the Kernel.
9. (Optional) Enter a description of the kernel.
10. Select the hardware architecture.
Clusterworx System Administrator’s Guide
115

Kernel Management
Create a Kernel
116
11. Enter the location of the kernel source (i.e., where you unpacked the kernel source) or click Browse to
open the Remote File Chooser. By default, kernel source files are located in /usr/src.
12. (Optional) Enter the binary path of the kernel (e.g., arch/i386/boot/bzImage).
13. Click Apply to complete the process. Click Revert or Close to abort this action.
14. Click Check In to import the new kernel into VCS.
Clusterworx System Administrator’s Guide

Edit a Kernel
To Edit a Kernel
1. Select the Imaging tab.
2. Select a kernel from the navigation tree.
3. Select Edit from the Edit menu or right-click on the kernel in the navigation tree and select Edit.
4. (Optional) Edit the kernel’s description in the Description field.
5. (Optional) Edit the Parameters field.
Kernel Management
Edit a Kernel
6. (Optional) Click Update to update a kernel that has been recompiled for some reason (e.g., a change in
kernel configuration). Clusterworx updates the kernel based on the Source Directory and Binary Path
used when you created the kernel. See To Create a Kernel Using an Existing Binary on page 112.
7. (Optional) Click Properties to view the “.config” and “System.map” files for the kernel (if they existed
when you imported the kernel).
8. (Optional) Click Add to include new modules in this kernel. You may select modules individually (files
ending in *.o) or you can add a directory and allow Clusterworx to automatically select all modules and
directories recursively. See also Modules Subtab on page 118.
9. (Optional) Select modules to remove from the kernel and click Delete.
10. Click Apply to complete the process. Click Revert or Close to abort this action.
11. Click Check In to commit changes to the kernel into VCS.
Clusterworx System Administrator’s Guide
117

Kernel Management
Edit a Kernel
118
MODULES SUBTAB
Many provisioning systems use a basic kernel to boot and provision the host, then reboot with an optimized
kernel that will run on the host. Clusterworx requires only a single kernel to boot and run; however, you
must compile any additional functionality into the kernel (i.e., monolithic) or add loadable kernel modules to
the kernel (i.e., modular). Clusterworx loads the modules during the provisioning process.
Note
If you encounter problems when provisioning hosts on your cluster, check to see that you compiled your
kernel correctly. If you compiled a modular kernel, you must include ethernet or file system modules
before the host can provision properly. Use the Icebox serial console to watch the host boot.
Tip
In some cases, it may be necessary to install kernel modules on a host during the provisioning process,
but not load them at boot time. Because an image ties a kernel and payload together, modules can be
copied to the host by adding them to an image rather than adding them to a payload.
To add modules to an image, run mkdir -p ramdisk/lib/modules from the images directory. For example,
if you were running as root and your image name were ComputeHost:
cd /opt/cwx/imaging/root/images/ComputeHost
mkdir -p ramdisk/lib/modules//kernel/
mkdir -p ramdisk/lib/modules//kernel/net/e1000
Then copy the modules you want to an appropriate subdirectory of the modules directory:
cp /usr/src/linux/drivers/net/e1000/e1000.o
ramdisk/lib/modules//kernel/net
ramdisk/lib/modules//kernel/net/e1000/
You may wish to look at your local /lib/modules directory if you have questions about the directory
structure. During the boot process, the kernel automatically loads the modules that were selected in the
kernel configuration screen. The additional modules will be copied to the host during the finalize stage.
This method keeps the payload independent from the kernel and allows you to load the modules after the
host boots.
Clusterworx System Administrator’s Guide

Delete a Kernel from VCS
To Delete a Working Copy of a Kernel
1. Select the Imaging tab.
2. Select a kernel from the navigation tree.
Kernel Management
Delete a Kernel from VCS
3. Select Delete from the File menu or right-click on the kernel in the navigation tree and select Delete.
Note
Before you delete the working copy of your kernel, use the VCS status option to verify that the kernel is
checked in. See Version Control System (VCS) on page 144 for details on using version control.
Tip
Once you check the kernel into VCS, you may delete the working copy of the kernel from your working
directory (e.g., to save space).
/opt/cwx/imaging///
Clusterworx System Administrator’s Guide
119

Image Management
Create an Image
120
Image Management
Images contain exactly one payload and one kernel, and allow you to implement tailored configurations on
various hosts throughout the cluster.
Warning!
Please consult Linux Networx before upgrading your Linux distribution or kernel. Upgrading to a
distribution or kernel not approved for use on your system may render Clusterworx inoperable or
otherwise impair system functionality. Technical Support is not provided for unapproved system
configurations.
Create an Image
To Create an Image
1. Select the Imaging tab.
2. Select New Image from the File menu or right-click on the Images entry in the navigation tree and select
New Image. A New Image pane appears.
3. Enter the name of the new image in the Name field.
4. (Optional) Enter a description of the new image in the Description field.
5. Define a Kernel by clicking Browse. To install additional kernel modules that do not load at boot time,
see Modules Subtab on page 118.
Clusterworx System Administrator’s Guide

6. Define a Payload by clicking Browse.
7. Define the partition scheme used for the compute hosts—the partition scheme must include a root (/)
partition. See To Create a Partition for an Image on page 124.
Note
Kernel support for selected file systems must be included in the selected kernel (or as modules).
Image Management
Create an Image
8. (Optional) Click the Advanced button to display the Advanced Options dialog. This dialog allows you to
configure partitioning behavior and payload download settings (see Advanced Imaging Options on
page 121).
9. (Optional) Implement RAID. See Managing Partitions on page 124.
10. (Optional) If you need to make modifications to the way hosts boot during the provisioning process,
select the RAM Disk tab. See RAM Disk on page 138.
11. Click Apply to complete the process. Click Revert or Close to abort this action.
Advanced Imaging Options
The Advanced Options dialog allows you to configure partitioning behavior and payload download settings.
These settings are persistent, but may be overridden from the Advanced Provisioning Options dialog. See
Advanced Provisioning Options on page 156.
PARTITIONING BEHAVIOR
This option allows you to configure the partition settings used when provisioning a host. You may
automatically partition a host if the partitioning scheme changes, always re-create all partitions (including
those that are exempt from being overwritten), or choose to never partition the host. see Managing Partitions
on page 124.
Clusterworx System Administrator’s Guide
121

Image Management
Create an Image
122
PAYLOAD DOWNLOAD
The payload options allow you to automatically download a payload if a newer version is available (or if the
current payload is not identical to that contained in the image), always download the payload, or choose to
never download a payload.
boot.profile
Clusterworx generates the file, boot.profile, each time you save an image (overwriting the previous file in
/etc/boot.profile). The boot profile contains information about the image and is required for the boot process
to function properly. You may configure the following temporary parameters:
dmesg.level The verbosity level (1-8) of the kernel—1 (the default) is the least verbose and 8 is
the most.
partition Configure the hard drive re-partitioning status (Automatic, Always, Never). By
default, Automatic.
partition.once Override the current drive re-partitioning status (Default, On, Off). By default,
Default.
image Configure the image download behavior (Automatic, Always, Never). By default,
Automatic. Always and Never will download the image even if it is up-to-date.
image.once Override the current image download behavior (Default, On, Off). By default,
Default. To view the current download behavior, see Advanced Imaging Options
on page 121.
image.path Specifies where to store the downloaded image. By default, /mnt.
To change the configuration of one of these parameters, add the parameter (e.g., dmesg.level: 7) to the
boot.profile and provision using that image. You may also configure most of these values from the GUI. See
Selecting an Image on page 154.
Note
Changes made to image settings remain in effect until the next time you save the image.
To Create a Copy of an Existing Image
1. Select the Imaging tab.
2. Select an image from the navigation tree, then right-click on the image and select Copy.
Tip
You may also open an image for editing, then click the Copy button.
3. Clusterworx prompts you for the name of the new image.
4. Enter the name of the new image and click OK. Click Cancel to abort this action.
Clusterworx System Administrator’s Guide

Delete an Image from VCS
To Delete a Working Copy of an Image
1. Select the Imaging tab.
Image Management
Delete an Image from VCS
2. Select the image you want to delete from the navigation tree. To select multiple images, use the Shift or
Ctrl keys.
3. Select Delete from the File menu or right-click on the image(s) in the navigation tree and select Delete.
Tip
Once you check the image into VCS, you may remove the directory from within your working user
directory (e.g., to save space).
/opt/cwx/imaging///
To verify that your changes were checked in, use the VCS status option. See Version Control System
(VCS) on page 144 for details on using version control.
Clusterworx System Administrator’s Guide
123

Image Management
Managing Partitions
124
Managing Partitions
To Create a Partition for an Image
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Select the Partitions subtab.
Clusterworx System Administrator’s Guide

5. Click Add. The New Partition dialog appears.
Image Management
Managing Partitions
6. Select a file system type from the Filesystem pull-down menu. To create a diskless host, see Diskless
Hosts on page 135.
7. Enter the device on which to add the partition or select a device from the pull-down menu. Supported
devices include the following, but the most common is /dev/hda because hosts typically have only one
disk and use IDE:
/dev/hda—Primary IDE Disk
/dev/hdb—Secondary IDE Disk
/dev/sda—Primary SCSI Disk
/dev/sdb—Secondary SCSI Disk
8. Enter a Mount Point or select one from the pull-down menu.
9. (Optional) Enter the fstab options. The /etc/fstab file controls where directories are mounted and,
because Clusterworx writes and manages the fstab on the hosts, any changes made on the hosts are
overwritten during provisioning.
10. (Optional) Enter the mkfs options to use when creating the file system (i.e., file size limits, symlinks,
journaling). For example, to change the default block size for ext3 to 4096, enter -b 4096 in the mkfs
options field.
11. (Optional) If creating an NFS mount, enter the NFS host.
12. (Optional) If creating an NFS mount, enter the NFS share.
13. (Optional) Uncheck the Format option to make the partition exempt from being overwritten or formatted
when you provision the host. This may be overridden by the Force Partitioning option or from the
boot.profile (see Selecting an Image on page 154 and boot.profile on page 122).
Note
After partitioning the hard disk(s) on a host for the first time, you can make a partition on the disk
exempt from being overwritten or formatted when you provision the host. However, deciding not to
Clusterworx System Administrator’s Guide
125

Image Management
Managing Partitions
126
format the partition may have an adverse affect on future payloads—some files may remain from
previous payloads. This option is not allowed if the partition sizes change when you provision the host.
14. Select the partition size:
Fixed size allows you to define the size of the partition (in MBs).
Fill to end of disk allows you to create a partition that uses any space that remains after defining partitions
with fixed sizes.
Tip
It is wise to allocate slightly more memory than is required on some partitions. To estimate the amount of
memory needed by a partition, use the du -hc command.
15. Click Apply to save changes or click Cancel to abort this action.
16. (Optional) Click Check In to import the image into VCS.
17. Click Apply to complete the process. Click Revert or Close to abort this action.
Note
Clusterworx generates the file, boot.profile, each time you save an image. For a description of the
information contained in this file, see boot.profile on page 122.
Clusterworx System Administrator’s Guide

RAID Partitions
To Create a RAID Partition
When adding a RAID partition, the host typically requires two disks and at least two previously created
software RAID partitions (one per disk).
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Select the Partitions subtab.
Image Management
RAID Partitions
5. Click Add to create the appropriate number of software RAID partitions for the RAID you are creating.
See To Create a Partition for an Image on page 124.
Note
The RAID button is disabled until you create at least two RAID partitions.
Clusterworx System Administrator’s Guide
127

Image Management
RAID Partitions
128
6. Click the RAID button to assign the partitions a file system, mount point, and RAID level. The Add RAID
dialogue appears.
7. Select a file system type from the Filesystem pull-down menu.
8. Enter a Mount point or select one from the pull-down menu.
9. Select a RAID level from the RAID Level pull-down menu. This level affects the size of the resulting RAID
and the number of RAID partitions required to create it (e.g., RAID0 and RAID1 require 2 RAID
partitions, RAID5 requires 3 RAID partitions).
10. (Optional) Enter the fstab options. The /etc/fstab file controls where directories are mounted and,
because Clusterworx writes and manages the fstab on the hosts, any changes made on the hosts are
overwritten during provisioning.
11. (Optional) Enter the mkfs options to use when creating the file system (i.e., file size limits, symlinks,
journaling). For example, to change the default block size for ext3 to 4096, enter -b 4096 in the mkfs field.
12. From the RAID Members list, select the currently unused RAID partitions to include in this RAID.
13. Click Ok to save changes or click Cancel to abort this action.
14. Click Apply to complete the process. Click Revert or Close to abort this action.
Clusterworx System Administrator’s Guide

Edit a Partition
To Edit a Partition on an Image
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Select the Partitions subtab.
5. Select the partition you want to edit from the list.
Image Management
Edit a Partition
Clusterworx System Administrator’s Guide
129

Image Management
Edit a Partition
130
6. Click Edit. The Edit Partition dialog appears.
7. Make any necessary changes to the partition, then click Apply to accept the changes. Click Cancel to
abort this action.
Clusterworx System Administrator’s Guide

Delete a Partition
To Delete a Partition from an Image
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Select the Partitions subtab.
5. Select the partition you want to delete from the list. To select multiple partitions, use the Shift or Ctrl
keys.
6. Click Delete.
Image Management
Delete a Partition
Clusterworx System Administrator’s Guide
131

Image Management
User-Defined File Systems
132
User-Defined File Systems
Establishing a user-defined file system allows you to create a raw partition that you may format with a file
system not supported by Clusterworx.
To Create a Partition with a User-defined File System
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Select the Partitions subtab.
Clusterworx System Administrator’s Guide

5. Click Add. The New Partition dialog appears.
6. Select User Defined from the Filesystem pull-down menu.
Image Management
User-Defined File Systems
7. Enter the device on which to add the partition or select a device from the pull-down menu. Supported
devices include the following, but the most common is /dev/hda because hosts typically have only one
disk and use IDE:
/dev/hda—Primary IDE Disk
/dev/hdb—Secondary IDE Disk
/dev/sda—Primary SCSI Disk
/dev/sdb—Secondary SCSI Disk
8. Create a plug-in to write the line for /etc/fstab during the boot process. See Plug-ins for the Boot Process
on page 140.
9. Select the partition size:
Fixed partition size allows you to define the size of the partition (in MBs).
Fill to end of disk allows you to create a partition that uses any space that remains after defining partitions
with fixed sizes.
Tip
When working with diskless hosts, it is wise to allocate slightly more memory than is required on some
partitions. To estimate the amount of memory needed by a partition, use the du -hc command.
It is important to note that memory allocated to a partition is not permanently consumed. For example,
consider programs that need to write temporary files in a /tmp partition. Although you may configure the
partition to use a maximum of 50 MB of memory, the actual amount used depends on the contents of the
partition. If the /tmp partition is empty, the amount of memory used is 0 MB.
10. Click Apply to save changes or click Cancel to abort this action.
11. Click Check In to import the image into VCS.
Clusterworx System Administrator’s Guide
133

Image Management
User-Defined File Systems
134
12. Click Apply to complete the process. Click Revert or Close to abort this action.
Note
Clusterworx generates the file, boot.profile, each time you save an image. See boot.profile on page 122 for
a description of the information contained in this file.
Clusterworx System Administrator’s Guide

Diskless Hosts
Image Management
Diskless Hosts
Clusterworx provides support for diskless hosts. For optimal performance, Clusterworx implements diskless
hosts by installing the operating system into the host’s physical memory, generally referred to as RAMfs or
TmpFS. Because the OS is stored in memory, it is recommended that you use a minimal Linux installation to
prevent consuming excess memory. An optimized Linux installation is typically around 100-150MB, but may
be as small as 30MB depending on which libraries are installed. Clusterworx also supports local scratch or
swap space on the hosts.
Note
Potentially large directories like /home should never be stored in RAM. Rather, they should be shared
through a global storage solution.
Warning!
When using diskless hosts, the file system is stored in memory. Changes made to the host’s file system
will be lost when the host reboots. If changes are required, make them in the payload first.
To Configure a Diskless Host
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Select the Partitions subtab.
5. Click Add. The New Partition dialog appears.
6. Select the tmpfs or nfs file system type from the Filesystem pull-down menu.
Clusterworx System Administrator’s Guide
135

Image Management
Diskless Hosts
136
Note
Although diskless hosts may use either tmpfs or nfs partitions, they must use only one type. If you are
converting or editing a diskless host, change all partitions to the same type.
7. Enter the Mount Point or select one from the pull-down menu (diskless hosts use root “/” as the mount
point).
Tip
In most Linux installations, the majority of the OS is stored in the /usr directory. To help conserve
memory, you may elect to share the /usr directory via NFS or another global file system.
8. (Optional) Enter the fstab options. The /etc/fstab file controls where directories are mounted.
Note
Because Clusterworx writes and manages the fstab on the hosts, any changes made on the hosts are
overwritten during provisioning.
9. Select the partition size:
Fixed partition size allows you to define the size of the partition (in MBs).
Fill to end of disk allows you to create a partition that uses any space that remains after defining partitions
with fixed sizes.
Tip
It is wise to allocate slightly more memory than is required on some partitions. To estimate the amount of
memory needed by a partition, use the du -hc command.
It is important to note that memory allocated to a partition is not permanently consumed. For example,
consider programs that need to write temporary files in a /tmp partition. Although you may configure the
partition to use a maximum of 50 MB of memory, the actual amount used depends on the contents of the
partition. If the /tmp partition is empty, the amount of memory used is 0 MB.
10. Click Apply to save changes or click Cancel to abort this action.
Clusterworx System Administrator’s Guide

11. Click Check In to import the image into VCS.
12. Click Apply to complete the process. Click Revert or Close to abort this action.
Note
Image Management
Diskless Hosts
Clusterworx generates the file, boot.profile, each time you save an image. See boot.profile on page 122 for
a description of the information contained in this file.
Clusterworx System Administrator’s Guide
137

Image Management
RAM Disk
138
RAM Disk
The RAM Disk is a small disk image that is created and loaded with the utilities required to provision the
host. When the host first powers on, it loads the kernel and mounts the RAM Disk as the root file system. In
order for host provisioning to succeed, the RAM Disk must contain specific boot utilities. Under typical
circumstances, you will not need to add boot utilities unless you are creating something such as a custom,
pre-finalized script that needs utilities not required by standard Linux versions (e.g., modprobe).
Note
Clusterworx uses two “skeleton” RAM Disks—one for ia32 and another for both AMD-64 and EM64T.
These skeleton disks are located in /opt/cwx/ramdisks and should never be modified manually. All
changes must be performed through Clusterworx or in /opt/cwx/imaging//images/
/ramdisk.
To Add Boot Utilities
Adding boot utilities to the RAM Disk allows you to create such things as custom, pre-finalized scripts using
utilities that are not required for standard Linux versions.
1. Select the Imaging tab.
2. Select an image from the navigation tree.
3. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
4. Click the RAM Disk subtab. Default files from the skeleton RAM Disk are grayed out—any changes or
updates appear in black.
Clusterworx System Administrator’s Guide

5. Click Add. The Add File to RAM Disk dialog appears.
6. Enter the boot utility path in the Source field or click Browse to locate a utility.
7. Specify the Destination location in which to install the boot utility in the RAM Disk file system.
8. Click OK to install the boot utility or click Cancel to abort this action.
9. (Optional) Select Add Debug Utilities to apply additional debugging utilities to the RAM Disk.
10. Click Apply to complete the process. Click Revert or Close to abort this action.
Note
Image Management
RAM Disk
Clusterworx generates the file, boot.profile, each time you save an image. See boot.profile on page 122 for
a description of the information contained in this file.
Clusterworx System Administrator’s Guide
139

Image Management
Plug-ins for the Boot Process
140
Plug-ins for the Boot Process
A host requires a boot process to initialize hardware, load drivers, and complete the necessary tasks to
initiate a login prompt. The boot process is composed of five main stages and allows you to include additional
plug-ins at each stage to expand system capabilities. During the boot process, the system moves from stage to
stage installing any plug-ins specified. If you do not specify any plug-ins, the host will boot using the built-in
boot process. The boot process is as follows:
initialize Stage one creates writable directories and loads any kernel modules.
identify Stage two uses DHCP to get the IP address and host name.
partition Stage three creates partitions and file systems.
image Stage four downloads and extracts the payload.
finalize Stage five configures Clusterworx services to run with the host name retrieved from
DHCP.
Note
Stage 1 Stage 2 Stage 3 Stage 4 Stage 5
initialize
/plugins/postinitialize
/plugins/preidentify
All plug-ins must be added inside the RAM Disk under /plugins/.
Warning!
identify
/plugins/postidentify
/plugins/preparation
When working with prefinalize scripts, you must make special considerations in a RedHat Enterprise
Linux 3 update 3 or 4 environment. To ensure that Clusterworx payload installations work properly, you
may need to merge your script with the Prefinalize script contained in the /misc directory. See To Install
the Clusterworx Prefinalize Script on page 143.
Although you can add or override functionality during the pre or post stages of the boot process,
overriding stages other than pre or post may cause the boot process to fail.
Clusterworx System Administrator’s Guide
partition
/plugins/postpartition
/plugins/preimage
image
/plugins/postimage
/plugins/prefinalize
finalize

To Add a Plug-in
The following example depicts how to run a script during the boot process.
Image Management
Plug-ins for the Boot Process
1. Write a shell or Perl script to run during the boot process. For example, to run a script immediately after
partitioning a drive, name the script postpartition and add it to the plugins directory in the RAMdisk
(i.e., /plugins/).
Note
You must add all necessary utilities for your plug-in script to the RAM Disk. For example, if you use a Perl
script as a plug-in, you must add the Perl binary and all necessary shared libraries and modules to the
RAM Disk. The shared libraries for a utility may be determined using the ldd(1) command. Please note
that adding these items significantly increases the size of the RAM Disk. See To Add Boot Utilities on
page 138.
2. Select the Imaging tab.
3. Select an image from the navigation tree.
4. Select Edit from the Edit menu or right-click on the image in the navigation tree and select Edit.
5. Click the RAM Disk subtab.
6. Click Add. The Add File to RAM Disk dialog appears.
Clusterworx System Administrator’s Guide
141

Image Management
Plug-ins for the Boot Process
142
7. Enter the boot utility path in the Source field or click Browse to locate a plug-in.
8. Specify the install location in the Destination field.
Note
All scripts must be installed in the /plugins/ directory. However, you can overwrite other utilities.
9. Click OK to install the utility or click Cancel to abort this action.
10. (Optional) Select Add Debug Utilities to apply additional debugging utilities to the RAM Disk.
11. Click Apply to complete the process. Click Revert or Close to abort this action.
Note
Clusterworx generates the file, boot.profile, each time you save an image. See boot.profile on page 122 for
a description of the information contained in this file.
Clusterworx System Administrator’s Guide

To Install the Clusterworx Prefinalize Script
Image Management
Plug-ins for the Boot Process
In a RedHat Enterprise Linux 3 update 3 or 4 environment, you must add the prefinalize script to ensure that
the Clusterworx payload installation functions correctly.
1. Copy the prefinalize script from the /misc directory on the Clusterworx ISO to your hard drive:
cp /mnt/cdrom/misc/prefinalize /root/prefinalize
2. Change the script to an executable:
chmod +x prefinalize
3. Select the Imaging tab and create a new image or edit an existing RedHat Enterprise Linux 3 or 4 image.
4. Under the RAM Disk sub tab, click the Add button.
5. Click Browse to select the prefinalize script as the source and enter /plugins/prefinalize as the
destination.
6. Click OK.
7. Click Apply to save changes or Revert or Close to abort this action.
Tip
If a prefinalize script already exists, you can merge the scripts or contact support for additional
assistance. By default, no additional prefinalize scripts exist.
Clusterworx System Administrator’s Guide
143

Version Control System (VCS)
Version Branching
144
Version Control System (VCS)
The Clusterworx Version Control System allows users with privileges to manage changes to payloads,
kernels, or images (similar in nature to managing changes in source code with a version control system). The
Version Control System is accessed via the VCS menu and supports common Check-Out and Check-In
operations. Items are version controlled by the user—when an item is checked out, it can be modified locally
and checked back in. For information on initially placing a payload, kernel, or image under version control,
see Payload Management on page 84, Kernel Management on page 112, or Image Management on page 120.
Version Branching
Image management works with VCS to allow you to branch any payload, kernel, or image under version
control arbitrarily from any version. The following diagram illustrates version branching for a kernel. The
process begins with a working copy of a kernel that is checked into VCS as a versioned kernel. The kernel is
then checked out of VCS, modified (as a working copy of the kernel), and checked back into VCS as a new,
versioned branch of the original kernel.
VCS
Tip
If another user checks out a copy of the same item you are working with and checks it back into VCS
before you do, you must either discard your changes and check out the latest version of the item or
create a new branch that does not contain the items checked in by the other user.
Note
Check In
(Working Copy version 0)
A Working Copy of a payload, kernel, or image is currently present in the working area (e.g. /opt/cwx/
imaging//payloads). A Versioned payload, kernel, or image is a revision of a payload, kernel, or
image stored in VCS.
Clusterworx System Administrator’s Guide
VCS 1
Check Out
Check In
VCS
1 2
(Versioned) (Versioned)
(Working Copy version 1)
New Branch

Version Branching Example
Version Control System (VCS)
Version Branching
Suppose, for example, that a payload under version control was gradually optimized to suit specific hardware
contained in a cluster. If the optimization were performed in stages (where each stage was a different VCS
revision), VCS would contain multiple versions of the payload. Now suppose that you added some new hosts
with slightly different hardware specifications to the cluster, but the last few revisions of the payload use
optimizations that are incompatible with the new hardware. Using the version branching feature, you could
create a new branch of the payload based on an older version that does not contain the offending
optimizations. The new branch could be used with the new hosts, while the remaining hosts could use the
original payload.
Clusterworx System Administrator’s Guide
145

Version Control System (VCS)
Version Control Check-in
146
Version Control Check-in
To Check In a Payload, Kernel, or Image
1. After making changes to a payload, kernel, or image, click Check In or select Check In from the VCS
menu. The VCS Import dialog appears.
2. (Optional) Enter an alias to use when referring to this version. The alias is the name displayed in the VCS
Log between the parentheses:
1()
February 26, 2004 9:14:17 AM MST, root
Description of changes...
3. (Optional) Select Branch to create a new branch of this item. Do not select this option if you want
Clusterworx to create a new revision on the current branch.
Note
If another user checks out a copy of the same item you are working with and checks it back into VCS
before you do, you must either discard your changes and check out the latest version of the item or
create a new branch that does not contain the items checked in by the other user.
4. (Optional) Click Status to view information about the item (i.e., repository, module, location, revision).
See also Version Status on page 149.
5. Click OK to continue or click Cancel to abort this action.
Tip
VCS Check In may fail if you have insufficient disk space. To monitor the amount of available disk space,
configure the disk space monitor to log this information, e-mail the administrator, or run a script when
disk space is low. See Clusterworx Monitoring and Event Subsystem on page 171 for details.
Clusterworx System Administrator’s Guide

Version Control Check-out
To Check Out a Payload, Kernel, or Image
1. Select the Imaging tab.
2. Select Check Out from the VCS Menu. The VCS Check Out dialog appears.
Version Control System (VCS)
Version Control Check-out
3. Select the payload, kernel, or image you want to check out of VCS (use the Shift or Ctrl keys to select
multiple items).
Note
When you check out a payload, kernel, or image, Clusterworx creates a working copy of the item. If you
check out the root of a payload, kernel, or image, Clusterworx selects the tip revision.
Warning!
Every time a user creates a payload (or checks a payload out of VCS), Clusterworx stores a working copy
of the payload in the user’s /opt/cwx/imaging directory. To accommodate this process, Clusterworx
requires a minimum of 10 GB of disk space. Once the payload is checked into VCS, the user may safely
remove the contents of the imaging directory.
4. Click OK. Clusterworx places the item(s) into a working directory where you may make changes. Click
Cancel to abort this action.
Clusterworx System Administrator’s Guide
147

Version Control System (VCS)
VCS Management
148
VCS Management
The VCS management option allows you to view the change history for a particular package, kernel, or
image.
To Launch the VCS Management Console
1. Select the Imaging tab.
2. Select VCS Management from the VCS menu. The VCS Management dialog appears.
3. Select a payload, kernel, or image for which to display a change history.
Tip
Click the A (Add), M (Modify), or D (Delete) options to include or exclude specific information.
4. To remove a payload, kernel, or image, select the item from the navigation tree and click Delete. When
deleting a version of any item, all subsequent versions are also deleted (i.e., deleting version 4 also
removes versions 5, 6, and so on).
Warning!
If you select Payloads, Kernels, or Images from the navigation tree, clicking Delete will remove ALL
payloads, kernels, or images from the system.
5. To copy a payload, kernel, or image, right-click on the item in the navigation tree and select Copy.
Clusterworx prompts you for a new name, then creates a new copy of the item in VCS.
Clusterworx System Administrator’s Guide

Version Status
Version Control System (VCS)
Version Status
In the event that a payload, kernel, or image is already under version control, you may view its version status
through the VCS menu.
Tip
To view a summary of changes made to an item since it was last checked into VCS, select Check Out
from the VCS menu. See VCS Management on page 148.
To View Version Status
1. Select Status from the VCS menu. The VCS Status dialog appears.
2. When finished, click OK to close the dialog.
Clusterworx System Administrator’s Guide
149

Version Control System (VCS)
VCS Host Compare
150
VCS Host Compare
The Host Compare feature allows you to compare the payload currently installed on a host with the latest
version of the payload stored in VCS. This is useful when determining whether or not to re-provision a host
with a new payload. Similar to the VCS Management Console, this option displays all additions,
modifications, and deletions made to the payload since you last used it to provision the host.
TO EXCLUDE FILES FROM THE COMPARISON LIST
1. Open the file, /opt/cwx/etc/exclude.files (a copy of this file should exist on all hosts):
proc
dev/pts
etc/ssh/ssh_host_dsa_key
etc/ssh/ssh_host_dsa_key.pub
etc/ssh/ssh_host_key
etc/ssh/ssh_host_key.pub
etc/ssh/ssh_host_rsa_key
etc/ssh/ssh_host_rsa_key.pub
media
mnt
root/.ssh
scratch
sys
tmp
usr/local/src
usr/share/doc
usr/src
var/cache/
var/lock
Clusterworx System Administrator’s Guide

var/log
var/run
var/spool/anacron
var/spool/at
var/spool/atjobs
var/spool/atspool
var/spool/clientmqueue
var/spool/cron
var/spool/mail
var/spool/mqueue
var/tmp
2. Edit the file as needed, then save your changes.
Tip
It is best to edit this file while it is in the payload so it can be copied to all hosts.
VersionControlService.profile
Version Control System (VCS)
VCS Host Compare
Clusterworx uses VersionControlService.profile, a global default exclude list that is not distribution-specific.
You may add files or directories to this list to prevent Clusterworx from checking them into VCS—particularly
helpful when importing payloads from the working directory. To remove items from the exclusion list,
comment them out of the profile.
Also contained in the VersionControlService.profile, the deflate.temp:/ parameter allows you to specify
an alternate path for large files created while importing a payload.
Clusterworx System Administrator’s Guide
151

Version Control System (VCS)
VCS Host Compare
152
Clusterworx System Administrator’s Guide

Chapter 8
Provisioning
Overview
The Clusterworx provisioning capability allows you to create an image, then apply the image to multiple
hosts. The following illustration depicts an image that is provisioned to multiple hosts.
+
=
Payload
Kernel
Image
Provision
Host
Host
Host
Host
Clusterworx System Administrator’s Guide
153

Selecting an Image
154
Selecting an Image
The Clusterworx provisioning service allows you to select a versioned image from VCS or a working copy of
an image from your working directory.
To Select an Image
1. Select the Provisioning tab.
2. Select the host(s) you want to provision from the navigation tree (use the Shift or Ctrl keys to select
multiple hosts).
3. Select the Versioned Images or Working Images subtab.
Note
A Working Copy of an image is currently present in the working area (e.g., /opt/cwx/imaging//
payloads). A Versioned image is a revision of an image stored in VCS. See Version Control System (VCS)
on page 144 for details on using the version control system.
4. Select the image you want to use to provision the host(s).
5. (Optional) Click the Advanced button to display the Advanced Options dialog (see Advanced
Provisioning Options on page 156.). This dialog allows you to override partitioning, payload, and kernel
verbosity settings.
6. Click Provision to distribute the image to the selected hosts. Clusterworx asks you to confirm your action.
Clusterworx System Administrator’s Guide

7. Click Yes to provision the host(s) or click No to abort this action.
Warning!
If you click Yes, Clusterworx re-provisions the hosts using the new image. Any pending or running jobs
on the selected host(s) are lost.
Tip
To conserve space in the /opt directory, you may delete cached .ebi and .payload files from
/opt/cwx/provision/cache/.
Please note, however, that removing ALL cached files may require more time to provision hosts. To
speed up the provisioning process, do not delete the latest cached file—removing cached payloads that
are in use on hosts forces Clusterworx to re-image the hosts the next time they are provisioned.
Tip
To disable the provisioning confirmation dialog, edit the ProvisioningService.profile and set the
provisioning.confirm option to true:
# Default value for the presence of a confirmation dialog
# before provisioning (in the Provisioning tab)
# true: Show the confirmation dialog
# false: Skip the confirmation dialog
provisioning.confirm: true
Selecting an Image
Clusterworx System Administrator’s Guide
155

Selecting an Image
Advanced Provisioning Options
156
Advanced Provisioning Options
The Advanced Options dialog allows you to temporarily configure partitioning behavior, payload download
settings, and Kernel verbosity. These settings are not persistent, they simply override those configurations
made using the Advanced Image Options dialog. See Advanced Imaging Options on page 121.
USE WORKING COPY OF KERNEL
Enable this option to use the working copy of the kernel in place of its version-controlled equivalent. Because
working copies of kernels are often shared, hosts associated with the working copy are updated to use the
latest version when they reboot—but only if the kernel was modified or used to provision other hosts.
USE WORKING COPY OF PAYLOAD
Enable this option to use the working copy of the payload in place of its version-controlled equivalent.
Because working copies of payloads are often shared, hosts associated with the working copy are updated to
use the latest version when they reboot—but only if the payload was modified or used to provision other
hosts.
Clusterworx System Administrator’s Guide

SCHEDULE PROVISION AT NEXT REBOOT
Selecting an Image
Advanced Provisioning Options
Enable this option to postpone provisioning until the next time you reboot the hosts. Provisioning channels
are created and hosts are assigned to the new image, but the hosts cannot reboot or cycle power without
being provisioned.
Tip
To change the default scheduled provisioning setting, edit $CWXHOME/etc/ProvisioningService.profile
as follows:
provisioning.nextreboot:{true|false}
Scheduling a provision at next reboot can be especially useful when used with PBS. For example, you may
make updates to a payload, then schedule provisioning to occur only after the current tasks are complete. To
do this, the root user (who must be allowed to submit jobs) can submit a job to each host instructing it to
reboot.
Root can submit jobs to PBS only if acl_roots is configured. To configure acl_roots, run qmgr and enter the
following from the qmgr prompt:
qmgr: set server acl_roots += root
If you already set up additional ACLs, you will also need to add root to those ACLs. For example, suppose you
have an acl_users list that allows access to a queue, workq. The command to add root to the ACL would be:
# set queue workq acl_users += root
The following is a sample PBS script you might use to reboot hosts:
#################################################
#!/bin/bash
for i in `seq 1 64`
do
echo \#PBS -N Reboot_n$i > Reboot_n$i.pbs
echo \#PBS -joe >> Reboot_n$i.pbs
echo \#PBS -V >> Reboot_n$i.pbs
echo \#PBS -l nodes=n$i >> Reboot_n$i.pbs
echo \#PBS -q workq >> Reboot_n$i.pbs
echo \#PBS -o /dev/null >> Reboot_n$i.pbs
echo \/sbin\/reboot >> Reboot_n$i.pbs
echo done >> Reboot_n$i.pbs
qsub < Reboot_n$i.pbs
rm Reboot_n$i.pbs
done
#################################################
PARTITION THIS TIME
This option allows you override the current partition settings. You may automatically partition an image if
the partition changed, force partitioning to re-create all partitions—including those that are exempt from
being overwritten (see Managing Partitions on page 124), or choose not to partition the host.
DOWNLOAD PAYLOAD THIS TIME
The payload options allow you to automatically download a payload if a newer version is available (or if the
current payload is not identical to that contained in the image), force Clusterworx to download a new copy of
the image—regardless of the image status, or choose not to download a payload.
Clusterworx System Administrator’s Guide
157

Selecting an Image
Configuring DHCP
158
KERNEL VERBOSITY
The kernel verbosity level (1-8) allows you to control debug messages displayed by the kernel during
provisioning. The default value, 1, is the least verbose and 8 is the most.
Configuring DHCP
Provisioning also allows you to modify DHCP settings. By default, when provisioning occurs, Clusterworx
automatically modifies DHCP settings and restarts the protocol. If you make manual DHCP modifications
and want Clusterworx to stop, start, restart, or reload DHCP, use the controls in the DHCP menu.
Note
When working with DHCP, ensure that the server installation includes DHCP and, if the subnet on
which the cluster will run differs from 192.168.0.0, edit the file in the Clusterworx DHCP installation
directory (i.e., /opt/cwx/dhcp/dhcpd.conf.template).
If you update your existing Clusterworx installation to a newer version on the Clusterworx Master Host,
any changes to the dhcpd.conf.template file will be lost and will need to be updated again.
To Configure DHCP Settings
The DHCP menu allows you to perform the following operations:
Stop
Start
Restart
Reload (re-creates the dhcpd.conf file)
Tip
Changes made to /etc/dhcpd.conf are overwritten when you provision the host. Any changes to DHCP
should be made to /opt/cwx/dhcp/dhcpd.conf.template.
To Configure Multicast Routes
Note
When provisioning with SuSE Linux Enterprise Server 9 (or newer) or RHEL4, the default multicast
configuration may not work properly. Ensure that multicast routing is configured to use the management
interface.
SLES
1. Enter the following from the CLI to temporarily add the route (where eth0 is the management interface):
route add -net 239.192.0.0 netmask 255.255.255.0 dev eth0
2. Make the change persistent by entering the following:
vi /etc/sysconfig/network/routes
Then add:
239.192.0.0 0.0.0.0 255.255.255.0 eth0 multicast
Clusterworx System Administrator’s Guide

RHEL4
Selecting an Image
Configuring DHCP
1. Enter the following from the CLI to temporarily add the route (where eth0 is the management interface):
route add -net 239.192.0.0 netmask 255.255.255.0 dev eth0
2. Make the change persistent by entering the following:
vi /etc/sysconfig/network-scripts/route-eth0
Then add:
239.192.0.0/24 dev eth0
Clusterworx System Administrator’s Guide
159

Provisioning Channels
Configuring DHCP
160
Provisioning Channels
On certain occasions, you may need to use more than 20 provisioning channels. For example, you may need
to use more than 10 images on your cluster. Because each image requires the use of two channels (one for the
EBI and one for the payload), you must create more channels to accommodate the additional images. In such
situations, you must edit /opt/cwx/etc/DistributionService.profile, /opt/cwx/etc/Activator.profile, and
/opt/cwx/etc/system-Clusterworx.profile.
Note
By default, 20 provisioning channels (00-19) are defined.
Add Provisioning Channels
1. In the DistributionService.profile, copy the last two channels and change all ports, IP addresses, and
numbers. For an explanation of the contents of this file, see DistributionService.profile on page 161.
Note
The multicast IP addresses are the same for the channel pairs but the ports are different.
2. In the Activator.profile, add a host and command entry for the new channels. For each additional
multicast channel added to DistributionService.profile, you must include the following in
Activator.profile:
DistributionService.provisioning-.host=
DistributionService.provisioning-.command=DistributionService
-channel\:provisioning-
For example:
DistributionService.provisioning-20.host=cwxhost
DistributionService.provisioning-20.command=DistributionService
-channel\:provisioning-20
3. Locate the system.dna.activate line in the system-Clusterworx.profile and add the new channel names to
the end of that line.
4. Restart Clusterworx.
5. (Optional) To view the additional channels, run executive list DistributionService.
Clusterworx System Administrator’s Guide

DistributionService.profile
Provisioning Channels
DistributionService.profile
/opt/cwx/etc/DistributionService.profile contains the options used to set the Clusterworx provisioning
channels. You may create additional channels or change multicast options by altering the contents of this
file. If multiple Clusterworx hosts exist in a heterogeneous network, you may need to define several multicast
sub-classes. The structure of DistributionService.profile is as follows:
DistributionService.profile
channels.provisioning-00.file: {system.home}/distribution/provisioning-00
Clusterworx automatically creates symbolic links as required.
channels.provisioning-00.interface: {host}
The host name of the Clusterworx Server (signified by the { host} variable).
channels.provisioning-00.registrar.address: {host.address}
The IP address of the Clusterworx Server (signified by the { host.address} variable).
channels.provisioning-00.registrar.port: 10000
Valid ports are currently set at 10000-10019. Additional multicast addresses can be added if more than 20
provisioning channels are required.
channels.provisioning-00.multicast.address: 239.192.0.128
Valid multicast addresses are 224.0.0.0 through 239.255.255.255, 239.x.x.x is reserved within an organization.
If multiple Clusterworx installations exist on the same network, you must specify different multicast
ranges.
channels.provisioning-00.multicast.port: 10000
Multicast transmission port.
channels.provisioning-00.multicast.size: 1446
Multicast packet size. Packet size must not exceed 1446 for EBI's. For non-EBI's (payloads), this value should
be between 4096 bytes (4K) and 32767 bytes (32K-1).
channels.provisioning-00.multicast.ttl: 1
Packet Time-To-Live. The number of router hops (0–255) the packet is allowed to make.
channels.provisioning-00.multicast.throttle: 10000000
The maximum number of bytes allowed to transfer per second. By default, the DistributionService allows a
data transfer rate of up to 10MB per second (e.g., a 100Mb Ethernet network has a theoretical maximum
bandwidth of 12.5MB). You may increase or decrease this value to increase or decrease the amount of bandwidth
consumed by the multicast transmission.
See warning on page 161.
channels.provisioning-00.multicast.wastegate: 100000
Number of nanoseconds between multicast packets (check switch manufacturer). High-speed switch
should be 0, low-quality switches use a high value. By default, this value is 10000.
See warning below.
Warning!
Do not change the multicast throttle or wastegate values without consulting Technical Support for
assistance.
Clusterworx System Administrator’s Guide
161

Provisioning Channels
DistributionService.profile
162
Note
When provisioning with SuSE Linux Enterprise Server 9 (or newer) or RedHat 4, the default multicast
configuration may not work properly. Ensure that multicast routing is configured to use the management
interface. See To Configure Multicast Routes on page 158.
Clusterworx System Administrator’s Guide

Chapter 9
Runner
Overview
The Clusterworx Runner allows you to remotely execute simultaneous commands on multiple hosts. For
example, you could use the Cluster Copy (ccp) command to copy files to all hosts, or copy and install an RPM
on all hosts. For additional information, see ccp on page 192.
Note
Runner is not a true shell. Avoid using commands that require terminal input or interaction from the
user—these commands may delay processing for your system. Commands to avoid include ping, reboot,
top, halt, and those associated with editing files. If a command you enter does not process quickly, click
Abort.
Tip
If you re-provision a host or execute a command that closes the host’s network connection (e.g., reboot),
close the host’s subtab in Runner. This will prevent you from accidentally sending a command to that
host. If a command is issued, the GUI will not respond until the host returns to normal status.
Clusterworx System Administrator’s Guide
163

Connect to a Host
164
Connect to a Host
Note
Before you can open a connection to a host, you must add the host to the host tree.
To Connect to a Host
1. Select the Runner tab.
2. Click Connect. The Hosts dialog appears.
Clusterworx System Administrator’s Guide

Connect to a Host
3. Select the host to which you want to connect and click Add. To select multiple hosts, use the Shift or Ctrl
keys. Click Cancel to abort this action.
Runner displays the connected host(s) in the navigation tree.
Clusterworx System Administrator’s Guide
165

View Host Output
166
View Host Output
To View Host Output
1. Select the host for which to display output from the navigation tree. To select multiple hosts, use the Shift
or Ctrl keys.
2. Click Open. Clusterworx displays an output subtab for each host.
3. The output tab displays the output from any commands executed on the host. See Execute Commands on
Hosts on page 167.
4. To close the output tab for a specific host, select the tab and click Close. To close the output tabs for all
open hosts, click Close All.
Clusterworx System Administrator’s Guide

Execute Commands on Hosts
Execute Commands on Hosts
When executing commands on hosts, there are two options available: executing commands on all hosts to
which you are connected, or executing commands on a specific host.
To Execute a Command on All Hosts
Enter a CLI command in the upper pane.
Note
If a command fails, Clusterworx displays an error message in the Errors pane.
Tip
Running interactive commands in batch mode will not work; however, many of these commands have a
batch mode that will run non-interactively and exit. The following table contains additional details
regarding some of these commands:
Command Description
top $ top -b -n 1 -b Invokes batch mode
n Refers to the number of iterations before exiting.
This example will print top once, then exit.
Clusterworx System Administrator’s Guide
167

Execute Commands on Hosts
168
Command Description
ping $-c 1 -c Tells the PING command to run a number of times, then exit.
To Execute a Command on a Specific Host
1. Select the output tab for the host on which you want to execute the command.
2. Enter the command in the host’s output pane. See tip on page 167.
Note
If a command fails, Clusterworx displays an error message in the Errors pane.
Clusterworx System Administrator’s Guide
This example will ping the host once, then exit.

Disconnect from a Host
To Disconnect from a Host
Disconnect from a Host
1. Select the host from which to disconnect from the navigation tree. To select multiple hosts, use the Shift
or Ctrl keys.
2. Click Disconnect. Runner closes the output tab(s) for the host(s) and removes them from the navigation
tree.
Clusterworx System Administrator’s Guide
169

Disconnect from a Host
170
Clusterworx System Administrator’s Guide

Chapter 10
Instrumentation Service
Clusterworx Monitoring and Event Subsystem
Clusterworx uses a monitoring and event system (including an event log) to track system values. This system
includes monitors, metrics, listeners, and loggers that collect values from the cluster, then display this
information using the Clusterworx instrumentation GUI (see Instrumentation on page 40). You can extend
the standard monitoring and event system to include custom values and set thresholds for user-defined
events. For example:
Monitoring custom values using scripts.
Displaying custom values in the Clusterworx list view.
Setting thresholds on values and taking an action if these thresholds are exceeded.
Logging custom error conditions in the Clusterworx log.
Running custom scripts as event actions.
Monitors run at a set interval and collect information from each host. Listeners receive information about
metrics from the instrumentation service, then determine if the values are reasonable. If a listener
determines that a metric is above or below a set threshold, the listener triggers a logger to take a specific
action.
Typically, configuration files are host-specific and are located in the /opt/cwx/etc directory. If you modify the
configuration files, copy these files into the payload to make them available on each host after you provision,
then restart Clusterworx.
Warning!
Re-installing Clusterworx will overwrite the configuration files. Please create backups of these files if
they are modified.
Clusterworx System Administrator’s Guide
171

Monitors
Custom Monitors
172
Monitors
Monitors run periodically on the hosts and provide metrics that are gathered, processed, and displayed using
the Clusterworx instrumentation GUI. All standard Clusterworx monitors are configured in the
InstrumentationMonitors.profile in the /opt/cwx/etc directory. The format of the monitor configuration in the
file is generally as follows (where is in milliseconds):
: com.lnxi.instrumentation.server.
.interval:
When working with standard monitors, it is strongly recommended that you leave all monitors enabled—
however, you can increase how often these monitors run. Raising the interval can reduce CPU time and
network use for monitoring. Because Clusterworx uses very little CPU processing time on the compute hosts,
values as high as 1 second (1000 milliseconds) are nearly undetectable. By default, some monitors are set to
run at 5 seconds (5000 milliseconds) or longer.
Example
#
# A monitor for network statistics.
# This information is polled every second.
#
network: com.lnxi.instrumentation.server.NetworkMonitor
network.interval: 1000
Note
The comments were added for readability only.
Custom Monitors
Custom monitors can be added to Clusterworx by using a special monitor called the Command Monitor. The
Command Monitor can use values from any user-defined program or script that returns the information in a
format Clusterworx can process. To use the Command Monitor, add an entry to the
InstrumentationMonitors.profile with the following information:
: com.lnxi.instrumentation.server.CommandMonitor
.command: /path/to/script
.interval: 5000
Note
The must be unique for each monitor.
Warning!
Test scripts carefully! Running an invalid script may cause undesired results with Clusterworx.
Clusterworx System Administrator’s Guide

Monitors
Custom Monitors
Because the Command Monitor typically invokes a script (e.g., bash, perl), using values of less than 5 seconds
is not recommended (but is supported). To use the Command Monitor, the program or script called must
return values to STDOUT in key:value pairs that use the following format:
hosts...:\n
hosts...:\n
The refers to the name of the host from which you are running the script.
The is the same name used in the InstrumentationMonitors.profile.
The parameter refers to what is being monitored.
The is the return value for that key. The script can return one or more items as long as they all have a
key and value. The value can be any string or number, but the script is responsible for the formatting. The \n
at the end is a newline character (required).
Custom Monitors Example
The following example uses perl to monitor how many users are logged into the host. The script will return
two values: how many people are logged in and who the people are. The script name is /opt/cwx/bin/who.pl
and returns who.who and who.count.
#!/usr/bin/perl -w
# Basic modules are allowed
use IO::File;
use Sys::Hostname;
$host = hostname;
my @users;
# This opens the program and runs it. Don't forget the '|' on the end
my $fh = new IO::File('/usr/bin/who |');
# If the program was started
if (defined $fh) {
# Then loop through its output until you get an eof.
while (defined($line = )) {
if ($line =~ m/^\w+.*/) {
$line =~ m/^(\w+).*$/;
push(@users,$1);
}
}
# Close the file.
$fh->close();
}
# Remove duplicate entries of who.
%seen = ();
foreach $item (@users) {
push(@uniq, $item) unless $seen{$item}++;
}
# Count how many items are in the array for our count
$count = scalar(@uniq);
Clusterworx System Administrator’s Guide
173

Monitors
Custom Monitors
174
# Rather than an array of values, just return a single text string;
foreach $users(@uniq) {
$who .= “$users,”;
}
chop($who);
print “hosts.”. $host . “.who.count:” . $count .“\n”;
print “hosts.”. $host . “.who.who:” . join(“,”, $who).“\n”;
When you run the script on host “n2” (assuming that perl and the perl modules above are installed correctly),
the following prints to STDOUT:
[root@n2 root]# ./who.pl
hosts.n2.who.count:1
hosts.n2.who.who:root
To configure Clusterworx to run this script and collect the values, add the configuration to the
InstrumentationMonitors.profile:
who: com.lnxi.instrumentation.server.CommandMonitor
who.command: /opt/cwx/bin/who.pl
who.interval: 5000
Note
Before changes can take effect, you must restart Clusterworx on each host where the custom monitor is
installed.
Clusterworx System Administrator’s Guide

Metrics
Metrics
Custom Monitors
Metrics refer to data collected by monitors that is processed and displayed by the Clusterworx
instrumentation service. The types of metrics collected are tab-specific (unique to each tab) and Clusterworx
allows you to view metrics for an individual host or group of hosts. For a list of available metrics, see Preconfigured
Metrics on page 237.
Note
Before you can display a custom metric, you must define a custom monitor to collect the data. See Custom
Monitors on page 172.
To Select Displayed Metrics
1. Select the Hosts tab.
2. Select the Instrumentation subtab.
3. Select the host(s) for which you want to define the metrics.
4. Select the Tab that identifies the metric type you will set.
Note
To define metrics for the General tab, select List from the View menu.
Clusterworx System Administrator’s Guide
175

Metrics
Metric Selector
176
5. Select Metrics from the Edit menu. The Metric Selector appears.
6. Select the metrics you want to include, then click OK.
Metric Selector
The Metric Selector reads from Metrics.profile in the /opt/cwx/etc directory on each Clusterworx client. You
may add custom metrics to this profile by making additions in the proper file format:
hosts...label:
hosts...description:
hosts...type:java.lang.
hosts...pattern:
The is the host name.
The is the title displayed in the Clusterworx list monitoring view and in the metric selector
dialog.
The indicates what the monitor does and appears in the metric selector dialog.
The is either “Number” or “String.” Numbers are right justified and Strings are left-justified in the
Clusterworx list view.
The helps set the column width for the Clusterworx list monitoring view. The column width should
reflect the number of characters typically returned by the value. If the returned value has 10-12 characters,
the pattern would be 12 zeros (000000000000). For example, if the returned value is a percent, the pattern
should be “100%” or 4 zeros (0000).
Clusterworx System Administrator’s Guide

Custom Metrics Example
Continuing with the example introduced in Custom Monitors on page 172, add the following to the
Metrics.profile on the Clusterworx client—then restart the Clusterworx client:
hosts.who.count.label=Who Count
hosts.who.count.description=Number of users logged in.
hosts.who.count.type=java.lang.Number
hosts.who.count.pattern=00
hosts.who.who.label=Who's On
hosts.who.who.description=Who's logged in.
hosts.who.who.type=java.lang.String
hosts.who.who.pattern=0000000
The new metrics appear in the Metric Selector dialog.
Metrics
Metric Selector
Clusterworx System Administrator’s Guide
177

Metrics
Metric Selector
178
The “who” additions also appear in the Instrumentation List view:
Clusterworx System Administrator’s Guide

Listeners and Loggers
Listeners and Loggers
Listeners
Listeners constantly read gathered metrics and allow you to set the threshold for every available metric. If the
system exceeds a threshold, Clusterworx executes a logger to address the issue. Standard loggers include
sending messages to the centralized Clusterworx message log, logging to a file, logging to the serial console,
and shutting down the host.
Listeners
Listeners are configured in the InstrumentationListeners.profile. Clusterworx includes several standard
listeners (pre-configured):
Listener Description
Icebox temperature warning Logs a warning if temperature exceeds 55° C.
Icebox temperature error Logs an error and safely shuts down the host if the temperature exceeds 60° C.
System Load information Logs an informational message if the system load exceeds 2.1.
Disk Usage information Logs an informational message when the disk is almost filled to capacity. Included
in code, but commented out.
Swap Usage information Logs an informational message if the host is using swap (needs configuration).
Included in code, but commented out.
The format of the InstrumentationListeners.profile is as follows:
: com.lnxi.instrumentation.server.ThresholdListener
.severity:
.interval:
.metric: hosts.{host.moniker}..
.:
.message: Example {1} limit {0} exceeded on host {3} (current value of {2})
.channels: {log} {file}
The is the name of the listener—every listener name must be unique.
The refers to the warning level for the Clusterworx log. Accepted values are “error,” “warning,”
and “information.”
The is the amount of time (in milliseconds) that the value must exceed the threshold before
triggering a logger. Specifying an interval is recommended when monitoring metrics that typically return
spikes in their values. The following example depicts the temperature fluctuation of a host. If a listener is
configured with an interval of 60,000 milliseconds, the host’s temperature must exceed the threshold for 60
seconds before a logger is triggered. If an interval is not specified, the listener triggers a logger every time the
temperature exceeds the threshold. If the value falls below the threshold, the listener’s interval is reset.
Temperature
�reshold
60 seconds
1Mi t 2Mi t 3Mi t
Clusterworx System Administrator’s Guide
179

Listeners and Loggers
Listeners
180
Note
The ThresholdListener can be used to set a threshold on many of the standard metrics included with
Clusterworx. For more information on available metrics and how to use them, see Pre-configured Metrics
on page 237.
The {host.moniker} represents the name of the host in Clusterworx and should not be changed.
The is the key of the item that will be monitored.
The : option allows you to monitor a high or a low threshold.
The refers to the numeric threshold set for the listener. Users can monitor any of the standard, preconfigured
metrics. See Pre-configured Metrics on page 237.
The message is user-configurable and contains the content of the log message or email message. Several
variables are available in the message:
{0} = Set Threshold
{1} = Metric Name
{2} = Metric Value at the time the listener was triggered
{3} = Hostname
The channels are the pre-configured loggers. The standard loggers are log, file, console, email, script,
powercycle, poweroff, poweron, reset, reboot, halt, and shutdown (explained in detail under Pre-defined
Loggers on page 181). Each listener should use at least one or more of these loggers. Loggers run in order and
should be listed in the same format (i.e., {}) as other Java variables in this file. For example, {log} {file}
{console}.
Example Listener Configuration
Continuing with the “who” example in this chapter, a listener can be created to see how many users are
logged into the system by adding the following configuration to the InstrumentationListeners.profile on the
host. After adding this configuration, you must restart Clusterworx services on the host.
who: com.lnxi.instrumentation.server.ThresholdListener
who.severity: information
who.interval: 10000
who.metric: hosts.{host.moniker}.who.count
who.maximum: 1
who.message: {1}: The current number of users logged in ({2}) exceeded the limit of {0} on host {3}.
who.channels: {log} {console}
This configuration sets up a threshold that allows only one user to log into the system at a time (with an
interval of 10 seconds). The message displayed on the serial console and sent to the Clusterworx message log
is “Who Count: The current number of users logged in (2) exceeded the limit of 1 on host n2.”
Clusterworx System Administrator’s Guide

Loggers
Pre-defined Loggers
Listeners and Loggers
Loggers
Also called Channels, pre-defined loggers are basically aliases (e.g., {log} or {file}) rather than the full logger
name (e.g., loggers.com.lnxi.instrumentation.). A logger refers to the event taken when a threshold
exceeds its maximum or minimum value. Clusterworx uses the following pre-configured loggers:
Logger Action
beacon Turns on the beacon for the host.
console Logs a message to the console. This typically includes the serial console on
/dev/ttyS0. (You may use the Icebox serial console or conman to log these messages.)
email Sends the message via email. Requires SMTP and a configured email address. By default, this logger is
commented out.
file Logs a message to a file on each host, typically /opt/cwx/log/event.log.
halt Sends a “halt” command to the host (this is the same as a shutdown on most machines). If the hosts
fail to power off after a halt, try shutdown.
log Logs a message to the centralized Clusterworx message log.
powercycle Uses the Icebox to perform a hard power cycle.
poweroff Uses the Icebox to execute a hard power off.
poweron Uses the Icebox to turn the power on.
reboot Sends a “reboot” command to the host.
reset Uses the Icebox to do a hard reset.
script Runs a user-defined script on the host. Currently set to use /bin/logger to send a message using syslog,
but other scripts could be added.
shutdown Sends a “shutdown” command to the host (same as halt on most machines). If the hosts fail to power
off after a shutdown, try halt.
Tip
To configure the types of messages displayed by loggers, see TemplateFormatter on page 183.
Clusterworx System Administrator’s Guide
181

Listeners and Loggers
Loggers
182
Custom Loggers
Although pre-configured loggers are typically sufficient, they may be extended or modified to include
additional capabilities. In the following example, script loggers are added to run scripts on the hosts.
Note
For the purposes of this example, refers to the name of the new logger you are creating and
/path/to/script refers to the absolute location of the script to be run.
1. Copy the ShellLogger configuration (shown below) from Logging.profile to create another logger.
loggers.com.lnxi.instrumentation.: \
com.xeroone.logging.ShellLogger
loggers.com.lnxi.instrumentation..command: /path/to/script
loggers.com.lnxi.instrumentation..formatter: \
com.lnxi.instrumentation.event
recorders.com.lnxi.instrumentation..enabled: true
recorders.com.lnxi.instrumentation..loggers: \
com.lnxi.instrumentation.
recorders.com.lnxi.instrumentation..severity: debug
2. Set up a channel to allow the new logger to be called easily. At the bottom of Logging.profile, add the
following:
channels.com.lnxi.instrumentation.: \
com.lnxi.instrumentation.
3. Add an alias (e.g., {script}) to the InstrumentationService.profile to allow the new logger to be aliased by
the listener.
:com.lnxi.instrumentation.
Tip
To configure the types of messages displayed by loggers, see TemplateFormatter on page 183.
Clusterworx System Administrator’s Guide

TemplateFormatter
Listeners and Loggers
Loggers
You may extend the abilities of pre-configured and custom loggers using the template field of the
TemplateFormatter. The template field allows you to configure the types of messages displayed by loggers.
For example, the message template type used in the following example is %m:
formatters.com.lnxi.instrumentation.event: \
com.xeroone.logging.TemplateFormatter
formatters.com.lnxi.instrumentation.event.template: %m
The following table contains a list of supported message templates:
Template Description
%N Sequential record number. This number resets each time the virtual machine restarts.
%T Creation time.
%C Channel.
%S Severity.
%M Message.
%E Event.
%EN Event name.
%ET Event trace.
%AN Application name.
%AM Application moniker.
%AST Application start time.
%AV Application version.
%HN Host name.
%HM Host moniker.
%MS Memory size.
%MF Memory free.
%OSN Operating system name.
%OSV Operating system version.
%% Literal % character.
'' Literal ' (single quote) character.
' Escape character for quoted text.
Clusterworx System Administrator’s Guide
183

Listeners and Loggers
Loggers
184
Clusterworx Message Log
The Clusterworx message log is located on the instrumentation overview screen. If you select multiple hosts
(or a container such as a cluster, partition, or region), the log shows messages for any host in the selection. If
you select a single host, the message log shows messages for this host only. Messages have three severity
levels: error, warning, and informational.
Clusterworx System Administrator’s Guide

Chapter 11
Command-Line Interface
Command-Line Syntax and Conventions
CLI commands documented in this guide adhere to the following rules—commands entered incorrectly may
produce the “Command not recognized” error message.
Convention Description
xyz Items in bold indicate mandatory parameters or keywords (e.g., all).
Angle brackets and italics indicate a user-defined variable (e.g., an IP address or host name)
[x] [ ] Square brackets indicate optional items.
[x|y|z] [ | ] Square brackets with a vertical bar indicate a choice of an optional value.
{x|y|z} { | } Braces with a vertical bar indicate a choice of a required value.
[x{y|z}] [ { | } ] A combination of square brackets and braces with vertical bars indicates a required choice
of an optional parameter.
Tip
Help for all CLI commands is available through man pages.
Note
All CLI command arguments documented in this chapter are shown using colon notation only
({--partition:|-p:}). You may also use a space or an equal sign (i.e., --description , -M=) with these
arguments.
Clusterworx System Administrator’s Guide
185

Command-Line Syntax and Conventions
CLI Commands
186
CLI Commands
CLI Commands
ccp {
[:]
[:]|
[{-usage|-help|-?}]
}
conman {
[[-b [ ...]]|
[-d [:]]|
[-e ]|
[-f]|
[-F ]|
[-h]|
[-j]|
[-l ]|
[-L]|
[-m]|
[-q]|
[-Q]|
[-r]|
[-v]|
[-V]]
}
Clusterworx System Administrator’s Guide

CLI Commands
cwhost {
[partadd [{--description:|-d:} ] [--enable:] [--disable:]
[{--regions:|-R} [,...]] [{--hosts:|-h} [,...]] |
[partmod {[{--name:|-n:} ] [{--description:|-d:} ]
[--enable:] [--disable:] [{--regions:|-R} [,...]]
[{--hosts:|-h} [,...]]} ]|
[partdel ]|
[partshow [[ ...]]]|
[regionadd [{--description:|-d:} ] [{--partition:|-p:} ]
[--enable:] [--disable:] [{--hosts:|-h} [,...]]
[{--groups:|-g} [,...]] ]|
[regionmod {--name:|-n:} [{--description:|-d:} ]
[{--partition:|-p:} ] [--enable:] [--disable:]
[{--hosts:|-h} [,...]]
[{--groups:|-g} [,...]] ]]|
[regiondel ]|
[regionshow [[ ...]]]|
[hostadd [ ] [{--description:|-d:} ]
[--enable:] [--disable:] [{--partition:|-p:} ]
[{--regions:|-R:} [,,...]]
[{--iceboxes:|-i:} :[,:,...:]]]|
[hostmod [{--name:|-n:} ] [{--interfaces:|-I} |[,|]]
[{--description:|-d:} ] [--enable:] [--disable:]
[{--partition:|-p:} ]
[{--regions:|-R:} [,,...]]
[{--iceboxes:|-i:} :[,:,...:]]]|
[hostdel ]|
[hostshow [[ ...]]]|
[ifaceadd [{--management:|-M:}]]|
[ifacemod | [{--management:|-M:}] [--mac:|-m:} ] [{--ip:|-i:} ]
[{--hostname:|-h:} ]]|
[ifacedel |]|
[ifaceshow [|[ | ...|]]]|
[iceboxadd [{--description:|-d:} ]
[{--password:|-p:} ] [{--hosts:|-h:} :[,:...]]]|
[iceboxmod [{--name:|-n:} ] [{--mac:|-m:} ] [{--ip:|-i:} ]
[{--description:|-d:} ] [{--password:|-p:} ]
[{--hosts:|-h:} :[,:...]]]|
[iceboxdel ]|
[iceboxshow [[ ...]]]|
[inflate [ ...]]|
[deflate [ ...]]|
[{--verbose|-v}]|
[-signature]|
[{-usage|-help|-?}]
}
Command-Line Syntax and Conventions
CLI Commands
Clusterworx System Administrator’s Guide
187

Command-Line Syntax and Conventions
CLI Commands
188
CLI Commands
cwpower {
{
[--on:|-1:]|
[--off:|-0:]|
[--cycle:|-C:]|
[--reset:|-R:]|
[--powerstatus:|-S:]|
[--reboot:|-r:]|
[--halt:|-h:]|
[--down:|-d:]|
[--hoststatus:|-s:]|
[--flash|-f]|
[--unflash|-u]|
[--beacon|-b]|
[{--duration|-F} [|force]]|
[--severity|-e]|
[{--verbose:|-v:} [--progressive:|-p:]]
}
[ ...]|
[-signature]|
[{-usage|-help|-?}]
}
cwprovision {
[{--download-path:|-d:}
{--image:|-i:}
{--image.revision:|-I:}
{--kernel:|-k:}[]
[{--kernel-log-level:|-l:}[]]
{--payload:|-p:}[]
[{--payload-download:|-D:}yes|no|default]
[{--repartition:|-R:}yes|no|default]
[{--working-image:|-w:}]|
[{--next-reboot:|-n:}]]|
[{--query-last-image:|-q} [--uncompressed-hostnames:|-u]]
[ ...]}|
[-signature]|
[{-usage|-help|-?}]
}
Clusterworx System Administrator’s Guide

CLI Commands
Command-Line Syntax and Conventions
CLI Commands
cwuser {
[useradd [{--description:|-c:}] [{--home:|-d:}] [{--group:|-g:}]
[{--groups:|-G:}[,,...]]
[{--password:|-p:}] [{--shell:|-s:}] [{--uid:|-u:}]
[{--enable:|-U}] [{--disable:|-L:}] [{--normal:|-n:}] ]|
[usermod [{--description:|-c:}] [{--home:|-d:}] [{--group:|-g:}]
[{--groups:|-G:}[,,...]]
[{--password:|-p:}] [{--shell:|-s:}] [{--uid:|-u:}]
[{--enable:|-U}] [{--disable:|-L:}] [{--name:|-l:}] ]|
[userdel ]|
[usershow [[ ...]]]|
[passwd ]|
[encryptpasswd]|
[groupadd [{--description:|-d:}] [{--gid:|-g:}]
[[{--roles:|-r:}] [,...]] [{--regions:|-R:}[,...]] ]|
[groupmod [{--description:|-d:}] [{--gid:|-g:}]
[[{--roles:|-r:}] [,,...]] [{--regions:|-R:}[,,...]]
[{--name:|-n:}] ]|
[groupdel ]|
[groupshow [[ ...]]]|
[roleadd [{--description:|-d:}] [{--privileges:|-p:}[,,...]] ]|
[rolemod [{--description:|-d:}] [{--privileges:|-p:}[,,...]]
[{--name:|-n:}] ]|
[roledel ]|
[roleshow [[ ...]]]|
[privshow [[ ...]]]|
[{--verbose|-v}]|
[-signature]|
[{-usage|-help|-?}]
}
dbix {
[{-d|--delete} [ ...]]|
[{-i|--import} ] |
[{-x|--export} [ ...]]|
[{-usage|-help|-?}]
}
dbx {
[{--domain:|-d} ] [{--format:|-f:} ] [{-usage|-help|-?}] [-runtime[:verbose]]
[-signature] [-splash]
}
imgr {
{--image:|-i:} [{--kernel:|-k:}] [{--kernel-revision:|-K:}]
[{--payload:|-p:}] [{--payload.revision:|-P:}] [{--force:|-f:}] [{--list:|-l:}]|
[{-usage|-help|-?}]
}
kmgr {
{--name:|-n:} [{--description:|-d:}]
{--path:|-p:} [{--kernel:|-k:}]
[{--architecture:|-a:}] [{--modules:|-m:}] [{--binary:|-b:}] [{--list:|-l:}]|
[{-usage|-help|-?}]
}
Clusterworx System Administrator’s Guide
189

Command-Line Syntax and Conventions
CLI Commands
190
CLI Commands
pdcp {[
[-w [,...,]]|
[-x [,...,]]|
[-a]|
[-i]|
[-r]|
[-p]|
[-q]|
[-f ]|
[-l ]|
[-t ]|
[-d]]
[ ... ]
}
pdsh {
[[-w [,...,]]|
[-x [,...,]]|
[-a]|
[-i]|
[-q]|
[-f ]|
[-s]|
[-l ]|
[-t ]|
[-u ]|
[-n ]|
[-d]|
[-S]|
[,...,]]
}
pmgr {
[[{--description:|-d:}] [{--include:|-i:}]
[{--include-from:|-I:}] [{--location:|-l:}] [{--silent:|-s:}]
[{--exclude:|-x:}]] [{--exclude-from:|-X:}] |
[{-usage|-help|-?}]
}
Clusterworx System Administrator’s Guide

CLI Commands
powerman {
[[{--on|-1}]|
[{--off|-0}]|
[{--cycle|-c}]|
[{--reset|-r}]|
[{--flash|-f}]|
[{--unflash|-u}]|
[{--list|-l}]|
[{--query|-q}]|
[{--node|-n}]|
[{--beacon|-b}]|
[{--temp|-t}]|
[{--help|-h}]|
[{--license|-L}]|
[{--destination|-d} host[:port]]|
[{--version|-V}]|
[{--device|-D}]|
[{--telemetry|-T}]|
[{--exprange|-x}]]
[ ...]
}
vcs {
[{identify| id}]|
[status]|
[include ]|
[exclude ]|
[archive ]|
[import -R: -M: [-n:] [-d:] []]|
[commit [-n:] [-d:] []]|
[branch [-n:] [-d:] []]|
[{checkout | co} -R: -M: [-r:||]]|
[{update | up} [-r:||] []]|
[name [-R:] [-M:] [-r:||] ]|
[describe [-R:] [-M:] [-r:||] ]|
[{narrate | log} [-R: -M:] [-r:||]]|
[iterate [-R: [-M: [-r:||]]]]|
[list]|
[{-usage|-help|-?}]
}
xms
Command-Line Syntax and Conventions
CLI Commands
Clusterworx System Administrator’s Guide
191

ccp
CLI Commands
192
ccp
ccp {
[:]
[:]|
[{-usage|-help|-?}]
}
Description
The Cluster Copy (ccp) command provides a file transfer service between two file systems—the client and the
host running the file service.
Note
This command is effective only when used in the Runner. From a single host it works much like rcp.
Parameters
[:]
The name of the source host and the location of the source file.
[:]
The name of the destination host and the location to which you will copy the
file.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Note
Only the source or the destination file location may be remote, not both. The local file location may be a
relative path, but the path for the remote file location must be absolute.
Tip
You can install an RPM on the hosts by using ccp to put it in a temporary directory, then use the Runner
feature to install it in parallel. Unless you install the RPM into the payload, it will not remain on the host
when you re-provision it.
Example
The following example copies /etc/hosts from the remote n2 to the local directory specified. However, when
used from the Runner, this command copies /etc/hosts from n2 to all other hosts that are selected. This is
very similar to pdcp, except that ccp allows users to copy files from any host in the cluster to all other hosts—
pdcp copies only from the Master Host to the other hosts.
ccp n2:/etc/hosts /etc
Clusterworx System Administrator’s Guide

conman
conman {
[[-b [ ...]]|
[-d [:]]|
[-e ]|
[-f]|
[-F ]|
[-h]|
[-j]|
[-l ]|
[-L]|
[-m]|
[-q]|
[-Q]|
[-r]|
[-v]|
[-V]]
}
Description
conman
CLI Commands
The ConMan client allows you to connect to remote consoles managed by ConManD. Console names are
separated by spaces or commas and matched to the configuration via globbing. Regular expression matching
can be enabled with the -r option.
ConMan supports three console access modes: monitor (read-only), interactive (read-write), and broadcast
(write-only). Unless otherwise specified, ConMan opens the console session in interactive mode (the default).
Parameters
[-b [ ...]]
(Optional) Broadcast to multiple host consoles (write-only). You may enter a
range of hosts or a space-delimited list of hosts (e.g., host[1-4 7 9]).
Data sent by the client is copied to all specified consoles in parallel, but console
output is not sent back to the client. You can use this option in conjunction with
-f or -j.
[-d [:]]
(Optional) Specify the location of the ConManD daemon, overriding the default
[127.0.0.1:7890]. This location may contain a host name or IP address and be
followed by an optional colon and port number.
[-e ] (Optional) Specify the client escape character, overriding the default (&).
[-f] (Optional) Specify that write-access to the console should be forced, thereby
stealing the console away from existing clients with write privileges. As
connections are terminated, ConManD informs the original clients of who
perpetrated the theft.
[-F ] (Optional) Read console names or patterns from a file with the specified name.
Only one console name may be specified per line. Leading and trailing white
space, blank lines, and comments (i.e., lines beginning with a #) are ignored.
[-h] (Optional) Display a summary of the command-line options.
[-j] (Optional) Specify that write-access to the console should be joined, thereby
sharing the console with existing clients that have write privileges. As privileges
Clusterworx System Administrator’s Guide
193

conman
CLI Commands
194
are granted, ConManD informs the original clients that privileges have been
granted to new clients.
[-l ] (Optional) Log console session output to a file with the specified name.
[-L] (Optional) Display license information.
[-m] (Optional) Monitor a console (read-only).
[-q] (Optional) Query ConManD for consoles matching the specified names or
patterns. Output from this query can be saved to file for use with the -F option.
[-Q] (Optional) Enable quiet-mode, suppressing informational messages. This mode
can be toggled on and off from within a console session via the &Q escape.
[-r] (Optional) Match console names via regular expressions instead of globbing.
[-v] (Optional) Enable verbose mode.
[-V] (Optional) Display version information.
The name of the host to which to connect.
ESCAPE CHARACTERS
ConMan supports the following escapes and assumes the default escape character (&):
&? Display a list of all escapes currently available.
&. Terminate the connection.
&& Send a single escape character.
&B Send a serial-break to the remote console.
&F Switch from read-only to read-write via a force.
&I Display information about the connection.
&J Switch from read-only to read-write via a join.
&L Replay the last 4KB of console output. This escape requires that logging is
enabled for the console in the ConManD configuration.
&M Switch from read-write to read-only.
&Q Toggle quiet-mode to display or suppress informational messages.
&R Reset the host associated with this console. This escape requires that resetcmd
is specified in the ConManD configuration.
&Z Suspend the client.
ENVIRONMENT
The following environment variables may be used to override default settings.
CONMAN_HOST Specifies the host name or IP address at which to contact ConManD, but may be
overridden with the -d command-line option. Although a port number separated
by a colon may follow the host name (i.e., host:port), the CONMAN_PORT
environment variable takes precedence. If you do not specify a host, the default
host IP address (127.0.0.1) is used.
CONMAN_PORT Specifies the port on which to contact ConManD, but may be overridden by the
-d command-line option. If not set, the default port (7890) is used.
Clusterworx System Administrator’s Guide

CONMAN_ESCAPE The first character of this variable specifies the escape character, but may be
overridden by the -e command-line option. If not set, the default escape
character (&) is used.
Warning!
Client and server communications are not yet encrypted.
Example 1
To connect to host console n1, enter:
conman n1
Note
Once in conman, enter &. to exit or &? to display a list of conman commands.
Example 2
To broadcast (write-only) to multiple hosts, enter:
conman -b n[1-10]
Tip
To view the output of broadcast commands on a group of hosts, use the conmen command before you
begin entering commands from conman. Conmen opens a new window for each host and displays the
host output.
For example, the following command opens new consoles for hosts n2-n4:
conmen n[2-4]
conman
CLI Commands
Clusterworx System Administrator’s Guide
195

cwhost
CLI Commands
196
cwhost
cwhost {
[partadd [{--description:|-d:} ] [--enable:] [--disable:]
[{--regions:|-R} [,...]] [{--hosts:|-h} [,...]] |
[partmod {[{--name:|-n:} ] [{--description:|-d:} ]
[--enable:] [--disable:] [{--regions:|-R} [,...]]
[{--hosts:|-h} [,...]]} ]|
[partdel ]|
[partshow [[ ...]]]|
[regionadd [{--description:|-d:} ] [{--partition:|-p:} ]
[--enable:] [--disable:] [{--hosts:|-h} [,...]]
[{--groups:|-g} [,...]] ]|
[regionmod {--name:|-n:} [{--description:|-d:} ]
[{--partition:|-p:} ] [--enable:] [--disable:]
[{--hosts:|-h} [,...]]
[{--groups:|-g} [,...]] ]]|
[regiondel ]|
[regionshow [[ ...]]]|
[hostadd [ ] [{--description:|-d:} ]
[--enable:] [--disable:] [{--partition:|-p:} ]
[{--regions:|-R:} [,,...]]
[{--iceboxes:|-i:} :[,:,...:]]]|
[hostmod [{--name:|-n:} ] [{--interfaces:|-I} |[,|]]
[{--description:|-d:} ] [--enable:] [--disable:]
[{--partition:|-p:} ]
[{--regions:|-R:} [,,...]]
[{--iceboxes:|-i:} :[,:,...:]]]|
[hostdel ]|
[hostshow [[ ...]]]|
[ifaceadd [{--management:|-M:}]]|
[ifacemod | [{--management:|-M:}] [--mac:|-m:} ] [{--ip:|-i:} ]
[{--hostname:|-h:} ]]|
[ifacedel |]|
[ifaceshow [|[ | ...|]]]|
[iceboxadd [{--description:|-d:} ]
[{--password:|-p:} ] [{--hosts:|-h:} :[,:...]]]|
[iceboxmod [{--name:|-n:} ] [{--mac:|-m:} ] [{--ip:|-i:} ]
[{--description:|-d:} ] [{--password:|-p:} ]
[{--hosts:|-h:} :[,:...]]]|
[iceboxdel ]|
[iceboxshow [[ ...]]]|
[inflate [ ...]]|
[deflate [ ...]]|
[{--verbose|-v}]|
[-signature]|
[{-usage|-help|-?}]
}
Description
The Host Administration (cwhost) utility allows you to add, modify, view the current state of, or delete any
partition, region, host, interface, or Icebox in your cluster.
Clusterworx System Administrator’s Guide

Subcommands
partadd
Add a partition to the cluster.
cwhost
CLI Commands
[{--description:|-d:} ]
(Optional) A brief description of the partition. If you do not specify a
description, this field remains blank.
[--enable:] [--disable:] (Optional) Indicates whether or not the partition is enabled. If you do not specify
this option, Clusterworx will enable the partition.
[{--regions:|-R} [,...]]
(Optional) The list of regions that are members of this partition. If you do not
specify any regions, none are included in the partition.
[{--hosts:|-h} [,...]]
(Optional) The list of hosts that are members of this partition. If you do not
specify any hosts, none are included in the partition.
The name of the partition to add.
partmod
Modify a partition on the cluster. Unchanged entries remain the same.
[{--name:|-n:} ]
(Optional) Change the partition name. If you do not specify a name,
Clusterworx uses the current partition name.
[{--description:|-d:} ]
(Optional) A brief description of the partition. If you do not specify a
description, Clusterworx uses the current partition description.
[--enable:] [--disable:] (Optional) Indicates whether or not the partition is enabled. If you do not specify
this option, the partition remains in its original state.
[{--regions:|-R} [,...]]
(Optional) The list of regions that are members of this partition. If you do not
specify any regions, the partition remains in its original state.
[{--hosts:|-h} [,...]]
(Optional) The list of hosts that are members of this partition. If you do not
specify any hosts, the partition remains in its original state.
The name of the partition to add.
partdel
Delete a partition from the cluster.
The name of the partition to delete.
partshow
Display the current settings for a partition(s).
[[ ...]]
(Optional) The name(s) of the partition(s) for which to display the current
settings. Multiple entries are delimited by spaces. Leave this option blank to
display all partitions.
Clusterworx System Administrator’s Guide
197

cwhost
CLI Commands
198
regionadd
Add a region to a partition.
[{--description:|-d:} ]
(Optional) A brief description of the region. If you do not specify a description,
this field remains blank.
[{--partition:|-p:} ]
(Optional) The partition to which this region belongs. If you do not specify a
partition, Clusterworx assigns the region to the default or unassigned partition.
[--enable:] [--disable:] (Optional) Indicates whether or not the region is enabled. If you do not specify
this option, Clusterworx will enable the region.
[{--hosts:|-h} [,...]]
(Optional) The list of hosts that are members of this region. If you do not specify
this option, the region will not contain any member hosts.
[{--groups:|-g} [,...]]
(Optional) The list of groups that may access this region. If you do not specify
this option, the region will not be available to any groups.
The name of the new region.
regionmod
Modify a region on the cluster. Unchanged entries remain the same.
{--name:|-n:} (Optional) Change the region name. If you do not specify a name, Clusterworx
uses the current region name.
[{--description:|-d:} ]
(Optional) A brief description of the region. If you do not specify a description,
Clusterworx uses the current region description.
[{--partition:|-p:} ]
(Optional) The partition to which this region belongs. If you do not specify a
partition, Clusterworx assigns the region to the original partition specified.
[--enable:] [--disable:] (Optional) Indicates whether or not the region is enabled. If you do not specify
this option, the region remains in its original state.
[{--hosts:|-h} [,...]]
(Optional) The list of hosts that are members of this region. If you do not specify
any hosts, the region remains in its original state.
[{--groups:|-g} [,...]]
(Optional) The list of groups that may access this region. If you do not specify
any groups, the region remains in its original state.
The name of the region to modify.
regiondel
Delete a region from the cluster.
The name of the region to delete.
Clusterworx System Administrator’s Guide

egionshow
Display the current settings for a region(s).
[[ ...]]
(Optional) The name of the region(s) for which to display the current settings.
Multiple entries are delimited by spaces. Leave this option blank to display all
regions.
cwhost
CLI Commands
hostadd
Add a host to the cluster.
[ ]
The name of each new host, its MAC address, and its IP address. The first host
specified is the management interface. Multiple entries are space-delimited.
[{--description:|-d:} ]
(Optional) A brief description of the host. If you do not specify a description, this
field remains blank.
[--enable:] [--disable:] (Optional) Indicates whether or not the host is enabled. If you do not specify this
option, Clusterworx enables the host.
[{--partition:|-p:} ]
(Optional) The partition to which this host belongs. If you do not specify a
partition, Clusterworx assigns the host to the default or unassigned partition.
[{--regions:|-r:} [,,...]]
(Optional) The region(s) to which this host belongs. If you do not specify a
region, Clusterworx does not assign the host to any region. Multiple entries are
comma-delimited.
[{--iceboxes:|-i:} :[,:,...:]]
(Optional) The Icebox(es) and port(s) to which this host is connected. If you do
not specify an Icebox and port, Clusterworx assumes that the host is not
connected to an Icebox. Multiple entries are comma-delimited.
hostmod
Modify a host on the cluster—unchanged entries remain the same.
The name of the host to modify.
{--name:|-n:} The host’s new name.
[{--interfaces:|-I} |[,|]]
(Optional) A list of interfaces with which this host is associated. If none of the
specified interfaces are management interfaces, Clusterworx marks the first
interface as the management interface.
[{--description:|-d:} ]
(Optional) A brief description of the host. If you do not specify a description,
Clusterworx uses the current host description.
[--enable: {yes|no}] (Optional) Indicates whether or not the host is enabled. If you do not specify this
option, the host remains in its original state.
[{--partition:|-p:} ]
(Optional) The partition to which this host belongs. If you do not specify a
partition, the host remains associated with the original partition specified.
Clusterworx System Administrator’s Guide
199

cwhost
CLI Commands
200
[{--regions:|-r:} [,,...]]
(Optional) The region(s) to which this host belongs. If you do not specify a
partition, the host will not belong to any region. Multiple entries are commadelimited.
[{--iceboxes:|-i:} :[,:,...:]]
(Optional) The Iceboxes and ports to which this host is connected. If you do not
specify an Icebox and port, Clusterworx assumes that the host is not connected
to an Icebox. Multiple entries are comma-delimited.
hostdel
Delete a Clusterworx host.
The name of the host to delete.
hostshow
Display the current settings for a host(s).
[[ ...]]
(Optional) The name of the host(s) for which to display the current settings.
Multiple entries are delimited by spaces. Leave this option blank to display all
hosts.
ifaceadd
Add an interface to the cluster.
The name of the host on which you added the interface.
The MAC address of the interface.
The IP address of the interface.
[{--management:|-M:}]
(Optional) Specify whether or not this interface is a management interface. If
you do not specify this option, Clusterworx assumes that this interface is not a
management interface.
ifacemod
Modify an interface on the cluster—unchanged entries remain the same.
The MAC address of the interface.
The IP address of the interface.
[{--management:|-M:}]
(Optional) Specify whether or not this interface is a management interface. If
you do not specify this option, the interface remains in its original state.
[--mac:|-m:} ] (Optional) Change the interface’s hardware or MAC address.
[{--ip:|-i:} ] (Optional) Change the interface’s IP address.
[{--hostname:|-h:} ]
(Optional) Change the host to which this interface belongs.
ifacedel
Delete an interface from the cluster.
The MAC address of the interface to delete.
The IP address of the interface to delete.
Clusterworx System Administrator’s Guide

ifaceshow
Display the current settings for an interface(s).
cwhost
CLI Commands
[|[ | ...|]]
(Optional) The MAC or IP address(es) of the interface(s) for which to display the
current settings. Multiple entries are delimited by spaces. Leave this option
blank to display all interfaces.
iceboxadd
Add an Icebox to the cluster.
The name of the new Icebox.
The MAC address of the new Icebox.
The IP address of the new Icebox.
[{--description:|-d:} ]
(Optional) A brief description of the Icebox. If you do not specify a description,
this field remains blank.
[{--password:|-p:} ]
(Optional) The Icebox’s administrative password. If you do not specify a
password, Clusterworx uses the default password “icebox”.
[{--hosts:|-h:} :[,:...]]
(Optional) A list of hosts connected to the Icebox and the ports to which they are
connected. If you do not specify this option, Clusterworx assumes that the hosts
are not connected to an Icebox.
iceboxmod
Modify an Icebox on the cluster—unchanged entries remain the same.
The name of the Icebox to modify.
[{--name:|-n:} ]
(Optional) The Icebox’s new name.
[{--mac:|-m:} ] (Optional) Change the Icebox’s hardware or MAC address.
[{--ip:|-i:} ] (Optional) Change the Icebox’s IP address.
[{--description:|-d:} ]
(Optional) A brief description of the Icebox. If you do not specify a description,
Clusterworx uses the current Icebox description.
[{--password:|-p:} ]
(Optional) The Icebox’s administrative password. If you do not specify a
password, Clusterworx uses the original password.
[{--hosts:|-h:} :[,:...]]
(Optional) A list of hosts connected to the Icebox and the ports to which they are
connected. If you do not specify this option, Clusterworx assumes that the hosts
remain in their original state.
iceboxdel
Delete a Clusterworx Icebox.
The name of the Icebox to delete.
Clusterworx System Administrator’s Guide
201

cwhost
CLI Commands
202
iceboxshow
Display the current settings for an Icebox(es).
[[ ...]]
(Optional) The Icebox(es) for which to display the current setting(s). Multiple
entries are delimited by spaces. Leave this option blank to display all Iceboxes.
inflate [ ...]
(Optional) Allows you to change between full and compressed host list format.
Inflate the specified host range(s) to display a full list of hosts.
deflate [ ...] (Optional) Allows you to change between full and compressed host list format.
Deflate the specified host range(s) to display a compressed host list.
[{--verbose|-v}] (Optional) Display verbose output when performing operations. This option is
common to all subcommands.
[-signature] (Optional) Displays the application signature. The application signature
contains the name, description, version, and build information of this
application.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
EXAMPLE 1
View the layout of the system:
cwhost hostshow
EXAMPLE 2
Get details of the system:
cwhost hostshow -v
EXAMPLE 3
Create a region called group1:
cwhost regionadd group1
EXAMPLE 4
Add a host to region group1 with the host name n1, the mac 0005b342afe1, and the IP address 10.0.0.1:
cwhost hostadd -r:group1 n1 0005b342afe1 10.0.0.1
EXAMPLE 5
Add host n2 to the group1 region:
cwhost hostmod -r:group1 n2
EXAMPLE 6
Add an Icebox with the name ice2, the mac 0003b349e8a3, and the IP address 10.0.0.102:
cwhost iceboxadd ice2 0003b349e8a3 10.0.0.102
Clusterworx System Administrator’s Guide

EXAMPLE 7
Deflate the host list n1, n2, n3, and n4:
cwhost deflate n1 n2 n3 n4
n[1-4]
EXAMPLE 8
Inflate the host list n[1-4]:
cwhost inflate n[1-4]
n1
n2
n3
n4
cwhost
CLI Commands
Clusterworx System Administrator’s Guide
203

cwpower
CLI Commands
204
cwpower
cwpower {
{
[--on:|-1:]|
[--off:|-0:]|
[--cycle:|-C:]|
[--reset:|-R:]|
[--powerstatus:|-S:]|
[--reboot:|-r:]|
[--halt:|-h:]|
[--down:|-d:]|
[--hoststatus:|-s:]|
[--flash|-f]|
[--unflash|-u]|
[--beacon|-b]|
[{--duration|-F} [|force]]|
[--severity|-e]|
[{--verbose:|-v:} [--progressive:|-p:]]
}
[ ...]|
[-signature]|
[{-usage|-help|-?}]
}
Description
The Power Administration (cwpower) utility allows you to perform power administration operations on a
host(s) within the cluster. Operations include power on, power off, power cycle, reset, reboot, halt, and power
down (a soft power off). You may also query the current power status of a particular host(s).
Note
You may specify only one power administration operation option each time you use the cwpower
command.
Parameters
[--on|-1] (Optional) Turn on power to the specified host(s).
[--off|-0] (Optional) Turn off power to the specified host(s).
[--cycle|-C] (Optional) Cycle power to the specified host(s).
[--reset|-R] (Optional) Perform a hardware reset for the specified host(s).
[--powerstatus|-S] (Optional) Query the hard power status for the specified host(s).
[--reboot|-r] (Optional) Reboot the specified host(s).
[--halt|-h] (Optional) Halt the specified host(s).
[--down|-d] (Optional) Execute a soft power down on the specified host(s).
[--hoststatus|-s] (Optional) Query the host administration power status for the specified host(s).
[--flash|-f] (Optional) Turn the beacon on for the specified host(s).
[--unflash|-u] (Optional) Turn the beacon off for the specified host(s).
[--beacon|-b] (Optional) Report the beacon status for the specified host(s).
Clusterworx System Administrator’s Guide

cwpower
CLI Commands
[{--duration|-F} [|force]]
(Optional) Used only with the flash option, specifies the duration (in seconds)
for which to flash the beacon on the specified host(s). To turn the beacon on
indefinitely, enter the force option. If you do not specify a duration, the beacon
turns on for 15 seconds.
Note
This option is available only for hosts that support IPMI.
[--severity|-e]| (Optional) Report the error status for the specified host(s).
[{--verbose|-v} [--progressive|-p]]
(Optional) Change the standard output to verbose. Output displays the power
status of each host, one per line. To display output as information becomes
available, select the progressive option—progressive output is not guaranteed to
be sorted and is not summarized.
[ ...]
The name of the host(s) for which to execute the specified operation. You may
enter a range of hosts or a space-delimited list of hosts (e.g., host[1-4 7 9]).
[-signature] (Optional) Displays the application signature. The application signature
contains the name, description, version, and build information of this
application.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
EXAMPLE 1
To Power on hosts 1–10:
cwpower -1 n[1-10]
EXAMPLE 2
Power off host 1:
cwpower -0 n1
EXAMPLE 3
Power cycle hosts 2–5:
cwpower -C n[2-5]
EXAMPLE 4
Check the status (On, Off, Unknown, Provisioning) of hosts 1–10:
cwpower -s n[1-10]
EXAMPLE 5
Flash the beacon on an IPMI host for 60 seconds:
cwpower -f -F 60 n5
Clusterworx System Administrator’s Guide
205

cwprovision
CLI Commands
206
cwprovision
cwprovision {
[{--download-path:|-d:}
{--image:|-i:}
{--image.revision:|-I:}
{--kernel:|-k:}[]
[{--kernel-log-level:|-l:}[]]
{--payload:|-p:}[]
[{--payload-download:|-D:}yes|no|default]
[{--repartition:|-R:}yes|no|default]
[{--working-image:|-w:}]|
[{--next-reboot:|-n:}]]|
[{--query-last-image:|-q} [--uncompressed-hostnames:|-u]]
[ ...]}|
[-signature]|
[{-usage|-help|-?}]
}
Description
The Provisioning (cwprovision) utility allows you to provision a host(s) on the cluster and use working copies
to override the kernel and payload associated with the image. See Provisioning on page 153 and Version
Control System (VCS) on page 144.
Parameters
{--download-path:|-d:}
The path to which to download the image during the boot process (by default,
/mnt).
{--image:|-i:} The image to use to provision the host(s). Unless you specify the working image
option, Clusterworx assumes that the image is a version-controlled image.
{--image.revision:|-I:}
The revision of the image to use to provision the host(s). If you specify a branch
revision, Clusterworx uses the tip revision of the branch. If you do not specify a
revision or a working image, Clusterworx uses the tip revision of the image.
Revisions may be specified either numerically or by alias.
Note
The image.revision option is not available in conjunction with the working-image option.
{--kernel:|-k:}[]
The working copy of the kernel associated with the image used to provision the
host(s). The name is required only if two or more working copies of the kernel
exist.
[{--kernel-log-level:|-l:}[]]
Select the kernel verbosity level used to control debug messages. This level may
range from 1 (the least verbose) to 8 (the most verbose). By default, the verbosity
level is 1.
Clusterworx System Administrator’s Guide

cwprovision
CLI Commands
Power Management{--payload:|-p:}[]
The working copy of the payload associated with the image used to provision
the host(s). The name is required only if two or more working copies of the
payload exist.
[{--payload-download:|-D:}yes|no|default]
(Optional) Specify whether or not to force a download of the payload to the host
during this provisioning operation. The default option automatically detects
whether or not to download the payload. See Advanced Provisioning Options on
page 156.
[{--repartition:|-R:}yes|no|default]
(Optional) Specify whether or not to force a repartition of the host during this
provisioning operation. The default option automatically detects whether or not
to repartition the host. See Advanced Provisioning Options on page 156.
[{--working-image:|-w:}]
(Optional) Use the working copy of the specified image to provision the host(s).
Note
The working-image option is not available in conjunction with the image.revision option.
[{--next-reboot:|-n:}] (Optional) Provision the selected host(s) after the next reboot.
[{--query-last-image:|-q}] (Optional) Display the name and revision of the last image used to provision the
host(s). By default, this option displays a list of compressed host names and their
corresponding images. To change this format, use the uncompressed-hostnames
option. The uncompressed format displays hosts and images in a colonseparated
list that is easily parsed by command-line tools. Each line follows the
format:
Tip
:[VCS| Working] Image::
{|}: :
The kernel and payload specify zero (0) if you use the VCS version and one (1) if you use the working
version to override the kernel or payload using the advanced provisioning options.
Note
The query-last-image option can display image and host information even if the host is down.
[{--uncompressed-hostnames:|-u}]
(Optional) Select this option to change the output format for query-last-image to
list one host name and corresponding image per line. This option can be used
only with query-last-image.
[ ...]
The name of the host(s) to provision. You may enter a range of hosts or a spacedelimited
list of hosts (e.g., host[1-4 7 9]).
Clusterworx System Administrator’s Guide
207

cwprovision
CLI Commands
208
[-signature] (Optional) Displays the application signature. The application signature
contains the name, description, version, and build information of this
application.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
Tip
Use vcs iterate -R:images to see what images are available for provisioning. For a list of working images,
use imgr --list.
EXAMPLE 1
To provision hosts 2–4 with image Compute_Host:
cwprovision -i:Compute_Host n[2-4]
EXAMPLE 2
To provision hosts 2–4 with an older version (version 3) of the image Compute_Host:
cwprovision -i:Compute_Host -I:3 n[2-4]
EXAMPLE 3
To set advanced options to force re-partitioning and download the payload for hosts 2–4:
cwprovision -i:Compute_Host -I:3 -R:yes -D:yes n[2-4]
EXAMPLE 4
To provision hosts 2–10 after the next reboot:
cwprovision -i:rhel4_img --next-reboot n[2-10]
Clusterworx System Administrator’s Guide

cwuser
cwuser {
[useradd [{--description:|-c:}] [{--home:|-d:}] [{--group:|-g:}]
[{--groups:|-G:}[,,...]]
[{--password:|-p:}] [{--shell:|-s:}] [{--uid:|-u:}]
[{--enable:|-U}] [{--disable:|-L:}] [{--normal:|-n:}] ]|
[usermod [{--description:|-c:}] [{--home:|-d:}] [{--group:|-g:}]
[{--groups:|-G:}[,,...]]
[{--password:|-p:}] [{--shell:|-s:}] [{--uid:|-u:}]
[{--enable:|-U}] [{--disable:|-L:}] [{--name:|-l:}] ]|
[userdel ]|
[usershow [[ ...]]]|
[passwd ]|
[encryptpasswd]|
[groupadd [{--description:|-d:}] [{--gid:|-g:}]
[[{--roles:|-r:}] [,...]] [{--regions:|-R:}[,...]] ]|
[groupmod [{--description:|-d:}] [{--gid:|-g:}]
[[{--roles:|-r:}] [,,...]] [{--regions:|-R:}[,,...]]
[{--name:|-n:}] ]|
[groupdel ]|
[groupshow [[ ...]]]|
[roleadd [{--description:|-d:}] [{--privileges:|-p:}[,,...]] ]|
[rolemod [{--description:|-d:}] [{--privileges:|-p:}[,,...]]
[{--name:|-n:}] ]|
[roledel ]|
[roleshow [[ ...]]]|
[privshow [[ ...]]]|
[{--verbose|-v}]|
[-signature]|
[{-usage|-help|-?}]
}
Description
cwuser
CLI Commands
The User Administration (cwuser) utility allows you to perform user, group, and role administration
operations on the cluster. Operations include adding, modifying, deleting, and displaying the current state of
users, groups, and roles.
Subcommands
useradd
Add a Clusterworx user account.
[{--description:|-c:}]
The user’s description (e.g., the user’s full name). If you do not specify a
description, this field remains blank.
[{--home:|-d:}]
The user’s home directory (by default, /home/).
Clusterworx System Administrator’s Guide
209

cwuser
CLI Commands
210
[{--group:|-g:}]
The user’s primary group. You may enter the group name or its numerical gid. If
you do not enter a primary group, Clusterworx will do one of the following:
Red Hat Linux
Create a group with the same name as the user and assign the primary
group to that group (unless you specify the [--normal:|-n:] option).
SuSE Linux
The primary group for the user is the default group specified for users,
usually users.
[{--groups:|-G:}[,,...]]
The secondary group(s) to which the user belongs. If you do not specify this
option, the user belongs to no secondary groups. Multiple entries are delimited
by commas.
[{--password:|-p:}]
The user’s encrypted password. If you do not specify a password, Clusterworx
disables the account.
[{--shell:|-s:}] The user’s login shell. If you do not specify this option, Clusterworx assigns
/bin/bash as the user’s login shell.
[{--uid:|-u:}] The user’s uid. If you do not specify a uid, Clusterworx assigns the first available
uid greater than 499.
[{--enable:|-U}] [{--disable:|-L:}]
These options allow you to enable or disable the user’s account. The -U (unlock)
and -L (lock) options are provided for compatibility with the useradd utility and
allow you to enable and disable the user’s account respectively. If you do not
specify either of these options, the user’s account is enabled by default (unless
no password is supplied).
[{--normal:|-n:}] If you do not specify a group for the user on Red Hat Linux, Clusterworx will
behave as it does with most other versions of Linux. The user’s primary group
uses the default user group, users.
The user’s login name.
usermod
Modify an existing Clusterworx user account.
[{--description:|-c:}]
The user’s description (e.g., the user’s full name). If you do not specify a
description, Clusterworx uses the current description.
[{--home:|-d:}]
The user’s home directory. If left blank, the current home directory.
[{--group:|-g:}]
The user’s primary group. You may enter the group name or its numerical gid. If
you do not enter a primary group, Clusterworx uses the current group
assignment.
[{--groups:|-G:}[,,...]]
The secondary group(s) to which the user belongs. If you do not specify this
option, Clusterworx assigns the user to any secondary groups previously
assigned. Multiple entries are delimited by commas.
Clusterworx System Administrator’s Guide

[{--password:|-p:}]
Change the user’s encrypted password. If you do not specify a password,
Clusterworx uses the current password.
[{--shell:|-s:}] The user’s login shell. If you do not specify this option, Clusterworx uses the
login shell previously assigned to the user.
[{--uid:|-u:}] The user’s uid. If you do not specify a uid, Clusterworx uses the current uid.
cwuser
CLI Commands
[{--enable:|-U}] [{--disable:|-L:}]
These options allow you to enable or disable the user’s account. The -U (unlock)
and -L (lock) options are provided for compatibility with the useradd utility and
allow you to enable and disable the user’s account respectively. If you do not
specify either of these options, the user’s account is enabled by default (unless
no password is supplied).
[{--name:|-l:}] Change the login name for the user’s account. If you do not specify this option,
Clusterworx uses the previous login name.
The user’s login name.
userdel
Delete a Clusterworx user account.
The user’s login name.
usershow
Display the current settings for Clusterworx user(s).
[[ ...]]
(Optional) The user’s(s’) login name(s). Multiple entries are delimited by spaces.
Leave this option blank to display all users.
passwd
Alter the password for a Clusterworx user. After making the change, Clusterworx prompts you to re-enter the
password.
The user’s login name.
encryptpasswd
This option allows you to encrypt a clear text password into the Clusterworx encrypted format and display it
on screen. You may then copy and paste the encrypted password when creating a new user account. See
example on page 214.
Note
Encrypted password strings often contain characters with which the Linux shell has problems. To
overcome this, encrypted text must be escaped using single quotes:
cwuser usermod '-p:$1$Jx^VLEZy$/7SmJmEbmbVMQW13kxaIg.' john
groupadd
Add a group to Clusterworx.
[{--description:|-d:}]
The group’s description. If you do not specify a description, this field remains
blank.
[{--gid:|-g:}] The group’s gid. If you do not specify a gid, Clusterworx assigns the first
available gid greater than 499.
Clusterworx System Administrator’s Guide
211

cwuser
CLI Commands
212
[{--roles:|-r:}[,,...]]
The roles associated with the group. If you do not specify a role(s), the group is
not associated with any roles. Multiple entries are delimited by commas.
[{--regions:|-R:}[,,...]]
The region(s) associated with the group. If you do not specify a region(s),
Clusterworx does not associate the group with any regions. Multiple entries are
delimited by commas.
Group name.
groupmod
Modify an existing Clusterworx group.
[{--description:|-d:}]
The group’s description. If you do not specify a description, Clusterworx uses
the current group description.
[{--gid:|-g:}] The group’s gid. If you do not specify a gid, Clusterworx uses the gid previously
assigned.
[{--roles:|-r:}[,,...]]
The roles associated with the group. If you do not specify a role(s), the group
maintains its previous role associations. Multiple entries are delimited by
commas.
[{--regions:|-R:}[,,...]]
The regions associated with the group. If you do not specify a region(s),
Clusterworx maintains the current region associations. Multiple entries are
delimited by commas.
[{--name:|-n:}] Use this option to change the group name. If you do not specify a name, the
group name remains unchanged.
Current group name.
groupdel
Delete a Clusterworx group.
Group name.
groupshow
Display the current settings for Clusterworx group(s).
[[ ...]]
(Optional) Group name(s) for which to display the current settings. Multiple
entries are delimited by spaces. Leave this option blank to display all groups.
roleadd
Add a role to the Clusterworx database.
[{--description:|-d:}]
The role’s description. If you do not specify a role description, this field remains
blank.
[{--privileges:|-p:}[,,...]]
The privileges associated with the role. If you do not specify a privilege(s),
Clusterworx does not assign any privileges to the role. Multiple entries are
delimited by commas.
The name of the role.
Clusterworx System Administrator’s Guide

olemod
Modify an existing Clusterworx role.
cwuser
CLI Commands
[{--description:|-d:}]
The role’s description. If you do not specify a description for the role,
Clusterworx uses the current description.
[{--privileges:|-p:}[,,...]]
The privileges associated with the role. If you do not specify a privilege(s),
Clusterworx uses current privilege associations. Multiple entries are delimited
by commas.
[{--name:|-n:}] Use this option to change the name of the role. If you do not specify a name, the
role name remains unchanged.
The name of the current role.
roledel
Delete a Clusterworx role.
The name of the role to delete.
roleshow
Display the current settings for Clusterworx role(s).
[[ ...]]
(Optional) The name of the role(s) for which to display the current settings.
Multiple entries are delimited by spaces. Leave this option blank to display all
roles.
privshow
Display the current settings for Clusterworx privilege(s).
[[ ...]]
(Optional) The privilege(s) for which to display the current settings. Multiple
entries are delimited by spaces. Leave this option blank to display all privileges.
[{--verbose|-v}] (Optional) Display verbose output when performing operations. This option is
common to all subcommands.
[-signature] (Optional) Displays the application signature. The application signature
contains the name, description, version, and build information of this
application.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
EXAMPLE 1
Display the current users in the system:
cwuser usershow -v
Clusterworx System Administrator’s Guide
213

cwuser
CLI Commands
214
EXAMPLE 2
Add the user john to the users group:
cwuser useradd -g:users john
Note
John’s account will be disabled until you add a password.
EXAMPLE 3
Add an encrypted password to a new user account:
cwuser encryptpasswd
The command outputs an encrypted string to use when creating the new account.
$1$Jx^VLEZy$/7SmJmEbmbVMQW13kxaIg
Note
Because encrypted password strings often contain characters with which the Linux shell has problems,
encrypted text and user names containing spaces (e.g., John Johnson) must be escaped using single
quotes.
Create the new user account using the encrypted password.
cwuser useradd '-p:$1$Jx^VLEZy$/7SmJmEbmbVMQW13kxaIg.' -d:/home/john -s:/bin/bash -uid:510 -g:users
-c:‘John Johnson’ john
Clusterworx System Administrator’s Guide

dbix
dbix {
[{-d|--delete} [ ...]]|
[{-i|--import} ] |
[{-x|--export} [ ...]]|
[{-usage|-help|-?}]
}
Description
dbix
CLI Commands
The dbix application provides support for importing, exporting, and deleting Clusterworx database entries.
The application uses the standard input and output streams for reading and writing data, and the delete and
export options accept an optional space-delimited list of contexts (a context refers to the path to the database
attributes on which to perform the operation).
Parameters
[{-d|--delete} [ ...]]
Delete entries under the specified context(s).
[{-i|--import} ]
Import entries from stdin.
[{-x|--export} [ ...]]
Export entries for the specified context(s) to stdout.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
EXAMPLE 1
Export the entire database to a file:
dbix -x > cwx.3.2.4-May.20.2005.db
EXAMPLE 2
Export the hosts section of the database to a file:
dbix -x hosts > cwx.3.2.4-hosts.db
EXAMPLE 3
Delete the entire database:
dbix -d
(confirm action)
EXAMPLE 4
Import a new database (or additions):
dbix -i < cwx.3.2.4-new_hosts.db
Clusterworx System Administrator’s Guide
215

dbx
CLI Commands
216
dbx
dbx {
[{--domain:|-d} ] [{--format:|-f:} ] [{-usage|-help|-?}] [-runtime[:verbose]]
[-signature] [-splash]
}
Description
This utility exports specific file formats from the database. Supported formats include a simple host name list
typically used for mpich, pdsh, etc., an IP address to host name map (/etc/hosts), and configuration files for
powerman and conman.
Parameters
Note
Arguments and option values are case sensitive. Option names are not.
[{--domain:|-d} ]
(Optional) Domain name.
[{--format:|-f:} ]
(Optional) Output file format. Supported formats are defined as follows:
names
Simple host name list.
hosts
IP address to host name map.
powerman
Powerman configuration file.
conman
Conman configuration file.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
[-runtime[:verbose]] (Optional) Provides specific information about the current Java runtime
environment.
[-signature] (Optional) Displays the application signature. The application signature
contains the name, description, version, and build information of this
application.
[-splash] (Optional) Enables the presentation of the application caption or splash screen.
By default, on.
Examples
EXAMPLE 1
Use dbx to configure a powerman.conf file:
dbx -f:conman > /etc/conman.conf
EXAMPLE 2
Use dbx to configure a hosts file:
dbx -f:hosts -d:lnxi.com > /etc/hosts
Clusterworx System Administrator’s Guide

imgr
imgr {
{--image:|-i:} [{--kernel:|-k:}] [{--kernel-revision:|-K:}]
[{--payload:|-p:}] [{--payload.revision:|-P:}] [{--force:|-f:}] [{--list:|-l:}]|
[{-usage|-help|-?}]
}
Description
The imgr command is used to modify the kernel or payload of an existing image. To create a new image,
please refer to Image Management on page 120. The Imaging CLI allows you to perform the following
operations:
Specify a kernel for an image
Specify a payload for an image
Note
If you change a kernel or payload, Clusterworx rebuilds the image but still requires that you commit the
image to VCS. See vcs on page 228.
Parameters
imgr
CLI Commands
{--image:|-i:} The name of the image to modify. By default, Clusterworx selects the version of
the image that was most recently checked in.
[{--kernel:|-k:}]
(Optional) The name of the kernel to modify.
[{--kernel-revision:|-K:}
(Optional) Specify which kernel revision to use. If you do not specify a revision,
you will be asked whether or not to use the latest revision.
[{--payload:|-p:}]
(Optional) The name of the payload.
[{--payload.revision:|-P:}]
(Optional) Specify which payload revision to use. If you do not specify a
revision, you will be asked whether or not to use the latest revision.
[{--force:|-f:}] (Optional) Select the force option to automatically select the latest revision of a
payload or kernel. Selecting this option suppresses the prompt that asks you
whether or not to use the latest revision.
[{--list:|-l:}] (Optional) Display a list of working images.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
Update image Compute to use revision 4 of kernel-2.4:
imgr -i:Compute -k:linux-2.4 -K:4
To use the latest revision of a payload in an image:
imgr -i:MyImage -p:MyPayload
You have not specified the payload revision (latest is 1)
Using latest revisions, continue (yes/no)?
yes
Clusterworx System Administrator’s Guide
217

kmgr
Example 1
218
kmgr
kmgr {
{--name:|-n:} [{--description:|-d:}]
{--path:|-p:} [{--kernel:|-k:}]
[{--architecture:|-a:}] [{--modules:|-m:}] [{--binary:|-b:}] [{--list:|-l:}]|
[{-usage|-help|-?}]
}
Description
The kmgr command is used to create a kernel package from a binary kernel or from a kernel source
directory. The utility copies the binary kernel, .config, System.map, and modules to the kernel directory.
Parameters
{--name:|-n:} The kernel name.
[{--description:|-d:}:]
(Optional) A brief description of the kernel.
{--path:|-p:}
The path to the kernel source.
[{--kernel:|-k:}]
(Optional) The binary name of the kernel. By default,
arch//boot/bzImage
[{--architecture:|-a:}]
(Optional) The kernel architecture: amd64 or ia32 (by default, ia32).
[{--modules:|-m:}] (Optional) The absolute path to lib/modules/.
[{--binary:|-b:}] (Optional) Enable support for binary kernels.
[{--list:|-l:}] (Optional) Display a list of working kernels.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Example 1
Create a new kernel named linux-2.4:
kmgr -n:linux-2.4 -p:/usr/src/linux-2.4.20-8 -a:ia32
Example 2
Create a new kernel, linux-2.6, from a binary kernel:
kmgr -b -n:linux-2.6 -p:/boot/vmlinuz-2.6.16-smp -a:amd64
Clusterworx System Administrator’s Guide

pdcp
pdcp {[
[-w [,...,]]|
[-x [,...,]]|
[-a]|
[-i]|
[-r]|
[-p]|
[-q]|
[-f ]|
[-l ]|
[-t ]|
[-d]]
[ ... ]
}
Description
Pdcp is a parallel copy command used to copy files from a Master Host to all or selected hosts in the cluster.
Unlike rcp which copies files only to an individual host, pdcp can copy files to multiple remote hosts in
parallel. When pdcp receives SIGINT (Ctrl+C), it lists the status of current threads. A second SIGINT within
one second terminates the program.
Parameters
TARGET HOST LIST OPTIONS
Note
If you do not specify any of the following options, the WCOLL environment variable must point to a file
that contains a list of hosts, one per line.
[-w [,...,]]
Note
No spaces are allowed in comma-delimited lists.
(Optional) Execute this operation on the specified host(s). You may enter a
range of hosts or a comma-delimited list of hosts (e.g., host[1-4,7,9]). Any list that
consists of a single “-” character causes pdsh to read the target hosts from stdin,
one per line.
[-x [,...,]]
(Optional) Exclude the specified hosts from this operation. You may enter a
range of hosts or a comma-delimited list of hosts (e.g., host[1-4,7,9]). You may
use this option in conjunction with other target host list options such as -a.
[-a] (Optional) Perform this operation on all hosts in the cluster.
Clusterworx System Administrator’s Guide
pdcp
Example 2
219

pdcp
Example 2
220
[-i] (Optional) Use this option in conjunction with -a or -g to request canonical host
names. By default, pdsh uses reliable host names.
Note
Gender or -g classifications are not currently supported in this version of pdsh.
[-r] (Optional) Copy recursively.
[-p] (Optional) Preserve modification time and modes.
[-q] (Optional) List option values and target hosts.
[-f ] (Optional) Set the maximum number of simultaneous remote copies (by default,
32).
[-l ] (Optional) This option allows you to copy files as another user, subject to
authorization. For BSD rcmd, the invoking user and system must be listed in the
user’s *.rhosts file (even for root).
[-t ] (Optional) Set the connect time-out (by default, 10 seconds)—this is concurrent
with the normal socket level time-out.
[-d] (Optional) Include more complete thread status when receiving SIGINT and,
when finished, display connect and command time statistics on stderr.
[ ... ]
List the source file(s) you want to copy from the Master Host. To copy multiple
files, enter a space-delimited list of files (e.g., pdcp -a /source1 /source2 /
source3 /destination).
Note
The destination is always the last file in the list.
The location to which to copy the file. The destination is set off from the source
by a space.
Example 1
Copy /etc/hosts to foo01–foo05:
pdcp -w foo[01-05] /etc/hosts /etc
Example 2
Copy /etc/hosts to foo0 and foo2–foo5:
pdcp -w foo[0-5] -x foo1 /etc/hosts /etc
Example 3
To copy a file to all hosts in the cluster:
pdcp -a /etc/hosts /etc/
Example 4
To copy a directory recursively:
pdcp -a -r /scratch/dir /scratch
Clusterworx System Administrator’s Guide

Example 5
To copy multiple files to a directory
pdcp -a /etc/passwd /etc/shadow /etc/group /etc
Clusterworx System Administrator’s Guide
pdcp
Example 2
221

pdsh
Example 2
222
pdsh
pdsh {
[[-w [,...,]]|
[-x [,...,]]|
[-a]|
[-i]|
[-q]|
[-f ]|
[-s]|
[-l ]|
[-t ]|
[-u ]|
[-n ]|
[-d]|
[-S]|
[,...,]]
}
Description
Pdsh is a variant of the rsh command. However, unlike rsh which runs commands only on an individual host,
pdsh allows you to issue parallel commands on groups of hosts. When pdsh receives SIGINT (Ctrl+C), it lists
the status of current threads. A second SIGINT within one second terminates the program. If set, the
DSHPATH environment variable is the PATH for the remote shell.
If a command is not specified on the command line, pdsh runs interactively, prompting for commands, then
executing them when terminated with a carriage return. In interactive mode, target hosts that time-out on the
first command are not contacted for subsequent commands. Commands prefaced with an exclamation point
are executed on the local system.
Parameters
TARGET HOST LIST OPTIONS
[-w [,...,]]
Note
No spaces are allowed in comma-delimited lists.
Clusterworx System Administrator’s Guide
(Optional) Execute this operation on the specified host(s). You may enter a
range of hosts or a comma-delimited list of hosts (e.g., host[1-4,7,9]). Any list that
consists of a single “-” character causes pdsh to read the target hosts from stdin,
one per line.
[-x [,...,]]
(Optional) Exclude the specified hosts from this operation. You may enter a
range of hosts or a comma-delimited list of hosts (e.g., host[1-4,7,9]). You may
use this option in conjunction with other target host list options such as -a.
[-a] (Optional) Perform this operation on all hosts in the cluster. By default, a list of
all hosts installed in the cluster is available under /etc/pdsh/machines.

[-i] (Optional) Use this option in conjunction with -a or -g to request canonical host
names. By default, pdsh uses reliable host names.
Note
Gender or -g classifications are not currently supported in this version of pdsh.
[-q] (Optional) List option values and target hosts.
[-f ] (Optional) Set the maximum number of simultaneous remote commands (by
default, 32).
[-s] (Optional) Combine the remote command stderr with stdout. Combining these
commands saves one socket per connection but breaks remote cleanup when
pdsh is interrupted with a Ctrl+C.
[-l ] (Optional) This option allows you to run remote commands as another user,
subject to authorization. For BSD rcmd, the invoking user and system must be
listed in the user’s *.rhosts file (even for root).
[-t ] (Optional) Set the connect time-out (by default, 10 seconds)—this is concurrent
with the normal socket level time-out.
[-u ] (Optional) Limit the amount of time a remote command is allowed to execute
(by default, no limit is defined).
[-n ] (Optional) Set the number of tasks spawned per host. In order for this to be
effective, the underlying remote shell service must support spawning multiple
tasks.
[-d] (Optional) Include more complete thread status when receiving SIGINT and,
when finished, display connect and command time statistics on stderr.
[-S] (Optional) Return the largest of the remote command return values.
[,...,]
The name of the host(s) on which to execute the specified operation. You may
enter a range of hosts or a comma-delimited list of hosts (e.g., host[1-4,7,9]).
Note
No spaces are allowed in comma-delimited lists.
The command you want to execute on the host(s).
Example 1
Run a command on foo7 and foo9–foo15:
pdsh -w foo[7,9-15]
Example 2
Run a command on foo0 and foo2–foo5:
pdsh -w foo[0-5] -x foo1
Clusterworx System Administrator’s Guide
pdsh
Example 2
223

pdsh
Example 2
224
Example 3
In some instances, it is preferable to run pdsh commands using a pdsh shell. To open the shell for a specific
group of hosts, enter the following:
pdsh -w foo[0-5]
From the shell, you may enter commands without specifying the host names:
pdsh> date
To exit the pdsh shell, type exit.
Clusterworx System Administrator’s Guide

pmgr
pmgr {
[[{--description:|-d:}] [{--include:|-i:}]
[{--include-from:|-I:}] [{--location:|-l:}] [{--silent:|-s:}]
[{--exclude:|-x:}]] [{--exclude-from:|-X:}] |
[{-usage|-help|-?}]
}
Description
The pmgr utility generates a Clusterworx payload from an existing Linux installation to use on a specified
host—however, Clusterworx services must be running on the remote host. An exclude list (or file) allows you
to manage which files and directories you want to exclude from the payload (e.g., remote NFS mounted
directories or /proc).
Parameters
[-d:] (Optional) The description of the payload.
[-i:]
(Optional) Enter the name of the file or directory to include in the payload.
When you specify a directory, the payload will include all files and
subdirectories contained in the directory.
Tip
To include a previously excluded item (i.e., a file or directory contained in an excluded directory), enter
the name of the file or subdirectory.
[{--include-from:|-I:}]
(Optional) Enter the name of the file that contains a list of all files to include in
the payload.
[-l:] (Optional) The directory in which to create the payload. By default, the user's
payload working directory with the payload name appended.
[-s:] (Optional) Omit all output other than errors, including the payload creation
progress meter and final summary. This is useful when scripting pmgr.
[-x:]
(Optional) Exclude the named file or directory from the payload. Excluding a
directory excludes all files and subdirectories.
[{--exclude-from:|-X:}]
(Optional) Enter the name of the file that contains a list of all files to exclude
from the payload.
The name of the payload.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Example
The following example demonstrates how to create a new payload from an existing host installation, n2, and
exclude some unwanted directories from the payload:
pmgr -x:/proc:/home:/var/log:/dev/pts:/mnt -h=n2 n2_payload
Clusterworx System Administrator’s Guide
pmgr
Example 2
225

powerman
Example 2
226
powerman
powerman {
[[{--on|-1}]|
[{--off|-0}]|
[{--cycle|-c}]|
[{--reset|-r}]|
[{--flash|-f}]|
[{--unflash|-u}]|
[{--list|-l}]|
[{--query|-q}]|
[{--node|-n}]|
[{--beacon|-b}]|
[{--temp|-t}]|
[{--help|-h}]|
[{--license|-L}]|
[{--destination|-d} host[:port]]|
[{--version|-V}]|
[{--device|-D}]|
[{--telemetry|-T}]|
[{--exprange|-x}]]
[ ...]
}
Description
PowerMan offers power management controls for hosts in clustered environments. Controls include power
on, power off, and power cycle via remote power control (RPC) devices. Target host names are mapped to
plugs on RPC devices in powerman.conf.
Parameters
[{--on|-1}] (Optional) Power hosts On.
[{--off|-0}] (Optional) Power hosts Off.
[{--cycle|-c}] (Optional) Cycle power to hosts.
[{--reset|-r}] (Optional) Assert hardware reset for hosts (if implemented by RPC).
[{--flash|-f}] (Optional) Turn beacon On for hosts (if implemented by RPC).
[{--unflash|-u}] (Optional) Turn beacon Off for hosts (if implemented by RPC).
[{--list|-l}] (Optional) List available hosts. If possible, output is compressed into host ranges.
[{--query|-q}] (Optional) Query plug status of a host(s). If you do not specify a host(s),
PowerMan queries the plug status of all hosts. Status is not cached—PowerManD
queries the appropriate RPC’s each time you use this option. Hosts connected to
RPC’s that cannot be contacted (e.g., due to network failure) are reported as
status unknown. If possible, output is compressed into host ranges.
[{--node|-n}] (Optional) Query host power status (if implemented by RPC). If you do not
specify a host(s), PowerMan queries the power status of all hosts. Please note
that this option returns the host’s power status only, not its operational status. A
host in the Off state could be On at the plug and operating in standby power
mode.
[{--beacon|-b}] (Optional) Query beacon status (if implemented by RPC). If you do not specify a
host(s), PowerMan queries the beacon status of all hosts.
Clusterworx System Administrator’s Guide

[{--temp|-t}] (Optional) Query host temperature (if implemented by RPC). If you do not
specify a host(s), PowerMan queries the temperature of all hosts. Temperature
information is not interpreted by PowerMan and is reported as received from
the RPC on one line per host, prefixed by the host name.
[{--help|-h}] (Optional) Display option summary.
[{--license|-L}] (Optional) Show PowerMan license information.
[{--destination|-d} host[:port]]
(Optional) Connect to a PowerMan daemon on a non-default host and optional
port.
[{--version|-V}] (Optional) Display the PowerMan version number.
[{--device|-D}] (Optional) Display RPC status information. If you specify a host(s), PowerMan
displays only RPC’s that match the host list.
[{--telemetry|-T}] (Optional) Displays RPC telemetry information as commands are processed.
This is useful for debugging device scripts.
[{--exprange|-x}] (Optional) Expand host ranges in query responses.
[ ...]
The name of the host(s) on which to execute the specified operation. You may
enter a range of hosts or a space- or comma-delimited list of hosts (e.g., host[1-4
7 9] or host[1-4 7,9]).
FILES
/usr/sbin/powermand
/usr/bin/powerman
/usr/bin/pm
/etc/powerman/powerman.conf
/etc/powerman/*.dev
Example 1
To power on hosts bar, baz, and n01–n05:
powerman --on bar baz n[01-05]
Example 2
To turn off hosts n4 and n7–n9:
powerman -0 n4,n[7-9]
Clusterworx System Administrator’s Guide
powerman
Example 2
227

vcs
Example 2
228
vcs
vcs {
[{identify| id}]|
[status]|
[include ]|
[exclude ]|
[archive ]|
[import -R: -M: [-n:] [-d:] []]|
[commit [-n:] [-d:] []]|
[branch [-n:] [-d:] []]|
[{checkout | co} -R: -M: [-r:||]]|
[{update | up} [-r:||] []]|
[name [-R:] [-M:] [-r:||] ]|
[describe [-R:] [-M:] [-r:||] ]|
[{narrate | log} [-R: -M:] [-r:||]]|
[iterate [-R: [-M: [-r:||]]]]|
[list]|
[{-usage|-help|-?}]
}
Description
Manage version controlled directories within Clusterworx.
Parameters
[{identify| id}] (Optional) Display information about the module contained in the current
working directory.
[status] (Optional) Display the status of the files within the current working directory
including whether they have been added (A), modified (M) or deleted (D).
[include ] (Optional) Add provided list of files to the include list. You may also use this
option to override a specific file exclusion.
[exclude ] (Optional) Add provided list of files to the exclude list. Excluding files allows you
to remove files that may cause problems (e.g., when trying to archive files).
[archive ] (Optional) Create an archive of the current working directory in the given file.
This option may be used to archive a host and include it in VCS as a payload.
[import -R: -M: [-n:] [-d:] []]
(Optional) Create a new module with the provided list of files or all of the
current working directory.
[commit [-n:] [-d:] []]
(Optional) Insert a new revision in the module using the provided list of files or
any working copy modifications.
[branch [-n:] [-d:] []]
(Optional) Insert a new revision that is not on tip using the provided list of files
or any working copy modifications.
[{checkout| co} -R: -M: [-r:||]]
(Optional) Retrieve an existing revision from a module. The contents of the
module will be stored in a new directory named after the module.
Clusterworx System Administrator’s Guide

[{update| up} [-r:||] []]
(Optional) Update the current directory to use the latest tip revision of a
branch (3.4), the main trunk of a specific branch (4), or a branch with a specific
name (Golden). The files option allows you to update a specific file contained in
a payload.
[name [-R:] [-M:] [-r:||] ]
(Optional) Add, modify or delete the optional name or alias of a revision. Names
are unique revision identifiers for the entire module. A blank for the name will
delete the previous value.
[describe [-R:] [-M:] [-r:||] ]
(Optional) Add, modify or delete the optional description of a revision. A blank
for the description will delete the previous value.
[{narrate| log} [-R: -M:] [-r:||]]
(Optional) Display the history of a module revision.
[iterate [-R: [-M: [-r:||]]]]
(Optional) Display the organizational information of the version service.
[list] (Optional) Display a list of all category types (payloads, kernels, and images) that
have been checked into VCS.
[{-usage|-help|-?}] (Optional) Display help information for the command and exit. All other options
are ignored.
Examples
EXAMPLE 1
Display a list of images contained in the Version Control System:
vcs iterate -R:images
EXAMPLE 2
Display a list of files that have changed since the last time the Compute payload was checked out:
cd /opt/cwx/imaging/root/payloads/Compute
vcs status
EXAMPLE 3
List current versions of all category types (payloads, kernels, and images) checked into VCS:
vcs list
Images
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MyImage (1) - Kernel: MyKernel (3) Payload: MyPayload (6.1.4)
TestImage (1) - Kernel: Compute (2) Payload: SLES10 (23)
Kernels
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MyKernel (5)
Compute (2)
Payloads
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MyPayload (6.1.7)
SLES9 (34)
SLES10 (23)
Clusterworx System Administrator’s Guide
vcs
Example 2
229

vcs
Example 2
230
EXAMPLE 4
Check out a specific revision, 8, of a version controlled payload named Compute:
vcs checkout -R:payloads -M:Compute -r:8
EXAMPLE 5
Use VCS to make sure you have the latest revision of what was originally checked out in the previous
example:
cd /opt/cwx/imaging//payloads/Compute
vcs update
Clusterworx System Administrator’s Guide

xms
xms
Description
This command displays the name, build date, build time, version number and build number for each module
installed in Clusterworx. The ClusterworxRelease module displays the version information for the
Clusterworx installation on the system.
Examples
EXAMPLE 1
Display all build information for each module:
xms
2004-11-15 23:44:48.269-0700 1.1.3-5 Authentication
2004-11-15 23:45:02.268-0700 1.1.4-5 AuthenticationServer
2004-12-21 13:28:14.364-0700 3.2.2-8 ClusterworxRelease
2004-11-15 23:45:12.265-0700 1.1.3-5 Command
2004-11-15 23:45:29.268-0700 1.1.4-5 CommandDesktop
2004-11-15 23:45:47.294-0700 1.1.4-4 CommandServer
2004-11-15 23:46:31.279-0700 1.2.1-4 DHCP
2004-11-15 15:51:54.322-0700 1.2.2-7 DHCPServer
2004-11-15 23:45:57.265-0700 1.1.1-4 Database
2004-12-01 13:40:30.318-0700 1.1.0-8 DatabaseConsole
2004-11-15 23:46:22.264-0700 2.1.1-4 DatabaseServer
2004-11-15 23:46:57.268-0700 1.1.2-5 DistributionServer
2004-11-15 23:47:40.287-0700 1.2.1-4 File
2004-11-15 23:47:50.263-0700 1.1.4-4 FileConsole
2004-11-24 16:21:58.362-0700 1.2.1-8 FileDesktop
2004-11-15 23:48:24.266-0700 1.1.4-4 FileServer
2004-12-08 14:02:56.356-0700 1.3.2-9 Foundation
2004-11-15 23:48:51.282-0700 2.0.1-4 Host
2004-12-17 12:00:05.357-0700 1.0.2-8 HostConsole
2004-12-17 12:01:19.363-0700 2.0.2-11 HostDesktop
2004-11-15 23:49:47.265-0700 2.0.2-4 HostServer
2004-11-15 23:49:59.261-0700 1.1.3-4 Icebox
2004-12-17 12:02:46.325-0700 1.1.4-10 IceboxDesktop
2004-11-15 23:50:35.282-0700 1.1.4-4 IceboxServer
2004-11-15 23:50:46.262-0700 1.2.1-4 Image
2004-11-15 23:51:01.264-0700 1.2.2-4 ImageConsole
2004-12-17 12:03:51.363-0700 1.3.2-11 ImageDesktop
2004-12-08 14:06:59.367-0700 1.2.2-9 ImageServer
2004-11-15 23:52:29.287-0700 1.2.1-4 Instrumentation
2004-09-22 15:32:02.549-0600 1.0.0-0 InstrumentationConsole
2004-12-17 12:06:11.318-0700 1.2.2-10 InstrumentationServer
2004-12-17 12:06:54.383-0700 1.1.4-8 Integration
2004-11-15 23:53:15.265-0700 1.2.1-4 Kernel
2004-11-15 23:53:30.265-0700 1.2.2-4 KernelConsole
2004-11-15 23:53:49.283-0700 1.2.2-4 KernelServer
2004-11-15 23:54:04.264-0700 2.0.2-4 License
2004-11-15 23:54:19.266-0700 2.0.1-4 LicenseDesktop
2004-11-15 23:54:36.272-0700 2.0.2-4 LicenseServer
2004-11-15 23:54:50.266-0700 1.0.1-4 Log
2004-11-15 23:55:05.315-0700 1.0.2-4 LogServer
2004-12-17 12:07:43.329-0700 1.2.2-9 Migration
2004-12-17 12:08:15.318-0700 1.3.1-9 Payload
2004-11-15 23:55:52.262-0700 1.3.2-4 PayloadConsole
2004-12-21 13:25:56.321-0700 1.3.2-11 PayloadServer
2004-11-15 23:56:28.262-0700 1.3.0-4 Provisioning
2004-11-24 16:31:23.369-0700 1.1.0-8 ProvisioningConsole
2004-12-17 12:09:40.363-0700 1.3.0-10 ProvisioningDesktop
2004-11-15 23:57:34.269-0700 1.3.0-4 ProvisioningServer
- - : : . - . . - Testing
2004-12-17 12:10:54.371-0700 1.0.2-8 Tree
2004-11-24 16:33:14.369-0700 1.0.2-8 TreeDesktop
2004-11-15 23:58:23.267-0700 1.0.2-4 TreeServer
Clusterworx System Administrator’s Guide
xms
Example 2
231

xms
Example 2
232
2004-11-15 23:58:40.265-0700 1.0.2-4 UserConsole
2004-12-17 12:13:30.367-0700 1.2.2-11 UserDesktop
2004-11-15 23:59:09.298-0700 1.2.2-4 Versioning
2004-11-15 23:59:25.268-0700 1.2.3-4 VersioningConsole
2004-12-17 12:14:23.318-0700 1.2.3-9 VersioningServer
2004-11-15 23:59:57.286-0700 1.2.1-4 Workload
2004-11-16 00:00:18.322-0700 1.2.2-4 WorkloadDesktop
2004-11-15 09:17:48.250-0700 3.0.1-1 XeroOne
- - : : . - . . - license
EXAMPLE 2
Display all modules based on build time:
xms -o:t
2004-09-22 15:32:02.549-0600 1.0.0-0 InstrumentationConsole
2005-05-24 15:20:10.273-0600 1.1.6-2 AuthenticationServer
2005-05-24 15:20:15.270-0600 1.2.0-2 Command
2005-05-24 15:20:52.414-0600 1.2.3-2 DHCP
2005-05-24 15:21:22.277-0600 1.1.6-2 FileServer
2005-05-24 15:21:28.356-0600 2.1.0-2 Host
2005-05-24 15:21:49.376-0600 2.1.0-1 HostServer
2005-05-24 15:21:56.306-0600 1.1.5-1 Icebox
2005-05-24 15:22:03.286-0600 1.2.0-1 IceboxServer
2005-05-24 15:22:40.429-0600 1.2.3-1 Instrumentation
2005-05-24 15:22:52.336-0600 1.1.6-1 Integration
2005-05-24 15:23:18.274-0600 2.0.3-1 LicenseDesktop
2005-05-24 15:23:34.467-0600 1.1.0-1 Log
2005-05-24 15:23:44.351-0600 1.3.0-1 Migration
2005-05-24 15:24:14.374-0600 1.5.0-2 Provisioning
2005-05-24 15:24:27.303-0600 1.5.0-2 ProvisioningServer
2005-05-24 15:24:33.402-0600 1.0.4-2 Tree
2005-05-24 15:24:36.406-0600 1.1.0-2 TreeDesktop
2005-05-24 15:24:39.390-0600 1.0.5-2 TreeServer
2005-05-24 16:12:49.230-0600 1.1.5-7 Authentication
2005-05-31 16:17:02.231-0600 1.4.0-3 PayloadConsole
2005-06-01 12:54:36.230-0600 1.1.4-4 DistributionServer
2005-06-01 13:26:49.229-0600 2.1.3-3 DatabaseServer
2005-06-01 13:27:34.231-0600 1.3.0-4 File
2005-06-01 13:27:51.230-0600 1.2.0-4 FileConsole
2005-06-01 13:48:46.229-0600 1.4.0-2 Image
2005-06-01 13:49:02.231-0600 1.4.0-2 ImageConsole
2005-06-01 13:51:54.230-0600 2.0.4-3 LicenseServer
2005-06-01 13:52:18.230-0600 1.1.0-3 LogServer
2005-06-01 13:53:54.229-0600 1.2.6-3 VersioningServer
2005-06-01 14:40:00.229-0600 1.2.4-4 Versioning
2005-06-08 15:53:31.230-0600 1.2.0-4 Database
2005-06-23 11:05:45.228-0600 1.2.0-3 CommandServer
2005-06-23 11:06:02.227-0600 1.2.3-3 FileDesktop
2005-06-23 11:07:09.228-0600 1.4.0-3 ImageServer
2005-06-23 11:08:04.230-0600 1.2.3-2 Kernel
2005-06-23 11:10:20.229-0600 1.3.0-3 KernelConsole
2005-06-23 11:10:41.229-0600 1.2.4-3 KernelServer
2005-06-23 11:11:40.228-0600 1.3.0-4 UserDesktop
2005-06-23 18:28:33.228-0600 1.0.4-10 UserConsole
2005-06-30 11:03:00.429-0600 4.0.0-11 XeroOne
2005-06-30 14:11:48.239-0600 1.2.0-5 DatabaseConsole
2005-06-30 14:12:15.232-0600 1.3.0-5 DHCPServer
2005-06-30 14:14:12.231-0600 1.5.0-1 ProvisioningDesktop
2005-06-30 14:15:25.233-0600 1.3.0-5 VersioningConsole
2005-07-12 15:42:21.271-0600 1.4.0-7 Foundation
2005-07-12 15:46:31.234-0600 1.1.0-13 HostConsole
2005-07-12 15:49:28.239-0600 1.2.0-3 IceboxDesktop
2005-07-12 16:05:13.235-0600 1.3.0-3 ProvisioningConsole
2005-07-13 15:52:57.238-0600 2.0.4-3 License
2005-07-13 17:06:07.237-0600 2.1.0-9 HostDesktop
2005-07-15 10:02:12.233-0600 3.3.0-22 ClusterworxRelease
2005-07-15 10:30:23.235-0600 1.2.5-9 InstrumentationServer
2005-07-15 10:30:44.246-0600 1.2.0-6 CommandDesktop
2005-07-15 10:31:36.236-0600 1.5.0-9 ImageDesktop
2005-07-15 10:32:32.235-0600 1.4.0-3 Payload
2005-07-15 10:33:06.234-0600 1.4.0-10 PayloadServer
Clusterworx System Administrator’s Guide

Glossary
Anti-aliasing A technique used to smooth images and text to improve their
appearance on screen.
Architecture-independent Allows hardware or software to function regardless of
hardware platform. Both Clusterworx and Icebox work together to deliver seamless cluster management
functionality. Because Icebox physically monitors individual processor temperatures and has direct power
control, administrators are not dependent on specific motherboards.
Baud rate A unit of measure that describes data transmission rates (in bits per second).
Block size The largest amount of data that the file system will allocate contiguously.
boot.profile A file that contains instructions on how to boot a host.
Boot utilities Utilities added to the RAM Disk that run during the boot process. Boot utilities allow you to
create such things as custom, pre-finalized scripts using utilities that are not required for standard Linux
versions.
Cluster Clustering is a method of linking multiple computers or compute hosts together to form a unified
and more powerful system. These systems can perform complex computations at the same level as a
traditional supercomputer by dividing the computations among all of the processors in the cluster, then
gathering the data once the computations are completed. A cluster refers to all of the physical elements of
your Linux Networx solution, including the Clusterworx Master Host, compute hosts, Clusterworx, Icebox,
UPS, high-speed network, storage, and the cabinet.
Clusterworx Master Host The Clusterworx Master Host is the host that controls the remaining hosts in a
cluster (for large systems, multiple masters may be required). This host is reserved exclusively for managing
the cluster and is not typically available to perform tasks assigned to the remaining hosts.
Command-line Interface (CLI) A user interface to the Icebox through which the administrator may enter
commands to perform additional tasks and configurations on the system. The CLI is accessible via the Serial
Console port, a Telnet session, and SSH.
DHCP Dynamic Host Configuration Protocol. Assigns dynamic IP addresses to devices on a network.
Diskless host A host whose operating system and file system are installed into physical memory. This
method is generally referred to as RAMfs or TmpFS.
EBI An ELF Binary Image that contains the kernel, kernel options, and a RAM Disk.
Event engine Allows administrators to trigger events based on a change in system status (e.g., when
processors rise above a certain temperature or experience a power interruption). Administrators may
configure triggers to inform users of a specific event or to take a specific action.
Ext Original extended file system for Linux systems. Provides 255-character filenames and supports files
sizes up to 2 Gigabytes.
Clusterworx System Administrator’s Guide
233

Glossary
234
Ext2 The second extended file system for Linux systems. Offers additional features that make the file
system more compatible with other file systems and provides support for file system extensions, larger file
sizes (up to 4 Terabytes), symbolic links, and special file types.
Ext3 Provides a journaling extension to the standard ext2 file system on Linux. Journaling reduces time
spent recovering a file system, critical in environments where high availability is important.
GUI A Graphical User Interface employs the use of visual cues and indicators (not just text) to help you
navigate through your system and perform system operations. Clusterworx uses a GUI to provide intuitive
cluster navigation and configuration.
Group A group refers to an organization with shared or similar needs. A cluster may contain multiple groups
with unique or shared rights and privileges. A group may also refer to an administrator-defined collection of
hosts within a cluster that perform tasks such as data serving, Web serving, and computational number
crunching.
Hardware flow control A Clusterworx control setting for Icebox host and auxiliary ports. Enabling
hardware flow control allows a transaction recipient to tell the transmitter to stop sending data (e.g., if the
recipient’s buffer is getting too full). This can eliminate data loss due to buffer overflow.
Health monitoring An element of the Instrumentation Service used to track and display the state of all
hosts in the system. Health status icons appear next to each host viewed with the instrumentation service or
from the navigation tree to provide visual cues about system health. Similar icons appear next to clusters,
partitions, and regions to indicate the status of hosts contained therein.
Host An individual server or computer within the cluster that operates in parallel with other hosts in the
cluster. Hosts may contain multiple processors.
Icebox An important piece of the Linux Networx cluster management solution, the Icebox is an
architecture-independent hardware device that provides remote monitoring and advanced power control for
hosts installed in your cluster. The Icebox can monitor up to four processors per host and is accurate to ± 1
degrees Celsius. The Icebox also contains advanced serial switching that allows administrators to maintain a
redundant serial network.
image.profile A file used to generate boot.profile. This file contains information about the image, including
the payload, kernel, and partition layout.
IP address A 32-bit number that identifies each sender or receiver of information. In order to transmit or
receive information on the network, each Icebox must have its own unique IP address (which can be set by
the administrator).
Kerberos Kerberos is a network authentication protocol. It is designed to provide strong authentication for
client/server applications by using secret-key cryptography.
Kernel The binary kernel, a .config file, System.map, and modules (if any).
LDAP Lightweight Directory Access Protocol is an Internet protocol that email programs use to look up
contact information from a server.
Listener A listener constantly reads and reviews system metrics. Configuring listener thresholds allows you
to trigger loggers to address specific issues as they arise.
Logger The action taken when a threshold exceeds its maximum or minimum value. Common logger events
include sending messages to the centralized Clusterworx message log, logging to a file, logging to the serial
console, and shutting down the host.
MAC address A hardware address unique to each device installed in the system.
Metrics Used to track logger events and report data to the instrumentation service (where it may be
monitored).
Clusterworx System Administrator’s Guide

MIB Management Information Base. The MIB is a tree-shaped information structure that defines what sort
of data can be manipulated via SNMP.
Monitors Monitors run periodically on hosts and provide the metrics that are gathered, processed, and
displayed using the Clusterworx instrumentation service.
Multi-user Allows multiple administrators to simultaneously log into and administer the cluster.
Netmask A string of 0's and 1's that mask or screen out the network part of an IP address so only the host
computer portion of the address remains. The binary 1's at the beginning of the mask turn the network ID
portion of the IP address into 0's. The binary 0's that follow allow the host ID to remain. A commonly used
netmask is 255.255.255.0 (255 is the decimal equivalent of a binary string of eight ones).
NIS Network Information Service makes information available throughout the entire network.
Node See Host.
Partition Partitions are used to separate clusters into non-overlapping collections of hosts.
Payload A compressed file system that is downloaded via multicast during the provisioning process.
Plug-ins Programs or utilities added to the boot process that expand system capabilities.
RAID Redundant Array of Independent Disks. Provides a method of accessing multiple, independent disks as
if the array were one large disk. Spreading data over multiple disks improves access time and reduces the
risk of losing all data if a drive fails.
RAM Disk A small, virtual drive that is created and loaded with the utilities that are required when you
provision the host. In order for host provisioning to succeed, the RAM Disk must contain specific boot
utilities. Under typical circumstances, you will not need to add boot utilities unless you are creating
something such as a custom, pre-finalized script that needs utilities not required by standard Linux versions
(e.g., modprobe).
RHEL RedHat Enterprise Linux.
Region A region is a subset of a partition and may share any hosts that belong to the same partition—even if
the hosts are currently used by another region.
Role Roles are associated with groups and privileges, and define the functionality assigned to each group.
Secure remote access The ability to monitor and control the cluster from a distant location through an
SSL-encrypted connection. Administrators have the benefit of secure remote access to their clusters through
any Java-enhanced browser. Clusterworx can be used remotely, allowing administrators access to the cluster
from anywhere in the world.
Secure Shell (SSH) SSH is used to create a secure connection to the CLI. Connections made with SSH are
encrypted and safe to use over insecure networks.
SLES SuSE Linux Enterprise Server.
Version branching The ability to modify an existing payload, kernel, or image under version control and
check it back into VCS as a new, versioned branch of the original item.
Version Control System (VCS) The Clusterworx Version Control System allows users with privileges to
manage changes to payloads, kernels, or images (similar in nature to managing changes in source code with a
version control system such as CVS). The Version Control System supports common Check-Out and
Check-In operations.
Versioned copy A versioned copy of a payload, kernel, or image is stored in VCS.
Working copy A working copy of a payload, kernel, or image is currently present in the working area only
(e.g., /opt/cwx/imaging// payloads). Working copies are not stored in VCS.
Clusterworx System Administrator’s Guide
Glossary
235

Glossary
236
Clusterworx System Administrator’s Guide

Appendix
Pre-configured Metrics
The Clusterworx instrumentation service supports the following metrics. For
information about defining and using metrics, see Metrics on page 175.
Architecture
Metric Name Format and Description
Architecture hosts.{host.moniker}.os.architecture
The host's hardware architecture.
CPU
Metric Name Format and Description
CPU Bogomips hosts.{host.moniker}.cpus.[#].bogomips
A measurement that indicates, in a relative way, how fast the processor runs.
CPU Cache hosts.{host.moniker}.cpus.[#].cache
The processor cache size.
CPU Count hosts.{host.moniker}.cpus.[#]
The number of processors on the host.
CPU Family hosts.{host.moniker}.cpus.[#].family
The processor family type.
CPU FPU hosts.{host.moniker}.cpus.[#].fpu
If the processor has a floating point unit.
CPU Hardware Interrupts hosts.{host.moniker}.cpus.[#].irq.hard
The cycles used by a specific CPU for hardware interrupts.
CPU Hardware Interrupts hosts.{host.moniker}.cpu.irq.hard
Aggregate
The total cycles used by all CPUs for hardware interrupts.
CPU I/O Wait hosts.{host.moniker}.cpus.[#].iowait
The cycles used by a specific CPU waiting for I/O.
Clusterworx System Administrator’s Guide
237

Pre-configured Metrics
CPU
238
Metric Name Format and Description
CPU I/O Wait Aggregate hosts.{host.moniker}.cpu.iowait
The total cycles used by all CPUs waiting for I/O.
CPU Level hosts.{host.moniker}.cpus.[#].level
The identifying level of the processor.
CPU Model hosts.{host.moniker}.cpus.[#].model
The model of the processor.
CPU Model Name hosts.{host.moniker}.cpus.[#].name
The model name of the processor.
CPU Nice hosts.{host.moniker}.cpus.[#].nice
The cycles used by a specific CPU in user mode with low priority.
CPU Nice Aggregate hosts.{host.moniker}.cpu.nice
CPU Software Interrupts
The total cycles used by all CPUs in user mode with low priority.
hosts.{host.moniker}.cpus.[#].irq.soft
The cycles used by a specific CPU for software interrupts.
CPU Software Interrupts hosts.{host.moniker}.cpu.irq.soft
Aggregate
The total cycles used by all CPUs for software interrupts.
CPU Speed hosts.{host.moniker}.cpus.[#].speed
The maximum speed of the processor.
CPU Stepping hosts.{host.moniker}.cpus.[#].stepping
Clusterworx System Administrator’s Guide
The revision level of the processor within the processor family.
CPU System hosts.{host.moniker}.cpus.[#].system
The cycles used by a specific CPU in kernel mode.
CPU System Aggregate hosts.{host.moniker}.cpu.system
The total cycles used by all CPUs in kernel mode.
CPU Total hosts.{host.moniker}.cpus.[#].total
The sum of User, Nice, and System for a specific CPU.
CPU Total Aggregate hosts.{host.moniker}.cpu.total
The sum of User, Nice, and System for all CPUs in the host.
CPU User hosts.{host.moniker}.cpus.[#].user
The cycles used by a specific processor in user mode.
CPU User Aggregate hosts.{host.moniker}.cpu.user
The total cycles used by all CPUs in user mode.
CPU Vendor hosts.{host.moniker}.cpus.[#].vendor
The name of the processor vendor.

Disk
Metric Name Format and Description
Disk Aggregate Block Reads hosts.{host.moniker}.disk.block.reads
The number of blocks read from all disks.
Disk Aggregate Block Writes hosts.{host.moniker}.disk.block.writes
The number of blocks written to all disks.
Disk Aggregate Capacity hosts.{host.moniker}.disk.capacity
Disk Aggregate Capacity
Free
Disk Aggregate Capacity
Used
The disk capacity for all disks.
hosts.{host.moniker}.disk.capacity.free
The disk capacity free for all disks.
hosts.{host.moniker}.disk.capacity.used
The disk capacity used for all disks.
Disk Aggregate I/O Read hosts.{host.moniker}.disk.io.reads
The number of I/O reads from all disks.
Disk Aggregate I/O Writes hosts.{host.moniker}.disk.io.writes
Disk Aggregate Percentage
Used
The number of I/O writes to all disks.
hosts.{host.moniker}.disk.percentage.used
The disk percentage used for all disks.
Disk Block Reads hosts.{host.moniker}.disks.block.reads
The number of blocks read from a disk.
Disk Block Writes hosts.{host.moniker}.disks.block.writes
The number of blocks written to a disk.
Disk Capacity hosts.{host.moniker}.disks.capacity
The disk capacity for each disk.
Disk Capacity Free hosts.{host.moniker}.disks.capacity.free
The disk capacity free for each disk.
Disk Capacity Used hosts.{host.moniker}.disks.capacity.used
The disk capacity used for each disk.
Disk I/O Read hosts.{host.moniker}.disks.io.reads
The number of I/O reads from a disk.
Disk I/O Writes hosts.{host.moniker}.disks.io.writes
The number of I/O writes to a disk.
Disk Mount Point hosts.{host.moniker}.disks.mountpoint
The mount point for each partition.
Disk Percentage Used hosts.{host.moniker}.disks.percentage.used
The disk percentage used for each disk.
Pre-configured Metrics
Disk
Clusterworx System Administrator’s Guide
239

Pre-configured Metrics
Icebox
240
EDAC (BlueSmoke)
Metric Name Format and Description
DIMM CE hosts.{host.moniker}.bluesmoke.CE
The number of Correctable Errors identified on all of the DIMMs. This metric is typically
used with listeners.
DIMM CE hosts.bluesmoke.CE.warning
A warning message displayed in the GUI to indicate a correctable error.
DIMM UE hosts.{host.moniker}.bluesmoke.UE
The number of Uncorrectable Errors identified on all of the DIMMs. This metric is
typically used with listeners.
DIMM UE hosts.bluesmoke.UE.warning
A warning message displayed in the GUI to indicate an uncorrectable error.
Icebox
Metric Name Format and Description
Icebox Average
iceboxes.{host.moniker}.ports.temperature
Temperatures
The average temperature per port from the Icecard in degrees Celsius.
Icebox Temperature iceboxes.{host.moniker}.ports.temperatures
Image
Kernel
Clusterworx System Administrator’s Guide
The temperatures from the Icecard in degrees Celsius for each port.
Metric Name Format and Description
Image Name hosts.{host.moniker}.image.name
The image last used to provision.
Image Revision hosts.{host.moniker}.image.revision
The image revision last used to provision.
Metric Name Format and Description
Kernel Boot Time hosts.{host.moniker}.kernel.boottime
Boot time, in seconds, since the epoch (January 1, 1970).
Kernel Contexts hosts.{host.moniker}.kernel.contexts
The number of context switches the system has undergone.
Kernel Interrupts hosts.{host.moniker}.kernel.interrupts
The number of interrupts received from the system since boot.

Metric Name Format and Description
Kernel Name hosts.{host.moniker}.kernel.name
The kernel last used to provision.
Kernel Pages In hosts.{host.moniker}.kernel.pages.in
The number of pages the system paged in from disk.
Kernel Pages Out hosts.{host.moniker}.kernel.pages.out
The number of pages the system paged out to disk.
Kernel Processes hosts.{host.moniker}.kernel.processes
The number of forks since boot.
Kernel Revision hosts.{host.moniker}.kernel.revision
The revision of kernel used to provision.
Kernel Swaps In hosts.{host.moniker}.kernel.swaps.in
The number of swap pages that have been brought in.
Kernel Swaps Out hosts.{host.moniker}.kernel.swaps.out
The number of swap pages that have been sent out.
Kernel Version hosts.{host.moniker}.os.version
The version of the currently running Linux kernel
Load
Metric Name Format and Description
Load 1 Minute hosts.{host.moniker}.load.1m
The number of tasks in the run state averaged over 1 minute.
Load 15 Minutes hosts.{host.moniker}.load.15m
The number of tasks in the run state averaged over 15 minutes.
Load 5 Minutes hosts.{host.moniker}.load.5m
The number of tasks in the run state averaged over 5 minutes.
Load Tasks hosts.{host.moniker}.load.jobs
The total number of tasks.
Load Running Tasks hosts.{host.moniker}.load.jobs.running
LinuxBIOS
The number of tasks currently running.
Metric Name Format and Description
LinuxBIOS Bootmode hosts.{host.moniker}.linuxbios.bootmode
The current operational status of LinuxBIOS.
Pre-configured Metrics
Load
Clusterworx System Administrator’s Guide
241

Pre-configured Metrics
LS-1 1950i and 1435a
242
LS-1 1950i and 1435a
Metric Name Format and Description
IPMITool Fan 1A Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_1A_RPM.description
Note
See also, LS-1 1435a Only on page 243.
Clusterworx System Administrator’s Guide
IPMITool Fan 1A Speed
IPMITool Fan 1B Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_1B_RPM.description
IPMITool Fan 1B Speed
IPMITool Fan 1C Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_1C_RPM.description
IPMITool Fan 1C Speed
IPMITool Fan 1D Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_1D_RPM.description
IPMITool Fan 1D Speed
IPMITool Fan 2A Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_2A_RPM.description
IPMITool Fan 2A Speed
IPMITool Fan 2B Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_2B_RPM.description
IPMITool Fan 2B Speed
IPMITool Fan 2C Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_2C_RPM.description
IPMITool Fan 2C Speed
IPMITool Fan 2D Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_2D_RPM.description
IPMITool Fan 2D Speed
IPMITool Fan 3A Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_3A_RPM.description
IPMITool Fan 3A Speed
IPMITool Fan 3B Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_3B_RPM.description
IPMITool Fan 3B Speed
IPMITool Fan 3C Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_3C_RPM.description
IPMITool Fan 3C Speed
IPMITool Fan 3D Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_3D_RPM.description
IPMITool Fan 3D Speed
IPMITool Fan 4A Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_4A_RPM.description
IPMITool Fan 4A Speed
IPMITool Fan 4B Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_4B_RPM.description
IPMITool Fan 4B Speed
IPMITool Fan 4C Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_4C_RPM.description
IPMITool Fan 4C Speed
IPMITool Fan 4D Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_4D_RPM.description
IPMITool Fan 4D Speed

LS-1 2950i
Metric Name Format and Description
IPMITool Fan 1 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_1_RPM.description
LS-1 1435a Only
Note
IPMITool Fan 1 Speed
IPMITool Fan 2 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_2_RPM.description
IPMITool Fan 2 Speed
IPMITool Fan 3 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_3_RPM.description
IPMITool Fan 3 Speed
IPMITool Fan 4 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_4_RPM.description
IPMITool Fan 4 Speed
IPMITool Fan 5 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_5_RPM.description
IPMITool Fan 5 Speed
IPMITool Fan 6 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_6_RPM.description
IPMITool Fan 6 Speed
By default, these metrics are disabled. These are useful only if no LS-1 1950i hosts are installed
Metric Name Format and Description
IPMITool Fan 1 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_1_RPM.description
IPMITool Fan 1 Speed
IPMITool Fan 2 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_2_RPM.description
IPMITool Fan 2 Speed
IPMITool Fan 3 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_3_RPM.description
IPMITool Fan 3 Speed
IPMITool Fan 4 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_4_RPM.description
IPMITool Fan 4 Speed
IPMITool Fan 5 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_5_RPM.description
IPMITool Fan 5 Speed
IPMITool Fan 6 Speed hosts.{host.moniker}.ipmitool.IPMITool-FAN_6_RPM.description
IPMITool Fan 6 Speed
Pre-configured Metrics
LS-1 2950i
Clusterworx System Administrator’s Guide
243

Pre-configured Metrics
Memory
244
Memory
Metric Name Format and Description
Memory Active hosts.{host.moniker}.memory.active
Clusterworx System Administrator’s Guide
The amount of active memory.
Memory Active Anon hosts.{host.moniker}.memory.active.anon
The amount of anonymous active memory.
Memory Active Cached hosts.{host.moniker}.memory.active.cache
The amount of active cached memory.
Memory Big Free hosts.{host.moniker}.memory.big.free
The amount of free big memory.
Memory Buffered hosts.{host.moniker}.memory.buffers
The amount of buffered memory.
Memory Cached hosts.{host.moniker}.memory.cached
The amount of cached memory.
Memory Committed hosts.{host.moniker}.memory.committed
The amount of committed memory.
Memory Dirty hosts.{host.moniker}.memory.dirty
The amount of dirty memory.
Memory Free hosts.{host.moniker}.memory.free
The total amount of free memory.
Memory High hosts.{host.moniker}.memory.high
The amount of used high memory.
Memory High Free hosts.{host.moniker}.memory.high.free
The amount of free high memory.
Memory Huge Pages Free hosts.{host.moniker}.memory.hugepages.free
The amount of huge pages available.
Memory Huge Pages Size hosts.{host.moniker}.memory.hugepages.size
The size of a huge page.
Memory Huge Pages Total hosts.{host.moniker}.memory.hugepages
The total amount of huge pages available.
Memory Inactive hosts.{host.moniker}.memory.inactive
The amount of inactive memory.
Memory Inactive Clean hosts.{host.moniker}.memory.inactive.clean
The amount of clean inactive memory.
Memory Inactive Dirty hosts.{host.moniker}.memory.inactive.dirty
The amount of dirty inactive memory.
Memory Inactive Laundry hosts.{host.moniker}.memory.inactive.laundry
The amount of inactive laundry memory.

Metric Name Format and Description
Memory Inactive Target hosts.{host.moniker}.memory.inactive.target
The target amount of inactive memory.
Memory Low hosts.{host.moniker}.memory.low
The amount of used low memory.
Memory Low Free hosts.{host.moniker}.memory.low.free
The amount of free low memory.
Memory Mapped hosts.{host.moniker}.memory.mapped
The amount of mapped memory.
Memory Page Tables hosts.{host.moniker}.memory.pagetables
The number of page tables available.
Memory Shared hosts.{host.moniker}.memory.shared
The total amount of shared memory.
Memory Slab hosts.{host.moniker}.memory.slab
The size of the memory slab used for dynamic kernel data.
Memory Swap hosts.{host.moniker}.memory.swap
The amount of free swap space.
Memory Swap Cached hosts.{host.moniker}.memory.swap.cached
The amount of cached swap.
Memory Swap Free hosts.{host.moniker}.memory.swap.free
The amount of free swap space.
Memory Total hosts.{host.moniker}.memory.total
The total amount of memory.
Memory VMalloc Chunk hosts.{host.moniker}.memory.vmalloc.chunk
The size of a VMalloc chunk.
Memory VMalloc Total hosts.{host.moniker}.memory.vmalloc
The total amount of VMalloc.
Memory VMalloc Used hosts.{host.moniker}.memory.vmalloc.used
The amount of VMalloc used.
Memory Writeback hosts.{host.moniker}.memory.writeback
The amount of writeback memory.
Pre-configured Metrics
Memory
Clusterworx System Administrator’s Guide
245

Pre-configured Metrics
Network
246
Network
Metric Name Format and Description
Network Bytes Received hosts.{host.moniker}.network..rx.bytes
Network Bytes Received
Aggregate
Network Compressed Bytes
Received
Network Compressed Bytes
Received Aggregate
Network Compressed Bytes
Transmitted
Network Compressed Bytes
Transmitted Aggregate
Network Dropped Packets
Received
Network Dropped Packets
Received Aggregate
Clusterworx System Administrator’s Guide
The total number of bytes received on an interface.
hosts.{host.moniker}.network..rx.bytes
The total number of bytes received on all interfaces.
hosts.{host.moniker}.network..rx.compressed
The amount of compressed traffic received on an interface.
hosts.{host.moniker}.network..rx.compressed
The amount of compressed traffic received on all interfaces.
hosts.{host.moniker}.network..tx.compressed
The amount of data compressed during transmission on an interface.
hosts.{host.moniker}.network..tx.compressed
The amount of data compressed during transmission on all interfaces.
hosts.{host.moniker}.network..rx.errors.dropped
The total number of dropped packets when receiving on an interface.
hosts.{host.moniker}.network..rx.errors.dropped
The total number of dropped packets when receiving on all interfaces.
Network Errors Received hosts.{host.moniker}.network..rx.errors
Network Errors Received
Aggregate
Network FIFO Errors
Received
Network FIFO Errors
Received Aggregate
Network Frame Errors
Received
Network Frame Errors
Received Aggregate
Network Multicast Bytes
Received
Network Multicast Bytes
Received Aggregate
The total number of errors when receiving on an interface.
hosts.{host.moniker}.network..rx.errors
The total number of errors when receiving on all interfaces.
hosts.{host.moniker}.network..rx.errors.fifo
The number of FIFO errors received on an interface.
hosts.{host.moniker}.network..rx.errors.fifo
The number of FIFO errors received on all interfaces.
hosts.{host.moniker}.network..rx.errors.frame
The number of frame errors when receiving on an interface.
hosts.{host.moniker}.network..rx.errors.frame
The number of frame errors when receiving on all interfaces.
hosts.{host.moniker}.network..rx.multicast
The number of bytes received via multicast on an interface.
hosts.{host.moniker}.network..rx.multicast
The number of bytes received via multicast on all interfaces.
Network Packets Received hosts.{host.moniker}.network..rx.packets
Network Packets Received
Aggregate
The total number of received packets on an interface.
hosts.{host.moniker}.network..rx.packets
The total number of received packets on all interfaces.

Metric Name Format and Description
Network Packets
Transmitted
Network Packets
Transmitted Aggregate
OS
hosts.{host.moniker}.network..tx.packets
The total number of packets transmitted on an interface.
hosts.{host.moniker}.network..tx.packets
The total number of packets transmitted on all interfaces.
Network Transmission Bytes hosts.{host.moniker}.network..tx.bytes
Network Transmission Bytes
Aggregate
Network Transmission
Carrier Errors
Network Transmission
Carrier Errors Aggregate
Network Transmission
Collisions
Network Transmission
Collisions Aggregate
Network Transmission
Dropped Packets
Network Transmission
Dropped Packets Aggregate
Network Transmission
Errors
Network Transmission
Errors Aggregate
Network Transmission FIFO
Errors
Network Transmission FIFO
Errors Aggregate
The total number of transmitted bytes on an interface.
hosts.{host.moniker}.network..tx.bytes
The total number of transmitted bytes on all interfaces.
hosts.{host.moniker}.network..tx.errors.carrier
The amount of carrier errors during transmission on an interface.
hosts.{host.moniker}.network..tx.errors.carrier
The amount of carrier errors during transmission on all interfaces.
hosts.{host.moniker}.network..tx.errors.collisions
The number of packet collisions when transmitting on an interface.
hosts.{host.moniker}.network..tx.errors.collisions
The number of packet collisions when transmitting on all interfaces.
hosts.{host.moniker}.network..tx.errors.dropped
The total number of dropped packets when transmitting on an interface.
hosts.{host.moniker}.network..tx.errors.dropped
The total number of dropped packets when transmitting on all interfaces.
hosts.{host.moniker}.network..tx.errors
The total number of errors when transmitting on an interface.
hosts.{host.moniker}.network..tx.errors
The total number of errors when transmitting on all interfaces.
hosts.{host.moniker}.network..tx.errors.fifo
The amount of FIFO errors during transmission on an interface.
hosts.{host.moniker}.network..tx.errors.fifo
The amount of FIFO errors during transmission on all interfaces.
Metric Name Format and Description
OS Distribution hosts.{host.moniker}.os.distribution.description
The name of the Linux distribution.
OS Name hosts.{host.moniker}.os.name
The name of the operating system
OS Version hosts.{host.moniker}.os.distribution.version
The version of the Linux distribution.
Pre-configured Metrics
OS
Clusterworx System Administrator’s Guide
247

Pre-configured Metrics
Payload
248
Payload
Metric Name Format and Description
Payload Name hosts.{host.moniker}.payload.name
Clusterworx System Administrator’s Guide
The payload last used to provision.
Payload Revision hosts.{host.moniker}.payload.revision
The revision of payload used to provision.

Index
Numerics
1435a
metrics 242
1435a only
metrics 243
1950i
metrics 242
2950i
metrics 243
A
accounts
disable user 63
enable 63
manage group 101
manage local 101
acl_roots 157
add
boot utilities 138
directory to payload 108
file to payload 108
group 57
user account to payload 104
host 25
Icebox 68
kernel modules without loading 118
local user account to payload 101
package
to existing payload 92
to new payload 88
partition 32
plug-in 141
RAID partition 127
region 36
role 52
user 62
to group 58
administration levels 50
annotations
electric shock iii
note iii
tip iii
warning iii
anti-aliasing 40, 41
appearance
interface 22
architecture
metrics 237
authentication management, payload 98
authentication, port 70
B
baud rate 72
beacon
turn off 78, 80
turn on 77, 80
block size 117, 125
BlueSmoke
metrics 240
boot process, plug-ins for 140
boot utilities, add 138
boot.profile 122, 139
branch, version 144
C
ccp 192
channels 181
check into VCS
Clusterworx System Administrator’s Guide
249

Index
D
250
image 146
kernel 146
payload 146
check out of VCS
image 147
kernel 147
payload 147
CLI 233
cluster 23
copy command 192
environment 49
host administration 196
power administration 204
provisioning 206
system monitoring 40
user administration 209
Clusterworx
install into payload 110
install on client 11
introduction 19
launch 10
Master Host
DHCP settings 158
rename 29
set up 4
services 14
system requirements 2
command-line interface 185, 233
ccp 192
conman 193
cwhost 196
cwpower 204
cwprovision 206
cwuser 209
dbix 215
dbx 216
imgr 217
kmgr 218
pdcp 219
pdsh 222
pmgr 225
powerman 226
vcs 228
compute host. See host
configuration subtab 67
configure
baud rate 72
NIS 98
conman 193
connect
Clusterworx System Administrator’s Guide
to host via Runner 164
copy
from VCS 148
image 122
kernel 114
payload 90
CPU
metrics 237
utilization 45
CPU tab 45
create
group 57
host 25
image 120
kernel 112
kernel from binary 218
multiple payloads from source 86
partition 32, 124
password
Icebox 68, 201
user 62, 210
payload 85
region 36
role 52
custom loggers 182
customer education iv
cwhost 196
cwpower 204
cwprovision 206
cwuser 209
D
dbix 215
dbx 216
default user administration settings 51
delete
all payloads, kernels, and images 148
file(s) from payload 109
group 61
account from payload 105
host 31
image partition 131
local user account from payload 103
package from payload 92
partition 35
payload 109
region 39
role 55
user account 66

working copy of image 123
working copy of kernel 119
working copy of payload 109
dependency checks, package 96
DHCP 158
dhcpd.conf 158
dhcpd.conf.template 158
disable
anti-aliasing 40
gradient fill 40
host 30
Kerberos 100
LDAP 99
NIS 98
partition 35
port authentication 70
SNMP settings 74
user account 63, 65
disconnect
from host via Runner 169
disk
aggregate usage 46
fill to end of 136
I/O 46
metrics 239
disk tab 46
diskless hosts 135
configure 135
mount point 136
distribution, upgrade 2
dmesg.level 122
DNS name resolution 92
documentation, online ii
E
ebi files 155
EDAC
metrics 240
edit
group 60
host 28
Icebox password 201
image partition 129
kernel 117
partition 34
password 64, 211
payload 94
using text editor 107
region 38
role 54
user account 64
electric shock iii
enable
anti-aliasing 40
concurrent Icebox ports 70
gradient fill 40
hardware flow control 72
Kerberos 100
LDAP 99
NIS 98
SNMP settings 74
temperature shutdown 70
user account 63
error messages 184
errors, RPM 89
EULA 259
event monitoring 171
exclude
files and directories from VCS 151
exclude file(s) from payload 91
F
feedback, documentation ii
file system, user-defined 132
file(s), exclude from payload 91
fill to end of disk 136
filter 41
filters subtab 75
flow control, enable hardware 72
format partition 125
fstab 125, 136
G
general subtab 70
general tab 42
GID 50, 57
gradient fill 40, 41
group 49, 57
add 57
account to payload 104
assign roles to 53, 58
assign user to 63
delete 61
account from payload 105
edit 60
GID 50, 57
grant access to region 59
Clusterworx System Administrator’s Guide
Index
E
251

Index
H
252
primary 63
region, add to 37
user membership 63
GTK, customized interface 22
H
hardware
enable flow control 72
system requirements 1
health monitoring 40
message log 41
system status icons 40
host 23, 25
add 25
to partition 33
administration 23
grant privileges 56
assign Icebox port 27
beacon
turn off 78
turn on 77
CLI administration 196
Clusterworx Master 23
DHCP settings 158
rename 29
set up 4
configure 23
diskless host 135
connect to via Runner 164
controls 77
cycle power to 78
delete 31
disable 30
disconnect from Runner 169
diskless 135
edit 28
install RPM 192
load monitoring 47
master. See Clusterworx Master Host
message log 41
names 111
port assignment 71
power
turn off 78
turn on 78
provision 153
using CLI 206
reboot 79
region
Clusterworx System Administrator’s Guide
add host to 37
assign host to 26
reset 78
remote reset 67
shared 23
shut down 78
states 40
view output via Runner 166
hosts subtab 77
I
Icebox 67
access, restore 75
add 68
administration 67
administration privileges 56
beacon
turn off 80
turn on 80
connect to 69
controls 80
create password for 68, 201
filter settings 75
deny 75
host port assignment 27
IP address 68
MAC address 69
metrics 240
modify password 201
power
cycle 81
turn off 80
turn on 80
power management 67, 77
primary 27
reset 81
remote reset 67
temperature monitoring 67
Iceboxes subtab 80
icons, system status 40
image 83, 122
add modules without loading 118
check into VCS 146
check out from VCS 147
CLI controls 217
copy 122
create 120
delete all 148
delete partition 131

delete working copy of image 123
edit image partition 129
management 120
metrics 240
partition 124
privileges, enable imaging 56
provision 153
select image 154
versioned 144
working copy 144
image.once 122
image.path 122
imgr 217
import
binary kernel 218
informational messages 184
install
Clusterworx 4
client 11
into payload 110
server 5
set up a Master Host 4
instrumentation 40
CPU utilization 45
custom loggers 182
custom monitors 172
disk
aggregate usage 46
I/O 46
enhance performance 40
host load 47
kernel information 47
list view 44
listeners 179
loggers, pre-defined 181
memory utilization 45
menu controls 41
message log 41
metrics, define 175
metrics, pre-configured 237
monitoring and event subsystem 171
packet transmissions 46
resource utilization 42
system configuration 42
system status 40
overview 42
temperature readings 48
thumbnail view 43
interface
customized appearance 22
map 21
interface, management 27
interval 41
IP address 234
host 26
Icebox 68
K
Kerberos 100
kernel 83
build from source 112
check into VCS 146
check out from VCS 147
CLI controls 218
copy 114
create 112
create from binary 218
delete all 148
delete working copy of kernel 119
edit 117
install modules without loading 118
loadable modules 118
management 112
metrics 240
modular 118
monolithic 118
upgrade 2
verbosity level 158, 206
versioned 144
working copy 144
kernel tab 47
kmgr 218
L
LDAP 99
license 15
administration 17
authentication 17
Clusterworx EULA 259
installation 15
new 15
viewer 17
links, dangling symbolic 91
list view 41, 44
listeners 171, 179
load
metrics 241
load tab 47
Clusterworx System Administrator’s Guide
Index
K
253

Index
M
254
loadable kernel modules 118
logger 171
loggers
custom 182
pre-defined 181
M
MAC address, Icebox 69
management
host(s), system requirements 1
management network 6
VCS 148
management interface 27
Master Host
definition 23
rename 29
set up 4
memory
estimate partition requirements 126, 133, 136
metrics 244
utilization 45
memory tab 45
message log 41, 184
metrics 175, 237
1435a 242
1435a only 243
1950i 242
2950i 243
alignment 176
architecture 237
BlueSmoke 240
CPU 237
custom 177
disk 239
EDAC 240
Icebox 240
image 240
instrumentation service 41
kernel 240
load 241
memory 244
metric selector 176
network 246
OS 247
payload 248
MIB 74
migration utility 13
mkelfimage 4
mkfs 125
Clusterworx System Administrator’s Guide
modules
install without loading 118
loadable kernel 118
modules subtab 118
monitoring
event 171
system health 40
monitors 171, 172
custom 172
multicast
route fix 162
route issues 158
throttle 162
wastegate values 162
N
name resolution 111
navigation tree 21
netmask 235
network metrics 246
network subtab 73
network tab 46
NFS 50
NIS 98
note iii
O
online documentation ii
operating system requirements 2
OS
metrics 247
out-of-memory error 110
output
view host output via Runner 166
overview 41
overview, system status 42
P
package
add to existing payload 92
add to new payload 88
dependency checks 96
remove from payload 94
packet transmissions 46
partition 23, 32, 122
add 32

host to 33
RAID 127
region to 33
create 124
user-defined file system 132
delete 35
delete from image 131
disable 35
edit 34
edit image partition 129
estimate memory requirements 126, 133, 136
format 125
manage 124
overwrite protection 125
partition this time 157
partitioning behavior 121
save 125
size
fill to end of disk 126, 133, 136
fixed 126, 133, 136
partition.once 122
password
create Icebox 68, 201
create new 62, 210
encrypt 211
modify 64, 211
modify Icebox 201
payload 83
.payload files 155
account management, local user 101
add
directory to 108
file to 108
group user account to 104
local user account to 101
package to existing 92
package to new 88
attributes, troubleshoot 87
authentication management 98
check into VCS 146
check out from VCS 147
CLI controls 225
configure 106
copy 90
create 85
multiple payloads from source 86
dangling symbolic links 91
delete 109
.payload files 155
file(s) from payload 109
group account from payload 105
local user account from payload 103
working copy of payload 109
delete all 148
download 122
download this time 157
edit
using CLI 108
with text editor 107
exclude file(s) 91
file configuration 106
group account management 101
install Clusterworx into 110
management 84
metrics 248
package dependency checks 96
pmgr 225
remove package from 94
update directory 108
update file 108
versioned 144
working copy 144
PBS 157
pdcp 219
pdsh 222
permissions 56
See role; privileges
physical memory utilization 45
plug-ins
add 141
for boot process 140
port
authentication, disable 70
enable concurrent Icebox ports 70
host port assignment 71
ports subtab 71
power
CLI administration 204
cycle
to host 78
to Icebox 81
management 67
powerman 226
turn off
to host 78
to Icebox 80
turn on
to host 78
to Icebox 80
power management subtab 77
Clusterworx System Administrator’s Guide
Index
P
255

Index
Q
256
powerman 226
pre-configured metrics 237
pre-defined loggers 181
primary
group 63
Icebox 27
privileges 56
change user 54, 55
host administration 56
Icebox administration 56
imaging 56
user administration 56
provision 153
CLI controls 206
disable confirmation dialog 155
enable confirmation dialog 155
format partition 125
schedule at next reboot 157
select an image 154
Q
qmgr 157
R
RAID 127
RAM Disk 138
block size 117
RAMfs 135
reboot host 79
region 23, 36, 49
add 36
group to 37
host to 37
to partition 33
assign to host 26
delete 39
edit 38
grant group access to 59
remote reset 67
remove
file(s) from payload 109
group 61
group account from payload 105
host 31
local user account from payload 103
package from payload 94
partition 35
region 39
Clusterworx System Administrator’s Guide
role 55
user account 66
rename
Clusterworx Master Host 29
host 28
requirements
software 2
reset
host 78
Icebox 81
remote reset 67
resource
utilization 42
RHEL 235
rights
See role; privileges
role 49, 52
add 52
assign to group 53, 58
delete 55
edit 54
grant privileges and permissions 53
RPM errors 89
RPM, install on hosts 192
Runner 163
connect to host 164
disconnect from host 169
execute commands on hosts 167
restrictions 163
troubleshooting 50
view host output 166
S
save
partition 125
schedule provision at next reboot 157
secure remote access 11
set temperature thresholds 72
shut down a host 78
size, thumbnail 41
SLES 235
SNMP
settings 74
traps 74
SNMP subtab 74
software
requirements 2
sort 41
SSL 99

states, system 40
status, version 149
support, technical iv
symbolic links, dangling 91
symlink 91
system
configuration 42
health 40
requirements
hardware 1
operating system 2
status
icons 40
message log 41
overview 42
T
task progress dialog 87
technical support iv
temperature
enable shutdown 70
monitoring, Icebox 67
readings 48
thresholds, set 72
temperature tab 48
third-party power controls 63
thumbnail
size 41
thumbnail view 41, 43
tip iii
TmpFS 135
training iv
transmissions, packet 46
troubleshooting
out-of-memory error 110
payload attributes 87
RPM errors 89
Runner 50
U
UID 50, 62
upgrade 3
Clusterworx 4
distribution 2
kernel 2
See also migration utility
user 49, 62
add 62
local user account to payload 101
to group 58
administration 49
default settings 51
privileges 56
assign to group 63
CLI administration 209
delete
local user account from payload 103
delete account 66
disable account 65
edit account 64
group membership 63
multi-group 50
UID 50, 62
user-defined file system 132
V
VCS 144
branch 146
CLI controls 228
command-line controls 228
copy 148
exclude files and directories 151
VCS management console 148
verbosity level, kernel 158, 206
version
branching 144
control system 144
check into 146
check out 147
vcs command 228
status 149
VersionControlService.profile 151
versioned copy 144, 235
virtual memory utilization 45
VPN support 11
W
warning iii
warning messages 184
Windows, customized interface 22
working copy 144, 235
X
xms 231
Clusterworx System Administrator’s Guide
Index
T
257

Index
258
Clusterworx System Administrator’s Guide

Clusterworx End User
License Agreement
PLEASE READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED
SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY “Software Maintenance Agreement”) CAREFULLY
BEFORE SIGNING THE FINAL ACCEPTANCE DOCUMENTS OF THE SYSTEM. BY ACCEPTING THE
SYSTEM OR SIGNING THIS AGREEMENT FROM LINUX NETWORX YOU AGREE TO ALL OF THE
TERMS OF THIS AGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY,
INDICATE YOUR ACCEPTANCE OF THESE TERMS BY ANSWERING “YES” AT THE END OF THIS
AGREEMENT. IF YOU DO NOT AGREE TO ALL THESE TERMS, PROMPTLY RETURN THE UNUSED
SOFTWARE OR, IF THE SOFTWARE IS ACCESSED ELECTRONICALLY, ANSWER “NO” AND THE
INSTALLATION PROCESS WILL NOT CONTINUE.
Linux Networx Inc. (“LNXI”) agrees to grant CUSTOMER a license to the release of the Clusterworx® 3.4
software and documentation in accordance with the following terms and conditions:
1. Definitions.
1.1. “Documentation” means the documentation specified in the Product Schedule(s), attached hereto and
incorporated herein by this reference, together with all additions, changes and updates furnished by LNXI
under this Agreement or the Software Maintenance Agreement. Any reference to the Documentation herein
shall include each component and/or portion of the Documentation.
1.2. “Product” means the computer programs specified in the Product Schedule(s) together with any and all
corrections and updates furnished by LNXI to CUSTOMER under this Agreement or the Software
Maintenance Agreement. Any reference to the Product herein shall include each component and/or portion
of the Product.
1.3. “Software Maintenance Agreement” means that certain Software Maintenance Agreement set forth
on Exhibit B attached hereto and incorporated herein by this reference.
1.4. “License File” means the binary electronic file distributed by LNXI containing the license key(s) for the
Product.
2. Product Delivery and License.
2.1. Deliverables. Upon execution of this Agreement, LNXI shall deliver to CUSTOMER one reproducible
master copy of the Product, in object code form and one copy of the Documentation, in electronic form.
2.2. Grant. LNXI hereby grants CUSTOMER a personal, nonexclusive, nontransferable license to:
2.2.1. Install and use the Product for internal processing requirements of CUSTOMER, on the number of
CUSTOMER'S computers then authorized under this Agreement. The number of computers authorized
initially is set forth in the Product Schedule(s). CUSTOMER may increase the number of authorized
computers from time to time in the unit quantities and upon payment to LNXI of the applicable amount as set
Clusterworx System Administrator’s Guide
259

Clusterworx End User License Agreement
260
forth in the Product Schedule(s). Customer shall keep accurate records of the reproduction and location of
each copy of software and, upon request, provide LNXI with complete access to such records and to
CUSTOMER'S facilities, computers and the Product to audit and verify CUSTOMER'S compliance with this
Agreement.
2.2.2. Reproduce and make one copy of the Product and documentation for archival and backup purposes.
2.3. Customer Responsibilities. CUSTOMER shall use the Product and the Documentation only for the
purposes specified in Section 2.2 and in accordance with the following:
2.3.1. CUSTOMER shall use the Product only on the then authorized number of computers which are
owned or used by CUSTOMER and will use the Product and Documentation solely for CUSTOMER'S
internal use.
2.3.2. CUSTOMER shall not distribute modified derivative works from the Product or Documentation except
as expressly permitted in Section 2.2 or with the express written permission of Linux Networx.
2.3.3. CUSTOMER shall not tamper with or emulate the License File or reverse engineer, disassemble or decompile
the Product.
2.3.4. CUSTOMER shall not remove, obscure, or alter any notice of patent, copyright, trade secret, trademark,
or other proprietary right present on any Product or Documentation.
2.3.5. CUSTOMER shall not sublicense, sell, lend, rent, lease, or otherwise transfer all or any portion of the
Product or the Documentation to any third party except as permitted in Section 8.3.
2.4. Protection Against Unauthorized Use. CUSTOMER shall promptly notify LNXI of any unauthorized
use of the Product or Documentation that comes to CUSTOMER'S attention. In the event of any
unauthorized use by any of CUSTOMER'S employees, agents or representatives, CUSTOMER shall use
reasonable efforts to terminate such unauthorized use and to retrieve any copy of the Product or
Documentation in the possession or control of the person or entity engaging in such unauthorized use.
CUSTOMER shall immediately notify LNXI of any legal proceeding initiated by CUSTOMER in connection
with such unauthorized use. LNXI may, at its option and expense, participate in any such proceeding and, in
such event, CUSTOMER shall provide such authority, information and assistance related to such proceeding
as LNXI may reasonably request to protect LNXI'S interests.
2.5. Reservation of Proprietary Rights. CUSTOMER and LNXI agree that the Product and the
Documentation involve valuable copyright, trade secret, trademark and other proprietary rights of LNXI.
Except for the license granted under Section 2.2, LNXI reserves all rights to the Product and the
Documentation. No title to or ownership of any Product or proprietary rights related to the Products or
Documentation is transferred to CUSTOMER under this Agreement. CUSTOMER agrees that modified or
enhanced version of the product do not constitute a program different form the Product, and as such, fall
under the other terms and conditions of this Agreement.
3. Software Maintenance and Support.
3.1. CUSTOMER and LNXI shall execute the Software Maintenance Agreement that shall govern all
maintenance, support and update obligations of LNXI and CUSTOMER with respect to the Product and the
Documentation.
4. Termination.
4.1. Term. The term of this Agreement and the license set forth in Section 2.2 shall commence on the date
of this Agreement and shall end upon the earlier to occur of the termination of this Agreement pursuant to
Section 4.2 or 4.3 or the date shown by the Product as specified by the License File.
4.2. Termination By CUSTOMER. CUSTOMER may terminate this Agreement and the license by giving
thirty (30) days' written notice to LNXI. Any and all outstanding fees due must be paid commensurate with
such notice of termination.
Clusterworx System Administrator’s Guide

Clusterworx End User License Agreement
4.3. Termination By LNXI. If CUSTOMER fails to pay any amount due hereunder when due, LNXI may
terminate this Agreement and the license, in addition to its other rights and remedies under law. If
CUSTOMER defaults in the performance of or compliance with any of its obligations under this Agreement
(other than a failure to pay any amount due hereunder), and such default has not been remedied or cured
within thirty (30) days after LNXI gives CUSTOMER written notice specifying the default, LNXI may
terminate this Agreement and the license, in addition to its other rights and remedies under law. An event of
default shall include but not be limited to the following: (a) if CUSTOMER files a petition under any chapter
of the Bankruptcy Code, as amended, or for the appointment of a receiver, (b) if an involuntary petition in
bankruptcy is filed against CUSTOMER and said petition is not discharged within thirty (30) days, (c) if
CUSTOMER shall become insolvent or make a general assignment for the benefit of its creditors, (d) if the
business or property of CUSTOMER shall come into the possession of its creditors, a governmental agency or
a receiver, (e) if any proceedings supplementary to judgment shall be commenced against CUSTOMER, or (f)
if any judgment against CUSTOMER, not fully bonded, shall remain unpaid in whole or in part for at least
five (5) days after entry thereof, then, in any case, the other party may at its option terminate this Agreement.
4.4. Post Termination. Upon termination of this Agreement by LNXI, CUSTOMER shall promptly cease use
of the Product and Documentation and return to LNXI all copies of the Product and Documentation then in
CUSTOMER'S possession or control.
4.5. Survival. Sections 1, 2.5, 4, 5, 6, and 7 and all other provisions of this Agreement which may
reasonably be interpreted or construed as surviving the termination of this Agreement, shall survive the
termination of this Agreement.
5. Warranties.
5.1. DISCLAIMER AND RELEASE. CUSTOMER ACKNOWLEDGES THAT EXCEPT WITH RESPECT TO
THE EXPRESS WARRANTY IN SECTION 5.2 BELOW, CUSTOMER HEREBY WAIVES, RELEASES AND
DISCLAIMS, ALL WARRANTIES, OBLIGATIONS AND LIABILITIES OF LNXI AND ALL OTHER
REMEDIES, RIGHTS AND CLAIMS OF CUSTOMER, EXPRESS OR IMPLIED, ARISING BY LAW OR
OTHERWISE, WITH RESPECT TO THE PRODUCTS, THE DOCUMENTATION, ANY SERVICES
PROVIDED BY LNXI AND ANY OTHER ITEMS SUBJECT TO THIS AGREEMENT, INCLUDING, BUT NOT
LIMITED TO: (A) ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE; (B) ANY IMPLIED WARRANTY ARISING FROM COURSE OF PERFORMANCE, COURSE OF
DEALING OR USAGE OF TRADE; (C) ANY OBLIGATION, LIABILITY, RIGHT, REMEDY, OR CLAIM IN
TORT, NOTWITHSTANDING ANY FAULT, NEGLIGENCE, STRICT LIABILITY OR PRODUCT LIABILITY
OF LNXI (WHETHER ACTIVE, PASSIVE OR IMPUTED); AND (D) ANY OBLIGATION, LIABILITY,
REMEDY, RIGHT OR CLAIM FOR INFRINGEMENT. (EXCEPT AS PROVIDED IN SECTION 5.2). WITHOUT
LIMITING THE FOREGOING LNXI DOES NOT WARRANT THAT THE PRODUCT IS FREE FROM ALL
BUGS, ERRORS AND OMISSIONS.
5.2. Proprietary Rights. LNXI warrants that the Product does not infringe any U.S. copyright. LNXI will
defend CUSTOMER against any proceeding based upon any failure to satisfy the foregoing warranty,
provided that: CUSTOMER notifies LNXI of the proceeding promptly after it is commenced; CUSTOMER
tenders sole control of the defense of the proceeding to LNXI; CUSTOMER provides such assistance in
defense of the proceeding as LNXI may reasonably request; and CUSTOMER complies with any court order
or settlement made in connection with the proceeding (e.g., relating to the future use of the affected Product).
Further, LNXI will: indemnify CUSTOMER against any and all damages, costs and attorneys' fees awarded
against CUSTOMER in connection with such proceeding as a result of any such noncompliance; reimburse
the expenses reasonably incurred by CUSTOMER to provide any assistance requested by LNXI in defense of
the proceeding; and, if the action is settled, pay any amounts agreed to by LNXI in settlement of any claims
based upon such noncompliance. If on account of such proceeding, CUSTOMER'S right to use the Product
are materially diminished, LNXI may refund all or an equitable portion of the compensation paid by
CUSTOMER to LNXI for the same in full satisfaction of CUSTOMER'S claims relating to such
noncompliance.
Clusterworx System Administrator’s Guide
261

Clusterworx End User License Agreement
262
5.3. Warranty Limitations. The warranty set forth in Section 5.2 applies only to the latest release of the
Product made available by LNXI to CUSTOMER. Such warranty does not apply to any noncompliance
resulting from misuse, casualty loss, use or combination of the Product with any products, goods, services or
other items furnished by anyone other than LNXI or any modification not made by or for LNXI.
6. Limitations of Liability.
6.1. Excused Performance. Neither party will be liable for, or be considered to be in breach of or default
under this Agreement on account of, any delay or failure to perform as required by this Agreement (other
than monetary obligations) as a result of any cause or condition beyond such party's reasonable control.
6.2. DOLLAR LIMITATION. LNXI'S LIABILITY (WHETHER IN CONTRACT, WARRANTY, TORT OR
OTHERWISE; AND NOTWITHSTANDING ANY FAULT, NEGLIGENCE, REPRESENTATION, STRICT
LIABILITY OR PRODUCT LIABILITY OF LNXI) UNDER THIS AGREEMENT (EXCEPT FOR LNXI'S
OBLIGATIONS UNDER SECTION 5.2) WITH REGARD TO ANY PRODUCT, DOCUMENTATION,
SERVICES OR OTHER ITEMS SUBJECT TO THIS AGREEMENT SHALL IN NO EVENT EXCEED THE
TOTAL COMPENSATION PAID BY CUSTOMER TO LNXI UNDER THIS AGREEMENT.
6.3. DAMAGE LIMITATION. IN NO EVENT WILL LNXI HAVE ANY OBLIGATION OR LIABILITY
(WHETHER IN CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR
OTHER CAUSE OF ACTION) FOR THE COST OF COVER OR FOR ANY INCIDENTAL, DIRECT, INDIRECT
OR CONSEQUENTIAL DAMAGES OR LIABILITIES (INCLUDING, BUT NOT LIMITED TO, ANY LOSS OF
REVENUE, PROFIT OR BUSINESS) EVEN IF LNXI OR ITS EMPLOYEES AND REPRESENTATIVES HAVE
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. Miscellaneous.
7.1. Confidential Information. CUSTOMER shall not disclose the terms of this Agreement except as
required by law or governmental regulation without LNXI'S prior written consent except that CUSTOMER
may disclose this Agreement on a confidential basis to CUSTOMER'S accountants, attorneys, parent
organizations and financial advisors and lenders.
7.2. Notices. Any notice or other communication under this Agreement given by either party to the other
will be deemed to be properly given if given in writing and delivered in person, by facsimile, if acknowledged
received by return facsimile, by nationally-recognized overnight courier, next business day delivery
requested, or by registered or certified U.S. mail, properly addressed and stamped with the required postage
with return receipt requested, to the intended recipient at its address specified in this Agreement. Such
notice shall be deemed given, if by mail, five days after depositing such notice with the U.S. Post Office, if by
overnight courier, the next business day following delivery of such notice to such courier, and, if in person or
by facsimile, the same day as so given. Either party may from time to time change its address for notices
under this Section by giving the other party notice of the change in accordance with this Section.
7.3. Assignment. CUSTOMER will not assign (directly, by operation of law or otherwise) this Agreement or
any of its rights under this Agreement without the prior written consent of LNXI. Any merger or other
similar transaction resulting in the transfer of fifty percent or more of the capital stock of CUSTOMER shall
be deemed to be a change in control. Subject to the foregoing, this Agreement is binding upon, inures to the
benefit of and is enforceable by the parties and their respective successors and assigns.
7.4. Nonwaiver. Any failure of either party to insist upon or enforce performance by the other party of any
of the provisions of this Agreement or to exercise any rights or remedies under this Agreement will not be
interpreted or construed as a waiver or relinquishment of such party's right to assert or rely upon such
provision, right or remedy in that or any other instance; rather the same will be and remain in full force and
effect.
7.5. Entire Agreement. This Agreement consists of the Software License Agreement, the Software
Maintenance Agreement and the Product Schedule(s), and supersedes any and all prior agreements, between
LNXI and CUSTOMER relating to the Product, the Documentation and other items subject to this
Clusterworx System Administrator’s Guide

Clusterworx End User License Agreement
Agreement. No amendment of this Agreement will be valid unless set forth in a written instrument signed by
both parties.
7.6. Compliance With Laws. LNXI and CUSTOMER shall each comply with all applicable laws,
regulations, rules, orders and other requirements, now or hereafter in effect, of any applicable governmental
authority, in their performance of this Agreement. Without limiting the generality of the foregoing,
CUSTOMER will comply with all export control laws and regulations of the United States in dealing with the
Product including its export and use of the Product outside the United States.
8. Governing Law. THIS AGREEMENT WILL BE INTERPRETED, CONSTRUED AND ENFORCED IN
ALL RESPECTS IN ACCORDANCE WITH THE LAWS OF THE STATE OF UTAH WITHOUT REFERENCE
TO ITS CHOICE OF LAW RULES AND NOT INCLUDING THE 1980 U.N. CONVENTION ON CONTRACTS
FOR THE INTERNATIONAL SALE OF GOODS. CUSTOMER WILL NOT COMMENCE OR PROSECUTE
ANY CLAIM, ACTION, SUIT OR PROCEEDING RELATING TO THIS AGREEMENT OR THE PRODUCT,
DOCUMENTATION, SERVICES OR OTHER ITEMS SUBJECT TO THIS AGREEMENT OTHER THAN IN
THE COURTS OF THE STATE OF UTAH, SALT LAKE COUNTY, OR THE UNITED STATES DISTRICT
COURT LOCATED IN SALT LAKE COUNTY. CUSTOMER HEREBY IRREVOCABLY CONSENTS TO THE
JURISDICTION AND VENUE OF THE COURTS IDENTIFIED IN THE PRECEDING SENTENCE IN
CONNECTION WITH ANY CLAIM, ACTION, SUIT OR PROCEEDING RELATING TO THIS AGREEMENT
OR ANY PRODUCT, DOCUMENTATION, SERVICES OR OTHER ITEMS SUBJECT TO THIS AGREEMENT.
Each party's authorized representative for execution of this Agreement or any amendment thereto shall be a
president, partner, or another duly authorized signatory of each respective party. The parties executing this
Agreement warrant that they have the requisite authority to bind their companies to the terms and
conditions of this Agreement.
Clusterworx System Administrator’s Guide
263

Clusterworx End User License Agreement
264
Clusterworx System Administrator’s Guide