Cray X1 System Administration Differences system administration software, CWS 2.3, CWS 2.4, SWS 6.2 system workstation, UNICOS mp 2.4 operating system, Programming Environment Server, Network Subsystem computer utilities User manual
Reklama
Reklama
Cray X1™ System Administration
Differences
S–2348–24
© 2002–2004 Cray Inc. All Rights Reserved. This manual or parts thereof may not be reproduced in any form unless permitted by contract or by written permission of Cray Inc.
U.S. GOVERNMENT RESTRICTED RIGHTS NOTICE
The Computer Software is delivered as "Commercial Computer Software" as defined in DFARS 48 CFR 252.227-7014.
All Computer Software and Computer Software Documentation acquired by or for the U.S. Government is provided with Restricted
Rights. Use, duplication or disclosure by the U.S. Government is subject to the restrictions described in FAR 48 CFR 52.227-14 or DFARS 48 CFR 252.227-7014, as applicable.
Technical Data acquired by or for the U.S. Government, if any, is provided with Limited Rights. Use, duplication or disclosure by the
U.S. Government is subject to the restrictions described in FAR 48 CFR 52.227-14 or DFARS 48 CFR 252.227-7013, as applicable.
Autotasking, CF77, Cray, Cray Ada, Cray Channels, Cray Chips, CraySoft, Cray Y-MP, Cray-1, CRInform, CRI/TurboKiva,
HSX, LibSci, MPP Apprentice, SSD, SuperCluster, UNICOS, UNICOS/mk, and X-MP EA are federally registered trademarks and Because no workstation is an island, CCI, CCMT, CF90, CFT, CFT2, CFT77, ConCurrent Maintenance Tools, COS,
Cray Animation Theater, Cray APP, Cray C90, Cray C90D, Cray CF90, Cray C++ Compiling System, CrayDoc, Cray EL, Cray
Fortran Compiler, Cray J90, Cray J90se, Cray J916, Cray J932, CrayLink, Cray MTA, Cray MTA-2, Cray MTX, Cray NQS,
Cray/REELlibrarian, Cray S-MP, Cray SSD-T90, Cray SV1, Cray SV1ex, Cray SV2, Cray SX-5, Cray SX-6, Cray T90,
Cray T94, Cray T916, Cray T932, Cray T3D, Cray T3D MC, Cray T3D MCA, Cray T3D SC, Cray T3E, CrayTutor, Cray X1,
Cray X-MP, Cray XMS, Cray-2, CSIM, CVT, Delivering the power . . ., DGauss, Docview, EMDS, GigaRing, HEXAR, IOS,
ND Series Network Disk Array, Network Queuing Environment, Network Queuing Tools, OLNET, RQS, SEGLDR, SMARTE,
SUPERLINK, System Maintenance and Remote Testing Environment, Trusted UNICOS, UNICOS MAX, and UNICOS/mp are trademarks of Cray Inc.
ADIC is a trademark of Advanced Digital Information Corporation. Etnus and TotalView are trademarks of Etnus, LLC. FLEXlm is a trademark of Macrovision Corporation. Globus Toolkit is a trademark of the University of Chicago. GNU is a trademark of The Free Software Foundation. HYPERchannel is a trademark of Storage Technology Corporation. IBM is a trademark of
International Business Machines Corporation. IRIX, Silicon Graphics, and XFS are trademarks of Silicon Graphics, Inc. Kerberos is a trademark of Massachusetts Institute of Technology. Linux is a trademark of Linus Torvalds. LSI is a trademark of LSI Logic
Corporation. MAGMA is a trademark of MAGMA, a Mobility Electronics, Inc., company. NFS, Solaris, Sun Blade, Sun, and Sun
Microsystems are trademarks of Sun Microsystems, Inc. in the United States and other countries. PBS Pro is a trademark of Altair
Grid Technologies. SPARC, SPARCstation, and UltraSPARC are trademarks of SPARC International, Inc. Proper use is allowed under licensing agreement. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc.
StorNext is a trademark of Advanced Digital Information Corporation. UNIX and X Window System are trademarks of The Open
Group. ZNYX is a trademark of ZNYX Networks, Inc. All other trademarks are the property of their respective owners.
The UNICOS, UNICOS/mk, and UNICOS/mp operating systems are derived from UNIX System V. These operating systems are also based in part on the Fourth Berkeley Software Distribution (BSD) under license from The Regents of the University of California.
New Features
Cray X1™ System Administration Differences S–2348–24
This manual supports the 2.4 release of the UNICOS/mp operating system on the Cray X1 system.
cws-sync
command was added to Table 2, and information about two new
commands, x1-log-filter and x1-log-viewer
, was added to Section 2.6.3, page 17.
added.
pm
command was added to Table 8, page 65.
admin , comb , delta , get , help , nl , prs , rmdel , sact , sccs , sccsdiff , unget , val , and vc
commands were removed from Table 12, User Commands Not Included for
UNICOS/mp, because they are now implemented for UNICOS/mp.
All other chapters include only minor updates.
Record of Revision
Version
1.0
2.0
2.1
2.2
2.3
2.4
Description
June 28, 2002
First draft printing to support the UNICOS/mp 1.0 and 2.0 releases and the
Cray Workstation (CWS) 1.0 and 2.0 releases.
December 20, 2002
Second draft printing to support the UNICOS/mp 2.0 release and the
Cray Workstation (CWS) 2.0 release.
March 17, 2003
Third draft printing to support the UNICOS/mp 2.1 release and the
Cray Workstation (CWS) 2.1 release.
July 2003
Supports the UNICOS/mp 2.2 release and the Cray Workstation (CWS) 2.2 release.
October 2003
Supports the UNICOS/mp 2.3 release and the Cray Workstation (CWS) 2.2 and
2.3 releases.
March 2004
Supports the UNICOS/mp 2.4 release and the Cray Workstation (CWS) 2.3 and
2.4 releases.
S–2348–24 i
Contents
Preface
Accessing Cray Documentation
Error Message Explanations
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Typographical Conventions .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Ordering Documentation
Reader Comments .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Introduction [1]
SWS and CWS Comparison [2]
Comparison of SWS and CWS Network Environments
Comparison of SWS and CWS Hardware .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Comparison of SWS and CWS Software .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Comparison of CWS Log and SWS Log .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Comparison of CWS and SWS Functionality .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Comparison of SWS and CWS Diagnostics .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CWS Online Diagnostics
CWS Offline Diagnostics
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Monitoring Tools .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Comparison of SWS and CWS Installation .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Installation [3]
Configuration [4]
System Hardware Configuration .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Configuration File .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
RAID C-bricks and S-bricks .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Cray Network Subsystem (CNS) .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
S–2348–24
Page
iii
Cray X1™ System Administration Differences
Page
Cray Programming Environment Server (CPES) .
.
.
.
.
.
.
.
.
.
.
.
.
.
Software Configuration .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Disk Configuration and Administration .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Kernel Subsystem Components .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
User Configuration .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Disk and File System Administration [5]
Partitioning Disks .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
pmd Device Naming Conventions .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
dksc Device Naming Conventions .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Managing Logical Volumes .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Managing File Systems .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
StorNext File System Client and Related Fibre Channel Connection .
.
.
.
.
.
.
.
.
Changing File System Hierarchy .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Comparing Disk and File System Tools .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Networking [6]
I/O Connections .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NFS
DNS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NIS .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
NTP .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Daemons and Commands .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Commands and Daemons Common to UNICOS/mp, UNICOS, and UNICOS/mk .
.
.
.
Commands and Daemons Unique to UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
UNICOS and UNICOS/mk Commands and Daemons Not Supported in UNICOS/mp .
.
Security [7]
Extensions to Traditional UNIX Security Provided with UNICOS/mp .
.
.
.
.
.
.
.
.
Encrypted Password Protection .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Access Control Lists (ACLs) .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Granular Privilege Mechanism .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
iv
S–2348–24
Extensions to Traditional UNIX Security That Are Not Provided with UNICOS/mp .
.
.
.
Audit Mechanism .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Configurable Authentication .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Multilevel Security (MLS) .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
OpenSSH and OpenSSL .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Kerberos Authentication .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Resource Administration [8]
Placement Scheduling .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Application Monitoring .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Limits .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Creating /etc/passwd and /etc/group Files .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Cray Policy for User IDs and Group IDs .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Accounting .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
System Monitoring and Reporting .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Checkpoint/Restart .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Checkpointing Jobs on CPES .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Checkpoint Commands .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Objects Not Checkpoint-safe .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
System Dump Analysis [9]
crashmp Utility .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
dumpmf Utility .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Batch System [10]
Key Features Comparison .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Migrating NQS/NQE Scripts to PBS Pro
ENVIRONMENT Variable .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Additional Information for System Administrators .
.
.
.
.
.
.
.
.
.
.
.
.
.
Administrator Commands [11]
Administrator Commands Unique to UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
.
S–2348–24
Contents
Page
v
Cray X1™ System Administration Differences
Administrator Commands Not Included for UNICOS/mp
Administrator Commands Modified for UNICOS/mp
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
User Commands [12]
User Commands Unique to UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
User Commands Not Included for UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
User Commands Modified for UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Glossary
Index
Figures
Figure 1.
Example of an SWS Network in a GigaRing Configuration .
.
.
.
.
.
.
.
Figure 2.
Example of a CWS Subnetwork in an AC Cray X1 System Environment .
.
.
.
.
Figure 3.
Example of a CWS Subnetwork in a LC Two-cabinet Cray X1 System Environment .
Figure 4.
SWS Directory Structure .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Figure 5.
CWS Directory Structure .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Tables
Table 1.
Comparison of SWS and CWS Hardware .
.
.
.
.
.
.
.
.
.
.
.
.
.
Table 2.
Comparison of SWS and CWS Software .
.
.
.
.
.
.
.
.
.
.
.
.
.
Table 3.
Comparison of SWS Log and CWS Log .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Table 4.
Comparison of SWS and CWS Functionality .
.
.
.
.
.
.
.
.
.
.
.
.
Table 5.
Standard Partition Numbers, Names, and Functions .
.
.
.
.
.
.
.
.
.
.
Table 6.
Disk and File System Tools Comparison
Table 7.
PBS Pro and NQE Key Feature Comparison
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Table 8.
Administrator Commands Unique to UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
Table 9.
Administrator Commands Not Included for UNICOS/mp .
.
.
.
.
.
.
.
.
Table 10.
Administrator Commands Modified for UNICOS/mp .
.
.
.
.
.
.
.
.
.
Table 11.
User Commands Unique to UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
Table 12.
User Commands Not Included for UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
vi
S–2348–24
Page
Table 13.
User Commands Modified for UNICOS/mp .
.
.
.
.
.
.
.
.
.
.
.
.
Contents
Page
S–2348–24 vii
Preface
This manual is intended to assist system administrators and operators as they transition to the Cray X1 operating system, UNICOS/mp. (To assist users and programmers as they transition to the Cray X1 Programming Environment, see
Cray X1 User Environment Differences.)
This preface describes how to access Cray documentation and error message explanations, interpret our typographical conventions, order Cray documentation, and contact us about this document.
Accessing Cray Documentation
Each software release package includes the CrayDoc documentation system, a collection of open-source software components that gives you fast, easy access to and the ability to search all Cray manuals, man pages, and glossary in HTML and/or PDF format from a web browser at the following locations:
• Locally, using the network path defined by your system administrator
• On the Cray public web site at: http://www.cray.com/craydoc/
All software release packages include a software release overview that provides information for users, user services, and system administrators about that release.
An installation guide is also provided with each software release package.
Release overviews and installation guides are supplied in HTML and PDF formats as well as in printed form. Most software release packages contain additional reference and task-oriented documentation, like this document, in
HTML and/or PDF formats.
Man pages provide system and programming reference information. Each man page is referred to by its name followed by a number in parentheses: manpagename( n ) where n is the man page section identifier:
3
4
1
2
User commands
System calls
Library routines
Devices (special files) and Protocols
S–2348–24 ix
Cray X1™ System Administration Differences
5
7
8
File formats
Miscellaneous information
Administrator commands
Access man pages in any of these ways:
• Enter the man command to view individual man pages in ASCII format; for example: man ftn
To print individual man pages in ASCII format, enter, for example: man ftn | col -b | lpr
• Use a web browser with the CrayDoc system to view, search, and print individual man pages in HTML format.
• Use Adobe Acrobat Reader with the CrayDoc system to view, search, and print from collections of formatted man pages provided in PDF format.
If more than one topic appears on a page, the man page has one primary name
( grep , for example) and one or more secondary names ( egrep , for example).
Access the ASCII or HTML man page using either name; for example:
• Enter the command man grep or man egrep
• Search in the CrayDoc system for grep or egrep
Error Message Explanations
Access explanations of error messages by entering the explain msgid command, where msgid is the message ID string in the error message. For more information, see the explain (1) man page.
x S–2348–24
Preface
Typographical Conventions
The following conventions are used throughout this document:
Convention command variable user input
[ ]
...
Meaning
This fixed-space font denotes literal items, such as file names, pathnames, man page names, command names, and programming language elements.
Italic typeface indicates an element that you will replace with a specific value. For instance, you may replace filename with the name datafile in your program. It also denotes a word or concept being defined.
This bold, fixed-space font denotes literal items that the user enters in interactive sessions. Output is shown in nonbold, fixed-space font.
Brackets enclose optional portions of a syntax representation for a command, library routine, system call, and so on.
Ellipses indicate that a preceding element can be repeated.
Ordering Documentation
To order CDs containing software documentation for a release, CrayDoc server software, or additional printed copies of the release overviews and installation guides, contact your Cray representative or contact the Cray Software
Distribution Center in one of the following ways:
E-mail: [email protected]
Telephone (inside U.S., Canada):
1–800–284–2729 (BUG CRAY), then 605–9100
Telephone (outside U.S., Canada):
+1–651–605–9100
Fax:
+1–651–605–9001
S–2348–24 xi
Cray X1™ System Administration Differences
Mail:
Software Distribution Center
Cray Inc.
1340 Mendota Heights Road
Mendota Heights, MN 55120–1128
USA
Reader Comments
Contact us with any comments that will help us to improve the accuracy and usability of this document. Be sure to include the title and number of the document with your comments. We value your comments and will respond to them promptly. Contact us in any of the following ways:
E-mail: [email protected]
Telephone (inside U.S., Canada):
1–800–950–2729 (Cray Customer Support Center)
Telephone (outside U.S., Canada):
+1–715–726–4993 (Cray Customer Support Center)
Mail:
Software Publications
Cray Inc.
1340 Mendota Heights Road
Mendota Heights, MN 55120–1128
USA xii S–2348–24
S–2348–24
Introduction [1]
This guide is intended to assist UNICOS and UNICOS/mk system administrators and operators as they transition to the Cray X1 operating system,
UNICOS/mp.
Specifically, the guide points out commonalities and differences of supercomputer administrative tasks from the UNICOS 10.0.1.0 or UNICOS/mk
2.0.6 system with a Cray system workstation (SWS) running the SWS 6.2 release to the UNICOS/mp 2.4 system with a Cray Workstation (CWS) running the
CWS 2.3 or 2.4 release.
Because the UNICOS/mp, UNICOS/mk, and UNICOS systems are all based on the UNIX system, the administrative tasks have more similarities than differences.
Cray X1 system administration encompasses the CWS software, which includes RAID administration; the UNICOS/mp operating system; the Cray
Programming Environment Server (CPES) software; and the Cray Network
Subsystem (CNS) software.
As a system administrator or operator of Cray X1 systems, you should be familiar with the following software releases and documents:
• Cray Workstation (CWS) release package, which includes the following
CWS administration documentation:
– Cray Workstation (CWS) Release Overview
– Cray Workstation (CWS) Installation Guide
– Cray X1 Configuration and CWS Administration
• Cray Programming Environment Server (CPES) release package, which includes the following CPES administration documentation:
– Cray Programming Environment Server (CPES) Release Overview and
Installation Guide
– Cray Programming Environment Server Administration
• Cray Fortran Programming Environment release package and/or the Cray
C and C++ Programming Environment release package, which include administration scripts, module files, and the Cray Programming Environment
Releases Overview and Installation Guide
1
Cray X1™ System Administration Differences
2
• Modules release package (also included with the Cray Programming
Environment release packages)
• Cray Network Subsystem (CNS) release package, which includes the Cray
Network Subsystem (CNS) Software Release Overview and Installation Guide
• UNICOS/mp release package, which includes the following UNICOS/mp administration documentation:
– UNICOS/mp Release Overview
– UNICOS/mp Installation Guide
– UNICOS/mp System Administration
– UNICOS/mp Disks and File Systems Administration
– UNICOS/mp Networking Facilities Administration
Installation and administration of UNICOS/mp documentation and CrayDoc documentation system is described in the CrayDoc Installation and Administration
Guide.
Additional details about UNICOS/mp are available in individual man pages and the following man page collections:
• Man Page Collection: UNICOS/mp Administrator Commands
• Man Page Collection: UNICOS/mp User Commands
• Man Page Collection: UNICOS/mp File Formats and Special Files
• Man Page Collection: UNICOS/mp System Calls
• Man Page Collection: UNICOS/mp Library Routines
In addition, details about CNS and CWS are available in individual man pages
(from the CWS) and the following man page collections:
• Man Page Collection: Cray Network Subsystem (CNS)
• Man Page Collection: Cray Workstation (CWS)
If your site also chooses to use any of the following products, you should also know the administration needs for these software packages:
• Message Passing Toolkit (MPT) release package, which includes the Cray
Message Passing Toolkit Release Overview
S–2348–24
S–2348–24
Introduction [1]
• Etnus TotalView release package, which includes TotalView Release Overview,
Installation Guide, and User’s Guide Addendum for Cray X1 Systems and
TotalView documentation from Etnus LLC
• Cray Open Software release package, which includes the Cray Open Software
Release Overview and Installation Guide and documentation about each included software package
• PBS Pro release package for UNICOS/mp systems, which includes the PBS
Pro Release Overview, Installation Guide, and Administration Addendum for Cray
Systems and PBS Pro documentation from Altair Grid Technologies
3
Cray X1™ System Administration Differences
4 S–2348–24
SWS and CWS Comparison [2]
This chapter compares the Cray system workstation (SWS) and the
Cray Workstation (CWS).
The SWS and the CWS both function as the system and maintenance workstation used to operate and manage the Cray mainframe. However, the SWS and the
CWS are not interchangeable and have separate sets of documentation.
For more information about CWS, see the following manuals:
Cray Workstation (CWS) Release Overview, Cray Workstation (CWS) Installation
Guide, and Cray X1 Configuration and CWS Administration.
2.1 Comparison of SWS and CWS Network Environments
The following information briefly compares the SWS GigaRing environment to the CWS in the Cray X1 environment.
Figure 1 shows a simple example of an SWS in a GigaRing configuration. The
multipurpose node (MPN) contains two Small Computer System Interface (SCSI) cards for associated disk devices. The Fibre Channel node (FCN) has two Fibre
Channel Arbitrated loops to SCSI disk devices. An Ethernet connection exists between the MPN or FCN and the SWS via the site’s network for access to the
Cray mainframe. The MPN and FCN both have access to the Warning and
Control System (WACS) interface through a serial line from the SWS.
S–2348–24 5
Cray X1™ System Administration Differences
SCSI WACS
SCSI
HME
FCN
Cray mainframe
GigaRing channel
WACS SCSI
SCSI
MPN
HME ETH
Ethernet concentrator Netblazer modem
WACS
3 2 1 0
HME
SWS
Private network
KEY
FCN -
HME -
Private Ethernet
Ethernet (ETH)
Serial line
Fibre Channel node
MPN -
SCSI -
SWS -
WACS -
Hardware motherboard Ethernet
Multipurpose node
Small computer system interface
System workstation
Warning and control system
Figure 1. Example of an SWS Network in a GigaRing Configuration
6 S–2348–24
S–2348–24
SWS and CWS Comparison [2]
The purpose of the CWS is much like that of the SWS for GigaRing based
systems. Figure 2 shows an example of a CWS network in a single air-cooled
(AC) cabinet Cray X1 environment. The left quad Ethernet card (containing the ports labeled 0 through 3) is used to provide a connection between the CWS and the multicabinet switch (also known as a top level switch) of the System Control
Facility (SCF) (the Cray L1 controllers, Cray L0 controllers, and connecting network equipment of a Cray X1 system). The second quad Ethernet card
(containing the ports labeled 4 through 7) is used to connect to:
• Optional Customer Support Integrated Services Digital Network (ISDN) router
• Private administration network, which connects the CWS to a PC-20 peripheral cabinet that contains the Cray Programming Environment Server
(CPES) and the Cray Network Subsystem (CNS)
Note: The CNS is a specialized router (gateway) for providing IP (Internet
Protocol) access and TCP assist functionality between the Cray mainframe and customer networks. The CPES functions as the server for the Cray
Programming Environment software.
• RAID network, which controls and monitors performance of the RAID
(redundant array of independent disks) C-bricks (controller bricks) and
S-bricks (storage bricks)
• Additional CWSs, if present
7
Cray X1™ System Administration Differences
AC Cray X1 cabinet
Chassis
Nodes
BCUs
Switch
I/O cabinet
IOB
L1
IOB
Switch
PC-20
CB
CB
Switch
PC-20
CPES
CNS
Switch
Multicabinet switch
Customer support
ISDN router
3 2 1 0 7 6 5 4
CWS
Port eri0
Key
Fibre Channel
Source Synchronous Channel
(SSC)
Private Ethernet
System Port Channel (SPC)
AC -
BCU -
CB -
Air-cooled
Brick cooling unit
RAID C-brick
CNS -
CPES -
CWS -
I/O -
IOB -
ISDN -
L1 -
Cray Network Subsystem
Cray Programming
Environment Server
Cray Workstation
Input/Output
I/O board (bridge)
Integrated Service Digital
Network
Cray L1 controller
Figure 2. Example of a CWS Subnetwork in an AC Cray X1 System Environment
8 S–2348–24
SWS and CWS Comparison [2]
The Cray X1 system with two liquid-cooled (LC) cabinets has a CWS network that is somewhat similar to the one shown in the air-cooled cabinet example in
Figure 2, page 8. Figure 3, page 10 shows the Cray X1 system complex with
two liquid-cooled (LC) cabinets and the functional networks to which the
CWS attaches.
S–2348–24 9
Cray X1™ System Administration Differences
LC Cray X1 cabinet
V-side
BP
Nodes
Routers
BCUs
Switch
W-side
BP
Nodes
Routers
BCUs
Switch
LC Cray X1 cabinet
V-side
BP
Nodes
Routers
BCUs
Switch
W-side
BP
Nodes
Routers
BCUs
Switch
I/O cabinet
IOB
L1
IOB
Switch
I/O cabinet
IOB
L1
IOB
Switch
PC-20
CB
CB
Switch
PC-20
CB
CB
CB
Switch
PC-20
CPES
CNS
Switch
Multicabinet switch
CB
CNS -
RAID C-brick
Cray Network Subsystem
Customer support
ISDN router
3 2 1 0 7 6 5 4
CWS
Port eri0
Key
Fibre Channel
Source Synchronous Channel
(SSC)
Private Ethernet
System Port Channel (SPC)
BCU Brick cooling unit
CPES -
CWS -
I/O -
IOB -
ISDN -
L1
LC
SPC -
-
-
Cray Programming
Environment Server
Cray Workstation
Input/Output
I/O board (bridge)
Integrated Service Digital
Network
Cray L1 controller
Liquid-cooled
System Port Channel
Figure 3. Example of a CWS Subnetwork in a LC Two-cabinet Cray X1 System Environment
10 S–2348–24
SWS and CWS Comparison [2]
2.2 Comparison of SWS and CWS Hardware
Table 1 compares the basic SWS and CWS hardware. The SWS is used as the
system workstation for Cray GigaRing based systems. The current CWS hardware configuration is similar to the SWS that currently ships with GigaRing based systems.
Component
Workstation type
Memory
Hard disk
Media drive
Monitor
Motherboard Ethernet connection
Ethernet controller
Modem
Table 1. Comparison of SWS and CWS Hardware
Current SWS Hardware
Two models serve as the SWS: Sun
SPARCstation 5 and Sun UltraSPARC
5
32 MB for Sun SPARCstation 5; 512 MB for Sun UltraSPARC 5
20 GB
CD-ROM for loading SWS software and digital data storage (DDS) tape drive that uses 4 mm digital audio tape (DAT) for SWS backup operations
Color (17-inch)
10/100Base-T Ethernet
Current CWS Hardware:
Sun Blade 150
1024 MB
Two 40 GB internal EIDE drives
DVD-ROM for loading software. The media device for CWS file system backup operations is an external
DDS-4 tape drive with one SCSI PCI controller.
Color (Liquid crystal display (LCD)
15-inch flat panel) monitor
10/100Base-T Ethernet
Sun Quad (4-port) 100Base-T
Controller board
Optional modem
Two ZNYX Quad 10/100Base-T PCI
Controller boards each with four
Ethernet connections. One controller is for the System Control Facility network and the other controller is for the other four CWS private networks.
Optional ISDN router with a Customer
Support contract.
S–2348–24 11
Cray X1™ System Administration Differences
Component
Other
Connections
Current SWS Hardware
Optional MAGMA serial port server and modem.
SWS and its associated mainframes connect to GigaRing based I/O equipment.
Current CWS Hardware:
Two serial ports and three PCI slots.
CWS connects by Ethernet to the
System Control Facility, which includes the Cray L1 controllers, Cray
L0 controllers, CWS(s) and connecting network equipment.
2.3 Comparison of SWS and CWS Software
Table 2 compares SWS and CWS software.
Topic
Release relationship
Account for install
Installation
Open source software
SWS Software
Table 2. Comparison of SWS and CWS Software
SWS-ION releases are separate from
UNICOS and UNICOS/mk releases.
Requires using the root account to install the system workstation software and set up new user accounts.
SWS uses the Common Installation Tool
(CIT) to perform the SWS installation.
UNICOS and UNICOS/mk are installed from the SWS.
OpenSSH, Tcl/Tk, and expect are integrated into SWS software package.
CWS Software
CWS release is separate from the
UNICOS/mp release.
Similar to SWS software.
CWS uses the CIT to perform the CWS installation. UNICOS/mp is installed from the CWS.
Note: The Cray Open Software product is not supported on the SWS, but it is available for purchase to use on Cray computer systems.
OpenSSH, OpenSSL, Tcl/Tk, expect, busybox, rsync, htmlwidget, libpcap, modules, net-snmp, newsyslog, nfs-utils, ntp, ntpclient, perl, portmap, squashfs, sudo, top, vnc, zlib, bwidget, and tktable are integrated into the CWS software package.
Note: The Cray Open Software (COS) product is not supplied on the CWS, but it is available for purchase to use on the
Cray X1 system.
12 S–2348–24
SWS and CWS Comparison [2]
Topic
Operating system
Dump, halt, and boot
Backup and
Restore
I/O Node
(ION)
SWS Software
SWS uses a Sun SPARCstation 5 running
Solaris 2.5 with Common Desktop
Environment (CDE) or a Sun UltraSPARC 5 running Solaris 7 with CDE.
The SWS has commands to boot, halt, and dump each of its associated systems; for example, boot xxx(8), halt xxx(8), and dump xxx(8), where xxx is sv1 for Cray SV1 systems, t3e for Cray T3E systems, and t90 for Cray T90 systems.
The swsbackup (8) command is used to dump SWS file systems for backup. The
Solaris ufrestore (1M) command is used to restores those file systems.
CWS Software
CWS runs Solaris 8 with CDE.
The CWS has commands to boot, halt, and dump all or parts of the Cray X1 system; for example, bootx1 (8), haltx1 (8), dumpsys (8), dumpmf (8), and mboot (8).
Similar to SWS, except the CWS uses the cwsbackup (8) command to dump file systems for backup and has the cwshotbackup (8) command to backup the
CWS boot disk.
SWS contains ION operational software.
The cws-sync (8) command is used to synchronize the primary CWS with a second emergency CWS.
N/A
S–2348–24 13
Cray X1™ System Administration Differences
Topic
Diagnostics
SWS Software
Uses online and offline diagnostics and monitoring.
User accounts and groups
SWS standard user accounts are crayadm , craydiag , and crayops . Standard groups on the system are crayadm , craydiag , crayops , and craynouser .
Each of the standard user accounts has a unique shell environment with a basic setup supplied by Cray that allows for site-modifiable environment files that do not change between SWS-ION software upgrades.
CWS Software
Uses online and offline diagnostics and monitoring. However, except for x1cpes , the online diagnostics are included in
UNICOS/mp.
CWS software has several components that provide control over the Cray X1 system including the Cray L1 controller and Cray L0 controller, which have both software and firmware, the CWS, RAID disks, and some diagnostics. The crayscan software is diagnostics code for Cray X1 offline module-level diagnostics. CRAYSM software is used to manage the RAID disk subsystem.
CWS standard user accounts are crayadm and crayops . Standard groups are crayadm , crayops , and craynouser .
There is no craydiag account or group on the CWS; instead, functionality similar to that of the SWS craydiag account is contained in the CWS crayadm account.
Each of the standard user accounts has a similar setup for their unique shell environment, which is similar to the
SWS-ION software.
14 S–2348–24
SWS and CWS Comparison [2]
2.4 Comparison of CWS Log and SWS Log
Table 3 compares CWS Log and SWS Log.
Table 3. Comparison of SWS Log and CWS Log
SWS Log
The SWS-ION software does not include system error log monitoring on the mainframe. As a result, the software does not provide thresholding or automatic notification when problems occur, and the problems are observable only from the system error logs. Operators must manually monitor the system using the errpt (8) command on the mainframe, the sserrpt command on the multipurpose node
(MPN), and watchlog , watchstream , sysmon , and nwacs on the SWS.
SWS software uses the SWS syslogd (1M) command to log messages. All log files for mainframes, Cray SSD-T90 devices, I/O nodes, and the SWS are located in the /opt/CYRIlog directory.
The SWS software uses the syslog (3) facilities
LOG_LOCAL0 through LOG_LOCAL5 .
CWS Log
The CWS is the focal point for all components of the Cray X1 system that can send a message via the Cray provided syslogd (8) utility; this includes messages from the System Control Facility
(Cray X1 mainframe, CWS, Cray L1 controllers,
Cray L0 controllers), CPES, CNS, RAID subsystems, and CWS command line invocations. The Cray syslogd daemon provides functionality similar to the syslogd daemon used in FreeBSD and Linux systems, and has the basic functionality to perform simple string matches. The CWS syslog daemon ensures that messages are filed according to their point of origin. Messages may be stored in duplicate locations, depending on their priority and content.
All CWS log messages go into files in
/opt/craylog .
All informational messages ( LOG_DEBUG and LOG_INFO ) are sent to the appropriate logname .info
file; for example, ion_syslog.info
, sws_operlog.info
, sws_syslog.info
, and elog.info
. All other messages (notice, warning, error, alert, and critical) are routed to the regular log file; for example, to ion_syslog , and so on.
CWS software has the watchlog and watchstream , which are similar to their
SWS counterparts.
2.5 Comparison of CWS and SWS Functionality
Table 4 lists similarities and differences between CWS and SWS functionality. The
major difference between the SWS and CWS is the network.
S–2348–24 15
Cray X1™ System Administration Differences
SWS Interfaces:
Table 4. Comparison of SWS and CWS Functionality
CWS Interfaces:
The SWS command line interface lets you configure, operate, administer, monitor, and diagnose Cray systems in a scalable I/O (SIO) environment based on GigaRing technology. However, the SWS graphical user interface (GUI) can only monitor
GigaRing based systems.
SWS Networks (2):
Private network: The SWS has one private network with static IP addresses for the various IONs, and uses the bootp command and protocol to boot the
IONs, assign host names, and so on.
Warning and Control System (WACS): This network is for hardware monitoring and control.
The CWS provides a command line interface and an operator GUI to control and monitor system components and provide a platform to monitor, boot, halt, and dump the Cray X1 mainframe in addition to other maintenance activities.
CWS Networks (5):
Private Administration network: This network connects the CWS to the CPES and the CNS. This hardware is located in Cray X1 PC-20 cabinets.
System Control Facility (SCF) network: The System
Control Facility consists of the Cray L1 controllers,
Cray L0 controllers, CWS(s) and connecting network equipment of the Cray X1 system. Besides diagnostics, system controller functions provide system configuration capabilities, system booting, and partitioning support. The Cray X1 system bring-up sequence is controlled from the CWS through the Cray L1 controllers. X1WACS ( x1wacs application) uses the System Control Facility network to do its work; there is not a private WACS network like on the SWS.
RAID network: The RAID network connects the
CWS to the RAID C-bricks (controllers), which are used to control the RAID S-bricks (storage bricks), that is, the disk arrays.
Customer Support network: The Customer Support network provides remote support access to the CWS through a separate hardware connection.
CWS network: This CWS shared private network only exists when there are multiple CWSs connected to a Cray X1 system. This network connects the various CWSs, if present, together through a switch.
16 S–2348–24
SWS and CWS Comparison [2]
2.6 Comparison of SWS and CWS Diagnostics
The CWS and SWS both have online and offline diagnostics, logs, and monitoring
tools. For a comparison of logs, see Section 2.4, page 15.
2.6.1 CWS Online Diagnostics
CWS online diagnostics and tests include but are not limited to:
• The x1cpes (8) test, which verifies the connection between the Cray X1 mainframe and the CPES
• The memtest (8), memsnoop (8), and test_ioca_mmrs (8) tests, which are part of the CWS release and are run from the CWS or Cray L1 controller
• Codes to monitor Cray X1 system processor health, interconnects between
Cray X1 processors, and available memory
• Disk function tests that write and read available scratch or tmp disk space
Note: Online diagnostics, except x1cpes (8), are distributed as part of the
UNICOS/mp release and are run from the mainframe
2.6.2 CWS Offline Diagnostics
Offline diagnostics include but are not limited to:
• Built-in Self Test (BIST)
• Boundary scan tests and functional diagnostics to test the Cray X1 system offline; these are under the control of Cray support personnel
2.6.3 Monitoring Tools
Some of the monitoring tools available for the SWS or CWS include:
• The CWS l1net (8) utility program, which you can use to produce diagnostic information about the network accessibility of Cray L1 controller components and Cisco switches of the Cray X1 system (including misconfigured switches by their lack of response to IP broadcasts to assure that basic network connectivity is valid).
• The netwatch facility, which runs on the CWS and is used to monitor the network topology against the arrangement of the chassis.
S–2348–24 17
Cray X1™ System Administration Differences
• The opuss operator utility, which runs on the CWS, can be used to display system status and perform basic system functions.
• The System Integrity Check (SICK) tool, which monitors the integrity of various Cray systems and alerts analysts and system administrators when abnormal operating conditions occur. SICK is planned to be integrated for
Remote Support in the SWS-ION 6.3 release. A limited version of SICK has been supported since the CWS 2.0 release.
• The watchlog and watchstream programs monitor a collection of data for regular expressions, which, by default, are any
EMERgency/ALERT/CRITical/ERRor/WARNING messages.
• The x1-log-filter (8) command, which can be used to filter Cray specific information from syslog files.
• The x1-log-viewer (8) command, which starts the graphical user interface for viewing/extracting Cray specific information from syslog files.
• To monitor and control power and to monitor cooling, the CWS uses the
X1WACS interface, whereas the SWS uses the Warning and Control System
(WACS) interface. The x1wacs program is an application running on the
CWS and serves some of the same functions that nwacs did on GigaRing systems. Also note that x1wacs uses the System Control Facility network to do its work; there is not a private network like on the SWS.
2.7 Comparison of SWS and CWS Installation
The cwsrel command on the CWS is used to administer the CWS packages.
The major difference for CWS software installation is that a crayx1_ Release# directory gets created for each CWS release. The purpose of creating this directory (directories) is to make it easier to have multiple CWS releases installed on the CWS at the same time. This directory contains most of the CWS software, except the /export/crayl1 directory.
The new /export/crayl1 partition did not exist on the SWS, but is similar in concept and functionality to /opt/CYRIion . The /export/crayl1 directory contains the Cray L1 controller’s root file system, which is exported from the
CWS to every Cray L1 controller in the Cray X1 system.
cray prefix, as opposed to CYRI for the SWS.
18 S–2348–24
SWS and CWS Comparison [2]
/opt
CYRI_overview
CYRIccmt
CYRI_version
CYRIdiag
CYRIdump
CYRIlog
CYRIops
CYRIos
CYRIinstall
CYRIion
SUNW*
MAGMA*
CYRIpkg bin config local home a10163
Figure 4. SWS Directory Structure
/opt
|
|
-----------------------------------------------------------------------------
| | | | | | | | | | | | | | | | craycfg/ | crayl1@ | dump@ | log/ | craylog/ | crayx1@ | crayos/ | os@ | rsc
| | | | | | | | | craydump/ |
| home/ |
|
Acrobat5 SM8 |
|
TT_DB craysm/ crayx1_release#/
|
|
|
|
|
|
| |
---------------bin/
| kernel/
| snXXXX/
|
|
|
| |
------------------------------------------
SUNWconn/
|
SUNWebnfs/
|
SUNWits/
|
SUNWrtvc/
|
---------------------------------------------------------
| | | | |
|
SUNWvts/ craydiag craymcu crayops/ crayoverview/ crayscan/ crayversion
| crayonlines
Figure 5. CWS Directory Structure
S–2348–24 19
Cray X1™ System Administration Differences
20 S–2348–24
S–2348–24
Installation [3]
Installation of the UNICOS/mp operating system on a Cray X1 system is similar to the installation process of the UNICOS operating system, using the Common
Installation Tool (CIT). Details for installation and using CIT for the Cray X1 system are described in the UNICOS/mp Installation Guide and the Common
Installation Tool (CIT) Reference Card.
The UNICOS/mp operating system is distributed on CD or DVD media.
The installation process is executed on the Cray Workstation (CWS). A major difference from the UNICOS and UNICOS/mk installation processes is that for
UNICOS/mp, most of the hardware configuration is determined dynamically by the kernel. All other hardware configuration is performed prior to shipping, as documented in the CWS release documentation.
In UNICOS and UNICOS/mp, the RAM file system used for installation is transmitted to the mainframe at boot time from the SWS and CWS, respectively.
In UNICOS/mk, the RAM file system is first stored on the MPN (multipurpose node), which is booted directly from the disk.
A Cray X1 system includes the Cray Programming Environment Server
(CPES) and Cray Network Subsystem (CNS). Software installation, as well as configuration and administration, for these products is documented in the Cray
Programming Environment Server Administration, Cray Programming Environment
Server (CPES) Release Overview and Installation Guide, and the Cray Network
Subsystem (CNS) Software Release Overview and Installation Guide.
Note: Refer to the Cray Programming Environment Releases Overview and
Installation Guide for installation and configuration of the Cray Programming
Environment on the CPES.
21
Cray X1™ System Administration Differences
22 S–2348–24
Configuration [4]
Configuration of the UNICOS/mp operating system on a Cray X1 system is done primarily from the Cray Workstation (CWS) and is described in Cray X1
Configuration and CWS Administration.
This chapter documents the major configuration differences that exist between
UNICOS and UNICOS/mk systems and UNICOS/mp systems.
4.1 System Hardware Configuration
The system hardware is configured by CWS commands as described in
Cray X1 Configuration and CWS Administration. Some of the system hardware configuration is similar to previous Cray systems, but the complexity has increased with the flexibility of the Cray X1 hardware.
Four major areas of difference include:
• Configuration file ( cray.cfg
)
• RAID controller bricks (C-bricks) and storage bricks (S-bricks)
• The Cray Network Subsystem (CNS)
• The Cray Programming Environment Server (CPES)
Each of these differences is described briefly in the following sections.
4.1.1 Configuration File
S–2348–24
The Cray X1 system configuration is based on information in a configuration text file that resides on the CWS, similar to GigaRing based systems and the SWS.
Information in the cray.cfg
system configuration file includes:
• Hardware present in the system
• Number and type of chassis
• Number, types, and locations of modules
• Type of memory on the node modules
• Number of I/O channel adapter (IOCA) modules and their locations
• Connectivity of the System Port Channels (SPCs)
23
Cray X1™ System Administration Differences
• Degradation information
• Ways to partition the system
The x1config (8) utility builds (reconfigures) and verifies the Cray X1 hardware configuration files. For more information, see the x1config (8) and x1config (5) man pages.
The routing initialization program cwsrte (8) (for configuring the memory routing network) is based on the CWS. For systems using the SWS, GigaRing topology files and options files describe the layout of the mainframe and I/O nodes (IONs) on the GigaRing channel.
4.1.2 RAID C-bricks and S-bricks
The hardware building blocks for I/O are the C-brick and S-brick.
The RAID C-brick is like a Fibre Channel node (FCN). A C-brick can have multiple RAID drives attached and has an Ethernet port to monitor the performance of the disks in the RAID. Each RAID C-brick is preconfigured. Cray assigns IP addresses and a host name to each RAID. The peripheral cabinets
(PC-20s) house RAID C-bricks, RAID S-bricks, controllers, and disks.
The RAID subsystem is housed in storage bricks (S-bricks), which are connected to a C-brick. The number of S-bricks that are attached to a C-brick is configuration dependent but is generally 2, 4, 6, or 8 S-bricks per C-brick.
On startup, UNICOS/mp scans all volume headers and makes available a special file in the /hw virtual file system for every discovered partition. Symbolic links from the /dev directory to the /hw are typically set up.
For detailed information about administering and partitioning UNICOS/mp
RAID devices, see UNICOS/mp Disks and File Systems Administration.
4.1.3 Cray Network Subsystem (CNS)
A Cray X1 system includes a Cray Network Subsystem (CNS) for network routing. In addition to bridging from Fibre Channel connections to network protocols, the CNS provides IP packet management, minimizing the impact on the Cray X1 processors.
The CNS supports Fibre Channel connection(s) to the Cray X1 mainframe and
Gigabit Ethernet connection(s) to a site’s network.
24 S–2348–24
Configuration [4]
The CNS can be configured for automatic failover using a Fibre Channel
IP bonded interface if you configure a bonding interface on the CNS and a corresponding UNICOS/mp bonding interface on the Cray X1 mainframe.
For detailed information about the CNS, see the Cray Network Subsystem (CNS)
Software Release Overview and Installation Guide.
4.1.4 Cray Programming Environment Server (CPES)
The Cray Programming Environment resides on the CPES. Program executions are invoked by user commands on the Cray X1 mainframe and are executed on the CPES transparent to the user. There is no user access (login) directly to the CPES.
The CPES is cross-mounted (via NFS) to the Cray X1 system. On invocation of the compiler, the user’s environment is captured along with local file information, and transferred to the CPES.
For detailed information about CPES software installation and administration, see Cray Programming Environment Server (CPES) Release Overview and Installation
Guide and Cray Programming Environment Server Administration.
Note: Refer to Programming Environment documentation for installation of a Cray Programming Environment on the CPES.
4.2 Software Configuration
UNICOS/mp software configuration is different from UNICOS and
UNICOS/mk systems in the areas of disk and file system administration, kernel subsystem components, and user configuration.
4.2.1 Disk Configuration and Administration
The UNICOS/mp system uses an array of disks with built-in redundancy
(called RAID devices) exclusively for storage. In addition, UNICOS/mp treats
RAID volumes as a single Logical Volume and communicates to it only through a RAID controller. In effect, the whole physical disk infrastructure is now invisible (and under total control of the RAID subsystem); all UNICOS/mp sees is virtual devices.
For disk and file system administration, the UNICOS/mp system includes the
XFS file system, the XLV volume manager, and Cray Storage Management
(CRAYSM) tools. Together, their features provide equivalent functionality to the
S–2348–24 25
Cray X1™ System Administration Differences most important disk and file system administration features in UNICOS and
UNICOS/mk.
Disk configuration on UNICOS/mp systems uses /dev/rdsk and /dev/dsk entries. Configuring and managing UNICOS/mp RAID controllers is done primarily through CRAYSM tools on the CWS.
The UNICOS and UNICOS/mk systems provide layers of drivers for:
• Organizing partitions and logical devices into mirrored logical volumes
• Organizing partitions and logical devices into striped logical volumes
• Concatenating partitions and logical devices to form a file system
These features are provided by various layers of drivers in the kernel, supported by the mknod (8) command, which creates special devices that define the configurations of volumes.
In a UNICOS/mp system, the XLV volume manager provides similar functionality. A volume (file system) contains a data subvolume, an optional log subvolume, and an optional real-time subvolume. Subvolumes are made of one to four plexes (mirrors) for one- to-four-way replication of data for reliability. Up to 128 volume elements can be concatenated into a plex. At the lowest level, up to
100 partitions can be concatenated or striped into volume elements.
For more information about UNICOS/mp RAID devices, see Cray X1
Configuration and CWS Administration and UNICOS/mp Disks and File Systems
Administration.
For more information about XLV concepts and commands, see UNICOS/mp
Disks and File Systems Administration.
4.2.2 Kernel Subsystem Components
26
The configuration of NFS on UNICOS and UNICOS/mk is controlled by setting kernel subsystem parameters through the ICMS.
Configuration of NFS on UNICOS/mp is through the chkconfig (8) command.
The chkconfig command configures on (or off) various available subsystems and daemons during system startup and during system operation.
The systune (8) command also provides a way to configure certain system parameters, either dynamically (on a running system) or statically (before booting the system).
For additional information, see the chkconfig (8) and systune (8) man pages.
S–2348–24
Configuration [4]
4.3 User Configuration
User configuration is different on UNICOS/mp in two ways:
• Configuring/adding users
• Setting user limits
There is no UDB (User Database) on UNICOS/mp. Configuring/adding users on
UNICOS/mp is a manual process.
UNICOS and UNICOS/mk job limits are not supported in UNICOS/mp.
Specifying user limits has been simplified for UNICOS/mp using the limit_mkdb (8) command rather than udbgen (8).
For additional information about limits, see UNICOS/mp System Administration, and the limit_mkdb (8) man page.
S–2348–24 27
Cray X1™ System Administration Differences
28 S–2348–24
Disk and File System Administration [5]
This chapter addresses the most important disk and file system feature differences between UNICOS/mp and the UNICOS and UNICOS/mk systems.
The UNICOS/mp system uses an array of disks with built-in redundancy (called
RAID devices) exclusively for storage. In addition, UNICOS/mp treats RAID volumes as a single, logical volume and communicates to it only through a RAID controller. In effect, the whole physical disk infrastructure is now invisible (and under total control of the RAID subsystem); UNICOS/mp sees only virtual devices.
For disk and file system administration, the UNICOS/mp system provides the
XFS file system, the XLV volume manager, and Cray storage management tools, provided by the CRAYSM software. Together, their features provide equivalent functionality to the most important disk and file system administration features in UNICOS and UNICOS/mk.
Complete information about disk and file system administration on
UNICOS/mp is provided in UNICOS/mp Disks and File Systems Administration.
5.1 Partitioning Disks
In UNICOS and UNICOS/mk systems, physical disks are partitioned using the mknod (8) command to create device nodes in the /dev directory. In UNICOS systems, it is possible to use solid-state storage devices (SSD) memory as a disk partition.
Note: UNICOS/mp does not support SSDs.
Instead of the device nodes manually built by mknod , UNICOS/mp RAID devices are defined using more conventional UNIX /dev/rdsk entries, as well as /dev/dsk entries. Configuring and managing UNICOS/mp RAID controllers is done primarily through CRAYSM on the Cray Workstation (CWS).
Each partition on a RAID device has a number from 0 through 15. By convention,
some of these partition numbers have a particular function and a name. Table 5
shows these numbers, names, and functions.
S–2348–24 29
Cray X1™ System Administration Differences
30
!
Partition
Number
0
1
2–7
8
9
10
11–15
Table 5. Standard Partition Numbers, Names, and Functions
Name root swap
Function
Root partition, used for the root file system on system disks
Swap partition, used by UNICOS/mp for temporary storage when there is less physical memory than all of its processes need
(none) General-purpose partitions volhdr Volume header
(none) Reserved partition (historically, this partition was the bad block partition on non-SCSI drives) volume The entire disk, including the volume header
(none) General-purpose partitions
UNICOS/mp RAID devices can be partitioned using the parts (8) command; it stores partition information on the device in the volume header partition. Each device can be sliced into a maximum of 16 partitions.
On startup, UNICOS/mp scans all volume headers and makes available a special file in the /hw virtual file system for every discovered partition. Symbolic links from the /dev directory to the /hw directory are typically set up to maintain
UNIX conventions.
Devices for UNICOS/mp systems are automatically built and automatically named using one of two disk drivers, the path-managed disk driver ( pmd ) or the
UNIX disk driver ( dksc ). The UNICOS/mp 2.4 release is the final release that supports both pmd and dksc . As of the UNICOS/mp 2.5 release, only pmd will be supported. Information about how to convert from dksc to pmd is included in
UNICOS/mp Disks and File Systems Administration.
Note: Beginning with the UNICOS/mp 2.4 release, new systems are shipped with the path-managed disk driver ( pmd ) as the default disk driver.
pmd names disk devices after the physical device; dksc names disk devices after the path with which they are connected to the host system.
Caution: The pmd driver and the dksc driver cannot be used concurrently.
The pmd driver offers several distinct advantages, it:
S–2348–24
Disk and File System Administration [5]
• Provides failover and dynamic path management without using XLV
• Provides all disk devices with a coherent, common set of disk capabilities
• Removes the naming confusion factor that could allow damage to file system data
• Eliminates the need to track multiple path names to a disk array (that is, it allows multiple paths to a disk array with one name)
Instructions to convert to the path-managed disk driver as well as for administering and partitioning UNICOS/mp RAID devices are discussed in detail in UNICOS/mp Disks and File Systems Administration.
5.1.1
pmd Device Naming Conventions
Using the pmd driver, this is the naming convention for disk devices: pm C d S L U s P where:
C
S
Chassis number
Slot of the C-Brick in the chassis
U
P
Logical Unit Number. This value is assigned by the RAID subsystem.
Partition (or Slice) number. This is governed by how the administrator of UNICOS/mp has partitioned the logical volume using the parts command.
For example, pm2d1L3s0 names the disk storage at chassis 2, slot 1, LUN
3, partition (slice) 0.
5.1.2
dksc Device Naming Conventions
Using the dksc driver, this is the naming convention for disk devices: dks C d T l L s P where:
C Logical Bus Number or Function Number.
A number listed in the cray.cfg
file that corresponds to the Fibre Channel port on a given
S–2348–24 31
Cray X1™ System Administration Differences
T
Fibre Channel network interface card in a given
I/O channel adapter. Also called the Controller
Number.
Target ID (on bus). This is the Fibre Channel loop
ID of a host port on a RAID controller. What the host connections on the RAID are set to typically governs this value.
L
P
Logical Unit Number. This value is assigned by the RAID subsystem. Note that UNICOS/mp omits the lprefix and the L from the name when L is zero.
Partition (or Slice) number. This is governed by how the administrator of UNICOS/mp has partitioned the logical volume using the parts command.
For example, dks3d2l4s0 names the disk storage at controller 3, disk target 2,
LUN 4, slice 0.
5.2 Managing Logical Volumes
The UNICOS and UNICOS/mk systems provide layers of drivers for:
• Organizing partitions and logical devices into mirrored logical volumes
• Organizing partitions and logical devices into striped logical volumes
• Concatenating partitions and logical devices to form a file system
The various layers of drivers in the kernel are supported by the mknod (8) command, which creates special devices that define the configurations of volumes.
The UNICOS/mp system XLV volume manager provides similar functionality. A volume (file system) contains a data subvolume, an optional log subvolume, and an optional real-time subvolume. Subvolumes are made of one to four plexes
(mirrors) for one- to-four-way replication of data for reliability. Up to 128 volume elements can be concatenated into a plex. At the lowest level, up to 100 partitions can be concatenated or striped into volume elements.
The xlv_make (8) man page describes the process of defining logical volumes, and the xlv (7) man page provides an overview of the logical volume feature.
The xlv_mgr (8) command can be used to administer logical volumes, such as
32 S–2348–24
Disk and File System Administration [5]
!
adding volume elements and plexes to logical volumes when there is already data in the logical volume.
Caution: Two critical differences exist between NC1 (the file system of the
UNICOS and UNICOS/mk operating systems) and XFS/XLV logical volume implementations:
• XLV/XFS places metadata and small files on all allocation groups in a file system (that is, there is no notion of primary and secondary allocation).
• An XFS/XLV storage combination can be tailored for parallel I/O by placing files into sequentially allocated directories. This will cause the files to be physically separated into different allocation groups.
Because of these two differences, XFS file systems should typically be configured using striping. UNICOS/mp does not support user-level striping, which is supported on UNICOS and UNICOS/mk systems using the open (2)
( cbits / cblks ) system call and the assign -p command. This means that for UNICOS/mp systems, all striping must be configured at the XLV level by the system administrator.
5.3 Managing File Systems
UNICOS and UNICOS/mk use the NC1 file system. NC1 supports the concept of primary and secondary partitions, where metadata (such as directories and inodes) are placed on primary partitions, and only data blocks are placed on secondary partitions. Allocation units can be set differently for primary and secondary partitions. The NC1 file system offers a choice of one of three round-robin allocation methods: all files, first-level directories, and all directories.
In the NC1 file system, each primary partition can contain a maximum of four inode regions. When the file system runs out of free inodes, the operating system automatically creates an additional inode region, provided the limit of four inode regions per primary partition has not already been reached.
A file’s allocated disk blocks are described by a linear list of variable-length extents. The NC1 file system provides special allocation features for large files, to improve performance by contiguous allocation. When a file is extended by seeking to an address and writing some data, the preceding unwritten space is automatically allocated and filled with zeros.
UNICOS/mp uses the XFS file system. XFS stores a file’s disk blocks in a tree of variable-length extents. XFS is a journaling file system, which means that metadata changes are recorded in a log, and all writes to disk are ordered so that
S–2348–24 33
Cray X1™ System Administration Differences the file system image on disk and the log are always consistent. This allows fast reconstruction of a file system if a system crash occurs before metadata blocks are written to disk. This means that it is not necessary to run the file system consistency check program when the system is restarted.
In UNICOS/mp, file systems can be created on raw devices or XLV logical volumes. XLV logical volumes contain:
• A data subvolume
• An optional log subvolume
• An optional real-time subvolume
With UNICOS/mp, you can use the mkfs_xfs (8) command to create a file system on the logical volume. When mkfs_xfs is run, several file system parameters may be left to the defaults chosen by mkfs_xfs , or specified by the user. These include the block size, the allocation group size, the size of the log, and the size of inodes.
In UNICOS/mp, inodes are distributed among the file system’s allocation groups, which enhances performance in several ways:
• When an inode is allocated for a file, an entire allocation group is locked; therefore, having multiple allocation groups allows file creations to be parallel.
• Related inodes (such as a directory and its entries) are preferentially allocated from the same group.
• Data for each file is preferentially kept in an allocation group with its inode.
Each allocation group has a portion of the inode address space, and new inodes are dynamically created as needed.
Placing the log in a separate subvolume allows the log to be separated from data and be mirrored for extra reliability, if desired. If there is no log subvolume, the log is kept in the data volume. Placing the log in a separate subvolume may also allow for better performance.
Real-time volumes (when used) allocate space in fixed-sized extents, which are sized when creating the file system with mkfs_xfs (8). Extents can be up to 1
GB in multiples of the logical block size for the volume. Applications can use the fcntl (2) system call to designate files as real-time, for placement on the real-time subvolume.
34 S–2348–24
Disk and File System Administration [5]
In addition, the XFS file system supports files with holes, which means that unwritten areas of a file will not consume disk blocks, depending on their position in the file, and these areas appear zero-filled when read.
Note: Backup is done across the network through the Cray Network
Subsystem (CNS).
Cray Programming Environment Server (CPES) files in the Cray X1 system use the distributed Network File System (NFS) to make mounted file systems
available. For more information about NFS and the I/O connections, see Chapter
6, page 39 and Cray Programming Environment Server Administration.
For more information about the XFS file system, see UNICOS/mp Disks and
File Systems Administration.
5.4 StorNext File System Client and Related Fibre Channel Connection
UNICOS/mp software supports the Advanced Digital Information Corporation
(ADIC) StorNext File System (StorNext FS) client software and related Fibre
Channel connection. This feature supports file sharing and file storage for
Cray X1 systems through a storage area network (SAN).
StorNext FS is a high-performance, heterogeneous, shared SAN file system that is usable from Cray X1 systems. StorNext FS safely allows multiple computer systems to share disk storage at the file level. File system data is shared among these computers (StorNext FS clients) across the Fibre Channel fabric at nearly the full Fibre Channel bandwidth. The UNICOS/mp software includes the Cray X1
StorNext FS client and Fibre Channel fabric support.
The Cray X1 hardware can attach to a SAN through Fibre Channel host bus adapters in a Cray X1 I/O drawer.
Note: When using StorNext FS on Cray X1 systems, you must use the path-managed disk driver ( pmd ); the dksc driver is not supported.
UNICOS and UNICOS/mk systems do not support StorNext FS client software and related Fibre Channel connection.
5.5 Changing File System Hierarchy
UNICOS/mp file system hierarchy was implemented to closely comply with the
Filesystem Hierarchy Standard (FHS) Version 2.2.
S–2348–24 35
Cray X1™ System Administration Differences
The following directories are new with the UNICOS/mp; they are not present in either UNICOS or UNICOS/mk:
• /hw contains the hardware graph of the system.
• /sbin is the first of three directories to contain utilities for system administration.
/sbin contains binaries essential for booting, restoring, recovering, and/or repairing the system in addition to commands in /bin while in single-user mode. Commands in this directory are not typically used by users in multiuser mode.
• /usr/sbin is the second directory to contain utilities for system administration. This directory contains binaries that are not needed in single-user mode. Typically, it contains system administration programs that are required for system repair or system recovery.
• /usr/X11 contains the X11 binaries, X11 libraries and X11 include files.
• /usr/libexec is the third directory to contain utilities for system administration. All the system daemons are located here.
• /var is a third high-level addition to the file system. Typically, /var is a separate partition from / . This directory includes spool directories and files, administrative and logging data, run-time data, and transient or temporary files.
In addition to the new directories, the contents of the following directories differ significantly from those in the UNICOS or UNICOS/mk operating systems:
• /etc no longer contains commands. System administrative commands or tools that typically resided in /etc in UNICOS or UNICOS/mk now reside in either /sbin or /usr/sbin in UNICOS/mp. Daemons that reside in /etc in UNICOS or UNICOS/mk now reside in /usr/libexec in
UNICOS/mp. The /etc directory in UNICOS/mp contains configuration and startup information.
• /usr/share/man now contains man pages.
• /usr/bin/X11 , /usr/include/X11 , and /usr/lib/X11 are now symbolic links to corresponding directories in /usr/X11 , where binary commands, include files, and libraries for X11 are located.
36 S–2348–24
S–2348–24
Disk and File System Administration [5]
5.6 Comparing Disk and File System Tools
Table 6 provides a mapping of XFS file system utilities provided with
UNICOS/mp systems to UNICOS and UNICOS/mk file system utilities. For detailed information, see the related man pages and UNICOS/mp Disks and
File Systems Administration.
UNICOS/mp tool mkfs_xfs or mkfs -t xfs xfs_check and xfs_repair xfsdump xfsrestore xfs_growfs xfs_copy xfs_bmap xlv_* parts pm prtvtoc scsifo hinv craid-adm and
Table 6. Disk and File System Tools Comparison
(CWS command), scsicontrol fx ,
Description
Creates a file system
UNICOS and UNICOS/mk tool
Checks file system consistency and repairs file system fsck
Dumps file system incrementally dump
Restores file system incrementally restore
No equivalent Expands an existing mounted file system
Copies a file system to other file systems dd
Prints block maps for an existing file
Administers logical volumes
Makes device slices and tunes devices fck —b mknod mknod
, ddstat , etc.
Provides path-managed disk driver monitor and control
None
Reports device node status (for dksc devices, not pmd devices)
Shows failover status or initiates failover status on a device
Displays the contents of the system hardware inventory table
Provides online disk maintenance and initialization routines mkfs
/etc/stor
/etc/ddstat
/CONFIG xdms
, sdconf
37
Cray X1™ System Administration Differences
38 S–2348–24
Networking [6]
6.1 I/O Connections
The Cray X1 system supports a direct 2-Gbps Fibre Channel connection to the
CPES. The CPES hosts local storage as needed to support the Programming
Environment software.
In addition, the Cray X1 system supports a direct 2-Gbps Fibre Channel connection to the CNS. The CNS in turn acts as an IP router, handling traffic to external networks and external I/O devices. The CNS is the only gateway between the Cray X1 system and outside networks.
6.2 NFS
Cray X1 systems use an IP over Fibre Channel network connection. This can be used to connect to any system that supports this protocol. Both the Cray
Programming Environment Server (CPES) and Cray Network Subsystem
(CNS) are connected to the Cray X1 mainframe in this way. The CNS provides connections between the Cray X1 system and the site’s network.
Networking for UNICOS/mp systems is described in UNICOS/mp Networking
Facilities Administration.
S–2348–24
The UNICOS/mp implementation of NFS is similar to that used in UNICOS and
UNICOS/mk but differs in the following ways:
• UNICOS/mp supports NFS versions 3 (default) and 2, and supports both the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) protocols.
• UNICOS/mp does not support either the Cray UNICOS NFS daemon
( cnfsd ) or PC-NFS daemon ( pcnfsd ).
• UNICOS/mp supports both automount and autofs . These two mounting methods are mutually exclusive and cannot be used on the same system concurrently. The default and preferred method is autofs .
• UNICOS/mp does not support ID mapping in the same sense that UNICOS does. UNICOS/mp has an NFS function called ID mapping, but this is related to the autofs command and the file system and has no similarity to the
UNICOS NFS ID mapping function, which handles network addresses. At
39
Cray X1™ System Administration Differences this time, UNICOS/mp neither requires nor includes a functional equivalent to UNICOS NFS ID mapping.
• UNICOS/mp supports CacheFS, an optional client-side caching system for
NFS. CacheFS reduces read-only data access time but adds overhead for read/write access.
6.3 DNS
The Internet Domain Name Service (DNS) client is supported in the
UNICOS/mp operating system.
Note: Support for DNS (the Berkeley Internet Name Domain (BIND)) server is deferred.
6.4 NIS
The Network Information Service (NIS) client is supported in the UNICOS/mp operating system.
Note: The NIS server functionality is deferred.
6.5 NTP
The Network Time Protocol is supported in UNICOS/mp. Because is it based on the NTP version 4 protocol, and UNICOS and UNICOS/mk are based on the NTP version 1 protocol, there are vast differences in functionality. See
UNICOS/mp Networking Facilities Administration for details on NTP functionality.
6.6 Daemons and Commands
This section lists the daemons and network administration commands that are
common to UNICOS/mp, UNICOS, and UNICOS/mk (Section 6.6.1, page 41),
that are new in UNICOS/mp (Section 6.6.2, page 44), and that are not supported
in UNICOS/mp (Section 6.6.3, page 45).
40 S–2348–24
Networking [6]
6.6.1 Commands and Daemons Common to UNICOS/mp, UNICOS, and UNICOS/mk
The following network administration commands and daemons are common to
UNICOS/mp, UNICOS, and UNICOS/mk. Differences in usage and syntax are noted here. Details are provided in the respective man pages.
arp (8) automount domainname exportfs fingerd finger ftpd ftp lp (1) mail
(8)
(1) hostid inetd lockd
(1) mailx (1) mountd
(8)
(1)
(1) hostname ifconfig
(8)
(8)
(8)
(8)
(8)
(1)
(8)
(1)
Added -n and -v options in UNICOS/mp.
-n causes mapping of IP addresses to host names to be suppressed.
-v is the typical “verbose” option.
Added -p (priority) option in UNICOS/mp. See also autofs
No known differences.
Completely different options.
Added -l , -L , -S , and -f options in
UNICOS/mp.
No known differences.
UNICOS/mp version does not support -h , -k ,
-v , -r , -s , -Sc , or -Sd options.
UNICOS/mp version does not support -c , -s ,
-Sc , or -Sd options.
No known differences.
No known differences.
Added -v (verbose) and -a (all interfaces) options in UNICOS/mp.
Added -l (queue length) and -s (parse configuration file) options in UNICOS/mp.
UNICOS/mp version does not support -t
(timeout) option.
No known differences.
UNICOS/mp version does not support -t
(persons) option; added -h (display header only) option.
UNICOS/mp version does not support -h , -r , and -F options in Send mode; and does not support the -d , -T , -U , and -V options in Receive mode. UNICOS/mp version adds support for the
-v (verbose) option in Send mode.
Added -l and -r options in UNICOS/mp.
S–2348–24 41
Cray X1™ System Administration Differences named (8) netstat (1) nettest (8) nfsstat (8) nslookup (1) ntp.conf
(5) ntpd (8) ntpdc (8) pac (8) ping (8) portmap (8) rcp (1) rdist (1) rexecd (8) rlogin (1) rlogind (8) rmt (8) route (8) rpc.ypupdated
(8) rpcgen (1) rpcbind (8) rpcinfo (8) rsh (1) rstatd (8) rusers (1) rusersd (8)
42
(Deferred implementation) The UNICOS/mp version does not support -S or -St options.
Major differences in options.
No known differences.
UNICOS/mp version does not support -t , -m , -x , or -a options.
No known differences.
Network Time Protocol configuration file.
Network Time Protocol (NTP) daemon.
Special NTP query program.
No known differences.
Many added options.
Completely different set of options.
UNICOS/mp version does not support -b , -c ,
-s , -S , or -T options.
Completely different set of options.
Completely different set of options.
UNICOS/mp version does not support -d , -E , or -S options.
Completely different set of options.
No known differences.
UNICOS/mp version does not support -d or -t options. Added -F (flush) option in UNICOS/mp.
(Deferred implementation) Daemon that updates information in the network information service
(NIS) (Linked to ypupdated ).
(Deferred implementation) No known differences.
Completely different set of options.
Added -m , -b , -d , and -C options in
UNICOS/mp.
Many differences in options.
No known differences.
Added -n (maximum number) option.
No known differences.
S–2348–24
S–2348–24 rwall (1) rwalld (8) sendmail (8) shutdown (8) spray (8) sprayd (8) statd (8) telnet (1) telnetd (8) tftp (1) tftpd (8) traceroute (8) uuencode (8) ypcat (1) ypinit (8) ypmatch (1) yppasswd (1) yppoll (8) yppush (8) ypserv (8) ypset (1) ypwhich (1) ypxfr (8) ypbind (8)
Networking [6]
No known differences.
No known differences.
sendmail version 8.12 is now supported.
Major differences in function.
No known differences.
No known differences.
Associated files are located in /var/statmon , not
/usr/spool .
No known differences.
No known differences.
UNICOS/mp version does not support -S option.
Completely different set of options.
UNICOS/mp version does not support -d , -f , or -S options. Added -g , -l , -M , -r , and -t options in UNICOS/mp.
No known differences.
No known differences.
UNICOS/mp version added the -c , -d , and
-y options.
No known differences.
No known differences.
(Deferred implementation) Shows the version of the NIS map on the NIS server.
(Deferred implementation) Forces propagation of a changed NIS map.
(Deferred implementation) The YP server provides a simple network lookup service consisting of databases and processes.
No known differences.
No known differences.
(Deferred implementation) Moves a network information service (NIS) map to the local host.
Network Information Services (NIS) binder process.
43
Cray X1™ System Administration Differences
6.6.2 Commands and Daemons Unique to UNICOS/mp
The following commands are in UNICOS/mp but are not in UNICOS or
UNICOS/mk. The commands are documented on their respective man pages: autofs (8) Installs automatic file system mount points. This is similar to automount but is the default and preferred command.
autofsd cfsstat lptest
Mail (1) ordist rdistd
(8) cfsadmin rpc.rexd
(8)
(8)
(1) network (8) ntpdate (8) ntpq (8) ntptrace (8) rpc.lockd
rpc.passwd
rup (1)
(1)
(8) ruptime rwho (1) rwhod snoop timed
(8)
(8)
(8)
(8)
(1) showmount
(8)
(8)
(8)
Note: autofs and automount cannot be used on the same system simultaneously.
AutoFS mount/unmount daemon.
Administers disk space used for CacheFS.
Displays CacheFS statistics.
Generates a line printer ripple pattern.
Sends and receives mail.
Starts or stops the network.
Sets the date and time via NTP.
Standard NTP query program.
Traces a chain of NTP servers back to the primary source.
Distributes and maintains identical copies of files over multiple hosts.
rdist daemon.
RPC-based remote execution server ( rpc daemon).
Provides locking services within the NFS environment.
(Deferred implementation) Server for modifying
NIS password file.
Shows the host the status of local machines ( rpc version).
Shows the host the status of local machines.
Similar to who , but for all machines on the LAN.
rwho daemon.
Shows all remote NFS mounts.
Captures and inspects network packets.
Time server daemon.
44 S–2348–24
Networking [6] timedc timeslave timetrim ttcp (1)
(8)
(8) ypchpass (1) ypmake (8)
(8) timed control program.
Matches (slaves) the clock in a local machine to a better clock.
Displays, sets, or adjusts clock frequency trim parameter.
tcp and udp test program.
Change selected NIS password fields.
(Deferred implementation) Rebuilds and distributes NIS databases.
6.6.3 UNICOS and UNICOS/mk Commands and Daemons Not Supported in UNICOS/mp
The following UNICOS and/or UNICOS/mk networking administration daemons and commands are not supported in UNICOS/mp: gated (8) mrouted routed
(8)
(8)
Gateway routing daemon. This function is handled by the Cray Network Subsystem (CNS).
IP multicast routing daemon. UNICOS/mp does not support multicast routing.
Network Routing Information Protocol (RIP) and router discovery daemon. This function is handled by the Cray Network Subsystem (CNS).
S–2348–24 45
Cray X1™ System Administration Differences
46 S–2348–24
Security [7]
This chapter describes the UNICOS/mp security features available to users making a transition from UNICOS and UNICOS/mk systems. The security features associated with this transition fall into the following categories:
• Extensions to traditional UNIX security that are provided with UNICOS/mp
• Extensions to traditional UNIX security that are not provided with
UNICOS/mp
• Multilevel security that is not provided with UNICOS/mp
• Open SSH and Open SSL, which are available with Cray Open Software
• Kerberos authentication that is not provided with UNICOS/mp
7.1 Extensions to Traditional UNIX Security Provided with UNICOS/mp
The extensions to traditional UNIX security that are available on UNICOS/mp and that augment the traditional security features offered by the UNIX operating system include:
• Encrypted password protection
• Access control lists (ACLs)
• Granular privilege mechanism
For detailed information, see UNICOS/mp System Administration.
7.1.1 Encrypted Password Protection
By default, the UNICOS/mp system stores user passwords in /etc/passwd , which is globally readable. However, UNICOS/mp systems can be configured to store encrypted passwords only in a protected /etc/shadow file. This shadow password file is readable only to an administrator, making it more difficult for an attacker to guess passwords.
7.1.2 Access Control Lists (ACLs)
On a traditional UNIX system, discretionary access to a named object is controlled by the object’s permission bits. UNICOS, UNICOS/mk, and
S–2348–24 47
Cray X1™ System Administration Differences
UNICOS/mp provide an extension to this permission mode called access control lists (ACLs). ACLs allow the owner of a file to control access to the file at the granularity of a single user.
7.1.3 Granular Privilege Mechanism
The granular privilege mechanism divides the power of the superuser into discrete units of privilege called capabilities. Capabilities are similar to the privileges used by the privilege assignment list (PAL) mechanism in UNICOS and UNICOS/mk systems. The granular privilege mechanism makes it possible for applications to use privilege more precisely than possible when using superuser privilege.
The UNICOS/mp capabilities feature provides a granular privilege mechanism similar to UNICOS and UNICOS/mk PRIV_SU plus PALs, except that it does not use PALs. The UNICOS/mp capability mechanism provides fine grained control over the privileges of a process. As a process attribute, a capability allows the process to perform a specific set of restricted operations, without granting general override of the system’s protection scheme. A process can possess multiple capabilities. Collectively, all defined capabilities comprise the set of abilities that are traditionally associated with the root user.
Administration of a UNICOS/mp system capabilities environment relies on inheritance of capabilities acquired by a user at login. The superuser or root account must be given a nonempty capability set when logging in, and must have the ability to acquire all capabilities needed when necessary. Capabilities are assigned to users by a file, /etc/capability , that is processed at login time.
The file /etc/capability describes the default capability set and the maximum capability set a user may have when logging onto the system or using the su (8) command. The file contains one entry for each user.
7.2 Extensions to Traditional UNIX Security That Are Not Provided with UNICOS/mp
The extensions to traditional UNIX security that are not available on
UNICOS/mp include:
• Audit mechanism
• Configurable authentication
48 S–2348–24
Security [7]
7.2.1 Audit Mechanism
The audit mechanism on UNICOS and UNICOS/mk systems allows the auditor to monitor events based on a concrete set of tokens written to the audit trail.
Audit records can be displayed in a human-readable form, or a single-line form, which is suitable for machine parsing.
UNICOS/mp does not support this audit mechanism capability.
7.2.2 Configurable Authentication
UNICOS and UNICOS/mk provide facilities for configuring the behavior of authentication mechanisms like login. This is achieved through the use of user exits, which are points in the code at which calls to externally supplied functions can occur.
UNICOS/mp does not support this configurable authentication capability.
7.3 Multilevel Security (MLS)
UNICOS and UNICOS/mk systems support a multilevel security environment.
There is no support in UNICOS/mp systems for a multilevel security environment.
7.4 OpenSSH and OpenSSL
The optional and separately licensed Cray Open Software (COS) product provides the following security packages:
• OpenSSH is the overall communications protocol, which implements both
SSH-1 and SSH-2 protocols.
• The Secure Socket Layer (SSL) protocol is an authentication and encryption technique that provides security services to TCP clients.
For more information about all software packages included in the COS product, see Cray Open Software Release Overview and Installation Guide.
S–2348–24 49
Cray X1™ System Administration Differences
7.5 Kerberos Authentication
Kerberos is a set of programs and libraries that provides distributed authentication over an open network and is available for UNICOS and
UNICOS/mk operating systems as optional, separately licensed software.
Cray does not provide or support Kerberos for UNICOS/mp systems.
50 S–2348–24
Resource Administration [8]
This chapter contains information about how system administration of UNICOS,
UNICOS/mk, and UNICOS/mp are different in the following features:
• Placement scheduling
• Application monitoring
• Limits
• Accounting
• System monitoring and reporting
• Checkpoint and restart
8.1 Placement Scheduling
Although Cray has ported the political scheduler ( psched daemon) from
UNICOS/mk to UNICOS/mp, enough differences exist that you should read about placement scheduling in UNICOS/mp System Administration. For example, the functionality of the Global Resource Manager (GRM) on UNICOS/mk has become part of the functionality of psched in UNICOS/mp.
The psched daemon manages the placement of applications on application nodes. It enforces the requirements of the hardware and operating system; manages the use of global address space IDs (GASIDs), processors, and memory on the nodes; and implements the oversubscription policy established by the administrator.
8.2 Application Monitoring
The UNICOS/mk grmview (1) command has been replaced by the apstat (1) and snflv (8) commands in UNICOS/mp. These commands provide information about running applications and configuring application nodes.
UNICOS/mp also provides the apkill (1) command to send a signal to all processes that are part of an application.
S–2348–24 51
Cray X1™ System Administration Differences
8.3 Limits
UNICOS and UNICOS/mk job limits are not supported in UNICOS/mp.
Specifying user limits has been simplified for UNICOS/mp. The maintenance tool for UNICOS/mp is the limit_mkdb command rather than the udbgen command used for UNICOS and UNICOS/mk. The user database (UDB) is not supported in UNICOS/mp; portions of its functionality are implemented by the limit database and the accounting database (see the userlimit (1) and limit_mkdb (8) man pages for details).
Limits are defined in two dimensions: service provider type (batch or interactive) and placement class (command or application). Both maximum and initial values may be specified for each limit.
8.4 Creating /etc/passwd and /etc/group Files
Because the UDB is not supported on UNICOS/mp, the following procedure can be performed to extract the UNICOS or UNICOS/mk UDB information and place it into the UNICOS/mp /etc/passwd file. It is assumed that the home directory names will be the same on UNICOS/mp as they were on UNICOS or
UNICOS/mk. You must have root permission to perform this procedure.
1. Execute the following command on UNICOS or UNICOS/mk: udbsee -f name,passwd,uid,gids,comment,dir,shell \
-m "%s:%s:%d:%s:%s:%s:%s\n" -q -a > tmpfile
2. Manually remove “system” user IDs from the remaining tmpfile entries
(users with uids less than 100) and append that tmpfile to the UNICOS/mp
password file that was installed with the system. See Section 8.4.1, page 53
for Cray policy on user and group IDs.
52 S–2348–24
Resource Administration [8]
3. If you want to run with shadow passwords, execute the following command on UNICOS/mp at this time: pwconv
The UNICOS/mp /etc/passwd file should now contain the UDB user entries from your UNICOS or UNICOS/mk system.
To create the group file, append the contents of the UNICOS or UNICOS/mk group file (with gids less than 100 already removed) to the UNICOS/mp group file that was installed with the system.
8.4.1 Cray Policy for User IDs and Group IDs
The Cray policy for user IDs and Group IDs used with UNICOS, UNICOS/mk,
UNICOS/mp, SWS, CWS, CPES, and open source software is as follows:
• Cray reserves any Cray account user ID (uid) and Cray group ID (gid) between 1 and 99, between 14900 and 14999, and the IDs 12655, 12795 and
29833.
• Cray uses the following approach to guide creation or usage of new user IDs and group IDs, in order of preference:
1. Use the standard or generally accepted values for the account if coming from the open source community.
2. Use the same user IDs and group IDs that are being used by other operating systems, such as the FreeBSD or Linux systems.
3. Use historical practices, such as using old historical values when possible.
8.5 Accounting
S–2348–24
UNICOS, UNICOS/mk, and UNICOS/mp provide standard UNIX System V
Release 4 (SVR4) accounting evaluation tools such as acctcom , acctcms , and acctmerg . In UNICOS/mp, these tools enable the collection of application-wide data. In addition, UNICOS/mp supports the capabilities to display account
IDs and consolidate by account ID.
Cray System Accounting (CSA) is not supported in UNICOS/mp.
In UNICOS/mp, ApTeam information is collected on a per-application basis for the following items; this information, when combined with the information
53
Cray X1™ System Administration Differences collected per process, presents the same level of accounting information as reported in UNICOS/mk:
• Application flags (such as MSP , SSP , FLX , ACS application ID )
• User ID and start time (when the user presses the Enter key)
• Launch time (when the application was started by psched )
• Elapsed time
• Connect time (different from elapsed time if gang scheduled)
• Application name
• Application width and depth
You can use the UNICOS/mp acctcom command to view the ApTeam accounting report. Specify the -A option to print summary information in the separate accounting record created for a completed parallel application. This command is not used by any other accounting evaluation tool. See the acctcom man page for details.
8.6 System Monitoring and Reporting
System activity data is accessed on UNICOS/mp by using the sar (1) and timex (1) utilities as it is on UNICOS and UNICOS/mk. However, on
UNICOS/mp, changes have been made to the subsets of the data being reported.
See the sar man page for details.
8.7 Checkpoint/Restart
UNICOS/mp provides a checkpoint/restart (CPR) facility, described in the cpr (1) man page, enabling a program, a user command, or operator to initiate a checkpoint. Functionality of the cpr command is similar to that of the chkpnt command used in UNICOS and UNICOS/mk.
The UNICOS and UNICOS/mk checkpoint/restart is used primarily within the functionality of supported in NQS (Network Queuing System) for starting and stopping batch jobs. PBS Pro is the optional batch processing software that can
be used with UNICOS/mp. (See Chapter 10, page 61, for information about
checkpointing and restarting jobs with NQS or PBS Pro batch systems.)
54 S–2348–24
Resource Administration [8]
8.7.1 Checkpointing Jobs on CPES
User access to the Programming Environment on the Cray Programming
Environment Server (CPES) involves the use of sockets between the Cray X1 system and the CPES. This means that jobs with active compiles are not checkpointable because processes with open sockets cannot be checkpointed.
8.7.2 Checkpoint Commands
The cpr command provides both checkpoint and restart capabilities in
UNICOS/mp. In UNICOS and UNICOS/mk, this capability is provided by both the chkpnt and restart commands. In addition, the following UNICOS/mp library routines are available:
• atcheckpoint , atrestart – Adds checkpoint and restart (CPR) event handlers
• ckpt_create , ckpt_remove , ckpt_restart , ckpt_setup , ckpt_stat –
Checkpoint and restart (CPR) library interfaces
8.7.3 Objects Not Checkpoint-safe
Due to the nature of checkpoint and restart, it is impossible to claim that everything a process owns or connects with can be restored. In UNICOS/mp, the following system objects are not checkpoint-safe:
• Network socket connections; see the socket man page
• X terminals and X11 client sessions
• Special devices
• Files opened with a setuid credential that cannot be reestablished
• UNIX System V semaphores and messages; see the semop and msgop man pages
• Memory-mapped files using the /dev/mmem file; see the mmap man page
• Open directories
S–2348–24 55
Cray X1™ System Administration Differences
56 S–2348–24
System Dump Analysis [9]
In UNICOS/mp, the crashmp (8) utility allows you to analyze mainframe system dumps generated by the dumpmf (8) utility. The crashmp utility includes
UNICOS/mk crashmk capabilities, but there are significant differences between the two utilities. The dumpmf command is based on the UNICOS/mk dumpmf command.
9.1
crashmp Utility
The UNICOS/mp utility crashmp includes significant changes from
UNICOS/mk crashmk utility:
• In crashmk , kernel structure definitions and defines ( #define ) are included from kernel header files at compile time. In crashmp , kernel structure definitions are read from ELF and DWARF data in the kernel image file
(namelist) at run time.
• Unlike crashmk , crashmp has no order restriction on command line arguments.
• With crashmk , printf output can be directed to stdout or a file. With crashmp , printf output can be directed to both stdout and stderr , as well as a file.
• crashmk provides one dump file per processing element, which contains all relevant kernel memory.
crashmp provides one dump file per node and kernel data is found only in the master node dump.
• Command line options for crashmk and crashmp are completely different.
See the crashmp (8) man page for details.
• Directive help (the -h , -H , and -l options) for crashmp includes detailed descriptions of directive options and arguments, as follows:
– To view detailed command line option and argument information, enter: crashmp -h
– To display descriptions of all crashmp directives and aliases, enter: crashmp -H
S–2348–24 57
Cray X1™ System Administration Differences
– To display detailed descriptions of all crashmp directives and aliases, enter: crashmp -l all
– To view specific information about any directive, use the -l option with that directive: crashmp -l dir
When you execute crashmp with the -h , -H , and/or -l options, you need not specify a system image file or a symbol information file, and you can combine the options.
For more information on system crash analysis, see UNICOS/mp System
Administration and the crashmp (8) man page.
9.2
dumpmf Utility
Specific options for the dumpmf utility include the following changes from the
UNICOS/mk version:
• The -p option specifies an application node number on the UNICOS/mp system, instead of a processing element number.
• The following input directives have been removed:
– FORMAT
– PE
– READ_OFFSET
– RECOMMENDED_SEGMENTS
– SECTOR_SIZE
– WRITE_OFFSET
58 S–2348–24
S–2348–24
System Dump Analysis [9]
• The following input directives have been added:
– NODENAME
– PFDATS_READ
• Options that include configuration file information have been updated to support UNICOS/mp systems.
For more specific information about system dump analysis, see UNICOS/mp
System Administration and the dumpmf (8) man page.
59
Cray X1™ System Administration Differences
60 S–2348–24
Batch System [10]
The Network Queuing Environment (NQE) product is not supported on
UNICOS/mp systems. Cray has chosen to partner with a third-party batch system vendor to provide this functionality.
PBS Pro is the batch system offered through Cray for UNICOS/mp systems. PBS
Pro is the professionally supported edition of the Portable Batch System (PBS) originally designed for NASA. PBS Pro permits system administrators to initiate and manage the workload of their users’ computational jobs in accordance with site scheduling policies.
Through a vendor agreement, Cray sells, licenses, and supports PBS Pro directly on all Cray systems. Documentation about using PBS Pro software is provided with the PBS Pro release package in the form of PDF files and man pages along with the PBS Pro Release Overview, Installation Guide, and Administration Addendum
for Cray Systems.
10.1 Key Features Comparison
Table 7 compares key features of PBS Pro and NQE.
Feature Description
Table 7. PBS Pro and NQE Key Feature Comparison
PBS Pro
Yes Installation : Cray’s Common Installation Tool (CIT) is used to install the product.
User Interface : System status available.
User Interface : Job submission available.
Job Priority : Users may specify job priority at submission.
Job Priority : Defaults may be assigned at the queue level.
Job Priority : Defaults may be assigned at the system level.
Job Interdependency : Jobs may be scheduled based on the status of other jobs. Such dependencies include execution order, synchronization, and conditional execution based on success or failure of a specified job.
Yes
Yes
Yes
Yes
Yes
Yes
NQE
Yes
Yes
Yes
Yes
Yes
Yes
No
S–2348–24 61
Cray X1™ System Administration Differences
Feature Description
Checkpoint/Restart : Supports Cray checkpoint and restart capabilities.
Automatic File Staging : Provides users with the ability to specify any files that need to be copied onto the execution host before the job runs and any that need to be copied off after the job completes. The job will be scheduled to run only after the required files have been successfully transferred.
Common User Environment : Offers users a common view of job submission, job querying, system status, and job tracking over all systems.
Cross-system Scheduling : Provides transparent job scheduling on any system by any authorized user. Jobs can be submitted from any client system or any compute server.
Security and Access Control Lists : Configuration options permit the administrator to allow or deny access on a per-system, per-group, and/or per-user basis.
Job Accounting : For chargeback or usage analysis, system maintains detailed logs of system activity. Custom charges can be tracked on a per-user, per-group, and/or per-system basis.
Comprehensive API : Includes a complete and documented
Application Programming Interface (API) for sites who wish to integrate their applications or that have unique job scheduling requirements.
Automatic Load Leveling : Provides numerous ways to distribute the workload across a cluster of machines, based on hardware configuration, resource availability, and keyboard activity.
Enterprise-wide Resource Sharing : Does not require that jobs be targeted to a specific computer system. This allows users to submit their job and have it run on the first available system that meets their resource requirements. This also prevents waiting on a busy system when other computers are idle.
User Name Mapping : Provides support for mapping user account names on one system to the appropriate name on remote server systems. This allows the batch system to fully function in environments where users do not have a consistent user name across all the resources to which they have access.
PBS Pro
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
62
NQE
Yes
No
No
Yes
Yes
Yes
Yes, at NQS queue level
Yes
No
No
S–2348–24
Batch System [10]
Feature Description
Parallel Job Support : Supports parallel programming libraries such as MPI. Such applications can be scheduled to run within a single multiprocessor system or across multiple systems.
Highly Configurable : May be easily tailored to meet the needs of individual sites. The scheduler component is highly configurable.
Broad Platform Availability : Provided on a wide range of
UNIX workstations, servers, and supercomputers.
Computational Grid Support : Provides integrated support for an enabling technology involving metacomputing and computational grids, including support for the Globus Toolkit.
PBS Pro
Yes
Yes
Yes
Yes
Planned for Cray systems
Yes Advance Reservations : Provides the ability to reserve computational resources in advance.
Distributed Clustering : Allows for utilization of physically distributed systems and clusters, including wide-area networks.
Resource Usage Control : Addressed with advanced scheduling features (in PBS Pro) or queue complexes (in NQS/NQE).
Reliable File Transfer : Provides facilities to support reliable file transfer.
Yes
Yes
No
NQE
Yes, on single multiprocessor system
Yes
Yes
No
No
No
Yes
Yes
For detailed information about the content of a PBS Pro release package, available training, and required licensing, see PBS Pro Release Overview, Installation Guide,
and Administration Addendum for Cray Systems.
For more information about the PBS Pro product, visit the web site at http://www.pbspro.com/overview.html
.
10.2 Migrating NQS/NQE Scripts to PBS Pro
To help you migrate from NQE to PBS Pro, PBS Pro provides the nqs2pbs utility that converts your existing Network Queueing System (NQS) job scripts to work with PBS Pro. The resulting script is valid for both NQS/NQE and PBS Pro. The existing script is copied and PBS Pro directives ( #PBS ) are inserted before each
NQS directive (either #QSUB or #Q$ ) in the original script.
If you use the nqs2pbs utility, you must carefully inspect the resulting job scripts prior to submission to PBS Pro; pay special attention to NQS directives
S–2348–24 63
Cray X1™ System Administration Differences
!
that do not appear to have a PBS Pro equivalent. The script is intended to aid in the process of converting #NQS directives to #PBS directives, although this is not possible in all cases.
Caution: Converting NQS date specifications to the PBS Pro form may result in a warning message and an incomplete converted date. PBS Pro does not support date specifications of "today", "tomorrow", or the name of the days of the week such as "Monday". If any of these are encountered in a script, the PBS Pro specification will contain only the time portion of the
NQS specification (that is, #PBS -a hhmm [.ss] ). It is suggested that you specify the execution time on the qsub command line rather than in the script.
All times are taken as local time. If any unrecognizable NQS directives are encountered, an error message is displayed. If any errors occur, the new PBS
Pro script will be deleted.
The nqs2pbs utility is documented in the PBS Pro User Guide and on the nqs2pbs (1) PBS Pro man page, which are included with the PBS Pro product from Cray.
10.3
ENVIRONMENT Variable
For NQS compatibility, the variable ENVIRONMENT is provided, set to the same value as PBS_ENVIRONMENT . For descriptions of PBS Pro environment variables, see the PBS Pro User Guide included with the PBS Pro product from Cray.
10.4 Additional Information for System Administrators
Because migration information for system administrators may change based on changes made to the PBS Pro software, this Cray X1 System Administration
Differences does not include system administration information about migrating from NQE/NQS to PBS Pro. Please read the PBS Pro Release Overview, Installation
Guide, and Administration Addendum for Cray Systems for additional migration information.
64 S–2348–24
Administrator Commands [11]
The UNICOS/mp system provides a subset of the traditional UNIX command set. This chapter lists the differences between the UNICOS and UNICOS/mk administrator command sets and the UNICOS/mp administrator command set.
In addition to the command information listed here, see Section 6.6, page 40 for
detailed information about networking commands.
Command apmigrate aprecovery attrinit autofs autofsd bfc cfsadmin cfsstat chkconfig chkutent chrtbl closewtmp colltbl
11.1 Administrator Commands Unique to UNICOS/mp
Table 8 lists administrator commands that are included in UNICOS/mp systems
but not in UNICOS or UNICOS/mk systems.
Table 8. Administrator Commands Unique to UNICOS/mp
Description
Manual application migration command
Unlocks apteams and triggers psched application recovery
Sets extended file attributes
Installs automatic mount points
AutoFS mount/unmount daemon
Manages bonded Fibre Channel interfaces
Administers disk space used for caching file systems with the Cache file system
Displays network file system (NFS) statistics
Prints the state of every configuration flag
Checks and repairs utmp entries
Generates character classification and conversion tables
Puts a false DEAD_PROCESS record in the
/var/adm/wtmp file
Creates collation database
S–2348–24 65
Cray X1™ System Administration Differences
Command crashmp dvhtool edquota foconfig fsr fsr_xfs fstyp fx grpck halt hinv ioca ioconfig iotrace limit_mkdb lsi_mkfs
MAKEDEV makemdbm mdbm_remove mkalias mkfs_xfs
(Deferred implementation) mkpts
66
Description
Provides system kernel analysis utility (replaces the
UNICOS crash and UNICOS/mk crashmk commands)
Modifies and obtains disk volume header information for dksc devices
Note: Support for this command will not be included after this release.
Edits user quotas
Processes the failover.conf
configuration file
Provides file system reorganizer
Provides file system reorganizer for XFS
Determines file system identifier
Provides a disk utility for dksc devices
Note: Support for this command will not be included after this release.
Verifies all entries in the group file
Halts the system
Displays the system hardware inventory table
Debugs Cray X1 system I/O channel adapter (IOCA) devices
Configures I/O devices
Prints and controls kernel I/O traces
Creates the user limits database
Invokes mkfs with stripe width of LSI RAID device
Creates specified device special files
Makes an NIS mdbm file
Invalidates and removes mdbm files
NIS mail alias tool
Constructs an XFS file system
Finds and allocates a pair of devices making a pseudo-TTY
S–2348–24
Command mntproc montbl mountall mpadmin network olfp olio olmc olnwt olrit olvmm parts passmgmt pcix pm proj_mkdb prtvtoc pwconv quot quotaoff quotaon rc0
S–2348–24
Administrator Commands [11]
Description
Mounts the /proc file system
Creates monetary database
Mounts multiple file systems
Lets administrators disable an SSP
Initializes or shuts down the standard and optional network devices and daemons
Tests UNICOS/mp floating point units
Tests user code access to drive space
Provides online memory confidence test
Tests processor to processor (SSP or MSP) communication through the use of shared memory
Verifies the proper operation and functionality of the
Cray X1 processor
Tests functionality of vector mask operations, and the bit matrix multiply (BMM) functional unit
Reads and writes disk partition information
Manages password files
Debugs and controls the Cray X1 system PCI-X controllers
Provides path managed disk driver monitor and control
Rebuilds the binary project account databases
Prints disk volume header information for dksc devices
Note: Support for this command will not be included after this release.
Installs and updates /etc/shadow with information from
/etc/passwd
Summarizes file system ownership
Turns file system quotas off
Turns file system quotas on
Runs commands required to enter single-user mode or halt the system
67
Cray X1™ System Administration Differences sulogin swap systune talkd timed timedc timeslave umountfs utmp2wtmp vnt
Command rc2 rdistd repquota rpc.rquotad
rwhod runon scsicontrol scsifo scsiha scsiquiesce setmnt snflv snoop sspnames suattr
68
Description
Runs commands required for multiuser environment
Provides remote file distribution server
Summarizes quotas for a local file system
Provides remote quota server
Creates system status databases used by rwho and ruptime
Runs a command on a particular processor
Probes and controls SCSI devices
Shows failover status or initiates failover status on a device
Probes and controls SCSI buses
Stops all SCSI bus activity for a specific amount of time
Establishes mount table
Sets node flavor of UNICOS/mp nodes
Captures and inspects network packets
Provides SSP or node IDs
Executes shell command with specified capabilities at specified MAC label
Accesses single-user mode
Swaps administrative interface
Displays and sets tunable parameters
Notifies a user that somebody else wants to initiate a conversation
Synchronizes the host’s time with the time of other machines in a local area network
Controls the operation of the timed program
Matches (slaves) the local clock to a better one
Unmounts a file system
Creates an entry in the file /var/adm/wtmp
Exercises the Fibre Channel driver and interface hardware on a Cray X1 system
S–2348–24
Administrator Commands [11]
Command x1memtest xfs_check xfs_copy xfs_db xfs_growfs xfs_logprint xfs_repair xfsdump xfsrestore xfsinvutil xlv_assemble xlv_labd xlv_make xlv_mgr xlv_plexd xlv_set_primary xlv_shutdown xlvd
Description
Provides Cray X1 system memory confidence test
Checks XFS file system consistency
Copies the contents of an XFS file system
Debugs an XFS file system
Expands an XFS file system
Prints the log of an XFS file system
Repairs an XFS file system
Backs up files and their attributes in an XFS file system
Restores XFS file systems from dumps produced by xfsdump
Checks the xfsdump inventory database for consistency
Initializes logical volume objects from disk labels
Writes logical volume disk labels
Creates logical volume objects
Administers XLV logical volume objects and their disk labels
Makes all plexes within a subvolume consistent
Sets the primary plex of a logical volume
Shuts down XLV volumes
Handles I/O to plexes and performs plex error recovery
11.2 Administrator Commands Not Included for UNICOS/mp
Table 9 lists administrator commands that exist in UNICOS or UNICOS/mk
systems, but not in UNICOS/mp systems. The column headed "Operating
System" lists the operating system on which the command is supported:
UNICOS, UNICOS/mk, or both.
S–2348–24 69
Cray X1™ System Administration Differences
Command airckconf aird airdchk airdet airexist airping airprconf airrep airsum airtsum aremex arrayd atmadmin atmarp bb bds bmap
70
Table 9. Administrator Commands Not Included for UNICOS/mp
Description
Prints and validates an automated incident reporting (AIR) configuration file
Provides automated incident reporting
(AIR)
Ensures that the AIR daemon ( aird (8)) is running ( cron (8) script)
Generates detailed AIR reports based on aird (8) binary log file
Searches the process table in kernel memory for a process matching the command-line requirements
Measures round-trip delays and packet loss across network paths, using the specified protocol
Prints AIR configuration file contents from configuration headers in the aird (8) binary log file
Produces AIR activity reports
Generates availability summary reports based on aird (8) binary log file
Generates detailed AIR reports based on aird (8) binary log file
Operating System
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
Array Services remote execution monitor UNICOS
Array services daemon UNICOS
UNICOS Configures and displays ATM administration statistics
Configures and displays an ATM ARP table
Both
Both Creates relative bad block file from ASCII flaw table files
Bulk data server
Identifies a block on a given file system
Both
Both
S–2348–24
Administrator Commands [11]
Command cfsync cfupdate chmem ckdacct ckptdump
Description
Propagates files to the mainframes in a cluster
Unpacks a cpio archive created by cfsync (8)
Displays and changes the system’s notion of physical memory size
Checks the size of daemon accounting files
Verifies restart files ckptutil cleantmp cll cm configtool coredd cpdmp cpkern cpset cpu
Verifies restart files
Deletes job temporary directories
Lists or resets the login failure attempts field in user database (UDB)
Moves a spindle in a disk configuration
Invokes the ConfigTool program, which is used to edit subsystem configuration files
Automatically copies sparse-format dump files to a compact-format dump file in a separate file system
Copies GigaRing common dumps from a raw device or from a dump file to a standard file system
Copies a Cray kernel binary file from a raw disk device to a standard
UNICOS/mk file
Installs object files in binary directories
Selects, dedicates, and changes mode bits per CPUs
Examines system core images crash (Replaced by crashmp ) crashmk (Replaced by crashmp ) Examines UNICOS/mk system images csa Overview of Cray system accounting csaaddc Adds cacct records
Operating System
UNICOS
UNICOS
UNICOS
Both
UNICOS/mk
UNICOS
Both
Both
Both
UNICOS/mk
Both
Both
UNICOS/mk
Both
UNICOS
UNICOS
UNICOS/mk
Both
Both
S–2348–24 71
Command csaboots csabuild csacon csaconvert csacrep csadrep csaedit csafef csafef2 csagcon csagfef csaibm csajrep csaline csam csanqs csapacct csaperiod csaperm csarecy
72
Cray X1™ System Administration Differences
Description
Records system boot times for the accounting subsystem
Generates a session record file
Operating System
Both
Condenses a session record file into a cacct file
Converts a previous level of UNICOS or
UNICOS/mk accounting files to a current
UNICOS or UNICOS/mk level format
Both
Both
Both
Reports on consolidated accounting data Both
Reports daemon usage
Displays, verifies, and deletes records from various accounting files
Both
Both
Formats data for front-end accounting system
Produces summarized session records
Prints a job report from the session record file
Preprocesses connect-time sessions
UNICOS
Consolidates accounting data for session and pacct files
UNICOS
Both
Formats consolidated accounting data Both
Converts session records into IBM format UNICOS
Both
Both
Both Displays system activity data on a dumb terminal
Preprocesses the NQS accounting files Both
Both Verifies and deletes records from a pacct file
Runs periodic accounting Both
Both Changes group ID and permissions of accounting files
Recycles unfinished sessions into next accounting run
Both
S–2348–24
Command csarun csasocket csaswitch csaverify csload csp cs_start csv cvtmldir ddoffload ddms ddstat ded devacct dgdemon dgstop diagccmt dig dmap
S–2348–24
Administrator Commands [11]
Description
Processes the daily accounting files and generates reports
Processes socket accounting data
Operating System
Both
Checks the status of and enables or disables process, daemon, and record accounting
UNICOS
Both
Checks accounting records for valid data Both
Loads configuration information into configuration server proxy
UNICOS/mk
Starts the configuration server proxy
Creates, validates, and loads configuration file
UNICOS/mk
UNICOS/mk
Verifies a UNICOS/mk configuration file UNICOS/mk
Converts between wildcard and multilevel directory (MLD) structures
Both
UNICOS Provides offloading of a single spindle of a DD-4x disk drive for Cray PVP systems
Provides online disk maintenance capabilities
Both
Both Displays configuration information about disk type character and block special devices
Runs a program in dedicated mode
Controls device and performance accounting
UNICOS
UNICOS
Invokes the diagnostic daemon
Terminates the diagnostic daemon
Online I/O diagnostic client
Sends domain name query packets to name servers
Maps physical and logical devices
UNICOS
UNICOS
Both
Both
Both
73
fddidump fddiload fddimap fddistat ff fping fmtcs fsck fsdaemon
74
Command dnsquery dump ebmchk econfig errdemon errpt errstop esdmon fconfig
Cray X1™ System Administration Differences
Description
Queries domain name servers by using resolver library calls
Operating System
Both
Invokes an incremental file system dump Both
Scans an a.out
instructions file looking for EBM UNICOS
UNICOS Verifies boot-time CSL directives for IOS model E systems and generates mknod commands for specified configuration
Invokes the error-logging daemon Both
Processes errors report generated by the error-logging daemon errdemon (8)
Both
Terminates the error-logging daemon errdemon (8)
Interactively monitors the logical-layer
External Semaphore Device
Verifies boot-time configuration server directives for Cray T3E systems, generates mknod (8) commands, and creates nodes for the specified disk configuration
Utility to dump FDDI (FCA-1) shared memory
Utility to load FDDI (FCA-1) microcode
Utility to gather FDDI station management information
Displays information about IOS model E
FDDI devices
Both
Both
UNICOS/mk
UNICOS
UNICOS
UNICOS
UNICOS
Lists file names and statistics for a file system
Both
Sends an echo packet to a GigaRing node UNICOS
Converts configuration file format UNICOS/mk
Checks file system consistency and interactively repairs it
File system monitor daemon
Both
Both
S–2348–24
Command fsed fslogd fsmap fsmon fsmpptest fsoffload fstest gated gdc getconfig getpal getprivs gettable grctl grmgr hddmon hit hpi3_clear hpi3_config hpi3_option
S–2348–24
Administrator Commands [11]
Description
Debugs NC1FS file systems
File system error logging daemon
Displays file system free-blocks
Interfaces with the file system monitor fsdaemon (8)
Operating System
Both
UNICOS
Both
Both
MPP multi-PE application file system and disk device test including performance measurement and data comparison
Lists files and directories on a logical device
Tests file systems and disk devices
Performs routing protocols
Operational user interface for gated (8)
Searches the accounting configuration file for the specified argument
Gets the privilege assignment list (PAL) category entries of a file
Gets the privilege sets of a file
Gets NIC format host tables from a host
Both
Both
Both
Both
Both
Both
Both
Both
Both
Displays and changes the state of a mainframe GigaRing node
Controls the global resources on a
Cray T3E system
UNICOS
UNICOS/mk
HIPPI disk device monitor and control program
UNICOS
Performs a HYPERchannel interface test UNICOS
Clears a IPI-3/HIPPI packet driver device UNICOS
UNICOS Configures a IPI-3/HIPPI channel up or down
Modifies a IPI-3/HIPPI packet driver option(s)
UNICOS
75
Command hpi3_start hpi3_stat hpi3_stop hpmall hpmflop hsxconfig htable hyroute ift infd initif iocstat ipi3_clear ipi3_config ipi3_option ipi3_start ipi3_stat ipi3_stop kcompress
76
Cray X1™ System Administration Differences
Description
Starts the IPI-3/HIPPI packet driver subsystem
Displays device statistics
Stops the IPI-3/HIPPI subsystem
Reports hardware performance statistics for entire machine workload
Operating System
UNICOS
UNICOS
UNICOS
UNICOS
Reports hardware performance statistics gathered for user processes
Configures HIPPI and HSX channel interfaces
UNICOS
UNICOS
Converts NIC standard format host tables Both
Sets the Internet address to hardware address mapping
UNICOS
Both Reads user Factory Flaw table and reports flaws
Allows the operator to display informative messages
Configures network interfaces
Both
Both
UNICOS Displays information about model E I/O cluster(s) (IOCs) attached to Cray PVP systems and their associated low-speed channel(s)
Clears an IPI-3/IPI packet driver device
Configures an IPI-3/IPI channel up or down
UNICOS
UNICOS
UNICOS Modifies a IPI-3/IPI packet driver option(s)
Starts the IPI-3/IPI packet driver subsystem or a single IOP
UNICOS
Displays device information
Stops the IPI-3/IPI subsystem or a single
IOP
Compresses a UNICOS kernel file
UNICOS
UNICOS
UNICOS
S–2348–24
Command kerbd keyenvoy keyserv klogind krbipd kshd labelit ldcache ld_fs ldsync lmdd lrmt map_mbone mddconf mddcp mdd_pre mfsck migrate mkbinhost
S–2348–24
Administrator Commands [11]
Description
Generates and validates Kerberos tickets for Kerberized NFS
Operating System
Both
Serves as intermediary to keyserv (8) Both
Stores public and private encryption keys Both
Remote login server Both
Validates Kerberos ticket address for
Kerberos servers
Provides remote shell server function
Both
Reads or writes file system labels and security labels
Both
Both
Assigns and displays logical device cache UNICOS
Copies a file or file system from the SWS onto CRAY T3E disks
UNICOS/mk
UNICOS
Both
Flushes logical device cache to disk
Moves I/O for performance and debugging tests
Copies data to rmt (8) command on network
Obtains routing information from multicast routers and builds a topological map from the information
Both
Both
Both Displays or changes a mirrored disk configuration
Copies leg of a mirrored disk
Prepares a mirrored file system for fsck processing, tunes a mirrored file system after fsck processing
Runs file system checks in parallel
Migrates a command or application between processing elements
Creates a binary network host file
Both
Both
Both
UNICOS/mk
Both
77
msgd msgdaemon msgdstop mvdir mverr mvfiles nconf netperf netstart netvar
78
Command mkbuild mkdmp mkfm mkspice mkstp mlmkdir mlrmdir mmr mppview mrinfo mrouted
Cray X1™ System Administration Differences
Description
Builds the UNICOS/mk system and command user exits
Initializes raw dump device header
Make fmsg nodes
Makes inodes for the ce , ift , and spare sector slices
Makes the character special files in
/dev/stp
Operating System
UNICOS/mk
Both
UNICOS
Both
UNICOS
Creates a multilevel directory
Removes a multilevel directory
Both
Both
Reads or writes a GigaRing MMR register UNICOS
Displays massively parallel processing
(MPP) system activity
Both
Both Obtains routing information from a multicast router
Forwards an Internet Protocol (IP) multicast datagram using Truncated
Reverse Path Broadcasting (TRPB)
Both
Allows operators to display action messages
Starts the message daemon
Both
Both
Stops the message daemon
Moves a directory
Moves the errlog file
Manages AIR log files
Displays information about the IOS model
E network driver
Displays X Window System TCP/IP network and NFS statistics
Starts networking software
Displays and alters network configuration variables
Both
Both
Both
UNICOS
UNICOS
Both
Both
Both
S–2348–24
Command newkey newmsglog nfsaddhost nfsaddmap nfsadduser nfsckhash nfsclear nfsd nfsgid nfsidmap nfsidmem nfslist nfsmerge nfsrmhost nfsrmmap nfsrmuser nfsstart nfsuid
S–2348–24
Administrator Commands [11]
Description
Creates a new key in the publickey database
Saves the latest versions of the message log file
Adds host addresses to ID mapping domains
Defines a user ID and/or group ID map for use with NFS
Adds entry from user ID map file to kernel user ID map
Checks consistency of NFS ID mapping hash tables in a kernel or a kernel dump
Operating System
Both
Both
Both
Both
Both
Both
Removes user and group mapping tables and ID mapping domains from the kernel
Both
Starts NFS daemons and services requests Both
Prints a group ID map entry Both
Both Reports or changes the state of NFS ID mapping in the kernel
Reports the amount of kernel memory that NFS ID mapping is using
Lists all kernel ID mapping domains
Both
Both
Both Creates a user or group mapping between the local Cray administrative environment and a remote administrative environment
Both Removes an ID mapping domain host address or a range of host addresses
Removes a previously defined user and/or group ID map
Removes a user ID map entry from a kernel ID map
Both
Both
Starts the network file system (NFS)
Prints entries from a user ID map file, or a user ID map in the kernel or kernel dump
Both
Both
79
Command nisaddcred nisaddent nis_cachemgr niscat nischgrp nischmod nischown nischttl nisctl nisd nisdefaults niserror nisgrpadm nisinit nisln nislog nisls nismatch nismkdir nispasswd nispath nisping nisrm
80
Cray X1™ System Administration Differences
Description
Creates NIS+ credentials
Creates NIS+ tables from their corresponding /etc files and NIS maps
Maintains a cache of location information about NIS+ servers
Displays NIS+ tables and objects
Changes the group owner of an NIS+ object
Changes access rights on an NIS+ object
Changes the owner of an NIS+ object
Changes the time-to-live value of an NIS+ object
Controls the operation of NIS+ servers
NIS+ service daemons
Displays NIS+ default values
Displays NIS+ error messages
Administers NIS+ groups
Initializes an NIS+ client and server
Symbolically links NIS+ objects
Displays the contents of the NIS+ transaction log
Lists the contents of an NIS+ directory
Searches NIS+ tables
Creates NIS+ subdirectories
Changes NIS+ password information
Prints the search path of a specified NIS+ name
Sends a ping to NIS+ servers
Removes NIS+ objects from the namespace
Operating System
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
S–2348–24
nschedv ntalkd ntp ntpstart ntptime nu nwmstart olcfpt oldmon oldt olhpa olmeme
Command nisrmdir nissetup nisshowcache nisstat nistbladm nistest nisupdkeys npecho nqsresp
S–2348–24
Administrator Commands [11]
Description
Removes NIS+ directories
Operating System
Both
Initializes an NIS+ domain Both
Prints the contents of the shared cache file Both
Reports NIS+ server statistics
Administers NIS+ tables
Returns the state of the NIS+ namespace
Updates the public keys in an NIS+ directory object
Utility to loop data to the Ie low-speed network driver
Attempts to open the named pipe that nqsdaemon is reading
Sets memory scheduling parameters
Listens at ports and logs debugging information
Queries a network time protocol (NTP) clock
Starts the NTP daemon
Both
Both
Both
Both
UNICOS
UNICOS
UNICOS
Both
Both
Both
Both Displays offset between local time and real time
Manages user login accounts
Initializes networking media
Online diagnostic CPU confidence tests
Initiates, controls, and monitors the down
CPU diagnostic tests
Provides online confidence testing of Cray disk drives
Formats UNICOS hardware errors logged by errdemon (8)
Cray T3E online memory test
Both
UNICOS
UNICOS
UNICOS
Both
UNICOS
UNICOS/mk
81
pscheck psview quadmin qudu rdump reduce
Command olnet olnxe olperi oper ospf_monitor panic pcache pcinit pcstat pcsync pddconf pddstat privcmd
82
Cray X1™ System Administration Differences
Description
Detects and isolates problems in networks associated with Cray UNICOS systems
Cray T3E online network test
Tests user mode instructions for Cray T3E processor chip
Invokes the operator display manager
Monitors OSPF gateways
Sets or clears the system user panic flag
Controls device cache allocation, deallocation and attributes
Runtime initialization of pcache
Displays device cache statistics
Syncs device cache and sets cache sync interval
Controls the state of a disk drive
Displays information about disk device
I/O
Sets file privileges, security label, permissions mode, owner, owning group, and security flags
Displays status information about the current political scheduling ( psched ) configuration
Displays status information about the political scheduling daemon ( psched )
Administers file quotas
Reports file system quota usage information
Performs a file system dump across a
TCP/IP network
Extracts, formats, and outputs security audit event files
Operating System
UNICOS
UNICOS/mk
UNICOS/mk
Both
Both
Both
UNICOS/mk
UNICOS/mk
UNICOS/mk
UNICOS/mk
Both
Both
Both
UNICOS/mk
UNICOS/mk
Both
Both
Both
Both
S–2348–24
Command regpar remove renumber rep restore ripquery rpcbstart rrestore rstatd rsvportbm runsequence sam samdaemon save_fs sdaemon sdc sdconf sdstat secded setacid setdate
S–2348–24
Administrator Commands [11]
Description
Generates register parity errors
Removes temporary accounting files
Renumbers individual processing elements from the mainframe
Allows the operator to respond to action messages
Operating System
UNICOS
Both
UNICOS/mk
Both
Performs an incremental file system restore
Queries routing information protocol
(RIP) gateways
Starts rpcbind (8) or portmap (8)
Both
Both
Restores a file system dump across a
TCP/IP network
Both
Both
Performs kernel statistics server function UNICOS
Creates a bit map of well-known reserved ports
Both
Performs automatic test sequencing
Displays data about system activity
System activity data daemon
UNICOS
Both
Both
UNICOS/mk Copies a file or file system from Cray T3E disks onto the SWS
Starts or kills daemon processes
Collects system activity data
Controls the state of a disk drive
Displays information about disk device
I/O
Memory error correction interface
SECDED hardware
Sets default accounting ID
Sets the system date from the IOS
Both
Both
Both
Both
UNICOS
Both
Both
83
Command setdev seterr setfs setpal setprivs sfsd shrtree shradmin shrdaemon shrdist shrlimit shrmon shrsync slogdemon smpmon smtd snmpd snmproute so_stpio
84
Cray X1™ System Administration Differences
Description
Initializes /dev information, including nodes for disk configuration
Sets maximum user error counts
Changes dynamic information in file system super block
Sets privilege assignment list (PAL) category entries of a file
Modifies the file privilege sets of a file
Initializes and monitors the External
Semaphore Device
Displays the fair-share hierarchy defined in the user database (UDB)
Changes and displays costs for fair-share scheduler usage calculations
Performs system functions for the fair-share scheduler
Redistributes shares among a resource group for the fair-share scheduler
Sets another user’s limits for the fair-share scheduler
Monitors detailed system fair-share scheduling information
Synchronizes the UDB and fair-share information for active users
Security event logging daemon
Interactively monitors the physical-layer
External Semaphore Device
FDDI station management daemon
SNMP agent daemon
Performs route tracing with the Simple
Network Management Protocol
User level test for scheduled transfer (ST) protocol
Operating System
UNICOS/mk
UNICOS
Both
Both
Both
Both
Both
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
UNICOS
Both
UNICOS
Both
Both
UNICOS
S–2348–24
Command spaudit spcheck spdev spfilck spmap spnet spwcard ssd ssddconf start_air staticrts stconf stdhosts stor stpio suspend swapper sysctl tcpstart
S–2348–24
Administrator Commands [11]
Description
Changes security auditing criteria
Performs security checks on a UNICOS or
UNICOS/mk system
Sets, clears, and displays objects
Checks and sets file ownership, access, and security parameters
Reads or generates and writes a physical disk spare map
Manages NAL, WAL, and IP Security
Options (IPSO) maps stored in network security tables
Operating System
Both
Both
Both
Both
Both
Both
Sets wildcard levels on system directories in a trusted environment
Display and change SSD configuration information
Converts/prints Internet addresses from hosts (5) or networks (5) files
Defines physical storage
Both
UNICOS
Controls the state of a model E SSD drive UNICOS
Starts the automated incident reporting
(AIR) system
UNICOS
Installs static routing information
Configures an ST unit
Both
UNICOS
Both
Both
UNICOS User-level test for scheduled transfer (ST) protocol
Suspends or resumes a process or group of processes
Displays current system swapping activity
Gets or sets kernel state
Starts the TCP/IP networking software
Both
Both
Both
Both
85
Command tpapm tpbmx tpclr tpconf tpconfig tpcore tpdaemon tpdev tpdstop tpformat tpfrls tpgstat tpinit tplabel tpmls tpmql tpscr tpset tpu trcollect trformat trpt
86
Cray X1™ System Administration Differences
Description
Tape daemon autoloader premount program
Displays operator information about tape devices
Clears the tape drive
Verifies new format tape daemon configuration file and converts it to binary
Configures tape devices up and down
Initiates the tape subsystem monitor
Starts tape daemon
Displays current tape equipment configuration
Stops tape daemon
Formats an ER90 tape volume
Forcibly releases tape reservation and associated devices
Displays user reservation status for all users
Initializes the tape subsystem
Labels a magnetic tape
Displays loader status
Displays tape daemon mount request queue list
Returns volumes to loader scratch pool
Sets features for the tape daemon
Unloads tape drives
Collects trace information for TCP/IP and
NFS
Formats trace information obtained from trcollect (8)
Transliterates protocol trace
Operating System
Both
Both
Both
Both
Both
Both
Both
Both
Both
UNICOS
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
S–2348–24
Command tsar turndacct udb_collect udb_edit udb_helper udb_merge udb_server udb_update udbchain udbgen udbpl udbrstrict unitap urmd urmsnap usetjob vht vst vtt warmboot
S–2348–24
Administrator Commands [11]
Description
System data processing language
Controls daemon accounting
Forwards UDB source to the collecting node in a cluster upon request
Generates a template cluster UDB record or extracts an existing cluster UDB record
Customizes the UDB source file collection and updates the UDB information on each node in the cluster
Generates a cluster UDB source file from collected node UDB source files
Operating System
Both
Both
UNICOS
UNICOS
UNICOS
UNICOS
Executes the cluster UDB requests on individual nodes
Distributes UDB changes to all nodes in the cluster
UNICOS
UNICOS
Verifies the user database (UDB) UNICOS/mk
Generates or maintains the user database Both
Prints administrative information for designated users
Both
Enables and disables user access Both
Provides online testing of magnetic tapes UNICOS
UNICOS Starts the Unified Resource Manager
(URM) daemon
Captures the current URM configuration
Changes minimum rank field in URM job table entries
Exercises SPN-based HIPPI devices
Exercises network devices capable of running TCP/IP
Provides tape device testing
From the mainframe, reboots or halts individual PEs
UNICOS
UNICOS
Both
Both
Both
UNICOS/mk
87
Cray X1™ System Administration Differences
Command watchstream xadmin xdi xdms xfddimap xmppview xsam xtpldr yppasswdd ypstart
Description
System monitoring program for the SWS
Manages user login accounts through a graphical user interface
Graphical user interface for X Window
System based diagnostic applications
Provides online disk maintenance and initialization routines for Cray GigaRing attached SCSI and fibre channel devices driven by the xdd driver
X Window System utility to draw an FDDI ring map
Displays MPP system activity through a graphic user interface
Displays graphic data about system activity
Manages selected autoloader operations
Handles password change requests from yppasswd
Starts the network information service
(NIS)
Operating System
Both
Both
Both
Both
UNICOS
Both
Both
Both
Both
Both
11.3 Administrator Commands Modified for UNICOS/mp
Table 10 lists the administrator commands that exist in UNICOS or UNICOS/mk
systems but have been modified for use in UNICOS/mp systems.
88 S–2348–24
Command rwall wall
Administrator Commands [11]
Table 10. Administrator Commands Modified for UNICOS/mp
Description Modification
Writes to all users over a network Implemented as a user command in
UNICOS/mp; was implemented as an administrator command in UNICOS and
UNICOS/mk
Writes to all users Implemented as a user command in
UNICOS/mp; was implemented as an administrator command in UNICOS and
UNICOS/mk
S–2348–24 89
Cray X1™ System Administration Differences
90 S–2348–24
User Commands [12]
The UNICOS/mp system provides a subset of the traditional UNIX command set. This chapter details the differences between the UNICOS and UNICOS/mk user command sets and the UNICOS/mp user command set.
In addition to the command information listed here, see Section 6.6, page 40 for
detailed information about networking commands.
Command apkill aprun apstat attr bufview chacl chcap cpr flex fmtmsg getoptcvt gzdiff gzexe gzforce gzgrep
S–2348–24
12.1 User Commands Unique to UNICOS/mp
Table 11 lists the user commands that are included in the UNICOS/mp system,
but not in UNICOS or UNICOS/mk systems.
Table 11. User Commands Unique to UNICOS/mp
Description
Sends a signal to a specified application
Starts an application on a Cray X1 system
Provides status information of UNICOS/mp applications
Manipulates Extended Attributes on file system objects
Monitors file system buffer cache activity
Changes the access control list of a file or directory
Changes file capability sets
Checkpoints and restarts processes; provides information about existing statefiles; deletes statefiles
Generates programs that perform pattern-matching on text
Displays a message on stderr or console
Parses command options
Compares compressed files
Compresses or decompresses executable files in place
Forces a .gz
extension on all gzip files
Searches possibly compressed files for a regular expression
91
Cray X1™ System Administration Differences
Command gzmore gznew lfmt mkmsgs ordist pfmt pmake quota ruptime rwho screen smake tcsh tlink userlimit
Description
Views compressed text
Recompresses .Z
files to .gz
files
Displays error message in standard format
Creates message file for use by gettxt
Distributes remote files
Displays error message in standard format
Creates programs in parallel
Displays disk usage and limits
Shows host status of local machines
Shows who is logged in on local machines
Screen manager with VT100/ANSI terminal emulation
Creates programs in parallel
Provides shell with file name completion and command line editing
Clones a file tree using symbolic links
Prints some or all of the information in the user limits database
12.2 User Commands Not Included for UNICOS/mp
Table 12 lists the user commands that exist in UNICOS or UNICOS/mk systems,
but not in UNICOS/mp systems. The column headed "Operating System" lists the operating system on which the command is supported: UNICOS,
UNICOS/mk, or both.
Command adb addbss airlogger
92
Table 12. User Commands Not Included for UNICOS/mp
Description
Invokes the absolute debugger
Increases the amount of BSS space in an executable file
Logs AIR messages in the system log
Operating System
UNICOS
UNICOS
UNICOS
S–2348–24
Command amlaw ar as ascheck banner bftp bld builddefs calendar catxt cb cdc cflow chacid checknr chkey
S–2348–24
User Commands [12]
Description
Displays maximum theoretical parallel processing speedup
Archive and library maintainer for portable archives. (Released as a part of the Cray Programming Environment release package, so it is available to
UNICOS/mp users.)
Invokes the CAL assembler version
2 (CAL2). (Released as a part of the
Cray Programming Environment release package, so it is available to
UNICOS/mp users.)
Validates the Array Services configuration
Makes posters
Provides user interface to the background file transfer program
Maintains relocatable libraries
Reads a definitions file that has embedded keywords to produce a keyword file and a definitions file without embedded keywords
Reminder service
Extracts message explanations from a message text file
C program beautifier
Changes the delta commentary of an
SCCS delta
Generates C-language flowgraph
Changes account ID of disk files
Checks nroff and troff input files; reports possible errors
Changes your encryption key
Operating System
UNICOS
Both
UNICOS
UNICOS
Both
Both
UNICOS
Both
Both
Both
Both
Both
Both
Both
Both
Both
93
Cray X1™ System Administration Differences deplib deroff diffmk emacs eqn etags exdf factor fck flodump from
Command chkpnt (replaced by cpr (1)) chkpnt_util chkptint chsh col csort cxref define
94
Description
Checkpoints a process, multitask group, or job
Verifies restartability of restart files
Registers current session to be checkpointed upon shutdown and/or periodically
Changes default login shell
Filters reverse line feeds
Sorts and/or merges blocked files
Generates C-language program cross-reference table
Displays definitions of Cray technical terms and terms added by a local site that match a specified search term
Manipulates dependent library names in bld library files
Removes nroff , troff , tbl , and eqn constructs
Marks differences between versions of a troff (1) input file
Invokes GNU project Emacs editor
Typesets mathematics
Generates tag file for Emacs
Transfers files to or from the IOS partition on the system console
Factors a number
Provides file information from file system internals
Recovers Flowtrace data from a dump or running process
Prints mail header lines to show you from whom your mail originated
Operating System
Both
UNICOS
UNICOS
Both
Both
UNICOS
Both
Both
UNICOS
Both
Both
Both
Both
Both
UNICOS
Both
Both
UNICOS
Both
S–2348–24
Command fts grmview guest host hpm ispell ja jstat kcp kdestroy keylogin kinit klist klogin kpasswd krsh ksrvtgt ksu ld limit
S–2348–24
User Commands [12]
Description
Performs file transfer server function for bftp (1B)
Displays information from GRM about the current PE configuration, running applications, and waiting application
Performs UNICOS Guest administrative functions
Looks up host names by using domain server
Monitors hardware performance during program execution
Corrects spelling for a file
Job accounting information
Displays job status information
Copies remote files and directories
Destroys Kerberos tickets
Decrypts and stores a secret key
Logs in to the Kerberos authentication and authorization system
Provides list of currently held Kerberos tickets
Performs remote login
Changes a user’s Kerberos password
Connects to the remote shell
Uses a service key to fetch and store a
Kerberos ticket-granting ticket
Uses Kerberos to substitute user ID
Invokes the link editor. (Released as a part of the Cray Programming
Environment release package, so it is available to UNICOS/mp users.)
Sets resource limits
Operating System
Both
UNICOS/mk
UNICOS
Both
UNICOS
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
95
Command lint lmcksum lmdown lmgrd lmhostid lmremove lmreread lmstat lmutil lmver lorder machid makekey mpprun msgi msgr mt mtdump mvf nasa nfsid
96
Cray X1™ System Administration Differences
Description
A C-language program checker
Checksums the FLEXlm license file
Shuts down all FLEXlm license daemons gracefully
Invokes the FLEXlm license daemon
Displays the host ID of a system
Removes specific FLEXlm licenses and returns them to license pool
Instructs the FLEXlm license daemon to reread the license file
Reports status of FLEXlm license daemons and feature usage
Both
Both
Both
Both
Core FLEXlm utility Both
Displays the FLEXlm version being used Both
Finds ordering relation for an object library
Both
Gives truth value about processor type
Generates encryption key
Both
Both
Executes a specified MPP compiled binary file
Sends informative message to operator
Sends action message to operator
Issues commands to a magnetic tape drive
Examines unformatted dump of multitasking history buffer
Provides a multivolume tape filter
Adds ASA carriage control characters for printing
Performs NFS authorization functions to
NFS servers
Operating System
Both
Both
Both
Both
UNICOS/mk
Both
Both
Both
UNICOS
Both
Both
Both
S–2348–24
User Commands [12]
Command nlimit nmake nroff obc odc pagesize pg privtext procstat ptyrecon quota quotamon regcmp remsh restart (Use cpr (1) instead) rls rmgr rsv sag scanit sdss segldr setf
S–2348–24
Description
Queries and modifies resource limits
Maintains and updates programs
Text formatting language
Invokes the arithmetic language preprocessor
Invokes the desk calculator
Displays and modifies segment page size information
File perusal filter for CRTs
Gets the privilege text of a file
Gathers I/O and process statistics
Manages pty reconnection
Reports quota information
Monitors quota state
Compiles regular expressions
Invokes a remote shell
Recovers a process, application, or job from a restart file
Releases reserved tape resources
Provides an interface to the Unified
Resource Manager (URM) daemon
Reserves tape resources
Displays system activity graph
Corrects code for certain user programs on Cray J90, Cray J90se, and Cray SV1 series systems
Reports status information about the secondary data segment pool
Invokes the Cray segment loader
(SEGLDR)
Initializes a file
Operating System
Both
Both
Both
Both
Both
UNICOS/mk
Both
Both
UNICOS
UNICOS
Both
Both
Both
Both
Both
Both
UNICOS
Both
Both
UNICOS
UNICOS
UNICOS
Both
97
Command setlabel snmptest snmptrap snmptrapd snmpwalk soelim spacl spclr spset sysconf setucat setucmp setulvl setusrv shrview sim sm snmpget snmpgetnxt snmpnetstat snmpstatus
98
Cray X1™ System Administration Differences
Description
Provides a method for selecting specific processing elements (PEs) when running applications
Sets your active categories
Sets your active compartments
Raises your active security level
Sets your authorized security attributes
Displays detailed fair-share scheduler information
Invokes an interactive Cray simulator
Invokes the UNICOS Source Manager
(USM)
Communicates with a network entity by using SNMP GET requests
Communicates with a network entity by using SNMP requests
Shows network status by using SNMP
Retrieves important information from a network entity by using SNMP requests
Communicates with a network entity by using SNMP requests
Operating System
UNICOS/mk
Both
Both
Both
Both
UNICOS
UNICOS
Both
Both
Both
Both
Both
Both
Sends an SNMP TRAP message to a host Both
Receives and logs SNMP TRAP messages Both
Both Communicates with a network entity by using SNMP requests
Resolves and eliminates .so requests from nroff (1) or troff (1) input
Both
Manages an access control list (ACL)
Performs secure clear operations
Sets and displays security attributes
Displays system configuration data
Both
Both
Both
Both
S–2348–24
tpstat troff udbsee unifdef units ustat uucp uustat uux whichcat
Command target tbl tc tmpdir tpcatalog tplist tpmnt tpquery tprst
S–2348–24
User Commands [12]
Description
Verifies target CPU characteristics. (Use uname (1) instead.)
Operating System
Both
Formats tables for nroff (1) or troff (1) Both troff (1) output interpreter Both
Creates a unique temporary directory Both
Both Catalogs, recatalogs, or deletes a dataset in a front-end catalog
Lists contents of tape volume
Requests a tape mount for a tape file
Queries autoloaders for VSN information
Displays reserved tape status for current job ID
Displays current tape status
Typesets or formats documents
Writes the ASCII source of a user database
Resolves and removes lines surrounded by #ifdef preprocessor statements
Unit conversion program
Both
Both
Both
Both
Both
Both
Both
Both
Both
UNICOS Displays Unified Resource Manager
(URM) session information
System-to-system copy uucp status inquiry and job control
Copies files to a location within the same system
Returns the name of the message system catalog being accessed
Both
Both
Both
Both
99
Cray X1™ System Administration Differences
12.3 User Commands Modified for UNICOS/mp
Table 13 lists the user commands that exist in UNICOS or UNICOS/mk systems,
but have been modified for use in UNICOS/mp systems.
Command dd du mkfifo renice su
Table 13. User Commands Modified for UNICOS/mp
Description
Converts and copies a file to the specified output device
Summarizes disk usage
Makes FIFO special files
Sets system scheduling priorities of running processes
Lets you become another user or the superuser
Modification
Implemented as an administrator command in UNICOS/mp; was implemented as a user command in
UNICOS and UNICOS/mk.
Implemented as an administrator command in UNICOS/mp; was implemented as a user command in
UNICOS and UNICOS/mk.
Implemented as an administrator command in UNICOS/mp; was implemented as a user command in
UNICOS and UNICOS/mk.
Implemented as an administrator command in UNICOS/mp; was implemented as a user command in
UNICOS and UNICOS/mk.
Implemented as an administrator command in UNICOS/mp; was implemented as a user command in
UNICOS and UNICOS/mk.
100 S–2348–24
S–2348–24
Glossary
access control list (ACL)
An extension to the normal file discretionary access control. ACLs support the ability to grant or deny access to a file on any user and/or group basis.
air-cooled (AC)
For Cray X1 systems, the description of the cabinet that uses a combination of
Fluorinert liquid and forced air to cool the components on a node module. The
Fluorinert is air cooled within a heat exchange unit so that a chilled water supply is not required for AC Cray X1 systems. An AC cabinet uses two blowers: one for the forced air cooling in the module cabinet, and the second for the Fluorinert heat exchange unit.
application node
For UNICOS/mp systems, a node that is used to run user applications.
Application nodes are best suited for executing parallel applications and are managed by the strong application placement scheduling and gang scheduling mechanism Psched. See also node; node flavor.
ApTeam
Applications launched via aprun or mpirun create an ApTeam of processes.
An ApTeam can be a single execution thread or a large number of processes and can use shared memory, distributed memory, or a hybrid model for parallel execution.
brick
A Cray X1 hardware term for four grouped node modules. On the Cray X1 mainframe cabinet, a brick is designated as either V or W. See also brick-pair;
node module.
brick-pair
Two bricks (the space required for 8 node modules) in the front or back half
(V-side or W-side for notational reference) of a liquid-cooled Cray X1 mainframe cabinet. Air-cooled Cray X1 systems have only the V-side brick. See also brick;
node module.
101
Cray X1™ System Administration Differences
102
C-brick
For Cray X1 systems, the modular controller component of a RAID subsystem, also called a controller brick. It is located in a PC-20. A C-brick can have multiple associated RAID storage components (S-bricks).
Common Installation Tool (CIT)
A graphical user interface (GUI) for loading software. The cit and setup commands invoke CIT.
Cray L0 controller
For Cray X1 systems, a microprocessor, physically located on a Cray L1 controller assembly and connected to a Cray L1 controller, that provides environmental monitoring and protection for the node module, router module, brick cooling unit (BCU), and I/O drawer (IOD) components.
Cray L1 controller
For Cray X1 systems, a microprocessor, embedded on a Cray L1 controller assembly, that is used as the maintenance access point to the node module, router module, brick cooling unit (BCU), and I/O drawer (IOD) components.
Cray Network Subsystem (CNS)
A specialized router (gateway) providing IP (Internet Protocol) network connectivity between a Cray mainframe and site networks. The CNS also provides Transmission Control Protocol (TCP) assist functionality that can enhance TCP performance in Cray systems.
Cray Open Software (COS)
A collection of public-domain software that is an optional product available for porting to certain Cray systems. COS provides options that are either not available in or behave differently than Cray operating system utilities. Using
COS also makes the transition to a new Cray system easier for programs that already use the utilities included in COS.
Cray Programming Environment Server (CPES)
A server for the Cray X1 system that runs the Programming Environment software.
S–2348–24
S–2348–24
Glossary
Cray Storage Management (CRAYSM)
Software on the Cray Workstation (CWS) that is used for configuring the RAID subsystem.
CrayDoc
Cray’s documentation system for accessing and searching Cray books, man pages, and glossary terms from a web browser.
CWS subnetwork
The network that connects Cray Workstations (CWSs) together through a switch.
This CWS shared private network exists only when there are multiple CWSs connected to a single Cray X1 system, due to either partitioning or resiliency.
deferred implementation
The label used to introduce information about a feature that will not be implemented until a later release.
elapsed time
The amount of real time, as measured by a clock, that passes between the start and termination of a user process. This includes user processing time, operating system time, I/O wait time, and sleep or idle time.
Etnus TotalView
For UNICOS/mp systems, a symbolic source-level debugger designed for debugging the multiple processes of parallel Fortran, C, or C++ programs.
failover
The ability to define and manage alternate paths to a single disk device or part of a disk device.
Global Resource Manager
The UNICOS/mp function that manages and allocates resources, including processors and memory.
granular privilege mechanism
A security feature that divides the power of the superuser into discrete units of privilege called capabilities.
103
Cray X1™ System Administration Differences
I/O Channel Adapter (IOCA)
For Cray X1 systems, a field programmable gate array, resident on an IOB, that converts proprietary System Port Channel transactions into standard PCI-X bus transactions.
liquid-cooled (LC)
Describing a Cray X1 system that has a chilled water supply. An LC system uses two chilled-water heat exchange systems: one to cool the Fluorinert liquid, and one to cool the forced air that cools node modules.
Message Passing Toolkit (MPT)
A Cray product that consists of the Message Passing Interface and shared distributed memory (SHMEM) data-passing routines.
Modules
A package on the UNICOS/mp system that allows you to dynamically modify your user environment by using module files. (This term is not related to the module statement of the Fortran language; it is related to setting up the
UNICOS/mp system environment.) The user interface to this package is the module command, which provides a number of capabilities to the user, including loading a module file, unloading a module file, listing which module files are loaded, determining which module files are available, and others.
MSP mode (multistreaming mode)
One of two types of application modes for UNICOS/mp systems. Programs are compiled either as MSP-mode applications (default) or SSP-mode applications.
MSP-mode applications run on one or more MSPs. For MSP-mode applications, each MSP coordinates the interactions of its associated four SSPs. See also SSP
mode.
multicabinet switch
Where there are one or more liquid-cooled Cray X1 cabinets or multiple air-cooled Cray X1 cabinets, the switch between the CWS and the switches in the Cray X1 cabinets and the I/O cabinets (IOCs). The top of two switches physically located in the first IOC. Referred to in the Cray X1 configuration file as topswitch (top switch).
104 S–2348–24
S–2348–24
Glossary multichip module (MCM)
For Cray X1 systems, the packaging that contains a multistreaming processor
(MSP) and resides on a node module assembly. The MCM contains four processor chips (P-chips) and four cache chips (E-chips). See also MSP.
multistreaming processor (MSP)
For UNICOS/mp systems, a basic programmable computational unit. Each MSP is analogous to a traditional processor and is composed of four single-streaming processors (SSPs) and E-cache that is shared by the SSPs. See also node; SSP;
MSP mode; SSP mode.
multiuser mode
For UNICOS/mp systems, system operation when there are multiple login sessions, many files open at once, and many active processes, including numerous daemons.
named pipe
A first-in, first-out file that allows communication between two unrelated processes running on the same host.
network file system (NFS)
A file system that is exported from a remote server and mounted on other hosts across a network.
Network Information Service (NIS)
A network-based information service and an administrative tool. It allows centralized database administration and a distributed lookup service. NIS supports multiple databases based on regular text files. For example, NIS databases can be generated from the hosts , passwd , group , and aliases files on the NIS master.
Network Time Protocol (NTP)
For Cray X1 systems, the protocol that allows synchronizing the clocks in the
System Controller and Cray mainframe by pointing the mainframe clocks to the
CWS. NTP is used by the CWS to keep the Cray L1 controllers synchronized.
This provides consistent time stamps among the various logs for use in diagnosing system problems.
105
Cray X1™ System Administration Differences
106 node
For UNICOS/mp systems, the hardware that comprises four multichip modules (MCMs) with one multistreaming processor (MSP) per MCM; globally addressable shared local memory that can be thought of as a cache domain; high-speed node interconnections; and system I/O ports. Physically, all nodes are the same; software controls how a node is used: as an OS node, application node, or support node. See also MCM; MSP, node flavor; SSP.
node flavor
All Cray X1 nodes are physically the same; software controls how a node is used.
A node’s software-assigned flavor dictates the kind of processes and threads that can use its resources. The three assignable node flavors are application, OS, and support. See also application node; OS node; support node; system node.
node module
For a Cray X1 mainframe, the physical, configurable, scalable building block.
Each node module on a Cray X1 system contains one Remote Translation Table
(RTT) and one node. See also node.
OS node
For UNICOS/mp systems, the node that provides kernel-level services, such as system calls, to all support nodes and application nodes. See also node; node flavor.
page size
The unit of memory addressable through the Translation Lookaside Buffer (TLB).
For Cray X1 systems, the base page size is 65,536 bytes, but larger page sizes (up to 4,294,967,296 bytes) are also available.
parallel processing
Processing in which multiple processors work on a single application simultaneously.
partitioning
Configuring a UNICOS/mp system into logical systems (partitions). Each partition is independently operated, booted, dumped, and so on without impact on other running partitions. Hardware and software failures in one partition do not affect other partitions.
S–2348–24
S–2348–24
Glossary path-managed disk driver
On Cray X1 systems, a logical disk driver that can manage one or more physical paths to each disk logical unit (LUN).
PC-20
For Cray X1 systems, the peripheral cabinet that can contain either RAID C-bricks and RAID S-bricks or a Cray Programming Environment Server (CPES), peripherals for the CPES, and the Cray Network Subsystem (CNS).
Psched
The UNICOS/mp application placement scheduling tool. The psched command can provide job placement, load balancing, and gang scheduling for all applications placed on application nodes.
RAID subsystem
The Cray X1 disk storage system, including RAID controllers, C-bricks, S-bricks, and the Fibre Channel using SCSI protocol paths from the I/O chassis to the various devices handling I/O.
rank
The number of dimensions in a Fortran array. Rank is declared when the array is declared and cannot change.
S-brick
For Cray X1 systems, the modular, scalable storage component of a RAID subsystem, also called a storage brick. It is located in a PC-20. Each S-brick contains a number of Fibre Channel disk drives. The number of drives per
S-brick and the size of each disk varies with the different S-brick modules.
single-streaming processor (SSP)
For UNICOS/mp systems, a basic programmable computational unit. See also
node; MSP; MSP mode; SSP mode.
single-user mode
For UNICOS/mp systems, system operation when only a few processes are active on the system and only a single login is allowed.
107
Cray X1™ System Administration Differences
SSP mode (single-streaming mode)
One of two types of application modes for UNICOS/mp systems. Programs are compiled either as MSP-mode applications (default) or SSP-mode applications.
SSP-mode applications run on one or more SSPs. Each SSP runs independently of the others, executing its own stream of instructions. In contrast, compiler options enable the programmer to develop command-mode programs that run on an SSP on the support node. See also MSP mode.
support node
For UNICOS/mp systems, the node that is used to run serial commands, such as shells, editors, and other user commands ( ls , for example). See also node;
node flavor.
System Control Facility (SCF)
For Cray X1 systems, the Cray L1 controllers, Cray L0 controllers, one or more
Cray Workstations (CWSs), and connecting network equipment.
System Integrity Check (SICK)
A remote support tool that monitors the integrity of the Cray system and alerts analysts and system administrators if abnormal operating conditions occur.
system node
A UNICOS/mp system requires a minimum of two nodes. Each system typically uses at least one node that is designated as both an OS node and a support node; this node is often called a system node; however, there is no node flavor of
"system." See also node; node flavor.
type
A means for categorizing data. Each intrinsic and user-defined data type has four characteristics: a name, a set of values, a set of operators, and a means to represent constant values of the type in a program.
UNICOS/mp
The operating system for Cray X1 systems.
108 S–2348–24
S–2348–24
Glossary vector
A series of values on which instructions operate; this can be an array or any subset of an array such as row, column, or diagonal. Applying arithmetic, logical, or memory operations to vectors is called vector processing.
X1WACS
The Cray X1 warning and control system, run by the x1wacs program, that enables the user to control power and monitor hardware status for one or more mainframe cabinets and one or more associated I/O cabinets.
XFS file system
The standard UNICOS/mp file system; a journaling, mature file system with support for very large individual files and file systems.
109
Cray X1™ System Administration Differences
110 S–2348–24
Index
A
ApTeam accounting report, 54 acctcom , 54
Application placement, 51 apstat (1), 51
B
C
CPES, 55 sockets, 55 uncheckpointable objects, 55
not included for UNICOS/mp, 69
autofs
automount
S–2348–24
dumpmf
finger , 41 fingerd , 41 ftp , 41 ftpd , 41
hostid , 41 hostname , 41 ifconfig , 41 inetd , 41 lockd , 41 lp , 41
named , 42 netstat , 42 nettest , 42
111
Cray X1™ System Administration Differences
ping , 42 portmap , 42 rcp , 42 rdist , 42
rexecd , 42 rlogin , 42 rlogind , 42 rmt , 42 route , 42
, 42 rpcbind , 42 rpcgen , 42 rpcinfo , 42 rsh , 42 rstatd , 42
112
spray , 43 sprayd , 43 statd , 43 telnet , 43 telnetd , 43 tftp , 43 tftpd , 43
timedc , 45 timeslave , 45 timetrim , 45
watchlog
watchstream
, 15, 18 x1-log-filter , 18 x1-log-viewer , 18
ypmatch , 43 yppasswd , 43 yppoll , 43 yppush , 43 ypserv , 43 ypset , 43 ypwhich , 43 ypxfr , 43
S–2348–24
Commands, SWS errpt , 15 nwacs , 15 sserrpt , 15
syslog , 15 syslogd , 15 sysmon , 15
watchlog , 15 watchstream , 15
Configuration (system), 23 hardware, 23
Cray Network Subsystem (CNS)
See CNS
Cray Programming Environment Server (CPES)
See CPES
Cray storage management tools, 29
Cray system workstation (SWS)
See SWS
Cray Workstation (CWS)
See CWS
comparison to SWS functionality, 15
S–2348–24
Index
Private Administration network, 16
D
Device node naming schemes dksc , 31
Directories changed from UNICOS or UNICOS/mk, 36
Cray storage management system, 29
pmd , 31 device node naming schemes
113
Cray X1™ System Administration Differences
differences, 29 partition numbers, names, and functions, 29
using fx , 30 using parts , 30
UNICOS and UNICOS/mk systems, 29
E
/etc/group migrating from UNICOS or UNICOS/mk, 52
/etc/passwd migrating from UNICOS or UNICOS/mk, 52
F
File systems administration, 29
Filesystem Hierarchy Standard (FHS) Version
UNICOS and UNICOS/mk systems, 32
UNICOS/mp systems, 32 managing
114
UNICOS and UNICOS/mk systems, 32
G
Global Resource Manager
See GRM
GRM psched , 51 grmview (1), 51
I
RAM file system, 21 software, 21
IP over Fibre Channel, 39 router, 39
J
L
l1net command troubleshooting, 17
M
Migrating scripts to PBS Pro, 63
S–2348–24
N
Network connectivity, validating, 17
Network Information Service (NIS), 40
Network Queueing System
See NQS
Network Timing Protocol (NTP), 40
Networking daemons and commands, 40
NFS differences from UNICOS, 39
NQE and PBS Pro feature comparison, 61
migrating scripts to PBS Pro, 63
NQS/NQE migrating scripts to PBS Pro, 63 nqs2pbs utility, 63
O
P
Partitions general purpose, 30 reserved, 30 root, 30
S–2348–24
Index
swap , 30 volhdr , 30 volume, 30
PBS Pro administration documentation, 64
key features comparison with NQE, 61
migrating scripts to PBS Pro, 63
PBS Pro documentation for system administrators, 64
pmd
Political scheduler
See Placement scheduler
R
RAM file system installation, 21
Resource administration accounting, 53
system monitoring and reporting, 54
S
SCF
See System Control Facility (SCF)
Security access control lists (ACLs), 47
configurable authentication, 49
115
Cray X1™ System Administration Differences
encrypted password protection, 47
extensions to traditional UNIX security not provided, 48
extensions to traditional UNIX security provided, 47 features, 47
granular privilege mechanism, 48
privilege assignment list (PAL), 48
comparison to CWS functionality, 15
syslog SWS command, 15 syslogd SWS command, 15 sysmon SWS command, 15
116
System configuration, 23 hardware, 23
System Control Facility (SCF), 16
System Integrity Check (SICK)
See SICK
System monitoring and reporting, 54
T
Transmission control protocol (TCP), 39
U
User datagram protocol (UDP), 39
W
See also X1WACS
Warning and Control System (WACS)
See WACS watchlog
watchstream
S–2348–24
X
x1-log-filter command, 18 x1-log-viewer command, 18
See also WACS
Index
S–2348–24 117
Atsisiųsti
Vieša nuoroda atnaujinta
Vieša nuoroda į jūsų pokalbį buvo atnaujinta. You may view and manage your chat links after registration here.
Dokumento vieša nuoroda
Reklama
