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-103
SUB option
SUB option. In some Subsystem Control Facility (SCF) subsystems, the designation that
the object name given in a command stands not just for itself but for the names of all
objects at the next-lower level in the hierarchy. The given object name can stand both
for itself and for the subordinate objects, or it can stand only for the subordinate
objects, depending on the value of the SUB option.
subordinate objects. In Subsystem Control Facility (SCF), objects that are logically
subordinate to other objects. Some subsystems are structured hierarchically, with
objects of one type logically subordinate to (that is, controlled by) an object of another
type. For example, a number of subdevices can be configured on a single line. Some
SCF commands include a SUB option that refers to subordinate objects.
Subscriber Channel (SC). A type of head on a fiber-optic cable in which the pins connect
through a push-pull mating interface.
substate. Further information about the state of a device. The state and substate together
provide information about the current condition of a device or path to a device.
SUBSYS object type. The Subsystem Control Facility (SCF) object type for most
subsystems that use SCF as the user interface.
subsystem. (1) A secondary or subordinate system, usually capable of operating
independently of or asynchronously with a controlling system. (2) A program or set of
processes that manages a cohesive set of Subsystem Control Facility (SCF) objects.
Each subsystem has a manager through which applications can request services by
issuing commands defined by that subsystem. See also subsystem manager
.
Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and
collecting information from a subsystem and its objects. SCF enables you to configure
and reconfigure devices, processes, and some system variables while your HP
NonStop™ S-series server is online.
Subsystem Control Point (SCP). The message router for Subsystem Control Facility
(SCF). There can be several instances of this process. Using the Subsystem
Programmatic Interface (SPI), applications send each command for a subsystem to an
instance of the SCP process, which in turn sends the command to the manager
process of the target subsystem. SCP also processes a few commands itself. It
provides security features, version compatibility, support for tracing, and support for
applications implemented as process pairs.
subsystem manager. A process that performs configuration and management functions for
a subsystem.
Subsystem Programmatic Interface (SPI). A set of procedures and associated definition
files and a standard message protocol used to define common message-based
interfaces for communication between management applications and subsystems. It
includes procedures to build and decode specially formatted messages; definition files
in Transaction Application Language (TAL), COBOL85, and HP Tandem Advanced
Command Language (TACL) for inclusion in programs, macros, and routines using the