NonStop S-Series Planning and Configuration Guide (G06.25+)
Table Of Contents
- What’s New in This Guide
- About This Guide
- 1 Terms and Concepts
- NonStop S-Series Servers
- Enclosures
- Components
- Components, Processor Enclosure Without Power Shelf, Appearance Side
- Components, Processor Enclosure Without Power Shelf, Service Side
- Components, I/O Enclosure Without Power Shelf, Appearance Side
- Components, I/O Enclosure Without Power Shelf, Service Side
- Components, Processor Enclosure With Power Shelf, Appearance Side
- Components, Processor Enclosure With Power Shelf, Service Side
- Components, I/O Enclosure With Power Shelf, Appearance Side
- Components, I/O Enclosure With Power Shelf, Service Side
- Components in NonStop S76000, S86000, and Later Configurations
- Cluster Switch Enclosure
- IOAM Enclosure Components
- CRU Identification, System Enclosures
- FRU Identification, IOAM Enclosures
- CRUs and FRUs
- CRU/FRU Replacement Tools
- ServerNet Architecture
- Networking
- 2 The ServerNet Communications Network
- 3 Topologies
- 4 System Components
- Appearance Side of System Enclosures
- Service Side of System Enclosures
- Group ID Label
- Module ID Label
- Group Service LED
- SEBs and MSEBs
- Associated Fabrics
- Adapter Slots and Associated Fabrics
- ServerNet Adapters
- Filler Panels
- Slot Assignments for Slots 51 Through 54
- Emergency Power-Off (EPO) Connector
- Processor Multifunction (PMF) CRUs
- Configurations of Memory Units
- I/O Multifunction (IOMF) CRUs
- Enclosure Doors
- Tall Enclosure Door
- Enclosure Side Panel
- Plug-in Cards
- Typical PIC Installations
- System Console
- Tape Drives
- SWAN Concentrators
- External Disk Drives
- ServerNet Clusters
- IOAM Enclosures
- 5 ServerNet Cabling
- 6 ServerNet Communication Pathways
- 7 Enclosure Arrangements and Cable Connections
- 8 Initial Configurations
- Processor Numbers and Locations
- Processor Types and Memory Sizes
- Internal Disk Drives
- External Disk Drives
- Tape Drives
- Initial Default Values for System Attributes
- Initial Configuration Files
- Objects Configured in the Initial CONFIG File
- Objects That Must Not Be Renamed
- Command Files for Objects Not Configured in the Initial CONFIG File
- Files Used to Create the Initial CONFIG File
- CONFBASE File
- Naming Conventions Used in the SCF0000 File for SCF Objects
- SCF Commands to Automate Disk Configuration
- SWAN Concentrator Configurations
- Ethernet Ports on PMF CRUs and IOMF CRUs
- ServerNet Adapter Configurations
- Factory-Default Configuration of MFIOBs
- Initial IP Addresses for System and System Consoles
- IOAM Enclosures
- 9 The Planning and Configuration Process
- People and Functions
- The Installation Forms
- Preparing to Plan
- Installing a New System
- Changing an Existing System
- Changing the System Name or System Number
- Adding a System Enclosure
- Adding Memory to a Processor
- Adding a System Console
- Enclosure Interleaving for Storage Devices
- Configuring $SYSTEM Disk Slots
- Adding an Internal Disk Drive
- Changing the Configuration of a Disk Drive
- Adding a Tape Drive
- Changing the Configuration of a Tape Drive
- Adding a ServerNet Adapter
- Changing the System Configuration of a ServerNet Adapter
- Adding a SWAN or SWAN 2 Concentrator
- Changing the Configuration of a SWAN Concentrator
- Adding an AWAN Server
- Changing the Configuration of an AWAN Server
- Adding or Changing the WAN Subsystem
- Adding an Open SCSI Device
- Adding or Changing the Configuration of Other Peripheral Devices
- 10 Planning for System Availability and Support
- 11 Planning for LAN Communications
- 12 Site Planning and Preparation
- 13 Completing the Installation Plan
- Create the Installation Schedule
- Assemble the Installation Document Packet
- Installation Document Checklist
- System Equipment Inventory Form
- Enclosure Arrangement Diagram
- Floor Plan
- Preinstalled I/O Device Cable Checklist
- System Enclosure Checklist
- PMF CRU Configuration Forms
- IOMF CRU Configuration Forms
- ServerNet Adapter Configuration Forms
- ServerNet Cluster Configuration Form
- ServerNet Cabling Forms
- Cross-Row Cabling Worksheets
- IOAM Worksheets
- Final Planning Checklist
- Finish Planning
- 14 Planning for CRU Replacement
- 15 Planning for System Configuration
- A Part Numbers
- NonStop S-Series Enclosures
- System Components
- PMF CRUs
- Memory
- IOMF CRUs and Related Components
- SEBs and Related Components
- Doors, Racks, and Related Components
- Visual Image Package
- System Console and Related Components
- Internal Disk Drives
- External Magnetic Disk Drive and Related Components
- Tape Drives
- Tape Libraries
- 5190/94 Tape Drive and Related Components
- 5258 ACL Tabletop Tape Drive and Related Components
- 9840 Fibre Channel Tape Drive and Cables
- Linear Tape Open (LTO) Tape Drive and Related Components
- Loopback Test Equipment
- ServerNet Adapters and Related Components
- ServerNet/DA and Related Components
- CCSA and Related Components
- 6770 ServerNet Cluster and Related Components
- 6780 Switch and Related Components
- AWAN Servers and Related Components
- SWAN Concentrator and Related Components
- SWAN 2 Concentrator and Related Components
- Ethernet Switches and Hubs
- Modems and Modem Cable
- Universal Modem and Its AC Power Cords
- IOAM Products
- Cables and Cable Assemblies
- AC Power Cords, Enclosures Without Power Shelves
- AC Power Cords, Enclosures With Power Shelves
- B Specifications
- C Blank Forms
- D Case Study: ServerNet Cable Lengths
- E Guide to Server Manuals
- Manual Sets
- NonStop SSeries Server Manuals
- Availability Guides
- Adapter Manuals
- Configuration and Management Manuals
- Disk Manuals
- Generic Process Manuals
- Guardian Manuals
- Modular I/O Manuals
- Network Manuals
- SCF Manuals
- ServerNet Cluster Manuals
- Site Planning and Power Manual
- System Management Manual
- System Upgrade
- Tape Manuals
- OSM, TSM, System Console Manuals and Online Help
- Titles and Abstracts
- Manual Sets
- F Supported Hardware and Configurations
- G Modular Power Information
- Safety and Compliance
- Glossary
- Index

