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-49
import library
import library. A file that represents a dynamic-link library (DLL) and can substitute for it as
input to the linker. Import libraries facilitate linking on auxiliary platforms (that is, PCs)
where it is inconvenient to store the actual DLLs.
in-band control (IBC). A symbol-based communications protocol for communicating
management information across a ServerNet link without interfering with any
application traffic in the network. In ServerNet II architecture, IBC traffic uses standard
ServerNet packets. ServerNet I architecture uses the Illegal Symbol variation of IBC,
which uses a subset of the available symbols to convey control information from one
node to another. The symbol subset chosen is from the group of symbols that are not
used for passing data. These symbols are usually considered illegal or unused.
incident report. A report sent by the OSM or TSM server software to the respective OSM
or TSM Notification Director. If remote notification (dial-out) is configured, the
Notification Director forwards incident reports to a service provider. The three types of
incident reports are problem incident reports, periodic incident reports, and software
configuration incident reports.
incremental discovery. Discovery of an HP NonStop™ S-series server when the OSM or
TSM client software has locally saved information but where configuration changes
have been made on the server since that information was saved.
indicator lights. Two light-emitting diodes (LEDs) on a customer-replaceable unit (CRU)
that indicate the status of the unit. The red or amber indicator light is lit when the unit is
not working properly. During startup, this light can indicate that the unit is not yet
functioning. The green indicator light is lit when the unit has proper power applied. See
also light-emitting diode (LED)
.
inductive reactance. Resistance at a frequency that is caused by the inductance of a coil
or circuit.
initial discovery. Discovery of an HP NonStop™ S-series server with which the OSM or
TSM client software has had no prior contact and for which the client software has no
locally saved information.
initialization. The process of defining a new Distributed Systems Management/Software
Configuration Manager (DSM/SCM) target system, including giving it a name, setting
up default values used when processing requests, and creating the first software
revision (list of products) for the system.
initial software revision. The software revision on a target system when it is first brought
into the Distributed Systems Management/Software Configuration Manager
(DSM/SCM) environment. The DSM/SCM host database must be initialized with
information about the initial software revision. The initial software revision is then used
as a baseline upon which new software revisions are based.
inode. A data structure that stores the location of an Open System Services (OSS) file.