About XC Series System Administration Guide (S-2393)
This publication includes information about administering Cray XC™ Series computers running Cray SMW and CLE software. It is intended for experienced Cray system administrators.
Scope and Audience
The XC™ Series System Administration Guide (S-2393) provides information about administering Cray XC™ Series computers running Cray System Management Workstation (SMW) and Cray Linux Environment (CLE) software.
This publication does not include procedures for installing software on a Cray XC™ Series system; for those, see XC™ Series Software Installation and Configuration Guide (S-2559).
This publication is intended for experienced Cray system administrators. It assumes some familiarity with standard Linux and open source tools (e.g., zypper/yum for RPMs, Ansible, YAML/JSON configuration data).
CLE 7.0.UP01 / SMW 9.0.UP01 Release
XC™ Series System Administration Guide (CLE 7.0.UP01) S-2393 supports Cray software release CLE 7.0.UP01 / SMW 9.0.UP01 for Cray XC™ Series systems, released on 29 August 2019.
- New section on adding aarch64 nodes to an existing XC system to create a system with a hybrid-architecture compute plane. See Add aarch64 Nodes to an Existing System for more information.
- Hugepage usage is now included when calculating job memory statistics. See Enable or Disable Hugepage Inclusion in Memory Statistics for more information.
- Various corrections and editorial changes were made.
| Publication Title | Date | Release |
|---|---|---|
| XC™ Series System Administration Guide (CLE 7.0.UP01) S-2393 | 29 Aug 2019 | CLE 7.0.UP01 / SMW 9.0.UP01 |
| XC™ Series System Administration Guide (CLE 7.0.UP00) S-2393 | 28 Feb 2019 | CLE 7.0.UP00 / SMW 9.0.UP00 |
| XC™ Series System Administration Guide (CLE 6.0.UP07) S-2393 | 12 Jul 2018 | CLE 6.0.UP07 / SMW 8.0.UP07 |
| XC™ Series System Administration Guide (CLE 6.0.UP06) S-2393 Rev A | 27 Mar 2018 | CLE 6.0.UP06 / SMW 8.0.UP06 |
| XC™ Series System Administration Guide (CLE 6.0.UP06) S-2393 | 01 Mar 2018 | CLE 6.0.UP06 / SMW 8.0.UP06 |
| XC™ Series System Administration Guide (CLE 6.0.UP05) S-2393 | 05 Oct 2017 | CLE 6.0.UP05 / SMW 8.0.UP05 |
| XC™ Series System Administration Guide (CLE 6.0.UP04) S-2393 | 22 Jun 2017 | CLE 6.0.UP04 / SMW 8.0.UP04 |
| XC™ Series System Administration Guide (CLE 6.0.UP03) S-2393 Rev A | 04 May 2017 | CLE 6.0.UP03 / SMW 8.0.UP03 |
| XC™ Series System Administration Guide (CLE 6.0.UP03) S-2393 | 16 Feb 2017 | CLE 6.0.UP03 / SMW 8.0.UP03 |
| XC™ Series System Administration Guide (CLE 6.0.UP02) S-2393 | 03 Nov 2016 | CLE 6.0.UP02 / SMW 8.0.UP02 |
| XC™ Series System Administration Guide (CLE 6.0.UP01) S-2393 | 20 Jun 2016 | CLE 6.0.UP01 / SMW 8.0.UP01 |
| CLE XC System Administration Guide S-2393-5204xc | 24 Sep 2015 | CLE 5.2.UP04 / SMW 7.2.UP04 |
| Manage System Software for the Cray Linux Environment S-2393-5203 | Apr 2015 | CLE 5.2.UP03 / SMW 7.2.UP03 |
Command Prompt Conventions
- Host name and account in command prompts
- The host name in a command prompt indicates where the command must be run. The account that must run the command is also indicated in the prompt.
- The
rootor super-user account always has the#character at the end of the prompt. - Any non-
rootaccount is indicated withaccount@hostname>. A user account that is neitherrootnorcrayadmis referred to asuser.
smw#
Run the command on the SMW as root.cmc#
Run the command on the CMC as root.sdb#
Run the command on the SDB node as root.crayadm@boot>
Run the command on the boot node as the crayadmuser.user@login>
Run the command on any login node as any non- rootuser.hostname#
Run the command on the specified system as root.user@hostname>
Run the command on the specified system as any non- rootuser.smw1# smw2#
For a system configured with the SMW failover feature there are two SMWs—one in an active role and the other in a passive role. The SMW that is active at the start of a procedure is smw1. The SMW that is passive is smw2. smwactive# smwpassive#
In some scenarios, the active SMW is smw1 at the start of a procedure—then the procedure requires a failover to the other SMW. In this case, the documentation will continue to refer to the formerly active SMW as smw1, even though smw2 is now the active SMW. If further clarification is needed in a procedure, the active SMW will be called smwactive and the passive SMW will be called smwpassive. - The
- Command prompt inside chroot
- If the chroot command is used, the prompt changes to indicate that it is inside a chroot environment on the system.
smw# chroot /path/to/chroot chroot-smw#
- Directory path in command prompt
- Example prompts do not include the directory path, because long paths can reduce the clarity of examples. Most of the time, the command can be executed from any directory. When it matters which directory the command is invoked within, the cd command is used to change into the directory, and the directory is referenced with a period (
.) to indicate the current directory.For example, here are actual prompts as they appear on the system:smw:~ # cd /etc smw:/etc# cd /var/tmp smw:/var/tmp# ls ./file smw:/var/tmp# su - crayadm crayadm@smw:~> cd /usr/bin crayadm@smw:/usr/bin> ./command
And here are the same prompts as they appear in this publication:smw# cd /etc smw# cd /var/tmp smw# ls ./file smw# su - crayadm crayadm@smw> cd /usr/bin crayadm@smw> ./command
Typographic Conventions
Monospace | Indicates program code, reserved words, library functions, command-line prompts, screen output, file/path names, and other software constructs. |
| Monospaced Bold | Indicates commands that must be entered on a command line or in response to an interactive prompt. |
| Oblique or Italics | Indicates user-supplied values in commands or syntax definitions. |
| Proportional Bold | Indicates a graphical user interface window or element and key strokes (e.g., Enter, Alt-Ctrl-F). |
\ (backslash) | At the end of a command line, indicates the Linux® shell line continuation character (lines joined by a backslash are parsed as a single line). |
Trademarks
© 2019, Cray Inc. All rights reserved. All trademarks used in this document are the property of their respective owners.