Glossary
HP NonStop S-Series Planning and Configuration Guide—523303-015
Glossary-57
link count
link count. In the Open System Services (OSS) file system, the number of directory entries
that refer to a particular file.
linker. (1) The process or server that invokes the message system to deliver a message to
some other process or server. (2) A programming utility, which combines one or more
compilation units’ linkfiles to create an executable loadfile for a native program or
library.
linkfile. (1) For native C/C++ compilers in the Guardian environment, a command file for
input to the
nld or ld utility. (2) A file containing object code that is not yet ready to
load and execute. Linkfiles are combined by means of a linker or binder to make an
executable loadfile for a program or library. Compiling creates one linkfile per
independent source module. Contrast with loadfile
.
linking. The operation of collecting, connecting, and relocating code and data blocks from
one or more separately compiled object files to produce a target object file.
link name. In the Open System Services (OSS) environment, the filename associated with
a specific file within a directory. The length of a filename, and therefore the length of a
link name, depends on the file system.
Linux. Linus Torvald’s version of the UNIX operating system. See also
http://www.linux.org.
listener. The process or server that is notified by the message system that a message from
some other process or server is being delivered.
LIU. See line interface unit (LIU).
LMU. See logical memory unit (LMU).
load. (1) To transfer the HP NonStop™ Kernel operating system image or a program from
disk into a computer’s memory so that the operating system or program can run. (2) To
insert a tape into a tape drive, which prepares it for a tape operation (read or write).
loadable library. A loadfile that offers functions and data to other loadfiles. In this manual,
dynamic-link libraries and hybrid shared run-time libraries are libraries. A library cannot
normally be invoked externally; for example, by a RUN command. Instead, it is invoked
by calls or data references from client loadfiles.
loader. A programming utility that transfers a program into memory so it can run. The
mechanism that brings loadfiles into memory for execution, maps them into virtual
address space, and resolves symbol references among them. Synonyms include
run-time loader and run-time linker. The loader for TNS and for TNS/R native programs
and libraries that are not position-independent code (PIC) is part of the operating
system. For PIC loadfiles, a loader called RLD works with the operating system to load
programs and libraries.