NonStop S-Series Hardware Installation and FastPath Guideh20628. · HP NonStop S-Series Hardware Installation and FastPath Guide Abstract This guide is written for anyone qualified

HP NonStop S-Series Hardware Installation and FastPath Guide

Abstract

This guide is written for anyone qualified to install an HP NonStop™ S-series server.

This guide describes how to install and start a NonStop S-series server for the first time. It includes information about installing server hardware, cabling system enclosures, installing and starting NonStop system consoles, installing external system devices, starting the server, and configuring the server after startup. This guide also provides overview information about the I/O adapter module (IOAM) enclosure. A quick reference to installing and configuring a two-processor or four-processor NonStop S-series server in the Tetra 8 topology is included.

Product Version

N.A.

Supported Release Version Updates (RVUs)

This publication supports G06.26 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.

Part Number Published529876-001 April 2005

Document History Part Number Product Version Published527257-001 N.A. September 2003

527809-001 N.A. December 2003

528858-001 N.A. September 2004

529443-001 N.A. December 2004

529876-001 N.A. April 2005


Glossary Index Figures Tables

What’s New in This Guide xixManual Information xixNew and Changed Information xx

About This Guide xxiWho Should Use This Guide xxiWhat’s in This Guide xxiWhere to Get More Information xxiiiNotation Conventions xxv

1. IntroductionInstallation Overview 1-3Standard Operating Practices 1-5

Using ESD Protection 1-6Tools 1-7Installation Checklist 1-8Shipping Packages 1-9

About Shipping Packages 1-9Shipping Package Specifications 1-10

Enclosure Types 1-12Enclosure Contents 1-12Enclosure Combinations 1-12Enclosure Positions 1-13Modified I/O Enclosures 1-13IOAM Enclosures 1-13Enclosure Illustrations 1-16

Groundstraps 1-23What Groundstraps Do 1-23Number of Groundstraps 1-23Where to Install Groundstraps 1-23More About Groundstraps and Power Requirements 1-23

Power-On Cables 1-24

Hewlett-Packard Company—529876-001i

Contents 1. Introduction (continued)

1. Introduction (continued)Emergency Power-Off Cables 1-25

About EPO Cables 1-25EPO Cable Requirements 1-25

System Organization 1-26Group, Module, and Slot Hierarchy for System Enclosures 1-26Group, Module, and Slot Hierarchy for IOAM Enclosures 1-28Server Numbering and Labeling 1-31

ServerNet Cabling 1-36System Size 1-36Topologies 1-37Fabrics and Slots 1-37IOAM Enclosure Cabling 1-38ServerNet Cables 1-38

The System Console 1-45System Consoles 1-45The OSM Product 1-45The TSM Package 1-46Primary and Backup System Consoles 1-47Modems 1-48Preloaded Hardware and Software 1-49Software Connections 1-53

System Startup 1-54Startup and Shutdown Files 1-54System Load Paths 1-54PMF CRU and IOMF CRU Power-On Self-Tests 1-56

2. Installing EnclosuresPrepare to Install New Equipment 2-2

1. Review the Documentation 2-22. Prepare the Work Space 2-33. Organize the Equipment 2-4

Unpack the Enclosures 2-6Tools 2-6Unpack the Enclosures 2-6

Connect the Groundstraps 2-13Inventory the Enclosures 2-16

Slot Assignments for NonStop S-Series Enclosures 2-16Inspect the Components 2-23

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001ii

Contents 3. Cabling Enclosures

3. Cabling Enclosures1. Connect Power-On Cables 3-12. Connect EPO Cables 3-33. Connect ServerNet Cables 3-4

4. Installing Service-Side Doors

5. Installing, Starting, and Testing a System ConsoleUnpacking and Assembling a System Console 5-2

Installation Quick Reference 5-2Finding Documentation 5-2Finding the Quick Setup Reference Card 5-2Unpacking the System Console 5-2Assembling the System Console 5-6

Starting and Testing a System Console 5-8Powering On a System Console 5-8Verifying Readiness 5-9Final Setup Steps 5-9Operational Considerations for OSM and TSM 5-10Connecting Multiple System Consoles 5-11System Console Function Keys 5-12

6. Connecting a System ConsoleThe Dedicated LAN 6-2

Server Connection to a LAN 6-2System Console Connection to a Dedicated Service LAN 6-3System Console Connection to a Secure Operations LAN 6-3Ethernet Cables 6-4Ethernet Switch Ports 6-4

Installing Ferrite Cores 6-4Installing the Ethernet Switch or Hub 6-5

Connect the Ethernet Switch or Hub to the Server 6-5Connect the System Console to the Ethernet Switch or Hub 6-6

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001iii

Contents 7. Installing External System Devices

7. Installing External System DevicesInstalling Tape Drives 7-1

Installing a 5175 Open-Reel Tape Subsystem 7-2Installing a 519x Cartridge Tape Subsystem 7-9Installing Other Tape Devices 7-12Attaching a Tape Drive to the NonStop S-Series Server 7-14

Installing a SWAN or SWAN 2 Concentrator 7-15Installing an AWAN Server 7-15Installing Printers and Terminals 7-16

8. Powering On and Starting the SystemStarting a System for the First Time 8-2

Startup Checklist 8-2Powering On External System Devices 8-3

Powering On the Primary System Console and Modem 8-3Powering On the Tape Subsystem 8-3

Powering On the System 8-6Fault Tolerance and Access to Power Cutoffs 8-6Power-On Procedure Using AC Power Cords 8-6Status LEDs During a Power-On Procedure 8-10Troubleshooting Abnormal LED States 8-12

Verifying Topology and System Components 8-14Starting the System 8-17

Loading the System 8-17Completing the System Load 8-20Verifying the System Is Started 8-20

9. Performing Post-Startup TasksTesting the System 9-1

Check Power Supplies 9-2Check System Enclosure Components 9-2Check Critical System Processes 9-6Check Disk Subsystem Status 9-7Test the Disk Drives 9-8Test the Communications Lines 9-10Check Tape Subsystem Status 9-10Test the Tape Subsystems 9-11

Completing Final Installation Steps 9-12System Configuration Changes and Verifications 9-13

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001iv

Contents 9. Performing Post-Startup Tasks (continued)

9. Performing Post-Startup Tasks (continued)Restarting the Inspect Monitor Process 9-14

Preparing for Daily Operations 9-15Reference Manuals 9-15

Configuring the OSM or TSM Environment 9-16Configuring the OSM Environment 9-16Configuring the TSM Environment 9-16

10. Configuring the SystemSetup Configuration 10-2

Procedure to Create the Setup Configuration 10-2Operating Configuration 10-3

Create the Operating Configuration 10-4Add a System Console to the Operating Configuration 10-7Add a Server to the Operating Configuration 10-9Create a Cascading Ethernet Switch Configuration 10-11Add a System Console to the Cascading Ethernet Switches 10-13Add a Server to the Cascading Ethernet Switches 10-13

Unattended Site Configuration 10-14Create the Unattended Site Configuration 10-15Add a Server to an Unattended Site Configuration 10-15

Nondedicated (Public) LAN Configuration 10-16Construct a Nondedicated (Public) LAN Configuration 10-16

11. Offline Configuration TasksChanges That Must Be Made Offline 11-1Application Reconfiguration 11-2Installing a New RVU 11-2Installing a Product Revision 11-2Changing System Name, System Number, or Time Attributes 11-3Changing the System Topology 11-3Changing the CONFTEXT File 11-3

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001v

Contents 12. Online Configuration Tasks

12. Online Configuration TasksSCF 12-2

Initial CONFIG file 12-2Subsystems in G-Series RVUs 12-3Generic Processes 12-4Making Important Processes Persistent 12-5Types of System Configuration Files 12-6

KMSF 12-8Initial Configuration of KMSF Swap Files 12-8Changing the Configuration of KMSF Swap Files 12-8KMSF and the Operations Environment 12-8

The OSM and TSM Packages 12-9Creating an Alternate System Disk 12-10

1. Choose the Target Disk and Plan Its Space and Files 12-112. Verify That the Target Disk Is Present 12-123. Stop Access to the Target Disk and Display Its Status 12-124. Change the Label of the Target Disk 12-135. Create a New System Volume and a System Image Tape (SIT) 12-146. Install the Boot Millicode on the Target Disk 12-147. Verify the Installation of Boot Millicode on the Target Disk 12-158. Copy Subvolumes to the Target Disk 12-16

Create a Command File 12-17

13. Creating Startup and Shutdown FilesAutomating System Startup and Shutdown 13-2

Startup 13-2Shutdown 13-2For More Information 13-2

Processes That Represent the System Console 13-3$YMIOP.#CLCI 13-3$YMIOP.#CNSL 13-3$ZHOME 13-3$ZHOME Alternative 13-4

Example Command Files 13-5CIIN File 13-6

Establishing a CIIN File 13-6Modifying a CIIN File 13-7If a CIIN File Is Not Specified or Enabled in OSM or TSM 13-7Example CIIN Files 13-8

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001vi

Contents 13. Creating Startup and ShutdownFiles (continued)

13. Creating Startup and Shutdown Files (continued)Tips for Startup Files 13-9How Process Persistence Affects Configuration and Startup 13-9Startup File Examples 13-10

System Startup File 13-10Spooler Warm-Start File 13-12TMF Warm-Start File 13-12TCP/IP Stack Configuration and Startup File 13-12CP6100 Lines Startup File 13-15ATP6100 Lines Startup File 13-15X.25 Lines Startup File 13-15Printer Line Startup File 13-16Expand-Over-IP Line Startup File 13-16Expand Direct-Connect Line Startup File 13-16

Tips for Shutdown Files 13-17Shutdown File Examples 13-17

System Shutdown File 13-18CP6100 Lines Shutdown File 13-19ATP6100 Lines Shutdown File 13-19X.25 Lines Shutdown File 13-19Printer Line Shutdown File 13-20Expand-Over-IP Line Shutdown File 13-20Direct-Connect Line Shutdown File 13-20Spooler Shutdown File 13-21TMF Shutdown File 13-21

Adding Super-Group User IDs 13-21

14. Case Study: Installing and Configuring a SystemAbout These Examples 14-2Background for Developers Inc. 14-3Hardware Configuration 14-4Installation Documents 14-4

Case Study: Installation Document Checklist 14-5Case Study: System Equipment Inventory Form 14-6Case Study: Enclosure Arrangement Diagram 14-7Case Study: Floor Plan 14-8Case Study: Preinstalled I/O Device Cable Checklist 14-9Case Study: Group 01 System Enclosure Checklist 14-10Case Study: Group 01 Slot 50 PMF CRU Configuration Form 14-11

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001vii

Contents 14. Case Study: Installing and Configuring aSystem (continued)

14. Case Study: Installing and Configuring a System (continued)Case Study: Group 01 Slot 55 PMF CRU Configuration Form 14-12Case Study: Group 01 Slot 53 E4SA Configuration Form 14-13Case Study: Group 01 Slot 54 E4SA Configuration Form 14-14Case Study: Group 02 System Enclosure Checklist 14-15Case Study: Group 02 Slot 50 PMF CRU Configuration Form 14-16Case Study: Group 02 Slot 55 PMF CRU Configuration Form 14-17Case Study: Group 02 Slot 53 E4SA Configuration Form 14-18Case Study: Group 02 Slot 54 E4SA Configuration Form 14-19

System Configuration: CONFTEXT File 14-20LAN Environment at Developers Inc. 14-20

Registry of IP Addresses 14-20Installing the System 14-22Customizing the Configuration 14-22

Adding Ethernet 4 ServerNet Adapters (E4SAs) 14-23Adding ConMgr Process 14-24Configuring NonStop TCP/IP Stacks on E4SA Ports 14-25Adding Persistent CLCI TACL, Expand Manager, and SCP Processes 14-27Starting the $ZEXP Expand Manager Process 14-27Adding a SWAN Concentrator 14-28Adding a SWAN 2 Concentrator 14-28Adding CP6100 Lines 14-29Adding an ATP6100 Line 14-30Adding a 5516 Printer 14-31Adding an X.25 Line 14-32Configuring and Starting the $NCP Network Control Process 14-33Adding an Expand-Over-IP Line 14-33Adding a Direct-Connect Line 14-34

A. Part Numbers

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001viii

Contents B. ServerNet Cabling

B. ServerNet Cabling What ServerNet Cabling Diagrams Mean B-2Maximum ServerNet Configurations B-4Maximum ServerNet Cabling Tables B-7

Shaded Areas in These Tables B-7Tetra 8 Cabling Tables B-8Tetra 16 Cabling Tables B-10

Small Tetra 8 Systems B-14About This Information B-14Tetra 8 Systems With One Processor Enclosure B-15Tetra 8 Systems With Two Processor Enclosures B-16Tetra 8 Systems With Three Processor Enclosures B-17Tetra 8 Systems With Four Processor Enclosures B-21

Small Tetra 16 Systems B-25About This Information B-25Tetra 16 Systems With Four Processor Enclosures B-26Tetra 16 Systems With Six Processor Enclosures B-28

C. Power-On Cabling

D. TroubleshootingReference D-2

Power States D-2Status LEDs D-4

Powering On the System D-5System Does Not Appear to Be Powered On D-6Power Is Applied to Enclosure But Fans Are Not Turning D-6Any Green LED Is Not Lit D-8Any Amber LED Remains Lit After POST D-9Yellow ServerNet Port LEDs on SEBs or MSEBs Are Not Lit D-9Group Service LED on System Enclosure Is Flashing D-9Correcting Topology Attribute D-9

Starting the System D-10Startup Event Stream and Startup TACL Windows Do Not Appear D-10System Load Fails D-11CIIN File Is Not Invoked During System Startup D-12Reload Fails D-13CPU Memory Test Fails D-14System Load Path Test Fails D-14

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001ix

Contents D. Troubleshooting (continued)

D. Troubleshooting (continued)Multifunction I/O Board (MFIOB) Test Fails D-15

Dumping Processor Memory D-16Dumping Processor Memory to Disk Online D-16Dumping Processor Memory to Tape Offline D-20

Expand-Over-IP Connections D-22Recovery Actions for the CONNECTING State D-24Recovery Actions for the WAIT State D-24

Backing Out a Software Revision D-26Prerequisites D-261. Start DSM/SCM D-262. Start and Log On to Target Interface D-273. Initiate Backout Activity D-274. Monitor Backout Process D-285. Stop All Applications D-286. Rename Software Files Using ZPHIRNM D-297. Stop System D-298. Load System From Saved Configuration D-309. Start Applications D-30

System Consoles D-31Software Configuration Problems D-36Software Corruption and Hard-Disk Problems D-37Restoring Software on the Hard Disk D-38 Configuring a ProCurve 24-Port Ethernet Switch D-48

E. FastPath Tasks: Required1. Install Hardware E-3

1. Inventory Shipment E-42. Collect Tools E-63. Unpack and Unload Server E-64. Connect Groundstraps E-105. Inventory and Inspect All Components E-116. Connect the Power-On Cables E-117. Connect Emergency Power-Off (EPO) Cables E-138. Connect ServerNet Cables E-149. Install Service-Side Enclosure Doors If Necessary E-1510. Install Primary System Console E-1611. Create Emergency Repair Disk or Automated System Recovery Disk E-1812. Install Ethernet Switch E-18

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001x

Contents E. FastPath Tasks: Required (continued)

E. FastPath Tasks: Required (continued)13. Connect Ethernet Switch to Group 01 E-1814. Connect Primary System Console to Ethernet Switch E-1915. Install Tape Drive E-19

2. Start the System E-221. Prepare for System Startup E-222. Power On External System Devices E-233. Connect AC Power Cords E-244. Apply Power to Server E-265. Verify Topology E-276. Verify System Components E-287. Start System E-28

3. Verify the System E-301. Verify Components E-302. Verify Critical System Processes E-313. Verify Disk Drives E-314. Verify Tape Drive E-325. Verify Firmware E-326. Verify State of the Internal ServerNet Fabric E-32

4. Configure the System E-331. Configure Passwords E-342. Configure Kernel-Managed Swap Files E-353. Configure OSM or TSM Environment E-364. Configure System Attributes E-375. Configure DSM/SCM E-41

5. Install the Backup System Console E-45

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xi

Contents F. FastPath Tasks: Optional

F. FastPath Tasks: Optional1. Prerequisites F-2

1a. Verify Required Configuration Changes F-21b. Review Initial System Configuration F-21c. Start Required Processes F-21d. Save Current System Configuration F-31e. If Your Server Will Be Part of a ServerNet Cluster F-3

2. Customize the System Configuration F-42a. Change SCF F-42b. Rename SCF Objects in the CONFIG File F-52c. Add SCF Objects to the CONFIG File F-6

3. Automate System Startup F-7Modify Provided Startup Files F-7Create Startup Files F-7

4. Automate System Shutdown F-8Tips for Shutdown Files F-8

5. Configure a SWAN or SWAN 2 Concentrator F-9Access the WAN Wizard Pro F-9

6. Configure an Expand-Over-IP Line F-10Prerequisites F-111. On the NonStop S-Series Server F-122. On the NonStop K-Series Server F-163. On the NonStop S-Series Server F-184. On the NonStop K-Series Server F-195. On Either NonStop Server F-21

7. Install Software F-22Configuring Software With DSM/SCM F-23Installing a Software Product Revision (SPR) F-25

Safety and Compliance

Glossary

Index

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xii

Contents Examples

ExamplesExample D-1. SCF STATUS LINE, DETAIL Display D-22Example F-1. SCF LISTDEV TCPIP Display F-13Example F-2. SCF LISTDEV TCP6SAM Display F-14Example F-3. SCF INFO SUBNET Display F-14Example F-4. SCF STATUS PROCESS Display F-15Example F-5. SCF LISTDEV TCPIP Display F-16Example F-6. SCF INFO SUBNET Display F-16Example F-7. SCF STATUS PROCESS Display F-17Example F-8. COUP INFO CONTROLLER Display F-19Example F-9. COUP INFO DEVICE Display F-19

FiguresFigure 1-1. The Shipping Package 1-10Figure 1-2. Shipping Package Dimensions 1-11Figure 1-3. Base and Stackable Enclosures 1-16Figure 1-4. SEBs in a Processor Enclosure Without a Power Shelf 1-17Figure 1-5. MSEBs in a Processor Enclosure With a Power Shelf 1-18Figure 1-6. Service Side of I/O Enclosure Without Power Shelf 1-19Figure 1-7. Service Side of I/O Enclosure With Power Shelf 1-20Figure 1-8. Rack with IOAM Enclosure (Front Side) 1-21Figure 1-9. Rack With IOAM Enclosure (Rear Side) 1-22Figure 1-10. Power-On Cable Connectors 1-24Figure 1-11. EPO Cable 1-25Figure 1-12. Port Numbers and Cable Connections on an MSEB 1-39Figure 1-13. SEB-to-SEB ECL Cable 1-40Figure 1-14. MSEB-to-MSEB ECL Cable 1-40Figure 1-15. SEB-to-MSEB ECL Cable 1-40Figure 1-16. Serial-Copper Cable 1-41Figure 1-17. Fiber-Optic Cable 1-41Figure 1-18. LC Connector for the 6780 Switch or ServerNet Switch Board 1-42Figure 1-19. SC Connector for MSEB 1-42Figure 1-20. ServerNet Cable Labeling 1-43Figure 1-21. Cable-Management Hardware 1-44Figure 1-22. System Load Paths 1-55Figure 2-1. Cords, Cables, and Other Contents of Short Cartons 2-5Figure 2-2. Unpacking the Enclosures 2-7Figure 2-3. Tabs on Plastic Locking Clip of Shipping Package 2-8Figure 2-4. Loosen End Piece of Pallet by Turning Twist-Lock Handles 2-8

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xiii

Contents Figures (continued)

Figures (continued)Figure 2-5. Removing End Piece of Pallet 2-9Figure 2-6. Velcro Strips on Loading Pallet 2-9Figure 2-7. Leveling Pads Must Be Raised Before Enclosure Is Moved 2-10Figure 2-8. Use Two People to Move an Enclosure Stack 2-11Figure 2-9. Lowering Legs of Base Enclosure 2-12Figure 2-10. Groundstrap Connector Locations 2-13Figure 2-11. Groundstrap Connections Between Enclosures 2-14Figure 2-12. Examples of Groundstrap Locations Between Enclosures 2-15Figure 2-13. Appearance Side, Processor Enclosure 2-17Figure 2-14. Service Side: Processor Enclosure Without Power Shelf 2-18Figure 2-15. Service Side: Processor Enclosure With Power Shelf 2-19Figure 2-16. Service Side: I/O Enclosure Without Power Shelf 2-20Figure 2-17. Service Side: I/O Enclosure With Power Shelf 2-21Figure 2-18. Unlocking and Opening an Enclosure Door 2-22Figure 2-19. Reseating a Disk Drive 2-23Figure 2-20. Reseating a PMF CRU or IOMF CRU 2-24Figure 2-21. Reseating a SEB or MSEB 2-25Figure 2-22. Reseating a ServerNet Adapter 2-26Figure 3-1. Connecting and Securing Power-On Cables 3-2Figure 3-2. EPO Connector on a System Enclosure 3-3Figure 3-3. Securing ServerNet Cables With Cable Ties 3-5Figure 4-1. Securing the Frame to the Enclosure Using a Mounting Hole 4-2Figure 4-2. Inserting a Phillips Screw Into the Mounting Hole 4-2Figure 4-3. Tightening a Phillips Screw in a Mounting Hole 4-3Figure 4-4. Service-Side Door Installed on a System Enclosure 4-4Figure 5-1. Setup Configuration 5-11Figure 6-1. Processor Enclosure PMF CRU Ethernet Ports 6-3Figure 6-2. Connections for the Setup Configuration 6-6Figure 7-1. 5175 Tape Subsystem 7-2Figure 7-2. Unloading a Tape Subsystem 7-3Figure 7-3. Removing the Shipping Restraints From a 5175 Tape Subsystem 7-5Figure 7-4. Installing the Top Panel and Corner Caps on a 5175 Tape

Subsystem 7-6Figure 7-5. Connecting a SCSI Cable to a 5175 Tape Subsystem 7-7Figure 7-6. AC Power Switch for 5175 Tape Drive CRU 7-8Figure 7-7. 519x Tape Subsystem 7-9Figure 7-8. Connecting a SCSI Cable to a 519x Tape Subsystem 7-10Figure 8-1. AC Power Switch for 5175 Tape Drive 8-4

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xiv


Figures (continued)Figure 8-2. AC Power Switch for 519x Tape Drive 8-5Figure 8-3. AC Power Cord 8-6Figure 8-4. Connecting an AC Power Cord to an Enclosure With No Power

Shelf 8-7Figure 8-5. Connecting an AC Power Cord to an Enclosure With a Power

Shelf 8-8Figure 8-6. Management Window in OSM or TSM Low-Level Link 8-15Figure 8-7. Verifying the System Topology 8-15Figure 8-8. Entering Information in the System Startup Dialog Box 8-18Figure 8-9. Checking Processor Status 8-21Figure 9-1. Management Window in the OSM Service Connection 9-3Figure 9-2. Management Window in the TSM Service Application 9-4Figure 10-1. Setup Configuration 10-2Figure 10-2. Operating Configuration 10-3Figure 10-3. Connections for the Operating Configuration 10-6Figure 10-4. Operating Configuration With an Added System Console 10-7Figure 10-5. Adding a System Console to the Operating Configuration 10-8Figure 10-6. Operating Configuration With an Added Server 10-9Figure 10-7. Connections for Adding a Server to the Operating Configuration 10-11Figure 10-8. Cascading Ethernet Switch Configuration 10-12Figure 10-9. Connecting Cascading Ethernet Switches 10-13Figure 10-10. Unattended Site Configuration 10-14Figure 10-11. LAN Configurations: Nondedicated (Public) and Dedicated 10-17Figure 12-1. Subsystems in G-Series RVUs 12-3Figure 12-2. Differences Among System Configuration Files 12-7Figure B-1. Correlation Between ServerNet Cable Diagram and One

Enclosure B-2Figure B-2. Correlation Between ServerNet Cable Diagram and Two

Enclosures B-3Figure B-3. Maximum Tetra 8 Topologies, X and Y Fabrics B-4Figure B-4. Maximum Tetra 16 Topology, X Fabric B-5Figure B-5. Maximum Tetra 16 Topology, Y Fabric B-6Figure B-6. Tetra 8 Cabling: Two Processor Enclosures, Two I/O Enclosures B-17Figure B-7. Tetra 8 Cabling: Three Processor Enclosures, Six I/O Enclosures B-20Figure B-8. Tetra 16 Cabling: Four Processor Enclosures, X Fabric B-26Figure B-9. Tetra 16 Cabling: Four Processor Enclosures, Y Fabric B-27Figure B-10. Tetra 16 Cabling: Six Processor Enclosures, X Fabric B-28Figure B-11. Tetra 16 Cabling: Six Processor Enclosures, Y Fabric B-29

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xv


Figures (continued)Figure C-1. Power-On Cabling: Single-High Stacks C-2Figure C-2. Power-On Cabling: Mixed Single-High and Double-High Stacks C-3Figure C-3. Power-On Cabling: Multiple-Row Systems C-4Figure C-4. Power-On Cable: One Processor Enclosure C-5Figure C-5. Power-On Cables: One Processor Enclosure, One I/O Enclosure C-5Figure C-6. Power-On Cables: One Processor Enclosure, Two I/O Enclosures C-5Figure C-7. Power-On Cables: Two Processor Enclosures, No I/O Enclosures C-6Figure C-8. Power-On Cables: Two Processor Enclosures, One I/O Enclosure C-6Figure C-9. Power-On Cables: Two Processor Enclosures, Two I/O

Enclosures C-6Figure C-10. Power-On Cables: Three Processor Enclosures, No I/O

Enclosures C-7Figure C-11. Power-On Cables: Three Processor Enclosures, One I/O

Enclosure C-7Figure C-12. Power-On Cables: Three Processor Enclosures, Two I/O

Enclosures C-7Figure C-13. Power-On Cables: Three Processor Enclosures, Three I/O

Enclosures C-8Figure C-14. Power-On Cables: Four Processor Enclosures, No I/O Enclosures C-8Figure C-15. Power-On Cables: Four Processor Enclosures, One I/O Enclosure C-8Figure C-16. Power-On Cables: Four Processor Enclosures, Two I/O

Enclosures C-8Figure C-17. Power-On Cables: Four Processor Enclosures, Three I/O

Enclosures C-9Figure C-18. Power-On Cables: Four Processor Enclosures, Four I/O

Enclosures C-9Figure E-1. Packaging of Enclosure Stack E-6Figure E-2. Velcro Strips on Loading Pallet E-8Figure E-3. Rolling the Stack to the Installation Area E-9Figure E-4. Enclosure Stacks in Final Positions E-9Figure E-5. Lowering Legs of Base Enclosure E-9Figure E-6. Groundstrap Connector Locations E-10Figure E-7. Power-On Cable Connectors E-11Figure E-8. Power-On Cables: One Processor Enclosure E-11Figure E-9. Power-On Cables: One Processor Enclosure, One I/O Enclosure E-11Figure E-10. Power-On Cables: One Processor Enclosure, Two I/O

Enclosures E-12Figure E-11. Power-On Cables: Two Processor Enclosures E-12

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xvi


Figures (continued)Figure E-12. Power-On Cables: Two Processor Enclosures, One I/O

Enclosure E-12Figure E-13. Power-On Cables: Two Processor Enclosures, Two I/O

Enclosures E-12Figure E-14. EPO Cable E-13Figure E-15. Connecting an Ethernet Switch to Group 01 E-18Figure E-16. Attaching SCSI Cable to PMF CRU E-20Figure E-17. Adding a System Console to the Operating Configuration E-46

TablesTable 1-1. Weights for Enclosure Shipping Packages 1-10Table 1-2. Maximum Processor and I/O or IOAM Enclosure Connections 1-31Table 1-3. Maximum Numbers of Enclosures for G06.03 and Later RVUs 1-36Table 1-4. ServerNet Cable Compatibilities With Components 1-38Table 1-5. Preloaded HP NonStop System Console Software (page 1 of 2) 1-49Table 1-6. Preconfigured IP Addresses for a NonStop S-Series Server 1-51Table 1-7. System Load Paths in Order of Use 1-54Table 2-1. Illustrations of Enclosures Including Slot Numbers 2-16Table 2-2. Slot Assignments: Tetra 8 Topology 2-16Table 2-3. Slot Assignments: Tetra 16 Topology 2-17Table 5-1. Contents of the Shipping Box 5-3Table 7-1. 517x Firmware Requirements 7-2Table 8-1. Status LEDs and Their Functions 8-10Table 8-2. Troubleshooting Abnormal LED States 8-12Table 8-3. Checking the Attributes of Selected System Components 8-16Table 9-1. System Configuration Changes and Verifications 9-13Table B-1. Maximum Tetra 8 ServerNet Cabling, Processor Enclosures B-8Table B-2. Maximum Tetra 8 ServerNet Cabling, I/O Enclosures B-9Table B-3. Maximum Tetra 16 ServerNet Cabling, Processor Enclosures B-10Table B-4. Maximum Tetra 16 ServerNet Cabling, I/O Enclosures B-11Table B-5. Tetra 8 Cabling: One Processor Enclosure, One I/O Enclosure B-15Table B-6. Tetra 8 Cabling: One Processor Enclosure, Two I/O Enclosures B-15Table B-7. Tetra 8 Cabling: Two Processor Enclosures, No I/O Enclosures B-16Table B-8. Tetra 8 Cabling: Two Processor Enclosures, One I/O Enclosure B-16Table B-9. Tetra 8 Cabling: Two Processor Enclosures, Two I/O Enclosures B-16Table B-10. Tetra 8 Cabling: Three Processor Enclosures, No I/O Enclosures B-17Table B-11. Tetra 8 Cabling: Three Processor Enclosures, One I/O Enclosure B-17

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xvii

Contents Tables (continued)

Tables (continued)Table B-12. Tetra 8 Cabling: Three Processor Enclosures, Two I/O

Enclosures B-18Table B-13. Tetra 8 Cabling: Three Processor Enclosures, Three I/O

Enclosures B-18Table B-14. Tetra 8 Cabling: Four Processor Enclosures, No I/O Enclosures B-21Table B-15. Tetra 8 Cabling: Four Processor Enclosures, One I/O Enclosure B-21Table B-16. Tetra 8 Cabling: Four Processor Enclosures, Two I/O Enclosures B-22Table B-17. Tetra 8 Cabling: Four Processor Enclosures, Three I/O

Enclosures B-22Table B-18. Tetra 8 Cabling: Four Processor Enclosures, Four I/O Enclosures B-23Table D-1. Troubleshooting the Expand Connection Procedure D-22Table D-2. Keyboard Is Inoperative D-32Table D-3. Mouse Is Inoperative D-33Table D-4. Monitor Screen Is Blank D-34Table D-5. System Unit Is Inoperative D-35Table D-6. Monitor Screen Is Frozen D-36Table D-7. Application Fails Immediately When Started D-37Table D-8. Install Windows XP Professional Operating System D-39Table D-9. Set Up Date and Time D-43Table D-10. Set Event Log Settings D-44Table D-11. Install Internet Explorer D-46Table E-1. ServerNet Cables for One Processor Enclosure, One I/O

Enclosure E-14Table E-2. ServerNet Cables for Two Processor Enclosures, No I/O

Enclosures E-14Table E-3. ServerNet Cables for Two Processor Enclosures, One I/O

Enclosure E-14Table E-4. ServerNet Cables for Two Processor Enclosures, Two I/O

Enclosures E-15Table F-1. SCF ADD DEVICE Command Worksheet F-18Table F-2. COUP Worksheet F-20

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xviii

What’s New in This GuideManual Information


Abstract

This guide is written for anyone qualified to install an HP NonStop™ S-series server.

This guide describes how to install and start a NonStop S-series server for the first time. It includes information about installing server hardware, cabling system enclosures, installing and starting NonStop system consoles, installing external system devices, starting the server, and configuring the server after startup. This guide also provides overview information about the I/O adapter module (IOAM) enclosure. A quick reference to installing and configuring a two-processor or four-processor NonStop S-series server in the Tetra 8 topology is included.

Product Version

N.A.

Supported Release Version Updates (RVUs)

This publication supports G06.26 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.

Document History

Part Number Published529876-001 April 2005

Part Number Product Version Published527257-001 N.A. September 2003

527809-001 N.A. December 2003

528858-001 N.A. September 2004

529443-001 N.A. December 2004

529876-001 N.A. April 2005

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xix

What’s New in This Guide New and Changed Information

New and Changed InformationThis publication has been updated to include information about the 4638 and 46144 internal disk drives.

Section Title ChangesManual-wide Editorial corrections.

About This Guide

1 Introduction Corrected topology information in Maximum Numbers of Enclosures for G06.03 and Later RVUs on page 1-36.

Updated information about ISEE for NonStop in Modems on page 1-48.


Updated for G06.26 RVU.

Glossary Updated for G06.26 RVU. Includes descriptions for of new 4638 and 46144 internal disk drives.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xx

About This GuideThis guide describes how to install and bring up a NonStop S-series server for the first time. It includes information about installing the server hardware, cabling system enclosures, installing and starting system consoles, installing external system devices, and starting the server. This guide is written for anyone who is qualified to install a NonStop S-series server.

This guide assumes that you are using the HP NonStop Open System Management (OSM) or Compaq TSM software to perform the OSM or TSM tasks described in this guide.

Who Should Use This GuideThis guide is written for anyone who installs system equipment at a customer site. You should be familiar with computers but does not need to be familiar with installing mainframe computer systems. However, those who perform the hardware tasks documented in this guide must have completed training courses on system support for NonStop S-series servers.

What’s in This Guide

Note. Throughout this guide, the term Sxx000 stands for NonStop S70000, S72000, S74000, S76000, S78000, S86000, S88000 servers.

Information in this guide also applies to NonStop S7x00 servers of model S7400 and higher.

Section Title Contents (page 1 of 2)

1 Introduction This section summarizes the installation process and gives an overview of the NonStop S-series system.

2 Installing Enclosures This section describes how to unpack new equipment and install NonStop system enclosures.

3 Cabling Enclosures This section explains how to cable enclosures in NonStop S-series systems with power-on, emergency power-off (EPO), and ServerNet cables.

4 Installing Service-Side Doors

This section describes how to install optional service-side doors on NonStop S-series system enclosures that are already installed and cabled. (New NonStop S-series system enclosures are shipped with service-side doors installed.)

5 Installing, Starting, and Testing a System Console

This section describes how to unpack, assemble, start, and test a system console.

6 Connecting a System Console

This section describes how to connect a primary system console to the installed server and dedicated LAN by using Ethernet cables and an Ethernet switch or Ethernet hub.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xxi

About This Guide What’s in This Guide

7 Installing External System Devices

This section describes how to install selected peripheral devices such as tape subsystems.

8 Powering On and Starting the System

This section describes how to power on NonStop S-series system enclosures, how to power on external devices, and how to start the system.

9 Performing Post-Startup Tasks

This section describes the tasks that you must perform after the NonStop S-series server has been powered up and started.

10 Configuring the System This section describes how to configure system consoles and NonStop S-series servers in several ways.

11 Offline Configuration Tasks

This section describes offline configuration tasks, which change software or hardware configurations and require the system to be shut down.

12 Online Configuration Tasks

This section describes how to configure your system online using the Subsystem Control Facility (SCF), Kernel-Managed Swap Facility (KMSF), OSM, and TSM, and how to create an alternate $SYSTEM disk.

13 Creating Startup and Shutdown Files

This section describes command files that automatically start and shut down a NonStop S-series server.

14 Case Study: Installing and Configuring a System

This section documents the installation and configuration of a NonStop S7000 system for a fictitious company.

A Part Numbers Part numbers have been moved to the CSSI Web.

B ServerNet Cabling This appendix contains ServerNet cabling diagrams and tables for maximum Tetra 8 and Tetra 16 configurations. It also contains diagrams and tables for selected smaller configurations.

C Power-On Cabling This section provides power-on cabling diagrams for selected large and smaller ServerNet configurations.

D Troubleshooting This appendix explains basic recovery tasks for the system and system console.

E FastPath Tasks: Required This appendix contains all the tasks required to install, start, and configure a two-processor or four-processor NonStop S-series server in the Tetra 8 topology.

F FastPath Tasks: Optional This appendix contains all optional configuration tasks for a two-processor or four-processor NonStop S-series server in the Tetra 8 topology.

Glossary The Glossary lists terms and abbreviations used in this text.

Section Title Contents (page 2 of 2)

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xxii

About This Guide Where to Get More Information

Where to Get More InformationDocumentation

Manuals, Hotstuff messages, and other kinds of documentation are available in the NonStop Technical Library (NTL) at http://techlibrary.cac.cpqcorp.net.ntl/.

For abstracts of the NonStop S-series manuals, see the NonStop S-Series Planning and Configuration Guide.

CSSI WebThe CSSI Web provides procedures, part numbers, troubleshooting tips, and tools for servicing NonStop S-series systems.

A link to the CSSI Web can be found in the left navigation area of the NTL home page.

Authorized service providers can also order the CSSI Web and HSM CD:

• Channel Partners and Authorized Service Providers: Order the CD from the SDRC at https://scout.nonstop.compaq.com/SDRC/ce.htm.

• HP employees: Subscribe at World on a Workbench (WOW). Subscribers automatically receive CD updates. Access the WOW order form at http://hiimpact.americas.cpqcorp.net/wow/order.asp.

OSM Guided Replacement ProceduresSome of the procedures in this guide refer to the OSM guided replacement procedures. These automated tools are integrated into the OSM Service Connection. They guide you step-by-step through replacing many customer-replaceable units (CRUs).

To launch OSM guided replacement procedures:

1. Log on to the OSM Service Connection.

2. In the tree pane, locate the CRU you want to replace.

3. Select the CRU.

4. Select Actions.

5. In the Actions dialog box, from the Available Actions list, select Replace.

6. Click Perform Action to launch the guided procedure.

Note. After G06.23, a snapshot of the CSSI Web is no longer included on the system console installer CD.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xxiii

About This Guide TSM Guided Replacement Procedures

TSM Guided Replacement ProceduresTSM guided replacements procedures are launched by the Windows Start menu (rather than integrated into the application).

To access the TSM guided replacement procedures:

Start > Programs > Compaq TSM > Guided Replacement Tools

These guided replacement procedures are currently available:

• Replace IOMF• Replace PMF • Replace Power Supply• Replace SEB or MSEB• Replace SNDA• Replace Switch Component• Guided Replacement Toolkit (GRT)

Note. The GRT is used to replace an IOMF, PMF, power supply, or 6760 ServerNet device adapter (ServerNet/DA) in a system running TSM server T7945AAW (shipped with the G06.12 RVU) or earlier.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xxiv

About This Guide Notation Conventions

Notation ConventionsHypertext Links

Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example:

This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2.

General Syntax NotationThis list summarizes the notation conventions for syntax presentation in this manual.

UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example:

MAXATTACH

lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example:

file-name

computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example:

myfile.c

italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example:

pathname

Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example:

error := NEXTFILENAME ( file-name ) ;

LISTOPENS SU $process-name.#su-name

Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example:

"[" repetition-constant-list "]"

Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example:

CALL STEPMOM ( process-id ) ;

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xxv

About This Guide Notation for Messages

If there is no space between two items, spaces are not permitted. In this example, there are no spaces permitted between the period and any other items:

$process-name.#su-name

Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example:

ALTER [ / OUT file-spec / ] LINE

[ , attribute-spec ]…

Notation for MessagesThis list summarizes the notation conventions for the presentation of displayed messages in this manual.

Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example:

Backup Up.

lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example:

p-register

process-name

Change Bar NotationChange bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example:

The message types specified in the REPORT clause are different in the COBOL environment and the Common Run-Time Environment (CRE).

The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001xxvi

1 IntroductionThis section summarizes the installation process and gives an overview of the NonStop S-series system.

Topic Page (page 2 of 2)

Installation Overview 1-3

Standard Operating Practices 1-5

Using ESD Protection 1-6

Tools 1-7

Installation Checklist 1-8

Shipping Packages 1-9

About Shipping Packages 1-9

Shipping Package Specifications 1-10

Enclosure Types 1-12

Enclosure Contents 1-12

Enclosure Combinations 1-12

Enclosure Positions 1-13

Modified I/O Enclosures 1-13

IOAM Enclosures 1-13

Enclosure Illustrations 1-16

Groundstraps 1-23

What Groundstraps Do 1-23

Number of Groundstraps 1-23

Where to Install Groundstraps 1-23

More About Groundstraps and Power Requirements 1-23

Power-On Cables 1-24

Emergency Power-Off Cables 1-25

About EPO Cables 1-25

EPO Cable Requirements 1-25

System Organization 1-25

Group, Module, and Slot Hierarchy for System Enclosures 1-26

Group, Module, and Slot Hierarchy for IOAM Enclosures 1-28

Server Numbering and Labeling 1-31

ServerNet Cabling 1-36

System Size 1-36

Topologies 1-37

Fabrics and Slots 1-37

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-0011-1

Introduction Installation Overview

IOAM Enclosure Cabling 1-38

ServerNet Cables 1-38

The System Console 1-45

System Consoles 1-45

The OSM Product 1-45

Primary and Backup System Consoles 1-47


Modems 1-48

Preloaded Hardware and Software 1-49

Software Connections 1-53

System Startup 1-54

Startup and Shutdown Files 1-54

System Load Paths 1-54

PMF CRU and IOMF CRU Power-On Self-Tests 1-56




Installation Overview Step Documentation Notes (page 1 of 2)

1. Decide which installation process to use.

This guide Use if you are:

• Installing a NonStop S-series server for the first time

OR

• Installing a Tetra 16 system

Appendix E, FastPath Tasks: Required

Appendix F, FastPath Tasks: Optional

Use if you are BOTH:

• Familiar with installing NonStop S-series servers

AND

• Installing a Tetra 8 system

2. Plan the installation of the server, system console, local area network (LAN) subsystem, and wide area network (WAN) subsystem.

Section 2, Installing Enclosures

NonStop S-Series Planning and Configuration Guide

G06.nn Release Version Update Compendium

LAN Configuration and Management Manual

TSM Configuration Guide

OSM Migration Guide

WAN Subsystem Configuration and Management Manual

Each server is shipped with a customized version of the operating system image already installed. This operating system image comes preconfigured with ServerNet adapters and essential system devices such as disk and tape subsystems.

3. Install the server.


Section 3, Cabling Enclosures

Section 4, Installing Service-Side Doors

4. Install an I/O adapter module (IOAM) enclosure.

Caution: IOAM enclosures must be installed by service providers trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

For connection to other storage options, you can install IOAM enclosures. Each IOAM enclosure is mounted into a standard 19-inch rack and connects to the MSEB of S76000 and later NonStop S-series systems. Each IOAM enclosure provides space for up to 10 specially designed ServerNet adapters.

5. Install the primary system console.



Section 5, Installing, Starting, and Testing a System Console

Section 6, Connecting a System Console

The primary system console has a modem and is configured as a dial-out point. You must install and configure this system console before you can view manuals, start and test the system, configure the OSM or TSM environment, or use the OSM or TSM software.

Do not install the backup system console until you have started and tested the server.

6. Install external system devices such as 517x and 519x tape subsystems:

Section 7, Installing External System Devices

7. Power on and start the server with the factory-default configuration.

Section 8, Powering On and Starting the System

8. Perform post-startup tasks such as testing system components and configuring the OSM or TSM environment.

Section 9, Performing Post-Startup Tasks You might also need:

• SCF Reference Manual for the Storage Subsystem

• OSM User’s Guide

• TSM Configuration Guide

• TSM Online User Guide

Step Documentation Notes (page 1 of 2)



Standard Operating PracticesWhen you handle a customer-replaceable unit (CRU), follow standard operating practices to minimize any potential damage to the equipment:

• When handling CRUs, work in an environment protected from electrostatic discharge (ESD). See Using ESD Protection on page 1-6.

• Obtain an ESD protection kit and follow the directions that come with the kit. You can purchase ESD kits from HP using the part number given in the CSSI Web. See CSSI Web on page xxiii.

• Make sure any ESD wriststrap has a built-in series resistor and includes an antistatic table mat.

• Before unpacking CRUs, place the packing container on an antistatic table mat.

• CRUs that require ESD protection are shipped in ESD protective bags. When opening packing containers for these CRUs, do not cut the ESD protective bag.

• Before moving a CRU from an antistatic table mat, attach the grounding clip from your ESD wriststrap to any exposed unpainted metal surface on the CRU frame.

• Before you bring the CRU in contact with the system enclosure, attach the grounding clip to any exposed unpainted metal surface on the enclosure frame.

• When removing a CRU from an enclosure, once you have pulled the CRU partway out of the slot, attach the grounding clip from your ESD wriststrap to any exposed unpainted metal surface on the CRU frame.

• Before setting a CRU on an antistatic table mat, attach the grounding clip from your ESD wriststrap to the antistatic table mat.

• Store CRUs that require ESD protection in ESD protective bags.

• Install or upgrade only hardware components that are designated customer-replaceable units (CRUs) and for which this guide includes installation procedures.

• Before any installation procedure, inspect the CRU. Check connectors for bent or broken pins and look for any other obvious damage.

• When installing a CRU that is located on the appearance side of the enclosure, work quickly to minimize the amount of time that the enclosure door is left open.

• Before working with electrical equipment, remove all metal accessories, such as rings, watches, and necklaces, that can damage the equipment.

• Before working with electromechanical equipment, restrain items such as long hair and sleeves that can get caught in the equipment.



Using ESD Protection

VST693.vsd

ESD antistatic table mat.Connect to soft ground(1 megohm min to 10megohm max)

ESD floor mat

Clip 15-foot straightground cord to screw ongrounded outlet cover.

ESD wriststrap clipped to door latch stud

System Enclosure (Appearance Side)

ESD floor mat



ToolsThe tools you might need when installing server components include:

Component Tool PurposeSystem enclosure

ESD protection kit Protect components against electrostatic discharge

Heavy-freight-handling equipment

Move shipping pallets to installation area

Safety glasses Prevent eye injury from flying particles

Scissors or cutters Clip cable ties and cut banding straps

Flashlight For lighting dark areas

Labels Pens or pencils

Label cables

3/4-inch (19-mm) or 9/16-inch (15-mm) open-end wrench

Lower system enclosure leveling pads (might have 3/4-inch nuts or 9/16-inch nuts)

Phillips screwdriver Loosen and tighten Phillips screws, including groundstrap screws

Stubby Phillips screwdriver

Loosen and tighten AC power cord retainer screws on some processor and I/O enclosures without power shelves

4-mm diagonal wrench(provided with server)

Unlock enclosure door

Tape subsystem

15/16-inch (24-mm) or adjustable, open-end wrench

Lower leveling pads on 5175 or 519x tape subsystem enclosures

Slotted screwdriver Loosen and tighten slotted-head screws, including those on 5175 tape subsystem shipping restraints



Installation Checklist Task See...Prepare to install new equipment.

Unpack the enclosures.

Connect the groundstraps.

Inventory the enclosures.

Inspect the CRUs.


Connect the power-on cables.

Connect the emergency power-off (EPO) cables.

Connect the ServerNet cables.

Section 3, Cabling Enclosures

Install service-side doors on system enclosures (optional).

Section 4, Installing Service-Side Doors

Unpack and assemble the system console.

Start and test the system console.


Connect the system console to the system. Section 6, Connecting a System Console

Install external system devices. Section 7, Installing External System Devices

Prepare for system startup.

Power on external system devices.

Power on the system.

Start the system.

Section 8, Powering On and Starting the System

Test the system.

Complete final installation tasks.

Prepare for daily operations.

Configure the OSM or TSM environment.

Section 9, Performing Post-Startup Tasks

Create the operating configuration. Section 10, Configuring the System



Shipping Packages Each enclosure or stack of enclosures is shipped in a shipping package.

About Shipping PackagesThe shipping package consists of protective cardboard panels on the top and sides of the enclosure, secured with nylon banding straps that are 1.5 inches (3.75 mm) wide.

Equipment is included in your shipment so that you can unload the shipping packages as follows:

• Wooden pallets

Each shipping package comes equipped with a wooden pallet as shown in Figure 1-1, The Shipping Package. This pallet includes skids spaced for forklift handling.

• The unloading ramp

° The ramp allows you to unload the enclosure from the pallet without a forklift.

° Only one unloading ramp is included in the shipment, regardless of the number of enclosures shipped.

° The ramp is attached to one shipping package with banding straps as shown in Figure 1-1, The Shipping Package.

Note. For information about shipping packages for IOAM enclosures, including package specifications and unpacking instructions, contact your HP trained service provider who can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library.



Shipping Package Specifications

Figure 1-1. The Shipping Package

Table 1-1. Weights for Enclosure Shipping PackagesNonStop S-Series Enclosure Type Single-High Stack Double-High Stack

Pounds Kilograms Pounds KilogramsS7000 processor enclosure without power shelf

290 132 580 264

S7x00 and Sxx000 processor enclosure with power shelf

367 167 734 337

I/O enclosure without power shelf 290 132 580 264

I/O enclosure with power shelf 367 167 734 334

Note. For information about shipping package specifications for IOAM enclosures, contact your HP trained service provider who can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library.

VST963.vsd

Single-High Stack Double-High Stack

Banding Straps

Unloading Ramp

Pallet



Figure 1-2. Shipping Package Dimensions

VST990.vsd

Double-High Stack

77.0 in195.6 cm

Single-High Stack

43.0 in109.2 cm

41.6 in105.7 cm

28.8 in73.0 cm



Enclosure TypesEnclosures can be described by their contents, how they are combined, their positioning, how they have been modified, and how they are mounted.

Enclosure Contents

Enclosure Combinations

For more about blocks, see the NonStop S-Series System Expansion and Reduction Guide.

Term DefinitionSystem enclosure An enclosure for system components. Processor enclosures and I/O

enclosures are both system enclosures.

Processor enclosure

A system enclosure that contains, among other units, two processor multifunction (PMF) customer-replaceable units (CRUs).

I/O enclosure A system enclosure that contains, among other units, two I/O multifunction (IOMF) CRUs. I/O enclosures connect to a SEB or MSEB in the processor enclosure.

I/O adapter module (IOAM) enclosure

An enclosure that contains up to 10 specially designed ServerNet adapters. Unlike self-contained system enclosures, IOAM enclosures reside in standard 19-inch racks. IOAM enclosures connect to an MSEB in the processor enclosure. I/O enclosures and IOAM enclosures can coexist in the same system. For information about what group numbers support IOAM enclosures, see Table 1-2.

Caution. IOAM enclosures must be installed by service providers trained by HP.

Term DefinitionBlock A grouping of one or more system enclosures that a NonStop

S-series system recognizes and supports as one unit. A block can be:• One processor enclosure• One I/O enclosure• One processor enclosure attached to one or more I/O enclosures

or IOAM enclosures. Note that IOAM enclosures are not standalone enclosures; they are mounted into standard 19-inch racks.



Enclosure PositionsSystem enclosures can be arranged in single-high stacks (one enclosure) or double-high stacks (two enclosures, one on top of the other):

If you will reduce your system at any point in the future, place enclosures that you might remove from your system on the top of the stack.

Modified I/O EnclosuresI/O enclosures shipped with the G06.13 RVU or earlier require removal of a pin from their backplanes to ensure system fault tolerance. If you do not know when your I/O enclosure was manufactured, contact your service provider.

For information about the removal procedure and the possibilities for later use of a modified enclosure, see the NonStop S-Series Planning and Configuration Guide.

IOAM EnclosuresAn IOAM enclosure provides you with access to additional disk storage. An IOAM enclosure is mounted into a modular cabinet and connects to the MSEB of S76000 and later NonStop S-series systems. Up to three IOAM enclosures, one maintenance switch, two PDUs, and one UPS can be installed into one cabinet. IOAM enclosures can be installed in any standard 19-inch rack, but the number of enclosures depends on the height of the rack.

IOAM Enclosure ComponentsAn IOAM enclosure (chassis) contains two midplanes:

• I/O midplane for routing ServerNet signals

• Power midplane for routing power and signals for the power-supply controls

These components are installed in an IOAM enclosure:

• Two ServerNet switch boards for routing ServerNet packages from the MSEB to the ServerNet adapters. The ServerNet switch board enables communication between a NonStop S-series system and an IOAM.

• Up to 10 specially designed ServerNet adapters. These adapters include:

Term DefinitionBase enclosure A system enclosure that can be placed on the floor with another

enclosure on top of it.

Stackable enclosure A system enclosure that can rest on top of another system enclosure.

Caution. IOAM enclosures must be installed by service providers trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.



• Fibre Channel ServerNet adapters (FCSA). FCSAs provide access to Fibre Channel storage devices, such as an Enterprise Storage System (ESS).

• Gigabit Ethernet 4-Port ServerNet adapters (G4SA). G4SAs provide increased Ethernet capacity. An IOAM enclosure that has 10 G4SAs provides up to 40 ports of Ethernet connections.

• Four fans for cooling components inside an IOAM enclosure

• Four power supplies with universal AC input to provide power to the components in an IOAM enclosure

• One bezel

• Two cable-management systems for managing the fiber-optic cables at the module level and at the modular cabinet level when it is installed on the modular cabinet

Related ComponentsThese components are used in conjunction with IOAM enclosures:

• Maintenance switch

The maintenance switch connects the OSM console to the Maintenance Entity in the ServerNet switch board and provides the communication between the IOAM enclosure and the OSM console. The maintenance switch can be mounted in a standard 19-inch rack.

• Modular cabinet

A modular cabinet is a 19”, 42 U high, industry standard rack and is used for mounting modular components. It houses the IOAM enclosure, uninterruptible power supplies (UPS), Extended Run Time Modules, and maintenance switches. The modular cabinet comes equipped with doors, power distribution units (PDUs), and side panels as needed.

• Power distribution unit (PDU)

The PDU supports additional power outlets for the components in the rack. The PDU is installed onto a rack extender frame attached to the modular cabinet. See Figure 1-9. For an IOAM enclosure, each IOAM power supply plugs into a different PDU.

Note. For more information about G4SAs, FCSAs, or the Enterprise Storage System (ESS), contact your service provider trained by HP.

For FCSA information, your service provider can refer to the Fibre Channel ServerNet Adapter (FCSA) Installation and Support Guide.

For G4SA information, your service provider can refer to the Gigabit Ethernet 4-Port Adapter Installation and Support Guide.

For ESS information, your service provider refer to the Modular I/O Installation and Configuration Guide.



• Uninterruptible power supply (UPS)

For IOAM enclosures, a UPS is optional but recommended where a site UPS is not available. You can choose to use any UPS that meets the IOAM enclosure power requirements for all enclosures being powered on from the UPS. One UPS option to support the IOAM enclosure is the HP R5500 UPS. You can also choose to have the UPS pre-installed inside the Modular Cabinet. See Figure 1-9.

The standard configuration for cabinets that have an R5500 XR UPS includes one Extended Runtime Module (ERM). Each Extended Runtime Module is a rack-mountable battery module that extends your overall battery runtime.

For power and environmental requirements for the R5500 UPS, and all planning, installation, and emergency power-off (EPO) instructions, refer to the documentation shipped with the UPS.



Enclosure Illustrations

Figure 1-3. Base and Stackable Enclosures

WARNING. Do not attempt to lift a stackable enclosure onto the top of a base enclosure by yourself. A trained service provider and at least four assistants must perform this procedure.

Base Enclosure(Appearance Side)

Stackable Enclosure Installedon Base Enclosure(Appearance Side)

VST547.vsd



Figure 1-4. SEBs in a Processor Enclosure Without a Power Shelf

50 55

51 52 53 54

56

Y-Fabric SEB

X-Fabric SEB

VST581.vsd



.

Figure 1-5. MSEBs in a Processor Enclosure With a Power Shelf

50 55

51 52 53 54

56

X-Fabric MSEB

Y-Fabric MSEB

VST969.vsd



Figure 1-6. Service Side of I/O Enclosure Without Power Shelf

VST970.vsd

To X Fabric To Y Fabric

50 55

51 52 53 54

56

Slot Component50, 55 IOMF CRU51, 52, 53, 54 SEB or MSEB56 EPO connector



Figure 1-7 illustrates the service side of an I/O enclosure that has a power shelf. The power shelf has two DC power supplies that furnish power to the IOMF 2 CRUs in slots 50 and 55.

The IOMF 2 CRU offers more connectivity options than the IOMF CRU. On the IOMF 2 CRU, the external SCSI port accepts the SCSI SAC used on PMF 2 and ServerNet/DAs for connecting tape devices. The ServerNet port accepts serial-copper and single-mode fiber-optic cables in addition to ECL cables.

Figure 1-7. Service Side of I/O Enclosure With Power Shelf

VST972.vsd

55

51 52 53 54

56

50

DC Power Cable (1 of 2)

50 55

To Y Fabric

Power Shelf

Slot Component50, 55 IOMF 2 CRU51, 52, 53, 54 SEB or MSEB56 EPO connector

To X Fabric

SCSI Port



Figure 1-8. Rack with IOAM Enclosure (Front Side)

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

23

24

25

26

27

18

19

20

21

22

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

23

24

25

26

27

18

19

20

21

22

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

VST010.vsd

IOAM Enclosure

Power Supplies

Fans

Uninterruptible Power Supply (UPS)

Extended Run-time Module (ERM)



Figure 1-9. Rack With IOAM Enclosure (Rear Side)

VST197A.vsd

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

23

24

25

26

27

18

19

20

21

22

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

Maintenance Switch

PowerDistributionUnit (PDU)

Uninterruptible PowerSupply (UPS)

To AC Power Source

PDUJunction Box

Extended Run-TimeModule (ERM)

IOAM Enclosure

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

23

24

25

26

27

18

19

20

21

22



GroundstrapsWhat Groundstraps Do

Groundstraps:

• Maintain the ground potential between NonStop S-series system enclosures

• Protect the system from harmful electrical transients

Number of GroundstrapsFor any system, the number of groundstraps required is equal to the number of NonStop S-series enclosures minus one. For example, if a system contains six enclosures, five groundstraps are required.

Where to Install GroundstrapsGroundstraps are installed between two enclosures, either in a stack or between adjacent stacks. Groundstraps are not required between separate rows. For examples of groundstrap locations for a variety of enclosure arrangements, see Figure 2-11 on page 2-14 and Figure 2-12 on page 2-15.

A groundstrap connecting two system enclosures in a double-high stack might be installed at the factory on a new system or an add-on enclosure. However, if you have three or more enclosures, you must install the groundstraps that link the base enclosures.

More About Groundstraps and Power Requirements• Groundstraps are installed on systems that have more than one enclosure.

• Groundstraps are 14.8 inches (37.5 centimeters) long.

Note. For grounding information for IOAM enclosures, your service provider can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library.



Power-On Cables

Power-on cables carry the power-on signal from one PMF CRU or IOMF CRU to another, allowing you to power on all system enclosures in a system from one push button.

• Power-on cables have an RJ-11 connector at each end as illustrated in Figure 1-10.

• One power-on cable is required for each system enclosure.

• Power-on cables can be 8.2 feet (2.5 meters) or 23.0 feet (7.0 meters) long.

• The cables and enclosures must form a continuous ring so that each enclosure can deliver the power-on signal to the next enclosure.

For Information About SeeWhen to use specific cable lengths NonStop S-Series Planning and Configuration Guide

Where to install the power-on cables • Your Installation Document Checklist

• Appendix C, Power-On Cabling

Note. IOAM enclosures do not require power-on cables. For more information, your service provider can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library

Figure 1-10. Power-On Cable Connectors

VST703.vsd

System Enclosure(Service Side)

Power-On Cable



Emergency Power-Off CablesEmergency power-off (EPO) cables automatically disconnect electrical power to connected equipment if an electrical emergency occurs.

About EPO Cables

• EPO cables usually connect to a junction box of the computer room EPO system. (The EPO system must provide contact closure during an emergency.)

• One EPO cable for each enclosure is shipped with your system.

• The EPO cable is equipped with a two-pin Mate-N-Lock style plug at one end. This plug attaches to the EPO connector socket in slot 56.

• The other end of the EPO cable is unterminated, to attach to the EPO system.

EPO Cable Requirements

Within the United StatesAn EPO disconnect is required in a system if the system is installed in a computer or data processing room that is designed to comply with the construction and fire-protection provisions of:

• NFPA-75, Protection of Electronic Computer/Data Processor Equipment• Article 645 of NFPA-70, the National Electric Code

Outside the United StatesEPO disconnects are usually not required unless specified by local authorities.

If a System Requires EPO CapabilityIf a system requires EPO capability, the customer is responsible for connecting an EPO cable to the EPO connector in slot 56 on the service side of all system enclosures.

Note. For EPO information for IOAM enclosures, contact your service provider who can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library

Figure 1-11. EPO Cable

VST980.vsd

Unterminated End



If a System Does Not Require EPO CapabilityIf a system does not require EPO capability, go to ServerNet Cabling on page 1-36.

System OrganizationThis subsection describes the organization, group numbering, and labeling in a NonStop S-series system. For IOAM enclosure organization, see Group, Module, and Slot Hierarchy for IOAM Enclosures on page 1-28.

A system consists of the hardware and the software that runs on it. To perform hardware operations using the OSM or TSM package, you must be familiar with the organization and naming conventions and know how to identify individual components within the server.

OSM has a naming convention similar to, but more abbreviated than, the naming convention for system resource locations in TSM. For example, TSM displays the location of a fan CRU in this form:

FAN.GRP-1.MOD-1.SLOT-26

OSM displays the location of the same fan CRU in this form:

FAN (1.1.26)

Group, Module, and Slot Hierarchy for System Enclosures Hardware in a server is organized according to a system, group, module, and slot hierarchy, as follows:

A system enclosure can be serviced from two sides:

Term DefinitionSystem A set of groups and external hardware components.

Group A set of components accessible to a pair of service processors (SPs) in a system enclosure. In a NonStop S-series server, an enclosure contains one group.

Module A set of slots sharing a common hardware interconnect (such as a backplane).

Slot A labeled physical space in an enclosure in which a component can be installed.

Term DefinitionAppearance side

Contains fans, disk customer-replaceable units (CRUs), group ID switches, and power monitor and control unit (PMCU) CRUs.

Service side

Provides access to the PMF CRUs or IOMF CRUs as well as to the ServerNet expansion boards (SEBs), modular SEBs (MSEBs), and ServerNet adapters. Cables are also accessed from the service side.



Group, Module, and Slot Hierarchy IllustrationThis figure illustrates the service side and the appearance side of a processor enclosure:

50 55

51 52 53 54

56

Appearance Side Service Side

Group

Module

Slots

VST721.vsd

09

10

19

20

23

24 25 26 27

28

01 02 03 04 05 06 07 08

1811 12 13 14 15 16 17

29 30

31 32

21 22



Group, Module, and Slot Hierarchy for IOAM EnclosuresHardware in an IOAM enclosure is organized according to a group, module, and slot hierarchy:

To perform hardware operations on an IOAM enclosure, you must use OSM. TSM does not support IOAM enclosures. To identify individual components within the IOAM enclosure using OSM, you must be familiar with the organization and naming conventions. For example, OSM displays the location of a fan in group 11, module 3, slot 17 in this form:

Fan(11.3.17)

Term DefinitionGroup The IOAM enclosure and all the components within it. IOAM

enclosures are numbered in the same way as I/O enclosures.

Module One I/O adapter module (IOAM). There are two IOAMs in an IOAM enclosure, numbered 2 and 3. Each IOAM contains:

• One ServerNet switch board connected to a fabric. The ServerNet switch board in module 2 is connected to the X fabric, and the ServerNet switch board in module 3 is connected to the Y fabric.

• Two power supplies

• Two fans

• Up to five ServerNet adapters

Slot A physical space in the IOAM module in which a component can be installed. Slot numbers are assigned for each module:

Slot Number Component1, 2, 3, 4, 5 ServerNet adapter

14 ServerNet switch board

15 and 18 Power supplies

16 and 17 Fans



Group, Module, and Slot Hierarchy Illustrations of an IOAM EnclosureThis figure shows the front of an IOAM enclosure:

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

23

24

25

26

27

18

19

20

21

22

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

23

24

25

26

27

18

19

20

21

22

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

VST052.vsd

IOAM Enclosure(Group 12)

Power SuppliesModules 2 and 3

Fans(Module 3)

Fans(Module 2)

Slot 17 Slot 17

Slot 16 Slot 16

Power SuppliesModules 2 and 3

Fans(Module 3)

Fans(Module 2)

Slot 17 Slot 17

Slot 16 Slot 16IOAM Enclosure

(Group 11)



This figure shows the rear of an IOAM enclosure:

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

23

24

25

26

27

18

19

20

21

22

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

38

39

40

41

42

33

34

35

36

37

28

29

30

31

32

13

14

15

16

17

08

09

10

11

12

03

04

05

06

07

01

02

23

24

25

26

27

18

19

20

21

22

Module 2


Module 3

Slot

1

Slot

5Sl

ot 4

Slot

3

Slot

2

Slot

1

Slot

5Sl

ot 4

Slot

3

Slot

2

IOAM(Module 2)

IOAM(Module 3)

ServerNet Switch Board (Module 2)ServerNet Switch Board (Module 3)

Module 2


Module 3

Slo

t 1

Slo

t 5S

lot 4

Slo

t 3

Slo

t 2

Slot

1

Slot

5Sl

ot 4

Slot

3

Slot

2

IOAM(Module 2)

IOAM(Module 3)

ServerNet Switch Board (Module 2)ServerNet Switch Board (Module 3)

VST050.vsd



Server Numbering and Labeling

A NonStop server can contain up to 44 system enclosures (8 processor enclosures and 36 I/O enclosures) with a total of 16 processors. IOAM enclosures can replace any or all I/O enclosures attached to group 01.

The type of NonStop server, the configuration, and the RVU all affect the number of I/O or IOAM enclosures supported. Table 1-2 shows the processors that reside in each processor enclosure, plus the maximum number of I/O enclosures or IOAM enclosures that each processor enclosure connects to. Groups 11 through 89 are I/O enclosures. IOAM enclosures can replace any or all I/O enclosures attached to group 01.

For an important restriction on adding IOAM enclosures to your system, see IOAM Configuration Requirements on page 1-32.

For Information About SeeProcessor and I/O enclosure connections

• NonStop S-Series Planning and Configuration Guide

• Section 3, Cabling Enclosures

Processor and IOAM enclosure connections

• Your service provider, who can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library

Table 1-2. Maximum Processor and I/O or IOAM Enclosure ConnectionsProcessor Enclosure (Group)

Contains Processors

Connects to I/O Enclosures (Groups)

Connects to IOAM Enclosures* (Groups)

01 0 and 1 11, 12, 13, 14, 15 11, 12, 13, 14, 15

02 2 and 3 21, 22, 23, 24, 25

03 4 and 5 31, 32, 33, 34, 35

04 6 and 7 41, 42, 43, 44, 45

05 8 and 9 51, 52, 53, 54

06 10 and 11 61, 62, 63, 64

07 12 and 13 71, 72, 73, 74

08 14 and 15 81, 82, 83, 84*For important restrictions on IOAM enclosures, see IOAM Configuration Requirements on page 1-32 .



IOAM Configuration RequirementsInstalling IOAM enclosures on your NonStop S-series system includes the following requirements:

• You must install the IOAM enclosure as group 11, 12, 13, 14, or 15.

• The presence of an IOAM enclosure in your system requires that certain other groups be left empty. If you have I/O enclosures in these groups, you must remove them.

If necessary, remove I/O enclosures from your system as follows:

To add an IOAM enclosure as group ...You must remove any I/O enclosures in groups ...

11 21, 31, 41

12 22, 32, 42

13 23, 33, 43

14 24, 34, 44

15 25, 35, 45



Group ID SwitchesSet group identification with the two-digit ID switches, located on the inside of system enclosures near the fans. Each enclosure has two sets of switches. Both the switches must display the same value. The service processors (SPs) read the switches at power on. This figure shows the group ID switches:

VST603.vsd

10

Group IDSwitch

Group IDSwitch



Identification Labels

Identification labels on the appearance side of an enclosure

Label Location NotesGroup ID

Placed in holders on service and appearance sides of enclosure before shipping

These labels help you find CRUs that need service.

The numbers shown by the group ID label and group ID switches must match.

Module ID

Service and appearance sides of enclosure

Because there is only one module in each group, this number is always 01.

Slot Attached to frame below each slot

These labels help you find CRUs that need service.

VST602.vsd

01

02

Group 02, Module 01, Slot 03

05040301 02 06

MODULE

01

SLOT

03



IOAM Enclosure ServerNet Switch Board LCDEach ServerNet switch board in an IOAM enclosure contains an LCD that reports information about the enclosure:

Information Displayed Description ExampleIP Address The IP address of the module. Each module

has a separate IP address.IP: 16.107.134.54

System, Group, and Module

The system name, the group number of the IOAM enclosure, and the module number of the IOAM.

STAR1-G013-M02

Rack Name and Offset

Name of the rack and the rack offset of the IOAM enclosure. The offset is the physical location of the enclosure within the rack with offset being the lowest number on the rack that the enclosure occupies.

The Rack Name and Rack Offset are assigned using OSM and are also displayed as enclosure attributes in OSM. Rack Name and Rack Offset are arbitrary and can be up to eight characters long.

Using OSM, you can further identify the location of an IOAM by using the Set Locator action. You can enter up to 64 characters of identification text which is displayed in OSM by the Locator attribute for an IOAM.

Rack: OSM2 -14

Maintenance Entity Firmware

The version of the firmware image saved on the Maintenance Entity of the ServerNet switch board.

T2805A01_18Jun2004_13APR2004_SD1-FW

Maintenance Entity FPGA

The version of the field-programmable gate array (FPGA) image saved on the Maintenance Entity of the ServerNet switch board.

T0437A01_18JUN2004_25NOV2003AAA-FW



This figure shows the LCD of a ServerNet switch board. Two lines are displayed at a time. You can use the scroll buttons to move up and down through the display.

ServerNet Cabling

This subsection describes ServerNet configurations, cables, connections, and routing. Review this information before connecting ServerNet cables.

System Size

For More Information About SeeAny of this information NonStop S-Series Planning and Configuration Guide

Table 1-3. Maximum Numbers of Enclosures for G06.03 and Later RVUs

TopologyNonStop S700 Server NonStop S7x00 Server NonStop Sxx000 Server

Tetra 8 1 processor enclosure2 I/O enclosures

4 processor enclosures8 I/O enclosures

4 processor enclosures8 I/O enclosuresIOAM enclosures can replace any or all I/O enclosures attached to group 01*

Tetra 16 N.A. 8 processor enclosures16 I/O enclosures

8 processor enclosures36 I/O enclosuresIOAM enclosures can replace any or all I/O enclosures attached to group 01*

*For important restrictions on IOAM enclosures, see IOAM Configuration Requirements on page 1-32.

ServerNet Switch Board

LCD

NEWHP-G013-M02Rack: OSM2 - 14

VST053.vsd



TopologiesSystems can be configured in two topologies, the Tetra 8 and Tetra 16 topologies.

Enclosures are cabled to each other in patterns that depend upon the system topology. This cabling remains the same regardless of how the enclosures are physically arranged.

For example, connector 1 on the ServerNet Expansion Board (SEB) in slot 51 of enclosure 01 connects only to the SEB connector 1 of enclosure 02. Similarly, all I/O enclosures connect to a unique SEB port although the ports might differ between Tetra 8 and Tetra 16 configurations.

Therefore, the cabling patterns remain the same whether the enclosures are adjacent, separated by other enclosures, or located in separate rows.

Fabrics and SlotsThe relationships among components, slots, and fabrics are:

ServerNet cables connect SEBs or MSEBs in a processor enclosure to any of:

• SEBs or MSEBs in another processor enclosure • IOMF CRUs in an I/O enclosure• ServerNet switch boards in an IOAM enclosure (MSEB connection only)

In systems with more than one enclosure, all processor enclosures contain SEBs or MSEBs. These components are installed in slots 51 and 52.

Enclosure One of These Components Fits in This SlotAnd Connects to This Fabric

System • IOMF CRU• IOMF 2 CRU• PMF CRU

50 X

55 Y

• SEB • MSEB• Other adapters

51 X

52 Y

53 X

54 Y

IOAM • IOAM ServerNet switch board (module 2)

14 X

• IOAM ServerNet switch board (module 3)

14 Y

• FCSA or G4SA 1 - 5 (modules 2 and 3) Connects to both X and Y fabrics (dual-ported)

Note. For information about whether SEBs or MSEBs are required for your system, see the NonStop S-Series Planning and Configuration Guide.



Other components, such as ServerNet/FX adapters and ServerNet/DAs, can be installed in slots 51 and 52. However, installing components besides SEBs or MSEBs in these slots prevents the attaching of I/O enclosures to the processor enclosure.

In Tetra 16 topologies, slots 53 and 54 contain SEBs or MSEBs if both the following are true:

• These slots belong to groups 01 through 04.• I/O enclosures are attached to these groups.

IOAM Enclosure CablingAn IOAM enclosure is mounted in a standard 19-inch rack and connects to the MSEB of S76000 and later NonStop S-series systems using multimode LC-SC fiber-optic cables up to a maximum length of 125 meters. The LC connector connects to the ServerNet switch board, and the SC connector connects to the MSEB.

ServerNet CablesServerNet cables connect SEBs, MSEBs, IOMF CRUs, IOMF 2 CRUs, and IOAM enclosures. These connections form the ServerNet system area network (ServerNet SAN), which allows enclosures and other devices to communicate.

Cable CompatibilitiesDifferent ServerNet cables connect to different components. When more than one type of cable can connect to a component, the choice of cable depends on the type of plug-in card (PIC) connector installed on the component.

Caution. If IOAM enclosures are installed in the field, they must be installed by service providers trained by HP. All cabling connections must be performed by your service provider. Your service provider can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library.

Table 1-4. ServerNet Cable Compatibilities With ComponentsCable Connects to Port Number Port Type

ECL

IOMF CRU N.A. N.A.

IOMF 2 CRU (with ECL PIC installed)

N.A. N.A.

SEB 1-6 N.A.

MSEB 1-5 Variable



Fiber-Optic

IOMF 2 CRU N.A. Variable

ServerNet switch board (IOAM)

1-4 Fiber-optic

MSEB1-5 Variable

6 Node-numbering agent (NNA)

Serial-copper

IOMF 2 CRU N.A. Variable

MSEB1-5 Variable

7-10 Fixed

Note. For information about cable compatibilities for an IOAM enclosure, your service provider can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library.

Figure 1-12. Port Numbers and Cable Connections on an MSEB

Table 1-4. ServerNet Cable Compatibilities With ComponentsCable Connects to Port Number Port Type

NNA Fiber-Optic PIC

ServerNet ECL,Fiber-Optic, orSerial Copper PICs

ServerNetSerial Copperports

7

8

9

10

6

5

4

3

2

1

VST099.vsd



Types of ServerNet CablesNonStop S-series systems support three kinds of ServerNet cables: emitter-coupled logic (ECL), fiber-optic, and serial-copper.

ECL CablesECL cables have two types of connectors. These different types of connectors allow the cables to connect SEBs to SEBs, MSEBs to MSEBs, or SEBs to MSEBs.

SEB-to-SEB ECL cables are terminated at each end by a large 50-pin connector.

The MSEB-to-MSEB ECL is terminated at each end by a small 50-pin connector.

To connect a SEB to an MSEB, use a SEB-to-MSEB ECL cable.

Figure 1-13. SEB-to-SEB ECL Cable

Figure 1-14. MSEB-to-MSEB ECL Cable

Figure 1-15. SEB-to-MSEB ECL Cable

VST984.vsd

VST104.vsd

MSEB Connector SEB Connector

VST105.vsd



Serial-Copper CablesSerial-copper cables are lighter than ECL cables.

Fiber-Optic CablesThe NonStop S-series servers support two types of fiber-optic cables: multimode fiber (MMF) and single-mode fiber (SMF).

Which cables you use depends on the fiber-optic plug-in cards (F-PICs) installed in the ports to which the cables connect.

Do not interchange SMF and MMF cables even though their connectors are similar. SMF cables operate correctly only with SMF PICs, and MMF cables operate correctly only with MMF PICs. MMF cables are often orange, and SMF cables are often yellow. You can distinguish the cables by the part numbers printed on them.

For most systems that use fiber-optic cables, MMF cables are recommended. SMF cables are used primarily with the ServerNet Cluster product to connect MSEBs to ServerNet cluster switches. For the ServerNet Cluster application, you must install NNA PICs in connector 6 of each MSEB you plan to use.

Fiber-optic cables allow enclosures to be placed further apart than ECL or serial-copper cables.

Fiber-Optic Cables With LC-SC ConnectorsFor the ServerNet Cluster product and the IOAM enclosures, LC-SC fiber-optic cables are used to connect to the MSEBs.

Figure 1-16. Serial-Copper Cable

Caution. You can bend or break two small retainer pins inside the associated PIC receptacle. When you disconnect a serial-copper cable connector from a serial-copper PIC, fully and firmly depress the tab on the cable connector before pulling out the cable connector.

Figure 1-17. Fiber-Optic Cable

Serial-Copper Cable

VST999.vsd

VST109.vsd



The duplex Lucent connectors (LC) are used to connect to the transceivers on a 6780 switch in the ServerNet cluster product and to the ServerNet switch boards in an IOAM enclosure. Figure 1-18 shows a fiber-optic cable terminated by an LC connector.

The duplex subscriber connector (SC) connects to a port on the MSEB. For the ServerNet cluster product, you must install NNA PICs in connector 6 of each MSEB you plan to use. Figure 1-19 shows a fiber-optic cable with an SC connector.

Cable LengthsThe ServerNet cable lengths for your system depend on how your system enclosures will be arranged.

Although two enclosure arrangements might be logically equivalent, the cable lengths required might vary greatly: various enclosure arrangements are possible for the same configuration. Configurations might be laid out in a single row or multiple rows, and enclosures might be stacked in different combinations.

You can determine cable lengths for your system in two ways:

• See the System Enclosure Arrangement Form for your system.

• See the instructions for determining cable length in the NonStop S-Series Planning and Configuration Guide.

Cable LabelsLabel both ends of each cable. Figure 1-20 shows a cable that connects port 5 of an SEB in slot 51 of the group 01 enclosure to the ServerNet port on the IOMF CRU in slot 50 of the group 11 enclosure.

Figure 1-18. LC Connector for the 6780 Switch or ServerNet Switch Board

Figure 1-19. SC Connector for MSEB

VST107.vsd

VST108.vsd



For more information about labeling, see the NonStop S-Series Planning and Configuration Guide.

Cable RoutingTo route ServerNet cables across enclosures:

1. Route them straight down. 2. Secure them to a cable support.3. Direct them into cable channels.

• Secure a cable to the cable support below the CRU to which the cable connects. Secure the cable so that if you remove that CRU, you do not disrupt other cables.

• Secure cables to the anchors on the cable supports. Secure ServerNet cables to the outer cable support, and Ethernet or power-on cables to the inner one.

• In a double-high stack, use only the base enclosure cable channels.

• Guideposts guide cables from a stackable enclosure into the cable channels of a base enclosure.

• Guideposts on base enclosures are not often used, but you can route cables underneath these guideposts to use up extra cable length.

Figure 1-20. ServerNet Cable Labeling

Caution. Do not pass cables or cords through the handles of CRUs or FRUs. The cables or cords might become accidentally unplugged during later procedures. See Figure 1-21 for proper cabling.

VST823.vsd

SEB 015105IOMF 1150

SEB 015105

IOMF 1150

SEB 015105IOMF 1150

SEB 015105IOMF 1150



Figure 1-21. Cable-Management Hardware

02

CableChannel

CableChannel

01

Inner Cable-Tie Anchor

ServerNetCables

VST966.vsd

CableSupport

CableGuidepost

Cable Tie



The System ConsoleThis subsection describes the system console, and introduces terms and concepts you must understand to install it.

System ConsolesA system console is an HP-approved personal computer used to run maintenance and diagnostic software for NonStop S-series servers. New system consoles are preconfigured with the required HP and third-party software. When upgrading to the latest RVU, software upgrades can be installed from the HP NonStop System Console Installer CD.

System consoles communicate with NonStop S-series servers over a dedicated local area network (LAN) or a nondedicated (public) LAN. For more information about LAN connections, see The Dedicated LAN on page 6-2.

Using a system console, you can:

• Monitor operations on servers using the OSM or TSM package

• View manuals

• Run HP Tandem Advanced Command Language (TACL) sessions using terminal-emulation software

• Install and manage system software using the Distributed Systems Management/Software Configuration Manager (DSM/SCM)

• Make remote requests to and receive responses from a server using remote operation software

The OSM ProductFor the G06.22 RVU, the HP Open System Management (OSM) product replaces TSM as the system management tool of choice for NonStop S-series systems. While TSM is still supported, OSM offers a browser-based interface that improves scalability, performance, and other limitations that exist in TSM. OSM is required for support of new functionality released at the G06.22 RVU and beyond.

Topic PageSystem Consoles 1-45

The OSM Product 1-45



Modems 1-48

Preloaded Hardware and Software 1-49

Software Connections 1-53



To access the OSM guided replacement procedures, see OSM Guided Replacement Procedures on page xxiii.

For more information about OSM, and detailed comparisons of OSM and TSM functions, see the OSM Migration Guide and the OSM User’s Guide.

The TSM PackageThe TSM package is a collection of software products that provide troubleshooting, maintenance, and service tools. The TSM package consists of TSM server software and TSM client software.

TSM server software is the portion of the TSM package that resides on the server. TSM client software is the portion of the TSM package installed on a system console.

For more information about the TSM package or for information about operating or configuring TSM software:

• TSM Online User Guide


• TSM Low-Level Link online help

• TSM Notification Director online help

• TSM Event Viewer online help



Primary and Backup System ConsolesSystem consoles equipped with modems and configured as primary or backup dial-out points are referred to as the primary and backup system consoles, respectively.

A primary or backup system console can receive incident reports from the server and notify a remote service provider of pending hardware or software problems. At least one system console (the primary system console) is required for the system. Having a second (or backup) system console is strongly recommended.

System consoles must be connected to the dedicated LAN. For more information about dedicated LAN connections, see The Dedicated LAN on page 6-2.

A server must be connected through an Ethernet LAN to at least one system console. Primary system consoles and other system consoles compare as follows:

For information about dial-in and dial-out capabilities of system consoles, see the OSM Notification Director online help or the TSM Notification Director online help.

Primary and Backup System Consoles Other System Consoles

• Must be connected to the dedicated LAN.

• Can be connected to the dedicated LAN or to a nondedicated (public) LAN.

• Can use all OSM and TSM client applications, including the Low-Level Link and Notification Director.

• Can use the OSM and TSM Low-Level Link and Notification Director only if connected to the dedicated LAN.

• Receive incident reports.

Only two system consoles can be configured to receive and forward (or dial out) incident reports for each system. These primary and backup dial-out points are referred to as the primary and backup system consoles for a particular system.

• Cannot receive incident reports.



ModemsModems modulate or demodulate digital information so that it can be transmitted or received over a telephone line. It is recommended that you equip primary and backup system consoles with modems connected to dedicated phone lines. This allows system consoles to dial out for remote notification of system problems. Dial in for remote access by your service provider can also be configured.

Dial-OutsDial-out capability lets the OSM or TSM Notification Director notify a remote service provider of pending hardware and software problems. Either of two system consoles, defined as the primary and backup dial-out points, can be used for dial-outs. In this guide, these are the primary and backup system consoles. If your system has only one system console, it is defined as the primary dial-out point.

While both OSM and TSM software can be installed on your system console, you should use only one of the Notification Director applications to avoid creating duplicate incident reports and dial-outs for the same problem.

In a dial-out situation, incident reports are forwarded by the server to the primary dial-out point. If the primary dial-out point does not respond, the reports are forwarded to the backup dial-out point. Either dial-out point uses the modem to send these reports to your service provider. Because your service provider has no access to the server, dial-outs are completely secure.

Configure dial-out capacity with the OSM or TSM Notification Director. If a LAN contains multiple servers, the primary and backup system consoles should be configured to receive incident reports from no more than 10 servers on the LAN.

For information about dial-out situations, see the OSM User’s Guide or the TSM Configuration Guide.

Note. Dial-out and dial-in are not available in countries where the provided modem is not certified. In these countries, you cannot dial out incident reports to, or accept dial-in communications from, your service provider.

Note. The NonStop system console and OSM Notification Director support using HP Instant Support Enterprise Edition (IEEE) as a web-based alternative to modem dial-out functionality. For more information on ISEE:

• Go to the CSSI Web and click ISEE for NonStop to learn about ISEE prerequisites and NonStop-specific details that you will need before downloading and configuring the ISEE client from the HP Hardware Support Services Web. A link to the CSSI Web can be found in the left navigation area of the NTL home page.

• Go to HP Hardware Support Services Web site at http://h20219.www2.hp.com/services/cache/10709-0-0-225-121-aspx to learn more about ISEE and to download the ISEE client, documentation, and training.

• Contact your HP representative.



Dial-InsDial-in capability lets a remote service provider access information about your server to diagnose hardware or software problems. For dial-in, your service provider uses a system console to dial in to a workstation on the same LAN as your server. The workstation uses remote operations software, such as Carbon Copy or Microsoft Windows NetMeeting, to route requests and responses between your server and your service provider.

All system consoles provided by HP include the software for dial-in capability. Security mechanisms are available to ensure that dial-ins do not jeopardize your operational security. For information about dial-in user names, passwords, configuration, and security, see the TSM Configuration Guide, the OSM User’s Guide, and the online help and documentation provided with your remote operations software.

Preloaded Hardware and SoftwarePersonal computers (PCs) provided for use as system consoles come preloaded with the hardware and software to run OSM software. TSM software can be installed from the HP NonStop System Console Installer CD.

Only PCs provided by HP for this purpose are supported as system consoles.

Caution. To preserve the integrity of applications running on system consoles, do not install any software applications on your system consoles other than those listed in Table 1-5. Compromising the software on the system console might leave you unable to communicate with your server.

Table 1-5. Preloaded HP NonStop System Console Software (page 1 of 2)

Software Function For more informationOSM Application suite, which contains these OSM components:

Lets you service and maintain the server.

OSM Migration Guide

OSM User’s Guide

• OSM Low-Level Link

Down-system support

• OSM Notification Director

Remote services (dial-in, dial-out)

• OSM Console Tools

Start menu shortcuts and default home pages for easy access to the OSM Service Connection and OSM Event Viewer (browser-based OSM applications that are not installed on the system console).



Optional but can be installed:

TSM Low-Level Link

TSM Service Application

TSM Notification Director

TSM Event Viewer

Lets you service and maintain the server.

TSM Online User Guide


TSM Low-Level Link online help

TSM Service Application online help

TSM Notification Director online help

TSM Event Viewer online help

OutsideView terminal emulator software

Runs a TACL session. Online help included with the software

Distributed Systems Management/Software Configuration Manager (DSM/SCM)

Beginning with the G06.19 RVU, DSM/SCM client software is no longer available on the HP NonStop Server System Console Installer. You must download DSM/SCM client software from the SUT.

DSM/SCM User’s Guide

To install and download the DSM/SCM client:

G06.nn Software Installation and Upgrade Guide

Carbon Copy remote operations software

Lets a service provider dial in to and operate a system console from a remote site using a modem

Documentation and online help included with the software

WAN Wizard Pro A graphical user interface (GUI) that guides you step-by-step through the configuration of wide area network (WAN) and local area network (LAN) software and hardware.

Access the WAN Wizard Pro on page F-9

See applicable online help in the Help menu

SP Tool Allows you to diagnose SP problems

Verifying Topology and System Components, Step 9, page 8-16

See applicable online help in the Help menu

Internet Explorer 6.0 Allows you access to the World Wide Web

Table 1-5. Preloaded HP NonStop System Console Software (page 1 of 2)

Software Function For more information



Preconfigured IP AddressesNew systems are shipped with preconfigured system IP addresses for system maintenance that OSM and TSM applications use to communicate with the system.

Note. IOAM components are not pre-configured with IP addresses. IOAM components require dynamically assigned IP addresses from a DHCP/DNS server, or from software that performs the same function as that server. For more information, your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

Table 1-6. Preconfigured IP Addresses for a NonStop S-Series ServerComponent IP Address NotesPrimary system console 192.231.36.1 • All system consoles provided by HP are

preconfigured with IP address 192.231.36.1.

• Two system consoles on the same LAN cannot use the same IP address.

• If the primary system console uses IP address 192.231.36.1, you must change the IP address on all other new system consoles before connecting them to the LAN.

• The recommended IP address for a backup system console is 192.231.36.4.

MSP0 192.231.36.2 • Access is through the Ethernet port on the PMF CRU in group 01, module 01, slot 50.

• This IP address allows you to establish a low-level link.

MSP1 192.231.36.3 • Accessed through the Ethernet port on the PMF CRU in group 01, module 01, slot 55.


NonStop operating system access using $ZTCP0

192.231.36.10 • Access is through the Ethernet port on the PMF CRU in group 01, module 01, slot 50.

• This IP address allows you to establish a service connection.

NonStop operating system access using $ZTCP1

192.231.36.11 • Access is through the Ethernet port on the PMF CRU in group 01, module 01, slot 55.

• This IP address allows you to establish a service connection.



MSP IP addresses communicate with the master service processors (MSPs). NonStop operating system IP addresses communicate with the operating system for the specified processor. For more information about how these IP addresses are used, see the NonStop S-Series Planning and Configuration Guide.

To provide security and to make NonStop S-series equipment compatible with your existing LAN, change these IP addresses before exiting the OSM or TSM Low-Level Link.

To change the system console, MSP, and operating system access IP addresses, use the OSM or TSM Low-Level Link. See the documentation appropriate to the software you are using:

• OSM Low-Level Link online help

• OSM User’s Guide

• TSM Low-Level Link online help


Subnet 192.231.36.0

Subnet mask 255.255.255.0

Gateway 192.231.36.9

Table 1-6. Preconfigured IP Addresses for a NonStop S-Series ServerComponent IP Address NotesPrimary system console 192.231.36.1 • All system consoles provided by HP are

preconfigured with IP address 192.231.36.1.

• Two system consoles on the same LAN cannot use the same IP address.

• If the primary system console uses IP address 192.231.36.1, you must change the IP address on all other new system consoles before connecting them to the LAN.

• The recommended IP address for a backup system console is 192.231.36.4.

MSP0 192.231.36.2 • Access is through the Ethernet port on the PMF CRU in group 01, module 01, slot 50.




Software ConnectionsA system console can communicate with a server using two types of software connections: a service connection and a low-level link. Both connections support NonStop user names, but low-level links support up to 18 MSP user names.

A service connection:

• Is a connection between the OSM or TSM software on a system console and the OSM or TSM software on the server.

• Lets you service and maintain a server when the NonStop operating system is running.

• Gives you comprehensive information about the server. You can examine the state of all supported devices as seen by the operating system and OSM or TSM server software.

• Is established by the OSM Service Connection or TSM Service Application.

A low-level link:

• Is a connection between the OSM or TSM software running on a system console and the master service processors (MSPs) on the server.

• Allows communication over a low-level link whether or not the NonStop operating system is running.

• Gives you access to critical information and functions.

• Is established by the OSM or TSM Low-Level Link.



System StartupStartup and Shutdown Files

Startup and shutdown files automate starting and stopping all processes on the system. There are two types of startup files: the CIIN file, which can be executed automatically during system load, and all other startup files, which can be invoked by an operator or by another startup file.

Automating system shutdown aids the operator in bringing the system to an orderly halt. You can implement the system shutdown sequence with a collection of shutdown files, each with a specific purpose. The shutdown file sequence reverses the order of commands in the startup file sequence: applications are shut down first, followed by the print spooler and other system software.

Create the startup and shutdown files now if you just installed a new system and previously had no other system to create these files. To create and modify startup and shutdown files, see the NonStop S-Series Planning and Configuration Guide.

System Load PathsEach system in a standard configuration ships with these startup characteristics:

• $SYSTEM disks are located in the system enclosures containing processors 0 and 1.

• System load paths are configured.• The CIIN function is enabled.

If the automatic system load is not successful using one load path, the system load task attempts to use another path and keeps trying until all possible paths have been used or the system load is successful. Eight paths are available for loading. Table 1-7 describes each load path in order of use.

Table 1-7. System Load Paths in Order of UseData Travels

Load Path Description From To Processor Over ServerNet Fabric1 Primary $SYSTEM-P 0 X

2 Backup $SYSTEM-P 0 Y

3 Mirror $SYSTEM-M 0 Y

4 Mirror backup $SYSTEM-M 0 X

5 Primary $SYSTEM-P 1 X

6 Backup $SYSTEM-P 1 Y

7 Mirror $SYSTEM-M 1 Y

8 Mirror backup $SYSTEM-M 1 X



The command interpreter input (CIIN) file is automatically invoked after the first processor is loaded. The CIIN file shipped with new systems contains the TACL RELOAD * command, which loads the remaining processors.

Figure 1-22 shows possible system load paths.

Figure 1-22. System Load Paths

Processor

x y

ServerNetAdapter

$SYSTEM-P

$SYSTEM-M

Router Router

P B

MMB

Processor

x y0 1

= X Fabric= Y Fabric

LegendServerNetAdapter

ServerNetAdapter

ServerNetAdapter

VST956.vsd



PMF CRU and IOMF CRU Power-On Self-TestsWhen the system is powered on or when a PMF CRU or IOMF CRU is initially connected to the backplane, a series of automatic power-on self-tests (POSTs) are run on the CRU. These POSTs take several minutes to finish. The three types of tests are:

• CPU memory test (PMF CRU only)• System load path test (PMF CRU only)• Multifunction I/O board (MFIOB) test

At completion of certain self-tests, the service processor (SP) generates events in the EMS log. Look for the SpEvCruTestComplete event for details about the POST operations. To view these details, use the OSM or TSM Event Viewer.

CPU Memory TestThe CPU memory test checks the system main memory. If the CPU memory test finishes successfully, the boot millicode starts the system load path test. If the test fails, the service processor (SP) lights the amber fault LED on the PMF CRU.

Generally, the CPU memory test fails because of a correctable memory error (CME) or a hardware error freeze.

To troubleshoot a failed CPU memory test, see Appendix D, Troubleshooting.

System Load Path TestThe system load path test checks the system load paths. If the system load path test finishes successfully, firmware for the intelligent SCSI processor (ISP) is loaded, the SCSI buses are scanned, the processor is reset, and the boot millicode starts the multifunction I/O board (MFIOB) test.

To troubleshoot a failed system load path test, see Appendix D, Troubleshooting.

Multifunction I/O Board (MFIOB) TestThe multifunction I/O board (MFIOB) test checks the MFIOB. If the MFIOB test finishes successfully, the service processor (SP) extinguishes the amber service LED on the PMF CRU or IOMF CRU and generates an event, completing the POST. If the MFIOB test fails, the MFIOB is either partially operational or not operational.

To troubleshoot a failed MFIOB test, see Appendix D, Troubleshooting.

Note. For IOAM enclosure, G4SA, and FCSA power-on self-tests, contact your service provider trained by HP.


2 Installing EnclosuresThis section describes how to unpack new equipment and install NonStop system enclosures.

The procedures in this section apply to all types of NonStop S-series processor enclosures and I/O enclosures.

For information about dimensions, weights, or other specifications of NonStop S-series enclosures, see Section 1, Introduction.

Topic PagePrepare to Install New Equipment 2-2

1. Review the Documentation 2-2

2. Prepare the Work Space 2-3

3. Organize the Equipment 2-4

Unpack the Enclosures 2-6

Tools 2-6

Unpack the Enclosures 2-6

Connect the Groundstraps 2-13

Inventory the Enclosures 2-16

Slot Assignments for NonStop S-Series Enclosures 2-16

Inspect the Components 2-23

Notes. If you are adding a processor or I/O enclosure to a previously installed system, see the NonStop S-Series System Expansion and Reduction Guide.

Caution. A new IOAM enclosure or an additional IOAM enclosure must always be installed by a service provider trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.


Installing Enclosures Prepare to Install New Equipment

Prepare to Install New EquipmentComplete the steps in this section when your equipment arrives.

1. Review the DocumentationTypically, documentation is provided by the system planner. The system planner gives you the information you need to perform the installation: what the system configuration is and the steps to complete.

Has the system planner completed the Installation Document Checklist?

• If yes:

1. Review all forms, diagrams, and lists in the Installation Document Checklist.

For an example of completed forms, see the NonStop S-Series Planning and Configuration Guide.

For blank forms, see:

° NonStop S-Series Planning and Configuration Guide° LAN Configuration and Management Manual° SWAN Concentrator Installation and Support Guide° TSM Configuration Guide° ServerNet adapter manuals

2. Ensure that you have everything listed in the checklist.

3. Ensure that you understand the documentation.

If the documentation is unclear or if you have questions about how to complete an installation procedure, contact the system planner or your service provider.

• If no:

Ensure that you have all necessary information about:

° The installation site° Power outlets° Communications lines° System configuration° Equipment you will be installing

See the preceding manuals for blank forms that can help you gather all necessary information.


Installing Enclosures 2. Prepare the Work Space

2. Prepare the Work Space1. Clear the installation site so that you have room to work.

2. Use the Floor Plan Diagram to find the installation site or sites.

3. Verify that preinstalled I/O device cables, such as Ethernet LAN cables, are installed:

• For a list of cables, see the Preinstalled I/O Device Cable Checklist.• To find the preinstalled cables, use the Floor Plan Diagram.

4. Report any missing cables to the system planner.

5. Ensure that the installation site provides adequate electrical connections.

Connections include:

• Two properly grounded outlets for each system enclosure to be installed

• One branch circuit breaker for each outlet

• Emergency power-off (EPO) disconnect wiring

This requirement applies only to computer room installations in the United States or installations governed by local regulations that stipulate EPO capability.

For more information about EPO requirements, see the NonStop S-Series Planning and Configuration Guide.

• One single-source distribution, uninterruptible power supply (UPS))

Connect the entire system to the UPS. For more information about UPS requirements, see the NonStop S-Series Planning and Configuration Guide.

6. Ensure the AC power cords for the enclosures to be installed are correct for the outlets at the installation site:

• For a list of supported AC power cords by country, plug type, part number, and length for system enclosures, see the CSSI Web. See CSSI Web on page xxiii.

• For power planning information, see the NonStop S-Series Planning and Configuration Guide.


Installing Enclosures 3. Organize the Equipment

3. Organize the Equipment1. Sort the shipping cartons into two groups:

2. Move all the short cartons to the installation site.

Do not unpack the tall cartons yet.

3. Verify that the OPEN FIRST box contents are complete as follows:

Height ContentsTall (at least 40 inches or 102 cm)

• System enclosures• Tape subsystems

Short (shorter than 40 inches or 102 cm)

• System console• ServerNet cables• System accessories• Service-side door add-on package (optional)

Note. Shipping cartons containing IOAM enclosures and their related components must be unpacked by your service provider. Information is available to your service provider in the Modular I/O Installation and Configuration Guide.

Item Description Allows you to ...Invoice Order information

Inventory equipment.Box Inventory List A list of part numbers, part descriptions, and quantities

Site update tape (SUT)

Cartridge or open-reel tapes.

These are already installed on your system disk. Do not use these tapes when installing or starting the system.

Use these tapes as backup. System image tape (SIT)

Envelope Documentation about your system as it was ordered

Review the initial system configuration.

CONFTEXT configuration file printout

A list of system attributes that define the HP NonStop operating system image for all processors in the system

• Review the initial system configuration.

• Plan your customized system configuration.SCF configuration file

printout, $SYSTEM.ZSYSCONF.SCF0000

A list of system attributes and other information that defines the system configuration

Ethernet switch Equipment Connect the system console to the server.Ethernet cables Type depends on your location

Modem Equipment Enable the system to receive dial-ins.Modem cable Type depends on type of modem

4-mm hexagonal wrench

Tool Unlock appearance-side enclosure doors.


Installing Enclosures 3. Organize the Equipment

4. Find the System Image Tape (SIT) and Site Update Tape (SUT).

These tapes contain the same files as on your system disk. Because the files are present on the system disk, do not use the tapes to install or start the system.

5. Verify that the format of the SIT and SUT tapes matches your tape subsystem. If the formats do not match your tape subsystem, contact your service provider.

6. Store the SIT and SUT tapes in a safe place.

7. Verify that the other short cartons contain:

8. Verify that all equipment has arrived and that cables are the correct lengths.

Did the system planner provide a System Equipment Inventory Form?

• If yes: Compare this form to the equipment received.

ServerNet adapters and disk drives are shipped installed in the enclosures. You can check off this equipment when you unpack and install the enclosures.

• If no: Compare the Product List or Box Inventory List to equipment received.

Getting Started Documentation Use the materials correctly.

Item QuantityEPO cable One per enclosure

AC power cords Two per each system enclosure that has no power shelf

Power-on cable One per enclosure

ServerNet cables Quantity varies depending on the number of enclosures. 0 for one processor enclosure with no I/O enclosures.

Cable ties 12 per enclosure

Groundstrap Number of enclosures minus one

Figure 2-1. Cords, Cables, and Other Contents of Short Cartons

Item Description Allows you to ...

Emergency Power-Off (EPO) Cable

AC Power Cord

Power-On Cable

ServerNet ECL Cable

Groundstrap

Cable Tie

VST977.vsd


Installing Enclosures Unpack the Enclosures

9. Report any missing or damaged items to your service provider.

10. Verify that you have all necessary tools. For a list of tools, see Tools on page 1-7.

Unpack the EnclosuresFor weights and dimensions of shipping packages and enclosures, see Shipping Packages on page 1-9.

ToolsTo unpack the enclosures, you need:

Unpack the Enclosures1. With heavy-freight-handling equipment, move all pallets and enclosures to the

installation area. Move enclosures with their protective coverings in place.

2. If the system was shipped in cold weather, allow it to warm up to room temperature.

3. Cut the straps, set the ramp aside, and lift the cardboard cap off the package:

Caution. Shipping packages for IOAM enclosures must be unpacked by a service provider trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

Tool PurposeHeavy-freight-handling equipment such as a forklift or pallet jack

To transport the pallet from the receiving area to the installation area

Scissors or cutters To remove the banding straps

Eye protection To ensure safety when removing the banding straps

WARNING. Wear safety glasses or other eye protection when cutting the banding straps. The ends of the straps might snap back when cut and cause an eye injury.



Figure 2-2. Unpacking the Enclosures

CardboardCap

CardboardPanel

UnloadingRamp

AntistaticBag

CardboardPanel

PlasticLocking

Clips

vst987.vsd



4. Open the plastic locking clips that hold the shipping package together:

a. Pinch the tabs on the clip together to unlock it.

b. Pull the tabs to remove the clip.

5. Pull the clips completely out of the shipping package and set them aside.

6. Remove the cardboard panels, the padded shipping insert, and the antistatic bag covering the system enclosure. Set these materials aside.

7. Position the ramp against the pallet.

8. Flip open the twist-lock handles on the pallet end piece.

9. Loosen the end piece by turning the twist-lock handles counterclockwise as far as they can go:

Figure 2-3. Tabs on Plastic Locking Clip of Shipping Package

Figure 2-4. Loosen End Piece of Pallet by Turning Twist-Lock Handles

VST004.vsd

System Enclosure(Side View)

Twist-Lock Handles

End Piece

VST951.vsd



10. Remove the end piece and set it aside.

11. Position the unloading ramp against the on the side from which you removed the end piece. Position the Velcro strips on either side of the ramp.

Ensure that the Velcro strips hold the ramp firmly against the pallet.

Figure 2-5. Removing End Piece of Pallet

Figure 2-6. Velcro Strips on Loading Pallet

System Enclosure on Pallet

End Piece

VST706.vsd

vst988.vsd

Velcro Strips



12. To prevent snagging hazards as you move the enclosure stack off the pallet, check that the leveling pads on the base enclosure are fully raised as shown:

If you need to raise the leveling pads, see the instructions later in this procedure.

Figure 2-7. Leveling Pads Must Be Raised Before Enclosure Is Moved

WARNING. When moving an enclosure stack:

• Always get at least one other person to help you move an enclosure stack. If the floor is uneven, use four people to move the enclosure, or contact your service provider.

• Move each enclosure slowly and gently, avoiding all unnecessary shock.

• Push on the frame of the enclosure stack. Do not push or pull on the plastic enclosure door or the cable channels.

• Casters on the appearance side of the enclosure swivel, but casters on the service side do not swivel. It is easiest to move the enclosure stack over discontinuities in the floor if the swiveling (appearance side) casters go first.

• A double-stacked enclosure tends to be top heavy. Move the enclosure stack off the pallet and down the ramp carefully.

• The enclosure pedestal is equipped with casters so that you can roll the enclosure down the ramp and push it across the floor to its final position. The casters are designed for short-distance moves over a smooth, hard surface or short-pile carpeting.

CasterCaster

CasterCaster

VST005.vsd



13. Using at least two people, grasp the enclosure stack frame. Slowly roll the stack off the pallet and down the ramp:

14. Move the enclosure stack to the location shown in the Floor Plan Diagram.

15. Position the enclosures according to the Enclosure Arrangement Diagram in the Installation Document Checklist designed for your system.

If you might reduce your system at any point, place enclosures that you might remove from your system on the top of the stack. The frames can touch one another. No service space is necessary on the sides of an enclosure.

Figure 2-8. Use Two People to Move an Enclosure Stack

vst986.vsd



16. With a 3/4-inch (19-mm) or a 9/16-inch (15-mm) open-end wrench, lower the four legs on the base enclosure:

a. Start with the enclosure leg raised. Use an open-ended wrench to loosen and lower the leg. The size of the wrench depends on the leveling pads.

b. Use the wrench to tighten the leg against the floor.

17. Repeat Step 3 through Step 16 for any additional system enclosures.

Figure 2-9. Lowering Legs of Base Enclosure

Caster Caster

VST017.vsd


Installing Enclosures Connect the Groundstraps

Connect the Groundstraps

For information about the purpose and specifications of groundstraps, see Groundstraps on page 1-23.

1. Find the groundstraps included with your system. The groundstraps are packaged in a plastic bag along with two Phillips-head screws for each groundstrap.

2. Find the four groundstrap connector locations on the service side of a system enclosure. See Figure 2-10. The groundstrap connector locations are the same for all system enclosures.

3. Connect the groundstraps following the pattern suggested in Figure 2-11 on page 2-14 and Figure 2-12 on page 2-15.

a. For each groundstrap, position one end of the groundstrap over the connector hole and install the screw using a Phillips screwdriver.

b. Route the groundstrap:

• To connect two base enclosures, route the groundstrap through the openings in the cable channels. See Figure 2-11. Tuck the excess strap length behind the cable channel.

• To connect two enclosures in a double-high stack, connect the groundstrap to the base enclosure. Tuck the excess strap length into the top of the base enclosure frame. Route the groundstrap behind the cable support on the stackable enclosure and up to the groundstrap connector.

Note. If your system has only one enclosure, go to Inventory the Enclosures on page 2-16.

Figure 2-10. Groundstrap Connector Locations

VST701.vsd

GroundstrapConnectors

Groundstrap



c. Install the other end of the groundstrap.

d. Repeat Step 3a through Step 3c until all system enclosures are linked by groundstraps.

4. For multiple-row systems, no groundstraps are installed between rows.

Figure 2-11. Groundstrap Connections Between Enclosures

Groundstrap Threaded ThroughOpening in Cable Channel

GroundstrapThreadedBehindCableSupport

Double-High Stack ofSystem Enclosures

(Service Side)

Base Enclosures (Service Side)

VST953.vsd



Figure 2-12. Examples of Groundstrap Locations Between Enclosures

Three EnclosuresTwo Enclosures

Five Enclosures Six Enclosures

Four Enclosures

Seven Enclosures Eight Enclosures

Sixteen EnclosuresVST976.vsd


Installing Enclosures Inventory the Enclosures

Inventory the EnclosuresVerify that the delivered system matches the system you ordered.

To make it easier to verify that all components are in the correct slots and your system is equipped as ordered, print or photocopy the following information.

Slot Assignments for NonStop S-Series Enclosures

Note. For information about whether SEBs or MSEBs are required for your system, see the NonStop S-Series Planning and Configuration Guide.

Table 2-1. Illustrations of Enclosures Including Slot NumbersEnclosure Type Appearance Side Service SideNonStop S7000 processor enclosure

Figure 2-13 on page 2-17


NonStop Sxx000 and S7x00 processor enclosures (except S7000)



I/O enclosure without power shelf None Figure 2-16 on page 2-20

I/O enclosure with power shelf None Figure 2-17 on page 2-21

Table 2-2. Slot Assignments: Tetra 8 TopologyEnclosure Hardware Slots NotesProcessor SEBs,

MSEBs51, 52 Reserve these slots for SEBs and MSEBs.

If ServerNet adapters are in slots 51 and 52, you cannot attach I/O enclosures to the processor enclosure.

ServerNet adapters

51, 52, 53, 54

The number of slots that support adapters depends on the number of enclosures in the system.

If ServerNet adapters are in slots 51 and 52, you cannot attach I/O enclosures to the processor enclosure.

I/O ServerNet adapters

51, 52, 53, 54

You can attach I/O enclosures to the processor enclosures in the Tetra 8 topology without installing SEBs or MSEBs in slots 53 and 54 of the processor enclosures.


Installing Enclosures Slot Assignments for NonStop S-Series Enclosures

Table 2-3. Slot Assignments: Tetra 16 TopologyEnclosure Hardware Slots NotesProcessor SEBs and

MSEBs51, 52, 53, 54

To attach I/O enclosures to the processor enclosures in the inner tetrahedron, you must install SEBs or MSEBs in slots 53 and 54 of the processor enclosures.

If ServerNet adapters are in slots 51 and 52, you cannot later attach I/O enclosures to the processor enclosure.

ServerNet adapters

51, 52, 53, 54

The number of slots that support adapters depends on the number of enclosures in the system.

I/O ServerNet adapters

51, 52, 53, 54

To attach I/O enclosures to the processor enclosures in the inner tetrahedron, you must install SEBs or MSEBs in slots 53 and 54 of the processor enclosures.

Figure 2-13. Appearance Side, Processor Enclosure

ComponentDiskDiskSCSI terminatorSCSI terminatorPMCU

BatteryGroup ID switchFanReserved (except for S7000)Power supply (except for S7000)

Slot01 - 0811 - 1809, 1019, 2021, 22

23, 2824, 2725, 2629, 3031, 32

Group Service LED

09

10

19

20

23

24 25 26 27

28

01 02 03 04 05 06 07 08

1811 12 13 14 15 16 17

21 22

29 30

31 32

VST622.vsd



Figure 2-14. Service Side: Processor Enclosure Without Power Shelf

VST621.vsd

50 55

51 52 53 54

56

Odd-NumberedProcessor

Even-NumberedProcessor

Module ID LabelGroup ID LabelGroup ServiceLED

ComponentProcessor Multifunction (PMF) CRUServerNet Expansion Board (SEB), Modular ServerNet Expansion Board (MSEB), or ServerNet Adapter, depending on topology and number of enclosuresSEB, MSEB, or ServerNet AdapterEmergency Power-Off (EPO) Connector

Slot50, 55

51, 52

53, 54

56



Figure 2-15. Service Side: Processor Enclosure With Power Shelf

VST623.vsd

ComponentProcessor Multifunction (PMF) CRUServerNet Expansion Board (SEB), Modular ServerNet Expansion Board (MSEB), or ServerNet Adapter, depending on topology and number of enclosuresSEB, MSEB, or ServerNet AdapterEmergency Power-Off (EPO) Connector

Slot50, 55

51, 52

53, 54

56

50 55

51 52 53 54

56



Module ID Label

Group IDLabel

GroupService

LED

PowerInterlock



Figure 2-16. Service Side: I/O Enclosure Without Power Shelf

VST970.vsd

50 55

51 52 53 54

56

Connects toY Fabric

Connects toX Fabric

Module ID Label

Group ID LabelGroup ServiceLED

ComponentI/O Multifunction (IOMF) CRUServerNet Adapter

Emergency Power-Off (EPO) Connector

Slot50, 55

51, 5253, 54

56



1. Open the appearance-side enclosure door, with a 4 mm (5/32 inch) diagonal wrench as in Figure 2-18 if necessary. The wrench is provided in the OPEN FIRST container or taped to the service side of the enclosure.

If you ordered optional service-side doors, this guide assumes that you install them after you complete the enclosure-cabling tasks in Section 3, Cabling Enclosures. To install these doors now, see Section 4, Installing Service-Side Doors.

Figure 2-17. Service Side: I/O Enclosure With Power Shelf

DC Power Cable (2 places)

VST972.vsd

55

51 52 53 54

56

X Fabric

Cable Support (1 of 2)

Cable-Routing Channels

Cable Guidepost (1 of 2)

50

Y Fabric

SCSI Port

50 55

Power Interlock

ComponentI/O Multifunction (IOMF) CRUServerNet Adapter

Emergency Power-Off (EPO) Connector

Slot50, 55

51, 5253, 54

56

Connects toConnects to



2. Verify that all components you ordered are present in the system enclosure:

• If the system planner completed the Installation Document Checklist:

With the System Enclosure Checklist, verify that each component ordered is present.

• If the system planner did not complete the Installation Document Checklist or if no other documentation is available:

Compare the order information with the contents of the enclosures.


Figure 2-18. Unlocking and Opening an Enclosure Door

Open the door

Unlock the door

System Enclosure Appearance Side

4-mm (or 5/32-inch)diagonal wrench

Turn counterclockwise

VST553.vsd


Installing Enclosures Inspect the Components

Inspect the ComponentsVibration that occurs during shipping or when you move a system can sometimes dislodge enclosure components or loosen connections to the backplane. Inspect these components, and reseat those that appear to be improperly seated.

• Disk drives• PMF CRUs• IOMF CRUs• SEBs or MSEBs• ServerNet adapters

Perform these steps for each system enclosure:

1. Inspect all disk drives in the system enclosure:

a. Open the enclosure door on the appearance side of the enclosure.

b. Verify that both thumbscrews on the faceplate of each disk drive are tight.

c. If any thumbscrews are loose and if a disk drive appears to be disengaged from the backplane connector, reseat the disk drive. See Step 2.

2. To reseat each disk drive that has become improperly seated during shipping:

a. Put on your ESD wriststrap and attach the grounding clip securely to an exposed, unpainted metal surface inside the disk card cage.

b. Simultaneously loosen both thumbscrews on the faceplate of the disk drive until the CRU disengages from the backplane connector. Do not pull the disk drive all the way out of the slot. See Figure 2-19.

Figure 2-19. Reseating a Disk Drive

VST985.vsd



c. Reinsert the disk drive and simultaneously tighten both thumbscrews on the faceplate to secure the drive. Do not overtighten the thumbscrews.

3. Close the enclosure door.

4. Verify that the power interlock of each PMF CRU or IOMF CRU is pushed down to hold the CRU in the slot.

If any power interlocks are loose and if the ejectors on a PMF CRU or IOMF CRU appear unlatched, reseat the CRU. See Step 5.

5. To reseat each PMF CRU or IOMF CRU that is improperly seated:

a. Put on your ESD wriststrap. Attach the grounding clip to an exposed, unpainted metal surface such as the ventilation holes on the PMF CRU or IOMF CRU.

b. Lift the power interlock that holds the PMF CRU or IOMF CRU in the slot.

c. Unlatch the two CRU ejectors simultaneously by pressing the blue-green tabs and pulling outward on the ejectors to unseat the CRU. See Figure 2-20.

Caution. In the next step, reinsert the disk drive CRU slowly. Inserting disk drives rapidly might create physical shock to the CRUs or a power malfunction in the enclosure.

Figure 2-20. Reseating a PMF CRU or IOMF CRU

VST965.vsd



d. Reinsert the PMF CRU or IOMF CRU until the ejectors on the CRU can be engaged into the notches on the enclosure.

e. Latch the two ejectors simultaneously by first pressing the blue-green tabs and then closing the ejectors. This seats the CRU against the backplane.

f. Push down on the power interlock to secure the CRU in the slot.

6. Inspect all SEBs or MSEBs in the system enclosure:

a. Verify that the ejectors on each SEB or MSEB in the enclosure are latched.

b. If any ejectors are unlatched, reseat the SEB or MSEB. See Step 7.

7. To reseat each SEB or MSEB that has become improperly seated during shipping:

a. Put on your ESD wriststrap. Attach the grounding clip securely to an exposed, unpainted metal surface such as the connector nuts on the SEB or MSEB.

b. Unlatch the ejector by pressing the blue-green tab and pulling outward on the ejector to unseat the SEB or MSEB. See Figure 2-21.

c. Reinsert the SEB or MSEB until the ejector on the SEB or MSEB can be engaged into the notch on the enclosure.

d. Latch the SEB or MSEB ejector by pressing the blue-green tab and then closing the ejector to seat the SEB or MSEB against the backplane.

8. Inspect all ServerNet adapters in the system enclosure:

Figure 2-21. Reseating a SEB or MSEB

VST538.vsd



a. Check that the ejectors on each ServerNet adapter in the enclosure are latched.

b. If any ejectors are unlatched, reseat the ServerNet adapter as described next.

9. Perform these steps to reseat each ServerNet adapter that has become improperly seated during shipping:

a. Put on your ESD wriststrap and attach the grounding clip securely to an exposed, unpainted metal surface, such as the power interlock on a PMF CRU or IOMF CRU.

b. Unlatch the ServerNet adapter ejector by pressing the blue-green tab and pulling outward on the ejector to unseat the adapter. See Figure 2-22.

c. Grasp the ServerNet adapter ejector with one hand and slide the adapter halfway out of the slot.

d. Reinsert the ServerNet adapter until the ejector on the adapter can be engaged into the notch on the enclosure.

e. Latch the ServerNet adapter ejector by pressing the blue-green tab and then closing the ejector to seat the adapter against the backplane.

10. Repeat Step 1 through Step 9 for all system enclosures.

Figure 2-22. Reseating a ServerNet Adapter

VST960.vsd


3 Cabling EnclosuresThis section explains how to cable enclosures in NonStop S-series systems with power-on, emergency power-off (EPO), and ServerNet cables.

If you are cabling NonStop S-series enclosures in a ServerNet cluster, see the ServerNet Cluster Manual and the ServerNet Cluster 6780 Planning and Installation Guide.

1. Connect Power-On Cables

1. Print or photocopy the appropriate power-on diagrams for easy reference.

Caution. Installing and cabling IOAM enclosures must be performed by service providers trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

Topic Page1. Connect Power-On Cables 3-1

2. Connect EPO Cables 3-3

3. Connect ServerNet Cables 3-4

Caution. Do not use the handles of CRUs or FRUs for cable management. If you pass cables or cords through the handles of CRUs or FRUs, the cables or cords might become unplugged during later replacement procedures. See Figure 3-3 for proper cabling.

Figure Title PageFigure C-1 Power-On Cabling: Single-High Stacks C-2

Figure C-2 Power-On Cabling: Mixed Single-High and Double-High Stacks C-3

Figure C-3 Power-On Cabling: Multiple-Row Systems C-4

Figure C-4 Power-On Cable: One Processor Enclosure C-5

Figure C-5 Power-On Cables: One Processor Enclosure, One I/O Enclosure C-5

Figure C-6 Power-On Cables: One Processor Enclosure, Two I/O Enclosures C-5

Figure C-7 Power-On Cables: Two Processor Enclosures, No I/O Enclosures C-6

Figure C-8 Power-On Cables: Two Processor Enclosures, One I/O Enclosure C-6

Figure C-9 Power-On Cables: Two Processor Enclosures, Two I/O Enclosures C-6

Figure C-10 Power-On Cables: Three Processor Enclosures, No I/O Enclosures C-7

Figure C-11 Power-On Cables: Three Processor Enclosures, One I/O Enclosure C-7

Figure C-12 Power-On Cables: Three Processor Enclosures, Two I/O Enclosures

C-7

Figure C-13 Power-On Cables: Three Processor Enclosures, Three I/O Enclosures

C-8

Figure C-14 Power-On Cables: Four Processor Enclosures, No I/O Enclosures C-8


Cabling Enclosures 1. Connect Power-On Cables

2. Insert the RJ-11 plug on one end of a power-on cable into the RJ-11 jack on the PMF CRU or IOMF CRU until the tab on the plug clicks into place. See Figure 3-1.

3. Insert the RJ-11 plug on the other end of the power-on cable into the RJ-11 jack on the PMF CRU or IOMF CRU until the tab on the plug clicks into place.

4. Repeat Step 2 and Step 3 for all power-on cables.

5. With the cable ties, secure the power-on cables for each enclosure to the cable support.

Figure C-15 Power-On Cables: Four Processor Enclosures, One I/O Enclosure C-8

Figure C-16 Power-On Cables: Four Processor Enclosures, Two I/O Enclosures C-8

Figure C-17 Power-On Cables: Four Processor Enclosures, Three I/O Enclosures

C-9

Figure C-18 Power-On Cables: Four Processor Enclosures, Four I/O Enclosures C-9

Figure 3-1. Connecting and Securing Power-On Cables

Figure Title Page

RJ-11Plug

VST021.vsd


Cabling Enclosures 2. Connect EPO Cables

2. Connect EPO Cables

1. Connect the unterminated end of an EPO cable to the appropriate junction box or facility wiring.

2. Route the other end of this EPO cable to the service side of the system enclosure.

3. Attach the EPO cable connector to the EPO connector (slot 56) on the enclosure. See Figure 3-2. The connector is designed to be attached only one way.

4. With the cable ties, secure the EPO cables for each enclosure to the cable support.

5. Repeat Steps 1, 2, and 3 for all remaining system enclosures.

Caution. If you pass cables or cords through the handles of CRUs or FRUs, the cables or cords might become unplugged during later replacement procedures. Do not use the handles of CRUs or FRUs for cable management. See Figure 3-3 for proper cabling.

Figure 3-2. EPO Connector on a System Enclosure

56

Emergency Power-Off(EPO) Connector

VST700.vsd


Cabling Enclosures 3. Connect ServerNet Cables

3. Connect ServerNet Cables

1. Print or photocopy the appropriate cabling tables and diagrams for easy reference.

Caution. If you pass cables or cords through the handles of CRUs or FRUs, the cables or cords might become unplugged during later replacement procedures. Do not use the handles of CRUs or FRUs for cable management. See Figure 3-3 for proper cabling.

Keys to Cabling Figures and Tables PageCorrelation Between ServerNet Cable Diagram and One Enclosure B-2

Correlation Between ServerNet Cable Diagram and Two Enclosures B-3

Tetra 8 Topology: Cabling Figures and Tables PageFigure B-3, Maximum Tetra 8 Topologies, X and Y Fabrics B-4

Tetra 8 Cabling: Two Processor Enclosures, Two I/O Enclosures B-17

Tetra 8 Cabling: Three Processor Enclosures, Six I/O Enclosures B-20

One Processor Enclosure, No I/O Enclosures B-15

One Processor Enclosure, One I/O Enclosure B-15

One Processor Enclosure, Two I/O Enclosures B-15

Two Processor Enclosures, One I/O Enclosure B-16

Two Processor Enclosures, Two I/O Enclosures B-16

Three Processor Enclosures, One I/O Enclosure B-17

Three Processor Enclosures, Two I/O Enclosures B-18

Three Processor Enclosures, Three I/O Enclosures B-18

Three Processor Enclosures, Six I/O Enclosures B-20

Four Processor Enclosures, One I/O Enclosure B-21

Four Processor Enclosures, Two I/O Enclosures B-22

Four Processor Enclosures, Three I/O Enclosures B-22

Four Processor Enclosures, Four I/O Enclosures B-23

Tetra 16 Topology: Cabling Figures PageMaximum Tetra 16 Topology, X Fabric B-5

Maximum Tetra 16 Topology, Y Fabric B-6

Tetra 16 Cabling: Four Processor Enclosures, X Fabric B-26

Tetra 16 Cabling: Four Processor Enclosures, Y Fabric B-27

Tetra 16 Cabling: Six Processor Enclosures, X Fabric B-28

Tetra 16 Cabling: Six Processor Enclosures, Y Fabric B-29



2. Connect and route the ServerNet cables between the enclosures and tighten the thumbscrews.

3. Secure the cables to the cable supports using the cable ties, as shown in Figure 3-3. Securing the cables means anchoring them to a cable tie anchor in the cable supports. Cable ties are provided with the cables for the server.

Figure 3-3. Securing ServerNet Cables With Cable Ties

0 2

CableChannel Cable Channel

0 1

Inner Cable-TieAnchor

ServerNet Cables

VST966.vsd

Cable Support(1 of 2)

Cable Guidepost(1 of 2)

Cable Tie




4 Installing Service-Side DoorsThis section describes how to install optional service-side doors on NonStop S-series system enclosures that are already installed and cabled. (New NonStop S-series system enclosures are shipped with service-side doors installed.)

This section does not describe the installation of long doors and side panels. Long doors and side panels are not customer-installable. To install long doors and side panels on existing enclosures, contact your service provider.

If you have not ordered service-side doors, skip this section and go to Section 5, Installing, Starting, and Testing a System Console. Figure 4-4 on page 4-4 shows a service-side door installed on a system enclosure.

To install a service-side door on a system enclosure, perform these steps (you need a Phillips screwdriver):

1. Obtain a service-side door add-on package (for part numbers, see CSSI Web on page xxiii), and verify that it contains these items:

• Adapter frame • Enclosure door, service side (The service-side door is preinstalled on the

adapter frame.) • 6 M5 Phillips screws • 6 M5 KEPS nuts • 1 4-mm diagonal wrench for unlocking the door • Group ID labels • Read Me instructions

2. Remove the door from the adapter frame. Then retrieve the adapter frame, which will be installed first.

3. Align the mounting hooks of the frame with the top, enlarged holes on the cable channels of the enclosure.

4. Push the frame in and down so that the mounting hooks engage. Verify that the frame is supported by and flush against the cable channels.

5. Verify that the four frame and cable channel mounting holes are aligned.


Installing Service-Side Doors

6. Using four M5 Phillips screws and four M5 KEPS nuts, perform these steps for each of the four mounting holes as shown in Figure 4-1.

a. Insert a Phillips screwdriver through the access hole in the frame.

b. Use the screwdriver to insert a Phillips screw through the mounting hole as shown in Figure 4-2:

Figure 4-1. Securing the Frame to the Enclosure Using a Mounting Hole

Figure 4-2. Inserting a Phillips Screw Into the Mounting Hole

Cable Channel

KEPS nut Phillips Screw

FrameScrewdriver AccessHole in Frame

Phillips Screwdriver

Mounting HoleVST098.vsd

VST095.vsd



c. Pull the Phillips screwdriver back out through the access hole in the frame.

d. Use your fingers to install a KEPS nut on the protruding end of the screw, which is in the cable channel.

e. Insert the Phillips screwdriver through the access hole in the frame.

f. Use the screwdriver to tighten the Phillips screw while you hold the KEPS nut in place with your free hand as shown in Figure 4-3.

7. Install the service-side door, including the faceplate and group ID label:

a. Align the top, elongated mounting pin of the door with the top hinge of the frame.

b. Insert that mounting pin partway into that hinge.

c. Verify that the bottom mounting pin of the door is aligned with the bottom hinge of the frame.

d. Lower the door to seat both mounting pins and secure the door to the enclosure.

e. Remove the faceplate from the door.

f. Retrieve the group ID label for the enclosure from the set of labels included with the service-side door add-on package.

g. Insert the group ID label in the faceplate.

h. Reinstall the faceplate on the door.

Figure 4-3. Tightening a Phillips Screw in a Mounting Hole

VST096.vsd



Figure 4-4 shows a system enclosure with a service-side door installed.

Figure 4-4. Service-Side Door Installed on a System Enclosure

VST003.vsd

Enclosure Frame Post

Cable Channel

Adapter Frame

Service Side Door

Faceplate

Group ID Label


5Installing, Starting, and Testing a System Console

This section describes how to unpack, assemble, start, and test a system console.

To install a new system with multiple system consoles, begin with the setup configuration described in Connecting Multiple System Consoles on page 5-11 and Setup Configuration on page 10-2.

After the system console has been started and tested and initial OSM or TSM configuration has been performed, you can connect and configure a backup system console.

Your new system console is shipped with the Microsoft Windows XP Professional operating system already installed. To migrate an existing system console from the Windows 2000 Professional operating system to the Windows XP Professional operating system, see the NonStop System Console Guide for Migrating to Microsoft Windows XP Professional.

Topic PageUnpacking and Assembling a System Console 5-2

Installation Quick Reference 5-2

Finding the Quick Setup Reference Card 5-2

Unpacking the System Console 5-2

Assembling the System Console 5-6

Starting and Testing a System Console 5-8

Powering On a System Console 5-8

Verifying Readiness 5-9

Final Setup Steps 5-9

Operational Considerations for OSM and TSM 5-10

Connecting Multiple System Consoles 5-11

System Console Function Keys 5-12



Installing, Starting, and Testing a System Console Unpacking and Assembling a System Console

Unpacking and Assembling a System ConsoleThis subsection describes how to unpack and assemble system console components. The instructions direct you to unpack all equipment before connecting components.

Installation Quick ReferenceIf you are already familiar with installing system consoles, use the system console tasks in Section E, FastPath Tasks: Required as a checklist. If you are not installing a system console in the setup configuration (where one system console manages one system), go to Section 10, Configuring the System, for the appropriate connection procedure.

Finding DocumentationDocumentation is available in the NonStop Technical Library (NTL). For the location of NTL, see Where to Get More Information on page xxiii.

Finding the Quick Setup Reference CardLook for the quick setup reference card as you unpack the system console hardware and software. This reference card is included in the accessories box and contains an up-to-date illustration of the back panel for your model of the system console. The reference card shows the location of connectors.

Unpacking the System Console PCs provided by HP to be used as system consoles come preloaded with the client components necessary to use OSM software (TSM client components can be installed), but some assembly of components is required. Hardware and software are delivered in various shipping boxes containing the components listed in Table 5-1 on page 5-3. Some hardware is optional, so your shipment might not contain all items listed.

Save all shipping boxes and packing material so you can repack components for shipment if necessary.

Topic PageInstallation Quick Reference 5-2

Finding Documentation 5-2

Finding the Quick Setup Reference Card 5-2

Unpacking the System Console 5-2

Assembling the System Console 5-6


Installing, Starting, and Testing a System Console Unpacking the System Console

You might also receive a kit to adapt the modem to your local telephone service.

Table 5-1. Contents of the Shipping BoxBox ContentsSystem unit box Accessory box

Keyboard box

System unit (processor)

Accessory bag (packaged in system unit box)

System unit power cord

Mouse with attached cable

Quick setup reference card

HP Restore CD

Microsoft Windows XP Professional CD --

The Certificate of Authenticity for Microsoft Windows XP Professional (In the form of a sticker attached to the PC)

Documentation

Keyboard box (packaged in system unit box)

Keyboard with attached cable

PC accessory box

50-foot (15-meter) Ethernet cable

System console binder

Assorted software media and documentation

Display monitor box

Display monitor with attached interface cable

Display monitor power cord

Documentation for the display monitor

Ethernet switch box

Documentation for the Ethernet switch

The Ethernet switch and 4 cables are included in the OPEN FIRST box.

Serial Modem USB ModemModem box (The serial modem itself is included

in the OPEN FIRST box)

Wall-to-modem telephone cable

Modem power converter with integral power cord

Documentation for the modem

USB modem

Wall-to-modem telephone cable

USB cable

Documentation for the modem



Unpack the System Unit Box1. Open the system unit box and remove any loose packing material.

2. Locate the accessory box in the system unit box.

3. Unpack the accessory box:

a. Open the accessories box and remove any loose packing material.

b. Remove all items including documentation packed with the mouse. For a list of items, see Table 5-1, Contents of the Shipping Box, on page 5-3.

4. Retrieve the keyboard box from the system unit box.

5. Unpack the keyboard box:

a. Open the keyboard box and remove any loose packing material, being careful to retain the documentation packed with the keyboard.

b. Remove the keyboard and attached cable.

6. Carefully remove the system unit and place it on a stable flat surface.

Unpack the PC Accessory Box1. Open the PC accessory box and remove any loose packing material.

2. Remove the Ethernet cable, but do not connect it at this time.

3. Remove the system console binder.

4. Store the software media for future reference.

System consoles come preloaded with software. Store the backup software packaged with the workstation for emergencies. To restore software on the system console hard disk, use the CD-ROM shipped with the system console. Retain the documentation packed with the accessories for future reference.

Unpack the Display Monitor Box

1. Open the display monitor box and remove any loose packing material.

2. Retain the documentation packed with the display monitor for future reference.

3. Remove the display monitor power cord.

4. Carefully remove the display monitor and its attached interface cable and place it on its swivel base on a stable flat surface.

Do not connect the power cord to a power outlet or connect the display monitor interface cable to the system unit at this time.

WARNING. Some display monitors are heavy. Use at least two people to lift the display monitor out of the shipping box and set it on a flat surface.



Unpack the Ethernet Switch BoxIf no Ethernet switch is included with your system, the switch and cables are included in the OPEN FIRST box. Go to Unpack the Modem Box.

1. Open the Ethernet switch box and remove any loose packing material.

2. Retain the Ethernet switch documentation for future reference.

3. Do not connect the power cord to a power outlet at this time.

Unpack the Modem BoxDepending on your order, a modem might not be included with your system console:

If no modem is included with your system console or OPEN FIRST box, go to Final Unpacking Steps on page 5-5.

1. Open the modem box and remove any loose packing material.

2. If the modem is present, remove it.

3. Retain the documentation packed with the modem for future reference.

4. Remove the wall-to-modem telephone cable.

5. Remove the USB modem cable.

6. Remove the modem power converter with integral power cord if it is present.

7. Your modem is a USB modem with these characteristics:

• Ships with PC workstations

• Usually connects to the front USB port on the workstation

• Powered through the USB connection, so it requires no converter

Final Unpacking StepsWhen you have unpacked all required items:

1. Verify that all items are removed from the shipping boxes.

2. Store all documentation in a safe place for future reference.

3. Remove the boxes and packing material from the work area. Save boxes and packing material so that you can repack the components for shipment if necessary.

4. Go to Assembling the System Console on page 5-6.


Installing, Starting, and Testing a System Console Assembling the System Console

Assembling the System ConsoleThese procedures describe how to assemble the unpacked components into a system console. To connect other devices such as a printer to your system console, see the documentation provided with the printer or the system console.

Tools Depending on the PC model shipped as the system console, you might need a small, slotted screwdriver for tightening cable connectors.

Connect the System Console Components1. Connect the display monitor interface cable to the video port on the back of the

system unit.

For the location of the video port, see the quick setup reference card.

2. Connect the keyboard to the back of the system unit:

a. To locate the keyboard connector, use the quick setup reference card. On some workstation models, the keyboard attaches to the PC through a Universal Serial Bus (USB) port.

b. Align the notch on the keyboard cable connector with the keyway on the system unit.

3. Connect the mouse to the system unit:

a. To locate the mouse port, use the quick setup reference card. On some workstation models, the mouse attaches to the PC through a USB port.

b. Align the notch on the cable connector with the keyway on the mouse port.

Connect the System Console to a Power SourceTo connect system console power cords to power outlets or to a surge suppressor:

1. Ensure that the voltage selection switch on the back of the system unit is set to the correct voltage.

2. Connect the display monitor power cord to the receptacle at the back of the monitor.

3. Connect the plug of the display monitor power cord to a grounded power outlet.

4. Plug the system unit power cord into the power cord outlet. To locate the system unit power cord outlet, use the quick setup reference card.

5. Connect the other end of the system unit power cord to a grounded power outlet.

Caution. To prevent data corruption and equipment failure, provide surge suppression or backup power facilities for the system console, modem, and Ethernet switch.


Installing, Starting, and Testing a System Console Assembling the System Console

Connect the Modem

Modems are recommended for primary and backup system consoles.

1. Use the USB cable to connect the modem to the USB port on the front of the workstation.

2. Connect the modem to the telephone line:

a. Plug one end of the wall-to-modem telephone cable into the telephone wall jack.

b. Plug the other end of the cable into the LINE connector on the back of the modem.

3. Connect a telephone adapter if necessary.

4. If instructed to do so by the documentation shipped with the modem, verify the installation.

If No Modem Is IncludedFor system consoles that are not used as primary or backup system consoles, modems are optional. If the system console you are installing does not have a modem, go to Starting and Testing a System Console on page 5-8.

Caution. To prevent equipment failure and data corruption, plan for the possibility of power outages. Provide surge suppression or backup power facilities for modems and Ethernet switches.

Note. To use ISEE, a web-based alternative to modem dial-outs, go to the CSSI Web and click ISEE for NonStop to learn about ISEE prerequisites and NonStop-specific details that you will need before downloading and configuring the ISEE client from the HP Hardware Support Services Web. A link to the CSSI Web can be found in the left navigation area of the NTL home page.


Installing, Starting, and Testing a System Console Starting and Testing a System Console

Starting and Testing a System ConsoleThis subsection describes how to power on a system console and ensure that it is operating properly. You start and test a system console before you start the server, connect the workstation to the dedicated LAN, and configure the OSM or TSM environment.

If you encounter problems with any of the procedures described in this subsection, see the diagnostic and corrective procedures provided in Appendix D, Troubleshooting.

Powering On a System ConsoleIf you received an Ethernet switch, you do not need to install or power on the switch until you connect the system console to the network. See Section 10, Configuring the System.

Be sure to power on the system console components in the order described here:

1. Power on the modem.

If your system console has a modem, see the documentation included with the modem for instructions on powering on and testing the modem.

2. Power on the display monitor.

Power on the display monitor by pressing the power switch on the display monitor. Within a few seconds, the display should become visible.

3. Power on the system unit.

Power on the system unit by pressing its power switch. To find the power switch, see the documentation included with the system unit.

Task PagePowering On a System Console 5-8

Verifying Readiness 5-9

Final Setup Steps 5-9

Operational Considerations for OSM and TSM 5-10

Connecting Multiple System Consoles 5-11



Installing, Starting, and Testing a System Console Verifying Readiness

Verifying ReadinessAfter you power on a system console, the console executes a set of startup hardware diagnostics. After the OS logo appears:

1. When prompted, press Ctrl-Alt-Delete to log on.

2. A logon screen shows the user name/administrator and password blank. Leave the password blank and click OK to complete logon.

The desktop appears, listing software applications in the form of icons.

The software on the system console hard disk has been installed to operate this workstation for NonStop servers. This configuration must be maintained in the user environment. Altering this configuration is not supported. Neither is loading and using software not approved for the system console. For a list of approved software, see Preloaded Hardware and Software on page 1-49.

If the operating system fails to load properly, see Appendix D, Troubleshooting.

Final Setup StepsThis subsection describes the final setup steps:

Restart the System Console1. From the Task Bar, click Start.

2. Select Shut Down.

3. Select Restart the computer.

4. Click Yes.

5. Observe the startup process again. It should be the same process described under Verifying Readiness on page 5-9, ending with the display of application icons on the desktop.

Action Procedure PageEnsure the system console can be powered down and restarted in the same condition.

Restart the System Console 5-9

If necessary, create an emergency repair disk or automated system recovery disk.

Create an Emergency Repair Disk (ERD) or Automated System Recovery (ASR) Disk

5-10


Installing, Starting, and Testing a System Console Operational Considerations for OSM and TSM

Create an Emergency Repair Disk (ERD) or Automated System Recovery (ASR) DiskThe ERD (for Windows 2000) or ASR disk (for Windows XP) saves repair information that you can use to reconstruct your Windows system files, system configuration, and startup environment variables if they are corrupted.

The OSM or TSM Low-Level Link and OSM or TSM Notification Director save important configuration information to the operating system registry. To back up this information, you must create (or update) an ERD or ASR for your workstation.

Use the backup procedure in the Windows 2000 or XP documentation shipped with your system console.

Operational Considerations for OSM and TSMYou now have an operational system console. Under normal circumstances, a system console should be left running, but:

• To prevent unauthorized operations, log off any OSM or TSM software when you are not using the workstation.

• If the display monitor is idle more than 20 minutes, the power save feature is enabled, putting the monitor into standby mode. The monitor screen goes blank, and the monitor power LED turns yellow or amber.

• For TSM, a user has to remain logged on to the system console at all times for the Notification Director application to receive and dial out incident reports. An important enhancement for the OSM Notification Director is that it can be configured to run as a Windows service, so it will start whenever the Windows operating system starts up and will function even without a user being logged on to Windows.

If you obtain results different from those described in the procedures in this section, verify that you have properly performed the procedures in this section and in Unpacking and Assembling a System Console on page 5-2. If you still have difficulty after this verification, follow the instructions in Appendix D, Troubleshooting.


Installing, Starting, and Testing a System Console Connecting Multiple System Consoles

Connecting Multiple System ConsolesIf you are installing a new system with multiple system consoles, you must create the setup configuration before you can add a second system console. The setup configuration is one server connected to one system console. See Figure 5-1.

It is recommended that you do not allow the setup configuration to serve as your permanent working configuration because it lacks fault tolerance. After you start and test the system, and perform the initial OSM or TSM configuration, add fault tolerance to the setup configuration by connecting a backup system console and a second Ethernet switch (you can also use an Ethernet hub). This recommended operating configuration is discussed in Section 10, Configuring the System.

Figure 5-1. Setup Configuration

VST992.vsd

System Console

EthernetSwitch

NonStopS-SeriesServer

ModemRemote Service

Provider


Installing, Starting, and Testing a System Console System Console Function Keys

System Console Function KeysThe keyboard provided with a system console contains function keys F1 through F12. Some applications that you access using the OutsideView terminal emulator software require function keys F13 through F16 or SF13 through SF16.

The terminal emulator software provides two ways for you to obtain these functions:

• Click one of the icons for F13 through F16 or SF13 through SF16 on the terminal emulator tool bar.

• Use a key combination:

These key combinations are valid only with the OutsideView terminal emulator.

For this function key… Use this key combination…F13 Alt + F3

F14 Alt + F4

F15 Alt + F5

F16 Alt + F6

SF13 Shift + Alt + F3





6 Connecting a System ConsoleThis section describes how to connect a primary system console to the installed server and dedicated LAN by using Ethernet cables and an Ethernet switch or Ethernet hub.

The connection instructions in this section work for both OSM and TSM software. For additional connectivity options to increase performance (reduce response time) for the OSM Service Connection, see the OSM Migration Guide.

Because these steps involve communication between the primary system console and the master service processors (MSPs) in the server, you must complete these steps before you power on and start the system.

Topic PageThe Dedicated LAN 6-2

Installing Ferrite Cores 6-4

Installing the Ethernet Switch or Hub 6-5

Connect the Ethernet Switch or Hub to the Server 6-5

Connect the System Console to the Ethernet Switch or Hub 6-6

Note. An IOAM enclosure connects to the system console using a managed Ethernet switch that must be configured by your service provider. Information is available to your service provider in the Modular I/O Installation and Configuration Guide.

For Information About See NotesConnecting a system console and system to the nondedicated (public) LAN

Nondedicated (Public) LAN Configuration on page 10-16

• This practice provides flexibility in locating system consoles.

• A nondedicated (public) LAN cannot be used to connect a primary or backup system console to the server.

Adding a backup system console

Section 10, Configuring the System

Perform this procedure only after you have started the system, tested the system, and performed initial OSM or TSM configuration.


Connecting a System Console The Dedicated LAN

The Dedicated LANYou must connect the system console that is being used as the primary system console to a private, dedicated LAN. A dedicated LAN:

• Connects the primary and backup system consoles to the server

• Connects system consoles to the Ethernet ports on the PMF CRUs of a server

• Supports NonStop S-series servers but does not support other types of servers or servers made by other vendors

• Supports system consoles, but does not support other types of workstations or workstations made by other vendors

• Allows access to OSM or TSM applications by a workstation connected to a dedicated LAN

• Allows access for system consoles connected to a dedicated LAN to all dial-in and dial-out operations and incident reports generated by the server

• Is constructed of Ethernet switches or hubs

Server Connection to a LANNonStop S-series servers offer several Ethernet connections, but the dedicated LAN must be connected to the Ethernet ports on the PMF CRUs in group 01. Figure 6-1 shows the service side of a processor enclosure with PMF CRU RJ-45 Ethernet connections.

The PMF CRU Ethernet ports in the group 01 enclosure are used only for the dedicated LAN. Do not use the Ethernet ports for PMF CRUs or IOMF CRUs in any other processor enclosures. Ethernet connections other than those for the dedicated LAN must use ServerNet adapters.

Caution. If you are using ProCurve 24-port (managed) Ethernet switches for your dedicated OSM or TSM service LAN, you should configure the switch ports that are used for connecting to PMF CRUs—and only those ports—to protect the services processors from possible overload. See Configuring a ProCurve 24-Port Ethernet Switch on page D-48 for the procedure. This procedure is not needed and does not apply to ProCurve 8-port (unmanaged) switches.


Connecting a System Console System Console Connection to a Dedicated ServiceLAN

System Console Connection to a Dedicated Service LANSystem consoles communicate with your NonStop servers through a dedicated service LAN. A network interface card (NIC) inside the system console connects the workstation to the dedicated LAN (connect a port on the NIC to an Ethernet switch or hub).

The quick setup reference card included with the workstation shows the location of this port at the back of the system console.

System Console Connection to a Secure Operations LANTo take advantage of ISEE functionality, a second NIC (or USB ethernet adapter cable) is used to connect the console to a secure operations LAN. For more information, go to the CSSI Web and click ISEE for NonStop to learn about ISEE prerequisites and NonStop-specific details that you will need before downloading and configuring the

Figure 6-1. Processor Enclosure PMF CRU Ethernet Ports

Ethernet Port

VST525.vsd


Connecting a System Console Ethernet Cables

ISEE client from the HP Hardware Support Services Web. A link to the CSSI Web can be found in the left navigation area of the NTL home page.

Ethernet CablesTo make Ethernet connections for a dedicated LAN, use Category 5 unshielded twisted pair (UTP) 10Base-T cables with RJ-45 connectors.

Ethernet Switch PortsSeveral procedures in this section involve connecting Ethernet cables to ports on the Ethernet switch or hub. Do not connect an Ethernet cable to the cascade port (sometimes called the uplink port) on the Ethernet switch or hub unless specifically instructed to do so. These ports are used for cabling additional switches. To determine which ports to use, see the documentation provided with the Ethernet switch or hub.

Installing Ferrite CoresIf any ServerNet adapter, PMF CRU, IOMF CRU, or IOM 2 CRU in the system connects to a cable with an RJ-45 connector, you should install two ferrite cores on that cable.

1. Find a place on the cable within 4 or 5 feet of the connection to the adapter or CRU.

2. Attach the ferrite cores at that location:

The ferrite cores are split, and open up into two pieces. To install a ferrite core, pass the RJ-45 cable through the core twice by wrapping the cable around the core and then closing the core jacket around the cable.

Space the cores no more than 12 inches apart from each other on each cable.

If you don’t have enough ferrite cores:

1. Count the number of cables terminating in RJ-45 connectors that are connected to every adapter in the system.

2. Multiply that number by 2.

3. Subtract from that number the number of ferrite cores included with the adapters.

4. That number is the quantity of ferrite cores to order.

For the part number for a ferrite core, see the CSSI Web or the NonStop S-Series Planning and Configuration Guide.


Connecting a System Console Installing the Ethernet Switch or Hub

Installing the Ethernet Switch or HubInstall the Ethernet switch or hub using the documentation that came with the switch or hub. You can position switches or hubs on a tabletop, under a table, or on a wall.

Connect the Ethernet Switch or Hub to the ServerConnect the Ethernet switch or hub to the server, using the setup configuration illustrated in Figure 5-1 on page 5-11:

1. Connect one end of an Ethernet cable to the Ethernet port on the PMF CRU in slot 50 of group 01. (The group number appears on both sides of an enclosure.)

To make the connection, insert the RJ-45 plug on the cable into the RJ-45 jack on the PMF CRU until the tab on the plug clicks into place. See Figure 6-2 on page 6-6.

2. Connect the other end of this Ethernet cable to a port on the Ethernet switch or hub.

Do not connect this Ethernet cable to the cascade port on the Ethernet switch or hub. These ports are used for cabling additional switches or hubs. To determine which ports to use, see the documentation that came with the switch or hub.

3. Connect one end of another Ethernet cable to the Ethernet port on the PMF CRU in slot 55 of group 01. See Step 1.

4. Connect the other end of this Ethernet cable to another port on the Ethernet switch or hub. See Step 2.

Caution. If you are using ProCurve 24-port (managed) Ethernet switches for your dedicated OSM or TSM service LAN, you should configure the switch ports that are used for connecting to PMF CRUs—and only those ports—to protect the services processors from possible overload. See Configuring a ProCurve 24-Port Ethernet Switch on page D-48 for the procedure. This procedure is not needed and does not apply to ProCurve 8-port (unmanaged) switches.

Note. To maintain the EMC compliance of all NonStop S-series systems except the S7000, the Ethernet cables must be equipped with a ferrite suppression component (ferrite bead) built into one end of the cables. Install the Ethernet cables that connect PMF CRUs to Ethernet switches or hubs with the ferrite-bead end of the cables connected to the PMF CRUs. See Figure 6-2 on page 6-6.


Connecting a System Console Connect the System Console to the Ethernet Switchor Hub

Connect the System Console to the Ethernet Switch or Hub1. Connect one end of an Ethernet cable to the 10Base-T connector on the NIC at the

back of the system unit. To locate the NIC connector, see the quick setup reference card.

2. Connect the other end of this Ethernet cable to a port on the Ethernet switch or hub. See Figure 6-2. See Step 2 in Connect the Ethernet Switch or Hub to the Server on page 6-5.

3. Set the medium-dependent interface (MDI) switch on the Ethernet switch or hub to MDI mode. To determine how to set this switch, see the documentation that came with the Ethernet switch or hub.

Figure 6-2. Connections for the Setup Configuration

Ethernet Port

Network InterfaceCard (NIC) onSystem ConsoleEthernet

Switch

Cascade Port

Ferrite Bead

RJ-45Plug

VST519.vsd


7Installing External System Devices

This section describes how to install selected peripheral devices such as tape subsystems.

Growing numbers of storage, communications, and network options are available for NonStop S-series servers. This section mentions some devices briefly, such as ServerNet wide area network (SWAN) concentrators. For detailed installation information about products not covered in this guide, see the manuals for those products.

Several different adapters are supported. For instructions on installing adapters, see the manual for that adapter. For supported adapters, see the part number lists on the CSSI Web. See CSSI Web on page xxiii.

Installing Tape DrivesInstall a tape drive only after you install the system enclosures, connect the ServerNet cables, and connect the primary system console to the system. However, it is recommended that you connect the tape drive before you start the system. With a tape drive connected to a server, you can use the BACKUP and RESTORE utilities to save data to and restore data from tape. With a tape drive connected to the PMF CRU in the group 01 enclosure, you can dump processor memory to tape to diagnose a processor halt.

To install a tape drive, see:

• Installing a 5175 Open-Reel Tape Subsystem on page 7-2

• Installing a 519x Cartridge Tape Subsystem on page 7-9

• Installing Other Tape Devices on page 7-12

For information about which tape products are supported for this RVU, see the G06.nn Release Version Update Compendium or the NonStop S-Series Planning and Configuration Guide.

Topic PageInstalling Tape Drives 7-1

Installing a SWAN or SWAN 2 Concentrator 7-15

Installing an AWAN Server 7-15

Installing Printers and Terminals 7-16


Installing External System Devices Installing a 5175 Open-Reel Tape Subsystem

Installing a 5175 Open-Reel Tape SubsystemA 5175 tape subsystem is an open-reel tape drive in a module on a modular storage system pedestal as shown in Figure 7-1.

Tape products can be installed by customers when shipped as a self-contained module (or as two modules) on a pedestal. Of the 517x tape subsystems, only the 5175 tape subsystem is customer installable. Other maintenance or changes to an installed 5175 tape subsystem require a trained service provider. Likewise, a trained service provider must install other 517x tape subsystem configurations.

1. To unpack and install a 5175 tape subsystem, you need:

• Small slotted screwdriver• A 15/16-inch (24-mm) or adjustable, open-end wrench

2. If you have a 517x tape subsystem currently connected to another system and you want to connect it to a server, ask your service provider to ensure the tape drive firmware is at the firmware or hardware version levels listed in Table 7-1.

Figure 7-1. 5175 Tape Subsystem

Table 7-1. 517x Firmware RequirementsComponent Firmware or Hardware VersionDisplay board 6.40

Control board 6.77 or 6.78

Buffer board 6.80

SCSI interface board 6.74 (6.xx firmware)

Module

Pedestal

Tape Drive CRU

VST544.vsd



3. If you are connecting a new 5175 tape subsystem, unpack the subsystem:

a. Remove any protective covering or packing material from outside the tape subsystem.

b. Flip open the twist-lock handles at the base of the pallet. Turn the twist-lock handles counterclockwise to loosen the pallet end piece as shown in Figure 7-2.

c. Remove the pallet end piece and set it aside, but save the U-bolts or Velcro straps. These bolts or straps hold the unloading ramp against the pallet.

d. Set the unloading ramp next to the pallet.

e. If you have Velcro straps, use them to fasten the unloading ramp to the pallet. Otherwise, insert U-bolts in the drilled holes in the pallet and the ramp to secure the ramp against the pallet, forming an incline for rolling the tape subsystem off the pallet.

4. Use two people to carefully roll the tape subsystem off the pallet and down the ramp.

Figure 7-2. Unloading a Tape Subsystem

WARNING. To avoid strain or injury, always use two people to unload and move the tape subsystem. A 5175 tape module on a pedestal can weigh up to 330 pounds (150 kilograms).

Tape Subsystem(Side View)

Insert U-Bolts Here

Unloading Ramp

Twist-Lock Handles

End Piece

VST022.vsd



5. Position the subsystem pedestal next to your system. See the Floor Plan Diagram in the Installation Document Checklist. You must position the pedestal:

• Close enough to the system enclosure to allow the subsystem to be connected to the PMF CRU or IOMF CRU. Cables range from 10 to 75 feet (3 to 23 m) long.

• Within 15 feet (4.6 m) of the power receptacle for the subsystem. You cannot use a power receptacle already dedicated to a system enclosure.

• With a service and ventilation clearance of 24 inches (61 cm) at the rear of the subsystem and 36 inches (92 cm) at the front.

6. Remove the shipping restraints from inside the 5175 module as shown in Figure 7-3 on page 7-5.

a. Grasp the hand hold at the top of the module back panel and pull the back panel down. The panel is hinged at the bottom.

b. Remove the shipping restraint (a metal plate) using the instructions on the plate.

c. With a slotted screwdriver, remove the four slide-retaining screws. The screws are located in an oval hole about two inches from the rear of the module.

d. Close the back panel, pushing firmly at the top to seat the fasteners.

e. Grasp the sides of the module front panel and pull it off.

f. Remove the shipping restraint (a metal plate) using the instructions on the plate.

g. Replace the front panel. Push firmly at the top and bottom of the panel to seat it.



7. On the pedestal, lower the legs, which are located next to each caster:

a. Turn each leg counterclockwise with your fingers until it touches the floor.

b. With a 15/16 inch (24 mm) wrench, turn the nut until the pad rests firmly on the floor.

Figure 7-3. Removing the Shipping Restraints From a 5175 Tape Subsystem

Front Panel

BackPanel

Shipping Restraint

VST019.vsd

Shipping Restraint



8. Install the pedestal top panel and corner caps as shown in Figure 7-4:

a. Position the pedestal top panel (packed separately) on top of the 5175 module, aligning the edges.

b. Position a red corner cap (packed separately) at each corner of the top panel, aligning the edges with the pedestal frame. Push down firmly to secure each cap. The four caps hold the top panel in place. Each cap fastens to the frame with a push/pull fastener.

9. Locate the tape subsystem SCSI cable, which is packed separately. For cable lengths and their corresponding part numbers, see the CSSI Web. See CSSI Web on page xxiii.

10. Connect the SCSI cable to the tape subsystem:

a. Open the back panel of the 5175 module.

b. Find the uncapped SCSI port at the rear of the tape drive CRU.

Figure 7-4. Installing the Top Panel and Corner Caps on a 5175 Tape Subsystem

Top Panel

VST557.vsd

Red Corner Cap(4 places)



c. Using the SCSI cable connector with the latch-clip flanges, attach the SCSI cable to the uncapped SCSI port, and latch the clips as shown in Figure 7-5.

11. Attach the SCSI cable to the NonStop S-series server. See Attaching a Tape Drive to the NonStop S-Series Server on page 7-14.

12. Connect the AC power cord:

a. Remove the shipping restraint for the AC power cord.

b. On the lower left side of the front panel of the tape subsystem, make sure the standby push-button switch is in the OFF position.

c. Plug one end of the AC power cord into the AC power receptacle at the rear of the tape drive CRU as shown in Figure 7-6 on page 7-8.

d. Plug the other end of the AC power cord into the designated power receptacle.

e. Close the back panel of the 5175 module. The panel is hinged at the bottom and held in place at the top with push/pull fasteners.

13. Push the AC power switch as shown in Figure 7-6 on page 7-8.

Figure 7-5. Connecting a SCSI Cable to a 5175 Tape Subsystem

SCSICable

Terminated(Capped)SCSI Port

Rear of 5175 Tape Drive CRU

LatchClip

Latch-ClipFlange

UncappedSCSI Port

VST961.vsd



Figure 7-6. AC Power Switch for 5175 Tape Drive CRU

AC PowerSwitch

AC Power Cord

Rear of 5175 Tape Drive CRU

VST533.vsd


Installing External System Devices Installing a 519x Cartridge Tape Subsystem

Installing a 519x Cartridge Tape SubsystemA 519x cartridge tape subsystem is a cartridge tape drive in a module on a storage pedestal as shown in Figure 7-7.

About Installing a 519X Tape Subsystem• For information on unpacking and installing the 519x tape drives, see the

5190/5194 Modular Tape Subsystem Manual.

• A 519x tape subsystem that is shipped with the modular storage system pedestal is customer-installable. However, some maintenance or changes to an installed subsystem require a trained service provider. For more information, see the 5190/5194 Modular Tape Subsystem Manual.

• To disconnect an installed 519x tape subsystem and reconnect it to another server, ensure that the firmware or hardware in your tape subsystem is at these version levels or higher:

Figure 7-7. 519x Tape Subsystem

Tape Drive Firmware or Hardware Version5190 097673-A05-07

5190ACL 097671-A08-11

5194 113644-A03-03

5194ACL 113643-A05-05

VST556.vsd

AutomaticCartridgeLoader(ACL)

Module



Installing a 519X Tape Subsystem1. Connect the SCSI cable to the tape subsystem. See Figure 7-8.

a. Open the rear bezel door of the tape module:

1. Pull on the blue-green handle at the top of the door. 2. Lower the door to a horizontal position. 3. Pull up on the spring-loaded plungers to release the hinges.4. Remove the door from the module.

b. Find the tape subsystem SCSI cable. For cable lengths and their corresponding part numbers, see the CSSI Web. See CSSI Web on page xxiii.

Figure 7-8. Connecting a SCSI Cable to a 519x Tape Subsystem

SCSI Terminatoron Port

UncappedSCSI Port

SCSICable

Rear of 519x Module

VST558.vsd



c. Find the uncapped SCSI port at the rear of the tape drive CRU. The uncapped port is the SCSI port that does not have a SCSI terminator installed. See Figure 7-8.

d. Using the SCSI cable connector with the latch-clip flanges, attach the SCSI cable to the uncapped SCSI port and latch the clips.

e. Route the cable following the instructions in the 5190/5194 Modular Tape Subsystem Manual.

2. Attach the SCSI cable to the NonStop S-series server. See Attaching a Tape Drive to the NonStop S-Series Server on page 7-14.

3. Connect the AC power cord using instructions in the 5190/5194 Modular Tape Subsystem Manual.

4. Push the AC power switch.


Installing External System Devices Installing Other Tape Devices

Installing Other Tape Devices Product Number Description Manual5142 Digital audio tape

(DAT) drives5142-xSE Rackmount Tape Subsystem User Guide

Models 5142 and 5142ACL 4mm Tape Drive Subsystems User Guide (available in hardcopy only)

515x Digital linear tape (DLT) drives

5150/5151 Digital Linear Tape Subsystems Installation and Users Guide Manual in the Third-Party Documentation Directory

5157/5157ACL S-Series Digital Linear Tape Subsystems Installation/Users Guide

5158ACL S-Series Digital Linear Tape Subsystem Installation/Users Guide

9710 (StorageTek) Addendum for NonStop Servers

5159 Cartridge tape drive in L700 tape library

L700 (CTL700) Installation and Operations guide (located in the Hardware Service and Maintenance Publications Library). Contact your service provider.

5242, 5242ACL

Digital audio tape (DAT) drives

DAT 72 (Models 5242 and 5242ACL) Tape Drive User’s Guide

5242-2SE Digital audio tape (DAT) unit

DAT 72 Model 5242-2SE Rackmount Tape Unit User’s Guide

525x High performance DLT

5257/5257ACL Installation and User’s Guide for S-Series Tape Enclosures

5258 ACL Installation and User’s Guide

5259 High performance DLT drive in L700 tape library

L700 (CTL700) Installation and Operations guide (located in the Hardware Service and Maintenance Publications Library). Contact your service provider.

9490 Cartridge tape drives

Documentation is shipped with the tape drive. Contact your service provider.

CT9840-1 Cartridge tape drive in L700 tape library

L700 (CTL700) Installation and Operations Guide

CT9840-2 Cartridge tape drive in 9710 tape library

9840 (CT9840-2) Installation Guide for the 9710 ACS

CT9840-3 Cartridge tape drive in tape enclosure

9840 (CT9840-3) Installation and Users Guide for NonStop S-Series Tape Enclosures

CT9840-4 Cartridge tape drive in 9310 tape library

Documentation is shipped with the tape drive.


Installing External System Devices Installing Other Tape Devices

Other manuals for these tape drives are listed in the Third-Party Documentation Director.

CT9840FC-1 Fibre channel tape drive in L700 tape library

L700 (CTL700) Installation and Operations Guide

CT9840FC-3 Fibre channel tape drive in tape enclosure

9840 (CT9840-3) Installation and Users Guide for NonStop S-Series Tape Enclosures

CT9840FC-4 Fibre channel tape drive in 9310 tape library

Documentation is shipped with the tape drive.

VT5801 Virtual tape server

Virtual Tape Solution Installation Guide (Tributary Systems)Virtual Tape Manager Installation and User’s Guide (Tributary Systems)

VT5900-A Virtual tape server

Virtual TapeServer Installation Guide (Tape Labs) (located in the NTL Hardware and Service Maintenance Collection. See your service provider.)Virtual TapeServer Operations and Administration Guide (Tape Labs)

VT5900-B Virtual tape server


VT5900-C Virtual tape server






N.A. Any tape drive attached to a ServerNet/DA

6760 ServerNet/DA Manual


Installing External System Devices Attaching a Tape Drive to the NonStop S-SeriesServer

If this documentation collection does not contain the manual for your tape library, contact your service provider.

Attaching a Tape Drive to the NonStop S-Series ServerTo attach a tape drive to any PMF CRU or IOMF CRU:

1. Determine which PMF CRU or IOMF CRU should be connected to the tape drive.

2. Using the SCSI cable connector with the thumbscrews, plug the other end of the SCSI cable into the differential SCSI port on the appropriate PMF CRU, IOMF CRU, or IOMF 2 CRU.

• NonStop S7000, S7400, S70000, and S72000 PMF CRUs and IOMF CRUs are equipped with an external SCSI passthrough terminator. Attach the SCSI cable to this SCSI passthrough terminator, which is factory-installed on the differential SCSI port.

• On some CRUs, the SCSI terminator is inside the CRU. In this case, attach the tape drive cable to the external connector.

The CRUs that contain an internal SCSI terminator include:

° IOMF 2 CRUs° S7x00 PMF CRUs of model S7600 and higher° Sxx000 PMF CRUs of model S74000 and higher

3. Tighten the thumbscrews on the cable connector by hand or use a small slotted screwdriver.

To attach tape drives to a 6760 ServerNet device adapter, see the 6760 ServerNet/DA Manual.

To Determine the Configuration of ... See ...Components that are factory-configured The SCF configuration file

($SYSTEM.ZSYSCONF.SCF0000) printout shipped with your server

A system that has been started, or components that have been installed and configured

SCF Reference Manual for G-Series RVUs

Caution. Never remove the SCSI passthrough terminator from the differential SCSI port. The SCSI passthrough terminator must be in place to a connect a tape drive to these PMF CRUs or IOMF CRUs. If it is not present, contact your service provider.


Installing External System Devices Installing a SWAN or SWAN 2 Concentrator

Installing a SWAN or SWAN 2 ConcentratorThe ServerNet wide area network (SWAN) concentrator communications device or the SWAN 2 concentrator communications device connects to a server using a pair of Ethernet local area networks (LANs). The SWAN concentrator or the SWAN 2 concentrator provides WAN connections supporting both synchronous and asynchronous data over a variety of electrical interfaces. The SWAN concentrator or the SWAN 2 concentrator can be installed in a 19-inch rack or on a desk or tabletop.

Install the SWAN concentrator or the SWAN 2 concentrator after the system is powered on, tested, and running the operating system. For information about installing or configuring a SWAN concentrator, see the SWAN Concentrator Installation and Support Guide. For information about installing or configuring a SWAN 2 concentrator, see the SWAN 2 Concentrator Installation and Support Guide.

You can install any SWAN or SWAN 2 concentrator by using the WAN Wizard Pro application. Depending on the RVU, you gain access to the WAN Wizard Pro through the taskbar on your system console by using one of the following methods:

• For G06.21 RVU and later RVUs:

Start>Programs>HP WAN Wizard Pro>WAN Wizard Pro

• For G06.20 RVU and earlier RVUs:

Start>Programs>Compaq TSM>Guided Configuration Tools>WAN Wizard

Installing an AWAN ServerThe two major types of asynchronous wide area network (AWAN) servers are:

• AWAN 3883/4/5 access server• AWAN 3886 server (3886-8, 3886-16, and 3886-32)

Both AWAN servers are LAN-based communications devices that provide asynchronous connections to various types of terminals as well as to serial printers and to workstation-based 6530 and VT-series terminal emulators for NonStop S-series servers. AWAN servers support multiple protocols, so you can connect to an AWAN server simultaneously using different types of protocols. All of these AWAN servers can take advantage of networking products and subsystems such as Telserv, HP NonStop TCP/IP subsystem, HP NonStop IPX/SPX subsystem, and others.

For information about installing or configuring an AWAN 3886 server, see the AWAN 3886 Server Installation and Configuration Guide. For up-to-date information regarding all AWAN servers, see the Interactive Upgrade Guide.


Installing External System Devices Installing Printers and Terminals

Installing Printers and Terminals You can install printers and terminals through the WAN, SLSA, ATP6100, or TELSERV subsystems, depending on how each device is physically attached to the server.

• Serial-connected printers can be connected to a NonStop S-series server through:

° A SWAN or SWAN 2 concentrator using WANPRINT printer software° An AWAN server using spooler FASTPxxx print process software

• LAN-attached printers can be connected to NonStop S-series servers through an Ethernet LAN and spooler FASTPxxx print process software.

For more information:

Topic Subsystem Manuals (page 1 of 2)

Ethernet

Local area network (LAN)

WAN

SLSA

Ethernet Adapter Installation and Support GuideFast Ethernet Adapter Installation and Support GuideGigabit Ethernet Installation and Support GuideLAN Configuration and Management ManualSWAN Concentrator Installation and Support Guide

Printer manuals Third-Party Documentation Director

Adapters

Supported connections

G06.nn Release Version Update Compendium

Configuring hosts and printers

Configuring UNIX-based Line Print Daemon (LPD), XNS, and Novell software

Spooler FASTP Network Print Processes Manual

Serial port

SWAN concentrator

SWAN 2 concentrator

Wide area network (WAN)

WAN

ATP6100

Asynchronous Terminals and Printer Processes Configuration and Management ManualSCF Reference Manual for Asynchronous Terminals and Printer ProcessesSWAN Concentrator Installation and Support Guide

SWAN 2 Concentrator Installation and Support Guide



AWAN access server

Asynchronous wide-area network (AWAN)

WAN

TELSERV

AWAN 3886 Server Installation and Configuration Guide

SCF Reference Manual for Telserv

SWAN Concentrator Installation and Support Guide

TCP/IP Configuration and Management Manual

TCP/IP (Parallel Library) Configuration and Management Manual

TCP/IPv6 Configuration and Management Manual

Topic Subsystem Manuals (page 2 of 2)




8Powering On and Starting the System

This section describes how to power on NonStop S-series system enclosures, how to power on external devices, and how to start the system.

Caution. IOAM enclosures must be installed, powered on, and started by a service provider trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

Topic PageStarting a System for the First Time 8-2

Startup Checklist 8-2

Powering On External System Devices 8-3

Powering On the Primary System Console and Modem 8-3

Powering On the System 8-6

Powering On the System 8-6

Fault Tolerance and Access to Power Cutoffs 8-6

Power-On Procedure Using AC Power Cords 8-6

Status LEDs During a Power-On Procedure 8-10

Troubleshooting Abnormal LED States 8-12

Verifying Topology and System Components 8-14

Starting the System 8-17

Loading the System 8-17

Completing the System Load 8-20

Verifying the System Is Started 8-20


Powering On and Starting the System Starting a System for the First Time

Starting a System for the First TimeStartup Checklist

1. Determine whether the AC power receptacles in your computer room are compatible with the AC power cords on your new system.

2. Determine which AC power receptacles are controlled by which circuit breakers.

3. Install and connect these components, but do not power any of them on yet:

4. Power on external devices such as the primary console, the tape subsystem, and any other devices you want started when the system starts.

If you connect only a primary system console and a tape subsystem to the system now, you can test your system before reconfiguring it or connecting other devices.

If you connect the tape subsystem to group 01, you can also dump processor memory to tape to diagnose a halt in processors 0 or 1, and use BACKUP and RESTORE to save data to and restore data from tape.

5. Power on the system.

6. Test the power cords and supplies in the system for fault-tolerance.

Component See Notes PageEthernet switch or hub

Installing the Ethernet Switch or Hub

The switch or hub also must be connected to the server and the system console.

6-5

EPO cables Emergency Power-Off Cables

Install if system requires EPO wiring.

1-25

Power-on cables 1. Connect Power-On Cables

Power-on cables are not the same as AC power cords.

3-1

Primary system console

Installing, Starting, and Testing a System Console

5-1

ServerNet cables ServerNet Cabling Install if system contains two or more enclosures.

1-36

Service-side doors


Shipped with all new systems; optional on others.

4-1

Enclosures Installing Enclosures 2-1

Tape subsystem Installing Tape Drives It is recommended that you connect a tape subsystem to group 01.

7-1

Note. If an IOAM enclosure is installed, it is powered on when you connect it to the AC power source. For more information, your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.


Powering On and Starting the System Powering On External System Devices

7. Configure the server components of the OSM or TSM software package. To configure and start OSM server processes, see the OSM Migration Guide.

8. With the OSM or TSM Low-Level Link, verify that the topology for the system has been set correctly and that system components display the correct attributes.

9. Start the system, which includes loading the NonStop operating system into the memory of each processor in the server and then reloading the processors.

Powering On External System DevicesBefore you power on any system enclosures, power on the external system devices and any other devices you want started when the system starts. External system devices include system consoles, modems, and tape subsystems.

Powering On the Primary System Console and ModemTo power on the primary system console and modem, see Powering On a System Console on page 5-8.

Powering On the Tape SubsystemChoose one of these procedures to power on your tape subsystem:

Procedure PagePowering On a 5175 Tape Subsystem 8-4

Powering On a 519x Tape Subsystem 8-5


Powering On and Starting the System Powering On the Tape Subsystem

Powering On a 5175 Tape Subsystem1. Ensure the 5175 tape subsystem is installed correctly. See Installing a 5175

Open-Reel Tape Subsystem on page 7-2.

2. Ensure that the AC power cord for the 5175 tape subsystem is plugged into a dedicated power receptacle, as indicated on the Floor Plan Diagram.

For every piece of equipment that has two power cords, plug each power cord into an AC power outlet controlled by a different breaker.

3. On the lower left side of the front panel, ensure the standby push-button switch is in the out (OFF) position.

4. At the back of the 5175 module, grasp the hand hold at the top of the back panel and pull down the back panel.

5. Press the AC power switch to apply power to the tape drive. See Figure 8-1.

6. Close the back panel of the 5175 module, pushing at the top to seat the fasteners.

7. At the front of the tape subsystem, ensure that the tape door is closed.

8. On the lower left side of the front panel, press the standby push-button switch to the ON position.

Figure 8-1. AC Power Switch for 5175 Tape Drive

AC PowerSwitch

AC Power Cord

Rear of 5175 Tape Drive

VST533.vsd


Powering On and Starting the System Powering On the Tape Subsystem

Powering On a 519x Tape Subsystem The power-up sequence for the 519x tape subsystem is described in detail in the 5190/5194 Modular Tape Subsystem Manual.

1. Ensure the 519x tape subsystem is installed correctly. See Installing a 519x Cartridge Tape Subsystem on page 7-9.

2. Ensure that the AC power cord for the 519x tape subsystem is plugged into a dedicated power receptacle, as indicated on the Floor Plan Diagram.

For every piece of equipment that has two power cords, plug each power cord into an AC power outlet controlled by a different breaker.

3. Open the rear bezel door of the 519x module by pulling the blue-green handle at the top. You can lower the door to a horizontal position.

4. Set the AC power switch to the ON position. See Figure 8-2.

5. Close the rear bezel door of the 519x module.

6. If the tape subsystem includes an automatic cartridge loader (ACL), install the cleaning cartridge in the ACL. For instructions on installing the cleaning cartridge, see the 5190/5194 Modular Tape Subsystem Manual.

You must install the cleaning cartridge before operating the ACL. If no cleaning cartridge is installed, a CHK F8 check code appears on the ACL front panel when the automatic cleaning routine is activated. Failing to install the cleaning cartridge can cause dirt buildup on the read-write head.

7. Check the tape subsystem SCSI ID using the operator buttons on the tape drive or ACL front panel. Reset the SCSI ID, if necessary, using the operator buttons. For information on checking and setting the SCSI ID, see the 5190/5194 Modular Tape Subsystem Manual.

Figure 8-2. AC Power Switch for 519x Tape Drive

AC Power Switch

AC Power Cord

AC PowerReceptacle

Rear of 519xTape Drive

VST051.vsd


Powering On and Starting the System Powering On the System

Powering On the SystemFault Tolerance and Access to Power Cutoffs

• Most NonStop S-series equipment supports two power cords. For fault tolerance, do not plug the two power cords on any one piece of equipment into the same AC receptacle. Plug each cord into a different receptacle that is connected to a different breaker.

• The AC receptacles to which the server is connected must be accessible to the operator.

Alternatively, the branch circuit breaker supplying power to each receptacle must be accessible to the operator and plainly marked to indicate which receptacle the circuit breaker supports.

Power-On Procedure Using AC Power Cords1. Find the detachable AC power cords included with your system. See Figure 8-3.

• AC power cords for enclosures without power shelves are packaged in one of the boxes included with your system.

• AC power cords for enclosures with power shelves are preconnected to the power shelves in the enclosures.

The AC power cord plugs vary depending on the country to which the system is shipped. For AC power cord plug types and part numbers, see the CSSI Web. See CSSI Web on page xxiii.

2. For each enclosure in the system, plug one end of a detachable AC power cord into the appropriate receptacle on the system enclosure:

• For enclosures that do not have power shelves:

a. Start with the group 01 processor enclosure.

b. Ensure the power interlock on the PMF CRU or IOMF CRU in slot 50 or 55 is fully engaged so that the power cord retainer is aligned with the power receptacle.

Figure 8-3. AC Power Cord

Caution. Do not plug the other end of the AC power cord into the dedicated outlet at this time. Doing so immediately powers on the PMF CRU or IOMF CRU.

VST982.vsd


Powering On and Starting the System Power-On Procedure Using AC Power Cords

c. Connect the AC power cord to the power receptacle on the PMF CRU or IOMF CRU as shown in Figure 8-4.

d. Using a stubby Phillips screwdriver, secure the AC power cord plug in the power cord retainer by tightening the retainer screw.

e. Repeat Step b through Step d for the other AC power cord for this enclosure and for all remaining enclosures that do not have power shelves.

• For enclosures that have power shelves, the AC power cords are shipped preconnected to the power shelves. Use this procedure only if these cords are not connected:

a. Start with the group 01 processor enclosure.

b. Insert the power cord into the retainer in the power shelf. See Figure 8-5. Orient the molded end of the AC power cord with the single contact on bottom, and insert the plug into the retainer until it is fully seated.

c. If you have difficulty inserting the plug into the retainer, you might need to remove the power supply from the power shelf, insert the power cord into the retainer, and reinstall the power supply.

d. Swing the locking bar down until it engages one of the slots on the plug housing and snaps into place.

Figure 8-4. Connecting an AC Power Cord to an Enclosure With No Power Shelf

WARNING. The underside of the locking bar is sharp. Placing your fingers under the locking bar can result in injury. Failure to fully seat the plug into the retainer can result in cord damage from the locking bar.

VST708.vsd

Power Cord Retainer

Retainer Screw

Power Receptacle

AC Power Cord

Power InterlockEjector



e. Repeat Step b through Step d for the other AC power cord for this enclosure and for all remaining enclosures that have power shelves.

3. When you are ready to power on the system, plug the AC power cords for the enclosures into the designated AC receptacles indicated on the Floor Plan Diagram.

If any piece of equipment has two power cords, plug each power cord into an AC power outlet controlled by a different breaker.

Start with the highest numbered group enclosure. Then work through the remaining enclosures in descending group-number order, from the highest group to group 01. The last group to be powered on is group 01.

If the AC power cords have a twist-lock plug on the end that connects to the AC receptacle, the receptacles at your site must be equipped to accept the twist-lock plugs.

If the dedicated AC receptacles are controlled by circuit breakers and currently do not have power, switch the circuit breakers on to provide power to the system.

Figure 8-5. Connecting an AC Power Cord to an Enclosure With a Power Shelf

VST983.vsd

AC Power Cord

Power CordRetainer

LockingBar

Slots onPlug Housing

01



4. Monitor power-on activity. These symptoms indicate that the system is powered:

• Fans on the appearance side of an enclosure start turning, and air begins to circulate through the enclosure. Place your hand near the exhaust grill, which is located above slots 51 through 54 on the service side, to feel for air circulation.

If the fans do not start turning a few seconds after you power on the system, check that the AC power cords and power-on cables are properly connected.

• After the fans start to operate, the other system components begin to power on. Status LEDs on the various enclosures and CRUs light during a series of power-on self-tests (POSTs). Eventually, all components in the group 01 processor enclosure power on, and then the components in other groups power on one after another. When the POSTs finish successfully, which can take up to 10 minutes, the green power-on LEDs light on all CRUs. All LEDs become lit briefly during the POSTs, but only the green power-on LEDs should remain lit after the POSTs finish.

Ensure that the POSTs have finished successfully and that only green power-on LEDs are lit in the system enclosures before you start the system. See system startup procedures on 8-6.

For more information about status LEDs, see Status LEDs During a Power-On Procedure on page 8-10.

If AC power is being supplied to the system but the system still does not appear to be powered, the system might be running internal tests. Wait several minutes (at least 10 minutes for large configurations). If the system is still not powered on after this time and you cannot determine the cause of the problem, contact your service provider.

5. After all power-on tests are completed and the system is running, check the AC power cords. Perform this test only if you have connected redundant power cords to separate circuits. See Step 3 on page 8-8.

a. Locate the circuit breaker that controls half the power cords.

b. Switch this breaker off.

c. Check all objects with redundant power cords to be sure that they are still operating.

d. Switch this breaker back on.

e. Locate the other circuit breaker that controls the other half of the power cords.

f. Switch this breaker off.

Caution. If the green power-on light-emitting diodes (LEDs) on the various CRUs are lit but the fans are not turning, power off the system immediately and contact your service provider.


Powering On and Starting the System Status LEDs During a Power-On Procedure

g. Check all objects with redundant power cords to be sure that they are still operating.

h. Switch this breaker back on.

If any two-corded piece of equipment fails during either power shutdown, there are three possibilities. In descending order of probability, the possibilities are:

• It is plugged in improperly.

Check the connection between each power cord and the AC power receptacle to which it is connected. If necessary, unplug and replug each cord to ensure that it is seated properly in the receptacle.

• It has a defective power cord.

• It has a defective power supply

Status LEDs During a Power-On ProcedureDuring a system power-on procedure, status LEDs on the enclosures and CRUs light during a series of POSTs. Table 8-1 lists the status LEDs and their functions.

Table 8-1. Status LEDs and Their Functions (page 1 of 2)

Location LED Name Color FunctionPMF CRU Power-on Green Lights when the PMF CRU is powered on successfully.

On PMF CRUs of model S74000 and higher, lights as soon as power is applied.

Service Amber Lights temporarily during power on when the PMF CRU has been initialized successfully.

Lights continuously if POST fails.

Flashes if the service processor (SP) image is being loaded from its peer.

IOMF CRU and IOMF 2 CRU

Power-on Green Lights when the IOMF CRU is powered on successfully.

Service Amber Lights temporarily during power on when the IOMF CRU has been initialized successfully.


ServerNet port service

Amber Lights when the service processor (SP) detects an error in the transfer of ServerNet data.

IOAM Enclosure

Contact your service provider for LED status information after powering on an IOAM enclosure.


Powering On and Starting the System Status LEDs During a Power-On Procedure

SEB or MSEB

Power-on Green Lights when the SEB or MSEB is powered on successfully.

Fault Amber Lights temporarily during power on until the SEB or MSEB has been successfully configured by the service processor (SP).

Lights continuously to indicate that the SEB or MSEB is not in a fully functional state.

ServerNet port

Yellow Unused.

ServerNet adapter

Power-on Green Lights when the ServerNet adapter is powered on successfully.

Service Amber Lights temporarily during power on when the ServerNet adapter has been initialized successfully.


Disk drive Power-on Green Lights when the drive is receiving power.

Activity Yellow or amber

Lights when the disk drive is executing a read or write command.

System enclosure

Group service

Amber Lights if a command to light the group service LED was issued using OSM or TSM.

Lights during certain OSM guided replacement procedures.

Table 8-1. Status LEDs and Their Functions (page 2 of 2)

Location LED Name Color Function


Powering On and Starting the System Troubleshooting Abnormal LED States

Troubleshooting Abnormal LED StatesHardware or software faults can prevent the green power-on LED on a CRU from lighting when power is applied. If the amber service LED for a CRU lights and remains lit, the CRU cannot be accessed. A fault might have been detected, or the CRU might not have been successfully initialized and configured for use as a system resource.

Note. For troubleshooting abnormal LED states displayed in IOAM enclosures, contact your service provider trained by HP.

Table 8-2. Troubleshooting Abnormal LED States (page 1 of 2)

Location LED State ActionSystem enclosure

Group service LED is flashing.

Check the group ID switch settings for all enclosures in the system:

• Settings for the two switches within any enclosure must be the same.

• Settings for any two enclosures must be different.

Change the switch settings, if necessary, using the information about adding a processor enclosure in the NonStop S-Series System Expansion and Reduction Guide.

In OSM, the action is Set Service LED State, which sets the state to On or Off. In TSM, the actions are Set Group Service LED and Clear Group Service LED.

PMF CRU Amber service LED is lit.

With the OSM or TSM Event Viewer, check the EMS log files for pertinent event messages.

Retry the operation.

Replace the PMF CRU if necessary. See:

• PMF CRU and IOMF CRU Power-On Self-Tests on page 1-56

• OSM Guided Replacement Procedures on page xxiii

• TSM Guided Replacement Procedures on page xxiv


Powering On and Starting the System Troubleshooting Abnormal LED States

IOMF CRU Amber service LED is lit.


Retry the operation.

Replace the IOMF CRU if necessary. See:

• PMF CRU and IOMF CRU Power-On Self-Tests on page 1-56



SEB or MSEB

Amber service LED is lit.


Reseat the SEB or MSEB, as described on 2-25.

If necessary, replace the SEB or MSEB. See:



Yellow ServerNet port LEDs do not light.

No corrective action is necessary. SEB and MSEB yellow LEDs are not used.

ServerNet adapter

Amber service LED is lit.

With the OSM or TSM Event Viewer, check the EMS log files for pertinent event messages. Reseat the adapter according to in the manual specific to that adapter. Replace the adapter if necessary.

Table 8-2. Troubleshooting Abnormal LED States (page 2 of 2)

Location LED State Action


Powering On and Starting the System Verifying Topology and System Components

Verifying Topology and System ComponentsBefore you start the system, use the OSM or TSM Low-Level Link to verify that the topology for the system has been set correctly and that system components are present with the correct attributes:

1. Log on to the OSM or TSM Low-Level Link.

The Low-Level Link window and Log On to Low-Level Link dialog box appear.

2. In the Log On to Low-Level Link dialog box:

a. In the system list, select the system \NONAME.b. Enter root as the user name, with no password.c. Click Log on.

3. On the toolbar, click System Discovery.

When system discovery finishes, the Management window appears as shown in Figure 8-6.

4. Resize the Management window so that its tree, view, and details panes are fully visible. Resize the view pane so that the group 01 enclosure (GRP-1) is visible.

Note. To verify IOAM enclosure components, contact your service provider.



.

5. Verify that the system topology is set correctly by referring to the Topology attribute in the details pane. The Attributes tab must be selected as shown in Figure 8-7.

Figure 8-6. Management Window in OSM or TSM Low-Level Link

Figure 8-7. Verifying the System Topology

VST013.VSD

VST001.vsd



If the Topology attribute value (Tetra 8 or Tetra 16) does not match the system configuration, you must reset the topology before loading the system. To reset the topology, see the OSM Low-Level Link online help or the OSM User’s Guide.

6. Verify that the system components in the tree pane match the components ordered.

7. From the tree pane, click each system component in the enclosure. The attributes for the selected component appear in the details pane. Verify that the value for each attribute is as listed in Table 8-3 on page 8-16.

If the Power State attribute for a PMF CRU does not have a value of OK, contact your service provider. The PMF CRU is either powered off or contains a fault.

8. Close the Management window.

9. Optional: Run the SP Tool Application (intended for use only by trained service providers) to retrieve detailed information about the system hardware components and ServerNet system area network.

As of the G06.22 RVU, the SP Tool is no longer packaged with TSM. It is installed independently of OSM and TSM (from the HP NonStop System Console Installer CD) and can be used in conjunction with either software package. To run the SP Tool Application:

Caution. If the Topology attribute value specified in the details pane does not match the configuration of the installed system, the view pane might not display all installed enclosures.

Table 8-3. Checking the Attributes of Selected System ComponentsTree Pane Example Details Pane: Attributes Tab

Name ValueDouble-click each IOMF or IOMF 2 CRU.

IOMF.GRP-11.MOD-1.SLOT-50

Power State OK

Click the power supply in each IOMF or IOMF 2 CRU.

IOMF.PS.GRP-11.MOD-1.SLOT-50

Logon State On

Double-click each PMF CRU. PMF.GRP-1.MOD-1.SLOT-50

Power State OK

Click the processor in the PMF CRU. PROCESSOR-0 Total Memory Size

MB should match the memory ordered.

NonStop S7000 servers: click the power supply in the PMF CRU.

PMF.PS.GRP-1.MOD-1.SLOT-50

Logon State On

All NonStop S-series servers except the S7000: click the power supply.

PS.GRP-1.MOD-1.SLOT-1

Logon State On

Click remaining components. FAN.GRP-1.MOD-1.SLOT-25

Power State OK


Powering On and Starting the System Starting the System

a. Click Start > Programs > HP SP Tool > SP Tool. The SP Tool Logon dialog box appears.

b. In the system list, select the system you want to log on to.

c. Enter the low-level link (MSP) user name and password in the User Name and Password fields, respectively.

d. Click Log On. The SP Tool Application main window appears.

e. From the System menu, select Verify System to display configuration information for all PMF CRUs and IOMF CRUs in the system and to verify that all ServerNet paths are functional.

f. From the ServerNet menu, select Path Test to verify that all ServerNet paths from group 01 to all other groups in the system are functional.

g. Click Exit to close the SP Tool Application.

Starting the SystemStarting the system requires loading the NonStop operating system into the memory of each processor in the server. You load the operating system into one processor’s memory from disk and then reload the remaining processors in the server.

For additional information on system startup, see Section 1, Introduction, and the NonStop S-Series Operations Guide.

This subsection assumes that you have already logged on to the OSM or TSM Low-Level Link to verify system components and the topology. If you have not completed this task, see Verifying Topology and System Components on page 8-14.

If the system disk is not located in group 01, slots 11 and 12, load the system from the Load Processor-n from Disk dialog box, not the System Startup dialog box. For more information, see the NonStop S-Series Operations Guide.

After you load the operating system into processor 0 or 1, the remaining processors are reloaded by executing commands in the command-interpreter input (CIIN) file.

Loading the SystemA normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1:

1. On the toolbar, click the Start System button, which appears as a vertical line enclosed in a diamond. The System Startup dialog box appears. For an example of its appearance in TSM (the OSM display is the same), see Figure 8-8 on page 8-18.


Powering On and Starting the System Loading the System

2. In the System Startup dialog box:

a. In the SYSnn field, enter 00, which is the number of the system subvolume that contains the version of the operating system you will load.

b. Under Configuration File, select Current (CONFIG), the default configuration file that represents the configuration currently running.

c. Under Option, verify that the CIIN disabled check box is unchecked.

The CIIN file must be enabled because it contains commands needed to start the server. The startup TACL process performs the commands in the CIIN file and then logs off.

For a description of the CIIN file, see the NonStop S-Series Planning and Configuration Guide.

Figure 8-8. Entering Information in the System Startup Dialog Box

VST591.vsd


Powering On and Starting the System Loading the System

3. In the System Startup dialog box, click Start system. The system load begins.

If you want to stop the system startup process, click Abort in the System Startup dialog box. You might wait up to 30 seconds before the abort takes effect.

Four OutsideView windows, consisting of two startup event stream windows (two CNSL sessions) and two startup TACL windows (two CLCI sessions), are automatically launched. It might take a few seconds before the windows appear.

One startup event stream window and one startup TACL window contain system startup information because they represent the primary ServerNet fabric (X or Y). The other two windows, which represent the backup ServerNet fabric, are blank.

If one or more of the startup event stream windows or startup TACL windows does not launch on the system console after a few minutes, you must connect to MSP 1 within each window. This step is described in the NonStop S-Series Operations Guide.

4. Monitor the system startup process. Messages indicating the progress and completion of the system load, as well as the reload of processors indicated in the CIIN file, appear in these display locations on the system console:

5. When the system load is complete (the operating system is loaded successfully into the memory of processor 0 or processor 1), the System Status box on the System Startup dialog box displays:

SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n

• If nothing appears in any of the startup event stream windows and startup TACL windows, you must connect to MSP 1 within each window. For instructions, see the NonStop S-Series Operations Guide.

• If the system load fails, look for halt codes or messages displayed in the System Startup dialog box or related events in the OSM or TSM Event Viewer. For recovery procedures, see the Processor Halt Codes Manual or Operator Messages Manual and contact your service provider.

Caution. Do not close the System Startup dialog box while startup is in progress. If you attempt to close the dialog box, an OSM or TSM message box indicates that the system startup process will be stopped if you continue. If you stop a system startup before the operation finishes, the state of your system cannot be predicted. You might need to perform another system startup to enable the system to resume normal operation.

Display Location Message TypeSystem Status box on the System Startup dialog box

Initial high-level messages that are not logged

Detailed Status box on the System Startup dialog box

Low-level messages that you can save to a file

Startup event stream windows Startup event stream messages

Startup TACL windows Startup messages


Powering On and Starting the System Completing the System Load

• If no messages appear in the Detailed Status box, the system load has probably failed.

• After the operating system is running on the server, messages are no longer sent to the System Status box. See the event messages sent to the startup event stream window.

• To correct abnormal LED states on enclosures and CRUs, see Troubleshooting Abnormal LED States on page 8-12.

Completing the System LoadTo complete the system load, the processors must be reloaded. Reloading means copying the operating system into other processors in the system after the first processor is loaded from disk by a system load. Reloading can be done in one of two ways:

• With commands in the command-interpreter input (CIIN) file (default method)

• With the TACL command interpreter

The method using the CIIN file is usually automatic. However, if the operating system loaded successfully into processor 0 or processor 1, but the commands in the CIIN file do not reload all remaining processors, you must use the TACL command interpreter:

1. From the system console, log on to the system as a super-group user (255,nnn) and enter:

> RELOAD nn

where nn is the processor number of the processor you want to reload.

If the reload is initiated successfully, this message appears in a startup TACL window on the system console screen:

PROCESSOR RELOAD: nn

For complete syntax, considerations, and examples of the TACL RELOAD command, see the TACL Reference Manual.

Verifying the System Is Started1. Verify that each processor is running the operating system:

a. From the Summary menu, select Processor Status.

b. The Processor Status dialog box should show each processor to be Executing NonStop OS. See Figure 8-9 on page 8-21.


Powering On and Starting the System Verifying the System Is Started

c. Close the Processor Status dialog box.

2. Verify that the NonStop operating system is working properly:

a. Check the startup TACL window to verify that the startup scripts completed successfully.

b. Check the startup event stream window and the startup TACL window for error messages.

3. Close the System Startup dialog box.

For more information on system loads, see:

• OSM Low-Level Link online help• OSM User’s Guide• NonStop S-Series Operations Guide• Section 1, Introduction

After the system starts successfully, you must perform post-startup tasks such as testing the system and configuring OSM or TSM. See Section 9, Performing Post-Startup Tasks.

Figure 8-9. Checking Processor Status

VST008.vsd


Powering On and Starting the System Verifying the System Is Started


9 Performing Post-Startup Tasks This section describes the tasks that you must perform after the NonStop S-series server has been powered up and started.

Testing the SystemThis subsection provides examples of the commands you can use to do the following after the system has been started:

These procedures are not meant to be complete and might not be appropriate for your system. For more information about system components and configurations, see Section 1, Introduction.

Note. If you installed an IOAM enclosure, all post-startup tasks are performed by your service provider.

Topic PageTesting the System 9-1

Completing Final Installation Steps 9-12

Restarting the Inspect Monitor Process 9-14

Configuring the OSM or TSM Environment 9-16

Test PageCheck Power Supplies 9-2

Check System Enclosure Components 9-2

Check Critical System Processes 9-6

Check Disk Subsystem Status 9-7

Check Tape Subsystem Status 9-10

Test the Disk Drives 9-8

Test the Communications Lines 9-10

Test the Tape Subsystems 9-11


Performing Post-Startup Tasks Check Power Supplies

Check Power SuppliesEnsure that all power supplies are functioning properly: perform the Redundant Power Scrub action in the OSM Service Connection or TSM Service Application for all Module objects in the system.

Check System Enclosure ComponentsThese tests provide a quick check that all system components are operating.

Use the OSM Service Connection or TSM Service Application to perform these tests. Do not use the OSM or TSM Low-Level Link for these tests because enclosures and system components that need service are not labeled with color-coded icons.

1. Log on to the OSM Service Connection or TSM Service Application.

2. Resize the Management window so that its tree, view, and details panes are fully visible.

3. Resize the view pane so that the group 01 enclosure (GRP-1) is fully visible.

4. Verify that no yellow or red triangle icons appear over the group diagrams in the view pane. Yellow triangle icons indicate that operator intervention is required.

Figure 9-1 on page 9-3 shows the OSM Management Window.

Figure 9-2 on page 9-4 shows the TSM Management Window.


Performing Post-Startup Tasks Check System Enclosure Components

Figure 9-1. Management Window in the OSM Service Connection

VST007.vsd



5. In the view pane, double-click the group 1 enclosure (GRP-1).

The Physical view of the enclosure appears.

Figure 9-2. Management Window in the TSM Service Application

VST002.vsd



6. In the view pane, verify that no components in the enclosure appear with a red or yellow icon.

7. Compare the tree pane or the Inventory view to the view pane to verify that the components displayed in the view pane match the components that were ordered.

8. For the PMF CRU in slot 50 of the group 01 enclosure:

a. In the view pane, click the PMF CRU. Click the Attributes tab.

Attributes for this PMF CRU appear in the details pane.

b. In the details pane, verify that the Power State attribute has a value of On in OSM, or OK in TSM. If the Power State attribute is not On or OK, the PMF CRU either is powered off or contains a fault. If it contains a fault, contact your service provider.

c. Select Processor 0.

d. In the Attributes tab, verify that the Halt Code attribute has a value of 0 and that the Halt Flag has a value of False in OSM, or 0 in TSM. If the Halt Code or Halt Flag attributes do not match these values, see the Processor Halt Codes Manual.

e. Also in the Attributes tab, verify that the Total Memory Size attribute (in MB) matches the amount of processor memory ordered.

f. Select the Power Supply.

g. In the Attributes tab, if the Service State attribute is visible, verify that it has a value of OK. (The Service State attribute is visible in OSM only if attention or service is required.)

9. Repeat Step 8 for the PMF CRU in slot 55 of group 01.

If the icon is It means thatRed Service is required. The component is not functioning. For example, a

processor is down.

• Select Alarms from the Summary menu. See the Alarm Summary dialog box for details.

• Click the Attributes tab in the details pane. See the Service State attribute, if it is present, for details. (The Service State attribute is visible in OSM only if attention or service is required.)

• Contact your service provider.

Yellow Intervention is required. The component is functioning but needs attention. For example, an operator might have brought down a disk drive.


Performing Post-Startup Tasks Check Critical System Processes

10. In the view pane, click the following enclosure components. Verify that the Power State attribute for each component has a value of On in OSM or OK in TSM:

• ServerNet expansion boards (SEBs)• Modular ServerNet expansion boards (MSEBs)• ServerNet adapters• Disk drives• Fans• Power monitor and control units (PMCUs)

After you click a component, it might take a few seconds for the Power State attribute to appear in the details pane.

11. In the tree pane, click the system name icon.

12. Repeat Step 5 through Step 11 for each remaining system enclosure in the system. For the I/O enclosures, verify the status of IOMF CRUs instead of PMF CRUs.

Check Critical System Processes1. From a TACL prompt, log on to the system using the super ID (255,255). New

systems are shipped without a password for the super ID. For information about assigning a password, see the Guardian User’s Guide.

> SUPER.SUPER

Password: password

2. Start SCF.

> SCF

3. Enter the LISTDEV command.

-> LISTDEV


Performing Post-Startup Tasks Check Disk Subsystem Status

4. Verify that the LISTDEV display includes all processes shown in this example. If any of these processes do not appear in the display, contact your service provider.

Check Disk Subsystem Status1. Enter the SCF STATUS DISK command for all disk volumes on the system:

-> STATUS DISK $*

2. Verify that the STATUS DISK display includes all the disk subsystems shown in the following example and that the primary, backup, mirror, and mirror-backup paths are all described as STARTED. If any of these disk subsystems do not appear in the display, or if any of these paths are described as STOPPED, contact your service provider.

LDev Name PPID BPID Type RSize Pri Program 0 $0 0,5 1,5 ( 1,0 ) 102 201 \NONAME.$SYSTEM.SYS00.OSIMAGE 3 $YMIOP 0,256 1,256 ( 6,4 ) 80 205 \NONAME.$SYSTEM.SYS00.OSIMAGE 5 $Z0 0,7 1,7 ( 1,2 ) 102 200 \NONAME.$SYSTEM.SYS00.OSIMAGE 6 $SYSTEM 0,257 1,257 ( 3,41) 4096 220 \NONAME.$SYSTEM.SYS00.OSIMAGE 7 $ZOPR 0,8 1,8 ( 1,0 ) 102 201 \NONAME.$SYSTEM.SYS00.OSIMAGE 38 $ZZKRN 0,15 1,12 (66,0 ) 132 180 \NONAME.$SYSTEM.SYS00.OZKRN 39 $ZZWAN 0,271 1,275 (50,3 ) 132 180 \NONAME.$SYSTEM.SYS00.WANMGR 40 $ZZSTO 0,272 1,282 (65,0 ) 4096 180 \NONAME.$SYSTEM.SYS00.TZSTO 41 $ZZLAN 0,14 1,15 (43,0 ) 132 180 \NONAME.$SYSTEM.SYS00.LANMAN 45 $ZSNET 0,15 1,12 (66,0 ) 132 180 \NONAME.$SYSTEM.SYS00.OZKRN 46 $ZNET 0,16 1,14 (50,63) 3900 175 \NONAME.$SYSTEM.SYS00.SCP 61 $ZM01 1,11 0,0 (45,0 ) 132 201 \NONAME.$SYSTEM.SYS00.QIOMON 62 $ZM00 0,13 0,0 (45,0 ) 132 201 \NONAME.$SYSTEM.SYS00.QIOMON 63 $ZLOG 0,286 0,0 ( 1,0 ) 4024 150 \NONAME.$SYSTEM.SYS00.EMSACOLL 72 $DSMSCM 0,280 1,261 ( 3,41) 4096 220 \NONAME.$SYSTEM.SYS00.TSYSDP2 79 $AUDIT 0,273 1,271 ( 3,41) 4096 220 \NONAME.$SYSTEM.SYS00.TSYSDP2 85 $ZTCP0 0,299 1,280 (48,0 ) 32000 200 \NONAME.$SYSTEM.SYS00.TCPIP 88 $ZTNP0 0,301 1,276 (46,0 ) 6144 170 \NONAME.$SYSTEM.SYS00.TELSERV 98 $ZTCP1 1,283 0,304 (48,0 ) 32000 200 \NONAME.$SYSTEM.SYS00.TCPIP 100 $ZTNP1 1,285 0,305 (46,0 ) 6144 170 \NONAME.$SYSTEM.SYS00.TELSERV

STORAGE - Status DISK \NONAME.$AUDITLDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 79 *STARTED STARTED *STARTED STARTED 0,273 1,271

STORAGE - Status DISK \NONAME.$DSMSCMLDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 72 *STARTED STARTED *STARTED STARTED 0,280 1,261 STORAGE - Status DISK \NONAME.$SYSTEMLDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 6 *STARTED STARTED *STARTED STARTED 0,257 1,257


Performing Post-Startup Tasks Test the Disk Drives

Test the Disk DrivesYou should test disk drives whenever you install a new system, replace a disk drive, or add a disk drive:

1. At the SCF prompt, check the status of all disks on the system:

-> STATUS DISK $*-*

2. In the display, ensure that paths to all installed disk drives are available. A path is available if the State column indicates STARTED. If no disk drive is installed in a slot, the Status column indicates INACTIVE, the State column indicates STOPPED, and the Substate column indicates HARDDOWN.

The following shows an example of a partial SCF STATUS DISK listing:

3. Determine the preferred path for each disk using the STATUS DISK command and specifying the name or logical device number of that disk. The asterisk (*) in the response indicates the preferred path. A mirrored disk volume has four paths (two for each physical disk) and two preferred paths.

4. For each disk drive whose paths you want to test, check that each path to that disk drive can be used as the preferred path. To test the paths to a disk named $DATA00:

a. Enter the following SCF command:

->SWITCH $DATA00-B

For the primary drive of the $DATA00 disk, this command switches the current path, which is the primary path ($DATA00-P), to the backup path ($DATA00-B).

b. Enter the STATUS DISK $DATA00 command. See Step 3 to check that the path switch occurred. Make sure the processor number in the Primary PID column is the same as it was before the switch.

STORAGE - Status DISK \Example.$DATA00LDev Path Status State Substate Primary Backup PID PID 06 PRIMARY ACTIVE STARTED 0,267 1,267 06 BACKUP INACTIVE STARTED 0,267 1,267 06 MIRROR ACTIVE STARTED 0,267 1,26 06 MIRROR-BACKUP INACTIVE STARTED 0,267 1,267 STORAGE - Status DISK \Example.$DATA01LDev Path Status State Substate Primary Backup PID PID 07 PRIMARY INACTIVE STOPPED HARDDOWN 0,33 1,33 07 BACKUP INACTIVE STOPPED HARDDOWN 0,33 1,33 07 MIRROR INACTIVE STOPPED HARDDOWN 0,33 1,33 07 MIRROR-BACKUP INACTIVE STOPPED HARDDOWN 0,33 1,33

->STATUS DISK $DATA00STORAGE - Status DISK \Example.$DATA00LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 06 *STARTED STARTED *STARTED STARTED 0,30 1,30


Performing Post-Startup Tasks Test the Disk Drives

The following example shows the listing for the disk from the example in Step 3 after the path has been successfully switched:

c. If you are testing a drive that is not mirrored, skip to Step 4e. Otherwise, enter:

->SWITCH $DATA00-MB

For the mirror drive of the $DATA00 disk, this command switches the preferred path from the current preferred path, which is the mirror path ($DATA00-M), to the mirror backup path ($DATA00-MB).

d. Enter the STATUS DISK $DATA00 command. See Step 3 to check that the path switch occurred. Make sure the processor number in the Primary PID column is the same as it was before the switch.

The following example shows the listing for the disk from the example in Step 4b after the path has been successfully switched:

e. Enter the following SCF command:

->PRIMARY DISK $DATA00, 1

This command switches the primary processor from the current primary processor to the backup processor.

f. Enter the STATUS DISK $DATA00 command. See Step 3 to check that the processor switch occurred. Make sure the processor number in the Primary PID column has changed to the number given in the command.

The following display shows that the primary processor was successfully switched:

Successfully completing these commands indicates that the disk can be accessed through both the primary and backup processors and through all the paths.

->STATUS DISK $DATA00STORAGE - Status DISK \Example.$DATA00LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 06 STARTED *STARTED *STARTED STARTED 0,30 1,30

->STATUS DISK $DATA00STORAGE - Status DISK \Example.$DATA00LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 06 STARTED *STARTED STARTED *STARTED 0,30 1,30

->STATUS DISK $DATA00STORAGE - Status DISK \Example.$DATA00LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 06 STARTED *STARTED STARTED *STARTED 1,30 0,30


Performing Post-Startup Tasks Test the Communications Lines

g. Return the preferred paths and the primary processor for this disk to their original states by entering the following commands. Wait for the SCF prompt to appear before you enter each command:

->PRIMARY DISK $DATA00, 0

->SWITCH $DATA00-P

(Enter this command only if you are testing a mirrored disk.)

->SWITCH $DATA00-M

Use the STATUS DISK $DATA00 command to check that the preferred paths and primary processor have returned to their original states. Compare with the example in Step 3.

5. Use the BAD attribute of the SCF INFO DISK command to check each disk for bad sectors. The following example checks for bad sectors on a disk named $DATA00:

->INFO DISK $DATA00, BAD

If you detect bad sectors, use the SCF CONTROL DISK, SPARE command to replace them. For more information, see the SCF Reference Manual for the Storage Subsystem.

6. If you must replace a disk drive, see the CSSI Web. See Where to Get More Information on page xxiii.

Test the Communications LinesFor information about testing communications lines, see the manual specific to the appropriate communications line.

Check Tape Subsystem StatusOSM, TSM, and other utilities do not test tape libraries.

1. Enter the SCF STATUS TAPE command for all tape volumes on the system:

-> STATUS TAPE $*

2. Verify that the STATUS TAPE display includes the tape subsystem and that the state is STARTED, the substate is UP, and the device status is READY. The following example shows the status for tape drive $T0151:

Caution. Using the CONTROL DISK, SPARE command can cause inconsistent data if processing is taking place when you issue the command. It is recommended that you stop all processing on the volume before issuing the CONTROL DISK, SPARE command, especially when sparing bad sectors on a system disk while one half of the volume is down.

STORAGE - Status TAPE $T0150LDev State Primary Backup Device Status PID PID 71 STARTED 0,282 1,273 READY


Performing Post-Startup Tasks Test the Tape Subsystems

If the tape subsystem does not appear in the display, or if the state, substate, or device status is not correct, ensure that:

• The tape subsystem is plugged in.

• The cables are attached correctly.

• All appropriate start buttons have been pushed.

• All LEDs on the subsystem show normal status. See the subsystem manual.

• The tape drive is configured properly in the system database.

If these troubleshooting techniques do not work, contact your service provider.

Test the Tape Subsystems Test tape subsystems with TSM, BACKUP and RESTORE, or SCF. OSM or TSM and other utilities do not test tape libraries.

• The OSM Service Connection and TSM Service Application support these tests for tape subsystems:

For help using the OSM or TSM windows and dialog boxes, see online help for the OSM Service Connection or TSM Service Application. For information about concepts, commands, dialog boxes, and how to perform tape tasks, see the TSM Online User Guide or the OSM User’s Guide.

• The BACKUP and RESTORE utilities test the status of tape drives. See the Guardian Disk and Tape Utilities Reference Manual.

• You can use SCF commands to obtain status information about a tape subsystem. For an example of the SCF STATUS TAPE command, see Check Tape Subsystem Status on page 9-10.

The SCF STATUS TAPE, DETAIL command produces a report that shows the processor numbers for the tape process, the logical device number of the tape drive, and the current state of the tape drive. The following example shows a report for $TAPE0:

OSM or TSM Action Description of ActionCRU Responsive Test Verifies that a tape drive is installed and responding.

Test Extended The specific test performed depends on type of tape drive. For more information, see the OSM User’s Guide or the TSM Service Application online help. The tape drive must be in the down state.

Test Verify Runs the power-on self-test for the tape drive and tests its internal circuitry. The tape drive must be in the down state.


Performing Post-Startup Tasks Completing Final Installation Steps

->STATUS TAPE $TAPE0, DETAIL

For more information about SCF commands for tape subsystems, see the SCF Reference Manual for the Storage Subsystem.

Completing Final Installation Steps1. Complete any post-installation procedures or special instructions in the Installation

Document Checklist.

2. Perform the required and optional system configuration changes and verifications listed in Table 9-1.

3. Restart the Inspect Monitor Process.

STORAGE - Detailed Status TAPE \ALM171.$TAPE0

Tape Process Information: LDev State Primary Backup DeviceStatus PID PID 51 STARTED 0,273 1,269 ONLINE, BOT

Tape I/O Process Information: Library File....... Program File....... $SYSTEM.SYS70.OTPPROCP

Current Settings: ACL................ INSTALLED Buffer Level...... RECORD Checksum Mode...... NORMAL I/O *Compression....... OFF *Density............ 38000 Media Type........ 36-TRACKS Opens.............. 0 *RecSize........... 2048 Short Write Mode... ALLOWED, PADDED SubType........... 9 Volume Switching.. TRANSPARENT Media Information: Automatic Volume Recognition Labels: VOL1: SANYOA HDR1: D87D040 SANYOA00010001000100000028 000000000000 HDR2: F080000080000 B


Performing Post-Startup Tasks System Configuration Changes and Verifications

System Configuration Changes and Verifications

Table 9-1. System Configuration Changes and Verifications (page 1 of 2)

Change or Verification Required RecommendedOptional or As Needed

Configure Kernel-Managed Swap Facility (KMSF) files. See the Kernel-Managed Swap Facility (KMSF) Manual.

X

Change the system name and system number attributes. See Changing System Name, System Number, or Time Attributes on page 11-3.

X

Check and set the system time. See the SCF Reference Manual for the Kernel Subsystem.

X

Configure DSM/SCM. See the DSM/SCM User’s Guide. Some DSM/SCM configuration is required as a result of changing the system name.

X X

Verify that all updatable firmware is at the proper revision level, using the OSM Service Connection or TSM Service Application. See the OSM User’s Guide, the TSM Online User Guide, or the G06.nn Software Installation and Upgrade Guide.

X

Verify the SP firmware, using the OSM Service Connection or TSM Service Application. See the OSM User’s Guide, the TSM Online User Guide, or the G06.nn Software Installation and Upgrade Guide.

X

With SCF, verify that paths and connections within the ServerNet system area network are properly configured and functional. See the NonStop S-Series Operations Guide.

X

Configure low-level link user names and passwords. See the TSM Configuration Guide or the OSM Low-Level Link online help. Service connection user names and passwords are created when you add NonStop user names and passwords.

X

Configure a backup system console. See Section 10, Configuring the System.

X

Invoke the STARTCOM and STARTSCF startup files to configure standard TCP/IP objects and start TCP/IP services. See 4e. Invoke STARTCOM and STARTSCF Startup Files on page E-40.

X


Performing Post-Startup Tasks Restarting the Inspect Monitor Process

Restarting the Inspect Monitor ProcessIf Visual Inspect is installed on your system, then on the G05 and later RVUs, $ZPM automatically starts the Inspect Monitor process $IMON early in the system startup sequence to provide Inspect debugging and saveabend file capability. However, Visual Inspect requires that $IMON be started after the TCP/IP and Port Mapper processes have started.

After $ZPM has started all processes specified in the CONFIG file and you start all other TCP/IP and Port Mapper processes, stop and restart $IMON as follows:

1. Log on as the super ID.

2. At the TACL prompt:

> Stop $IMON

3. At the TACL prompt, restart $IMON:

> IMON /name $IMON, term $YMIOP.#CNSL, cpu <p>, nowait /<b>

where <p> and <b> are the primary and backup processors, respectively, where $IMON is to run.

Change time attributes. X

Configure and initialize the spooler subsystem. See the Spooler Utilities Reference Manual and the Guardian User’s Guide.

X

Configure the IOAM enclosure. X

Configure and start additional subsystems. See the manual specific to that subsystem.

X

Table 9-1. System Configuration Changes and Verifications (page 2 of 2)

Change or Verification Required RecommendedOptional or As Needed


Performing Post-Startup Tasks Preparing for Daily Operations

Preparing for Daily OperationsIf the new system is running properly, you can now prepare it for daily operations. Your preparation tasks might include:

• Adding users to the system• Setting the file security of various program files and system files• Loading application software

Reference Manuals

Procedures for loading application software depend on the application. For more information, see the documentation for the application.

For more information about… See…Performing routine system operations • NonStop S-Series Operations Guide

• Guardian User’s Guide

Replacing failed hardware components and other support procedures

• CSSI Web on page xxiii



Guidelines, suggestions, and ideas about the following topics:

StaffingOperations and support areasOperations documentationProduction and problem managementChange and configuration managementPerformance managementSecurityDisaster prevention and recovery planningApplication managementAutomating and centralizing operationsOperations management and continuous improvementOperations management tools

Introduction to NonStop Operations Management


Performing Post-Startup Tasks Configuring the OSM or TSM Environment

Configuring the OSM or TSM EnvironmentConfiguring the OSM Environment

To configure the OSM environment for a new system, see the OSM User’s Guide, the OSM Low-Level Link online help, or the OSM Notification Director online help as appropriate.

Configuring the TSM EnvironmentUse the TSM Low-Level Link, TSM Notification Director, and special TACL procedures to configure the TSM environment for a new system. You can run the TSM Low-Level Link and the TSM Notification Director at any time after the primary system console and the server are installed and the server is running the NonStop operating system.

Servers and system consoles are shipped with default configuration values that allow them to operate without initial configuration. You need not perform initial configuration if you accept the default values. However, the default values might not implement the features you want. For information about default values, see the TSM Configuration Guide.

Use the TSM Low-Level Link to:

• Change the default password (which is no password) for the user root. Change this password to prevent unauthorized access.

• Add new low-level link users. These users can log on to the master service processors (MSPs).

• Change the default IP addresses for the primary or backup dedicated LAN.

Changing the default IP addresses used for service connection access requires editing macro files and running macros that are located on the server to restart the $ZTCP0 and $ZTCP1 processes. For this task, see the TSM Configuration Guide.

Use the TSM Notification Director to:

• Add a backup system console or additional system consoles to the dedicated LAN.• Configure onsite contact information.• Configure how often the server generates periodic incident reports (IRs).• Configure dial-out (remote notification) or dial-in (remote access) capability.• Test the dial-out path to the GCSC.

The TSM Low-Level Link and the TSM Notification Director test the physical connections between the system console, the master service processors (MSPs), and the operating system. Status messages alert you to connectivity problems.

For more information, see the TSM Configuration Guide, the TSM Low-Level Link online help, or the TSM Notification Director online help.


10 Configuring the SystemThis section describes how to configure system consoles and NonStop S-series servers in several ways.

• Operating configuration• With cascading Ethernet switches or hubs• At an unattended site• On a nondedicated (public) LAN• With Ethernet 4 ServerNet Adapters (E4SAs)• With Fast Ethernet ServerNet Adapters (FESAs)

For information about Gigabit Ethernet configurations, see the Gigabit Ethernet Installation and Support Guide.

This section assumes that you have used the preceding sections of this guide to connect the primary system console and server in a setup configuration. Use the configurations in this section for installing and operating system consoles.

Your new system console is shipped with the Microsoft Windows XP Professional operating system already installed. To migrate an existing system console from the Microsoft Windows 2000 Professional operating system to the Microsoft Windows XP Professional operating system, see the NonStop System Console Guide for Migrating to Microsoft Windows XP Professional.

Note. IOAM enclosures must be installed by service providers trained by HP. This requirement includes configuring the IOAM enclosure and configuring system consoles to communicate with the IOAM enclosure. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

Topic PageSetup Configuration 10-2

Procedure to Create the Setup Configuration 10-2

Operating Configuration 10-3

Create the Operating Configuration 10-4

Add a System Console to the Operating Configuration 10-7

Add a Server to the Operating Configuration 10-9

Create a Cascading Ethernet Switch Configuration 10-11

Add a System Console to the Cascading Ethernet Switches 10-13

Add a Server to the Cascading Ethernet Switches 10-13

Unattended Site Configuration 10-14

Create the Unattended Site Configuration 10-15

Add a Server to an Unattended Site Configuration 10-15

Nondedicated (Public) LAN Configuration 10-16

Construct a Nondedicated (Public) LAN Configuration 10-16


Configuring the System Setup Configuration

Setup ConfigurationThe setup configuration is a stand-alone LAN used to configure Internet protocol (IP) addresses. These IP addresses allow a system console to communicate with the master service processors (MSPs) in the server as shown in Figure 10-1. Actual connections vary depending upon the Ethernet switch or hub you use.

Procedure to Create the Setup ConfigurationOn a new server, all these tasks must be performed before you can expand to the operating configuration:

Do not use the setup configuration as your working configuration. It lacks fault tolerance. Add fault tolerance to the setup configuration by connecting a backup system console and a second Ethernet switch or hub. See Operating Configuration on page 10-3.

Figure 10-1. Setup Configuration

Task Instructions PageInstall and cable the server Section 2, Installing Enclosures

Section 3, Cabling Enclosures2-13-1

Install, start, and test the system console


5-1

Install the Ethernet switch or hub Installing the Ethernet Switch or Hub 6-5

Connect the Ethernet switch or hub to the server

Connect the Ethernet Switch or Hub to the Server

6-5

Connect the system console to the Ethernet switch or hub

Connect the System Console to the Ethernet Switch or Hub

6-6

Start the server Powering On the System 8-6

Configure the OSM or TSM environment

Configuring the OSM or TSM Environment 9-16

VST992.vsd

System Console

EthernetSwitch


ModemRemote Service

Provider


Configuring the System Operating Configuration

Operating ConfigurationAfter you have completed the setup configuration tasks, you can expand to the operating configuration by adding a backup system console and second Ethernet switch or hub. Figure 10-2 shows primary and backup system consoles connected to separate Ethernet switches.

Figure 10-2. Operating Configuration

VST998.vsd

BackupSystemConsole

Switch 2

Modem

RemoteServiceProvider


Switch 1

PrimarySystemConsole

Modem

RemoteServiceProvider

Note: Do not use this figure as a wiring diagram. Actual connections vary depending on the Ethernet switch you use.


Configuring the System Create the Operating Configuration

Create the Operating ConfigurationThe primary system console is the system console installed in the setup configuration. Switch 1 is the switch installed in the setup configuration.

The backup system console and Switch 2 are added for fault tolerance. You can add a backup system console and switch to the setup configuration online. Do not add a backup system console until you have completed Setup Configuration on page 10-2.

The Ethernet switches or hubs are linked by a cable that enables the system consoles and server to be on the same subnet. This cable connects the cascade port of one switch to an open port on the other switch.

1. If the backup system console is not unpacked, see Unpacking and Assembling a System Console on page 5-2.

2. Start and test the backup system console. See Starting and Testing a System Console on page 5-8.

3. Change the IP address and host name for the backup system console. Because all system consoles are shipped with the same default IP address and computer name, you must modify the IP address and host name for the backup system console so that they do not conflict with those of the primary system console:

a. Select Start>Settings>Control Panel.

b. Double-click the Network icon.

The Network dialog box appears.

c. Click the Protocols tab.

d. In the Network Protocols box, double-click TCP/IP Protocol.

The Microsoft TCP/IP Properties dialog box appears.

e. Select Specify an IP address and enter:

f. Click the DNS tab.

g. In the Host Name field, change the default name.

You can change it to anything that does not conflict with the host name used by another workstation already on the LAN. For example, if the default name is NONAME, you can change the name to NONAME1 or NONAME2.

h. Click OK to return to the Network dialog box.

i. Click OK to return to the Control Panel window.

j. Select Start > Shut Down.

IP Address 192.231.36.4Subnet Mask 255.255.255.0Default Gateway 192.231.36.9



k. Select Restart the computer. Click Yes.

4. Unpack and install an Switch 2 using the documentation that comes with the switch.

Switch 1 is the switch installed in the initial setup configuration. Switch 2 is the switch you add for fault tolerance.

5. Move the cable attached to the PMF CRU in group 01, slot 55, from Switch 1 to Switch 2.

To maintain EMC compliance in NonStop S-series systems, Ethernet cables must be equipped with a ferrite suppression component. Install the Ethernet cables that connect the PMF CRUs to the Ethernet switches or hubs with the ferrite end of the cables connected to the PMF CRUs.

a. At Switch 1, disconnect the cable attached to the Ethernet port on the PMF CRU in slot 55, group 01.

b. Reconnect this end of the cable to any port on Switch 2 except the cascade port. Insert the RJ-45 plug on the cable into the RJ-45 jack on the Ethernet switch or hub until the tab on the plug clicks into place as shown in Figure 10-3.



6. Connect the backup system console to Switch 2:

a. Connect an Ethernet cable to the 10Base-T connector on the network interface card (NIC) at the back of the system unit for the backup system console. For the location of the NIC connector, see the quick setup reference card.

b. Connect the other end of this Ethernet cable to any port on Switch 2 except the cascade port.

7. Set the medium-dependent interface (MDI) switch on Switch 1 to allow the cascade port of Switch 1 to connect to another switch or hub. See the documentation provided with Switch 1. The position of the MDI switch on Switch 2 does not matter.

8. Connect the three-foot Ethernet cable provided with the switch or hub from the cascade port of Switch 1 to any port on Switch 2 except the cascade port.

Figure 10-3. Connections for the Operating Configuration

VST535.vsd

Note: Connections vary depending on the Ethernet switch you use

Ethernet Switch 1 Ethernet Switch 2

To PrimarySystem

Console To BackupSystem

Console

CascadePort

CascadePort

Medium-DependentInterface (MDI) Switch

(Setting for Ethernet Switch)

MDITo

EthernetSwitch

To PCMDI-X

Group 01 Processor Enclosure

PMF CRU ContainingProcessor 0

Slot 50

PMF CRU ContainingProcessor 1Slot 55


Configuring the System Add a System Console to the OperatingConfiguration

Add a System Console to the Operating ConfigurationFigure 10-2 on page 10-3 shows the operating configuration. You can add a system console to this configuration as long as you have an unused port on one of the Ethernet switches or hubs.

You can add a system console while all system components are online. Figure 10-4 shows the operating configuration with an added system console.

Before you add a system console to the operating configuration:

• Install the primary and backup system consoles and the two Ethernet switches or hubs. See Create the Operating Configuration on page 10-4.

• Install, start, and test the server fully, and ensure the operating system is up and running. See Section 8, Powering On and Starting the System.

• Configure OSM or TSM. See Configuring the OSM or TSM Environment on page 9-16 and the OSM User’s Guide or TSM Configuration Guide.

System consoles are shipped with the same default IP address and computer name. Ensure that the IP address and computer name of the system console you are adding are different from the address and name of all other workstations on the Ethernet LAN.

Figure 10-4. Operating Configuration With an Added System Console

Do not use this figure as a wiring diagram. Actual connections vary depending on the Ethernet switch.

System Console

VST065.vsd

Switch 2


Switch 1

Modem

Remote ServiceProvider

Modem


PrimarySystem Console

BackupSystem Console


Configuring the System Add a System Console to the OperatingConfiguration

Procedure1. Unpack the system console. See Unpacking and Assembling a System Console on

page 5-2.

2. Start and test the system console. See Starting and Testing a System Console on page 5-8.

3. Before connecting the system console to the LAN, use the Windows XP Professional operating system to assign a unique IP address and computer name to the system console. For information about setting these and other network parameters, see Step 3 on page 10-4 or the online help for the operating system.

4. Connect one end of an Ethernet cable to the 10Base-T connector on the network interface card (NIC) at the back of the system unit for the backup system console.

5. Connect the other end of this Ethernet cable to any port on an Ethernet switch or hub except the cascade port. See Figure 10-5.

Figure 10-5. Adding a System Console to the Operating Configuration

VST537.vsd

CascadePort


settings forEthernet switches

Ethernet Switch 1 Ethernet Switch 2To Backup

System Console

To PrimarySystemConsole

CascadePort

PMF CRUcontaining

Processor 1

PMF CRUcontaining

Processor 0

Group 01

MDIto

EthernetSwitch

MDI-Xto PC


Configuring the System Add a Server to the Operating Configuration

Add a Server to the Operating ConfigurationA server in the operating configuration requires connections to both Ethernet switches or hubs. If each switch or hub has an unused port, you can add a server to the configuration online.

Before you add a server to the operating configuration:

• Install a primary system console, a backup system console, and two Ethernet switches or hubs. See Operating Configuration on page 10-3.

• Ensure that the existing server in the operating configuration is fully operational. See Section 8, Powering On and Starting the System.

• Configure OSM or TSM. See Configuring the OSM or TSM Environment on page 9-16 and the OSM User’s Guide or TSM Configuration Guide.

• Because all servers are shipped with the same default low-level link (MSP) and operating system IP addresses, ensure that the server you are adding has IP addresses different from those of all servers currently on the Ethernet LAN. To view or change the MSP IP addresses, use the OSM or TSM Low-Level Link.

Figure 10-6 shows a server that has been added to the operating configuration.

Figure 10-6. Operating Configuration With an Added Server


Switch 2


Switch 1

Modem


Modem




NonStop S-Series Server

VST068.vsd


Configuring the System Add a Server to the Operating Configuration

Procedure1. Create a temporary setup configuration using the server you are adding, its system

console, and its switch or hub. See Setup Configuration on page 10-2.

2. Configure the OSM or TSM environment. While you are configuring the server you are adding, make sure you assign IP addresses that do not conflict with the addresses used by the server already installed in the operation configuration.

3. Disconnect the server you are adding from the temporary setup configuration. Then connect that server to the operating configuration.

4. Connect the ferrite-bead end of an Ethernet cable to the Ethernet port on the PMF CRU in slot 50 of group 01 of new server you are adding. Connect the other end of this Ethernet cable to any port on Switch 1 except the cascade port. Make sure the RJ-45 plug on the cable clicks into place as shown in Figure 10-7.

5. Connect the ferrite-bead end of another Ethernet cable to the Ethernet port on the PMF CRU in slot 55 of group 01 of the server you are adding. Connect the other end of this Ethernet cable to any port on Switch 2 except the cascade port. Make sure the RJ-45 plug on the cable clicks into place.


Configuring the System Create a Cascading Ethernet Switch Configuration

Create a Cascading Ethernet Switch ConfigurationWhen no ports are left on the Ethernet switches or hubs in the operating configuration, you can expand the configuration by cascading two additional Ethernet switches or hubs online. Figure 10-8 shows a cascading Ethernet switch configuration.

A cascading Ethernet switch configuration containing more than four switches or hubs is not supported for LAN configurations.

Figure 10-7. Connections for Adding a Server to the Operating Configuration

VST536.vsd

Ethernet Switch 1 Ethernet Switch 2

To PrimarySystemConsole To Backup

SystemConsole

CascadePort

CascadePort


(Setting for Ethernet Switch)

MDITo

EthernetSwitch

To PCMDI-X

Group 01 Processor Enclosure(Service Side)

PMF CRU ContainingProcessor 0

Slot 50

PMF CRU ContainingProcessor 1Slot 55

Note: Connections vary depending on the Ethernet switch you use

To Ethernet Portof PMF CRUin Slot 55

To Ethernet Portof PMF CRUin Slot 50


Configuring the System Create a Cascading Ethernet Switch Configuration

ProcedureThis procedure to construct a cascading Ethernet switch configuration assumes you have already constructed the operating configuration shown in Figure 10-2 on page 10-3.

Switch 1 and Switch 2 are the Ethernet switches or hubs already installed in the operating configuration. You are adding cascading switches or hubs 3 and 4.

1. Unpack and install Switch 3 using the documentation that came with the switch or hub.

2. Unpack and install Switch 4 using the documentation that came with the switch or hub.

3. Set the MDI switch on Switches 2 and 3 to allow the cascade ports of Switches 2 and 3 to connect to another switch or hub as shown in Figure 10-9. To set the MDI switch, see the documentation provided with the Ethernet switches or hubs.

The MDI switch on Switch 1 should already be set to allow the cascade port of Switch 1 to connect to another Switch.

Figure 10-8. Cascading Ethernet Switch Configuration

VST069.vsd


Switch 2


Switch 1

Modem


Modem




Switch 3 Swich 4

Cascading Ethernet Switch


Configuring the System Add a System Console to the Cascading EthernetSwitches

4. Connect a three-foot Ethernet cable, provided with the switch or hub, from the cascade port of Switch 2 to any port on Switch 4 except the cascade port.

5. Connect a three-foot Ethernet cable from the cascade port of Switch 3 to any unused port on Switch 1.

Add a System Console to the Cascading Ethernet SwitchesSee Add a System Console to the Operating Configuration on page 10-7.

Add a Server to the Cascading Ethernet SwitchesSee Add a Server to the Operating Configuration on page 10-9.

Figure 10-9. Connecting Cascading Ethernet Switches

EthernetSwitch 2

Medium-DependentInterface (MDI) Switch(Settings for EthernetSwitches 1, 2, and 3)

MDITo

EthernetSwitch

To PCMDI-X

CascadePort

EthernetSwitch 1

EthernetSwitch 3

EthernetSwitch 4

CascadePort

Cascade Port

Note: The actual location of the cascade port varies among different types of Ethernet Switches.

VST070.vsd


Configuring the System Unattended Site Configuration

Unattended Site ConfigurationAn unattended site configuration consists of one or more system consoles at one site, typically a centralized monitoring station, and a stand-alone, dedicated network at a remote site that includes primary and backup system consoles. Because it has no onsite operator, the remote site is referred to as an unattended site. Figure 10-10 shows an example of an unattended site configuration.

Figure 10-10. Unattended Site Configuration

VST528.vsd

Unattended Site

Workstation atCentral Site

Modem

Switch 2

Modem

NonStopS-Series Server

Switch 1


Modem


Note: Do not use this figure as a wiring diagram. Actual connections vary depending on the Ethernet switch you use.


Configuring the System Create the Unattended Site Configuration

Create the Unattended Site ConfigurationA system console at the central site typically is configured for low-level link and service connection access to the remote site. This workstation can be an independent system console, as shown in Figure 10-10, or part of another network configuration. Redundant workstations are recommended to prevent loss of communications as a result of a workstation failure.

Procedure1. At the central site, install the system console to be used for monitoring the

unattended site.

a. Unpack and assemble the system console. See Unpacking and Assembling a System Console on page 5-2.

b. Start and test the system console. See Starting and Testing a System Console on page 5-8.

2. At the unattended site, construct a secure stand-alone network by using one of these procedures:

3. See the TSM Configuration Guide for information about configuring the system consoles at the central site and at the unattended site.

4. If your system uses OSM: Although OSM supports unattended site configurations, automatic logon is not necessary. The OSM Notification Director runs as a Windows service, so it does not need a user to be logged on in order to receive and dial out incident reports. If you did not choose the option for the Notification Director to run automatically as a service during OSM installation, you can change the configuration without reinstalling OSM. See the OSM Notification Director online help.

If your system uses TSM: reinstall TSM. Configure the workstation for automatic logon at the unattended site.

Add a Server to an Unattended Site ConfigurationSee Add a Server to the Operating Configuration on page 10-9.

To construct thisnetwork configuration See this topicSetup configuration Setup Configuration on page 10-2

Operating configuration Operating Configuration on page 10-3


Configuring the System Nondedicated (Public) LAN Configuration

Nondedicated (Public) LAN ConfigurationA nondedicated (public) LAN:

• Connects servers to system consoles using Ethernet ports

• Can include many clients, servers, routers, and bridges

• Provides extra flexibility in locating system consoles

• Allows system consoles outside the dedicated LAN to access the server

• Is used only by the OSM Service Connection, the TSM Service Application, and the OSM or TSM Event Viewer.

Construct a Nondedicated (Public) LAN ConfigurationYou can connect system consoles to a nondedicated (public) LAN if the following conditions are true:

To connect system consoles to a nondedicated (public) LAN, use the server’s E4SA, FESA, or GESA ports.

Caution. System consoles that act as a primary or backup system console must connect to a dedicated LAN. See Section 6, Connecting a System Console.

If you are using OSM If you are using TSMYour server is running the G06.08 or later RVU.

Your server is running the G06.04 or later RVU.

You have installed SPR T7945AAG or later.


Configuring the System Construct a Nondedicated (Public) LANConfiguration

Figure 10-11. LAN Configurations: Nondedicated (Public) and Dedicated

VST061.vsd

BackupSystemConsole

Modem


Switch 1

Note: Do not use this figure as a wiring diagram. Actual connections vary depending on your Ethernet switch.

Switch 2

EthernetSwitches

Dedicated LAN

EthernetPort onPMFCRU

50 55

51 52 53 54

56

Modem

Ethernet Porton E4SA orFESA

Public LAN

Publ

ic L

AN

Remote Service ProviderRemote Service Provider



Procedure1. Connect the system console to the nondedicated (public) LAN as shown in

Figure 10-11.

a. Connect the Ethernet cable to the 10Base-T connector on the network interface card (NIC) at the back of the system console.

b. Connect the other end of the Ethernet cable to the nondedicated (public) LAN.

c. Connect the nondedicated (public) LAN to the ServerNet adapter.

d. On the system console, configure the IP address for the console, and the subnet mask and gateway for the nondedicated (public) LAN, as described in Step 3 on page 10-4.

2. Install OSM or version 7.0 or later of the TSM client software. See the applicable documentation:

° NonStop System Console Installer Guide

° TSM Online User Guide

° OSM Migration Guide

When asked if the workstation is installed on a dedicated LAN, click No.

The OSM package should already be installed on the workstation, but it might be configured for a dedicated LAN. If so, all OSM client applications appear in the OSM Start Menu shortcuts, but you can use only the TSM Service Application, the OSM Service Connection, and the OSM or TSM Event Viewer.

3. Use the OSM Service Connection or TSM Service Application to enter the IP addresses for the ServerNet adapter. For instructions using TSM, see the TSM Configuration Guide, For OSM, see the OSM Migration Guide.

4. Specify the TCP/IP process associated with the ServerNet adapter. For TSM, use TEDIT or EDIT (see theTSM Configuration Guide). For OSM, see the OSM Migration Guide.

5. Configure the OSM or TSM Event Viewer to use the TCP/IP process associated with the ServerNet adapter. For instructions, see the OSM Migration Guide or TSM Configuration Guide.

6. Test the nondedicated (public) LAN connection:

a. For OSM:

For the configuration changes made in the OSMCONF file (in steps 3-5) to take effect, use the Reload Configuration Settings option from the Tools menu in the OSM Service Connection. See the OSM User’s Guide for more information.

For TSM:



1. Wait 30 minutes to ensure that the server has executed the changes in the TSMINI file for TSM.

2. Start and log on to the TSM Service Application.

For more information on the nondedicated (public) LAN, see the LAN Configuration and Management Manual and the Ethernet Adapter Installation and Support Guide.




11 Offline Configuration TasksThis section describes offline configuration tasks, which change software or hardware configurations and require the system to be shut down.

Changes That Must Be Made OfflineA few configuration changes must be made offline:

• Installing a new RVU.

• Installing a product revision, such as a software product revision (SPR), that requires a system load.

• Making configuration changes that either cannot be made using an online configuration tool or require a system load to take effect, such as changing the system name.

• Changing the system topology.

• Changing the configuration of the QIOMON process.

• Changing the CONFTEXT file.

• Some online PMF CRU upgrades are not allowed. To see what upgrades can be made online, see the NonStop S-Series Planning and Configuration Guide. No others are supported.

Offline changes are usually performed during a planned outage. For more information about planned outages, see the NonStop S-Series Planning and Configuration Guide.

Topic PageChanges That Must Be Made Offline 11-1

Application Reconfiguration 11-2

Installing a New RVU 11-2

Installing a Product Revision 11-2

Changing System Name, System Number, or Time Attributes 11-3

Changing the System Topology 11-3

Changing the CONFTEXT File 11-3


Offline Configuration Tasks Application Reconfiguration

Application ReconfigurationReconfiguring an application can sometimes require that the application be taken offline. A discussion of application reconfiguration is beyond the scope of this guide. However, the Availability Guide for Application Design provides information on designing highly available applications.

Installing a New RVUHP currently requires that you shut down your system to activate a new version of the operating system. By using the Distributed Systems Management/Software Configuration Manager (DSM/SCM), your current system can continue to run while you create a new SYSnn; you have to shut down the system only to perform the system load.

To install a new RVU, perform the tasks described in the G06.nn Software Installation and Upgrade Guide. These tasks involve:

• Receiving the new software into the archive and creating the new software revision.

• Building and applying a software revision to the target system.

• Activating the new software on the target system. The activation instructions created by DSM/SCM indicate the steps to perform, such as performing a system load or updating the firmware.

Installing a Product RevisionA product revision, such as an SPR, might include one or more fixes to programs supplied by HP, or it might contain code that adds new function to an HP software product. Installing a product revision might or might not require that the system be shut down. Follow the installation instructions provided with the product revision. The DSM/SCM User’s Guide describes installing product revisions in detail.


Offline Configuration Tasks Changing System Name, System Number, or TimeAttributes

Changing System Name, System Number, or Time Attributes

After the first system load, use SCF to modify the values for the following system attributes:

• SYSTEM_NAME• SYSTEM_NUMBER• TIME_ZONE_OFFSET • DAYLIGHT_SAVINGS_TIME

See the SCF Reference Manual for the Kernel Subsystem.

Because the attributes that change the system name and Expand system (node) number are stored in a SEEPROM in the enclosure backplane, changes to them require a system reset and reload to take effect. If you do not modify these attribute values, they default to the values shipped by HP:

Changing the System TopologyIf you want or need to change the topology of a system, you must shut down the system. The NonStop S-Series System Expansion and Reduction Guide gives complete information about the procedures necessary to reconfigure your system offline.

Changing the CONFTEXT FileAny changes to the CONFTEXT file take effect after the next system load. If you want to modify the CONFTEXT file, see the System Generation Manual for G-Series RVUs.

The modified CONFTEXT file is used by DSM/SCM when generating a new operating system image. See the DSM/SCM User’s Guide.

SYSTEM_NAME \NONAMESYSTEM_NUMBER 254TIME_ZONE_OFFSET 0:00 (London)DAYLIGHT_SAVINGS_TIME NONE

Caution. Changing the system name or Expand system (node) number is intended for a newly installed system. If you change the system name or system number on an existing system and are running complex applications like NonStop SQL/MP, HP NonStop Transaction Management Facility (TMF), or HP NonStop Open System Services (OSS), you must reconfigure the applications and take additional precautions to avoid losing data.


Offline Configuration Tasks Changing the CONFTEXT File


12 Online Configuration TasksThis section describes how to configure your system online using the Subsystem Control Facility (SCF), Kernel-Managed Swap Facility (KMSF), OSM, and TSM, and how to create an alternate $SYSTEM disk.

Topic PageSCF 12-2

Initial CONFIG file 12-2

Subsystems in G-Series RVUs 12-3

Generic Processes 12-4

Making Important Processes Persistent 12-5

Types of System Configuration Files 12-6

KMSF 12-8

Initial Configuration of KMSF Swap Files 12-8

Changing the Configuration of KMSF Swap Files 12-8

KMSF and the Operations Environment 12-8

The OSM and TSM Packages 12-9

Creating an Alternate System Disk 12-10

1. Choose the Target Disk and Plan Its Space and Files 12-11

2. Verify That the Target Disk Is Present 12-12

3. Stop Access to the Target Disk and Display Its Status 12-12

4. Change the Label of the Target Disk 12-13

5. Create a New System Volume and a System Image Tape (SIT) 12-14

6. Install the Boot Millicode on the Target Disk 12-14

7. Verify the Installation of Boot Millicode on the Target Disk 12-15

8. Copy Subvolumes to the Target Disk 12-16


Online Configuration Tasks SCF

SCFThe Subsystem Control Facility (SCF) configures, controls, and collects information about subsystems and the objects (devices, subdevices, processes, and so forth) belonging to each subsystem.

Using SCF commands, you can:

• Add, alter, or delete objects (such as I/O processes or generic processes) in the system configuration

• Obtain configured or current information about objects

System configuration changes that are made online using SCF take effect as soon as the object is restarted (using the SCF START command). For subsystems that are new for the G-series, these changes are permanent; that is, they persist through processor and system loads (unless you load the system with a different configuration file).

The general method for performing SCF configuration changes is:

1. Create a command file containing the SCF commands to implement a configuration change.

2. For fallback purposes, save the current configuration database CONFIG file using the SCF SAVE command. The following example saves the current CONFIG file to a file named CONF0102 on the $SYSTEM.ZSYSCONF subvolume:

-> SAVE CONFIGURATION 1.2

3. Invoke the command file created in Step 1. For example:

-> OBEY SCFCONF

If the most recent change results in a problem, you can fall back to a known, stable configuration by loading the system from the saved configuration file. These steps are described in detail in the SCF Reference Manual for G-Series RVUs.

Initial CONFIG fileWhen a system is delivered, the $SYSTEM.ZSYSCONF.CONFIG file contains a standard system configuration created by HP. The contents of this file, called the initial CONFIG file, are described in NonStop S-Series Planning and Configuration Guide.

This initial CONFIG file is also saved on your system as the ZSYSCONF.CONF0000 file. See the SCF Reference Manual for G-Series RVUs for example displays from the CONF0000 file.


Online Configuration Tasks Subsystems in G-Series RVUs

Subsystems in G-Series RVUsA system running a G-series RVU has multiple subsystems that handle the configuration and management of subsystem-specific generic processes, I/O processes, and system hardware. This illustration is an overview of the configuration components in these systems.

Figure 12-1. Subsystems in G-Series RVUs

Component FunctionCONFIG system configuration database file

Contains information about the location and characteristics of all system components. This file is on the $SYSTEM.ZSYSCONF subvolume.

$ZCNF configuration utility process

Is the database server for the subsystem managers and monitor processes. Controls access to the system configuration database. Manages requests for information about the CONFIG file. Starts and maintains the $ZPM persistence manager process.

$ZPM persistence manager process

Starts and maintains persistence of subsystem managers and monitor processes. Starts, stops, and (optionally) restarts generic processes.Coordinates system load and processor reload activities.

Subsystem managers and monitor processes

Configure and control subsystem devices.

$ZZSTO$ZZLAN

$ZZKRN $ZZWAN

$ZPM$ZCNF

CONFIG

$SYSTEM.ZSYSCONF.CONFIG

CommunicationsSubsystems

$ZZxyz

VST115.vsd


Online Configuration Tasks Generic Processes

Each subsystem manager or monitor process is started by the $ZPM persistence manager process at system load and has the following functions:

• Creates I/O processes and other manager processes within the subsystem

• Configures subsystem objects such as adapter hardware and the ServerNet addressable controllers (SACs) supported by those adapters

• Identifies the names of processes that must be reserved at system load

• Monitors its processes to immediately re-create any process that has terminated (if it was configured to be persistent)

Each configuration manual listed in the NonStop S-Series Planning and Configuration Guide describes a subsystem, the objects the subsystem supports, and how to configure those objects.

You can display information about the following generic processes for G-series RVUs that are subsystem managers or monitor processes.

Generic ProcessesGeneric processes can be created by the operating system or by a user. Examples of generic processes created by a user are an HP program, a third-party program, or a user-written program that you configure to be controlled by the operating system.

When the system is started, all generic processes that are configured to be persistent are started automatically by the $ZPM persistence manager or by the subsystem manager, which is started by $ZPM.

See the SCF Reference Manual for the Kernel Subsystem for more information about generic processes.

Subsystem Process ATM $ZZATM, the Asynchronous Transfer Mode (ATM) monitor process

Expand $ZEXP, the Expand manager process

Kernel $ZZKRN, the Kernel subsystem manager process

PAM $ZZPAM, the Port Access Method (PAM) manager process

QIO $ZMnn, the Query I/O (QIO) monitor process in processor nn

ServerNet/FX adapter

$ZZFOX, the FOX monitor process

SLSA $ZZLAN, the ServerNet LAN Systems Access (SLSA) subsystem manager process

Storage $ZZSTO, the storage subsystem manager process

WAN $ZZWAN, the wide area network (WAN) subsystem manager process


Online Configuration Tasks Making Important Processes Persistent

Making Important Processes PersistentYou can make important system processes, such as the Expand manager process or the Subsystem Control Point (SCP) process, start automatically at system load and be persistent (that is, restart automatically if stopped abnormally) by creating them as generic processes in the system configuration database and specifying the AUTORESTART parameter.

This example SCF command file adds persistent generic processes for the CLCI TACL, Expand manager, and SCP processes. This file can be invoked by the following TACL command:

> SCF / IN GPADD /

== This file is GPADD

== Adds the CLCI TACL, Expand manager, and SCP processes as generic== processess.

============================================================================ CLCI TACL ============================================================================ADD PROCESS $ZZKRN.#CLCI-TACL, NAME $CLCI, PRIORITY 199, & AUTORESTART 10, PROGRAM $SYSTEM.SYSTEM.TACL, PRIMARYCPU 0, & BACKUPCPU 1, TYPE OTHER, STARTMODE MANUAL, HOMETERM $YMIOP.#CLCI, & INFILE $YMIOP.#CLCI, OUTFILE $YMIOP.#CLCI, STARTUPMSG "<BCKP-CPU>"============================================================================ Expand manager process ============================================================================ADD PROCESS $ZZKRN.#ZEXP, NAME $ZEXP, PRIORITY 180, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.OZEXP, PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER, & STARTMODE SYSTEM, HOMETERM $ZHOME, OUTFILE $ZHOME, & STARTUPMSG "<BCKP-CPU>"============================================================================ SCP ============================================================================ADD PROCESS $ZZKRN.#SCP, NAME $ZNET, PRIORITY 175, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.SCP, PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER, & STARTMODE SYSTEM, HOMETERM $ZHOME, OUTFILE $ZHOME, & STARTUPMSG "<BCKP-CPU> ; AUTOSTOP -1"


Online Configuration Tasks Types of System Configuration Files

Types of System Configuration Files On systems running G-series RVUs:

• Most I/O processes are not prebuilt by SYSGENR. Rather, the subsystems send information about these processes into the system configuration database.

• The SYSnn.OSCONFIG file contains only Software Problem Isolation and Fix Facility (SPIFF) and Software ID (SWID) records.

• The system configuration database files are stored on the $SYSTEM.ZSYSCONF subvolume, independent of the SYSnn subvolume on which the operating system is running.

The system configuration files used on systems running G-series RVUs are:

See the TSM Configuration Guide or the OSM User’s Guide for instructions on how to select a system configuration file during system load.

File Type File Name DescriptionOn the $SYSTEM.SYSnn subvolume:Base CONFIG

CONFBASE Contains the minimal configuration to load the system. You use this file when you want to rebuild the system configuration from the absolute minimum configuration.

File Type File Name DescriptionOn the $SYSTEM.ZSYSCONF subvolume:Input to initial CONFIG

SCF0000 Is used to create the CONF0000 file, which HP uses to configure and test a standard system before shipment.

Current CONFIG

CONFIG Contains the current system configuration.

Saved CONFIG

CONFxxyy Contains a copy of a CONFIG file, saved for future use. You can use one of these files to return to an earlier, stable configuration. The file-naming convention is to let xx indicate a major configuration change and yy indicate a minor change.

Autosaved CONFIG

CONFSAVE Contains a saved version of the current CONFIG file that the operating system automatically creates when you load the system from a saved CONFIG file.

If you load the system from CONFBASE or a CONFxxyy file to abandon a corrupt configuration, HP can analyze the corrupt configuration file to determine the reason for the corruption. If the CONFSAVE file is not corrupt, you can use it to reload the system if you first rename it to CONFxxyy.


Online Configuration Tasks Types of System Configuration Files

This figure illustrates the differences among the types of system configuration files.

Figure 12-2. Differences Among System Configuration Files

VST911.vsd

+ =Initial CONFIG File

Initial CONFIG

CONF0000

SCF0000 FileBase CONFIG

CONFBASE

Normal System Load

Current CONFIG

CONFIG

+Saved Configuration =

Saved CONFIG

CONFIG

Current CONFIG

CONFIG

-> SCF SAVE

Automatically Saved Configuration

Current CONFIG

CONFIG

System Load FromAnother CONFIG File

Current CONFIG

CONFIGAutosaved CONFIG

CONFSAVE


Online Configuration Tasks KMSF

KMSFKernel-managed swap space manages virtual memory using swap files controlled by the operating system. During a shortage of available physical memory, pages of memory not currently in use are swapped, or copied, to disk. These memory pages are swapped back or overwritten to physical memory when the code or data is needed. When swapped to disk, the data is stored in swap files. Through the Kernel-Managed Swap Facility (KMSF), the operating system opens one or more swap files for each processor and manages the files for all the processes needing them.

Proper configuration and management of kernel-managed swap space is critical to system operation.

When you set up a new system, you must configure KMSF swap files. Using the guidelines provided in the Kernel-Managed Swap Facility (KMSF) Manual, you decide:

• How much swap space you should configure• Where to place swap files• What guidelines to create for operations staff on monitoring and altering swap files

Initial Configuration of KMSF Swap FilesNew systems are initially configured with these default KMSF swap files:

Changing the Configuration of KMSF Swap FilesChange the configuration of KMSF swap files if:

• Your system is using default swap file configurations. These configurations are minimums for system load. To run most applications, you must configure additional swap files.

• You want to increase the number or size of your swap files.

• You want to change the location of one or more swap files.

KMSF and the Operations EnvironmentKMSF affects routine operations. Operations staff must monitor KMSF and operator messages to spot potential problems and dynamically add swap space as needed. Event Management Service (EMS) messages are generated to alert staff to swap files that have reached a configured threshold and to changes in KMSF configuration.

Attribute ValueLocation $SYSTEM

Number 1 swap file for each processor

Name $SYSTEM.ZSYSSWAP.SWAPnn, where nn is the processor number

Size 128 MB with at least 64 MB allocated


Online Configuration Tasks The OSM and TSM Packages

The OSM and TSM PackagesThe OSM and TSM packages are collections of software products that provide troubleshooting, maintenance, and service tools.

WIth the OSM or TSM package, you can make these configuration changes online:

• Verify and update firmware for components.• Implement remote monitoring and maintenance functions.• Specify IP addresses of system consoles and the master service processors.

With the OSM or TSM Notification Director and the OSM or TSM Low-Level Link, you can configure:

• User names and passwords for the OSM or TSM package (for security)• Remote dial-in access to the system from a service provider• Remote access from the system to an unattended line• Remote dial-out access from the system to a service provider• IP addresses for the dedicated local area network (LAN)

For information you need to configure remote access, contact your service provider.

For information about performing configuration changes, see:• OSM Low-Level Link online help• OSM Notification Director online help• OSM User’s Guide• TSM Configuration Guide • TSM Low-Level Link online help• TSM Notification Director online help• TSM Online User Guide

For a more detailed comparison of OSM and TSM functionality, see: • OSM Migration Guide• OSM User’s Guide


Online Configuration Tasks Creating an Alternate System Disk

Creating an Alternate System Disk

Reasons to create an alternate system disk include:

• Minimizing unplanned outage minutes by having an alternate system disk configured as a backup.

• Avoiding planned outages by configuring an alternate system disk to use in case you must stop your current system disk.

• Keeping your system running with the alternate system disk while the main system disk is offline.

For more information, see the DSM/SCM User’s Guide.

Step Page1. Choose the Target Disk and Plan Its Space and Files 12-11

2. Verify That the Target Disk Is Present 12-12

3. Stop Access to the Target Disk and Display Its Status 12-12

4. Change the Label of the Target Disk 12-13

5. Create a New System Volume and a System Image Tape (SIT) 12-14

6. Install the Boot Millicode on the Target Disk 12-14

7. Verify the Installation of Boot Millicode on the Target Disk 12-15

8. Copy Subvolumes to the Target Disk 12-16


Online Configuration Tasks 1. Choose the Target Disk and Plan Its Space andFiles

1. Choose the Target Disk and Plan Its Space and Files The target disk is the disk that will become the alternate system disk. Before choosing the target disk, plan its space and the files that will be stored on it.

Ensure that this target disk has enough room for the subvolumes it will hold. The best way to do this is to set aside an entire disk as the target disk. If you cannot set aside an entire disk, you might need to purge files from the disk you will use.

Plan your alternate system disk using the following considerations:

• Allow enough space on the target disk for the Kernel-Managed Swap Facility (KMSF) to operate.

• Ensure that all the files that will remain on the target disk can still be accessed when it is used as an alternate system disk. For example, you cannot have audited files on the alternate system disk if your TMF audit trails also are located on that disk.

• Ensure that your startup files, such as the CIIN file, refer to $SYSTEM.

Note. The default KMSF swap files immediately allocate 64 megabytes of swap space and can grow to a maximum size of 128 megabytes. However, the Kernel-Managed Swap Facility (KMSF) Manual recommends that you initially configure a swap file of 512 megabytes for each processor. Because the optimal amount of swap space varies, you should adjust the size of the swap files depending on system use and workflow patterns.

As much as 2 gigabytes could be required for a processor with 1 gigabyte of memory.

HP recommends configuring KMSF swap files instead of using the default KMSF swap files because many processes require more swap space than is provided by default swap files. Insufficient swap space can result in errors, process failures, and processor halts.


Online Configuration Tasks 2. Verify That the Target Disk Is Present

2. Verify That the Target Disk Is PresentUse SCF to verify that the target disk you have chosen is physically present on the system. In this example, the target disk is $DATA08. 7-> status $data08,detailSTORAGE - Detailed Status DISK \WAGER.$DATA08

Disk Path Information: LDev Path Status State Substate Primary Backup PID PID

74 PRIMARY ACTIVE STARTED 2,261 74 BACKUP INACTIVE STARTED 2,261 74 MIRROR ACTIVE STARTED 2,261 74 MIRROR-BACKUP INACTIVE STARTED 2,261

General Disk Information: Device Type........... 3 Device Subtype........... 42 Primary Drive Type.... 4608-1 Mirror Drive Type........ 4608-1 Physical Record Size.. 4096 Priority................. 220 Library File.......... Program File.......... \WAGER.$SYSTEM.SYS00.TSYSDP2 Protection............ MIRRORED

Hardware Information:Path Location Power Physical Status (group,module,slot)

PRIMARY (2,1,17) DUAL PRESENT MIRROR (2,1,18) DUAL PRESENT

3. Stop Access to the Target Disk and Display Its StatusUse the SCF STOP command to stop access to the target disk.

You can use the SCF STATUS command to check whether access to that disk has been stopped. 8-> stop $data08STORAGE W01007 The STOP DISK $DATA08 operation will cause \WAGER.$DATA08 to be INACCESSIBLE to user processes.Do you want to STOP DISK \WAGER.$DATA08 (Y/[N])y

9-> status $data08STORAGE - Status DISK \WAGER.$DATA08LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 74 STOPPED STOPPED STOPPED STOPPED 2,262


Online Configuration Tasks 4. Change the Label of the Target Disk

4. Change the Label of the Target DiskUse SCF to change the label of the target disk.

In this example, the preferred volume name is set to $SYSTEM, and the alternate name is not changed. 12-> info $data08, labelSTORAGE - Label Information DISK \WAGER.$DATA08 Disk Label Information $DATA08 Primary: *Volume Name.......................... $SYSTEM *Alternate Volume Name................ $DATA08 Volume ID............................ 19 Volume Label Verifier................ D2 Volume Label Version................. 0 Operating System Last Mounted Under.. F40 (P40) Volume Label Last Written............ 02 Apr 1997, 16:41:06.036 Disk Subtype......................... 42

Section Name Address Length Version Parameter -------------------- ------------- ------------- ------- ------------- 0. Spare Tracks Table 000000.003000 000000.005000 0 000000.000000 1. Boot 000000.000000 000000.000000 0 000000.000000 2. Free Space Table 000000.010000 000000.020000 0 000000.000000 3. Directory Label 000000.110000 000000.010000 0 000000.000000 4. Unused 000000.000000 000000.000000 0 000000.000000 5. Undo 000000.120000 000000.020000 0 000000.000000 6. Pool 000000.000000 000000.000000 0 000000.000000 10. Pool-LSA 000000.000010 000407.061554 3 000000.000000 11. Free Space Table-LSA 000000.000010 000000.000020 3 000000.000000 12. Boot-LSA 000000.000000 000000.000000 0 000000.000000

Disk Label Information $DATA08 Mirror: *Volume Name.......................... $SYSTEM *Alternate Volume Name................ $DATA08 Volume ID............................ 19 Volume Label Verifier................ D2 Volume Label Version................. 0 Operating System Last Mounted Under.. F40 (P40) Volume Label Last Written............ 02 Apr 1997, 16:41:06.036 Disk Subtype......................... 42



Online Configuration Tasks 5. Create a New System Volume and a SystemImage Tape (SIT)

5. Create a New System Volume and a System Image Tape (SIT)Create a new system volume and a system image tape (SIT) for the target disk.

You can create a system volume in either of these ways:

• Use DSM/SCM to place needed subvolumes on the target disk.

• Back up the original subvolumes to tape and then restore them to the target disk.

For more information on either of these procedures or the procedure for creating a SIT, see the DSM/SCM User’s Guide.

6. Install the Boot Millicode on the Target DiskUse SCF to install the boot millicode on the target disk. In this example, the boot millicode is installed on $DATA08.13-> control $data08, replaceboot $system.sys00.sysdiscSTORAGE W01012 The CONTROL DISK, REPLACEBOOT operation will OVERWRITE the existing bootstrap on $DATA08.Are you sure you want to REPLACE the bootstrap on $DATA08 (Y/[N])ySTORAGE W01013 To protect you against failure when replacing the bootstrap file on $DATA08, SCF can place $DATA08-M in a STOPPED summary state, substate HARDDOWN.Do you want to abort $DATA08-M (Y/[N])n


Online Configuration Tasks 7. Verify the Installation of Boot Millicode on theTarget Disk

7. Verify the Installation of Boot Millicode on the Target DiskUse the SCF INFO, LABEL command to verify that the boot millicode was installed correctly.

In this example, section 12 (Boot-LSA) shows that the address and length values are now nonzero values. 14-> info $data08, labelSTORAGE - Label Information DISK \WAGER.$DATA08 Disk Label Information $DATA08 Primary: *Volume Name.......................... $SYSTEM *Alternate Volume Name................ $DATA08 Volume ID............................ 20 Volume Label Verifier................ D2 Volume Label Version................. 0 Operating System Last Mounted Under.. F40 (P40) Volume Label Last Written............ 02 Apr 1997, 16:41:45.006 Disk Subtype......................... 42


Disk Label Information $DATA08 Mirror: *Volume Name.......................... $SYSTEM *Alternate Volume Name................ $DATA08 Volume ID............................ 20 Volume Label Verifier................ D2 Volume Label Version................. 0 Operating System Last Mounted Under.. F40 (P40) Volume Label Last Written............ 02 Apr 1997, 16:41:45.006 Disk Subtype......................... 42



Online Configuration Tasks 8. Copy Subvolumes to the Target Disk

8. Copy Subvolumes to the Target DiskYou might want to copy these subvolumes to the target disk. These are examples only; your files and subvolumes might be different.

Also copy any subvolume that contains configuration information, such as the subvolume that contains your TCP/IP HOSTS file (normally $SYSTEM.ZTCPIP).

File LocationAll copies of the system configuration database

$SYSTEM.ZSYSCONF.*

OSM subvolumes $SYSTEM.ZSERVICE.*$SYSTEM.ZOSM.*$SYSTEM.ZOSMLH.*

TSM subvolumes $SYSTEM.ZSERVICE.*$SYSTEM.ZTSM.*

System startup files For example, $SYSTEM.STARTUP.*

System shutdown files For example, $SYSTEM.SHUTDOWN.*

Spooler data files For example, $SYSTEM.SPL.*


Online Configuration Tasks Create a Command File

Create a Command FileA command file can automate the task of reconfiguring paths that have been stopped or deleted. For example, a set of disk drives can be added in one operation rather than one at a time. The command file must be constructed before the system is prepared to lose access to the paths.

To prepare a command file that configures a disk drive:

1. Create an editable file by issuing the SCF LOG command:

-> SCF LOG [ logfile-spec [ ! ] ]

2. Write to this file by issuing the SCF INFO DISK, OBEYFORM command:

-> INFO DISK $disk-name, OBEYFORM

where $disk-name is a disk to be reconfigured by the command file.

3. Stop writing to this log file by either exiting from SCF or using the SCF LOG command:

->LOG

-> SCF LOG LOGFILE43

-> info $data3,obeyform

ADD DISK $data3 , & SENDTO STORAGE , & BACKUPCPU 3 , & HIGHPIN ON , & PRIMARYCPU 2 , & PROGRAM $SYSTEM.SYSTEM.TSYSDP2 , & STARTSTATE STARTED, & PRIMARYDEVICEID 0 , & PRIMARYLOCATION (2,1,54) , & PRIMARYSAC 3 , & BACKUPDEVICEID 0 , & BACKUPLOCATION (2,1,54) , & BACKUPSAC 4 , & AUDITTRAILBUFFER 0 , & AUTOREVIVE OFF, & AUTOSTART ON, & CBPOOLLEN 1000 , & FSTCACHING OFF , & FULLCHECKPOINTS ENABLED , & HALTONERROR 1 , & LKIDLONGPOOLLEN 8 , & LKTABLESPACELEN 15 , & MAXLOCKSPEROCB 5000 , & MAXLOCKSPERTCB 5000 , & NUMDISKPROCESSES 4 , & OSSCACHING ON , & PROTECTDIRECTORY SERIAL , & REVIVEBLOCKS 1 , & REVIVEINTERVAL 100 , & SERIALWRITES ENABLED-> log


Online Configuration Tasks Create a Command File

4. Edit this log file to create a command file:

• Remove the top line (the INFO command).

• Remove the bottom line (the LOG command).

• Update the locations for any affected adapters (PRIMARYLOCATION and BACKUPLOCATION).

5. Save this command file for later use.

== STORAGE - Obeyform Information Magnetic DISK \S3.$data3ADD DISK $data3 , & SENDTO STORAGE , & BACKUPCPU 3 , & HIGHPIN ON , & PRIMARYCPU 2 , & PROGRAM $SYSTEM.SYSTEM.TSYSDP2 , & STARTSTATE STARTED, & PRIMARYDEVICEID 0 , & PRIMARYLOCATION (1,1,53) , & PRIMARYSAC 3 , & BACKUPDEVICEID 0 , & BACKUPLOCATION (1,1,53) , & BACKUPSAC 4 , & AUDITTRAILBUFFER 0 , & AUTOREVIVE OFF, & AUTOSTART ON, & CBPOOLLEN 1000 , & FSTCACHING OFF , & FULLCHECKPOINTS ENABLED , & HALTONERROR 1 , & LKIDLONGPOOLLEN 8 , & LKTABLESPACELEN 15 , & MAXLOCKSPEROCB 5000 , & MAXLOCKSPERTCB 5000 , & NUMDISKPROCESSES 4 , & OSSCACHING ON , & PROTECTDIRECTORY SERIAL , & REVIVEBLOCKS 1 , & REVIVEINTERVAL 100 , & SERIALWRITES ENABLED


13Creating Startup and Shutdown Files

This section describes command files that automatically start and shut down a NonStop S-series server.

Automating System Startup and Shutdown 13-2

Startup 13-2

Shutdown 13-2

For More Information 13-2

Processes That Represent the System Console 13-3

Example Command Files 13-5

CIIN File 13-6

Tips for Startup Files 13-9

How Process Persistence Affects Configuration and Startup 13-9

Startup File Examples 13-10

System Startup File 13-10

Spooler Warm-Start File 13-12

TMF Warm-Start File 13-12

TCP/IP Stack Configuration and Startup File 13-12

CP6100 Lines Startup File 13-15

ATP6100 Lines Startup File 13-15

X.25 Lines Startup File 13-15

Printer Line Startup File 13-16

Expand-Over-IP Line Startup File 13-16

Expand Direct-Connect Line Startup File 13-16

Tips for Shutdown Files 13-17

Shutdown File Examples 13-17

System Shutdown File 13-18

CP6100 Lines Shutdown File 13-19

ATP6100 Lines Shutdown File 13-19

X.25 Lines Shutdown File 13-19

Printer Line Shutdown File 13-20

Expand-Over-IP Line Shutdown File 13-20

Direct-Connect Line Shutdown File 13-20

Spooler Shutdown File 13-21

TMF Shutdown File 13-21



Creating Startup and Shutdown Files Automating System Startup and Shutdown

Automating System Startup and ShutdownStartup

You can use startup command files to automate the starting of devices and processes on the system, which minimizes the possibility of operator errors caused by forgotten or mistyped commands.

The system is shipped with a basic startup file named CIIN, located on the $SYSTEM.SYS00 subvolume. The CIIN file must be specified in a particular way. See CIIN File on page 13-6 for more information.

After the commands in the CIIN file are executed, other startup files can be invoked either automatically, from another startup file, or manually in commands entered by the operator. The startup file sequence usually starts the spooler and other system software first and then starts applications.

ShutdownAutomating system shutdown with a collection of shutdown files helps the operator bring the system to an orderly halt. The shutdown file sequence reverses the order of commands in the startup file sequence: applications are shut down first, followed by the spooler and other system software.

For More Information For information about ... SeeConfiguring the spoolers Spooler Utilities Reference Manual

Configuring and managing Pathway applications

TS/MP System Management Manual

Configuring and managing TMF TMF Planning and Configuration Guide

TMF Operations and Recovery Guide

Configuring and managing TRANSFER applications

TRANSFER Installation and Management Guide

Configuring and managing your system monitoring environment



Creating Startup and Shutdown Files Processes That Represent the System Console

Processes That Represent the System Console

On NonStop S-series servers, the system console is a pair of windows on a LAN-connected system console. It is represented by the processes $YMIOP.#CLCI and $YMIOP.#CNSL, and the home terminal is represented by the $ZHOME process pair.

$YMIOP.#CLCI$YMIOP.#CLCI is the primary interactive terminal for the operator interface to the system.

This process:

• Runs on the system console• Is preconfigured on your system during system generation

TACL processes are started on $YMIOP.#CLCI by commands in the CIIN file. If a read operation is pending, such as a TACL prompt on $YMIOP.#CLCI, write operations are blocked, causing the process attempting the write operation to wait indefinitely.

$YMIOP.#CNSL$YMIOP.#CNSL is a write-only device for logging.

This process:

• Runs on the system console• Is preconfigured on your system during system generation

$ZHOMEThe $ZHOME process is a process pair that provides a reliable home terminal to which processes can perform write operations. The $ZHOME process can be used by processes that must write to the system console but do not require a response.

$ZHOME is preconfigured on your system by the CONFBASE file. $ZHOME is a generic process that is part of the SCF Kernel subsystem. Note the following about the configuration of $ZHOME:

• The $ZHOME process is configured with $YMIOP.#CLCI as its HOMETERM, INFILE, and OUTFILE.


Creating Startup and Shutdown Files $ZHOME Alternative

• Because $ZHOME acts as a reliable home terminal designed to interact with the system console, $YMIOP.#CLCI, HP recommends that you do not change its configuration. Most important:

° Do not specify $ZHOME for the INFILE, OUTFILE, or HOMETERM for the $ZHOME process.

° Never specify $ZHOME for the INFILE for a process. The $ZHOME process returns the FEINVALOP error (file-system error 2) in response to any read operation.

• Generic processes started by the $ZPM persistence manager inherit $YMIOP.#CLCI as the HOMETERM, INFILE, and OUTFILE unless these attributes are changed in the configuration record for the generic process. HP recommends that you configure most NonStop Kernel and system-level generic processes to use $ZHOME for the HOMETERM and OUTFILE.

$ZHOME AlternativeInstead of $ZHOME, you might want to use the optional NonStop Virtual Hometerm Subsystem (VHS) product if both of the following conditions are true:

• The processes you are configuring cannot handle error responses returned if $YMIOP.#CNSL or $YMIOP.#CLCI is not available.

• The process must perform read operations to the device.


Creating Startup and Shutdown Files Example Command Files

Example Command FilesThis section describes and shows examples of command files that can be used to start up and shut down the server:

• Examples and sample programs are for illustration only and might not be suited for your particular purpose.

HP does not warrant, guarantee, or make any representations regarding the use or the results of the use of any examples or sample programs in any documentation. You must verify the applicability of any example or sample program before placing the software into production use.

• These examples are for a system whose configuration has been changed from the factory-installed configuration. Your system’s initial configuration will differ from these examples.

• The examples in this section are based on the examples in Appendix 14, Case Study: Installing and Configuring a System.

The startup files in this section assume that the objects they start have already been added to the configuration database for the system. For examples of files that add these objects to the configuration database, see Appendix 14, Case Study: Installing and Configuring a System.

• The IP addresses used in this section are examples only. If you use the example files described in this section on your system, you must change the IP addresses in these examples to IP addresses that are appropriate for your LAN environment.

• The configuration track-ID for the SWAN concentrator used in the example files, X001XX, is also an example.

If you use the example files described in this section on your system, you must change the configuration track-ID used in these examples to the actual configuration track-ID assigned to your SWAN concentrator.


Creating Startup and Shutdown Files CIIN File

CIIN FileThe CIIN file contains a limited set of commands that usually:

• Start a TACL process pair on the system console for the system console TACL window ($YMIOP.#CLCI)

When the startup TACL executes the commands in the CIIN file and terminates, the $YMIOP.#CLCI process pair lets you log on to the system and complete the system startup.

OSM or TSM software lets you define primary and backup IP addresses for TACL windows. For more information about configuring OSM or TSM software, see the OSM User’s Guide or the TSM Configuration Guide.

• Load all processors that are not currently running

Alternatively, the CIIN file can reload a minimal set of processors, such as processor 1, to bring up a minimal system. You can then test for successful startup of a minimal system environment before you bring up the remainder of the system.

Establishing a CIIN FileThe CIIN file is configured at the factory as $DSMSCM.SYS.CIIN. You do not need to establish this file. DSM/SCM automatically copies the CIIN file from the initial location into each SYSnn you create.

The name of the CIIN file is specified in the INITIAL_COMMAND_FILE entry of the CONFTEXT configuration file.

The SYSGENR program (run from the DSM/SCM application) copies the file specified in the CONFTEXT file onto the SYSnn subvolume on the disk and renames the file CIIN. If no file is specified in CONFEXT, the operating system does not look for the startup file SYSnn.CIIN at system startup, even if you enable that file. You cannot simply copy a startup file to the SYSnn subvolume and name it CIIN.

For information about SYSGENR, see the System Generation Manual for G-Series RVUs.

Note. Before these TACL processes start, open the appropriate HP Tandem terminal emulator (TTE) windows with the OSM or TSM Low-Level Link. You must open these windows before performing a system load.

Note. The CIIN file must be owned by a member of the super-group (255,n). HP recommends that you specify “N” for the read access portion of the file security attribute (RWEP) to allow the file to be read by any user on the network. For example, you might secure this file “NCCC.”


Creating Startup and Shutdown Files Modifying a CIIN File

Modifying a CIIN FileAfter the CIIN file is established on $SYSTEM.SYSnn (as part of running DSM/SCM), you can modify the contents of SYSnn.CIIN with a text editor such as TEDIT. You need not run DSM/SCM again to make these changes effective.

You might want to modify the RELOAD command in the CIIN file to reload only a minimal set of processors, such as processor 1.

If a CIIN File Is Not Specified or Enabled in OSM or TSMThe results of the startup TACL process varies depending on whether a CIIN file is specified in the CONFTEXT file and whether the CIIN option is enabled.

Note. Do not start other command files in the CIIN file. To ensure proper startup and to facilitate recovery in case of failure, bring up the system in stages, each verified by an operator.

CONFTEXT CIIN Entry and CIIN File

CIIN Option Results

1. CONFTEXT has CIIN entry, and file is available in specified location.

Enabled CIIN is executed by initial (startup) TACL process. Upon completion, this TACL process terminates. You must log on to a different TACL process (the TACL process on $YMIOP.#CLCI started by the CIIN file) to complete the system startup process.

2. CONFTEXT has CIIN entry, and file is available in specified location, but file is empty or aborts because of syntax errors before another TACL process is started.

Enabled CIIN is executed by initial (startup) TACL process. Upon completion, this TACL process terminates, leaving no TACL process available. You must reload the system with the CIIN option disabled in the System Startup dialog box invoked from the OSM or TSM Low-Level Link; then log on and correct the CIIN file. Then, either enable the CIIN option, using the System Startup dialog box, and reload; or complete the system startup process manually.

3. CONFTEXT has CIIN entry, but file is not available in specified location.

Enabled Initial TACL process is started and left in logged-off state. You must log on to complete the system startup process.

4. CONFTEXT has CIIN entry.

Disabled Initial TACL process is started and left in logged-off state. You must log on to complete the system startup process.

5. CONFTEXT has no CIIN entry.

Enabled or disabled

Initial TACL process is started and left logged on to the super ID (255,255). You must initiate the remainder of the system startup process manually and then log off.


Creating Startup and Shutdown Files Example CIIN Files

Example CIIN FilesThis example CIIN file does not include a persistent CLCI TACL process.Comment -- This is the initial command input (CIIN) file for the system.Comment -- If CIIN is enabled in TSM and configured in your CONFTEXTComment -- file, the initial TACL process will read this file andComment -- then terminate.

Comment -- This file is used to reload the remaining processors and Comment -- start a TACL process pair for the system console.

Comment -- Reload the remaining processors.

RELOAD /TERM $ZHOME, OUT $ZHOME/ *

Comment -- Start a TACL process pair for the system console TACL window.Comment -- Use the TSM Low-Level Link to start a TTE session Comment -- for the startup TACL before issuing this command (see theComment -- Start Terminal Emulator command under the File menu).Comment -- These should be the last commands in this file, becauseComment -- the TACL process displays a prompt and attempts to readComment -- from $YMIOP.#CLCI, blocking other processes from writing toComment -- this device.

TACL/TERM $YMIOP.#CLCI, IN $YMIOP.#CLCI, OUT $YMIOP.#CLCI, NAME $SC0, &PRI 199, CPU 0/1TACL/TERM $YMIOP.#CLCI, IN $YMIOP.#CLCI, OUT $YMIOP.#CLCI, NAME $SC0, &PRI 199, CPU 1/0

Comment -- Upon completion of this file, the initial TACL processComment -- terminates. You need to log on to a new TACL sessionComment -- to complete the remainder of the system startup process.

This example CIIN file shows what you would use if you had created a persistent CLCI TACL process by configuring it as a generic process. See Section 12, Online Configuration Tasks.

Comment -- This is the initial command input (CIIN) file for the system.Comment -- If CIIN is enabled in TSM and configured in your CONFTEXTComment -- file, the initial TACL process will read this file andComment -- then terminate.

Comment -- This file is used to reload the remaining processors andComment -- start a TACL process pair for the system console.

Comment -- Reload the remaining processors.

RELOAD /TERM $ZHOME, OUT $ZHOME/ *

Comment -- Use SCF to start a persistent TACL process pair for theComment -- system console TACL window. Comment -- Use the TSM Low-Level Link to start a TTE session

Caution. Situation 5 presents a security issue: the initial TACL process is left logged on to the super ID (255,255). You must either immediately continue with the system startup process (as described in the Results column), log on to another user ID, or log off.

Caution. If you use the following example as is, you must first create the $ZZKRN.#CLCI-TACL process. See Making Important Processes Persistent on page 12-5. If you do not create the $ZZKRN.#CLCI-TACL process first, you might have no access to the system after it loads. To recover, load the system again from another SYSnn or with CIIN disabled.


Creating Startup and Shutdown Files Tips for Startup Files

Comment -- for the startup TACL before issuing this command (see theComment -- Start Terminal Emulator command under the File menu). This SCFComment -- command must be the last command in this file, because the TACLComment -- process creates displays a prompt and attempts to read from Comment -- $YMIOP.#CLCI, blocking other processes from writing to this Comment -- device.

SCF /NOWAIT, OUT/ START PROCESS $ZZKRN.#CLCI-TACL

Tips for Startup FilesHP recommends that you specify “N” for the read access portion of the file security attribute (RWEP) for your startup files to allow the files to be read by any user on the network. For example, you might secure these files “NCCC.”

The sequence in which you invoke startup files can be important. Some processes require other processes to be running before they can be started. Be sure to indicate the order in which your startup files are to be run.

Because the TCP/IP configurations are not stored in the configuration database, they are not preserved after system loads. Therefore, TCP/IP stacks must be configured as well as started each time the system is started.

How Process Persistence Affects Configuration and Startup

When the system is started, all processes that are configured to be persistent are started automatically by the $ZPM persistence manager or by the subsystem manager, which is started by $ZPM.

For example, when the system is started, the WAN subsystem manager automatically starts all WAN I/O processes (IOPs) that were started before the system was shut down. However, communications lines and paths must be started manually by the operator.

To make important system processes like the Expand manager process or the Subsystem Control Point (SCP) process start automatically at system load and be persistent (that is, restart automatically if stopped abnormally), you should create them as generic processes in the system configuration database. See Section 12, Online Configuration Tasks.

For more information about persistence and the $ZPM persistence manager, see the SCF Reference Manual for G-Series RVUs.


Creating Startup and Shutdown Files Startup File Examples

Startup File ExamplesYou can implement the system startup sequence with a collection of startup files, each with a specific purpose. HP recommends that you invoke the startup files in this order:

1. Startup file for the system, to be invoked after the CIIN file is invoked

2. Startup files for the system software

3. Startup files for the subsystems

4. Startup files for the communications lines

5. Startup files for the applications

See the NonStop S-Series Operations Guide for detailed instructions on the startup procedure. For information about automating disk processes upon startup, see the NonStop S-Series Planning and Configuration Guide.

System Startup FileThe following example shows a partial command file that starts up the system software and invokes other startup files.

After the commands in the CIIN file have been executed and the initial system startup sequence is complete, the local operator invokes this file by entering the following TACL command:

> OBEY $SYSTEM.STARTUP.STRTSYS

Comment -- This is $SYSTEM.STARTUP.STRTSYS

comment -- Start the server for labeled tape processing.

ZSERVER / NAME $ZSVR, NOWAIT, PRI 145, CPU 0 / 1ZSERVER / NAME $ZSVR, NOWAIT, PRI 145, CPU 1 / 0MEDIACOM ALTER TAPEDRIVE *, NLCHECK OFF

Comment -- If you have used SCF to start a persistent Subsystem Comment -- Control Process (SCP) process pair, you do not need an Comment -- explicit SCP command to start $ZNET, unless you load the Comment -- system from a different CONFIG file. Comment -- All SCF commands are routed through the SCP process. $ZNET Comment -- routes each request to the appropriate communicationComment -- management process (such as Expand or SNAX).

Comment -- If you have not configured SCP as a persistent generic Comment -- process, remove the commenting from the following SCP Comment -- command and start SCP as a nonpersistent process pair. Comment -- SCP / NAME $ZNET, NOWAIT, PRI 199, TERM $ZHOME, OUT $ZHOME, & Comment -- CPU 0/1; AUTOSTOP -1

Note. Examples and sample programs are for illustration only and might not be suited for your particular purpose. HP does not warrant, guarantee, or make any representations regarding the use or the results of the use of any examples or sample programs in any documentation. You must verify the applicability of any example or sample program before placing the software into production use. For more information, see Example Command Files on page 13-5.


Creating Startup and Shutdown Files System Startup File

Comment -- If you have used SCF to start a persistent $ZEXP Expand Comment -- manager process pair, you do not need an explicit SCP Comment -- command to start $ZEXP, unless you load the system from a Comment -- different CONFIG file.

Comment -- If you have not configured $ZEXP as a persistent generic Comment -- process,remove the commenting from the following SCP Comment -- command and start $ZEXP as a nonpersistent process pair. Comment -- OZEXP / NAME $ZEXP, NOWAIT, PRI 180, OUT $ZHOME, CPU 0/1

comment -- Warm start the spooler subsystem using the SPOOLCOM command comment -- file SPLWARM

OBEY $SYSTEM.STARTUP.SPLWARM

comment -- Start the Transaction Management Facility (TMF) subsystem comment -- using the TMFCOM command file TMFSTART

TMFCOM / IN $SYSTEM.STARTUP.TMFSTART, OUT $ZHOME /

comment -- Configure and start the TCP/IP stacks on the E4SA ports used comment -- by the SWAN

OBEY $SYSTEM.STARTUP.IPSTK*

comment -- Start the CP6100 lines on the SWAN

SCF / IN $SYSTEM.STARTUP.STRTCP6, OUT $ZHOME /

comment -- Start the ATP6100 lines on the SWAN

SCF / IN $SYSTEM.STARTUP.STRTATP, OUT $ZHOME /

comment -- Start the X.25 lines on the SWAN

SCF / IN $SYSTEM.STARTUP.STRTX25, OUT $ZHOME /

comment -- Start the printers on the SWAN

SCF / IN $SYSTEM.STARTUP.STRTLP, OUT $ZHOME /

comment -- Start the Expand-over-IP line to \Case2

SCF / IN $SYSTEM.STARTUP.IP2CASE2, OUT $ZHOME /

comment -- Start the direct-connect line

SCF / IN $SYSTEM.STARTUP.STRTLH, OUT $ZHOME /


Creating Startup and Shutdown Files Spooler Warm-Start File

Spooler Warm-Start File This example command file warm starts the spooler.

After the spooler has been brought up, the printer devices should be in the WAITING state. This file can be invoked automatically from the STRTSYS file, or you can invoke it by using the following TACL command:

> OBEY $SYSTEM.STARTUP.SPLWARM

comment -- This is $SYSTEM.STARTUP.SPLWARMcomment -- This file warm starts the spooler, leaving all jobs intact.

SPOOL / IN $SYSTEM.SPL.SPL, OUT $ZHOME, NAME $SPLS, NOWAIT, PRI 149, & CPU 1/0 SPOOLCOM; SPOOLER, START

comment -- check to see that the spooler started successfully

SPOOLCOM; SPOOLER, STATUS

TMF Warm-Start FileThis example command file warm starts the TMF subsystem.

This file can be invoked automatically from the STRTSYS file, or you can invoke it by using the following TACL command:

> TMFCOM / IN $SYSTEM.STARTUP.TMFSTART, OUT $ZHOME /

-- This is $SYSTEM.STARTUP.TMFSTART-- This file warm starts the Transaction Management Facility (TMF) subsystem-- and checks to see if TMF started successfully.

START TMF;ENABLE DATAVOLS *;STATUS TMF;EXIT

TCP/IP Stack Configuration and Startup FileConfiguration data for NonStop TCP/IP (conventional TCP/IP) processes is not added to the configuration database. Therefore, TCP/IP stacks must be both configured and started for each LAN port that connects to a SWAN concentrator each time you start the system, unless you are using Parallel Library TCP/IP or NonStop TCP/IPv6 over SWAN. (If so, see the manuals that support those TCP/IP subsystems.)

You can create TACL command files to configure TCP/IP stacks on the other ports by assigning the appropriate values the following variables in this example file:

The Parallel Library TCP/IP and the NonStop TCP/IPv6 subsystems participate in the system configuration database (however, not with the initial configuration database that is shipped with a new system). For more information, see:

GWÂDDR LINE^NAME TCP^CPU2HOST^NAME LST^NAME TCP^NAMEIPÂDDR TCP^CPU1 TEL^NAME


Creating Startup and Shutdown Files TCP/IP Stack Configuration and Startup File

• TCP/IP Configuration and Management Manual

• TCP/IP (Parallel Library) Configuration and Management Manual

• TCP/IPv6 Configuration and Management Manual

This example shows a TACL command file that configures the TCP/IP stack on $ZZLAN.L018. ?TACL MACRO

== This file is $SYSTEM.STARTUP.IPSTK1== Adds TCPIP and related processes to $ZZLAN.L018

#FRAME#PUSH CON^NAME, LINE^NAME, TCP^NAME, LST^NAME, TEL^NAME#PUSH HOST^NAME, IPÂDDR, GWÂDDR, TCP^CPU1, TCP^CPU2

#SET IPÂDDR 192.231.36.099#SET GWÂDDR 192.231.36.17

#SET CON^NAME $ZHOME#SET LINE^NAME L018#SET TCP^NAME $ZB018#SET LST^NAME $ZP018#SET TEL^NAME $ZN018#SET HOST^NAME "Case1_L018.DevInc.com"#SET TCP^CPU1 0#SET TCP^CPU2 1

[#IF NOT [#PROCESSEXISTS $ZNET] |THEN| #OUTPUT #OUTPUT Starting SCP... SCP /NAME $ZNET, NOWAIT, CPU 0, PRI 165, TERM [CON^NAME]/ 1; AUTOSTOP -1

]

[#IF [#PROCESSEXISTS [LST^NAME]]

|THEN| STOP [LST^NAME]

]#OUTPUT

#OUTPUT Stopping existing TCP/IP processes...[#IF [#PROCESSEXISTS [TEL^NAME]] |THEN| STOP [TEL^NAME]

]

[#IF [#PROCESSEXISTS [LST^NAME]] |THEN| STOP [LST^NAME]

]

[#IF [#PROCESSEXISTS [TCP^NAME]] |THEN| #PUSH #INLINEPREFIX SET VARIABLE #INLINEPREFIX +


Creating Startup and Shutdown Files TCP/IP Stack Configuration and Startup File

SCF /INLINE, OUT [#MYTERM], NAME/ + ALLOW ALL ERRORS + ABORT PROCESS [TCP^NAME] + EXIT #POP #INLINEPREFIX

]

#OUTPUT

#OUTPUT Starting TCP/IP: [TCP^NAME]TCPIP /NAME [TCP^NAME], TERM [CON^NAME], NOWAIT, CPU [TCP^CPU1] / [TCP^CPU2]DELETE DEFINE =TCPIP^PROCESS^NAMEADD DEFINE =TCPIP^PROCESS^NAME, FILE [TCP^NAME]PARAM TCPIP^PROCESS^NAME [TCP^NAME]PARAM ZTNT^TRANSPORT^PROCESS^NAME [TCP^NAME]

#OUTPUT#OUTPUT Configuring TCP/IP...PUSH #INLINEPREFIXSET VARIABLE #INLINEPREFIX +SCF /INLINE, OUT [#MYTERM], NAME/+ ALLOW ALL ERRORS+ ASSUME PROCESS [TCP^NAME]+ ALTER , HOSTNAME [HOST^NAME]+ ADD SUBNET #SN1, TYPE ETHERNET, IPADDRESS [IPÂDDR], DEVICENAME [LINE^NAME]+ ALTER SUBNET #SN1, SUBNETMASK %%hFFFFFF00+ ALTER SUBNET #LOOP0, IPADDRESS 127.1+ START SUBNET *+ ADD ROUTE #GW, DESTINATION 0, GATEWAY [GWÂDDR], DESTTYPE BROADCAST+ START ROUTE *+ EXITPOP #INLINEPREFIX

#OUTPUT#OUTPUT Starting Listner: [LST^NAME]LISTNER /NAME [LST^NAME], CPU [TCP^CPU1], PRI 160, NOWAIT, TERM [CON^NAME], HIGHPIN OFF/ $SYSTEM.ZTCPIP.PORTCONF

#OUTPUT#OUTPUT Starting Telserv: [TEL^NAME]TELSERV /NAME [TEL^NAME], CPU [TCP^CPU1], PRI 170, NOWAIT, TERM [CON^NAME]/ -backupcpu [TCP^CPU2]


DELETE DEFINE =TCPIP^PROCESS^NAMECLEAR PARAM TCPIP^PROCESS^NAMECLEAR PARAM ZTNT^TRANSPORT^PROCESS^NAME#UNFRAME


Creating Startup and Shutdown Files CP6100 Lines Startup File

CP6100 Lines Startup FileThis example shows an SCF command file that starts the CP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF / IN $SYSTEM.STARTUP.STRTCP6, OUT $ZHOME /

== This is $SYSTEM.STARTUP.STRTCP6

== Starts CP6100 lines associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

START LINE $CP6*

ATP6100 Lines Startup FileThis example shows an SCF command file that starts the ATP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF / IN $SYSTEM.STARTUP.STRTATP, OUT $ZHOME /

== This is $SYSTEM.STARTUP.STRTATP

== Starts ATP6100 lines associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

START LINE $ATP*

X.25 Lines Startup FileThis example shows an SCF command file that starts the X.25 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF / IN $SYSTEM.STARTUP.STRTX25, OUT $ZHOME /

== This is $SYSTEM.STARTUP.STRTX25

== Starts the X.25 lines associated with the SWAN concentrator == $ZZWAN.#S01

ALLOW 20 ERRORS

START LINE $X25*


Creating Startup and Shutdown Files Printer Line Startup File

Printer Line Startup FileThis example shows an SCF command file that starts a printer line associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF / IN $SYSTEM.STARTUP.STRTLP, OUT $ZHOME /

== This is $SYSTEM.STARTUP.STRTLP

== Starts the printer associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

START LINE $LP5516

Expand-Over-IP Line Startup FileThis example shows an SCF command file that starts an Expand-over-IP communications line from $ZZLAN.LAN08, at IP address 192.231.36.094, to \Case2, a NonStop K-series server at IP address 192.231.36.089.


> SCF / IN $SYSTEM.STARTUP.IP2CASE2, OUT $ZHOME /

Note that the IP addresses used in this file are examples only. If you use this example file on your system, you must change these IP addresses to IP addresses that are appropriate for your LAN environment. == This is $SYSTEM.STARTUP.IP2CASE2

ALLOW 100 ERRORS

START LINE $Case2IP

Expand Direct-Connect Line Startup FileThis example shows an SCF command file that starts an Expand direct-connect line on a SWAN concentrator.


> SCF / IN $SYSTEM.STARTUP.STRTLH, OUT $ZHOME /

== This is $SYSTEM.STARTUP.STRTLH

START LINE $Case2elh


Creating Startup and Shutdown Files Tips for Shutdown Files

Tips for Shutdown FilesHP recommends that you specify “N” for the read access portion of the file security attribute (RWEP) for your shutdown files to allow the files to be read by any user on the network. For example, you might secure these files “NCCC.”

The sequence in which you invoke shutdown files can be important. Some processes require other processes to be stopped before they can be stopped. Be sure to indicate the order in which shutdown files are to be run.

Shutdown File ExamplesYou can implement the system shutdown sequence with a collection of shutdown files, each with a specific purpose. HP recommends that you invoke the shutdown files in this order:

1. Shutdown files for the applications

2. Shutdown files for the communications lines

3. Shutdown files for the subsystems

4. Shutdown files for the system software

5. Shutdown file for the system

See the NonStop S-Series Operations Guide for detailed instructions on the shutdown procedure.

Note. Examples and sample programs are for illustration only and might not be suited for your particular purpose. HP does not warrant, guarantee, or make any representations regarding the use or the results of the use of any examples or sample programs in any documentation. You must verify the applicability of any example or sample program before placing the software into production use. For other information about these examples, see Example Command Files on page 13-5.


Creating Startup and Shutdown Files System Shutdown File

System Shutdown FileThis example shows a TACL command file that shuts down the system software and invokes other shutdown files.

The local operator invokes this file by entering the following TACL command:

> OBEY $SYSTEM.SHUTDOWN.STOPSYS

comment -- This is $SYSTEM.SHUTDOWN.STOPSYScomment -- Use this file to shut the system down in an orderly fashion.

comment -- Shut down the CP6100 lines associated with the SWAN concentrator

SCF/ IN $SYSTEM.SHUTDOWN.SDNCP6, OUT $ZHOME /

comment -- Shut down the ATP6100 lines associated with the SWAN concentrator

SCF/ IN $SYSTEM.SHUTDOWN.SDNATP, OUT $ZHOME /

comment -- Shut down the X.25 lines associated with the SWAN concentrator

SCF/ IN $SYSTEM.SHUTDOWN.SDNX25, OUT $ZHOME /

comment -- Shut down the printer lines associated with the SWAN concentrator

SCF/ IN $SYSTEM.SHUTDOWN.SDNLP, OUT $ZHOME /

comment -- Shut down the Expand-over-IP line to \Case2

SCF/ IN $SYSTEM.SHUTDOWN.IP2CASE2, OUT $ZHOME /

comment -- Shut down the Expand manager process, $ZEXP

SCF/ IN $SYSTEM.SHUTDOWN.SDNEXP, OUT $ZHOME /

comment -- Shut down the direct-connect line

SCF/ IN $SYSTEM.SHUTDOWN.STRTLH, OUT $ZHOME /

comment -- Drain the spooler subsystem using the SPOOLCOM command filecomment -- SPLDRAIN.

OBEY $SYSTEM.SHUTDOWN.SPLDRAIN

comment -- Stop the Transaction Management Facility (TMF) subsystem using the comment -- TMFCOM command file TMFSTOP.

TMFCOM / IN $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME /

Note. Shutting down the system in an orderly fashion does not require that you shut down every process. Some processes that have startup files might not need shutdown files.


Creating Startup and Shutdown Files CP6100 Lines Shutdown File

CP6100 Lines Shutdown FileThis example shows an SCF command file that stops the ATP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).

This file can be invoked automatically from the STOPSYS file, or you can invoke it by using the following TACL command:

> SCF/ IN $SYSTEM.SHUTDOWN.SDNCP6, OUT $ZHOME /

== This is $SYSTEM.SHUTDOWN.SDNCP6

== This shuts down the CP6100 lines associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

ABORT LINE $cp6*

ATP6100 Lines Shutdown FileThis example shows an SCF command file that stops the ATP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF/ IN $SYSTEM.SHUTDOWN.SDNATP, OUT $ZHOME /

== This is $SYSTEM.SHUTDOWN.SDNATP

== This shuts down the ATP6100 lines associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

ABORT LINE $ATP*

X.25 Lines Shutdown FileThis example shows an SCF command file that stops the X.25 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF/ IN $SYSTEM.SHUTDOWN.SDNX25, OUT $ZHOME /

== This is $SYSTEM.SHUTDOWN.SDNX25

== This shuts down the X.25 lines associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

ABORT LINE $X25*


Creating Startup and Shutdown Files Printer Line Shutdown File

Printer Line Shutdown FileThis example shows an SCF command file that stops the printer line associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX).


> SCF/ IN $SYSTEM.SHUTDOWN.SDNLP, OUT $ZHOME /

== This is $SYSTEM.SHUTDOWN.SDNLP

== Shuts down the printer associated with the SWAN concentrator== $ZZWAN.#S01

ALLOW 20 ERRORS

ABORT LINE $LP5516

Expand-Over-IP Line Shutdown FileThis example shows an SCF command file that stops the Expand-over-IP communications line from \Case1, a NonStop S7000 server, to \Case2, a NonStop K-series server.


> SCF/ IN $SYSTEM.SHUTDOWN.IP2CASE2, OUT $ZHOME /

== This is $SYSTEM.SHUTDOWN.IP2CASE2

ABORT LINE $Case2IP

Direct-Connect Line Shutdown FileThis example shows an SCF command file that stops the direct-connect line on a SWAN concentrator.


> SCF/ IN $SYSTEM.SHUTDOWN.STOPLH, OUT $ZHOME /

== This is $SYSTEM.SHUTDOWN.STOPLH

== This shuts down the direct-connect line

ALLOW 20 ERRORS

ABORT LINE $Case2elh


Creating Startup and Shutdown Files Spooler Shutdown File

Spooler Shutdown FileThis example shows a TACL command file that drains the spooler.


> OBEY $SYSTEM.SHUTDOWN.SPLDRAIN

To maintain the integrity of the spooler environment, HP recommends that you wait until the spooler has finished draining rather than stop any spooler processes by using the TACL STOP command. comment -- This is $SYSTEM.SHUTDOWN.SPLDRAIN

comment -- This file drains the spooler subsystem leaving all jobs intact.

SPOOLCOM $SPLS; SPOOLER, DRAIN

TMF Shutdown FileThis example shows a TMFCOM command file that stops the Transaction Management Facility (TMF) subsystem.


> TMFCOM / IN $SYSTEM.SHUTDOWN.TMFSTOP, OUT $ZHOME /

To maintain the integrity of the TMF environment, HP recommends that you wait until all transactions have finished rather than stop any TMF processes by using the TACL STOP command. ! comment -- This is $SYSTEM.SHUTDOWN.TMFSTOP

! comment -- This file stops any new transactions from being started, ! comment -- allows any transactions in process to finish, and then ! comment -- stops the TMF subsystem.

DISABLE BEGINTRANS; STOP TMF, WAIT ON; EXIT

Adding Super-Group User IDsAfter you determine that the system is performing correctly, you can add the super-group user IDs for your local operators and your service provider:

1. Add a super-group user ID for the local operator and for your service provider (if you are allowing access to the system for remote support) using the TACL ADDUSER command. Set the passwords and default characteristics for these user IDs. Adding user IDs and setting default characteristics for user IDs is described in the Guardian User’s Guide.

2. Ask the local operator to log on to the system and verify the passwords.


Creating Startup and Shutdown Files Adding Super-Group User IDs


14Case Study: Installing and Configuring a System

This section documents the installation and configuration of a NonStop S7000 system for a fictitious company.

About These Examples 14-2

Background for Developers Inc. 14-3

Hardware Configuration 14-4

Installation Documents 14-4

System Configuration: CONFTEXT File 14-20

LAN Environment at Developers Inc. 14-20

Registry of IP Addresses 14-20

Installing the System 14-22

Customizing the Configuration 14-22

Adding Ethernet 4 ServerNet Adapters (E4SAs) 14-23

Adding ConMgr Process 14-24

Configuring NonStop TCP/IP Stacks on E4SA Ports 14-25

Adding Persistent CLCI TACL, Expand Manager, and SCP Processes 14-27

Starting the $ZEXP Expand Manager Process 14-27

Adding a SWAN Concentrator 14-28

Adding a SWAN 2 Concentrator 14-29

Adding CP6100 Lines 14-29

Adding a 5516 Printer 14-31

Adding an X.25 Line 14-32

Configuring and Starting the $NCP Network Control Process 14-33

Adding an Expand-Over-IP Line 14-33

Adding a Direct-Connect Line 14-34

Note. Examples and sample programs are illustrations only and might not suit your purposes. HP does not warrant, guarantee, or make any representations regarding the use, or the results of the use, of examples or sample programs in any documentation. You must verify the applicability of any example or sample program before placing the software into production use.


Case Study: Installing and Configuring a System About These Examples

About These ExamplesNote the following about the examples in this appendix:

• This case study does not document the factory-installed configuration.

To determine the configuration of your system, see the SCF Configuration File printout that is shipped with your server for a listing of names and locations of configured drives. This file can also be found on the ZSYSCONF subvolume under the name SCF0000. After you have installed and started your system, you can use SCF to determine the configuration of your system. See the SCF Reference Manual for G-Series RVUs for more information about this task.

• The IP addresses used in this appendix are reserved for HP and are only examples.

If you use files described in this appendix on your system, you must change these IP addresses to IP addresses that are appropriate for your LAN environment.

• Names for devices such as tape drives and disks are only examples.

To determine which PMF CRU or IOMF CRU to connect tape drives to on your own system, you need to know the factory-default configuration of your tape drives. The configuration track-ID for the SWAN concentrator used in the example files, X001XX, is also an example. Each SWAN concentrator is uniquely identified by a configuration track-ID, which is printed on the label on the back of the SWAN concentrator. This track-ID, which is case-sensitive, is an important part of the system configuration for the SWAN concentrator. If you use files described in this appendix on your system, you must change the configuration track-ID to the configuration track-ID assigned to your SWAN concentrator.


Case Study: Installing and Configuring a System Background for Developers Inc.

Background for Developers Inc.Developers Inc., a fictitious software development company, plans to add a NonStop S7000 system to their development environment. They already have a NonStop K20000 running the D42.xxsuper-group RVU, and they plan to port applications from the K20000 server to the S7000 server. This conceptual drawing shows what the environment will look like after the NonStop S7000 server is installed.

VST919.vsd

Public LAN

Expand/IP

NonStop K-SeriesServer

System Name: \Case2System Number: 10

SWAN

Dedicated LANfor SWANs

NonStop S-SeriesServer

System Name: \Case1System Number: 5

Remote ServiceProvider (GCSC)

Modem Modem

Dedicated LANfor TSM

BackupSystemConsole


Remote ServiceProvider (GCSC)


Case Study: Installing and Configuring a System Hardware Configuration

Hardware ConfigurationThe hardware configuration for \Case1, the NonStop S7000 system described in this case study, includes:

• Two system enclosures, each containing:

° Two processor multifunction (PMF) CRUs. Each processor has 256 megabytes (MB) of memory.

° Two ServerNet expansion boards (SEBs).

° Two Ethernet 4 ServerNet adapters (E4SAs).

° Sixteen 4-gigabyte (GB) disk drives.

• One 5175 open-reel tape drive attached to the PMF CRU in group 01, module 01, slot 50. This PMF CRU contains processor 0.

• One 5190 or 5194 cartridge tape drive attached to the PMF CRU in group 01, module 01, slot 55. This PMF CRU contains processor 1.

• Primary and backup system consoles attached to a LAN connected to the Ethernet ports on the PMF CRUs in group 01.

• One SWAN concentrator. The configuration track-ID for this concentrator is X001XX.

• Four Ethernet switches.

Installation DocumentsThe following figures contain the installation documents needed for the system described in this case study.

Examples of completed configuration forms and worksheet for the SWAN concentrator are included in the SWAN Concentrator Installation and Support Guide.


Case Study: Installing and Configuring a System Case Study: Installation Document Checklist

Case Study: Installation Document Checklist

VST233.vsd

Installation Document Checklist

System Equipment Inventory Form

Preinstalled I/O Device Cable

Checklist

Floor Plan

Enclosure Arrangement Diagram

System Enclosure Checklist

PMF CRU Configuration Form andPMF 2 CRU Configuration Form

Other forms, notes, or checklists:

Special Notes or Instructions:

Adapter Configuration Form

System Name

/ /Date

IOMF CRU Configuration Form andIOMF 2 CRU Configuration Form

Cross-Row Cabling Worksheet,SEB to SEB

Cross-Row Cabling Worksheet,SEB to IOMF CRU

ServerNet CommunicationPathways Worksheet

ServerNet Cabling Form

x

07

x

x

x

x

x

x

1

1

1

1

2

4

4

22 96\Case1

ofPage 1 1

#PagesForm, Diagram, or Checklist

#PagesForm, Diagram, or Checklist

VST305.vsd


Case Study: Installing and Configuring a System Case Study: System Equipment Inventory Form

Case Study: System Equipment Inventory Form

VST229.vsd

System Equipment Inventory Form

Part or ProductNumber Description

QuantityOrdered

QuantityReceived

System Name

of/ /Date

Page

Processor enclosure, double-high 2

S-series system console 2

\Case107 22 96

1 1

ServerNet cable, 4.5 feet (1.6 meters) 2

7194

S7X-PC

675-004

ServerNet WAN (SWAN) Concentrator 1

7159 Pedestal 1

5194 Tape Drive CRU in module

5175 Tape subsystem with 5170 tape drive

1

1

Ethernet hub 4

Modem V32 BIS (for system console) 2

3880

7159

5196

5175

131369 S-Series SCSI Tape Cable, 25 feet 2

S-series EPO cable 2S7X-EPO

SHUB-110

SMOD-US

5516 Line Printer 15516

VST306.vsd


Case Study: Installing and Configuring a System Case Study: Enclosure Arrangement Diagram

Case Study: Enclosure Arrangement Diagram

VST202.vsd

Enclosure Arrangement Diagram

Building __________________Room __________________Scale: 1/4 inch = 1 foot

Number of Rows

Note which enclosures are base enclosures and which are stacked enclosures.You can indicate a base enclosure by drawing casters on it.

ProcessorEnclosure

Group 02

ProcessorEnclosure

Group 01

System Name/ /Date

System Number(In Expand Network)

\Case107 21 96

10

1

22395

VST316.vsd


Case Study: Installing and Configuring a System Case Study: Floor Plan

Case Study: Floor Plan

POWERRECEPTACLES

Floor Plan System Name/ /DateBuilding Room

Scale: 1/4 inch = 1 footD

esk

(A)

Cha

ir

File

Table

Cabinet

Chair

Cha

irSystemConsole(Primary)

Service

Appearance

SystemEnclosure

Service

Appearance

SystemEnclosure

EthernetSwitches

COMM LINESEXIT

I/O CABLESTO OTHERROOMS EXITHERE

TAPES

PRE-INSTALLEDETHERNE

T

SUPPLIES

Cabinet

Shel

ves

(A)

modem

SystemConsole(Backup)

modem

Group 2

Group 1power

Group 2power

Power forfuturesystemenclosures

7159Pedestal

5190$Tape1

7159Pedestal

5170$Tape0

SWAN

Group 1

EthernetSwitches

EthernetEthernetEthernetEthernetSwitchSwitchSwitchSwitch

EthernetSw

itch

5 2239\Case1

07 22 96

VST226.vsd

VST315.vsd


Case Study: Installing and Configuring a System Case Study: Preinstalled I/O Device Cable Checklist

Case Study: Preinstalled I/O Device Cable Checklist

Preinstalled I/O Device Cable Checklist

Cable ID Tag Floor Plan

System Name

of/ /Date

Page

\Case107 21 96

1 1

10Base-T to Building Ethernet Switch Room 2239 East wall

VST231.vsd

VST314.vsd


Case Study: Installing and Configuring a System Case Study: Group 01 System Enclosure Checklist

Case Study: Group 01 System Enclosure Checklist

VST203.vsd


Shaded areas indicate nonconfigurablecomponents

Service Side:

0301 02 04 05 06 07 08

11 12 14 15 16 17 1813

Appearance Side:

50 55

51 52 53 54

$DA

TA

01-P

$DA

TA

01-M

$DA

TA

02-P

$DA

TA

02-M

$DA

TA

03-P

$DA

TA

03-M

$DA

TA

04-P

$DA

TA

04-M

$DS

MS

CM

-P

$DS

MS

CM

-M

$AU

DIT

-P

$AU

DIT

-M

$DA

TA

00-P

$DA

TA

00-M

$SY

ST

EM

-P

$SY

ST

EM

-M

PMF PMF

Processor 0

Processor 1

SEBSEB

E4S

A

E4S

A

E0153

E0154

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

Date / /07 21 96

Group Number 01System Name \Case1

Module Number 01

VST303.vsd


Case Study: Installing and Configuring a System Case Study: Group 01 Slot 50 PMF CRUConfiguration Form

Case Study: Group 01 Slot 50 PMF CRU Configuration Form

207VST .vsd

Group SlotModule 01

System Name

/ /DatePMF CRU Configuration Form

Shaded areas indicate nonconfigurable components

304VST

POWER ON

SCSI

SERIAL

CONSOLE

ETHERNET

MODEM

AUX

POWER-ON

CABLE

Product Number:

SCF Name:

SCSI Port

Ethernet Port

IP Address:

Adapter Name:

SAC Name:

PIF Name:

LIF Name:

SAC Access List:

SCSI Cable:

AC Power

or

DC Power

\Case1

5001

07 21 96

5794

$TAPE0

PN 131369

Initially 192.231.36.10Get new address from LAN department

$ZZLAN.MIOE0

$ZZLAN.MIOE0.0

0,1

$ZZLAN.MIOE0.0.A

$ZZLAN.LANX

.vsd




VST209.vsd

Group SlotModule 01

System Name/ /DatePMF CRU Configuration Form

Shaded areas indicate nonconfigurablecomponents

\Case1

5501

07 21 96

POWER ON

SCSI

SERIALCONSOLE

ETHERNET

MODEM

AUX

POWER-ONCABLE

Product Number:

SCF Name:

SCSI Port

Ethernet PortIP Address:

Adapter Name:

SAC Name:

PIF Name:

LIF Name:

SAC Access List:

SCSI Cable:

AC Power

DC Power

$TAPE0

$ZZLAN.LANY

$ZZLAN.MIOE1.0

$ZZLAN.MIOE1.0.A

$ZZLAN.MIOE1

1,0

Initially 192.231.36.11Get new address from LAN department

PN 131369

5175

or

VST304.vsd


Case Study: Installing and Configuring a System Case Study: Group 01 Slot 53 E4SA ConfigurationForm

Case Study: Group 01 Slot 53 E4SA Configuration Form

E4SA Configuration Form System Name/ /Date

Group SlotModule 01

SAC 1 ENET 1B:

Adapter Name:

SAC Name: SAC Access List:

PIF Name: LIF Name:

IP Address:

SAC 1 ENET 1A:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 0 ENET 0B:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 0 ENET 0A:

Adapter Name:


PIF Name: LIF Name:

IP Address:

\Case107 21 96

01 53

E0153

E0153.1 (0,1)

E0153.1.B L01B

E0153

E0153.1 (0,1)

E0153.1.A L01A

E0153

E0153.0 (0,1)

E0153.0.B L019

E0153

E4SA0.0 (0,1)

E4SA0.0.A L018

192.231.36.090

192.231.36.091

192.168.2.092

192.168.2.093

SAC 1

ENET 0B

ENET 0A

ENET 1A

ENET 1B

SAC 0

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

VST234.vsd

VST320.vsd





Group SlotModule 01

SAC 1 ENET 1B:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 1 ENET 1A:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 0 ENET 0B:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 0 ENET 0A:

Adapter Name:


PIF Name: LIF Name:

IP Address:

\Case107 21 96

01 54

E0154

E0154.1 (1,0)

E0154.1.B L01F

E0154

E0154.1 (1,0)

E0154.1.A L01E

E0154

E0154.0 (1,0)

E0154.0.B L01D

E0154

E0154.0 (1,0)

E0154.0.A L01C

192.168.2.090

192.168.2.091

192.231.36.092

192.231.36.093

SAC 1

ENET 0B

ENET 0A

ENET 1A

ENET 1B

SAC 0

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

VST235.vsd

VST320.vsd


Case Study: Installing and Configuring a System Case Study: Group 02 System Enclosure Checklist

Case Study: Group 02 System Enclosure Checklist

VST205.vsd


Date / /

Module NumberShaded areas indicate nonconfigurable components

Service Side:

0301 02 04 05 06 07 08

11 12 14 15 16 17 1813

Appearance Side:

50 55

51 52 53 54

01

System NameGroup Number

\Case107 21 96 02

$DA

TA

09-P

$DA

TA

09-M

$DA

TA

10-P

$DA

TA

10-M

$DA

TA

11-P

$DA

TA

11-M

$DA

TA

12-P

$DA

TA

12-M

$DA

TA

06-P

$DA

TA

06-M

$DA

TA

07-P

$DA

TA

07-M

$DA

TA

08-P

$DA

TA

08-M

$DA

TA

05-P

$DA

TA

05-M

PMF PMF

Processor 2

Processor 3

SEBSEB

E4S

A

E4S

A

E0253

E0254

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

4608

VST303.vsd




VST211.vsd

Group SlotModule 01

System Name

/ /DatePMF CRU Configuration Form

Shaded areas indicate nonconfigurable components

.POWER

ON

SCSI

SERIALCONSOLE

ETHERNET

MODEM

AUX

POWER-ONCABLE

Product Number:

SCF Name:

SCSI Port


Adapter Name:

SAC Name:

PIF Name:

LIF Name:

SAC Access List:

SCSI Cable:

AC Power

or

DC Power

\Case1

5002

Available for future use

Port is not available for use.

07 21 96

VST304.vsd




VST213.vsd

Group SlotModule 01

System Name

/ /DatePMF CRU Configuration FormShaded areas indicate nonconfigurable components

POWERON

SCSI

SERIALCONSOLE

ETHERNET

MODEM

AUX

POWER-ONCABLE

Product Number:

SCF Name:

SCSI Port


Adapter Name:

SAC Name:

PIF Name:

LIF Name:

SAC Access List:

SCSI Cable:

AC Power

or

DC Power

\Case1

5502

Available for future use

Port is not available for use.

07 21 96

VST304.vsd





Group SlotModule01

SAC 1 ENET 1B:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 1 ENET 1A:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 0 ENET 0B:

Adapter Name:


PIF Name: LIF Name:

IP Address:

SAC 0 ENET 0A:

Adapter Name:


PIF Name: LIF Name:

IP Address:

\Case107 21 96

02 53

E0253

E4SA2.1 (2,3)

E4SA2.1.B L02B

E0253

E4SA2.0 (2,3)

E4SA2.0.A L028

192.231.36.094

192.168.2.097

SAC 1

ENET 0B

ENET 0A

ENET 1A

ENET 1B

SAC 0

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

E0253

E4SA2.1 (2,3)

E4SA2.1.A L029

192.168.2.096

E0253

E4SA2.0 (2,3)

E4SA2.0.B L02A

192.231.36.096

VST236.vsd

VST320.vsd




VST239.vsd


Group SlotModule

SAC 1 ENET 1A:

Adapter Name:


PIF Name: LIF Name:

SAC 0 ENET 0B:

Adapter Name:


PIF Name: LIF Name:

E0254

E4SA3.1

E4SA3.1.A L029

E0254

E4SA3.0

E4SA3.0.B L02A

SAC 1

ENET 0B

ENET 0A

ENET 1A

ENET 1B

SAC 0

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

RXTX

COLLNK

01

\Case107 21 96

02 54

SAC 1 ENET 1B:

Adapter Name:


PIF Name: LIF Name:

E0254

E4SA3.1

E4SA3.1.B L02B

(2,3)

(2,3)

(2,3)

Adapter Name:


PIF Name: LIF Name:

SAC 0 ENET 0A:

E0254

E4SA3.0

E4SA3.0.A L028

(2,3)

192.168.2.097

192.168.2.096

192.231.36.096

192.231.36.094

IP Address:

IP Address:

IP Address:

IP Address:

VST320.vsd


Case Study: Installing and Configuring a System System Configuration: CONFTEXT File

System Configuration: CONFTEXT FileThis example shows the CONFTEXT file for \Case1. This file is used by DSM/SCM and is stored in the SYSnn subvolume of the $DSMSCM disk. ALLPROCESSORS:

SYSTEM_PROCESSOR_TYPE NSR-W; SYSTEM_VOLUME_SUBVOL $SYSTEM.SYS00; SYSTEM_LIBRARY_CODE_FILES TANDEM^LIBRARY^CODE^FILES; SYSTEM_PROCESS_CODE_FILES TANDEM^PROCESS^CODE^FILES; SYSTEM_PROCESS_LIBRARY_FILES TANDEM^PROCESS^LIBRARY^FILES; STANDARD_MICROCODE TANDEM^STANDARD^MICROCODE; MICROCODE_FILES TANDEM^MICROCODE^FILES; FILES_TO_COPY_TO_NEW_SYSTEM TANDEM^FILES^TO^COPY; FORMATTER_TEMPLATE_FILES TANDEM^FORMATTER^TEMPLATE^FILES; INITIAL_COMMAND_FILE $DSMSCM.SYSnn.CIIN;

LAN Environment at Developers Inc.Developers Inc. has installed a LAN in their building that connects to multiple workstations and printers, as well as to \Case2, the NonStop K-series server at their site. They plan to connect the new NonStop S-series server, \Case1, to this LAN. Developers Inc. also has a staff responsible for managing this nondedicated (public) LAN and keeping track of the IP addresses of the various LANs in the building.

Registry of IP AddressesDevelopers Inc. decided to create a registry of the IP addresses used on their LANs, because they found that problems on their LANs had often been caused by multiple endpoints using the same IP address. The registry allowed them to keep track of the IP addresses already in use.

Note. The IP addresses used in this appendix are examples only. If you use files described in this appendix on your system, you must change these IP addresses to IP addresses that are appropriate for your LAN environment.


Case Study: Installing and Configuring a System Registry of IP Addresses

Registry of IP Addresses for Developers Inc.IP Address Purpose192.231.36.1 System console

192.231.36.2 Ethernet port on PMF 0 (MSP0 TSM access)

192.231.36.3 Ethernet port on PMF 1 (MSP1 TSM access)

192.231.36.10 Ethernet port on PMF 0 (operating system access for TSM)

192.231.36.11 Ethernet port on PMF 1 (operating system access for TSM)

192.231.36.17 Gateway address for $ZZLAN.L018 (ENET 0A in E4SA in (01,01,53))

192.231.36.099 $ZZLAN.L018 (ENET 0A in E4SA in (01,01,53))

192.231.36.100 $ZZLAN.L019 (ENET 0B in E4SA in (01,01,53))

192.168.2.099 $ZZLAN.L01A (ENET 1A in E4SA in (01,01,53))

192.168.2.100 $ZZLAN.L01B (ENET 1B in E4SA in (01,01,53))

192.231.36.089 \Case2 IP address (destination for $zzwan.#Case2IP)

192.168.3.099 $ZZLAN.L01C (ENET 0A in E4SA in (01,01,54))

192.168.3.100 $ZZLAN.L01D (ENET 0B in E4SA in (01,01,54))

192.168.4.099 $ZZLAN.L01E (ENET 1A in E4SA in (01,01,54))

192.168.4.100 $ZZLAN.L01F (ENET 1B in E4SA in (01,01,54))



192.168.6.099 $ZZLAN.L02A (ENET 0B in E4SA in (02,01,53))

192.168.6.100 $ZZLAN.L02B (ENET 1B in E4SA in (02,01,53))

192.168.7.099 $ZZLAN.L02C (ENET 0A in E4SA in (02,01,54))

192.168.7.100 $ZZLAN.L02D (ENET 1A in E4SA in (02,01,54))

192.168.8.099 $ZZLAN.L02E (ENET 0B in E4SA in (02,01,54))

192.168.8.100 $ZZLAN.L02F (ENET 1B in E4SA in (02,01,54))

192.231.36.101 $ZZWAN.#S01 (SWAN, track-ID X001XX), path 1.a

192.168.2.101 $ZZWAN.#S01 (SWAN, track-ID X001XX), path 1.b






Case Study: Installing and Configuring a System Installing the System

Installing the SystemThe installers at Developers Inc. installed the system as it was shipped from the factory. They also changed the system name and number, and changed other parts of the system configuration. The examples in Customizing the Configuration, following, show examples of command files that Developers Inc. can use to build a custom configuration.

Customizing the ConfigurationThe following subsections contain examples of adding various objects to the configuration database. All examples add and start the objects.

These examples assume that the E4SAs and SWAN concentrators were not added at the factory. For your configuration, disks, tapes, ServerNet adapters, and SWAN concentrators and other processes are configured at the factory. For a description of the initial configuration files, see the NonStop S-Series Planning and Configuration Guide.

The startup and shutdown files, used to start and stop this system in an orderly manner, are described in Section 13, Creating Startup and Shutdown Files.

Note. Beginning with the G06.13 RVU, you do not need to add the WANBOOT, SNMPTMUX, TFTPSERV processes. These processes are automatically added and started when the SWAN concentrators are configured at the factory.


Case Study: Installing and Configuring a System Adding Ethernet 4 ServerNet Adapters (E4SAs)

Adding Ethernet 4 ServerNet Adapters (E4SAs)This example contains an SCF command file that adds Ethernet 4 ServerNet adapters (E4SAs) to the configuration database. It also contains a startup file.== This is $SYSTEM.STARTUP.ADDE4SA

== This SCF command file adds the E4SAs to the configuration.

ALLOW 20 ERRORS

ASSUME PROCESS $ZZLAN

== Add the adapter in Group 01, Module 01, Slot 53

ADD ADAPTER E0153, TYPE E4SA, LOCATION (1,1,53), ACCESSLIST (0,1)

== Start the adapter and the SACs and PIFs subordinate to it

START ADAPTER E0153, SUB ALL

== Add the LIFs associated with the PIFs

ADD LIF L018, PIF E0153.0.AADD LIF L019, PIF E0153.0.BADD LIF L01A, PIF E0153.1.AADD LIF L01B, PIF E0153.1.B

== Start the LIFs on the adapter

START LIF L018START LIF L019START LIF L01ASTART LIF L01B






ADD LIF L01C, PIF E0154.0.AADD LIF L01D, PIF E0154.0.BADD LIF L01E, PIF E0154.1.AADD LIF L01F, PIF E0154.1.B


START LIF L01CSTART LIF L01DSTART LIF L01ESTART LIF L01F






Case Study: Installing and Configuring a System Adding ConMgr Process


ADD LIF L028, PIF E0253.0.AADD LIF L029, PIF E0253.0.BADD LIF L02A, PIF E0253.1.AADD LIF L02B, PIF E0253.1.B


START LIF L028START LIF L029START LIF L02ASTART LIF L02B






ADD LIF L02C, PIF E0254.0.AADD LIF L02D, PIF E0254.0.BADD LIF L02E, PIF E0254.1.AADD LIF L02F, PIF E0254.1.B


START LIF L02CSTART LIF L02DSTART LIF L02ESTART LIF L02F

Adding ConMgr ProcessThis example contains a startup file and an SCF command file that adds the concentrator manager to the configuration database. == This is $SYSTEM.STARTUP.ADDMGR

== This file adds the ConMgr process.

ALLOW 20 ERRORS

== Add and start 1 ConMgr for each processor to the database

ADD PROCESS $ZZWAN.#0, IOPOBJECT $SYSTEM.SYS00.CONMGRADD PROCESS $ZZWAN.#1, IOPOBJECT $SYSTEM.SYS00.CONMGRADD PROCESS $ZZWAN.#2, IOPOBJECT $SYSTEM.SYS00.CONMGRADD PROCESS $ZZWAN.#3, IOPOBJECT $SYSTEM.SYS00.CONMGR

START PROCESS $zzwan.#0START PROCESS $zzwan.#1START PROCESS $zzwan.#2START PROCESS $zzwan.#3


Case Study: Installing and Configuring a System Configuring NonStop TCP/IP Stacks on E4SA Ports

Configuring NonStop TCP/IP Stacks on E4SA PortsThis example contains a TACL command file that configures and starts the NonStop TCP/IP stack on $ZZLAN.L018. NonStop TCP/IP stacks must be created for each LAN port that connects to a SWAN concentrator and must be both configured and started each time the system is started. The TACL command files to configure and start TCP/IP stacks on the other ports can be created by changing the following variables to the appropriate values:

?TACL MACRO

== This file is $SYSTEM.STARTUP.IPSTK1== Adds TCPIP and related processes to $ZZLAN.L018

#FRAME#PUSH CON^NAME, LINE^NAME, TCP^NAME, LST^NAME, TEL^NAME#PUSH HOST^NAME, IPÂDDR, GWÂDDR, TCP^CPU1, TCP^CPU2

#SET IPÂDDR 192.231.36.099#SET GWÂDDR 192.231.36.17

#SET CON^NAME $ZHOME#SET LINE^NAME $L018#SET TCP^NAME $ZB018#SET LST^NAME $ZP018#SET TEL^NAME $ZN018#SET HOST^NAME "Case1_L018.DevInc.com"#SET TCP^CPU1 0#SET TCP^CPU2 1

[#IF NOT [#PROCESSEXISTS $ZNET] |THEN| #OUTPUT #OUTPUT Starting SCP... SCP /NAME $ZNET, NOWAIT, CPU 0, PRI 165, TERM [CON^NAME]/ 1; AUTOSTOP -1

]

#OUTPUT#OUTPUT Stopping existing TCP/IP processes...[#IF [#PROCESSEXISTS [TEL^NAME]]

GWÂDDR LINE^NAME TCP^CPU2

HOST^NAME LST^NAME TCP^NAME

IPÂDDR TCP^CPU1 TEL^NAME

Note. If you are using Parallel Library TCP/IP or NonStop TCP/IPv6, you might not need to create a TACL command file because these subsystems participate in the system configuration database. See the TCP/IP (Parallel Library) Configuration and Management Manual or the TCP/IPv6 Configuration and Management Manual.


Case Study: Installing and Configuring a System Configuring NonStop TCP/IP Stacks on E4SA Ports

|THEN| STOP [TEL^NAME]

]

[#IF [#PROCESSEXISTS [LST^NAME]] |THEN| STOP [LST^NAME]

]

[#IF [#PROCESSEXISTS [TCP^NAME]] |THEN| #PUSH #INLINEPREFIX SET VARIABLE #INLINEPREFIX + SCF /INLINE, OUT [#MYTERM], NAME/ + ALLOW ALL ERRORS + ABORT PROCESS [TCP^NAME] + EXIT #POP #INLINEPREFIX

]

#OUTPUT

#OUTPUT Starting TCP/IP: [TCP^NAME]TCPIP /NAME [TCP^NAME], TERM [CON^NAME], NOWAIT, CPU [TCP^CPU1] / [TCP^CPU2]DELETE DEFINE =TCPIP^PROCESS^NAMEADD DEFINE =TCPIP^PROCESS^NAME, FILE [TCP^NAME]PARAM TCPIP^PROCESS^NAME [TCP^NAME]PARAM ZTNT^TRANSPORT^PROCESS^NAME [TCP^NAME]

#OUTPUT#OUTPUT Configuring TCP/IP...PUSH #INLINEPREFIXSET VARIABLE #INLINEPREFIX +SCF /INLINE, OUT [#MYTERM], NAME/+ ALLOW ALL ERRORS+ ASSUME PROCESS [TCP^NAME]+ ALTER , HOSTNAME [HOST^NAME]+ ADD SUBNET #SN1, TYPE ETHERNET, IPADDRESS [IPÂDDR], DEVICENAME [LINE^NAME]+ ALTER SUBNET #SN1, SUBNETMASK %%hFFFFFF00+ ALTER SUBNET #LOOP0, IPADDRESS 127.1+ START SUBNET *+ ADD ROUTE #GW, DESTINATION 0, GATEWAY [GWÂDDR], DESTTYPE BROADCAST+ START ROUTE *+ EXITPOP #INLINEPREFIX

#OUTPUT#OUTPUT Starting Listner: [LST^NAME]LISTNER /NAME [LST^NAME], CPU [TCP^CPU1], PRI 160, NOWAIT, TERM [CON^NAME], HIGHPIN OFF/ $SYSTEM.ZTCPIP.PORTCONF


DELETE DEFINE =TCPIP^PROCESS^NAMECLEAR PARAM TCPIP^PROCESS^NAMECLEAR PARAM ZTNT^TRANSPORT^PROCESS^NAME#UNFRAME


Case Study: Installing and Configuring a System Adding Persistent CLCI TACL, Expand Manager, andSCP Processes

Adding Persistent CLCI TACL, Expand Manager, and SCP Processes

This example shows an SCF command file that adds persistent generic processes for the CLCI TACL, Expand manager, and SCP processes to the configuration database. These processes are started automatically at system load and are restarted automatically if they are stopped abnormally. == This file is GPADD

== Adds the CLCI TACL, Expand manager, and SCP processes as generic== processess.

============================================================================ CLCI TACL ============================================================================ADD PROCESS $ZZKRN.#CLCI-TACL, NAME $CLCI, PRIORITY 199, & AUTORESTART 10, PROGRAM $SYSTEM.SYSTEM.TACL, PRIMARYCPU 0, & BACKUPCPU 1, TYPE OTHER, STARTMODE MANUAL, HOMETERM $YMIOP.#CLCI, & INFILE $YMIOP.#CLCI, OUTFILE $YMIOP.#CLCI, STARTUPMSG "<BCKP-CPU>"============================================================================ Expand manager process ============================================================================ADD PROCESS $ZZKRN.#ZEXP, NAME $ZEXP, PRIORITY 180, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.OZEXP, PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER, & STARTMODE SYSTEM, HOMETERM $ZHOME, OUTFILE $ZHOME, & STARTUPMSG "<BCKP-CPU>"============================================================================ SCP ============================================================================ADD PROCESS $ZZKRN.#SCP, NAME $ZNET, PRIORITY 175, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.SCP, PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER, & STARTMODE SYSTEM, HOMETERM $ZHOME, OUTFILE $ZHOME, & STARTUPMSG "<BCKP-CPU> ; AUTOSTOP -1"

Starting the $ZEXP Expand Manager ProcessThis example contains a TACL command file that starts the Expand manager process, $ZEXP, if the Expand manager processes was not configured as a persistent generic process.

== This is $SYSTEM.STARTUP.STRTEXP

OZEXP/ NAME $zexp,OUT $ZHOME,PRI 180,NOWAIT, CPU 0/1


Case Study: Installing and Configuring a System Adding a SWAN Concentrator

Adding a SWAN ConcentratorThis example contains an SCF command file that adds a SWAN concentrator to the configuration database. The values for TRACKID, hostip, and ALThostip are only examples. This example also contains a startup file.== This is $SYSTEM.STARTUP.ADDSWAN

== This file should be invoked after ADDMGR

ALLOW ALL ERRORS

== Add SWAN concentrator with configuration track-ID X001XX. Use E4SA LIFs== $ZZLAN.L018 and $ZZLAN.L01C

ADD ADAPTER $ZZWAN.#S01, &TRACKID "X001XX", &TCPIP $ZB018, &ALTTCPIP $ZB01C, &hostip 192.231.36.099, &ALThostip 192.168.3.099, &SNMPCODE $system.CSSnn.C7849P00 KERNELCODE $SYST3M.CSSnn.C7953P00 SUBNETMASK 255.255.255.0ALTSUBNETMASK 255.255.255.0

delay 2

ADD SERVER $ZZWAN.#S01.1ADD SERVER $ZZWAN.#S01.2ADD SERVER $ZZWAN.#S01.3

delay 2

ADD PATH $ZZWAN.#S01.1.a,ipaddress 192.231.36.101ADD PATH $ZZWAN.#S01.1.b,ipaddress 192.168.3.101ADD PATH $ZZWAN.#S01.2.a,ipaddress 192.231.36.102ADD PATH $ZZWAN.#S01.2.b,ipaddress 192.168.3.102ADD PATH $ZZWAN.#S01.3.a,ipaddress 192.231.36.103ADD PATH $ZZWAN.#S01.3.b,ipaddress 192.168.3.103

START ADAPTER $ZZWAN.#S01,SUB ALL

Adding a SWAN 2 ConcentratorThe SNMP attribute is optional for both SWAN and SWAN 2 concentrators because the SNMP module is linked with the SWAN NonStop kernel (in G06.07 and later RVUs) and does not have to be downloaded.


Case Study: Installing and Configuring a System Adding CP6100 Lines

Adding CP6100 LinesThis example contains an SCF command file that adds two CP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX) to the configuration database. It also contains a startup file.== This is $SYSTEM.STARTUP.ADDCP6

== This file should be invoked after ADDMGR, STRTMGR,

== ADDSWAN, and STRTSWAN.

ALLOW 20 ERRORS

ADD PROFILE $ZZWAN.#profbsc, FILE $SYSTEM.sys00.PCP6BSC

ADD PROFILE $ZZWAN.#profadcp, FILE $SYSTEM.sys00.PCP6ADCP

ADD DEVICE $ZZWAN.#cp6p1, &CPU 0, &ALTCPU 1, &PROFILE profbsc, &IOPOBJECT $system.sys00.ocp6css, &TYPE (51,1), &RECSIZE 150, &CLIP 1, &LINE 0, &ADAPTER s01, &PATH A

ADD DEVICE $ZZWAN.#cp6p2, &CPU 0, &ALTCPU 1, &PROFILE profadcp, &IOPOBJECT $system.sys00.ocp6css, &TYPE (51,2), &RECSIZE 150, &CLIP 2, &LINE 0, &ADAPTER s01, &PATH A

START DEVICE $ZZWAN.#CP6*

== To enable data communications, you must start the lines using == the command START LINE $CP6* or by invoking a startup file that== contains this command.


Case Study: Installing and Configuring a System Adding an ATP6100 Line

Adding an ATP6100 LineThis example contains an SCF command file that adds an ATP6100 line associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX) to the configuration database. This line can be used to connect an asynchronous terminal that uses the RS-232 interface. It also contains a startup file. == This is $SYSTEM.STARTUP.ADDATP

== This file should be invoked after ADDMGR,

== and ADDSWAN.

== Add and start an ATP6100 device

allow 20 errors

ADD PROFILE $ZZWAN.#prof6530, FILE $SYSTEM.sys00.PATP6530

ADD DEVICE $ZZWAN.#atpp1, &CPU 0, &ALTCPU 1, &PROFILE prof6530, &IOPOBJECT $system.sys00.oatpcss, &TYPE (53,00), &RECSIZE 150, &CLIP 2, &LINE 1, &ADAPTER s01, &PATH A

START DEVICE $ZZWAN.#S01

== To enable data communications, you must start the lines using == the command START LINE $atpp1 or by invoking a startup file that== contains this command.

== To start a process, such as a TACL process, on this line== specify $ATPP1.#TERM.


Case Study: Installing and Configuring a System Adding a 5516 Printer

Adding a 5516 PrinterThis example contains an SCF command file that adds a 5516 printer associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX) to the configuration database. It also contains a startup file.== This is $SYSTEM.STARTUP.ADDLP


== and ADDSWAN.

== Add and start a 5516 printer

ADD PROFILE $ZZWAN.#PRINTER, FILE $SYSTEM.SYS00.PATP5516

ADD DEVICE $ZZWAN.#LP5516, &CPU 0, &ALTCPU 1, &PROFILE printer, &IOPOBJECT $system.sys00.oatpcss, &TYPE (51,0), &RECSIZE 132, &BAUD19200 , &CLIP 1, &LINE 1, &ADAPTER s01, &PATH A

START DEVICE $ZZWAN.#LP5516

== To enable data communications, you must start the lines using == the command START LINE $LP5516 or by invoking a startup file that== contains this command.

== To refer to this printer, such as in a FUP copy command== or when defining it in the spooler, specify $LP5516.#LP.


Case Study: Installing and Configuring a System Adding an X.25 Line

Adding an X.25 LineThis example contains an SCF command file that adds an X.25 line associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX) to the configuration database. It also contains a startup file.== This is $SYSTEM.STARTUP.ADDX25


== and ADDSWAN.

allow 20 errors

ADD PROFILE $ZZWAN.#profx25, FILE $SYSTEM.sys00.PX25DTE

ADD DEVICE $ZZWAN.#x25p1, &CPU 0, &ALTCPU 1, &PROFILE profx25, &IOPOBJECT $system.sys00.x25obj, &TYPE (61,63), &RECSIZE 150, &CLIP 3, &LINE 0, &ADAPTER S01, &PATH A

ADD DEVICE $ZZWAN.#x25s1, &CPU 0, &ALTCPU 1, &PROFILE profx25, &IOPOBJECT $system.sys00.x25obj, &TYPE (61,63), &RECSIZE 150, &CLIP 3, &LINE 1, &ADAPTER S01, &PATH A

== Start the devices configured above.

START DEVICE ($ZZWAN.#x25p1, $ZZWAN.#x25s1)

== To enable data communications, you must start the lines using == the command START LINE $x25* or by invoking a startup file that== contains this command.


Case Study: Installing and Configuring a System Configuring and Starting the $NCP Network ControlProcess

Configuring and Starting the $NCP Network Control ProcessThis example contains an SCF command file that configures and starts the network control process, $NCP.== This is $SYSTEM.STARTUP.ADDNCP

== This file configures and starts $NCP.

== Add NCP profile

ALLOW 100 ERRORS

ADD PROFILE $zzwan.#pexpncp, FILE $SYSTEM.SYS00.PEXPNCP

ADD DEVICE $zzwan.#ncp, PROFILE pexpncp, CPU 0,ALTCPU 1, &

IOPOBJECT $SYSTEM.SYS00.NCPOBJ, TYPE (62,6),RECSIZE 1

DELAY 5

START DEVICE $zzwan.#ncp

Adding an Expand-Over-IP LineThis example contains a startup file, and an SCF command file that configures and starts an Expand-over-IP communications line from $ZZLAN.L028, at IP address 192.168.5.99, to \Case2, a NonStop K-series server at IP address 192.231.36.089. These IP addresses are only examples.== This is $SYSTEM.STARTUP.IP2CASE2

== Add an Expand-over-IP line from $ZZLAN.L028 to \Case2.

ALLOW 100 ERRORSADD PROFILE $zzwan.#pexpsip , FILE $system.sys00.pexpsip

ADD DEVICE $zzwan.#Case2IP, TYPE (63,0) , PROFILE pexpsip , &IOPOBJECT $system.sys00.lhobj , RECSIZE 03 , CPU 0 , ALTCPU 1, &SRCIPADDR 192.168.5.099, DESTIPADDR 192.231.36.089, &SRCIPPORT 5701, DESTIPPORT 5700, NEXTSYS 252, ASSOCIATEDEV $ZTC028

== Start the device configured above.

START DEVICE $zzwan.#Case2IP

== To enable data communications, you must start the lines using == the SCF command START LINE $Case2IP or by invoking a startup file that== contains this command.


Case Study: Installing and Configuring a System Adding a Direct-Connect Line

Adding a Direct-Connect Line This example contains an SCF command file that adds a direct-connect line and a startup file. == This is $SYSTEM.STARTUP.ADDLH

ADD PROFILE $zzwan.#pexpsswn, FILE $system.sys00.pexpsswn

ADD DEVICE $zzwan.#Case2elh, CPU 0, ALTCPU 1, RSIZE 12, & IOPOBJECT $system.sys00.lhobj, TYPE (63,5), PROFILE pexpsswn, & NEXTSYS 252, ADAPTER s01, CLIP 1, LINE 0, PATH A

== Start the device configured above.

START DEVICE $ZZWAN.#Case2elh

== To enable data communications, you must start the lines using == the command START LINE $Case2elh or by invoking a startup file that== contains this command.


A Part NumbersFor all part numbers, see:

• The CSSI Web. For the location of the CSSI Web, see CSSI Web on page xxiii.

• The NonStop S-Series Planning and Configuration Guide.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001A-1

Part Numbers

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001A-2

B ServerNet Cabling This appendix contains ServerNet cabling diagrams and tables for maximum Tetra 8 and Tetra 16 configurations. It also contains diagrams and tables for selected smaller configurations.

Caution. In most instances, whenever I/O enclosures are listed, an IOAM enclosure can be substituted. However, IOAM enclosures must be installed and cabled by service providers trained by HP. Your service provider should refer to the Modular I/O Installation and Configuration Guide which is located in the NTL Hardware Service and Maintenance library.

Topic PageWhat ServerNet Cabling Diagrams Mean B-2

Correlation Between ServerNet Cable Diagram and One Enclosure B-2

Correlation Between ServerNet Cable Diagram and Two Enclosures B-3

Maximum ServerNet Configurations B-4

Maximum Tetra 8 Topologies, X and Y Fabrics B-4

Maximum Tetra 16 Topology, X Fabric B-5

Maximum Tetra 16 Topology, Y Fabric B-6

Maximum ServerNet Cabling Tables B-7

Shaded Areas in These Tables B-7

Tetra 8 Cabling Tables B-8


Maximum ServerNet Cabling Tables B-7

About This Information B-14

Tetra 8 Systems With One Processor Enclosure B-15

Tetra 8 Systems With Two Processor Enclosures B-16

Tetra 8 Systems With Three Processor Enclosures B-17

Tetra 8 Systems With Four Processor Enclosures B-21

Small Tetra 16 Systems B-25

About This Information B-25


Tetra 16 Systems With Six Processor Enclosures B-28

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001B-1

ServerNet Cabling What ServerNet Cabling Diagrams Mean

What ServerNet Cabling Diagrams MeanFigure B-1. Correlation Between ServerNet Cable Diagram and One Enclosure

PMF CRUSlot 55

46123

6 5 4 3 2 1

Group02

5

Port 6Port 6Port 5

Port 4Port 3

Port 2Port 1

PMF CRU Slot 50

SEB Slot 51

SEB Slot 53

SEB Slot 52

SEB Slot 54

VST006.vsd


ServerNet Cabling What ServerNet Cabling Diagrams Mean

Figure B-2. Correlation Between ServerNet Cable Diagram and Two Enclosures

Group25

IOMF50

46123

6 5 4 3 2 1

SEB51

SEB53

PMF50 Group

02

5

Group 02, SEB 53, Port 5

Group 25, Slot 50

VST009.vsd


ServerNet Cabling Maximum ServerNet Configurations

Maximum ServerNet ConfigurationsFigure B-3. Maximum Tetra 8 Topologies, X and Y Fabrics

VST303.vsd

Tetra 8 Topology X Fabric

Tetra 8 Topology Y Fabric

Group02

SEB51

PMF 50

321645

Group01

SEB51

PMF 50

321645

Group22

IOMF

50

Group21

IOMF

50

Group11

IOMF

50

Group12

IOMF

50

Group42

IOMF

50

Group41

IOMF

50

Group04 SEB

51

PMF 50

321645

Group03SEB

51

PMF 50

321645

Group31

IOMF

50

Group32

IOMF

50

Group02

SEB52

PMF 55

321645

Group01

SEB52

PMF 55

321645

Group22

IOMF

55

Group21

IOMF

55

Group11

IOMF

55

Group12

IOMF

55

Group42

IOMF

55

Group41

IOMF

55

Group04 SEB

52

PMF 55

321645

Group03SEB

52

PMF 55

321645

Group31

IOMF

55

Group32

IOMF

55



Figure B-4. Maximum Tetra 16 Topology, X Fabric

VST301.vsd

Group64

IOMF

50

Group63

IOMF

50

Group62

IOMF

50

Group61

IOMF

50

Group06

SEB51

PMF 50

654321

Group05

SEB51

PMF 50

654321

Group51

IOMF

50

Group52

IOMF

50

Group53

IOMF

50

Group54

IOMF

50

Group02

SEB51

PMF 50

1256 4 3321456

SEB53

Group25

IOMF50

Group24

IOMF50

Group23

IOMF50

Group22

IOMF50

Group21

IOMF50

Group15

IOMF 50

Group14

IOMF 50

Group13

IOMF 50

Group12

IOMF 50

Group11

IOMF 50

Group01

SEB51

PMF 50

1 2 5 643321456

Group31

IOMF50

Group32

IOMF50

Group33

IOMF50

Group34

IOMF50

Group35

IOMF50

Group03SEB

51

PMF 50

1256 4 3

SEB53

321456

Group07

654321

SEB51

PMF 50

Group74

IOMF

50

Group73

IOMF

50

Group72

IOMF

50

Group71

IOMF

50

Group08

654321

SEB51

PMF 50

Group81

IOMF

50

Group82

IOMF

50

Group83

IOMF

50

Group84

IOMF

50

Group41

IOMF 50

Group42

IOMF 50

Group43

IOMF 50

Group44

IOMF 50

Group45

IOMF 50

SEB53Group

04 SEB51

PMF 50

1 2 5 643321456

SEB53



Figure B-5. Maximum Tetra 16 Topology, Y Fabric

VST302.vsd

Group64

IOMF

55

Group63

IOMF

55

Group62

IOMF

55

Group61

IOMF

55

Group06

SEB52

PMF 55

654321

Group05

SEB52

PMF 55

654321

Group51

IOMF

55

Group52

IOMF

55

Group53

IOMF

55

Group54

IOMF

55

Group02

SEB52

PMF 55

1256 4 3321456

SEB54

Group15

IOMF

55

Group14

IOMF

55

Group13

IOMF

55

Group12

IOMF

55

Group11

IOMF

55

Group01

SEB52

PMF 55

1 2 5 643321456

Group31

IOMF

55

Group32

IOMF

55

Group33

IOMF

55

Group34

IOMF

55

Group35

IOMF

55

Group03SEB

52

PMF 55

1256 4 3

SEB54

321456

Group07SEB

52

PMF 55

Group08

654321

SEB52

PMF 55

Group81

IOMF

55

Group82

IOMF

55

Group83

IOMF

55

Group84

IOMF

55

Group41

IOMF

55

Group42

IOMF

55

Group43

IOMF

55

Group44

IOMF

55

Group45

IOMF

55

SEB54Group

04 SEB52

PMF 55

1 2 5 643321456

Group74

IOMF

55

Group73

IOMF

55

Group72

IOMF

55

Group71

IOMF

55

654321

Group25

IOMF

55

Group24

IOMF

55

Group23

IOMF

55

Group22

IOMF

55

Group21

IOMF

55

SEB54


ServerNet Cabling Maximum ServerNet Cabling Tables

Maximum ServerNet Cabling Tables

Each table in this section describes the ServerNet cable connections for the specified enclosures in the maximum topology.

Whenever a SEB is identified, an MSEB can also appear.

Shaded Areas in These TablesIn any table, shaded areas indicate the redundant entry for each cable. For example, the cable that connects these groups:

Is the same cable that connects these groups:

A cabling table can list this cable in two categories (From Group 01 and From Group 02), but the second category will be shaded.

Topic PageShaded Areas in These Tables B-7


Maximum Tetra 8 ServerNet Cabling, Processor Enclosures B-8

Maximum Tetra 8 ServerNet Cabling, I/O Enclosures B-9


Maximum Tetra 16 ServerNet Cabling, Processor Enclosures B-10


From ToGroup Slot Port Group Slot Port01 51 1 02 51 1

From ToGroup Slot Port Group Slot Port02 51 1 01 51 1


ServerNet Cabling Tetra 8 Cabling Tables

Tetra 8 Cabling Tables Table PageMaximum Tetra 8 ServerNet Cabling, Processor Enclosures B-8


Table B-1. Maximum Tetra 8 ServerNet Cabling, Processor EnclosuresFrom ToGroup Slot ServerNet Port Group Slot ServerNet Port01 51 1 02 51 1

01 52 1 02 52 1

01 51 2 03 51 2

01 52 2 03 52 2

01 51 3 04 51 3

01 52 3 04 52 3

02 51 1 01 51 1

02 52 1 01 52 1

02 51 2 04 51 2

02 52 2 04 52 2

02 51 3 03 51 3

02 52 3 03 52 3

03 51 1 04 51 1

03 52 1 04 52 1

03 51 2 01 51 2

03 52 2 01 52 2

03 51 3 02 51 3

03 52 3 02 52 3

04 51 1 03 51 1

04 52 1 03 52 1

04 51 2 02 51 2

04 52 2 02 52 2

04 51 3 01 51 3

04 52 3 01 52 3



Table B-2. Maximum Tetra 8 ServerNet Cabling, I/O EnclosuresFrom ToGroup Slot Group Slot ServerNet Port11 50 01 51 5

11 55 01 52 5

12 50 01 51 4

12 55 01 52 4

21 50 02 51 5

21 55 02 52 5

22 50 02 51 4

22 55 02 52 4

31 50 03 51 5

31 55 03 52 5

32 50 03 51 4

32 55 03 52 4

41 50 04 51 5

41 55 04 52 5

42 50 04 51 4

42 55 04 52 4



Tetra 16 Cabling TablesTable PageMaximum Tetra 16 ServerNet Cabling, Processor Enclosures B-10


Table B-3. Maximum Tetra 16 ServerNet Cabling, Processor EnclosuresGroup Slot Port Connects to Group Slot Port (page 1 of 2)

01 51 1 02 51 1

01 52 1 02 52 1

01 51 2 03 51 2

01 52 2 03 52 2

01 51 3 04 51 3

01 52 3 04 52 3

01 51 5 05 51 5

01 52 5 05 52 5

02 51 1 01 51 1

02 52 1 01 52 1

02 51 3 03 51 3

02 52 3 03 52 3

02 51 2 04 51 2

02 52 2 04 52 2

02 51 5 06 51 5

02 52 5 06 52 5

03 51 2 01 51 2

03 52 2 01 52 2

03 51 3 02 51 3

03 52 3 02 52 3

03 51 1 04 51 1

03 52 1 04 52 1

03 51 5 07 51 5

03 52 5 07 52 5

04 51 3 01 51 3

04 52 3 01 52 3

04 51 2 02 51 2

04 52 2 02 52 2

04 51 1 03 51 1



04 52 1 03 52 1

04 51 5 08 51 5

04 52 5 08 52 5

05 51 5 01 51 5

05 52 5 01 52 5

06 51 5 02 51 5

06 52 5 02 52 5

07 51 5 03 51 5

07 52 5 03 52 5

08 51 5 04 51 5

08 52 5 04 52 5

Table B-4. Maximum Tetra 16 ServerNet Cabling, I/O EnclosuresGroup Slot Connects to Group Slot Port (page 1 of 3)

11 55 01 54 1

12 50 01 53 2

12 55 01 54 2

13 50 01 53 3

13 55 01 54 3

14 50 01 53 4

14 55 01 54 4

15 50 01 53 5

15 55 01 54 5

21 50 02 53 1

21 55 02 54 1

22 50 02 53 2

22 55 02 54 2

23 50 02 53 3

23 55 02 54 3

24 50 02 53 4

24 55 02 54 4

25 50 02 53 5

25 55 02 54 5

31 50 03 53 1

Table B-3. Maximum Tetra 16 ServerNet Cabling, Processor EnclosuresGroup Slot Port Connects to Group Slot Port (page 2 of 2)



31 55 03 54 1

32 50 03 53 2

32 55 03 54 2

33 50 03 53 3

33 55 03 54 3

34 50 03 53 4

34 55 03 54 4

35 50 03 53 5

35 55 03 54 5

41 50 04 53 1

41 55 04 54 1

42 50 04 53 2

42 55 04 54 2

43 50 04 53 3

43 55 04 54 3

44 50 04 53 4

44 55 04 54 4

45 50 04 53 5

45 55 04 54 5

51 50 05 51 1

51 55 05 52 1

52 50 05 51 2

52 55 05 52 2

53 50 05 51 3

53 55 05 52 3

54 50 05 51 4

54 55 05 52 4

61 50 06 51 1

61 55 06 52 1

62 50 06 51 2

62 55 06 52 2

63 50 06 51 3

63 55 06 52 3

64 50 06 51 4




64 55 06 52 4

71 50 07 51 1

71 55 07 52 1

72 50 07 51 2

72 55 07 52 2

73 50 07 51 3

73 55 07 52 3

74 50 07 51 4

74 55 07 52 4

81 50 08 51 1

81 55 08 52 1

82 50 08 51 2

82 55 08 52 2

83 50 08 51 3

83 55 08 52 3

84 50 08 51 4

84 55 08 52 4



ServerNet Cabling Small Tetra 8 Systems

Small Tetra 8 SystemsThis subsection provides ServerNet cabling tables and diagrams for selected small Tetra 8 configurations. These configurations range in size up to six processor enclosures and six I/O enclosures.

About This Information• You do not have to conform to one of these enclosure configurations. They are

merely examples. The number of possible enclosure arrangements for all systems is too great to provide tables and diagrams for all.

• Wherever a SEB is identified, an MSEB can also appear.

• Installation requires four types of connections:

Configuration PageAbout This Information B-14

Tetra 8 Systems With One Processor Enclosure B-15

One Processor Enclosure, One I/O Enclosure B-15

One Processor Enclosure, Two I/O Enclosures B-15

Tetra 8 Systems With Two Processor Enclosures B-16

Two Processor Enclosures, One I/O Enclosure B-16

Two Processor Enclosures, Two I/O Enclosures B-16

Tetra 8 Systems With Three Processor Enclosures B-17

Three Processor Enclosures, One I/O Enclosure B-17

Three Processor Enclosures, Two I/O Enclosures B-18

Three Processor Enclosures, Three I/O Enclosures B-18

Three Processor Enclosures, Six I/O Enclosures B-20


Four Processor Enclosures, One I/O Enclosure B-21

Four Processor Enclosures, Two I/O Enclosures B-22

Four Processor Enclosures, Three I/O Enclosures B-22

Four Processor Enclosures, Four I/O Enclosures B-23

Connection Information Appears in ...Groundstraps Section 2, Installing Enclosures

EPO cables Section 2, Installing Enclosures

ServerNet cables This appendix

Power-on cables This appendix


ServerNet Cabling Tetra 8 Systems With One Processor Enclosure

Tetra 8 Systems With One Processor Enclosure

One Processor Enclosure, No I/O EnclosuresSystems consisting of one processor enclosure (two processors) with no I/O enclosures do not require ServerNet cables because the processors communicate through the backplane.

One Processor Enclosure, One I/O Enclosure

One Processor Enclosure, Two I/O Enclosures

Table B-5. Tetra 8 Cabling: One Processor Enclosure, One I/O EnclosureGroup Slot Connects to Group Slot Port11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5

Table B-6. Tetra 8 Cabling: One Processor Enclosure, Two I/O EnclosuresGroup Slot Connects to Group Slot Port11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5

12 (I/O) 50 01 51 ServerNet 4

12 (I/O) 55 01 52 ServerNet 4


ServerNet Cabling Tetra 8 Systems With Two Processor Enclosures

Tetra 8 Systems With Two Processor Enclosures

Two Processor Enclosures, No I/O Enclosures

Two Processor Enclosures, One I/O Enclosure

Two Processor Enclosures, Two I/O Enclosures

Table B-7. Tetra 8 Cabling: Two Processor Enclosures, No I/O EnclosuresGroup Slot Port Connects to Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1

01 52 ServerNet 1 02 52 ServerNet 1

Table B-8. Tetra 8 Cabling: Two Processor Enclosures, One I/O EnclosureGroup Slot Port Connects to Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1


11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5

Table B-9. Tetra 8 Cabling: Two Processor Enclosures, Two I/O EnclosuresGroup Slot Port Connects to Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1


11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5

21 (I/O) 50 02 51 ServerNet 5

21 (I/O) 55 02 52 ServerNet 5


ServerNet Cabling Tetra 8 Systems With Three Processor Enclosures

Tetra 8 Systems With Three Processor Enclosures

Three Processor Enclosures, No I/O Enclosures

Three Processor Enclosures, One I/O Enclosure

Figure B-6. Tetra 8 Cabling: Two Processor Enclosures, Two I/O Enclosures

Table B-10. Tetra 8 Cabling: Three Processor Enclosures, No I/O EnclosuresGroup Slot Port Connects to Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1






Table B-11. Tetra 8 Cabling: Three Processor Enclosures, One I/O EnclosureAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1



VST300.vsd



Three Processor Enclosures, Two I/O Enclosures

Three Processor Enclosures, Three I/O Enclosures


11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5



Table B-12. Tetra 8 Cabling: Three Processor Enclosures, Two I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1




11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5



21 (I/O) 50 02 51 ServerNet 5

21 (I/O) 55 02 52 ServerNet 5

Table B-13. Tetra 8 Cabling: Three Processor Enclosures, Three I/O EnclosuresAttach cable between… And...

Group Slot Port Group SlotSEB or MSEB Port





11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5

Table B-11. Tetra 8 Cabling: Three Processor Enclosures, One I/O EnclosureAttach cable between… And...Group Slot Port Group Slot Port





21 (I/O) 50 02 51 ServerNet 5

21 (I/O) 55 02 52 ServerNet 5

31 (I/O) 50 03 51 ServerNet 5

31 (I/O) 55 03 52 ServerNet 5

Table B-13. Tetra 8 Cabling: Three Processor Enclosures, Three I/O EnclosuresAttach cable between… And...

Group Slot Port Group SlotSEB or MSEB Port



Three Processor Enclosures, Six I/O Enclosures

Figure B-7. Tetra 8 Cabling: Three Processor Enclosures, Six I/O Enclosures

VST800.vsd


ServerNet Cabling Tetra 8 Systems With Four Processor Enclosures

Tetra 8 Systems With Four Processor Enclosures

Four Processor Enclosures, No I/O Enclosures

Four Processor Enclosures, One I/O Enclosure

Table B-14. Tetra 8 Cabling: Four Processor Enclosures, No I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1












Table B-15. Tetra 8 Cabling: Four Processor Enclosures, One I/O EnclosureAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1






11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5






Four Processor Enclosures, Two I/O Enclosures

Four Processor Enclosures, Three I/O Enclosures




Table B-16. Tetra 8 Cabling: Four Processor Enclosures, Two I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1






11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5





21 (I/O) 50 02 51 ServerNet 5

21 (I/O) 55 02 52 ServerNet 5



Table B-17. Tetra 8 Cabling: Four Processor Enclosures, Three I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1



Table B-15. Tetra 8 Cabling: Four Processor Enclosures, One I/O EnclosureAttach cable between… And...Group Slot Port Group Slot Port



Four Processor Enclosures, Four I/O Enclosures




11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5





21 (I/O) 50 02 51 ServerNet 5

21 (I/O) 55 02 52 ServerNet 5



31 (I/O) 50 03 51 ServerNet 5

31 (I/O) 55 03 52 ServerNet 5

Table B-18. Tetra 8 Cabling: Four Processor Enclosures, Four I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port01 51 ServerNet 1 02 51 ServerNet 1






11 (I/O) 50 01 51 ServerNet 5

11 (I/O) 55 01 52 ServerNet 5





21 (I/O) 50 02 51 ServerNet 5

Table B-17. Tetra 8 Cabling: Four Processor Enclosures, Three I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port



21 (I/O) 55 02 52 ServerNet 5



31 (I/O) 50 03 51 ServerNet 5

31 (I/O) 55 03 52 ServerNet 5

41 (I/O) 50 04 51 ServerNet 5

41 (I/O) 55 04 52 ServerNet 5

Table B-18. Tetra 8 Cabling: Four Processor Enclosures, Four I/O EnclosuresAttach cable between… And...Group Slot Port Group Slot Port


ServerNet Cabling Small Tetra 16 Systems

Small Tetra 16 SystemsAbout This Information

• You do not have to conform to one of these enclosure configurations. They are merely examples. The number of possible enclosure arrangements for all systems is too great to provide tables and diagrams for all.

• Wherever a SEB is identified, an MSEB can also appear.

• Installation requires four types of connections. You can find information about these connections as follows:

• The following diagrams illustrate Tetra 16 configurations for all NonStop systems except NonStop S7000, S7xx, and S7x systems. NonStop S7000 systems support Tetra 16 configurations but are limited to two I/O enclosures per processor enclosure.

Connection Information Appears in ...Groundstraps Section 2, Installing Enclosures

EPO cables Section 2, Installing Enclosures

ServerNet cables This appendix

Power-on cables This appendix



Tetra 16 Systems With Four Processor Enclosures

Figure B-8. Tetra 16 Cabling: Four Processor Enclosures, X Fabric

VST740.vsd

Note: This illustrationshows the maximumpossible number of I/Oenclosures. Your serviceprovider can tell you thenumber of I/Oenclosures supported bythe RVU running onyour system.

Group

2150

Group

22

Group

23

Group

24

Group

25

50

50

50

50

546123

6 5 4 3 2 1

Group

02

PMF

50

SEB 53

SEB

51

Group

3550

Group

34

Group

33

Group

32

Group

31

50

50

50

50

546123

6 5 4 3 2 1

Group

03PMF

50

SEB

51

SEB 53

PMF

50

SEB 53

Group

01

654321

50

Group

15

50

Group

14

50

Group

13

50

Group

12

50

Group

11

50

Group

45

50

Group

44

50

Group

43

50

Group

42

50

Group

41

1 2 3 4 5 6

564123

Group

04 PMF

50

SEB 53

SEB

51

123

46

5

SEB

51



Figure B-9. Tetra 16 Cabling: Four Processor Enclosures, Y Fabric

PMF

55

SEB 54

Group

01

654321

55Group

15

55Group

14

55Group

13

55Group

12

55Group

11

55Group

45

55Group

44

55Group

43

55Group

42

55Group

41

1 2 3 4 5 6

564123

Group

04PMF

55

SEB 54

SEB

52

123

46

5

SEB

52

Group

21

55

Group

22

Group

23

Group

24

Group

25

55

55

55

55

546123

6 5 4 3 2 1

Group

02

PMF

55

SEB 54

SEB

52

Group

35

55

Group

34

Group

33

Group

32

Group

31

55

55

55

55

546123

6 5 4 3 2 1

Group

03PMF

55

SEB

52

SEB 54

VST741.vsd



ServerNet Cabling Tetra 16 Systems With Six Processor Enclosures

Tetra 16 Systems With Six Processor Enclosures

Figure B-10. Tetra 16 Cabling: Six Processor Enclosures, X Fabric

VST742.vsd


50

Group

45

50

Group

44

50

Group

43

50

Group

42

50

Group

41

1 2 3 4 5 6

564123

Group

04PMF

50

SEB 53

SEB

51

PMF

50

SEB 53

Group

01

654321

50

Group

15

50

Group

14

50

Group

13

50

Group

12

50

Group

11

123

46

5

SEB

51

PMF

50

SEB 53

SEB

51

Group 05

123465

654321

Group

55 50

50

Group

56

50

Group

57

50

Group

58

50

Group

59

50

Group

51

50

Group

52

50

Group

53

50

Group

54

Group

2150

Group

22

Group

23

Group

24

Group

25

50

50

50

50

546123

6 5 4 3 2 1

Group

02

PMF

50

SEB 53

SEB51

50

Group

64

50

Group

63

50

Group

62

50

Group

61

Group

6550

Group

66

Group

67

Group

68

Group

69

50

50

50

50

Group 06

6 5 4 3 2 1

PMF

50

SEB 53

SEB

51

564321

Group

3550

Group

34

Group

33

Group

32

Group

31

50

50

50

50

546123

6 5 4 3 2 1

Group

03PMF

50

SEB

51

SEB 53



Figure B-11. Tetra 16 Cabling: Six Processor Enclosures, Y Fabric

VST743.vsd

Note: This illustrationshows the maximumpossible number ofI/O enclosures. Yourservice provider cantell you the number ofI/O enclosuressupported by the RVUrunning on yoursystem.

Group

21

55

Group

22

Group

23

Group

24

Group

25

55

55

55

55

546123

6 5 4 3 2 1

Group

02

PMF

55

SEB 54

SEB

52

Group

35

55

Group

34

Group

33

Group

32

Group

31

55

55

55

55

546123

6 5 4 3 2 1

Group

03PMF

55

SEB

52

SEB 54

55Group

45

55Group

44

55Group

43

55Group

42

55Group

41

1 2 3 4 5 6

564123

Group

04PMF

55

SEB 54

SEB

52

PMF

55

SEB 54

Group

01

654321

55Group

15

55Group

14

55Group

13

55Group

12

55Group

11

123

46

5

SEB

52

PMF

55

SEB 54

SEB

52

Group 05

123465

654321

Group

55

55

55Group

56

55Group

57

55Group

58

55Group

59

55

Group

51

55

Group

52

55

Group

53

55

Group

54

55

Group

64

55

Group

63

55

Group

62

55

Group

61

Group

65

55

Group

66

Group

67

Group

68

Group

69

55

55

55

55

Group 06

6 5 4 3 2 1

PMF

55

SEB 54

SEB

52

564321




C Power-On CablingThis section provides power-on cabling diagrams for selected large and smaller ServerNet configurations.

Although the power-on cabling connections are required, the arrangement of your enclosures does not have to conform to these illustrations. For example, you can stack two enclosures or place them side by side.

Figure Title PageFigure C-1 Power-On Cabling: Single-High Stacks C-2

Figure C-2 Power-On Cabling: Mixed Single-High and Double-High Stacks C-3

Figure C-3 Power-On Cabling: Multiple-Row Systems C-4

Figure C-4 Power-On Cable: One Processor Enclosure C-5

Figure C-5 Power-On Cables: One Processor Enclosure, One I/O Enclosure C-5

Figure C-6 Power-On Cables: One Processor Enclosure, Two I/O Enclosures C-5

Figure C-7 Power-On Cables: Two Processor Enclosures, No I/O Enclosures C-6

Figure C-8 Power-On Cables: Two Processor Enclosures, One I/O Enclosure C-6

Figure C-9 Power-On Cables: Two Processor Enclosures, Two I/O Enclosures C-6

Figure C-10 Power-On Cables: Three Processor Enclosures, No I/O Enclosures C-7

Figure C-11 Power-On Cables: Three Processor Enclosures, One I/O Enclosure C-7

Figure C-12 Power-On Cables: Three Processor Enclosures, Two I/O Enclosures

C-7

Figure C-13 Power-On Cables: Three Processor Enclosures, Three I/O Enclosures

C-8

Figure C-14 Power-On Cables: Four Processor Enclosures, No I/O Enclosures C-8

Figure C-15 Power-On Cables: Four Processor Enclosures, One I/O Enclosure C-8

Figure C-16 Power-On Cables: Four Processor Enclosures, Two I/O Enclosures C-8

Figure C-17 Power-On Cables: Four Processor Enclosures, Three I/O Enclosures

C-9

Figure C-18 Power-On Cables: Four Processor Enclosures, Four I/O Enclosures C-9

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001C-1

Power-On Cabling

Figure C-1. Power-On Cabling: Single-High Stacks

VST805.vsd

Moved Cable

Existing Cable

New Cable

Added Enclosure

Existing Enclosure


Power-On Cabling

Figure C-2. Power-On Cabling: Mixed Single-High and Double-High Stacks

VST806.vsd

Moved Cable

Existing Cable

New Cable

Added Enclosure

Existing Enclosure


Power-On Cabling

Figure C-3. Power-On Cabling: Multiple-Row Systems

Diagonal cross-row cabling is possible ifcable length permits.

VST000.vsd


Power-On Cabling

Figure C-4. Power-On Cable: One Processor Enclosure

Figure C-5. Power-On Cables: One Processor Enclosure, One I/O Enclosure

Figure C-6. Power-On Cables: One Processor Enclosure, Two I/O Enclosures

01

VST110.vsd

VST111.vsd

0111

VST119.vsd

01

11

12


Power-On Cabling

Figure C-7. Power-On Cables: Two Processor Enclosures, No I/O Enclosures

Figure C-8. Power-On Cables: Two Processor Enclosures, One I/O Enclosure

Figure C-9. Power-On Cables: Two Processor Enclosures, Two I/O Enclosures

VST120.vsd

01

02

VST121.vsd

01

02

11

VST122.vsd

01

02

11

21


Power-On Cabling

Figure C-10. Power-On Cables: Three Processor Enclosures, No I/O Enclosures

Figure C-11. Power-On Cables: Three Processor Enclosures, One I/O Enclosure

Figure C-12. Power-On Cables: Three Processor Enclosures, Two I/O Enclosures

VST130.vsd

01

03

02

VST131.vsd01

03

02

11

VST132.vsd01

02

11

21

03


Power-On Cabling

Figure C-13. Power-On Cables: Three Processor Enclosures, Three I/O Enclosures

Figure C-14. Power-On Cables: Four Processor Enclosures, No I/O Enclosures

Figure C-15. Power-On Cables: Four Processor Enclosures, One I/O Enclosure

Figure C-16. Power-On Cables: Four Processor Enclosures, Two I/O Enclosures

VST133.vsd01

02

11

21

0331

VST140.vsd

01 03

02 04

VST141.vsd

01 03

02 04

11

VST142.vsd

01 03

02 04

11

21


Power-On Cabling

Figure C-17. Power-On Cables: Four Processor Enclosures, Three I/O Enclosures

Figure C-18. Power-On Cables: Four Processor Enclosures, Four I/O Enclosures

VST142.vsd

01 03

02 04

11

21

31

01

02

03

04

11

21

31

41

VST144.vsd


Power-On Cabling


D TroubleshootingThis appendix explains basic recovery tasks for the system and system console.

Note. For troubleshooting an IOAM enclosure, contact your service provider.


Reference D-2

Power States D-2

Status LEDs D-4

Powering On the System D-5

System Does Not Appear to Be Powered On D-6

Power Is Applied to Enclosure But Fans Are Not Turning D-6

Any Green LED Is Not Lit D-8

Any Amber LED Remains Lit After POST D-9

Yellow ServerNet Port LEDs on SEBs or MSEBs Are Not Lit D-9

Group Service LED on System Enclosure Is Flashing D-9

Correcting Topology Attribute D-9

Starting the System D-10

Startup Event Stream and Startup TACL Windows Do Not Appear D-10

System Load Fails D-11

CIIN File Is Not Invoked During System Startup D-12

Reload Fails D-13

CPU Memory Test Fails D-14

System Load Path Test Fails D-14

Multifunction I/O Board (MFIOB) Test Fails D-15

Dumping Processor Memory D-16

Dumping Processor Memory to Disk Online D-16

Dumping Processor Memory to Tape Offline D-20

Expand-Over-IP Connections D-22

Recovery Actions for the CONNECTING State D-24

Recovery Actions for the WAIT State D-24

Backing Out a Software Revision D-26

1. Start DSM/SCM D-26

2. Start and Log On to Target Interface D-27

3. Initiate Backout Activity D-27

4. Monitor Backout Process D-28

5. Stop All Applications D-28

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001D-1

Troubleshooting Reference

Reference

Power StatesThis table summarizes the NonStop S-series server power-on, power-off, and power-fail/recovery states. For more information about the effects of starting or shutting down the server, see the NonStop S-Series Operations Guide.

6. Rename Software Files Using ZPHIRNM D-29

7. Stop System D-29

8. Load System From Saved Configuration D-30

9. Start Applications D-30

System Consoles D-31

Connectivity Problems D-32

Software Configuration Problems D-36

Software Corruption and Hard-Disk Problems D-37

Restoring Software on the Hard Disk D-38

Configuring a ProCurve 24-Port Ethernet Switch D-48

Topic PagePower States D-2

Status LEDs D-4

Server State External Event Result (page 1 of 2)

The server has been shut down with SCF or the OSM or TSM Low-Level Link. AC power is disconnected from the server.

You reconnect AC power to the server.

Power is applied to the server components.

The components complete their startup sequence.

The server is ready for system start.

The server has been shut down with SCF or the OSM or TSM Low-Level Link. AC power remains connected to the server.

You push the power-on push button on a PMF CRU.

The server components complete their startup sequence.

You start the system with the OSM or TSM Low-Level Link.

The operating system is loaded and started.

The system is ready.

The system is operating normally.

You stop the system with SCF, OSM, or TSM.

Processing halts.

Power is disconnected from the server components.



Troubleshooting Power States

The system is operating normally. The batteries are connected, enabled, and charged.

AC power fails for less than 30 seconds.

The batteries provide power to the server components inside the enclosures.

Processing is uninterrupted.

The default time for power-fail protection is 30 seconds.

AC power fails for more than 30 seconds.

Processing is interrupted.

The batteries provide power to memory, usually for approximately 45 minutes, depending on charge state and the system configuration.

Memory contents are saved until the batteries are drained.

The system is operating normally. The batteries are disconnected, disabled, or not charged.

AC power fails. Processing halts.

Memory content is lost.

Processing cannot be recovered from the point where AC power failed.

AC power fails for more than 30 seconds. The batteries are maintaining the contents of memory.

AC power is restored before the batteries are drained.

Power is applied to the server components.

The system restarts processing at the point where AC power failed.

AC power fails for more than 30 seconds. The batteries are drained.

Memory content is lost.

Processing cannot be recovered from the point where AC power failed.

AC power is restored. Power is applied to the server components.

These components complete their startup sequence.

The system is ready.

Server State External Event Result (page 2 of 2)


Troubleshooting Status LEDs

Status LEDs

Location LED Name Color Function (page 1 of 2)

Disk drive CRU

Power-on Green Lights when the disk drive is receiving power.

Activity Yellow or Amber

Lights when the disk drive is executing a read or write command.

FCSA Power-on Green Lights when the adapter is receiving power.

Service Amber Lights temporarily when first installed and continuously when the adapter is not fully functional.

G4SA Power-on Green Lights when the adapter is receiving power.

Fault Amber Lights temporarily during power-on procedure and continuously when the ServerNet adapter is not fully functional.

IOMF CRU

Power-on Green Lights when the IOMF CRU is receiving power.

Service Amber Lights temporarily during power-on procedure and continuously when the IOMF CRU is not fully functional.

ServerNet port service

Amber Lights when the service processor (SP) detects an error in the transfer of ServerNet data.

In an IOMF 2 CRU, the Prepare to Power Off action in OSM or TSM causes this LED to flash, to help identify the CRU for removal or replacement.

IOAM Fan Power-on Green Flashes temporarily during power-on procedure then continuously when the fan is operating normally.

Fault Amber Lights continuously to indicate that the fan is not operational.

IOAM Power Supply

Power-on Green Flashes temporarily during the power-on procedure then continuously when the power supply is receiving power from the AC power source.

Predictive Fail Amber Flashes continuously when the power supply is about to fail due to a fan problem.

Fail Amber Lights continuously to indicate that the power supply is not operational.

IOAM ServerNet switch board

Power-on Green Lights when the ServerNet switch board is receiving power.

Service Amber Lights temporarily during the power-on procedure and continuously when the ServerNet switch board is not fully functional.


Troubleshooting Powering On the System

Powering On the System

PMF CRU Power-on Green Lights when the PMF CRU is receiving power.

Service Amber Lights temporarily during power-on procedure, and continuously when the PMF CRU is not fully functional.

In a PMF CRU identified in OSM or TSM as a PMF 2 CRU, the Prepare to Power Off action in OSM or TSM causes this LED to flash, to help identify the CRU for removal or replacement.

SEB or MSEB

Power-on Green Lights when the SEB is receiving power.

Fault Amber Lights to indicate that the SEB is not fully functional. At initial power on, this LED lights until the SEB has been successfully configured by the service processor (SP). Then the LED becomes unlit.

Lights continuously to indicate the SEB or MSEB is not operational.

ServerNet port(6/SEB, 12/MSEB)

Yellow Unused.

ServerNet adapter

Power-on Green Lights when the ServerNet adapter is receiving power.

Service Amber Lights temporarily during power-on procedure and continuously when the ServerNet adapter is not fully functional.

System enclosure

Group service (2 per enclosure)

Amber Lights when a command to light the group service LED is issued using OSM or TSM.

Topic PageSystem Does Not Appear to Be Powered On D-6

Power Is Applied to Enclosure But Fans Are Not Turning D-6

Any Green LED Is Not Lit D-8

Any Amber LED Remains Lit After POST D-9

Yellow ServerNet Port LEDs on SEBs or MSEBs Are Not Lit D-9

Group Service LED on System Enclosure Is Flashing D-9

Correcting Topology Attribute D-9

Location LED Name Color Function (page 2 of 2)


Troubleshooting System Does Not Appear to Be Powered On

System Does Not Appear to Be Powered On1. If the fans are not turning and if none of the green LEDs on the system

components in an enclosure are lit, the power might not have been properly applied. Check that the AC power cords and the power-on cables are properly connected and repeat the power-on procedure.

2. If AC power is being supplied to the system but the system still does not appear to be powered on, the system might be running internal power-on self-tests (POSTs). Wait several minutes. It can take as long as 10 minutes for the POSTs to finish.

3. If the system still does not appear to be powered on after this time and you cannot determine the cause of the problem, contact your service provider.

Power Is Applied to Enclosure But Fans Are Not Turning

1. If a green LED is not lit on one or more system enclosures:

a. Ensure that all AC power cords and power-on cables are properly connected.b. Repeat the power-on procedure.

2. If the AC power cords and power-on cables are properly connected and the server still is not powered on:

a. Locate the power-on push button on the PMF CRU.

Caution. If the system is powered on, green LEDs are lit on enclosures, and fans are not turning in one or more enclosures, power off the system immediately to avoid potential hardware damage. Then contact your service provider.


Troubleshooting Power Is Applied to Enclosure But Fans Are NotTurning

b. Press and hold the power-on push button for at least one second.

3. If the system still cannot be powered on, contact your service provider.

01

50

51

52

53

54

55

56

VST580.vsd



Amber Service LED

Green Power-On LED

Power-On Push Button POWER ON


Troubleshooting Any Green LED Is Not Lit

Any Green LED Is Not Lit

1. Make sure the fans are turning. If the fans are not turning and if none of the green LEDs on the system components in an enclosure are lit, the power might not have been properly applied. Check that the power-on cables are properly connected and repeat the power-on procedure.

2. Wait for the POSTs to finish. It can take several minutes after power is applied for the green LEDs on all system components to light.

3. If a green LED still does not light on a system component, it might have failed its POST. Check for other indications that the POST has failed. For example, the following are indications that a POST for a PMF CRU has failed:

4. Unseat and reseat the component.

5. If you cannot determine the cause of the problem, contact your service provider.

6. If necessary, replace the component using the procedures on the CSSI Web. See CSSI Web on page xxiii.

If the component is an IOMF, PMF, SNDA, Power Supply, SEB, or MSEB, see the guided replacement procedures in the OSM Service Connection, or the appropriate guided procedure located in the TSM program group.

To access the OSM guided replacement procedures, see OSM Guided Replacement Procedures on page xxiii.

Note. To troubleshoot any LEDs in an IOAM enclosure, contact your service provider who can refer to the Modular I/O Installation and Configuration Guide located in the NTL Hardware Service and Maintenance library.

Power-On Self-Test Other Indications of FailureFailed Processor Memory Test • Processor halts with a halt code of %100236.

• Hardware error freeze occurs.

Failed System Load Path Test • Processor halts with a halt code of %100237.

Failed MFIOB Test • PMF CRU green power-on and amber service LEDs do not light if the MFIOB is not operational.

• PMF CRU amber service LED lights if the MFIOB is partially operational.


Troubleshooting Any Amber LED Remains Lit After POST

Any Amber LED Remains Lit After POST A fault might have been detected, or the component might not have been correctly initialized and configured:

1. Check that the power-on cables are properly connected.2. Repeat the power-on procedure.3. Unseat and reseat the component.4. If necessary, replace the component using the procedures on the CSSI Web.5. If you cannot determine the cause of the problem, contact your service provider.

Yellow ServerNet Port LEDs on SEBs or MSEBs Are Not LitNo corrective action is necessary. These LEDs are not used.

Group Service LED on System Enclosure Is Flashing Check the group ID switch settings for all enclosures in the system. Settings for the two switches within an enclosure must match, but two different enclosures must not have the same group ID settings. If necessary, change the group ID switch settings using the information about adding a processor enclosure in the NonStop S-Series System Expansion and Reduction Guide.

The group service LED might have been activated manually using the OSM or TSM package. To deactivate the LED:

1. Log on to the OSM Service Connection or TSM Service Application.2. In the Tree pane, right-click the Group for that system enclosure. 3. Select Actions.4. In OSM, select Set Service LED State, click Perform action, and select Off.

In TSM, select Clear Group Service LED and click Perform action.

Correcting Topology AttributeIf the value for the Topology attribute is Tetra 16 or error, use the OSM or TSM Low-Level Link to:

• Reset the Topology attribute: before system discovery, click System Actions. • Power off the system: before system discovery, click System Power Off. • Power on the system.• Ensure that the fans are turning and that the POSTs have finished.

If any system enclosure remains not visible in the Physical view, contact your service provider.

You can reset the Topology attribute and power off the system before or after system discovery. See the OSM or TSM Low-Level Link online help.


Troubleshooting Starting the System

Starting the System

Startup Event Stream and Startup TACL Windows Do Not Appear 1. Log on to the OSM or TSM Low-Level Link.

2. From the File menu, select Start Terminal Emulator > For Startup TACL.

Two OutsideView windows appear, one on top of the other. If the TACL prompt does not appear in one window, view the other with the Windows taskbar buttons.

3. From the File menu, select Start Terminal Emulator > For Event Streams.

Two OutsideView windows appear, one on top of the other. If the TACL prompt does not appear in one window, view the other with the Windows taskbar buttons.

If any of the four startup windows do not appear after the previous steps:

1. Select Start > OutsideView > OutsideView. The OutsideView dialog box appears.

2. From the Session menu, select New. The New Session Properties dialog box appears.

3. On the Session tab, in the Session Caption box, enter a session caption name, such as Startup Events or Startup TACL.

4. Click IO Properties. The TCP/IP Properties dialog box appears.

5. Enter the IP address of MSP 1, a space, and the port number of the window type (303 for the startup event stream window, 301 for the startup TACL window). For example:

192.231.36.2 303 (startup event stream window)192.231.36.3 303 (startup event stream window)192.231.36.2 301 (startup TACL window)192.231.36.3 301 (startup TACL window)

If your workstation is not authorized or is not in the access list in the TSM Low Level Link, you will not receive such a list.

6. Click OK. You are returned to the New Session Properties dialog box.

7. Click OK. The startup event stream window or startup TACL window appears. A TACL prompt appears in the startup TACL window.

With the OSM or TSM Event Viewer, look for important messages that might have been logged to the EMS log during this procedure.

Topic PageStartup Event Stream and Startup TACL Windows Do Not Appear D-10

System Load Fails D-11

CIIN File Is Not Invoked During System Startup D-12

Reload Fails D-13


Troubleshooting System Load Fails

System Load Fails

If a system load is not successful or if the system halts:

1. Check the following locations for halt code or event messages:

• The Processor Status dialog box of the TSM Low-Level Link • The System Status and Detailed Status boxes in the System Startup dialog box• The OSM or TSM Event Viewer • The startup TACL window• The startup event stream window

2. Record any event messages or halt codes. See the appropriate documentation for recovery information.

• If possible, look up event messages in the EMS logs ($0 and $ZLOG). For the cause, effect, and recovery procedures for these events, see the documentation appropriate for your system among the TSM Event Viewer online help, the OSM User’s Guide, and the Operator Messages Manual. (If you configured your processor to print event messages to a printer, you might be able to retrieve messages sent while the system was going down.)

• For the cause and recovery procedures, look up the halt code in the Processor Halt Codes Manual.

3. Perform a processor dump, if needed. See Dumping Processor Memory on page D-16. Do not prime or reset the processor before performing the dump.

4. Correct any problems shown in the dump, or contact your service provider.

5. Load the system again.

You can also try loading the system using one of the following methods:

1. Load the system from an earlier version of the system configuration database by specifying a saved version of the CONFIG file if one is available. You can use this method to recover from a configuration change that caused a problem:

a. Load the system from a system console, specifying a saved version of the system configuration file in the form xx.yy. For example, the CONF0205 file would be specified as 02.05 or 2.5.

b. When the system starts and displays a TACL prompt, log on and start the rest of the system applications.

Caution. Performing a tape load from a system image tape (SIT) to restore the system image files to the $SYSTEM disk (SYSnn and CSSnn subvolumes) is generally not recommended. Perform a tape load only with the advice of the GCSC or your service provider. Loading from a tape reinitializes the disk directory, overlays the disk directory with the directory from the tape, and destroys all files on the disk. Many additional steps are required to restore your system to working order because the SIT does not contain all the files that were on the $SYSTEM disk, including almost all important system configuration information.


Troubleshooting CIIN File Is Not Invoked During System Startup

2. If the current configuration file has become corrupted, and there is no saved configuration file from which you can load the system, use the following procedure to load the system and re-create the initial CONFIG file that was delivered to you when you first received your system:

a. Log on to the OSM or TSM Low-Level Link.

b. Using the System Startup dialog box:

• In the SYSnn field, enter 00 as the number of the SYSnn subvolume containing the version of the operating system to be loaded.

• In the Configuration File box, select Base (CONBASE) as the configuration file.

• The CIIN disabled option must be selected. Click the checkbox.

c. Click Start system.

d. After the system starts and displays a TACL prompt, log on and start SCF with a command that invokes the SCF command file SCF0000. For example:

> SCF / IN $SYSTEM.ZSYSCONF.SCF0000 /

SCF executes the SCF0000 file, makes online configuration changes to the running system, creates an SCFLOG file of the processed commands and returned messages, and records the changes permanently in the CONFIG file.

SCF adds these configuration changes to the CONFBASE file to create the CONFIG file. At this point, the contents of the CONFIG file are the same as those of the CONF0000 file shipped with the system.

e. At the startup TACL prompt, issue the following command for each of the processors to be reloaded:

> reload (nn), prime

3. If you still cannot load the system, contact your service provider.

CIIN File Is Not Invoked During System StartupAfter the first processor is loaded, the initial TACL process invokes the CIIN file automatically only if all the following conditions are true:

• The CONFTEXT configuration file located in the $SYSTEM.SYSnn subvolume has an INITIAL_COMMAND_FILE entry for the CIIN file.

• The CIIN file is available in the specified location.

• The CIIN option is not disabled in the System Startup dialog box.

If the CIIN file is not invoked, issue the following command at the startup TACL prompt for each of the processors to be reloaded:



Troubleshooting Reload Fails

Reload Fails If a reload is not successful:

1. Check the following locations for halt code or event messages:

• The Processor Status dialog box of the OSM or TSM Low-Level Link• The System Startup dialog box (System Status and Detailed Status boxes)• OSM or TSM Event Viewer • The startup TACL window• The startup event stream window

2. Record any event messages or halt codes, and see the appropriate documentation for recovery information:

• Look up event messages in the EMS logs ($0 and $ZLOG). For information about the cause, effect, and recovery for this event, see the documentation appropriate for your system among the TSM Event Viewer online help, the OSM User’s Guide, and the Operator Messages Manual.

• Look up the halt code in the Processor Halt Codes Manual. That manual contains information about the cause and recovery.

3. Contact your service provider. Perform a processor dump, if needed. See Dumping Processor Memory on page D-16. Do not prime or reset the processor before performing the processor dump.

4. Correct the problem, and reload the processor or processors using one of the following methods:

• At the startup TACL prompt, issue the following command for each of the processors to be reloaded:


• If you cannot prime or load a processor, as indicated by messages on the status line of the terminal-emulation window, use the following procedure:

a. Log on to the OSM or TSM Low-Level Link.b. From the toolbar, select Processor Status.c. Select the processors to be reloaded.d. From the Processor Actions menu, scroll to Prime for Reload.e. Click Perform Action.f. Close the Processor Status dialog box.


Troubleshooting CPU Memory Test Fails

CPU Memory Test FailsThe CPU memory test checks the system main memory. If the CPU memory test finishes successfully, the boot millicode starts the system load path test. If the test fails, the service processor (SP) does not light the green power-on LED on the PMF CRU.

Generally, the CPU memory test fails because of a correctable memory error (CME) or a hardware error freeze.

System Load Path Test FailsThe system load path test checks the system load paths. If the system load path test finishes successfully, firmware for the intelligent SCSI processor (ISP) is loaded, the SCSI buses are scanned, the processor is reset, and the boot millicode starts the multifunction I/O board (MFIOB) test.

Signs of a Failed CPU Memory Test Corrective Action

• PMF CRU green power-on LED remains unlit.

• Processor halts with a halt code of %100236.

• Hardware error freeze occurs.

1. Retry the operation.

2. If the test fails a second time, use the OSM or TSM Event Viewer to check the event logs for event messages. The location of a failed memory CRU is stored in an SpEvCruTestComplete event message.

The memory might need to be replaced. Contact your service provider.

Signs of a Failed System Load Path Test Corrective Action

• PMF CRU green power-on LED remains unlit.

• Processor halts with a halt code of %100237.


2. If the test fails a second time, replace the PMF CRU. See:




Troubleshooting Multifunction I/O Board (MFIOB) Test Fails

Multifunction I/O Board (MFIOB) Test FailsThe multifunction I/O board (MFIOB) test checks the MFIOB. If the MFIOB test finishes successfully, the service processor (SP) extinguishes the amber service LED on the PMF CRU or IOMF CRU and generates an event, completing the POST. If the MFIOB test fails, the MFIOB is either partially operational or not operational.

Indications of a Failed MFIOB Test Corrective Action

• PMF CRU or IOMF CRU amber service LED lights if the MFIOB is partially operational.

• PMF CRU or IOMF CRU green power-on and amber service LEDs do not light if the MFIOB is not operational.


2. If the test fails a second time, use the OSM or TSM Event Viewer to check the event logs for the SpEvCruTestComplete event message.

3. Replace the PMF CRU or IOMF CRU. See:




Troubleshooting Dumping Processor Memory

Dumping Processor MemoryYou can dump (copy) the contents of processor memory to disk or tape. Your service provider can then use the memory dump to troubleshoot your system.

• When a system or processor is online, you can dump processor memory to disk.• When a system or processor is offline, you can dump processor memory to tape.

Dumping Processor Memory to Disk OnlineA processor dump to disk occurs online, over either the X or Y fabric of the system:

1. If a disk file called dumpfile does not exist, the RCVDUMP utility creates it.

2. The RCVDUMP utility copies the dump in a compressed format from the processor into dumpfile.

3. As the dump proceeds, the status of the processor being dumped changes in the Processor Status dialog box.

4. When the dump is finished:

• The status of the processor again changes in the Processor Status dialog box.

• RCVDUMP sends a message to the terminal-emulation window from which it was run:

CPU n has been dumped to dumpfile.

Topic PageDumping Processor Memory to Disk Online D-16

Prerequisites D-17

Procedure for Dumping Processor Memory to Disk D-17

Making a Compressed Disk Copy of a Dump File D-19

Dumping Processor Memory to Tape Offline D-20


Troubleshooting Dumping Processor Memory to Disk Online

PrerequisitesBefore you perform a processor dump to disk:

• If dumpfile already exists, it must be empty. Its EOF must be zero. • You must not prime or reset the processor beforehand.• You must have access to:

° A second processor that is running° A connected terminal or workstation with a running command interpreter° A disk with enough space to store the dump

A processor dump requires 256 extents. Each extent should equal slightly more than 1/256 the size of the processor memory. For example, a processor with 256 megabytes of main memory requires 256 extents of at least 512 pages each.

Procedure for Dumping Processor Memory to DiskIf you do not have failure-recovery software installed on your system, perform the following steps to dump processor memory to disk on a running system.

For complete syntax and considerations for the TACL RECEIVEDUMP command and the RCVDUMP utility, and the error and informational messages that they generate, see the Guardian User’s Guide .


2. On the toolbar, click Processor Status.

The Processor Status dialog box appears.

3. Write down the status message displayed in the Processor Status dialog box for the halted processor.

Do this so that you have complete information about the halt when you notify your system manager or service provider after completing these steps.

4. Make sure that the processor you want to dump is halted.

If the processor is not halted (its state is “Executing NonStop OS”), use the Processor Status dialog box to perform a halt action on it:

a. Select the processor you want to dump to disk.b. In the Actions list, select Halt.c. Click Perform action.

5. Log on to a TACL session as the super ID (255,255).

6. Ensure that the disk file dumpfile either does not exist or is empty.

Note. You must be assigned the super ID (255,255) to issue the TACL RECEIVEDUMP command (or run the RCVDUMP utility) to obtain a dump of a halted processor.



• If dumpfile does not exist, RCVDUMP creates it.

• If dumpfile already exists, it must be empty. Its EOF must be zero.

To empty an existing dumpfile:

> FUP PURGEDATA dumpfile

7. Dump the memory of the processor to a disk file in either of two ways:

• Issue the TACL RECEIVEDUMP command, which runs the RCVDUMP utility:

> RECEIVEDUMP / OUT dumpfile / cpu , { 0 | 1 }

• Run the RCVDUMP utility directly.

The syntax of the RCVDUMP command is:

RCVDUMP [ / run-option [ , run-option ] _ / ] dump-file , cpu, { X | Y } [ , param [ , param ] ] ]

param is either:

{ PRIME | NOPRIME }

{ FULL | PARTIAL }

or:

ONLINE (You cannot also specify another param or bus X|Y.)

For example, you could enter:

> RCVDUMP dumpfile , cpu , { X | Y }, FULL

RCVDUMP begins copying the dump in a compressed format from the specified processor cpu, over the specified ServerNet X or Y fabric, into the disk file dumpfile. The processor performing the dump is the one in which the TACL command interpreter is running.

For an explanation of the RCVDUMP messages, see the TACL Reference Manual.

8. Monitor the dump to ensure it finishes successfully.

As the dump proceeds, the status of the processor being dumped should change in the Processor Status dialog box. When the dump is finished, the status of the selected processor changes to indicate the completion of the dump.

In addition, RCVDUMP sends the following message to the terminal from which it was run:

CPU n has been dumped to dumpfile

9. Ensure the dump was successful by checking the size of dumpfile:

> FUP INFO dumpfile

The end-of-file pointer (EOF) should not be zero.



If a message indicates that the dump was not successful, repeat Step 7 over the other ServerNet fabric.

If a halt code appears in the Processor Status dialog box for the selected processor, see the Processor Halt Codes Manual.

10. After the dump finishes successfully, reload the processor by issuing the RELOAD nn, PRIME command at the TACL prompt.

11. Log off of the OSM or TSM Low-Level Link and the TACL session.

Making a Compressed Disk Copy of a Dump File1. At the TACL prompt:

> COPYDUMP { $tape | dumpfile }, destfile

where:

2. When the copy operation is complete, this message appears:

{$tape# | dumpfile} HAS BEEN COPIED (COMPRESSED) TO destfile

$tape name of the tape drive where the tape dump file is located

dumpfile name of the disk dump file specified in the RECEIVEDUMP or RCVDUMP command

destfile name of the destination disk file


Troubleshooting Dumping Processor Memory to Tape Offline

Dumping Processor Memory to Tape OfflineSystems running G-series RVUs support tape dump only on down systems, which means that all processors in the system must be halted.

If you need a processor dump on tape, you must do one of the following:

• Halt all processors and perform a tape dump as described in this subsection. You must stop the system to use this method.

• Dump the processor to disk. See Dumping Processor Memory to Disk Online on page D-16. This method can be used on a running system.

Then use the BACKUP utility to copy the dump from disk to tape. For information about the BACKUP utility, see the Guardian Disk and Tape Utilities Reference Manual.

Procedure For Dumping Processor Memory to Tape1. Mount a tape that is not write-protected (for open-reel tapes, make sure the

write-enable ring is present) on a tape drive. Position the tape at the load point and put the drive online.


3. From the toolbar, click Processor Status.

4. Record the status message for the processor to be dumped so that you have complete information about the halt when you notify your system manager or service provider after completing these steps.

5. Check to see whether any processors are still running (have a state of “Executing NonStop OS”).

6. Halt any running processors. In the Processor Status dialog box:

a. Select the processors to be halted.

b. In the Processor Actions field, scroll to Halt.

c. Click Perform action.

Caution. Performing a tape dump on a running system can result in disk corruption.

Caution. Ensure the tape is at the load point. If a load from tape is attempted but the tape is not at the load point, the operation fails with no indication of the cause of failure.


Troubleshooting Dumping Processor Memory to Tape Offline

7. In the Processor Status dialog box:

a. When all processors are halted, select the processor you want to dump to tape.

b. In the Processor Actions field, scroll to Tape Dump.

c. Click Perform action. The Dump Processor-n to Tape dialog box appears, where n is the processor number of the selected processor.

8. In the Dump Processor-n to Tape dialog box:

a. Specify the location of the PMF CRU to which the tape drive is connected.

Tape drives connected to processor 0 or processor 1 are connect to SCSI controllers on PMF CRUs. Each PMF CRU is associated with a ServerNet fabric (X or Y). For example, you might select the PMF CRU in group 01, module 01, slot 55, ServerNet Y fabric.

b. Specify the small computer system interface (SCSI) ID of the tape drive. The default value is 5, the current software requirement.

c. Click Dump.

9. Monitor the tape dump. Status messages in the Processor Status dialog box indicate the progress of the tape dump.

10. After the dump finishes successfully, start the system using the OSM or TSM Low-Level Link.

11. Log off the OSM or TSM Low-Level Link.

Note. You can dump only to a tape drive that is connected to processor 0 or 1.


Troubleshooting Expand-Over-IP Connections

Expand-Over-IP ConnectionsYou can diagnose most Expand-over-IP problems using information provided by the Expand subsystem SCF STATUS LINE command with the DETAIL option.

This display provides error information in the Detailed State and Detailed Info fields. Table D-1 lists the possible values for the Detailed State field and describes the cause, effect, and recovery action for each state.

Task PageRecovery Actions for the CONNECTING State D-24

Recovery Actions for the WAIT State D-24

Example D-1. SCF STATUS LINE, DETAIL DisplayEXPAND Detailed Status LINE $IPPF2

PPID............... ( 0, 31) BPID................. ( 1, 28)State.............. STARTED Path LDEV............ 39Trace Status....... OFFDetailed State..... CONNECTINGDetailed Info... None

Table D-1. Troubleshooting the Expand Connection Procedure (page 1 of 2)

Detailed State Cause and Effect RecoveryBINDING The Expand-over-IP line-handler process is

binding to the local NonStop TCP/IP process.

This state is normal while the line is coming up.

If this state persists, contact your service provider.

CONNECTING The Expand-over-IP line-handler process has connected to the local NonStop TCP/IP process and is now attempting to connect to the remote Expand-over-IP line-handler process. This state is normal while the connection is being established.

If the line remains in this state:

• The remote Expand-over-IP line-handler process might not be operational.

• There might be a network problem.

Diagnose the problem with the SCF STATS LINE and SCF INFO LINE commands on D-24.


Troubleshooting Expand-Over-IP Connections

PASSIVE If the Expand-over-IP line-handler process is configured to issue passive connect requests, this state indicates that the line-handler process is waiting for the remote Expand-over-IP line-handler process to initiate a connection.

If the Expand-over-IP line-handler process is configured to issue active connect requests, this state indicates that the reconnect limit has been reached and that the line-handler process has been configured to subsequently issue passive connect requests.

This state is normal. No recovery action is required.

QUERY A connection has been established with the remote Expand-over-IP line-handler process, but no data has been received within the inactivity interval. The Expand-over-IP line-handler process is sending Probe messages to the remote Expand-over-IP line-handler process to verify that it is operational.

If the line remains in this state, the remote (destination) Expand-over-IP line-handler process is down or there is a network problem.

SOCKET WAIT The Expand-over-IP line-handler process is waiting for a User Datagram Protocol (UDP) socket to be created.

This state is normal while the line is coming up. If the line remains in this state, an internal error might have occurred.

If the line remains in this state, contact your service provider.

WAIT The Expand-over-IP line-handler process is waiting for another process or subsystem.

The line remains started, but it is not ready for data transfer.

See the Detailed Info field of the SCF STATUS LINE display for more specific error information. Recovering from these types of problems is described further on D-24.

Table D-1. Troubleshooting the Expand Connection Procedure (page 2 of 2)

Detailed State Cause and Effect Recovery


Troubleshooting Recovery Actions for the CONNECTING State

Recovery Actions for the CONNECTING StateIf the SCF STATUS LINE, DETAIL command displays CONNECTING in the Detailed State field, use the SCF STATS LINE command to obtain further information:

• If the line is configured to issue active connect requests, determine whether Connect Command frames (Conn Cmd column) are being sent (Send row).

If the line is configured to issue passive connect requests, determine whether Connect Command frames (Conn Cmd column) are being received (Rcvd row).

If no Connect Command frames are being sent or received, the destination line-handler process might not be operational or there might be a network problem.

• If the Invalid Frames Rcvd counter is greater than 0, frames are being corrupted. Contact your service provider.

• If the Invalid IP Addr Rcvd counter is greater than 0, the internet protocol (IP) address configured for the local or remote Expand-over-IP line-handler process might be invalid. Use the SCF INFO LINE command with the DETAIL option to display the configured IP addresses and associated NonStop TCP/IP process.

Recovery Actions for the WAIT StateIf the SCF STATUS LINE, DETAIL command displays WAIT in the Detailed State field, check the Detailed Info field for more detailed error information:

The Detailed Info field displays the last error message returned to the Expand-over-IP line-handler process. This field provides more information about the current detailed state. Each possible entry in this field corresponds to an Event Management Service (EMS) event generated by the Expand subsystem.

Detailed Info DescriptionIP shared memory system unavailable

The QIO subsystem is not available. Check the QIO subsystem. The line becomes ready when the QIO subsystem becomes available.

IP ownership error The Expand-over-IP line-handler process cannot switch processors. The NonStop TCP/IP process associated with the Expand-over-IP line-handler process is no longer the primary process, but the line-handler process cannot switch processors because other lines in the multiline path are active.

An Expand-over-IP line-handler process and the NonStop TCP/IP process with which it is associated must always reside in the same processor. The Expand-over-IP line-handler process cannot switch processors until all other lines in the path are inactive, meaning that they do not have socket connections.

IP associate TCP process unavailable

The NonStop TCP/IP process associated with the Expand-over-IP line-handler process is not available. Check the NonStop TCP/IP process. The line becomes ready when the associated NonStop TCP/IP process becomes available.


Troubleshooting Recovery Actions for the WAIT State

For cause, effect, and recovery information for the events generated by the Expand subsystem, see the Operator Messages Manual.

Detailed Info Event NumberInternal error nnn, Info %Hxxx, Loc %yyy 8

Shared Memory error nnn, Info %Hxxx, Loc %yyy 9

Unexpected QIO event, Info %Hxxx, Loc %yyy 10

TCP error nnn, Info %Hxxx, Loc %yyy 11

Response error nnn, nnn, Info %Hxxx, Loc %yyy 12

Ownership error 13

Associate TCP process unavailable 14

Shared memory system unavailable 15

Connect retries exhausted 16

Timeout waiting for assoc TCP process, Info %Hxxx, Loc %yyy 17


Troubleshooting Backing Out a Software Revision

Backing Out a Software RevisionIf you encounter problems, you can back out from the current software revision to a previous revision.

For example, if you install an SPR that causes system problems, you can use the following procedure to return to the previous revision. DSM/SCM makes the current revision inaccessible, reapplies the previous revision, and displays instructions for activating the previous revision.

Prerequisites• Skip 7. Stop System and 8. Load System From Saved Configuration if the current

revision did not require SYSGENR or system load.

• When backing out a revision, you do not need to fall back to a previous firmware version if you have not updated the firmware to versions different from that shipped with your NonStop S-series server.

• If you need to back out a revision and DSM/SCM will not run, see the DSM/SCM User’s Guide.

1. Start DSM/SCM1. If the TMF subsystem is not already running, start it at a TACL prompt:

> TMFCOM START TMF

2. If DSM/SCM is not already running, start it:

> VOLUME $DSMSCM.ZDSMSCM> RUN STARTSCM

Task PagePrerequisites D-26

1. Start DSM/SCM D-26

2. Start and Log On to Target Interface D-27

3. Initiate Backout Activity D-27

4. Monitor Backout Process D-28

5. Stop All Applications D-28

6. Rename Software Files Using ZPHIRNM D-29

7. Stop System D-29

8. Load System From Saved Configuration D-30

9. Start Applications D-30


Troubleshooting 2. Start and Log On to Target Interface

2. Start and Log On to Target Interface1. Start the Target Interface at the TACL prompt:

> RUN ZPHITI

The Target Interface Logon Menu appears.

2. Enter your password and press F1. The Target Interface Main Menu appears.

3. Initiate Backout Activity1. Enter 3 (Perform target activities) in the Selection number field, and press F1. The

Target Menu - Select Target Screen appears.

2. On the Target Menu - Select Target Screen, enter the number corresponding to the name of the target system, and press F1.

3. On the Target Menu - Select Action screen, enter 2 (Perform backout to S/W) in the Selection number field, and press F1.

DSM/SCM displays the Backout - Verify Request screen, which contains the following:

• The SYSnn, date, and timestamp of the current software revision and of the previous revision, which becomes the current revision once the Backout request finishes

• The location where DSM/SCM places the snapshot

• A warning that this request makes the last software applied on this target inaccessible

4. Press F1 to submit the backout request. DSM/SCM automatically reapplies the previous software revision to the target system.

While the backout request is processing, DSM/SCM displays the Backout - Processing Backout screen, which gives a description of the request, its processing status, and the location of the previous SYSnn software affected by the request. The screen is updated with current status information approximately every 15 seconds.

5. The Backout - Complete Backout screen with operator instructions appears:

a. Choose a printer to receive the instructions.

b. Press Shift-F16 to exit the Target Interface.


Troubleshooting 4. Monitor Backout Process

4. Monitor Backout Process1. From a system console, go to the task menu bar and select Start > Programs >

Dsmscm > DSMSCM.

2. Log on to the Planner Interface by using the super ID (255,255). DSM/SCM displays the Planner Interface main screen.

3. From the Requests menu, select Request list.

4. The Requests list screen appears, showing the type of activity and current status. Double-click to select the backout activity, which should be at the top of the Requests list.

5. Click Status details.

6. The Request Activity Summary screen appears. Monitor the backout processing activity by watching the timestamp in the upper right-hand corner of the screen. Select Show EMS events to obtain an update at any time.

7. When the backout is complete, exit the Planner Interface.

5. Stop All Applications1. To stop DSM/SCM, enter the following at the TACL prompt:

> VOLUME $DSMSCM.ZDSMSCM> RUN STOPSCM

2. Stop the TMF subsystem:

> TMFCOM STOP TMF

3. Stop all other applications.

Caution. Do not stop DSM/SCM until the backout operation is complete.

Note. In some cases, certain applications or subsystems such as the TMF subsystem might need to be running during ZPHIRNM. Depending on how your system is configured, you also might need to leave the Safeguard application running during ZPHIRNM.


Troubleshooting 6. Rename Software Files Using ZPHIRNM

6. Rename Software Files Using ZPHIRNM1. Enter the following command using the SYSnn for the software configuration you

are backing out to:

> RUN ZPHIRNM $DSMSCM.SYSnn

The following prompt appears:

Do you want to use a log file with this session? (Y/N)

2. Enter Y. The following prompt appears:

You may use any file for logging. If you request to use a disk file that doesn’t exist, it will be created as an entry-sequenced file.

Please enter a filename:

3. Enter a disk file name. The following message appears:

Log file, filename, was successfully created.

ZPHIRNM then renames the applied files. ZPHIRNM issues an EMS event message when it has successfully finished.

ZPHIRNM must run without errors to complete the software activation. If ZPHIRNM notifies you of any errors, correct them and run ZPHIRNM again.

7. Stop System Skip this step if SYSGENR and system load are not required for the revision you are backing out to and were not required the last time you created a new revision.

1. Shut down any user applications that are still running, such as TMF and Safeguard.

2. Drain the spooler.


4. From the Processor Status dialog box:

a. Select every processor displayed.b. From the Actions list, select Halt.c. Click Perform Action. d. A message appears asking if you want to halt the processor. Click OK.


Troubleshooting 8. Load System From Saved Configuration

8. Load System From Saved ConfigurationSkip this step if SYSGENR and system load are not required for the revision you are backing out to, and were not required the last time you created a new revision.

1. From the toolbar of the OSM or TSM Low-Level Link, click Start System.

2. In the System Startup dialog box, enter the necessary information:

a. Enter the SYSnn you are backing out to.

b. Select Saved Version of the system configuration and enter the appropriate value.

3. Click Start system. Two startup event stream windows and two startup TACL windows are displayed.

4. Log off the OSM or TSM Low-Level Link.

You are now back to your previous software configuration.

9. Start ApplicationsYou can now start your applications, including TMF.


Troubleshooting System Consoles

System Consoles

Your new system console is shipped with the Microsoft Windows XP Professional operating system already installed. To migrate an existing system console from Microsoft Windows 2000 Professional operating system to the Microsoft Windows XP Professional operating system, see the NonStop System Console Guide for Migrating to Microsoft Windows XP Professional.

Topic PageConnectivity Problems D-32

Keyboard Is Inoperative D-32

Mouse Is Inoperative D-33

Monitor Screen Is Blank D-34

System Unit Is Inoperative D-35

Software Configuration Problems D-36

Monitor Screen Is Frozen D-36

Software Corruption and Hard-Disk Problems D-37

Application Fails Immediately When Started D-37

Restoring Software on the Hard Disk D-38

Install Operating System and Configure System Console D-39

Configure the System Console D-43

Install Software Provided by HP D-45

Create, Update, and Use an ERD or ASR D-47



Connectivity ProblemsConnectivity refers to the connections, or interfaces, between the devices and components of a system. This subsection contains diagnostic procedures for the following connectivity problems:

Keyboard Is InoperativeAn inoperative keyboard might be the result of software configuration problems. See also Table D-6, Monitor Screen Is Frozen, on page D-36.

Topic PageKeyboard Is Inoperative D-32

Mouse Is Inoperative D-33

Monitor Screen Is Blank D-34

System Unit Is Inoperative D-35

Table D-2. Keyboard Is InoperativeSymptom Recovery Typing on the keyboard has no effect.

1. Ensure that the keyboard cable is securely attached to its connector on the system unit.

2. Disconnect the keyboard cable from the system unit. Examine the cable, connector, and receptacle for damage such as loose pins, bent pins, connector housing cracks, and frayed or broken cable wires and insulation.

3. Verify that all the keys on the keyboard operate with no resistance.

4. Repair or replace any defective items.

5. Reconnect the keyboard cable to the system unit and recheck keyboard operation.



Mouse Is Inoperative

Table D-3. Mouse Is InoperativeSymptom Recovery Moving the mouse or clicking its buttons has no effect.

1. Ensure that you are not experiencing a software configuration problem. Press the Start key or the Windows key. If the Start menu does not appear, a system or software configuration error has occurred. See Monitor Screen Is Frozen on page D-36.

2. Ensure that the mouse cable is securely attached to its connector on the system unit.

3. Disconnect the mouse cable from the system unit. Examine the cable, connector, and receptacle for damage such as loose pins, bent pins, connector housing cracks, and frayed or broken cable wires and insulation.

4. Verify that the ball inside the mouse moves freely in all directions. If the ball does not move freely, dislodge dust or dirt in the ball mechanism by doing one of the following:

Lightly spray the ball and the surrounding area with compressed air from an aerosol can or other source.

Dampen (do not soak) a lint-free cloth with a solution of mild detergent and water, lay it on a flat surface, and move the mouse around on the cloth as you would during normal operation. Allow the mouse to dry.

5. Verify that all the mouse buttons operate with no resistance.


7. Reconnect the mouse cable to the system unit. Recheck mouse operation.



Monitor Screen Is Blank

Table D-4. Monitor Screen Is BlankSymptom Recovery The display monitor screen appears as if it is switched off.

1. Verify that the power switch on the display monitor is in the on position and that the display monitor power indicator light is lit.

2. Verify that power is available from the power source.

3. Ensure that the display monitor power cord is securely connected to the power source.

4. Check that the display monitor interface cable is securely attached to its connector on the system unit.

5. Verify that the brightness and contrast controls are adjusted to produce a proper display, using the vendor documentation as required.

6. Power off the display monitor and system unit.

7. Unplug the display monitor power cord from the power source. Examine the cable, connector, and receptacle for damage such as connector housing cracks, and frayed or broken cable wires and insulation. Reconnect the power cord to the power source.

8. Disconnect the display monitor interface cable from the system unit, and examine the cable, as in the previous step. Reconnect the interface cable.


10. Power on the system unit and display monitor and recheck the display monitor operation.



System Unit Is Inoperative

Table D-5. System Unit Is InoperativeSymptom Recovery None of the indicator lights on the system unit are lit, and the hard-disk drive and cooling fan are not operating.

1. Ensure that the system unit power cord is securely attached to its connector on the system unit and to the power source.

2. Verify that the power switch on the system unit is in the on position.

3. Verify that power is available from the power source.

4. Try restarting the system console by pressing Ctrl-Alt-Del and selecting Restart.

5. If restarting the system console does not work, power off the system console.

6. Disconnect the system unit power cord from the power source. Examine the cable, connector, and receptacle for damage such as connector housing cracks, and frayed or broken cable wires and insulation. Disconnect the power cord from the system unit and repeat this examination.

7. Reconnect the power cord, first to the system unit and then to the power source.

8. Power on the system console and recheck the system unit operation.


Troubleshooting Software Configuration Problems

Software Configuration ProblemsWhen you encounter a software problem, first see the application documentation to ensure that you are using the software properly.

Any change to the software configuration of a system console can affect the function of the programs installed on it, or prevent access to them or to the system console.

The software on the system console hard disk operates this workstation as a system console for NonStop S-series servers. Changing this configuration is not supported. Neither is loading and using software other than that provided with the initial configuration.

Monitor Screen Is FrozenSee also Table D-4 on page D-34.

Table D-6. Monitor Screen Is FrozenSymptom Recovery Typing on the keyboard or using the mouse has no effect on the screen.

1. Press the Esc key, and then try to use the keyboard and mouse. Do the same with the Ctrl-Q key combination, in that order.

2. If the keyboard and mouse still do not work, restart the system console: press Ctrl-Alt-Del and select Shutdown. In the Shutdown screen, select Shutdown and Restart.

3. When the system console has restarted, you should be able to use the keyboard and mouse normally.


Troubleshooting Software Corruption and Hard-Disk Problems

Software Corruption and Hard-Disk ProblemsThe software on the system console might exhibit various symptoms indicating that software has been destructively altered in some way. Software corruption can manifest itself in many ways, from simple data errors and functional quirks to application failures, system failures, and workstation inoperability.

Software corruption and hard-disk problems can seriously affect and even prevent the operation of the system console. Fortunately, almost all of these types of problems can be easily corrected using the tools provided with the system console. Only the most severe conditions, such as hard-disk failures, require outside assistance.

Always start investigating a problem with the simple and easily correctable, such as improper use or connectivity and software configuration problems, before you investigate software corruption and equipment failures.

Application Fails Immediately When Started

If repeated attempts to start the system console are unsuccessful, you might need to reinstall the Microsoft operating system and other software. For information about installing or restoring applications, see Restoring Software on the Hard Disk on page D-38.

Table D-7. Application Fails Immediately When StartedSymptom Recovery Clicking an application icon produces an error message indicating that the application is unavailable or disabled.

1. Record the error message for further reference.

2. Try again to start the application. If the failure occurs again, record the error message accompanying the failure.

3. Press Ctrl-Alt-Del and select Shutdown to restart the system console. In the Shutdown screen, select Shutdown and Restart, and then try again to start the application.

4. You might need to restore configuration information using your ERD or ASR.

5. If this last attempt fails, you might need to restore the application. See Restoring Software on the Hard Disk on page D-38.

6. If restoring the application fails, contact your service provider.


Troubleshooting Restoring Software on the Hard Disk

Restoring Software on the Hard Disk

If one or more applications become unusable or the hard disk becomes corrupted, you must restore the software on the hard disk with the following tools and information:

Try restoring individual applications before reinstalling the XP Professional operating system. See Install Software Provided by HP on page D-45.

Topic PageInstall Operating System and Configure System Console D-39

Configure the System Console D-43

Install Software Provided by HP D-45

Create, Update, and Use an ERD or ASR D-47

Materials Where to FindOn any of the computersERD or ASR If you do not already have an ERD or ASR, see Create

an Emergency Repair Disk (ERD) or Automated System Recovery (ASR) Disk on page 5-10.

Windows OS Product ID number On the Certificate of Authorization for the workstations

HP NonStop Server System Console Installer

Shipped with each system console and included in the system console binder

Caution. Restoring individual applications can erase all information on the hard disk. If possible, back up all applications before restoring software on the hard disk.



Install Operating System and Configure System Console

Install the Operating System Use the HP Restore CD to install the XP Professional operating system on the following computers:

• HP iPAQ Evo D500 Ultra-Slim Desktop • HP Deskpro EN-Series, models 6350, 6500, or 866

Note. This procedure reformats your hard drive.

Table D-8. Install Windows XP Professional Operating System (page 1 of 4)

Action Result1. Insert the HP Restore CD into the

CD-ROM drive. Press Ctrl-Alt-Del. You are prompted to select the language interface.

2. Select English. Press Enter. The HP Restore CD screen appears.

3. Click BEGIN. You are prompted to select the operating system and language.

4. Select XP Professional for operating system and English for language.

A list appears of the options you have chosen to restore the operating system.

5. Click Next. You are asked which drive to format.

6. On the Drive Partitioning Scheme, click the right arrow until the file system is NTFS.

7. Click Next. A message warns you that your hard disk contents will be destroyed.

8. Click Next. A second warning appears.

9. Click Yes. Your hard disk is partitioned. A graph shows the progress. A message appears.

10. Click Reboot. The workstation restarts. Files are copied to the hard disk.

11. After the files are copied to the hard disk, remove the HP Restore CD.

Insert the Windows XP Professional operating system CD. Click Next.

Windows XP (English) files are copied to the hard disk.

A message indicates that your hard drive is formatted and prepared.

You are prompted to click Begin Setup.

12. Click Begin Setup.

Remove the Windows XP Professional Workstation CD.

Click OK.

The workstation restarts several times.

Files are copied to your system.

The Windows XP Professional Setup Wizard appears.

13. Click Next. The software license agreement appears.



14. Click I accept this agreement. Click Next.

The Installing Devices screen appears.

15. In the Regional Settings screen, customize the appearance of numbers, currencies, dates, and keyboard layout. Click Next.

The Name and Organization screen appears.

16. For name, type NonStop S-series System Console. Type the name of your organization. Click Next.

The Date and Time Settings screen appears.

17. Set the date and time.

Check Automatically adjust clock for daylight saving changes. Click Next.

Installing Components screens appear.

Performing Final Tasks screens appear.

18. When setup is complete, click Finish.

Click Restart Now.

The system restarts.

More software is installed.

19. Press Enter. The system automatically converts the file system from FAT to NTFS.

The Desktop appears.

20. Double-click Connect to the Internet. The Internet Connection wizard appears.

21. Select I want to setup my internet connection manually....

The Setup Internet Connection screen appears.

22. Select I connect through a local area network (LAN). Click Next.

The Local Area Network Configuration screen appears.

23. Select Automatic Discovery of proxy server (recommended). Click Next.

The Setup Internet Mail Account appears.

24. Select No. Click Next. The Completing Internet Connection wizard appears.

25. Clear the checkmark.

Click Finish.The Desktop appears.

The Connect to Internet icon disappears.

26. Start > Settings > Control Panel The Control Panel appears.

27. Double-click the System icon. The System Properties screen appears.

28. In the Network Identification tab, start the Network Identification Wizard.

The Network Identification Wizard appears.

29. Click the Network ID button. Click Next.30. Select This computer is part of a

business network. Click Next.The Connecting to the Network screen appears.

31. Select My computer uses a network without a domain. Click Next.

The Workgroup dialog box appears.


Action Result



32. Verify that the Workgroup field contains Workgroup. Click Next. Click Finish.

The Completing Network Configuration screen appears.

33. Click OK to restart the computer.

34. Click Properties.

Type Tandem for computer name.

Click OK twice to restart.

Click Yes to restart.

The Identification Changes Workgroup radio button is selected.

The Network ID Screen appears.

35. Start > Settings > Control Panel The Control Panel appears.

36. Select the Modems tab.

Select Add. Click Next.The Add/Remove Hardware Wizard and Install New Hardware screen appears.

37. Double-click Phone and Modem. The Phone and Modem screen appears.

38. Select Don’t detect new hardware. Click Next.

A list of manufacturers and models appears.

39. Find your modem manufacturer (should be Multitech) and model.

If MT5634ZBA is not in the list, click Have disk.

The Install From Disk screen appears.

40. Enter C:\Multitech or browse to find your driver on the Installer CD.

The Install From Disk screen continues to be displayed

41. Select 56ZBA-V. Select Open. The Install screen appears.

42. Select Install from disk. Click OK. The Install New Modem screen appears.

43. Select Multitech Systems MT5634ZBA. Click Next.

The Select the Port screen appears.

44. Select Selected Ports. Select Com1. Click Next.

The Modem Installation is Finished screen appears.

45. Click Finish. The Phone and Modem screen appears.

46. Click OK. You return to the Control Panel.

47. Double-click the Network and Dialup Connections icon.

The Dialup and Networks Screen appears on the Network Connection Wizard.

48. Click the Make New Connection icon. The Network Connection Type appears.

49. Select Next. Options appear.

50. Select Accept incoming connections. The Devices for Incoming Connection screen appears.

51. Select Multitech MT5634ZBA. Click Next.

The Incoming Virtual Private Connection screen appears.


Action Result



52. Select Do not allow virtual private connections. Click Next.

The Allowed Users screen appears.

53. Select GCSC User. If this selection is not available, call the GCSC. Otherwise, click Next.

The Network Components screen appears.

54. Select Internet Protocol TCP/IP.

Click Properties.

The Incoming TCP/IP Properties screen appears.

55. Under Network Access, select Allow callers to access my local network.

The Incoming TCP/IP Properties screen indicates the selection.

56. If the Specify an IP address check box is not checked, check it.

The Incoming TCP/IP Properties screen indicates the selection.

57. In the IP Address field, type:

Default From value: 192.231.36.77

Default To value: 192.231.36.78

Select Allow calling computer to specify its own address.

Click OK.

The Networking Components Screen appears.

58. Click Next. The Completing the Network Connection Wizard and the default name of the Dialup Connection appear.

59. Incoming Connection is selected. Click Finish.

The Local Area Network Connection Status screen appears.


Double-click Local Area Connection.The Local Area Connection Status screen appears.

61. Click Properties. The TCP/IP Properties screen appears.

62. If the Specify and IP address check box is not checked, check it. All the following values are defaults.

63. In the IP Address field, type 192.231.36.1

64. In the Subnet Mask field, type 255.255.255.0

65. In the Default Gateway field, type 192.231.36.9

66. Click OK twice. The Local Area Communications Status screen appears.

67. Click Close. You have completed the procedure.


Action Result



Configure the System Console

Set Up Date and Time

Table Task PageTable D-9 Set Up Date and Time D-43Table D-10 Set Event Log Settings D-44

Table D-9. Set Up Date and TimeAction Result1. If the date/time properties in the form

of a map of the world are not displayed, select Start > Settings > Control Panel.

The Control Panel appears.

2. Click the Date/Time icon. The Date/Time Properties screen appears.

3. In the Date & Time tab, set day, month, and year.

4. Select your time zone from the menu. Click Date & Time.

5. Click the Time Zone tab and select your time zone from the menu.

Optionally, select Automatically adjust clock for daylight saving changes.Click OK.

The Date/Time Properties screen closes.

6. Still in the control panel, click the Display icon.

The Display Properties screen appears.

7. In the Settings tab, under Desktop Area, move the slide button to the right (toward More). Show 800 X 600 pixels or more.

8. Under Color Palette, select 65536 Colors. Click Test.

Setup displays a message regarding the test pattern and a five-second wait.

9. Click OK to start the test. After the test, you are prompted if you saw the bitmap.

10. Click Yes if the screen is readable. If not, change the desktop setting by repeating Steps 7 through 9.

Click OK.

The Display Properties screen closes.



Set Event Log SettingsThis step is required because OSM or TSM generates many events in normal operation.

Table D-10. Set Event Log Settings Action Result1. Start > Settings > Control Panel The Control Panel opens.

2. Click the Administrative Tools folder. Administrative Tools opens.

3. Click the Event Viewer icon. Event View opens.

4. In the left pane, select Security Log. Security events appear in the right pane.

5. In main menu: Action > Properties. The Properties dialog box opens.

6. In the event log wrap section, click Overwrite Events as needed. Click OK.

If the log file fills, older security events are overwritten.

7. In the left pane, click Application Log. Application events appear in the right pane.

8. In main menu: Action > Properties. Properties dialog box opens.

9. In the event log wrap section, click Overwrite Events as needed. Click OK.

As the log file fills, older application events are overwritten.

10. Close Event Viewer Window. You have completed the procedure.



Install Software Provided by HP If you have problems while installing software, you can restart the console and repeat the installation of the individual software product without reinstalling all the products.

You are now working in a Windows environment. When a procedure requires you to restart the system console, you might need to log on again. Details of logging on are not repeated in these procedures. You might have to enter a user name and password, if configured. Otherwise, you can close the logon screen by clicking OK.

Install Windows XP Professional Service PackYour new system console is shipped with the Microsoft Windows XP Professional operating system already installed. To migrate an existing system console from the Windows 2000 Professional operating system to the Windows XP Professional operating system, see the NonStop System Console Guide for Migrating to Microsoft Windows XP Professional.

Install DSM/SCMYou must download DSM/SCM client software from the SUT. For download and installation instructions, see the G06.nn Software Installation and Upgrade Guide.

Table Topic PageNA Install Windows XP Professional Service Pack D-45

NA Install DSM/SCM D-45

Table D-11 Install Internet Explorer D-46

NA Install the OutsideView Terminal Emulator D-46

NA Install OSM or TSM Client Software D-46

NA For installation instructions, see the NonStop System Console Installer Guide.

D-46

NA Configure the System Console for Remote Access D-47

NA Start the OSM or TSM Low-Level Link and TSM Service Application or OSM Service Connection

D-47

NA Create, Update, and Use an ERD or ASR D-47



Install Internet ExplorerIf necessary, insert the System Console CD-ROM into the CD-ROM drive.

After your computer is restarted, the following items are installed:

• Internet Explorer• Internet Explorer tools• Security• Desktop settings

Install the OutsideView Terminal EmulatorThis copy of the OutsideView terminal emulator is licensed only for the system console and must not be installed on any other workstation.

For installation instructions, see the NonStop System Console Installer Guide.

Install OSM or TSM Client SoftwareFor installation instructions, see the NonStop System Console Installer Guide.

Install Carbon Copy Version 5.7

You must uninstall your existing Carbon Copy version before installing Carbon Copy Version 5.7. For installation instructions (and instructions for removing your existing copy), see the NonStop System Console Installer Guide.

Table D-11. Install Internet ExplorerAction Result1. In the All Folders column, navigate

to the folder D:\IE6.The contents of the Iexplorer folder appear.

2. Open the I386 folder. The contents of the I386 folder appear.

3. Double-click ie6setup.exe. Internet Explorer 6.0 Active Setup wizard appears.

4. Click Next. The License Agreement dialog box appears.

5. Accept the agreement. Click Next. The Installation Open dialog box appears.



Configure the System Console for Remote AccessTo enable access to your system console during unattended periods, configure Carbon Copy to load whenever the system console is restarted. For configuration instructions, see the NonStop System Console Installer Guide, Carbon Copy Help topics (under Carbon Copy’s Help menu) and ReadMe (from the Start>Programs>Altiris Carbon Copy submenu).

Start the OSM or TSM Low-Level Link and TSM Service Application or OSM Service ConnectionSee the following documentation:

• OSM User’s Guide• OSM Low-Level Link online help• The TSM Online User Guide• The TSM Low-Level Link online help• The TSM Service Application online help

Create, Update, and Use an ERD or ASR

The Emergency Repair Disk (ERD) or Automated System Recovery (ASR) disk saves repair information for you to reconstruct Windows system files, system configuration, and startup environment variables.

The OSM or TSM Low-Level Link and the OSM or TSM Notification Director save important configuration information to the Windows registry.

To back up this information, you must create or update an ERD or ASR for your workstation. Update your ERD or ASR any time you use OSM or TSM to change the OSM or TSM environment.

Create or Update an ERD or ASR Use the procedure in the Windows 2000 or XP Professional documentation shipped with your system console.

Restore Configuration Information From an ERD or ASRUse the procedure in the Windows 2000 or XP Professional documentation shipped with your system console.

Topic PageCreate or Update an ERD or ASR D-47

Restore Configuration Information From an ERD or ASR D-47

Note. This guide assumes that you have already created an ERD or ASR as part of the final system console setup steps. See Create an Emergency Repair Disk (ERD) or Automated System Recovery (ASR) Disk on page 5-10.


Troubleshooting Configuring a ProCurve 24-Port Ethernet Switch

Configuring a ProCurve 24-Port Ethernet Switch

If you are using ProCurve 24-port (managed) Ethernet switches for your dedicated OSM/TSM service LAN, you should configure the switch ports that are used for connecting to PMF CRUs—and only those ports—to protect the Services Processors from possible overload. This procedure is not needed and does not apply to ProCurve 8-port (unmanaged) switches.

1. To access the switch’s configuration interface, open an Internet Explorer browser window and enter the IP address of the switch in this form:

http://<ip address>.

2. In the configuration interface, select the Configuration tab, then select Port Configuration.

3. Double-click the port being used for connectivity to the Ethernet port on the PMF CRU.

4. Make sure Port Enabled is set to Yes.

5. Set Mode to 10HDx.

6. In the Broadcast Limit window, enter a value of 1.

7. Click Apply Settings (you may then close the switch configuration interface window).

8. Repeat steps 1 through 7 for all other connections to PMFs on all of the switches.

Caution. These procedures restore Windows registry files. Your existing configuration might be lost. Before using these procedures, try restoring the configuration from tape backups, or access the last known good configuration by holding down the space bar as your computer restarts.

Note. The switch requires a username and password for configuration changes. See documentation shipped with the switch for the default values


E FastPath Tasks: RequiredThis appendix contains all the tasks required to install, start, and configure a two-processor or four-processor NonStop S-series server in the Tetra 8 topology.

If your server contains more than four processors or must be configured in the Tetra 16 topology, do not use this appendix. See the rest of this manual.

If you intend to add this server to a ServerNet cluster, do not do so until the server is fully installed and configured. For more information, see the ServerNet Cluster Manual and the ServerNet Cluster 6780 Planning and Installation Guide.

Task (page 1 of 2) Page (page 1 of 2)

1. Install Hardware E-3

1. Inventory Shipment E-4

2. Collect Tools E-6

3. Unpack and Unload Server E-6

4. Connect Groundstraps E-10

5. Inventory and Inspect All Components E-11

6. Connect the Power-On Cables E-11

7. Connect Emergency Power-Off (EPO) Cables E-13

8. Connect ServerNet Cables E-14

9. Install Service-Side Enclosure Doors If Necessary E-15

10. Install Primary System Console E-16

11. Create Emergency Repair Disk or Automated System Recovery Disk

E-18

12. Install Ethernet Switch E-18

13. Connect Ethernet Switch to Group 01 E-18

14. Connect Primary System Console to Ethernet Switch E-19

15. Install Tape Drive E-19

2. Start the System E-22

1. Prepare for System Startup E-28

2. Power On External System Devices E-23

3. Connect AC Power Cords E-24

4. Apply Power to Server E-26

5. Verify Topology E-27

6. Verify System Components E-28

7. Start System E-28

3. Verify the System E-30

1. Verify Components E-30

2. Verify Critical System Processes E-31

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001E-1

FastPath Tasks: Required

3. Verify Disk Drives E-31

4. Verify Tape Drive E-32

5. Verify Firmware E-32

6. Verify State of the Internal ServerNet Fabric E-32

4. Configure the System E-33

1. Configure Passwords E-34

2. Configure Kernel-Managed Swap Files E-35

3. Configure OSM or TSM Environment E-36

4. Configure System Attributes E-37

5. Configure DSM/SCM E-41


Task (page 2 of 2) Page (page 2 of 2)


FastPath Tasks: Required 1. Install Hardware

1. Install Hardware Task Page1. Inventory Shipment E-4

1a. Inventory the OPEN FIRST Box E-4

1b. Inventory Equipment E-5

2. Collect Tools E-6

3. Unpack and Unload Server E-6

4. Connect Groundstraps E-10

5. Inventory and Inspect All Components E-11

6. Connect the Power-On Cables E-11

7. Connect Emergency Power-Off (EPO) Cables E-13

8. Connect ServerNet Cables E-14

9. Install Service-Side Enclosure Doors If Necessary E-15

10. Install Primary System Console E-16

11. Create Emergency Repair Disk or Automated System Recovery Disk E-18

12. Install Ethernet Switch E-18

13. Connect Ethernet Switch to Group 01 E-18

14. Connect Primary System Console to Ethernet Switch E-19

15. Install Tape Drive E-19


FastPath Tasks: Required 1. Inventory Shipment

1. Inventory Shipment

1a. Inventory the OPEN FIRST Box Depending on your configuration, the box might contain:

Inventory Lists

System Files and Documentation

Tools, Components, and Equipment

Item Description Enables You ToInvoice Information about your order

Inventory equipmentBox Inventory Part numbers, descriptions, quantities

Envelope Description of system as it was ordered Review initial system configuration

Item Description Enables You ToCONFTEXT configuration file list

Attributes that define operating system image for system processors

Review initial system configuration

Plan customized system configuration

SCF configuration file list

Attributes that define system configuration

NTL CD-ROM NonStop Technical Library Read user documentation

Documentation This manual Install, set up, operate system

SWAN Concentrator Installation and Support Guide (if applicable)

Install and configure SWAN concentrator

SWAN 2 Concentrator Installation and Support Guide (if applicable)

Install and configure SWAN 2 concentrator

AWAN 3886 Server Installation and Configuration Guide (if applicable)

Install and configure device

Item Description Enables You ToEnvelope Contains:

• 4-mm hexagonal wrench• Number labels• Flash memory for AWAN• iTP Web Server CD• DAT tape

• Unlock a system enclosure door

• Designate enclosures

Power-on cable Installed between enclosures Power on multiple enclosures

Groundstraps Installed between enclosures Electrically ground enclosures

Ethernet cables Type depends on your location Connect workstation to system

Modem and cable Types depend on your location Allow system to receive dial-ins

Site update tape (SUT) Contain files already installed on your system disk

Store system startup files (not to install or start your system)System image tape (SIT)


FastPath Tasks: Required 1. Inventory Shipment

1b. Inventory Equipment1. Verify that all equipment you ordered has arrived:

• If you have a System Equipment Inventory Form, check off each piece of equipment received.

• If you do not have a System Equipment Inventory Form, compare the Product List or the Box Inventory List to the equipment you have received.

2. Verify that all cables are the length you ordered.

3. Ensure that the other smaller containers contain the following:


Note. Inventory the following equipment in later steps:

• CRUs in enclosures: 5. Inventory and Inspect All Components on page E-11. • System consoles: 10. Install Primary System Console on page E-16.• Tape subsystem SCSI cables: 15. Install Tape Drive on page E-19.

! Item QuantityDetachable AC power cords

Two per enclosure

Groundstraps The number of enclosures minus one; none for one processor enclosure with no I/O enclosures.

ServerNet cables Quantity varies with number of enclosures; none for one processor enclosure with no I/O enclosures. Type varies with plug-in cards (PICs) installed in PMF CRUs and IOMF CRUs.

Cable ties 12 per enclosure

EPO cables One per enclosure

Power-on cables One per enclosure

Emergency Power-Off (EPO) Cable

AC Power Cord

Power-On Cable

ServerNet ECL Cable

Groundstrap

Cable Tie

VST977.vsd


FastPath Tasks: Required 2. Collect Tools

2. Collect Tools

3. Unpack and Unload Server

1. Move each shipping pallet as close as possible to the installation area.

2. If necessary, allow components to warm to room temperature before installation. This practice reduces condensation that can damage electronic and moving parts.

3. At the installation site, remove all packaging from each enclosure stack.

Object Tools for Installation PurposeSystem enclosure

ESD protection kit Protect components against electrostatic discharge

Heavy-freight-handling equipment Move shipping pallet to installation site

Safety glasses Protect eyes

Scissors or cutters Cut banding straps

Open-end wrench: 3/4 inch (19 mm) or 9/16 inch (15 mm)

Lower enclosure legs

4 mm diagonal wrench (provided) Unlock system enclosure door

Phillips screwdriver Fasten groundstraps

Stubby Phillips screwdriver Secure AC power cords if present

Labels and pens or pencils Label cables

Tape subsystem

Open-end wrench: 15/16 inch (24 mm) or adjustable

Lower legs on subsystem enclosure

Small slotted screwdriver Remove shipping restraints if present

Note. One unloading ramp is provided regardless of the number of enclosures shipped.

Figure E-1. Packaging of Enclosure Stack

Cardboard CapCardboard Panel

Antistatic Bag

Cardboard Panel

Plastic Locking Clips

vst987.vsd

Unloading Ramp


FastPath Tasks: Required 3. Unpack and Unload Server

4. Prepare to roll the enclosure stack off the pallet:

a. Flip open the twist-lock handles on the pallet end piece. To loosen the end piece, turn the twist-lock handles counterclockwise as far as they can go:

b. Remove the end piece and set it aside:

System Enclosure(Side View)

Twist-Lock Handles

End Piece

VST951.vsd

System Enclosure on Pallet

End Piece

VST706.vsd



c. Position the unloading ramp against the pallet on the same side as the end piece.

d. Position the Velcro strips. Ensure the Velcro strips hold the ramp firmly against the pallet:

e. To prevent snagging hazards, raise the leveling pads on the base enclosure fully before you move the enclosure stack.

Figure E-2. Velcro Strips on Loading Pallet

WARNING. Before moving an enclosure stack:

• Always get at least one other person to help you move an enclosure stack. If the floor is uneven, use four people to move the enclosure stack, or contact a service provider.

• Move each enclosure stack slowly and gently, avoiding all unnecessary shock.

• When pushing the enclosure stack, push on the frame. Do not push or pull on a plastic enclosure door. Do not grasp the cable channels on the service side.

• Casters on the appearance side of the enclosure swivel, but casters on the service side do not swivel. If you position the swiveling appearance side casters to go first, it is easier to move the enclosure stack over bumps in the floor.

• A double-high enclosure stack tends to be top-heavy. When moving the enclosure stack off the pallet and down the ramp, do so carefully.

• If you plan to stack single-high system enclosures, you need at least five trained people. Anyone who lifts a system enclosure to stack it must be at least five feet tall and capable of lifting and holding approximately 25 pounds (11 kilograms).

vst988.vsd

Velcro Strips



5. Roll the enclosure or stack off the pallet.

a. Using at least two people, grasp the frame of the stack and slowly roll the enclosure stack off the pallet, down the ramp, and to the installation area:

6. Move the enclosure stack to its final position. Side frames can touch each other:

7. With a 3/4-inch (19-mm) or a 9/16-inch (15-mm) open-end wrench, lower each leg on the base enclosure and tighten it against the floor:

8. Repeat the unpacking and unloading tasks for all remaining system enclosures.

Figure E-3. Rolling the Stack to the Installation Area

Figure E-4. Enclosure Stacks in Final Positions

Figure E-5. Lowering Legs of Base Enclosure

vst986.vsd

Group 02

Group 01

VST707.vsd

Group 21

Group 11

VST017.vsd


FastPath Tasks: Required 4. Connect Groundstraps

4. Connect GroundstrapsIf the server consists of only one enclosure, skip to 5. Inventory and Inspect All Components on page E-11.

1. Find the groundstraps included with the system.

2. Find the four groundstrap connectors on the service side of each enclosure:

3. Connect the groundstraps:

Figure E-6. Groundstrap Connector Locations

VST701.vsd

GroundstrapConnectors

Groundstrap

02

Two Enclosures

01 11 01

Three Enclosures

0111

02

Four Enclosures

VST709.vsd

21

11

02

01


FastPath Tasks: Required 5. Inventory and Inspect All Components

5. Inventory and Inspect All Components 1. In each system enclosure, verify that all components ordered are present.

2. In each system enclosure, inspect the disk drives, PMF CRUs, IOMF CRUs, SEBs if present, MSEBs if present, and ServerNet adapters.

3. Reseat any CRU that appears to be improperly seated.

6. Connect the Power-On Cables1. Find the power-on cables included in a box with the system.

2. Find the power-on cable connectors on the service side of each enclosure:

3. Connect the power-on cables according to the appropriate diagram:

Note. The appearance side of the system enclosure is equipped with a door. If neces-sary, open the door with the 4-mm (5/32-inch) hex wrench that is located in the OPEN FIRST box or taped to the service side of the enclosure.

Figure E-7. Power-On Cable Connectors

Figure E-8. Power-On Cables: One Processor Enclosure

Figure E-9. Power-On Cables: One Processor Enclosure, One I/O Enclosure

Power-On Cable

VST703.vsd

01

VST110.vsd

VST111.vsd

0111


FastPath Tasks: Required 6. Connect the Power-On Cables

Figure E-10. Power-On Cables: One Processor Enclosure, Two I/O Enclosures

Figure E-11. Power-On Cables: Two Processor Enclosures

Figure E-12. Power-On Cables: Two Processor Enclosures, One I/O Enclosure

Figure E-13. Power-On Cables: Two Processor Enclosures, Two I/O Enclosures

VST119.vsd

011112

VST120.vsd

0201

VST121.vsd01

02

11

VST122.vsd01

02

11

21


FastPath Tasks: Required 7. Connect Emergency Power-Off (EPO) Cables

7. Connect Emergency Power-Off (EPO) CablesEmergency power-off (EPO) cables are used only if the system is installed in a room designed to comply with special construction and fire-protection provisions. If no EPO function is needed, skip to 8. Connect ServerNet Cables on page E-14.

1. Find the EPO cables included in a box with the system (one cable per enclosure):

2. Connect the unterminated end of one EPO cable to the appropriate junction box or facility wiring for the EPO control circuit at the customer site.

3. Attach the two-pin connector end of the EPO cable to the EPO connector (slot 56) on the service side of the system enclosure:

4. Repeat Step 2 and Step 3 for all remaining system enclosures.

Figure E-14. EPO Cable

VST908.vsd

Unterminated end

VST700.vsd

56

EmergencyPower-Off (EPO)

Connector


FastPath Tasks: Required 8. Connect ServerNet Cables

8. Connect ServerNet CablesIf the server consists of only one enclosure, skip to 9. Install Service-Side Enclosure Doors If Necessary on page E-15.

1. Find the ServerNet cables included with the system. These cables might be any of the following types:

• SEB-to-SEB ECL• SEB-to-MSEB ECL• MSEB-to-MSEB ECL• Serial-copper• Fiber-optic

Most two-processor or four-processor NonStop S-series systems use ECL cables. However, if your server is part of a ServerNet cluster, it might be equipped with other cables. See the NonStop S-Series Planning and Configuration Guide, the ServerNet Cluster Manual, and the ServerNet Cluster 6780 Planning and Installation Guide.

2. Connect the ServerNet cables according to the appropriate tables:

Table E-1. ServerNet Cables for One Processor Enclosure, One I/O Enclosure Attach Cable From Group Slot Connector To Group Slot01 51 5 11 50

01 52 5 11 55

Table E-2. ServerNet Cables for Two Processor Enclosures, No I/O EnclosuresAttach Cable From Group Slot Connector To Group Slot Connector01 51 1 02 51 1

01 52 1 02 52 1

Table E-3. ServerNet Cables for Two Processor Enclosures, One I/O EnclosureAttach Cable From Group Slot Connector To Group Slot Connector01 51 1 02 51 1

01 52 1 02 52 1

01 51 5 11 50 N.A.

01 52 5 11 55 N.A.


FastPath Tasks: Required 9. Install Service-Side Enclosure Doors If Necessary

3. Route the cables between the enclosures.

4. Connect and tighten the thumbscrews on the cable connectors.

9. Install Service-Side Enclosure Doors If NecessaryIf you need to install service-side doors on any enclosures, follow the instructions in the Read Me document included in the service-side door add-on package.

Table E-4. ServerNet Cables for Two Processor Enclosures, Two I/O EnclosuresAttach Cable From Group Slot Connector To Group Slot Connector01 51 1 02 51 1

01 52 1 02 52 1

01 51 5 11 50 N.A.

01 52 5 11 55 N.A.

02 51 5 21 50 N.A.

02 52 5 21 55 N.A.


FastPath Tasks: Required 10. Install Primary System Console

10. Install Primary System Console1. Locate and unpack the system console. If your system includes multiple consoles,

unpack only one console at a time:

You might also receive a kit to adapt the modem to your local telephone service.

Box ContentsSystem unit box Keyboard box

Accessories box

System unit

Accessories bag (in system unit box)

System unit power cord

Mouse with attached cable

Quick setup reference card

HP Restore CD

Windows XP Professional Workstation CD

Windows XP Professional Workstation Manual

Documentation

Keyboard box (in system unit box)

Keyboard with attached cable

PC accessory box 50-foot (15-meter) Ethernet cable

NonStop S-series system console binder

Assorted software media and documentation

Display monitor box

Display monitor with attached interface cable

Display monitor power cord

Documentation for the display monitor

Ethernet switch box

(Rack-mountable Ethernet switch packed in OPEN FIRST box)

Documentation for the Ethernet switch

Modem box Serial Modem USB Modem(Serial modem is packaged in the OPEN FIRST box)

USB modem

Wall-to-modem telephone cable Wall-to-modem telephone cable

Modem power converter with integral power cord

USB cable

Modem documentation Modem documentation


FastPath Tasks: Required 10. Install Primary System Console

2. Store the backup software packaged with the workstation in a safe place.

3. Set the system console on a table or other hard surface. Connect the remaining components such as the monitor, mouse, and keyboard.

To identify the various connectors on the workstation, see the quick setup reference card in the system console binder.

4. Connect the power cords for the workstation and monitor to a grounded outlet.

5. Determine whether your modem is a serial modem or a USB modem:

6. Connect the modem.

For a serial modem:

a. Connect the modem RS-232-C port to a serial port on the workstation.b. Connect the modem to a telephone line.c. Connect the modem power supply to a grounded outlet.

For a USB modem:

a. Connect the modem to the USB port on the front of the workstation. b. Connect the modem to the telephone line.c. If necessary, connect the telephone adapter kit.

7. Power on the following components:

a. Modemb. Display monitorc. Workstation

8. Test the operation of the system console.

a. Verify operation of the display monitor.b. Verify operation of the keyboard and mouse.c. Verify operation of the Windows operating system.

9. Ensure the workstation can be powered down and restarted in the same condition.

Caution. You should plan for the possibility of power outages. It is recommended that you prevent data corruption and equipment failure by providing surge suppression or backup power facilities for the system console, modem, and Ethernet switch.

Serial Modem USB ModemShipped with the EVO D500 PC workstation Shipped with the EVO 510 PC

workstation

Connects to the workstation with the Legacy module

Does not require the Legacy module

Requires a power converter with integral power cord to adapt it to local power

Powered through the USB connection, so it requires no converter


FastPath Tasks: Required 11. Create Emergency Repair Disk or AutomatedSystem Recovery Disk

11. Create Emergency Repair Disk or Automated System Recovery Disk

Much of your system configuration is saved to the Windows registry. If your Windows system files become corrupted, an emergency repair disk or automated system recovery disk can reconstruct them.

Use the backup procedure described in the Windows XP Professional documentation shipped with your system console.

12. Install Ethernet Switch Unpack and install Ethernet switch 1 using the documentation that came with the switch.

13. Connect Ethernet Switch to Group 011. Connect any port (except the cascade port) on the switch to the Ethernet port on

the PMF CRU in group 01, slot 50.

2. Connect the switch to the Ethernet port on the PMF CRU in group 01, slot 55.

Figure E-15. Connecting an Ethernet Switch to Group 01

Ethernet Port

Network InterfaceCard (NIC) onSystem ConsoleEthernet

Switch

Cascade Port

Ferrite Bead

RJ-45Plug

VST519.vsd


FastPath Tasks: Required 14. Connect Primary System Console to EthernetSwitch

14. Connect Primary System Console to Ethernet Switch

1. Connect a cable from Ethernet switch 1 to the network interface card behind the console.

2. Set the medium-dependent interface (MDI) switch on Ethernet switch 1 to MDI mode. To set this switch, see the documentation provided with the Ethernet switch.

15. Install Tape Drive

Installing a 5175 Tape Drive1. Determine which PMF CRU, IOMF CRU, or 6760 ServerNet device adapter

(ServerNet/DA) should be connected to the tape drive.

2. Unpack the tape drive module using the scissors or cutters.

3. Unload the tape drive module using the unloading ramp included with the unit.

4. Move the tape drive module into place.

5. Lower the legs on the pedestal using a 15/16-inch (24-mm) wrench.

6. Install the pedestal top panel and red corner caps.

7. Open the back panel of the 5175 tape drive.

8. Find the copper SCSI cable for the tape drive.

9. Connect the SCSI cable to the uncapped SCSI port at the rear of the tape drive. Latch the clips.

Caution. System consoles are shipped with identical IP addresses. To avoid software errors, specify a unique IP address for the backup system console before you connect the console to the Ethernet switch or NonStop S-series server.

Note. Do not connect this cable to the cascade port on switch 1.

Title PageInstalling a 5175 Tape Drive E-19

Installing a 519x Tape Drive E-21

Note. To perform a tape dump, connect the tape drive to a PMF CRU in groups 01 or 02.

Note. Ensure the tape drive CRU AC power switch is in the OFF (0) position.


FastPath Tasks: Required 15. Install Tape Drive

10. Depending on the model of your PMF CRU, attach the other end of the SCSI cable either to the SCSI terminator covering the SCSI port on the PMF CRU as shown, or to the SCSI port itself:

• S7000, S7400, S70000, and S72000 PMF CRUs have an external SCSI terminator.

• All other PMF CRUs contain an internal terminator, so you can attach the SCSI cable to the SCSI port directly.

11. Connect the AC power cord for the tape subsystem.

12. Reinstall and close the back panel of the 5175 module.

Caution. On a S7000, S7400, S70000, or S72000 PMF CRU, do not remove the external SCSI passthrough terminator from the differential SCSI port.

Figure E-16. Attaching SCSI Cable to PMF CRU

Cable fromthe tape

subsystem

VST016.vsd

PMF CRU

DifferentialSCSI Port

50 55

51 52 53 54

56

C

SCSI PassthroughTerminator


FastPath Tasks: Required 15. Install Tape Drive

Installing a 519x Tape Drive1. Determine which PMF CRU, IOMF CRU, or 6760 ServerNet/DA should be

connected to each tape drive.

2. Unpack the 519x tape drive module using scissors or cutters.

3. Unload the 519x tape drive module using the unloading ramp included with the unit.

4. Move the tape subsystem into place and lower the legs on the pedestal using a 15/16-inch (24-mm) wrench.

5. Remove foam packing from tape drives with an automatic cartridge loader (ACL).

6. If necessary, install the ACL and the cleaning cartridge.

7. Open and remove the rear bezel door of the tape drive module.

8. Find the copper tape subsystem SCSI cable:

9. Attach one end of the SCSI cable to the uncapped SCSI port at the rear of the tape drive.

10. Depending on the model of your PMF CRU, attach the other end of the SCSI cable either to the SCSI terminator covering the SCSI port on the PMF CRU as shown in Step 10 on page E-20, or to the SCSI port itself:

• S7000, S7400, S70000, and S72000 PMF CRUs have an external SCSI terminator.

• All other PMF CRUs contain an internal terminator, so you can attach the SCSI cable to the SCSI port directly.

11. Connect the AC power cord for the tape drive.

12. Reinstall and close the rear bezel door of the tape drive.

Note. Make sure the tape drive CRU AC power switch is in the OFF (0) position.

Caution. On a S7000, S7400, S70000, or S72000 PMF CRU, do not remove the external SCSI passthrough terminator from the differential SCSI port.


FastPath Tasks: Required 2. Start the System

2. Start the System

1. Prepare for System Startup1. If your system has multiple enclosures, verify that the ServerNet cables are

connected.

2. Verify that the following components are installed:

Task Page1. Prepare for System Startup E-28

2. Power On External System Devices E-23

3. Connect AC Power Cords E-24

Enclosures Without Power Shelves E-24

Enclosures With Power Shelves E-25

4. Apply Power to Server E-26

5. Verify Topology E-27

6. Verify System Components E-28

7. Start System E-28

Component NotesAll system enclosures N.A.

Power-on cables Not the same as the AC power cords. AC power cords are not installed until you are ready to apply power to the system.

Service-side enclosure doors Included with new system

Ethernet switch Must be connected to both the server and to the system console

OSM or TSM Verify that the system console on which OSM or TSM is installed is properly connected to the system

Emergency power-off (EPO) cables

Within the United States, an EPO disconnect is required in a system if the system is installed in a computer or data processing room that is designed to comply with the construction and fire-protection provisions of the following:

• NFPA-75, Protection of Electronic Computer/Data Processor Equipment

• Article 645, NFPA-70 (National Electric Code)

Outside the United States, an EPO disconnect is usually not required unless specified by local authorities.

Tape drive Used for processor memory dumps


FastPath Tasks: Required 2. Power On External System Devices

2. Power On External System Devices1. If necessary, power on the system consoles:

a. System unitb. Display monitorc. Modem

2. Power on the tape drive:

• To power on a 5175 tape drive:

a. Make sure the AC power cord is plugged into a dedicated power receptacle.

b. On the lower left side of the front panel of the tape drive, make sure the standby push-button switch is in the out (OFF) position.

c. Open the back panel of the 5175 module.

d. At the rear of the tape drive CRU, press the top part of the AC power switch (“|” on the rocker switch) to apply power to the tape drive.

e. Close the back panel of the 5175 module.

f. On the lower left side of the front panel of the tape drive, press the standby push-button switch so that it is in the in (ON) position.

• To power on a 519x tape drive:

a. Make sure the AC power cord is plugged into a dedicated power receptacle.

b. Open the rear bezel door.

c. At the rear of the tape drive CRU, set the AC power switch to the ON position to apply power to the tape drive.

d. Close the rear bezel door of the 519x module.

e. If the tape drive includes an automatic cartridge loader (ACL), install the cleaning cartridge in the ACL.

f. Check the tape drive SCSI ID using the operator buttons on the drive or ACL front panel. If necessary, reset the SCSI ID with the operator buttons.

• If your system has another type of tape drive, see the documentation for that tape drive.


FastPath Tasks: Required 3. Connect AC Power Cords

3. Connect AC Power Cords

Enclosures Without Power Shelves 1. Find the detachable AC power cords included with your system.

2. Start with the group 01 processor enclosure.

3. Make sure the power interlock on the PMF CRU or IOMF CRU in slot 50 or 55 is fully engaged so that the power cord retainer is aligned with the power receptacle.

4. Connect the AC power cord to the power receptacle on the PMF CRU or IOMF CRU.

5. Using a stubby Phillips screwdriver, secure the power cord plug in the power cord retainer by tightening the retainer screw.

6. Repeat Steps 3 through 5 for the other AC power cord for this enclosure and for all remaining enclosures without power shelves.


VST708.vsd

Power Cord Retainer

Retainer Screw

Power Receptacle

AC Power Cord

Power InterlockEjector


FastPath Tasks: Required 3. Connect AC Power Cords

Enclosures With Power ShelvesFor these enclosures, the DC power cords are shipped already connected to the power shelves. Use the following procedure only if these cables are not connected:

1. Find the detachable AC power cords included with your system.

2. Start with the group 01 processor enclosure.

3. Select either of the power supplies. Orient the molded end of the AC power cord with the single contact on the bottom. Insert the plug into the retainer until it is fully seated:

4. Swing the locking bar down until it engages one of the slots on the plug housing and snaps into place.

5. Repeat Steps 3 and 4 for the remaining power cord for this enclosure and for all remaining enclosures that have power shelves.


WARNING. The underside of the locking bar is sharp. Placing your fingers under the locking bar can result in injury. Failure to fully seat the plug in the retainer can result in cord damage from the locking bar.

Power CordRetainer

VST983.vsd

AC Power Cord

LockingBar

Slots onPlug Housing

01


FastPath Tasks: Required 4. Apply Power to Server

4. Apply Power to Server1. Start with the highest-numbered group. Switch on its circuit breaker or plug the

power shelf AC power cords into the designated AC receptacles.

2. On the service side of the enclosure, check that the fans are operating by placing your hand over the exhaust grill. The fans should be turning, and you should hear air circulating through the enclosure.

After a few seconds, if the fans do not operate, shut the system down quickly. See Power Is Applied to Enclosure But Fans Are Not Turning on page D-6.

3. Repeat Step 1 and Step 2 for all remaining enclosures without power shelves. Work in descending order of group number, ending with group 01.

4. During system startup, status LEDs on the various enclosures and CRUs light during a series of power-on self-tests (POSTs), which can take up to 10 minutes. All LEDs are lit briefly during POSTs, but only the green power-on LEDs should remain lit after the POSTs finish.

Before you start the system, ensure that POSTs have finished successfully. If the green power-on LED does not light or other LEDs remain lit, see Appendix D, Troubleshooting.


FastPath Tasks: Required 5. Verify Topology

5. Verify Topology1. Log on to the OSM or TSM Low-Level Link.

a. In the Log On dialog box, select system \NONAME.

b. Type root as the user name, with no password.

c. Click Log on. When the logon is successful, an empty window appears, and the message “logged on” appears in the status bar.

2. Verify that the topology is Tetra 8:

a. From the toolbar, select System Actions.

b. If the topology is Tetra 8, close the dialog box and skip to Step 8.

If the topology is Tetra 16, perform the following steps:

1. Select Show Actions.2. In the Available Actions list, select Set Topology to Tetra 8.3. Select Perform Action. Wait for the action to finish.

3. Return to the main screen and select Power off from the toolbar.

4. Push the Power-on push button on one of the PMF CRUs in group 01.

5. During system startup, status LEDs on the various enclosures and CRUs light during a series of power-on self-tests (POSTs), which can take up to 10 minutes. All LEDs are lit briefly during POSTs, but only the green power-on LEDs should remain lit after the POSTs finish.

You must ensure that POSTs have finished successfully before you start the system. If the green power-on LED does not light or other LEDs remain lit, see Appendix D, Troubleshooting before proceeding.

6. When system is powered on, log on as in Step 1.

7. When logon finishes, verify that Tetra 8 topology appears in the Attribute Value column. If the Topology attribute is Tetra 16 or an error, reset the topology to Tetra 8 before loading the system.

8. Click the System Discovery button on the toolbar. The Management window appears.

9. Verify that all system enclosures are visible in the Physical view.

If your server contains I/O enclosures but the Physical view does not show them, the Topology attribute value might be inconsistent with the topology of your system.

When you use the cabling tables in 8. Connect ServerNet Cables on page E-14, your system is connected as a Tetra 8 system.


FastPath Tasks: Required 6. Verify System Components

6. Verify System ComponentsFollow the instructions given in Verifying Topology and System Components on page 8-14.

Ensure that the value for each attribute is as listed in Table 8-3, Checking the Attributes of Selected System Components, on page 8-16.

7. Start System1. After POSTs finish, green power-on LEDs should remain lit. No amber LEDs

should be lit. If any LEDs exhibit abnormal behavior, see Appendix D, Troubleshooting.

2. Verify processor status:

a. On the menu bar, select Summary > Processor Status.b. Verify that all processors have passed POST.c. Close the Processor Status window.

3. From the toolbar, click Start System. The System Startup dialog box appears.


a. In the SYSnn field, enter 00 as the number of the SYSnn subvolume containing the version of the operating system to be loaded.

b. In the Configuration File box, select Current (CONFIG).

c. Ensure the CIIN disabled option has no check mark in the selection box.

5. Click Start system. The system load begins.

The event stream and TACL windows open on the console where the START SYSTEM was performed. If the workstation is not configured in the access list of authorized workstations, the windows are blank.

The startup TACL window for the primary fabric contains a TACL prompt. The startup event stream window for the primary fabric contains event messages. The other two windows are blank.

Note. If the Power State attribute for a PMF CRU does not have a value of On, contact your service provider.

Note. To stop startup, click Abort. Up to 30 seconds might pass before the abort takes effect.

Caution. Do not close the System Startup dialog box while startup is in progress. If you attempt to do so, a message box indicates that the system startup process will stop if you continue. If you stop a system startup before it has finished, results are unpredictable. You might need to start the system again to enable it to resume normal operation.

Note. The startup TACL windows and startup event stream windows launch directly on top of each other. You must move or minimize some of the window to see the active windows.


FastPath Tasks: Required 7. Start System

The operating system is loaded into the memory of processor 0 or processor 1. The remaining processors are reloaded by commands in the CIIN file.

6. Monitor the system startup process.

Messages indicating the progress and completion of the system load and the reload of the processors appear in the following locations on the system console:

• System Startup dialog box

° System Status box (initial high-level messages that are not logged to a file)° Detailed Status box (low-level messages that you can save to a file)

• Startup event stream window (startup event stream messages)

• Startup TACL window (startup messages)

7. When the operating system is loaded successfully into the memory of processor 0 or processor 1, the System Status box on the System Startup dialog box displays:

SYSTEM STARTUP COMPLETE, NSK RUNNING ON Processor n

8. Close the System Startup dialog box.

9. Check processor status:

a. From the toolbar, click Processor Status.

b. Verify that the NonStop operating system is running for all processors.

c. Close the Processor Status dialog box.

10. Log on to the OSM Service Connection or TSM Service Application.

11. In the tree pane, select System Object.

12. In the Attributes tab, verify that the Current Topology in OSM or the Topology attribute in TSM, has a value of Tetra 8.


FastPath Tasks: Required 3. Verify the System

3. Verify the System

1. Verify Components1. Log on to the OSM Service Connection or TSM Service Application.

2. Use the tree pane to check for any enclosures that have yellow or red icons over them.

3. Double-click to expand the enclosure or Group object further to identify components that require attention (yellow) or service (red).

4. Double-click the PMF CRU in slot 50.

5. Select the Processor object.

6. In the Attributes tab, verify that the Halt Code attribute has a value of 0 and that the Halt Flag has a value of False in OSM, or 0 in TSM.

7. For the Processor object in the PMF CRU in slot 55, repeat Steps 4 through 6.

Task Page1. Verify Components E-30

2. Verify Critical System Processes E-31

3. Verify Disk Drives E-31

4. Verify Tape Drive E-32

5. Verify Firmware E-32

6. Verify State of the Internal ServerNet Fabric E-32

Caution. If a red triangle appears over an enclosure diagram, or if any component is highlighted in red, contact your service provider.

Note. If the Halt Code or Halt Flag attributes do not match these values, see the Processor Halt Codes Manual.


FastPath Tasks: Required 2. Verify Critical System Processes

2. Verify Critical System Processes1. At the startup TACL window, log on to TACL:

> SUPER.SUPER

2. Enter the LISTDEV command:

> SCF LISTDEV

3. Verify that the LISTDEV display includes all processes shown in this example. If any of these processes are not listed in the display, call your service provider.

3. Verify Disk Drives1. Enter the SCF STATUS DISK command:

> SCF STATUS DISK $*

2. Verify that the STATUS DISK display includes all disk drives in this example. If any of these drives are not listed in the display, contact your service provider.

3. Verify that the primary, backup, mirror, and mirror backup paths are all STARTED. If any paths are STOPPED, restart the disks.

LDev Name PPID BPID Type RSize Pri Program 0 $0 0,5 1,5 ( 1,0 ) 102 201 \NONAME.$SYSTEM.SYS00.OSIMAGE 3 $YMIOP 0,256 1,256 ( 6,4 ) 80 205 \NONAME.$SYSTEM.SYS00.OSIMAGE 5 $Z0 0,7 1,7 ( 1,2 ) 102 200 \NONAME.$SYSTEM.SYS00.OSIMAGE 6 $SYSTEM 0,257 1,257 ( 3,41) 4096 220 \NONAME.$SYSTEM.SYS00.OSIMAGE 7 $ZOPR 0,8 1,8 ( 1,0 ) 102 201 \NONAME.$SYSTEM.SYS00.OSIMAGE 38 $ZZKRN 0,15 1,12 (66,0 ) 132 180 \NONAME.$SYSTEM.SYS00.OZKRN 39 $ZZWAN 0,271 1,275 (50,3 ) 132 180 \NONAME.$SYSTEM.SYS00.WANMGR 40 $ZZSTO 0,272 1,282 (65,0 ) 4096 180 \NONAME.$SYSTEM.SYS00.TZSTO 41 $ZZLAN 0,14 1,15 (43,0 ) 132 180 \NONAME.$SYSTEM.SYS00.LANMAN 45 $ZSNET 0,15 1,12 (66,0 ) 132 180 \NONAME.$SYSTEM.SYS00.OZKRN 46 $ZNET 0,16 1,14 (50,63) 3900 175 \NONAME.$SYSTEM.SYS00.SCP 61 $ZM01 1,11 0,0 (45,0 ) 132 201 \NONAME.$SYSTEM.SYS00.QIOMON 62 $ZM00 0,13 0,0 (45,0 ) 132 201 \NONAME.$SYSTEM.SYS00.QIOMON 63 $ZLOG 0,286 0,0 ( 1,0 ) 4024 150 \NONAME.$SYSTEM.SYS00.EMSACOLL 72 $DSMSCM 0,280 1,261 ( 3,41) 4096 220 \NONAME.$SYSTEM.SYS00.TSYSDP2 79 $AUDIT 0,273 1,271 ( 3,41) 4096 220 \NONAME.$SYSTEM.SYS00.TSYSDP2 85 $ZTCP0 0,299 1,280 (48,0 ) 32000 200 \NONAME.$SYSTEM.SYS00.TCPIP 88 $ZTNP0 0,301 1,276 (46,0 ) 6144 170 \NONAME.$SYSTEM.SYS00.TELSERV 98 $ZTCP1 1,283 0,304 (48,0 ) 32000 200 \NONAME.$SYSTEM.SYS00.TCPIP 100 $ZTNP1 1,285 0,305 (46,0 ) 6144 170 \NONAME.$SYSTEM.SYS00.TELSERV

STORAGE - Status DISK \NONAME.$AUDITLDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 79 *STARTED STARTED *STARTED STARTED 0,273 1,271

STORAGE - Status DISK \NONAME.$DSMSCMLDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 72 *STARTED STARTED *STARTED STARTED 0,280 1,261 STORAGE - Status DISK \NONAME.$SYSTEMLDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 6 *STARTED STARTED *STARTED STARTED 0,257 1,257


FastPath Tasks: Required 4. Verify Tape Drive

4. Verify Tape Drive1. Enter the SCF STATUS TAPE command:

> SCF STATUS TAPE $*

2. Verify that the STATUS TAPE display includes a least one tape drive configured and running, as shown in the following example. If no tape drive is listed in the display, call your service provider.

3. Verify the following:

• The state of the tape drive is STARTED• The substate is UP• The device status is READY

4. If the state, substate, or status of the tape drive is not as listed here, restart the tape drive.

5. Verify FirmwareUse the OSM Service Connection or TSM Service Application to verify that all updatable firmware is at the proper revision level.

For more information, see the OSM User’s Guide or the TSM Online User Guide.

6. Verify State of the Internal ServerNet FabricTo verify that the paths and connections within the ServerNet system area network (ServerNet SAN) are properly configured and functional:

1. Log on to the OSM Service Connection or TSM Service Application or.

2. In the tree pane, check for alarms on the Internal ServerNet X and Y Fabric objects.

3. If an alarm exists:

a. Select the fabric object displaying the alarm.

b. Select the Alarms tab of the details pane.

c. Select the individual alarm.

d. Select Detail.

4. Diagnose and resolve any problems that are causing the alarm. If necessary, contact your service provider.

STORAGE - Status TAPE $T0150LDev State Sub State Primary Backup Device Status PID PID 71 STARTED UP 0,282 1,273 READY


FastPath Tasks: Required 4. Configure the System

4. Configure the System

Use this section, regardless of the number of processors in your system, after verifying system operations. You must configure kernel-managed swap files, the OSM or TSM package, the system attributes, and DSM/SCM in the order specified in these procedures.

Topic Page1. Configure Passwords E-34

1a. Configure Super ID and Null User Passwords E-34

1b. Configure Root User Password E-34

2. Configure Kernel-Managed Swap Files E-35

3. Configure OSM or TSM Environment E-36

3a. Configure Dial-Out Workstation E-36

3b. Update Emergency Repair Disk or Automated System Recovery Disk E-36

4. Configure System Attributes E-37

4a. Save Current Configuration Database E-37

4b. Set System Name, Number, and Time E-38

4c. Restart System E-39

4d. Check and Reset System Time If Necessary E-39

4e. Invoke STARTCOM and STARTSCF Startup Files E-40

4f. Reconfigure Processes That Use SNMP E-40

5. Configure DSM/SCM E-41

5a Change System Name Parameter in DSM/SCM Client E-41

5b. Configure DSM/SCM System Environment E-42

5c. Configure Host Information for Host Database E-43

5d. Configure Target Information for Host’s Logical Target E-44

5e. Restart Inspect Monitor Process E-44


FastPath Tasks: Required 1. Configure Passwords

1. Configure Passwords

1a. Configure Super ID and Null User Passwords1. Log on to TACL using the super ID (255,255):

> logon super.super

> password: newpassword

2. Assign a password to the super ID (255,255):

> password newpassword

3. If you need the 0,0 (NULL.NULL) user ID, assign a password to it:

> logon null.null

> password newpassword

If you do not need the 0,0 (NULL.NULL) user ID, delete it:

> deluser null.null

1b. Configure Root User Password 1. Log on to the OSM or TSM Low-Level Link.

2. Complete a System Discovery.

3. From the File menu, select Add/Remove User IDs.

4. In the MSP Users dialog box:

a. Select the root user. (Predefined for the low-level link on new systems.)

b. Click Modify.

5. In the Change Low-Level Link Password dialog box:

a. Type a new password for the root user. Changing the password is strongly recommended for security.

b. Type the new password again to confirm it.

c. Click Change.

6. Click OK.

7. Click OK.

8. In the MSP Users dialog box, click OK.

Task Page1a. Configure Super ID and Null User Passwords E-34

1b. Configure Root User Password E-34


FastPath Tasks: Required 2. Configure Kernel-Managed Swap Files

2. Configure Kernel-Managed Swap Files1. Log on to TACL using the super ID (255,255):

> logon super.super

> password: password2. At the TACL prompt, type NSKCOM.

3. Use the NSKCOM ADD command to create swap files for each processor. For example:

NSK- ADD SWAPFILE $volume.subvolume.filename, CPU nn, SIZE nnn MB

4. Start the swap files. For example:

NSK- START SWAPFILE $volume.subvolume.filename

5. Confirm the amount of configured swap space for each processor. For example:

NSK- INFO SWAPFILE *

The minimum recommended file size of the swap file for each processor is approximately twice the size of the processor memory.

For more information, see the Kernel-Managed Swap Facility (KMSF) Manual.

Note. When naming configured swap files, do not use the naming convention for default swap files, $SYSTEM.ZSYSSSWAP.SWAPnn.


FastPath Tasks: Required 3. Configure OSM or TSM Environment

3. Configure OSM or TSM Environment

The following procedure configures the default OSM or TSM environment on your system. You must have the latest OSM or TSM software.

Accepting the default values might not provide the configuration you want. For example, dial-in and dial-out capability are not configured by default. However, you can change your configuration later.

To change your OSM or TSM configuration, or to complete the initial configuration without using the OSM or TSM default configuration values, see the OSM User’s Guide or the TSM Configuration Guide.

3a. Configure Dial-Out Workstation1. Start the OSM or TSM Notification Director.

2. In the Systems menu, select the system to be configured.

3. In the Licensing dialog box, click Continue.

4. In the Logon dialog box:

a. Type a valid user ID and password for the NonStop Kernel operating system.

b. Click Log on.

5. In the System Configuration dialog box, click the Preferences tab.

6. In the Preferences tab, select the following in the Dial-out Point Definition box:

• Select Primary Dial-out Point when configuring the primary system console.

• Select Backup Dial-out Point when configuring the backup system console.

7. Click OK to close the System Configuration dialog box.

3b. Update Emergency Repair Disk or Automated System Recovery DiskUpdate your Windows 2000 ERD or Windows XP ASR disk using the same procedure you used for creating an emergency repair disk or automated system recovery disk. See 11. Create Emergency Repair Disk or Automated System Recovery Disk on page E-18. Follow the applicable online help. Update the emergency repair disk or automated system recovery disk any time you change the configuration of your workstation in a way that changes the registry.

Task Page3a. Configure Dial-Out Workstation E-36

3b. Update Emergency Repair Disk or Automated System Recovery Disk E-36


FastPath Tasks: Required 4. Configure System Attributes

4. Configure System Attributes

4a. Save Current Configuration Database1. Log on to TACL using the super ID (255,255) and a valid password.

2. List the saved configuration files. At the SCF prompt:

-> FUP INFO $SYSTEM.ZSYSCONF.CONF*

3. Save the current configuration using a unique file name. At the SCF prompt:

-> SAVE CONFIGURATION xx.yy

where xx.yy is a number in the range 0.0 through 99.99.

A display appears in the terminal-emulation window as shown in the following example. This example saves the fourth minor change to the current system configuration to the file $SYSTEM.ZSYSCONF.CONF0104.

Caution. On a new system, you must complete these procedures before you run DSM/SCM or any other program that uses NonStop SQL/MP. Otherwise you might corrupt your SQL database.

Task Page4a. Save Current Configuration Database E-37

4b. Set System Name, Number, and Time E-38

4c. Restart System E-39

4d. Check and Reset System Time If Necessary E-39

4e. Invoke STARTCOM and STARTSCF Startup Files E-40

4f. Reconfigure Processes That Use SNMP E-40

-> SAVE CONFIGURATION 1.4The configuration file $SYSTEM.ZSYSCONF.CONF0104 has been created.



4b. Set System Name, Number, and Time1. Start SCF:

> SCF

2. Specify the Kernel subsystem and display the current settings:

-> ASSUME SUBSYS $ZZKRN

-> INFO, DETAIL

3. Type a unique (within your Expand network) system name and system number:

-> ALTER, SYSTEM_NAME \sys-name , SYSTEM_NUMBER sys-number

4. Type system time attributes:

-> ALTER, DAYLIGHT_SAVING_TIME time , TIME_ZONE_OFFSET offset

time is { TABLE | USA66 | NONE } ; NONE is the default value.

offset is { [ + | - ] [ h ] h [ :mm ] } ; 0:00 is the default value.

For more information on time and offset, see the SCF ALTER command in the SCF Reference Manual for the Kernel Subsystem.

5. Confirm the changes.

-> INFO

6. From a TACL prompt, verify that the $SYSTEM alternate key file does not point to \NONAME.$SYSTEM.SYSTEM. USERIDAK.

-> FUP INFO $SYSTEM.SYSTEM.USERID,DETAIL

Look for the Alt File parameter, which should not point to the system name.

7. Exit SCF.

8. If your system arrived with Open System Services (OSS) preconfigured, then after you change the system number (Step 3), you might experience a problem. The Enscribe key-sequenced database file $SYSTEM.ZXOSSMON.ZOSSFSET, which defines OSS filesets in the OSS file system, might refer to the old system number.

If it does, the OSS Monitor cannot open the database and the OSS file system cannot be started. Any product that ships with an Enscribe key-sequenced file might have this problem.

To prevent this situation, enter the following SCF commands after changing the system number:

-> VOLUME $SYSTEM.ZXOSSMON

-> ALTER ZOSSFSET, ALTFILE (0,ZOSSFS00)

-> ALTER ZOSSFSET, ALTFILE (1,ZOSSFS01)

-> EXIT



4c. Restart System1. Log on to the OSM or TSM Low-Level Link.

2. In the tool bar, click Processor Status. The Processor Status dialog box appears.

3. Select all processors.

4. From the Processor Actions drop-down menu, select Halt.

5. Click Perform action.

6. In the Processor Status dialog box, monitor the progress of the action. Wait for the processors to halt before proceeding.

7. From the toolbar, click Start System. The System Startup dialog box appears.


a. Type 00 as the number of the SYSnn subvolume containing the system image to be loaded.

b. Select Current as configuration file.

c. Ensure that the CIIN disabled option has no check mark in the checkbox.

9. Click Start system.

Four windows are launched: two startup event stream and two startup TACL windows. It might take a few seconds before the windows open.

10. When the system load is complete, the System Status portion of the System Startup dialog box displays:

SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n

11. In the toolbar, click Processor Status.

12. Verify that the NonStop Kernel operating system is running for all processors.

13. Close the Processor Status dialog box.

4d. Check and Reset System Time If NecessaryCheck the system time, log on to TACL, and reset the system time if the time is wrong:

> SETTIME month day year time

Note. The Start system function automatically resets the processor with the new attributes you defined. If you do not use the Start system function to reload the processors, you must first halt the processors, and then reset them by selecting Reset from the Processor Actions menu on the Processor Status dialog box.



4e. Invoke STARTCOM and STARTSCF Startup Files1. If necessary, log on to a TACL prompt.

2. At the TACL prompt, invoke the STARTCOM file:

> OBEY $SYSTEM.ZSYSCONF.STARTCOM

The STARTCOM file:

• Invokes the $SYSTEM.ZSYSCONF.STARTSCF command file to configure standard NonStop TCP/IP objects

• Starts NonStop TCP/IP services using the LAN devices configured in the CONFIG file

The STARTCOM and STARTSCF startup files configure objects that are not stored in the CONFIG file and therefore must be reconfigured by invoking their command files after a system load.

4f. Reconfigure Processes That Use SNMP1. At a TACL prompt, start SCF:

> SCF

2. List each process that uses SNMP:

-> LISTDEV SNMP

3. Type the following commands for each process that uses SNMP:

-> ASSUME PROCESS $ process-name

-> INFO ENDPOINT *

-> STOP ENDPOINT endpoint-name

-> ALTER ENDPOINT endpoint-name, network, $ tcpip

-> START ENDPOINT endpoint-name

-> INFO TRAPDEST *

-> STOP TRAPDEST trapdest-name

-> ALTER TRAPDEST trapdest-name, network, $ tcpip

-> START TRAPDEST trapdest-name


FastPath Tasks: Required 5. Configure DSM/SCM

5. Configure DSM/SCMPerform this procedure before installing any new software (SPRs or SUTs) on your system.

5a Change System Name Parameter in DSM/SCM Client1. Double-click the SETUP.EXE file in the DSMSCM program group.

DSM/SCM displays the Setup Logon screen, followed by licensing information and a series of dialog boxes.

2. Click OK in each dialog box until the dialog box asking for the system name appears.

3. Type the host system name. Click OK.

SETUP updates the DSMSCM.INI file on your workstation with the information you entered.

4. A dialog box appears

5. saying that SETUP is finished and asking if you want to start the Planner Interface. Click No.

6. Close the DSM/SCM program group.

Note. These basic DSM/SCM procedures configure the server as a stand-alone host system. For more information on these procedures and other DSM/SCM procedures, including configuring the system as a remote target system, see the DSM/SCM User’s Guide.

Task Page5a Change System Name Parameter in DSM/SCM Client E-41

5b. Configure DSM/SCM System Environment E-42

5c. Configure Host Information for Host Database E-43

5d. Configure Target Information for Host’s Logical Target E-44

5e. Restart Inspect Monitor Process E-44



5b. Configure DSM/SCM System Environment1. Log on to TACL using the super ID (255,255).

2. Start the Transaction Management Facility (TMF) subsystem:

> TMFCOM START TMF

3. Run INITENV from the ZDSMSCM subvolume:

> VOLUME $DSMSCM.ZDSMSCM> RUN INITENV

INITENV displays a series of questions. Answer them as described in the following steps.

4. To change the default settings, enter C.

5. INITENV displays the current system name and system number. Indicate that the information is correct.

This step confirms the system name and system number for DSM/SCM. It does not change the system name and number. Changing the system name and system number was performed in 4b. Set System Name, Number, and Time on page E-38.

6. Indicate that the system is a host system.

7. Type the database/Pathway owner user ID if you want to change the default value from being the super ID.

8. Type the name of a hometerm for DSM/SCM to use.

Note. You can use the Change option only once. An Initialization Build/Apply is not necessary when you use the Change option. However, if you change the system name and number again, you must use the Reinitialize option to reinitialize DSM/SCM, and then perform an Initialization Build/Apply before you can use DSM/SCM to manage software



5c. Configure Host Information for Host Database1. Run ZPHIHMI from the ZDSMSCM subvolume:

> VOLUME $DSMSCM.ZDSMSCM> RUN STARTSCM> RUN ZPHIHMI

2. Log on to the host Maintenance Interface using the super ID.

3. Add planners and their security as follows:

a. In the Maintenance Interface main menu, select 3 (Security Maintenance Menu). Press F1.

b. In the Security Maintenance Menu, select 1 (Planner Security Maintenance). Press F1.

c. In the Planner Security Maintenance screen, add the appropriate planners as instructed by the interface, specifying which DSM/SCM tasks each planner can perform.

d. When all planners are added, press F16 twice to return to the main menu.

4. Modify the Configuration Manager Profile:

a. In the main menu, select 7 (Configuration Manager Profile Maintenance) and press F1.

b. In the Configuration Manager Profile Maintenance screen, review the information, and change the default values if necessary.

c. Press Shift-F2 to enter changes. Press F16 to return to the main menu.

5. Press Shift-F16 to exit the host Maintenance Interface.

Note. The super ID is already set up as a planner.

Note. If necessary, use the SCF command LISTDEV TYPE 4 or SCF NAMES $ZZSTO, SUB TAPE to determine the name of the tape drive connected to the system.



5d. Configure Target Information for Host’s Logical Target1. Run ZPHITMI from the ZDSMSCM subvolume.

> VOLUME $DSMSCM.ZDSMSCM> RUN ZPHITMI

2. Log on to the target Maintenance Interface using the super ID.

3. Add operators and their security:

a. In the Maintenance Interface main menu, select 3 (Security Maintenance Menu). Press F1.

b. In the Security Maintenance Menu, select 1 (Operator Security Maintenance).

c. In the Operator Security Maintenance screen, add the appropriate operators as instructed by the interface, specifying which DSM/SCM tasks each operator can perform. When all operators are added, press F16 twice to return to the main menu.

4. Press Shift-F16 to exit the target Maintenance Interface.

5e. Restart Inspect Monitor ProcessIf Visual Inspect is installed on your system, for the G05 and later RVUs, $ZPM provides Inspect debugging and saveabend file capability by automatically starting the Inspect Monitor process $IMON early in the system startup sequence. However, Visual Inspect requires that $IMON be started after the TCP/IP and Port Mapper processes.

After $ZPM has started all processes specified in the CONFIG file, and you start all other TCP/IP and Port Mapper processes, stop and restart $IMON as follows:

1. Log on as the super ID.

2. At the TACL prompt, stop $IMON by entering:

> Stop $IMON

3. At the TACL prompt, restart $IMON by entering:

> IMON /name $IMON, term $YMIOP.#CNSL, cpu p, nowait /b

where p and b are the primary and backup processors, respectively, where $IMON is to run.

Note. The super ID is already set up as an operator.


FastPath Tasks: Required 5. Install the Backup System Console

5. Install the Backup System ConsoleYour system might not include a backup system console. If you received two system consoles, the second one is the backup console.

1. Unpack and assemble the backup console. See 10. Install Primary System Console on page E-16.

2. Select Start > Setting > Network Dial-up Connection > Local Area Connection.The Local Area Connection dialog box appears.

3. From the general tab, click properties.The Local Area Connection properties dialog box appears.

4. From the displayed list:

a. Click Internet Protocol (TCP/IP).b. Click properties.c. Click Specify an IP address.d. Enter the following values:

e. Click OK to close all the windows.

5. Close all dialog boxes.

6. Click Start.

7. Click Setting > Control Panel > System.The system properties dialog box appears.

8. Click the Network Identification tab.


10. Change the computer name to TANDEM2.

11. Click OK to close the window.

12. Unpack and install the Ethernet switch 2 using documentation that came with the switch.

13. Connect the backup system console to switch 2:

a. Connect an Ethernet cable to the network interface card behind the console.b. Connect the other end of this Ethernet cable to a port on switch 2.

Caution. All system consoles are shipped with the same IP address. To permit the primary and backup system consoles to operate simultaneously, specify a unique IP address for the backup system console before you connect that console to the Ethernet switch or hub and server.

IP Address 192.231.36.4Subnet Mask 255.255.255.0Default Gateway 192.231.36.9


FastPath Tasks: Required 5. Install the Backup System Console

14. Connect an Ethernet cable from the cascade port of switch 1 to a port on switch 2, as shown following. Do not use the cascade port on switch 2.

15. Disconnect the cable between switch 1and the Ethernet port on the PMF CRU in slot 55, group 01.

16. Connect the cable between switch 2 and the Ethernet port on the PMF CRU in slot 55, group 01 as shown:

17. Perform 3. Configure OSM or TSM Environment on page E-36.

Note. The connections shown are only examples. Actual connections might vary.

Figure E-17. Adding a System Console to the Operating Configuration

Note. The backup system console might display the following message: Unable to establish a TCP/IP connection to:0.0.0.0 23. To fix this problem, do not modify the default parameter file TDMTSM.PRM. See the TSM Low-Level Link online help.

VST537.vsd

CascadePort


settings forEthernet switches

Ethernet Switch 1 Ethernet Switch 2To Backup

System Console

To PrimarySystemConsole

CascadePort

PMF CRUcontaining

Processor 1

PMF CRUcontaining

Processor 0

Group 01

MDIto

EthernetSwitch

MDI-Xto PC


F FastPath Tasks: Optional This appendix contains all optional configuration tasks for a two-processor or four-processor NonStop S-series server in the Tetra 8 topology.

If your server contains more than four processors or must be configured in the Tetra 16 topology, do not use this appendix. See the rest of this manual.

Topic Page1. Prerequisites F-2

1a. Verify Required Configuration Changes F-2

1b. Review Initial System Configuration F-2

1c. Start Required Processes F-2

1d. Save Current System Configuration F-3

1e. If Your Server Will Be Part of a ServerNet Cluster F-3

2. Customize the System Configuration F-4

2a. Change SCF F-4

2b. Rename SCF Objects in the CONFIG File F-5

2c. Add SCF Objects to the CONFIG File F-6

3. Automate System Startup F-7

Modify Provided Startup Files F-7

Create Startup Files F-7

4. Automate System Shutdown F-8

Tips for Shutdown Files F-8

5. Configure a SWAN or SWAN 2 Concentrator F-9

Access the WAN Wizard Pro F-9

6. Configure an Expand-Over-IP Line F-10

Prerequisites F-11

1. On the NonStop S-Series Server F-12

2. On the NonStop K-Series Server F-16



5. On Either NonStop Server F-21

7. Install Software F-22

Configuring Software With DSM/SCM F-23

Installing a Software Product Revision (SPR) F-25

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001F-1

FastPath Tasks: Optional 1. Prerequisites

1. PrerequisitesBefore you change the system configuration, complete the following tasks.

1a. Verify Required Configuration ChangesVerify that the procedures in Appendix E, FastPath Tasks: Required are complete.

1b. Review Initial System ConfigurationThe following initial system configuration is shipped in the OPEN FIRST box:

• CONFTEXT configuration file list• SCF initial configuration file list: $SYSTEM. ZSYSCONF. SCF0000.

The SCF0000 file is an input file to the initial $SYSTEM. ZSYSCONF.CONFIG file.

Verify how the system is initially configured:

• Which processes and devices are already configured in the initial system configuration database and started automatically during system load?

• Which processes do not start automatically and therefore require startup files?

• Which processes and devices must not be renamed?

For information about default values for OSM or TSM, see the OSM User’s Guide or the TSM Configuration Guide as appropriate.

1c. Start Required Processes Before you perform some system configuration procedures, such as configuring Expand-over-IP, certain processes must be started. Some of these processes do not start automatically when the system is loaded. Examples of such processes include:

• NonStop TCP/IP processes (except $ZTCP0 and $ZTCP1)• Parallel Library TCP/IP processes and associated routes and subnets

For information about the standard configuration and startup files for NonStop TCP/IP processes that are shipped with your system, see Preloaded Hardware and Software on page 1-49.

To modify the standard startup files or create startup files for required processes, see 3. Automate System Startup on page F-7.

1a. Verify Required Configuration Changes F-2

1b. Review Initial System Configuration F-2

1c. Start Required Processes F-2

1d. Save Current System Configuration F-3

1e. If Your Server Will Be Part of a ServerNet Cluster F-3


FastPath Tasks: Optional 1d. Save Current System Configuration

1d. Save Current System ConfigurationSave the current system configuration (CONFIG) before making any changes. This practice allows you to undo changes if necessary. If the most recent change results in a problem, you can restore the previous system configuration by loading the system from the saved system configuration file.

Save the current CONFIG file as follows:

1. List the saved configuration files. At the SCF prompt:


2. Save the current configuration using a unique file name. At the SCF prompt:



1e. If Your Server Will Be Part of a ServerNet ClusterThe NonStop ServerNet Cluster product connects multiple servers in a cluster (up to 24 servers using the star topologies and up to 64 servers using the layered topology) and passes information from one server to any other server in the cluster. This product extends the ServerNet fabrics outside the system boundary and allows the ServerNet protocol to be used for intersystem messaging.

A ServerNet cluster consists of individual servers, each containing internal ServerNet fabrics, connected through fiber-optic cables and cluster switches to other servers. Only NonStop S-series servers can belong to a ServerNet cluster.

For information about configuring a server as part of a ServerNet cluster, see the ServerNet Cluster Manual (for star topologies) or the ServerNet Cluster 6780 Planning and Installation Guide (for layered topologies).


FastPath Tasks: Optional 2. Customize the System Configuration

2. Customize the System ConfigurationAdapt the CONFIG file to your system. Some of the ways you can customize the CONFIG file include:

• Renaming SCF objects that are not part of the standard configuration• Adding SCF objects that are not part of the initial system configuration

2a. Change SCF1. Create a command file containing the SCF commands to change the configuration:

a. Copy the SCF0000, STARTCOM, and STARTSCF files as templates for SCF command files.

Changing these files directly is not recommended.

b. Configure important processes as persistent generic processes.

Persistent processes start automatically at system load and restart automatically if stopped.

c. Place commands that change the CONFIG file in a command file that is separate from the commands that do not change the CONFIG file.

Commands that change the CONFIG file use the SCF interface to the WAN, Kernel, storage, LAN, ServerNet/FX, and ATM subsystems. Commands that do not change the CONFIG file use the SCF interface to all other subsystems.

2. For fallback purposes, save the current system configuration database CONFIG file. See 1d. Save Current System Configuration on page F-3.

3. Invoke the SCF command file created in Step 1. For example:

-> SCF/ IN SCF0000/

For more information, see the SCF subsystem documentation.

2a. Change SCF F-4

2b. Rename SCF Objects in the CONFIG File F-5

2c. Add SCF Objects to the CONFIG File F-6


FastPath Tasks: Optional 2b. Rename SCF Objects in the CONFIG File

2b. Rename SCF Objects in the CONFIG FileThe naming convention for SCF objects usually suggests the physical location of the object in the enclosure. Most SCF objects can be renamed. The SCF objects that cannot be renamed include:

• $SYSTEM disks

• The following processes and devices used by OSM or TSM:

• The following generic processes:

You can display the names of these generic processes by entering the following SCF command:

-> NAMES $ZZKRN

• $DSMSCM and $AUDIT disks (strongly discouraged)

LANX $ZCVP0 $ZPRP0 $ZSPE $ZCMOM

LANY $ZCVP1 $ZPRP1 $ZTSM $ZOEV

MIOE0 $ZTCP0 $ZTNP0 $ZTSMS $ZOLHI

MIOE1 $ZTCP1 $ZTNP1 $ZOSM

$ZZKRN.#CEV-SERVER-MANAGER-P0 $ZZKRN.#CEV-SERVER-MANAGER-P1

$ZZKRN.#CLCI-TACL $ZZKRN.#IMON

$ZZKRN.#QIOMON-0 $ZZKRN.#QIOMON-1

$ZZKRN.#QIOMON-2 $ZZKRN.#QIOMON-3

$ZZKRN.#ROUTING-DIST $ZZKRN.#SCP

$ZZKRN.#TSM-SNMP $ZZKRN.#SP-EVENT

$ZZKRN.#TSM-SRM $ZZKRN.#ZLOG

$ZZKRN.#ZTCP0 $ZZKRN.#ZTCP1

$ZZKRN.#ZHOME $ZZKRN.#ZZKRN

$ZZKRN.#ZZLAN $ZZKRN.#ZZSTO

$ZZKRN.#ZZWAN


FastPath Tasks: Optional 2c. Add SCF Objects to the CONFIG File

2c. Add SCF Objects to the CONFIG FileYou can customize your system configuration by adding SCF objects that are not part of the initial system configuration. For example, you can:

• Add devices that were not included in the initial system configuration.

• Configure important system processes as generic processes.

Only processes that can be started from a TACL prompt and do not require PARAM or ASSIGN messages can be configured as generic processes. For more information about configuring generic processes, see the SCF Reference Manual for the Kernel Subsystem.

For example, to make an important system process, such as the Expand manager process, start automatically at system load and have persistence (that is, to restart automatically if stopped abnormally), create it as a generic process in the system configuration database:

1. Create an SCF command file containing the correct commands. For example, you can configure the Expand manager process as follows:

2. Save the current configuration database file. See 1d. Save Current System Configuration on page F-3.

3. Invoke the command file created in Step 1. For example:

> SCF / IN GPADD /

4. Start the process.

============================================================================ Expand manager process ============================================================================ADD PROCESS $ZZKRN.#ZEXP, NAME $ZEXP, PRIORITY 180, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.OZEXP, PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER, & STARTMODE SYSTEM, HOMETERM $ZHOME, OUTFILE $ZHOME, & STARTUPMSG "<BCKP-CPU>"


FastPath Tasks: Optional 3. Automate System Startup

3. Automate System Startup Some system applications and subsystems are not configured to start automatically in the initial CONFIG file. Startup command files can automate the starting of devices and processes on the system. Automating system startup minimizes the possibility of operator errors caused by forgotten or incorrectly typed commands.

To automate system startup, you can Modify Provided Startup Files or Create Startup Files.

Modify Provided Startup FilesFor a description of the startup files shipped with the server, see Preloaded Hardware and Software on page 1-49. Consider modifying the RELOAD command in the CIIN file to reload only a minimal set of processors (such as processor 1). This strategy allows you to test for successful startup of a minimal system environment before you bring up the remainder of the system.

Create Startup FilesYou can implement the system startup sequence with a collection of startup files, each with a specific purpose. Startup files can be created for:

• System software• Subsystems• Communications lines• Applications

Tips for Startup Files• Copy the STARTCOM and STARTSCF files on the $SYSTEM.ZSYSCONF

subvolume and make changes to these copies to create your own command files. Do not alter these files directly.

• The sequence in which you invoke startup files can be important. Some processes require other processes to be running before they can be started. Be sure to indicate the order in which startup files are to be run.

• You must configure a line-handler process for a data communications line in the CONFIG file before you can invoke a startup file for that line, if one is required.

• You do not need to create startup files for processes in the CONFIG file that are configured to start automatically.

• It is recommended that you specify “N” for the read access portion of the file security attribute (RWEP) for your startup files to allow the file to be read by any user on the network. For example, you might secure these files “NCCC.”


FastPath Tasks: Optional 4. Automate System Shutdown

4. Automate System ShutdownAutomating system shutdown aids the operator in bringing the system to an orderly halt. You can implement the system shutdown sequence with a collection of shutdown files, each with a specific purpose.

Be sure to indicate the order in which shutdown files are to be run; the sequence in which you invoke shutdown files is important. The shutdown file sequence reverses the order of commands in the startup file sequence. Some processes require that other processes be stopped before they can be stopped. Shut down your system by invoking the shutdown files in this order:

1. Shutdown files for the applications2. Shutdown files for the communications lines3. Shutdown files for the subsystems4. Shutdown files for the system software5. Shutdown file for the system

Tips for Shutdown FilesIt is recommended that you specify “N” for the read access portion of the file security attribute (RWEP) for your shutdown files to allow the file to be read by any user on the network. For example, you might secure these files “NCCC.”


FastPath Tasks: Optional 5. Configure a SWAN or SWAN 2 Concentrator

5. Configure a SWAN or SWAN 2 ConcentratorThe ServerNet wide area network (SWAN) concentrator and the SWAN 2 concentrator are communications devices that connect to a NonStop S-series server through dual Ethernet ports and provide WAN connections. They support both synchronous and asynchronous data using EIA-232, EIA-449, V.35, and X.21 electrical and physical interfaces.

The SWAN concentrator or SWAN 2 concentrator connects to your NonStop S-series server through Ethernet ports on one or two Ethernet 4 ServerNet adapters (E4SAs).

To configure a SWAN concentrator or SWAN 2 concentrator, you can use the WAN Wizard Pro configuration tool, a graphical user interface (GUI) that eliminates using multiple Subsystem Control Facility (SCF) commands.

Access the WAN Wizard Pro From the task bar on your system console, click:

Start > Programs > HP WAN Wizard Pro > WAN Wizard Pro


FastPath Tasks: Optional 6. Configure an Expand-Over-IP Line

6. Configure an Expand-Over-IP LineThis section describes how to configure an Expand-over-IP connection to a network through a NonStop K-series server.

To help you create an Expand connection quickly, this procedure describes how to configure a single Expand-over-IP line with default configuration values. To customize the Expand configuration described in this section, see the Expand Configuration and Management Manual.

Topic PagePrerequisites F-11

NonStop S-Series Server F-11

NonStop K-Series Server F-11


1a. Save the Current Configuration F-12

1b. Configure $ZEXP F-12

1c. Configure $NCP F-13

1d. Obtain TCP/IP Information F-13


2a. Obtain TCP/IP Information F-16


3a. Configure and Start an Expand-Over-IP Line-Handler Process F-18


4a. Configure and Start an Expand-Over-IP Line-Handler Process F-19

5. On Either NonStop Server F-21

5a. Start the Expand-Over-IP Line F-21


FastPath Tasks: Optional Prerequisites

PrerequisitesThe NonStop S-series and K-series servers should be in the following states.

NonStop S-Series Server

NonStop K-Series Server

State NotesThe default system configuration with which the system was shipped is complete.

The initial OSM or TSM configuration is complete.

See 3. Configure OSM or TSM Environment on page E-36.

The system name and system number are defined.

See 4b. Set System Name, Number, and Time on page E-38.

The NonStop Kernel subsystem is configured and started.

This function is automatic.

The QIO subsystem is configured and started. This function is automatic.

The WAN subsystem manager process ($ZZWAN) is configured and started.

This process should start automatically.

The ServerNet LAN Systems Access (SLSA) subsystem is configured and started.

This subsystem should start automatically.

An Ethernet 4 ServerNet adapter (E4SA) is installed, configured, and started.

This adapter should start automatically.

A NonStop TCP/IP process and its associated routes and subnets are defined and started.

To start the NonStop TCP/IP process, use the STARTCOM and STARTSCF files.

StateThe default system configuration with which the system was shipped is complete.

The initial SYSGENR/Install software configuration is complete.

The following subsystems are configured and started:

• HP Tandem LAN Access Method (TLAM)• QIO

An Ethernet controller is installed, configured, and started.

The system name and system number are defined.

The following processes are configured and started:

• A NonStop TCP/IP process and associated routes and subnets• The Expand network control process ($NCP)

The server is running the D40 product version of the Expand subsystem.

A dummy controller is configured and has available unit numbers.


FastPath Tasks: Optional 1. On the NonStop S-Series Server

1. On the NonStop S-Series Server

1a. Save the Current ConfigurationAt the SCF prompt:



A display appears in the terminal-emulation window as shown in the following example. In this example, the operator saves the fourth minor change to a current system configuration to the file $SYSTEM.ZSYSCONF.CONF0104.

1b. Configure $ZEXP

1. Log on to the NonStop S-series server using the super ID (255.255) and enter the correct password at the Password prompt:

> logon super.super

Password: password

2. At the TACL prompt, start the Subsystem Control Facility (SCF):

> SCF

3. Add the Expand manager process ($ZEXP) as a generic process. At the SCF prompt:

-> ADD PROCESS $ZZKRN.#ZEXP, NAME $ZEXP, PRIORITY 180, & AUTORESTART 10,PROGRAM $SYSTEM.SYSTEM.OZEXP, & PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER,STARTMODE SYSTEM, & HOMETERM $ZHOME, OUTFILE $ZHOME, STARTUPMSG "<BCKP-CPU>"

4. Start the Expand manager process ($ZEXP):

-> START PROCESS $ZZKRN.#ZEXP

-> SAVE CONFIGURATION 1.4The configuration file $SYSTEM.ZSYSCONF.CONF0104 has been created.

Note. Do not log off or exit SCF on the NonStop S-series server after finishing this task. The remaining tasks in this section that you must perform on the NonStop S-series server require the use of SCF commands and super ID privileges.

Note. Use this command to start $ZEXP for the first time. Thereafter, the persistence monitor $ZPM automatically:

• Starts $ZEXP during a system load or processor reload• Restarts $ZEXP if it stops while the system is running



1c. Configure $NCP1. From an SCF prompt, create a profile for the network control process:

-> ADD PROFILE $zzwan.#pexpncp, file $system.sys00.pexpncp

2. Confirm that the profile has been created:

-> INFO PROFILE $zzwan.#pexpncp

3. Create the network control process:

-> ADD DEVICE $zzwan.#ncp, iopobject $system.sys00.ncpobj, &-> PROFILE pexpncp, cpu 0, altcpu 1, type (62,6), rsize 1

4. Start the network control process:

-> START DEVICE $zzwan.#ncp

1d. Obtain TCP/IP Information1. Determine the name of the NonStop TCP/IP, Parallel Library TCP/IP (TCPSAM), or

NonStop TCP/IPv6 (TCP6SAM) process you want to associate with the Expand-over-IP line-handler process.

To list all TCP/IP transport service providers:

> LISTDEV TCPIP

The SCF LISTDEV program displays process types as follows:

The following example output shows both TCPSAM and NonStop TCP/IP processes because NonStop TCP/IP and Parallel Library TCP/IP are both running on this system. (Parallel Library TCP/IP and NonStop TCP/IPv6 cannot run on the same system.)

Type of process Program field ends in ...Conventional NonStop TCP/IP TCPIP

Parallel Library TCP/IP TCPSAM

NonStop TCP/IPv6 TCP6SAM

Example F-1. SCF LISTDEV TCPIP DisplayLDev Name PPID BPID Type RSize Pri Program

124 $ZTC02 0,301 1,287 (48,0) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPSAM 125 $ZTCP0 0,304 1,282 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 129 $ZTCP1 1,285 0,308 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 160 $ZTC21 2,292 3,276 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 161 $ZTC01 0,313 1,292 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 165 $ZTC03 0,316 1,293 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP



To list all NonStop TCP/IP and TCP6SAM transport service providers:

> LISTDEV TCPIP

The following output shows both TCP6SAM and NonStop TCP/IP processes because NonStop TCP/IP and NonStop TCP/IPv6 are both running on this system. (Parallel Library TCP/IP and NonStop TCP/IPv6 cannot run on the same system.)

2. The NonStop TCP/IP, TCPSAM, or TCP6SAM process you select must have an Ethernet subnet configured.

To list the subnets configured for a particular TCP/IP process:

-> INFO SUBNET $tcpip-process-name.*

Example F-3 shows an SCF INFO SUBNET display. Ethernet subnets are identified by the word ETHERNET in the TYPE field.

3. Record the name of the NonStop TCP/IP, TCPSAM, or TCP6SAM process you selected (shown in the Name field of the SCF LISTDEV display) in the tcpip_process field in the SCF ADD DEVICE Command Worksheet on page F-18.

4. Locate the first numbers in the PPID and BPID fields in the SCF LISTDEV display. These are the primary and backup processor numbers for the NonStop TCP/IP, TCPSAM, or TCP6SAM process. Record them in the cpunum and altcpunum fields in the SCF ADD DEVICE Command Worksheet on page F-18.

5. Record the IP address of the subnet you want to use in the src_ipaddr field in the SCF ADD DEVICE Command Worksheet on page F-18 and in the dest_ipaddr field in the COUP Worksheet on page F-20.

Example F-2. SCF LISTDEV TCP6SAM DisplayLDev Name PPID BPID Type RSize Pri Program

124 $ZTC02 0,301 1,287 (48,0) 32000 200 \MYSYS.$SYSTEM.SYS00.TCP6SAM 125 $ZTCP0 0,304 1,282 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 129 $ZTCP1 1,285 0,308 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 160 $ZTC21 2,292 3,276 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 161 $ZTC01 0,313 1,292 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP 165 $ZTC03 0,316 1,293 (48,0 ) 32000 200 \MYSYS.$SYSTEM.SYS00.TCPIP

Example F-3. SCF INFO SUBNET Display TCPIP Info SUBNET \MYSIS.$ZTC21.*

Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R

#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N#SN1 \MYSIS.LANX 172.16.35.16 ETHERNET %HFFFFFF00 ON N



6. Determine a User Datagram Protocol (UDP) port number to be used by the Expand-over-IP process:

-> STATUS PROCESS $tcpip-process-name

Example F-4 shows an SCF STATUS PROCESS display. UDP port numbers are identified by UDP in the Proto field.

UDP port numbers in use are shown in the LPort field. Choose any valid unused UDP port number. Do not use well-known port numbers in the range 0 through 1023.

7. Record the UDP port number to use in the src_ipport field in the SCF ADD DEVICE Command Worksheet on page F-18 and in the dest_ipport field in COUP Worksheet on page F-20.

Example F-4. SCF STATUS PROCESS DisplayTCPIP Status PROCESS \MYSYS.$ZTC21Status: STARTEDPPID............ ( 2,293) BPID................... ( 3,277)Proto State Laddr Lport Faddr Fport SendQ RecvQ TCP LISTEN 0.0.0.0 9000 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 telnet 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 ftp 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 finger 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 echo 0.0.0.0 * 0 0 UDP 172.16.35.16 5705 0.0.0.0 * 0 0 UDP 172.16.35.16 5706 0.0.0.0 * 0 0 UDP 172.16.35.16 5703 0.0.0.0 * 0 0 UDP 172.16.35.16 5704 0.0.0.0 * 0 0 UDP 0.0.0.0 1030 0.0.0.0 * 0 0 UDP 0.0.0.0 69 0.0.0.0 * 0 0 UDP 0.0.0.0 68 0.0.0.0 * 0 0 UDP 0.0.0.0 67 0.0.0.0 * 0 0


FastPath Tasks: Optional 2. On the NonStop K-Series Server

2. On the NonStop K-Series Server

2a. Obtain TCP/IP Information1. Log on to the NonStop K-series server using the super ID and enter the correct

password at the Password prompt:

> logon super.superPassword: password

2. At the TACL prompt, start SCF:

> SCF

3. Determine the name of the NonStop TCP/IP process you associated with the Expand-over-IP line-handler process on the NonStop K-series server:

-> LISTDEV TCPIP

Example F-5 shows an SCF LISTDEV TCPIP display. Important information is highlighted in boldface type.

4. The NonStop TCP/IP process you select must have an Ethernet subnet configured. List the subnets configured for a particular NonStop TCP/IP process:

-> INFO SUBNET $tcpip-process-name.*

Example F-6 shows an SCF INFO SUBNET display. Ethernet subnets are identified by the word ETHERNET in the TYPE field. Important information is highlighted in boldface type.

5. Record the name of the NonStop TCP/IP process you selected (shown in the Name field in the SCF LISTDEV display) in the tcpip_process field in the COUP Worksheet.

Example F-5. SCF LISTDEV TCPIP DisplayLDev Name PPID BPID Type RSize Pri Program

124 $ZTC2 4,43 7,28 (48,0) 32000 200 \JOHN.$SYSTEM.ZTCPIP.TCPIP 716 $ZTC0 4,39 7,36 (48,0 ) 32000 150 \JOHN.$SYSTEM.ZTCPIP.TCPIP 723 $ZTC1 9,28 8,33 (48,0 ) 32000 150 \JOHN.$SYSTEM.ZTCPIP.TCPIP 740 $ZTC3 5,12 6,33 (48,0 ) 32000 150 \JOHN.$SYSTEM.ZTCPIP.TCPIP 749 $ZTC10 4,45 5,38 (48,0 ) 32000 150 \JOHN.$SYSTEM.ZTCPIP.TCPIP1148 $ZTCS0 12,46 13,71 (48,0 ) 32000 150 \JOHN.$SYSTEM.ZTCPIP.TCPIP1633 $ZTCS2 12,79 13,70 (48,0 ) 32000 150 \JOHN.$SYSTEM.ZTCPIP.TCPIP

Example F-6. SCF INFO SUBNET DisplayTCPIP Info SUBNET \JOHN.$ZTC10.*

Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R

#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N#EN0 \JOHN.$LAM12 155.186.70.123 ETHERNET %HFFFFFC00 ON N



6. Record the primary and backup processor numbers (the first number in the PPID and BPID fields in the SCF LISTDEV display) in the cpunum and altcpunum fields in the COUP Worksheet.

7. Record the IP address of the subnet you want to use (shown in the IPADDRESS field in the SCF INFO SUBNET display) in the dest_ipaddr field in the SCF ADD DEVICE Command Worksheet and in the src_ipaddr field in the COUP Worksheet.

8. Determine a UDP port number to be used by the Expand-over-IP line-handler process:

-> STATUS PROCESS $tcpip-process-name

Example F-7 shows an SCF STATUS PROCESS command. UDP port numbers are identified by UDP in the Proto field.

UDP port numbers in use appear in the LPort field. You can choose any valid UDP port number that is not in use. It is recommended that you do not use well-known port numbers in the range 0 through 1023.

9. Record the UDP port number you want to use in the dest_ipport field in the SCF ADD DEVICE Command Worksheet and in the src_ipport field in COUP Worksheet.

10. Exit SCF:

-> EXIT

Example F-7. SCF STATUS PROCESS DisplayTCPIP Status PROCESS \JOHN.$ZTC10

Status: STARTED

PPID............ ( 4, 45) BPID................... ( 5, 38)

Proto State Laddr Lport Faddr Fport SendQ RecvQ

TCP ESTAB 172.16.10.50 110 155.186.68.169 1128 0 0 TCP ESTAB 127.0.0.1 1101 127.0.0.1 smtp 0 0 TCP ESTAB 127.0.0.1 1100 127.0.0.1 smtp 0 0 TCP ESTAB 127.0.0.1 smtp 127.0.0.1 1100 0 0 TCP ESTAB 127.0.0.1 smtp 127.0.0.1 1101 0 0 TCP LISTEN 0.0.0.0 110 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 6006 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 smtp 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 ftp 0.0.0.0 * 0 0 TCP LISTEN 0.0.0.0 finger 0.0.0.0 * 0 0 UDP 172.16.10.50 11221 0.0.0.0 * 0 0 UDP 172.16.10.50 11222 0.0.0.0 * 0 0

Note. Do not log off after completing this task.



3. On the NonStop S-Series Server

3a. Configure and Start an Expand-Over-IP Line-Handler Process1. Return to the SCF prompt at the NonStop S-series server.

2. Create a profile for the Expand-over-IP line-handler process by entering the following SCF command:

-> ADD PROFILE $zzwan.#pexpsip, file system.sys00.pexpsip

3. Add the Expand-over-IP line-handler process as a device to the WAN subsystem using the values you record in Table F-1. Fields that must be replaced by values you record in the worksheet are highlighted in boldface italic type.

-> ADD DEVICE $zzwan.$sline, profile pexpsip, &-> IOPOBJECT $system.sys00.lhobj, &-> ASSOCIATEDEV $tcpip_process, &-> CPU cpunum, ALTCPU altcpunum, &-> TYPE (63,0), RSIZE 3, &-> SRCIPADDR src_ipaddr, SRCIPPORT src_ipport, &-> DESTIPADDR dest_ipaddr, DESTIPPORT dest_ipport, &-> NEXTSYS sysnum

4. Start the Expand-over-IP line-handler process:

-> START DEVICE $zzwan.#sline

5. Exit SCF:

-> EXIT

Table F-1. SCF ADD DEVICE Command WorksheetField Valuetcpip_process ____________________ (Step 3 on page F-14)

cpunum ____________________ (Step 4 on page F-14)

altcpunum ____________________ (Step 4 on page F-14

src_ipaddr ____________________ (Step 5 on page F-14)

src_ipport ____________________ (Step 7 on page F-15)

dest_ipaddr ____________________ (Step 7 on page F-17)

dest_ipport ____________________ (Step 9 on page F-17)

sysnum This is the system number of the NonStop K-series server that will be connected to the other end of the line. NonStop S-Series system numbers can be displayed using the SCF INFO PROCESS $NCP, LINESET command. However, you cannot display the system number for a system before the line has been configured. NonStop K-series system numbers are defined in the CONFTEXT file.



4. On the NonStop K-Series Server

4a. Configure and Start an Expand-Over-IP Line-Handler Process 1. Return to the TACL prompt at the NonStop K-series server.

2. Start COUP:

> COUP

3. Determine the name of a dummy controller that the Expand-over-IP line-handler process can use. To list all the dummy controllers with product number 6999 on the NonStop K-series server:

1) INFO CONTROLLER *, PRODUCT 6999

Example F-8 shows a COUP INFO CONTROLLER display.

The dummy controller must have two unit numbers available, one for writing and one for reading data. List the unit numbers configured for a particular controller:

2) INFO DEVICE *, CONTROLLERNAME dummy_name

Example F-9 shows a COUP INFO DEVICE command. Configured unit numbers appear in the UNITS field.

Choose two valid, unconfigured unit numbers. The first must be even, and the second must be odd.

• The 6999 dummy controller has unit numbers in the range 0 through 7.• The 6997 dummy controller has unit numbers in the range 0 through 255. • The 6998 dummy controller has unit numbers in the range 0 through 63.

Note. Dummy controllers can also have product numbers of 6997 or 6998.

Example F-8. COUP INFO CONTROLLER Display

NAME PRODUCT ADDRESS/CPU ADDRESS/CPU FLAGS

DUMMY0 6999 0-%300/01 0-%300/00DUMMYC 6999 0-%300/04 0-%300/05DUMMYD 6999 0-%330/03 0-%330/00DUMMYE 6999 0-%300/06 0-%300/07DUMMYF 6999 0-%310/07 0-%310/06

Example F-9. COUP INFO DEVICE Display

2) info device *, controllername dummye

NAME PRODUCT/MACRO CONTROLLERNAME UNITS FLAGS

$FXPRU NETCLUSTER DUMMYE 00,01 S



4. In Table F-2, COUP Worksheet:

a. The dummy controller name appears in the NAME field of the COUP INFO CONTROLLER display. Record the name in the dummy_name field.

b. Record the write and read unit numbers you want to use in the write_unit and read_unit fields.

5. Add the Expand-over-IP line-handler process to the system using the values you record in Step 4. Fields that must be replaced by values you record in the worksheet appear here in boldface italics.

3) ASSUME DEVICE4) SET MACRO NETIP5) SET CONTROLLERNAME dummy_name6) SET SUBTYPE 07) SET UNIT (write_unit,read_unit)8) SET RSIZE 39) SET DESTIPADDR dest_ipaddr10) SET DESTIPPORT dest_ipport11) SET ASSOCIATEDEV $tcpip_process12) SET NAME #qio13) SET SRCIPADDR src_ipaddr14) SET SRCIPPORT src_ipport15) SET NEXTSYS sysnum16) ADD $kline

6. Start the Expand-over-IP line-handler process:17) START $kline

7. Exit COUP:18) EXIT

Table F-2. COUP Worksheet Field Valuedummy_name ______________________ (Step a on page F-20)

write_unit ______________________ (Step b on page F-20)

read_unit ______________________ (Step b on page F-20

dest_ipaddr ______________________ (Step 5 on page F-14)

dest_ipport ______________________ (Step 7 on page F-15)

tcpip_process ______________________ (Step 5 on page F-16)

cpunum ______________________ (Step 6 on page F-17)

altcpunum ______________________ (Step 6 on page F-17)

src_ipaddr ______________________ (Step 7 on page F-17)

src_ipport ______________________ (Step 9 on page F-17)

sysnum The system number of the server to be connected to the other end of the line. Display system numbers with SCF INFO PROCESS $NCP, LINESET.


FastPath Tasks: Optional 5. On Either NonStop Server

5. On Either NonStop Server

5a. Start the Expand-Over-IP Line Start the Expand-over-IP line from either the NonStop S-series server or the NonStop K-series server:

1. Start SCF at the TACL prompt:

-> SCF

2. Enter one of the following commands at the SCF prompt:

• On the NonStop S-series server:

-> START LINE $sline

• On the NonStop K-series server:

-> START LINE $kline

3. Exit SCF:

-> EXIT


FastPath Tasks: Optional 7. Install Software

7. Install SoftwareThis section explains how to install software with the Distributed Systems Management/Software Configuration Manager (DSM/SCM), and how to install a software product revision (SPR) from tape.

The SPR installation instructions assume that the installation does not require a system load or SP firmware update.

Topic PageConfiguring Software With DSM/SCM F-23

1. Receive New Software Into Archive F-23

2. Create Software Revision F-23

3. Build and Apply New Configuration Revision F-24

4. Activate New Software on Target System F-24

Installing a Software Product Revision (SPR) F-25

1. Save Current System Configuration Database F-25

2. Log On to DSM/SCM F-26

3. Receive SPR Into Archive F-26

4. Create New Software Revision F-27

5. Build and Apply Configuration Revision F-27

6. Activate Software F-27


FastPath Tasks: Optional Configuring Software With DSM/SCM

Configuring Software With DSM/SCMThis subsection summarizes the general procedure for configuring new software on a target. For more information on this process, see the DSM/SCM User’s Guide.

1. Receive New Software Into ArchiveWhen you receive a SUT or SPR, you use DSM/SCM to receive its product files. Products received into DSM/SCM are stored as software inputs in the DSM/SCM archive, from which you can later use them to update the software configuration of your system.

2. Create Software RevisionA software revision is a list of products in the DSM/SCM archive that are used together to update the software configuration of a system. After you have received the products you need into the DSM/SCM archive, use DSM/SCM to create a software revision:

1. Review the softdocs and RVU documents for the products to determine if any conflicts might arise. These documents describe new features, corrected problems, remaining known problems, and other product information.

2. Create a new software revision by designating the specific products in the DSM/SCM archive that will be installed on the target system.

To create a new revision:

a. Open the current revision of the software.

b. Modify the current revision by copying new product versions or SPRs from various software inputs in the DSM/SCM archive.

Task Page1. Receive New Software Into Archive F-23

2. Create Software Revision F-23

3. Build and Apply New Configuration Revision F-24

4. Activate New Software on Target System F-24


FastPath Tasks: Optional Configuring Software With DSM/SCM

3. Build and Apply New Configuration RevisionA new configuration revision is the package that DSM/SCM builds to transfer the products designated in a software revision from the DSM/SCM archive to the target system. After the configuration revision is built and transferred to the target system, it is applied to the target system, which places the product files on the system so they are ready for activation. Often the Build and Apply requests can be executed together in a few steps:

1. Perform a Build, in which you merge the distribution files into executable or usable formats. If necessary, include a new operating system image produced by SYSGEN.

2. Transfer the files to the target system. If the host and target are connected through a network, this transfer can occur automatically.

3. Perform an Apply, which places the merged files in target subvolumes (TSVs) on the target systems.

4. Activate New Software on Target SystemOnce a new configuration revision has been applied to a system, it can be activated. The activation procedure varies depending on the system and the products involved, but includes these steps:

1. Send a snapshot of the target system back to the host system database. This snapshot is then received into the host database, ensuring that the host system has an accurate record of the current software configuration on the target system.

2. Run ZPHIRNM to rename the temporary file names to their actual names. To minimize downtime for your applications, product files are placed on a target system using temporary file names so they do not interfere with any existing versions of the software.

3. Activate the new software on the target system. This task can involve a variety of steps including updating firmware, loading the system, and starting and stopping applications at certain times.


FastPath Tasks: Optional Installing a Software Product Revision (SPR)

Installing a Software Product Revision (SPR)

1. Save Current System Configuration Database1. At the TACL prompt, run SCF:

-> SCF

2. List saved configuration files:


3. Save the current system configuration using a unique file name:


where xx.yy is a number in the range 0.0 through 99.99. The following message appears when the configuration has been saved:

The configuration file $SYSTEM.ZSYSCONF.CONFxxyy has been created.

4. If you specify an existing configuration file CONFxxyy, SCF asks if you want to replace it. If you do not want to replace it, you must repeat the SAVE command with a different value for xx.yy.

Task Page1. Save Current System Configuration Database F-25

2. Log On to DSM/SCM F-26

3. Receive SPR Into Archive F-26

4. Create New Software Revision F-27

5. Build and Apply Configuration Revision F-27

6. Activate Software F-27



2. Log On to DSM/SCM1. Exit SCF.

2. To determine the current SYSnn, enter at the TACL prompt:

> status 0,0

Or use the SYSINFO command, which returns:

System nameEXPAND node numberCurrent SYSnnSystem numberSoftware RVU ID

3. Record this SYSnn in case you must back out a revision later.

4. If the TMF subsystem is not already running, start it:

> TMFCOM START TMF

5. If DSM/SCM is not already running, start it:

> VOLUME $DSMSCM.ZDSMSCM> RUN STARTSCM

6. Log on to the Planner Interface with the super ID.

The Planner Interface displays Software in Archive and Configuration Revisions.

3. Receive SPR Into ArchiveThe Software in Archive window lists the software currently in the DSM/SCM archive.

1. In the Software in Archive window, click Receive software.

The Receive Software Request dialog box appears. DSM/SCM assigns the SPR name. The default is Determine from incoming data. For multiple SPRs, DSM/SCM uses the name of the first selected SPR.

2. In the Receive Software Request dialog box:

a. Click Input Source.b. In the Request Source Options dialog box, select Tape drive.c. Select a tape from the scrollable list.d. Click OK.

3. To submit the request, in the Receive Software Request dialog box, click OK.

4. Check the status of the request in the status window. DSM/SCM updates this window regularly. Wait until the window indicates that the request has completed.

5. In the Window menu, click Refresh.

The Software in Archive window is updated to show the newly received SPR.



4. Create New Software Revision1. In the Configuration Revisions window, select the configuration revision to be

updated.

2. Click New software revision.

A New Software Revision window appears, showing the products in the last software revision that was built for the target.

3. In the New Software Revision window, edit the revision notes for the new revision:

a. Click Edit Revision Notes. b. In the Revision Notes box, add a description of the changes.c. Click OK.

4. In the Software in Archive window:

a. Select the SPR. b. To add the SPR to the new revision, click Copy.

5. When the Confirmation dialog box appears, click Continue.

5. Build and Apply Configuration Revision1. In New Software Revision window, click Build/Apply.

DSM/SCM displays the Build/Apply Request dialog box, which appears grayed out for several minutes while DSM/SCM assembles the build information.

DSM/SCM assigns a name to the Build/Apply request.

2. In the Build/Apply Request dialog box:

a. Use the default values for the following options:

• Output options• Target subvolume (TSV) locations• SYSGEN options• Include only changed files in the activation package

b. In the Activation SYSnn box, specify the SYS00 subvolume name.

c. Click Edit instructions.

d. Add any necessary instructions to the instructions provided by DSM/SCM.

e. Click OK.



f. To schedule a time for the Build/Apply request to run, click Scheduling...

a. In the Request Scheduling Options dialog box, enter a time for the Build/Apply request to run.

To avoid disrupting other system activity, you can schedule the Build to run at night (based on the time on the host system), and the Apply to run immediately after the Build.

b. Click OK.

g. To submit the Build request, click OK.

DSM/SCM runs the Build and Apply requests as scheduled. A status window opens and is updated regularly. The activation package is created, and the new software is placed on the system’s subvolumes. When the Apply request is completed, a snapshot is automatically created and returned to the host.

6. Activate Software1. Print the operator instructions:

a. Log on to the Target Interface (ZPHITI) by using the super ID.

b. Select 3 (Perform target activities) from the main menu. Press F1.

c. In the list of targets, enter the number for the target (DEFAULT) on which the new software was applied. Press F1.

d. In the Target Menu - Select Action screen, select 3 (Review operator instructions for the last apply completed). Press F1.

e. Print the displayed operator instructions.

f. Verify the output location, and then press F9.

g. Press Shift-F16 to exit the Target Interface.

2. Follow the operator instructions to activate the new software.

The following steps summarize a set of standard instructions if a system load and SYSGEN are not required. However, operator instructions vary depending on the new software. Use the instructions that come with your software.

a. Stop all applications, including DSM/SCM.

To stop DSM/SCM and TMF, enter at a TACL prompt:

> VOLUME $DSMSCM.ZDSMSCM> RUN STOPSCM> TMFCOM STOP TMF



b. Run ZPHIRNM:

1. Start ZPHIRNM:

> RUN ZPHIRNM $SYSTEM.SYSnn

The following prompt appears:

Do you want to use a log file with this session? (Y/N)

2. Enter Y and press Enter. The following prompt appears:

You may use any file for logging. If you request to use a disk file that doesn’t exist, it will be created as an entry-sequenced file.

Please enter a filename:

3. Enter a disk file name. The following message appears:

Log file, filename, was successfully created.

ZPHIRNM then renames the applied files. If ZPHIRNM notifies you of any errors, correct them and run ZPHIRNM again.

ZPHIRNM must run without errors to complete the software activation. ZPHIRNM issues an EMS message when it has successfully completed.

c. Restart your applications:

> TMFCOM START TMF> RUN STARTSC




Safety and ComplianceSafety Information

Safety information, in several languages, is located in Important Safety Information, part number 296382-025. This booklet is delivered with new NonStop NS-series servers and can be accessed in NTL. Additional safety information for NonStop S-series servers starts on page 6.

Regulatory Compliance StatementsThe following warning and regulatory compliance statements apply to the products documented by this manual.

FCC ComplianceThis equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

Any changes or modifications not expressly approved by Hewlett-Packard Computer Corporation could void the user’s authority to operate this equipment.

Canadian ComplianceThis class A digital apparatus meets all the requirements of the Canadian Interference-Causing Equipment Regulations.

Cet appareil numérique de la classe A respecte toutes les exigences du Règelment sur le matériel brouilleur du Canada.

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001Statements-1

Safety and Compliance Regulatory Compliance Statements

Korea MIC Compliance

Taiwan (BSMI) Compliance

Japan (VCCI) Compliance

This is a Class A product based on the standard or the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case the user may be required to take corrective actions.



European Union NoticeProducts with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.

Compliance with these directives implies conformity to the following European Norms (the equivalent international standards are in parenthesis):

• EN55022 (CISPR 22)—Electromagnetic Interference

• EN55024 (IEC61000-4-2, 3, 4, 5, 6, 8, 11)—Electromagnetic Immunity

• EN61000-3-2 (IEC61000-3-2)—Power Line Harmonics

• EN61000-3-3 (IEC61000-3-3)—Power Line Flicker

• EN60950 (IEC950)—Product Safety

Laser ComplianceThis product may be provided with an optical storage device (that is, CD or DVD drive) and/or fiber optic transceiver. Each of these devices contains a laser that is classified as a Class 1 Laser Product in accordance with US FDA regulations and the IEC 60825-1. The product does not emit hazardous laser radiation.

The Center for Devices and Radiological Health (CDRH) of the U.S. Food and Drug Administration implemented regulations for laser products on August 2, 1976. These regulations apply to laser products manufactured from August 1, 1976. Compliance is mandatory for products marketed in the Unites States.

WARNING: Use the controls or adjustments or performance of procedures other than those specified herein or in the laser product’s installation guide may result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation:

• Do not try to open the module enclosure. There are no user-serviceable components inside.

• Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein.

• Allow only HP Authorized Service technicians to repair the module.



Declares under our sole responsibility that the following product

Conforms to the following normative European and International Standards.

Following the provisions of the normative European Council Directives: EMC Directive 89/336/EEC (including amendments) Low Voltage Directive 73/23/EEC (amended by 93/68/EEC)

Supplementary Information:

Product conformance to cited product specifications is based on sample (type) testing, evaluation, or assessment at Hewlett Packard’s compliance laboratories in Cupertino, California or at accredited laboratories accepted by European Union Notified and Competent Bodies.

DECLARATION OF CONFORMITY

Supplier Name: HP COMPUTER CORPORATION

Supplier Address: HP Computer Corporation, NonStop Enterprise Division10333 Vallco ParkwayCupertino, CA 95014USA

Represented in the EU By:Hewlett Packard EMEA GmbHP.O. Box 81 02 4481902 MunichGermany

Product Name: NonStop S-series serverRegulatory Model CPTOF-0301Product Model No: S88000, S86000, S76000, S7600, S74000, S7400, S78000, S7800

Product Safety: EN60950:2003 (IEC 60950-1 1st Edition)

Electromagnetic EN 55022:1998 Radiated and Conducted EmissionCompatibility: EN 61000-3-2:2000 Harmonic Current Emission

EN 61000-3-3 +A1:2001 Voltage Fluctuation and FlickerEN 55024:1998 EMC Immunity

Safety: Protection Class I, Pollution Degree IIEmissions: EMC Class AYear Assessed/First Production: 2004

Charles DenningManager, Hardware Product AssuranceNonStop Enterprise DivisionCupertino, California



Declares under our sole responsibility that the following product

Conforms to the following normative European and International Standards.

Following the provisions of the normative European Council Directives: EMC Directive 89/336/EEC (including amendments) Low Voltage Directive 73/23/EEC (amended by 93/68/EEC)

Supplementary Information:

Product conformance to cited product specifications is based on sample (type) testing, evaluation, or assessment at Hewlett Packard’s compliance laboratories in Cupertino, California or at accredited laboratories accepted by European Union Notified and Competent Bodies.

DECLARATION OF CONFORMITY

Supplier Name: HP COMPUTER CORPORATION

Supplier Address: HP Computer Corporation, NonStop Enterprise Division10333 Vallco ParkwayCupertino, CA 95014USA

Represented in the EU By:Hewlett Packard EMEA GmbHP.O. Box 81 02 4481902 MunichGermany

Product Name: NonStop Modular SystemRegulatory Model CPTOF-0430 (IOAM), CPTOF-0431 (Rack system with PDU)Product Model No: M8360-1(IOAM), M8320 (Rack system with PDU)

Product Safety: EN 60950-1/IEC 60950-1:2001

Electromagnetic EN 55022:1998, CISPR22:1997 Radiated and Conducted EmissionCompatibility: EN 61000-3-2/IEC61000-3-2:2000 Harmonic Current Emission

EN 61000-3-3/A1, IEC61000-3-3/A1:2001 Voltage Fluctuation and FlickerEN 55024:1998 EMC Immunity

Safety: Protection Class I, Pollution Degree IIEmissions: EMC Class AYear Assessed/First Production: 2004

Charles DenningManager, Hardware Product AssuranceNonStop Enterprise DivisionCupertino, California


Safety and Compliance Important Safety Information For PDU (PowerDistribution Unit)

Important Safety Information For PDU (Power Distribution Unit)

Retain and follow all product safety and operating instructions. Observe all warnings on the product and in the operating instructions. To reduce the risk of bodily injury, electric shock, fire, and damage to the equipment, observe all precautions included in this guide.

GENERAL PRECAUTIONSTo reduce the risk of electric shock and/or equipment damage when servicing PDU: The routine maintenance and service of PDU must be performed by individuals who are knowledgeable about the procedures, precautions, and hazards associated with AC power products. It should only be performed by a licensed electrician in accordance with National Electrical Code (NFPA70 Article 310) in North America and national wiring regulations.

Do not attempt to make any modifications to PDU assembly. Improper repairs or modifications can create a safety hazard.

Verify that the AC power supply branch circuit that provides power to the rack is not overloaded. This will reduce the risk of personal injury, fire, or damage to the equipment. The total rack load should not exceed 80 percent of the branch circuit rating. Consult the electrical authority having jurisdiction over your facility for installation requirements.

If the product sustains damage requiring service, disconnect the product from the AC electrical outlet and refer servicing to a HP authorized service provider. Examples of damage requiring service include:

• The power cord, extension cord or plug has been damaged.

• Liquid has been spilled on the product.

• The product has been exposed to rain or water.

To reduce the risk of electric shock or damage to the equipment when maintaining or servicing PDU, observe the following precautions:

• Disconnect all power supply cords from the source. Remove all watches, rings, or loose jewelry when working in hot-plug areas of an energized system.

• Never use the product in a wet location. Avoid inserting foreign objects through openings in the product.


Safety and Compliance SAFETY CAUTION

SAFETY CAUTIONThe following icon or caution statements may be placed on equipment to indicate the presence of potentially hazardous conditions:

DOUBLE POLE FUSINGCAUTION: DOUBLE-POLE /NEUTRAL FUSING.

ATTENTION: DOUBLE POLE/FUSIBLE SUR LE NEUTRE

NOT FOR EXTERNAL USECAUTION: NOT FOR EXTERNAL USE. ALL RECEPTACLES ARE FOR INTERNAL USE ONLY.

ATTENTION: NE PAS UTILISER A L’EXTERIEUR DE L’EQUIPEMENT

IMPORTANT: TOUS LES RECIPIENTS SONT DESTINES UNIQUEMENT A UN USAGE INTERNE.

VORSICHT: ALLE STECKDOSEN DIENEN NUR DEM INTERNEN GEBRAUCH.

DUAL POWER CORDS CAUTION: THIS UNIT HAS MORE THAN ONE POWER SUPPLY CORD. DISCONNECT ALL POWER SUPPLY CORDS TO COMPLETELY REMOVE POWER FROM THIS UNIT."

"ATTENTION: CET APPAREIL COMPORTE PLUS D'UN CORDON D'ALIMENTATION. DÉBRANCHER TOUS LES CORDONS D'ALIMENTATION AFIN DE COUPER COMPLÈTEMENT L'ALIMENTATION DE CET ÉQUIPEMENT".

VOR DER WARTUNG BITTE ALLE HAUPTZKABEL AUS DER STRECKDOSE ZIEHEN

Any surface or area of the equipment marked with these symbols indicates the presence of electric shock hazards. The enclosed area contains no operator-serviceable parts.WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure.


Safety and Compliance Consumer Safety Statements

HIGH LEAKAGE CURRENTTo reduce the risk of electric shock due to high leakage currents, a reliable grounded (earthed) connection should be checked before servicing power distribution unit.

Observe the following limits when connecting the product to AC power distribution devices: For PDU that have attached AC power cords or are directly wired to the building power, the total combined leakage current should not exceed 5 percent of the rated input current for the device.

HIGH LEAKAGE CURRENT, EARTH CONNECTION ESSENTIAL BEFORE CONNECTING SUPPLY”

“HOHER ABLEITSTROM. VOR INBETRIEBNAHME ERDUNGSVERBINDUNG HERSTELLEN”

“COURANT DE FUITE E’LEVE’. RACCORDEMENT A LA TERRE INDISPENSABLE AVANT LE RACCORDEMENT AU RESEAU”

FUSE REPLACEMENTCAUTION – For continued protection Against Risk of Fire, Replace Only with Same Fuse Type TCF15, Rated 600V~, 15A. Disconnect the interior AC power cord from the PDU to the module before changing the fuse.

Consumer Safety StatementsCustomer Installation and Servicing of Equipment

The following statements pertain to safety issues regarding customer installation and servicing of equipment described in this manual.

• Keep door closed for normal operation.

• The equipment must be installed near the receptacles for the power cords, and the receptacles must be easily accessible to the user.

WARNING. Do not touch the DC power connector on the NonStop S7400, S7600, or Sxx000 PMF CRU after you have unplugged the DC power cable from the CRU. It is possible to incur a severe energy hazard for as long as fifteen (15) seconds after unplugging the cable. You can make sure the CRU is safe to remove by testing (by using a volt meter) before touching the pins on the DC power connector.


Safety and Compliance Applicability of Procedures, Instructions, andExamples

Applicability of Procedures, Instructions, and Examples

WARNING. The procedures and instructions and the examples of procedures and instructions found in this manual apply only to the system enclosures and components found in NonStop S-series servers which are described in the NonStop S-series server documentation. Do not attempt to use these instructions with any other NonStop system equipment. You can determine that your system is a NonStop S-series server by reading the label that appears inside each system enclosure on the CRU in slot 50 or 55. The label includes the product number, 195x, 196x, 197x, or 198x. Read the label before proceeding with any procedure or instruction found in this manual.


Safety and Compliance Consignes de sécurité à l'intention du client

Consignes de sécurité à l'intention du clientInstallation et entretien du système par le client

Les consignes de sécurité qui suivent concernent l'installation et l'entretien par le client du système décrit dans le présent manuel.

• Garder la porte fermée pendant le fonctionnement normal du système.

• Installer le système à proximité des prises de courant nécessaires à son branchement. Ces prises doivent être faciles d'accès.

Applicabilité des procédures, des directives et des exemples

MISE EN GARDE. Ne pas toucher au connecteur d'alimentation C.C. de l'unité PMF remplaçable par le client du NonStop S7400/S7600/Sxx000 après avoir débranché le cordon d'alimentation C.C. de cette unité. Des risques de chocs électriques dangereux peuvent subsister pendant quinze (15) secondes après le débranchement du câble. Lors de la dépose de l'unité, on pourra confirmer l'absence de danger avec un voltmètre avant de toucher les broches du connecteur d'alimentation C.C.

MISE EN GARDE. Les procédures et directives ainsi que les exemples y afférents contenus dans le présent manuel concernent uniquement les boîtiers et pièces des serveurs NonStop série S décrits dans la documentation connexe. Elles ne sont applicables à aucun autre système NonStop. Pour savoir si votre serveur est un NonStop de la série S, consultez l'étiquette figurant à l'intérieur du boîtier du système sur l'unité remplaçable par le client installée dans l'emplacement 50 ou 55. Cette étiquette indique le nombre de produit, 195x, 196x, 197x, ou 198x. Consultez cette étiquette avant d'exécuter l'une quelconque des procédures ou directives prescrites dans le présent manuel.


Safety and Compliance Verbraucher-Sicherheitsangaben

Verbraucher-SicherheitsangabenGeräteinstallation und -wartung durch den Kunden

Die folgenden Angaben betreffen Sicherheitsfragen in Hinsicht auf die Geräteinstallation und -wartung durch den Kunden, wie sie in diesem Handbuch beschrieben werden.

• Tür für normalen Betrieb geschlossen lassen.

• Die Geräte müssen in der Nähe der Steckdosen für die Netzanschlußkabel installiert werden, und die Steckdosen müssen für den Benutzer leicht zugänglich sein.

Anwendbarkeit von Verfahren, Anleitungen und Beispielen

WARNUNG. Den Gleichstrom-Steckverbinder an der vom Kunden austauschbaren PMF-Einheit des NonStop S7400/S7600/Sxx000 nicht berühren, nachdem das Gleichstromkabel von der vom Kunden austauschbaren Einheit abgezogen wurde. Bis zu fünfzehn (15) Sekunden nach Abziehen des Kabels besteht starke Elektroschockgefahr. Durch Prüfen (mit einem Spannungsmesser) läßt sich vor Berührung der Stifte am Gleichstrom-Steckverbinder feststellen, ob die vom Kunden austauschbare Einheit gefahrlos entfernt werden kann.

WARNUNG. Die in diesem Handbuch enthaltenen Verfahren und Anleitungen und die Beispiele von Verfahren und Anleitungen gelten nur für die in den NonStop-S-Serie-Servern vorgefundenen Systemgehäuse und Komponenten, die in der Dokumentation der NonStop-S-Serie-Server beschrieben werden. Versuchen Sie nicht, diese Anleitungen mit anderen NonStop-System-Geräten zu benutzen. Sie können feststellen, daß Ihr System ein NonStop-S-Serie-Server ist, indem Sie den Aufkleber lesen, der sich im Innern eines jeden Systemgehäuses befindet in der vom Kunden austauschbaren Einheit in Steckplatz 50 oder 55. Der Aufkleber soll die Produktnummer 195x, 196x, 197x, oder 198x angeben. Lesen Sie den Aufkleber, bevor Sie mit irgendeiner der in diesem Handbuch enthaltenen Verfahren oder Anleitungen fortfahren.


Safety and Compliance Declaraciones sobre la seguridad del consumidor

Declaraciones sobre la seguridad del consumidorInstalación y servicio al equipo por el consumidor

Las siguientes declaraciones tienen que ver con aspectos de seguridad relacionados con la instalación y servicio al equipo por el consumidor, y que se describen en este manual.

• Mantenga la puerta cerrada durante la operación normal del equipo.

• El equipo tiene que estar instalado cerca de los receptáculos de los cordones de alimentación eléctrica, y dichos receptáculos tienen que ser de fácil acceso para el usuario.

ForbrugersikkerhedsmeddelelserInstallation og service af udstyr der udføres af kunden

De følgende meddelelser vedrører sikkerheden angående installation og service af udstyr, der udføres af kunden, som beskrives i denne brugerhåndbog.

• Hold lugen lukket under normal drift.

• Udstyret skal installeres i nærheden af stikkontakterne til netledningerne, og stikkontakterne skal være let tilgængelige for brugeren.

ADVERTENCIA. No toque el conector de alimentación de corriente directa en la unidad reemplazable por el cliente NonStop S7400/S7600/Sxx000 PMF después de haber desenchufado el cable de alimentación de corriente directa de dicha unidad. Es posible incurrir en un peligro grave debido a la energía eléctrica hasta por unos quince (15) segundos después de haber desenchufado el cable. Usted puede asegurarse de que la unidad reemplazable por el cliente ya se pueda quitar sin problema alguno probándola (con un voltímetro) antes de tocar las clavijas del conector de alimentación de corriente directa.

ADVARSEL! Berør ikke jævnstrøms forbindelsesstikket på NonStop S7400/S7600/Sxx000 PMF-enheden, der kan udskiftes af kunden, når du har afbrudt jævnstrøms netkablet fra enheden, der kan udskiftes af kunden. Der er risiko for alvorligt stød i op til 15 sekunder efter, at kablet afbrydes. Du kan sikre dig, at det er sikkert at fjerne enheden, der kan udskiftes af kunden, ved at teste den (med et voltmeter), før du berører stifterne på jævnstrøms forbindelsesstikket.


Safety and Compliance Veiligheidsinstructies voor de consument

Veiligheidsinstructies voor de consumentInstallatie en onderhoud van apparatuur door de klant

De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de klant van de in deze handleiding beschreven apparatuur.

• Houd bij normaal bedrijf de deur gesloten.

• De apparatuur moet nabij contactdozen voor stroomkabels worden geïnstalleerd en de contactdozen moeten voor de gebruiker gemakkelijk bereikbaar zijn.

Käyttöturvaa koskevia huomautuksiaAsiakkaan suorittama laiteasennus ja huolto

Seuraavat huomautukset koskevat turvallisuusnäkökohtia, jotka asiakkaan täytyy ottaa huomioon tässä käsikirjassa kuvattuja laiteasennuksia ja huoltotoimenpiteitä suoritettaessa.

• Kansi täytyy pitää suljettuna normaalin käytön aikana.

• Laitteisto täytyy asentaa lähelle virtapistokkeita, ja pistokkeiden tulee olla helposti käytettävissä.

WAARSCHUWING. Raak de gelijkstroomconnector op het NonStop S7400/S7600/Sxx000 PMF apparaat dat door de klant kan worden vervangen, niet aan nadat de gelijkstroomkabel is losgekoppeld van het door de klant vervangbare apparaat. Een ernstig energierisico kan nog wel vijftien (15) seconden nadat de kabel is losgekoppeld, aanwezig zijn. Controleer of het door de klant vervangbare apparaat veilig kan worden verwijderd door (met een spanningsmeter) een test uit te voeren voordat u de pennen op de gelijkstroomconnector aanraakt.

VAARA. Älä kosketa NonStop S7400/S7600/Sxx000 PMF vaihto-osan virtaliitintä heti sen jälkeen kun olet irrottanut vaihto-osan tasavirtakaapelin. Vaarallista jännitettä voi olla jäljellä vielä viidentoista (15) sekunnin kuluttua kaapelin irrottamisesta. Jännitemittarilla on mahdollista testata, onko vaihto-osan tasavirtaliittimen pistokkeiden koskettaminen turvallista.


Safety and Compliance Veiligheidsinstructies voor de consument

Veiligheidsinstructies voor de consumentInstallatie en onderhoud van apparatuur door de klant

De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de klant van de in deze handleiding beschreven apparatuur.

• Houd bij normaal bedrijf de deur gesloten.

• De apparatuur moet nabij contactdozen voor stroomkabels worden geïnstalleerd en de contactdozen moeten voor de gebruiker gemakkelijk bereikbaar zijn.

Misure precauzionali per i clienteInstallazione e manutenzione del sistema da parte del cliente

Le seguenti misure precauzionali riguardano l’installazione e la manutenzione da parte del cliente del sistema descritto nel presente manuale.

• Mantenere la porta chiusa durante il funzionamento normale del sistema.

• Il sistema deve essere installato vicino alle prese di corrente che saranno usate per il collegamento alla rete. Tali prese devono essere facilmente accessibili.

WAARSCHUWING. Raak de gelijkstroomconnector op het NonStop S7400/S7600/Sxx000 PMF apparaat dat door de klant kan worden vervangen, niet aan nadat de gelijkstroomkabel is losgekoppeld van het door de klant vervangbare apparaat. Een ernstig energierisico kan nog wel vijftien (15) seconden nadat de kabel is losgekoppeld, aanwezig zijn. Controleer of het door de klant vervangbare apparaat veilig kan worden verwijderd door (met een spanningsmeter) een test uit te voeren voordat u de pennen op de gelijkstroomconnector aanraakt.

ATTENZIONE. Non toccare il connettore di corrente continua sull’unità sostituibile dal cliente NonStop S7400/S7600/Sxx000 PMF dopo aver disinserito il cavo di corrente continua dall’unità stessa. Un serio rischio elettrico può perdurare fino a 15 secondi dopo aver disinserito il cavo. È possibile controllare con un voltmetro che l’unità sostituibile dal cliente possa essere rimossa con sicurezza prima di toccare i piedini del connettore di corrente continua.


Safety and Compliance Informações de segurança para os consumidores

Informações de segurança para os consumidoresInstalação e manutenção do equipamento pelo cliente

As seguintes informações se referem a questões de segurança relacionadas à instalação e manutenção, pelo cliente, do equipamento descrito neste manual.

• Para garantir o funcionamento normal, mantenha a porta fechada.

• O equipamento deve ser instalado próximo das tomadas, e o usuário deve ter acesso fácil às tomadas.

Meddelanden beträffande konsumentsäkerhetKundutförd installation och service

De följande meddelandena beskriver säkerhetsföreskrifter för kundutförd installation och service av utrustning som beskrivs i denna manual:

• Dörren skall vara stängd under normal drift.

• Utrustningen bör monters nära eluttag för nätsladdar. Nätsladdarna måste vara lättillgängliga.

AVISO. Não toque no conector de alimentação DC da Unidade Substituível pelo Cliente (USC) NonStop S7400/S7600/Sxx000 PMF logo após ter desligado o cabo de alimentação DC da USC. Existe a possibilidade de ocorrer um acidente elétrico sério até quinze (15) segundos após o desligamento do cabo. Assegure-se de que é seguro remover a USC testando-a (ou usando um medidor de voltagem), antes de tocar nos pinos do conector de alimentação DC.

VARNING! Likströmskontakten som är placerad på NonStop S7400/S7600/Sxx000 PMF-enheten är strömförande upp till femton (15) sekunder efter att elkablen till enheten har blivit urkopplad. Du skyddar dig från strömstötar genom att testa om likströmskontakten fortfarande är strömförande (med hjälp av en voltmätare).


Safety and Compliance Kundutförd installation och service

S7400/S7600/Sxx000

S7400/S7600/Sxx000



S7x000

S7400/S7600/Sxx000




Glossary19-inch rack. A computer rack that accepts 19-inch components in 1-u increments. The 19-

inch racks can differ in depth, rails, and mounting requirements. A 19-inch rack, doors, PDR extention, and optional side panels make up a modular cabinet.

3-phase. Describes a single power source with three output phases (A, B, and C). The phase difference between any two of the three phases is 120 degrees.

3860 ATM 3 ServerNet adapter (ATM3SA). See ATM 3 ServerNet adapter (ATM3SA).

3861 Ethernet 4 ServerNet adapter (E4SA). See Ethernet 4 ServerNet adapter (E4SA).

3862 Token-Ring ServerNet adapter (TRSA). See Token-Ring ServerNet adapter (TRSA).

3863 Fast Ethernet ServerNet adapter (FESA). See Fast Ethernet ServerNet adapter (FESA).

3865 Gigabit Ethernet ServerNet adapter (GESA). See Gigabit Ethernet ServerNet adapter (GESA).

4619 disk drive. An 18-gigabyte, 15,000-rpm, small computer system interface (SCSI) disk drive for HP NonStop™ S-series enclosures. The 4619 disk drive can coexist and operate with lower-capacity or lower-speed drives in the same storage subsystem module.

4637 disk drive. A 36-gigabyte, 10,000-rpm, small computer system interface (SCSI) disk drive for HP NonStop™ S-series enclosures.



6740 ServerNet/FX adapter. See ServerNet/FX adapter.

6742 ServerNet/FX 2 adapter. See ServerNet/FX 2 adapter.

6760 ServerNet device adapter (ServerNet/DA). See ServerNet device adapter (ServerNet/DA).

6761 F-PIC. See fiber-optic plug-in card (F-PIC).

6762 S-PIC. See SCSI plug-in card (S-PIC).

6763 Common Communication ServerNet adapter (CCSA). See Common Communication ServerNet adapter (CCSA).

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001Glossary-1

Glossary 8800 Gigabit Ethernet 4-port ServerNet adapter(G4SA)

8800 Gigabit Ethernet 4-port ServerNet adapter (G4SA). See Gigabit Ethernet 4-port ServerNet adapter (G4SA).

8840 Fibre Channel ServerNet adapter (FCSA). See Fibre Channel ServerNet adapter (FCSA).

A. See ampere (A).

A0CINFO file. A distribution subvolume (DSV) file that contains information about a product and each of its files, including product and file dependencies, how the files are used and where they are placed, and which type of processor the product runs on. Every product and software product revision (SPR) to be managed by Distributed Systems Management/Software Configuration Manager (DSM/SCM) is distributed in a subvolume, and that subvolume must contain the product’s A0CINFO file.

absolute pathname. An Open System Services (OSS) pathname that begins with a slash (/) character and is resolved beginning with the root directory. Contrast with relative pathname.

AC. See alternating current (AC).

accelerate. To speed up emulated execution of a TNS object file by applying the Accelerator for TNS/R system execution before running the object file.

accelerated mode. See TNS accelerated mode.

accelerated object code. The MIPS RISC instructions (in the MIPS region) that result from processing a TNS object file with the Accelerator.

accelerated object file. A TNS object file that, in addition to its TNS instructions (in the TNS region) and symbol information (in the symbol region), has been augmented by the Accelerator with equivalent but faster MIPS RISC instructions (in the MIPS region).

Accelerator. A program optimization tool that processes a TNS object file and produces an accelerated object file that also contains equivalent MIPS RISC instructions (called the MIPS region). TNS object code that is accelerated runs faster on TNS/R processors than TNS object code that is not accelerated.

Accelerator-generated MIPS RISC instructions. See MIPS RISC instructions.

Accelerator-generated RISC instructions. See MIPS RISC instructions.

Accelerator mode. The TNS/R operational environment in which an object file containing MIPS RISC instructions (called the MIPS region) executes. Contrast with TNS/R native mode.

Accelerator region of an object file. The region (called the MIPS region) of an object file that contains MIPS RISC instructions and tables necessary to execute the object file


Glossary access mode

on a TNS/R system in accelerated mode. The Accelerator creates this region. See also accelerated object file.

access mode. The form of file access permitted for a user or process.

ACL. See automatic cartridge loader (ACL).

ACS. See automated cartridge subsystem (ACS).

action. An operation that can be performed on a selected resource.

activation. The operator action of putting software into use after the software has been applied from the activation package to the target system.

activation package. A set of files containing product files, operator instructions, and instructions for applying the software on the target system. It consists of a header file containing the activation instructions and file attributes, multiple data files, Distributed Systems Management/Software Configuration Manager (DSM/SCM) control information, and Event Management Service (EMS) events.

AC transfer switch. A component of an HP NonStop™ Cluster Switch (model 6770) that provides access to dual AC power sources and the ability to switch between the two sources if one fails. The AC transfer switch draws power from its primary power source as long as it is available. If the primary source fails, the AC transfer switch is switched to draw power from the secondary power source.

adapter. See ServerNet adapter.

adapter cable. (1) A cable that connects components that have incompatible electrical interfaces. (2) For the ServerNet wide area network (SWAN) concentrator, one of four types of cable that can connect any of the six 50-pin WAN ports to one of the supported electrical interfaces (RS-232, RS-449, X.21, or V.35).

ADAPTER object type. The Subsystem Control Facility (SCF) object type for all adapters attached to your system.

address space. The memory locations to which a process has access.

ADE. See application development environment (ADE).

adjacent SP. A service processor (SP) that is directly connected through the ServerNet fabrics to the enclosure of a specified SP.

administrator. (1) For an HP NonStop™ system, the person responsible for the installation and configuration of a software subsystem on a NonStop node. Contrast with operator. (2) For an IBM system, the person responsible for the day-to-day monitoring and maintenance tasks associated with a software subsystem on an IBM node. (3) For a UNIX system, the owner of /dev/console. The administrator is responsible for the installation and configuration of all hardware and software within a node.


Glossary ADP

ADP. See Automated Data Processing (ADP).

ALLPROCESSORS paragraph. A required paragraph in the CONFTEXT configuration file that contains attributes defining the HP NonStop™ operating system image for all system processors. The ALLPROCESSORS paragraph follows the optional DEFINES paragraph.

alternate path. A path not enabled as the preferred path. An alternate path can become a primary path when a primary path is disabled.

alternating current (AC). An electric current having a waveform that regularly reverses in positive and negative directions. North American electrical power alternates 60 times/second (60 hertz). European electrical power alternates at 50 hertz. Contrast with direct current (DC).

amperage. Current-carrying capacity, expressed in amperes.

ampere (A). The unit of electrical current or rate of flow of electrons. One volt across one ohm of resistance causes a current flow of one ampere. A flow of one coulomb/second is defined as one ampere of current.

ANSI. The American National Standards Institute.

APE. See Accelerated Program Examiner (APE).

API. See application program interface (API).

appearance side. The side of an HP NonStop™ S-series system enclosure that contains disk customer-replaceable units (CRUs) and power monitor and control unit (PMCU) CRUs that do not require cables. The appearance side always has a short door and panel, or a tall door, that is required for cooling the enclosure. The appearance side is opposite the service side. The appearance-side door is lockable for security purposes. See also service side.

application binary interface (ABI). The conventions used to call functions and access global or external data.

application development environment (ADE). A set of methods and tools that are used throughout the lifecycle of an application project to design, code, and manage that project.

Accelerated Program Examiner (APE). A tool used to browse through TNS object files that have been accelerated by the Accelerator. APE displays MIPS RISC code in addition to TNS code.

application program interface (API). A set of services (such as programming language functions or procedures) that are called by an application program to communicate with other software components. For example, an application program in the form of a client might use an API to communicate with a server program.


Glossary application-specific integrated circuit (ASIC)

application-specific integrated circuit (ASIC). A custom-built integrated circuit (IC) used to perform highly specialized functions.

Apply. The Distributed Systems Management/Software Configuration Manager (DSM/SCM) action of executing the instructions contained in an activation package, such as placing new software on the target system and taking a snapshot of the new target system.

appropriate privileges. In the Open System Services (OSS) environment, an implementation-defined means of associating privileges with a process for function calls or function call options that need special privileges.

archive. 1. A collection of files of a similar type. For example, one archive might contain only Guardian executable files and another might contain only Java servlets or only configuration files. Archives are used for convenience, such as moving similar files between multiple environments (UNIX to PC to Guardian). There are many software utilities for creating archives; the best known is the UNIX ar utility. 2. For DSM/SCM, a set of unstructured files used to collect the software received onto the host system. Files received as input are placed in the DSM/SCM archive, and attributes of the files are stored in the host database. You can use the Archive and Database Maintenance Interface to specify the archive location in the Configuration Manager profile.

Archive and Database Maintenance Interface. A block-mode interface run by a database or system administrator at both the host system and target systems to perform Distributed Systems Management/Software Configuration Manager (DSM/SCM) maintenance functions.

ASCII. American Standard Code for Information Interchange. A single-byte code set that uses only 7 of the 8 bits in a byte to represent each character. The ASCII code set contains the uppercase and lowercase characters of the U.S. English alphabet, some punctuation symbols, the digits 0 through 9, and some symbols and control characters. Because of its limited characters, and because the 8th bit is sometimes used in ASCII programs as a utility bit, the ASCII code set is not appropriate for use in international software.

ASIC. See application-specific integrated circuit (ASIC).

ASSIGN. An HP Tandem Advanced Command Language (TACL) command you can use to associate a file name with a logical file of a program or to assign a physical device to logical entities that an application uses.

assign message. Within Subsystem Control Facility (SCF), a message created by SCF for each ASSIGN command. A new process must request its assign message following receipt of the startup message. All assign messages set by the SCF ASSIGN command, plus the ones read from the HP Tandem Advanced Command Language (TACL) command interpreter, are passed to the new process.

assumed object. The object type or object name specified by a Subsystem Control Facility (SCF) ASSUME command. If an ASSUME command has been used to establish a default object type and fully qualified default object name, and if that object type and


Glossary asynchronous wide area network (AWAN) servers

object name together refer to a valid object, object-spec can be omitted entirely from an SCF command, and the command is applied to the object known as the assumed object.

asynchronous wide area network (AWAN) servers. A local area network (LAN)-based communications device that provides (1) asynchronous connections to terminals, printers, and terminal emulators for HP NonStop servers; (2) remote-access disk operating system (DOS), Windows, and Macintosh platforms; (3) VT-to-6530 protocol conversion; and (4) dial-out connections for LAN-attached DOS, Windows, and Macintosh platforms.

ATM3SA. See ATM 3 ServerNet adapter (ATM3SA).

ATM 3 ServerNet adapter (ATM3SA). A ServerNet adapter that provides access to Asynchronous Transfer Mode (ATM) networks from an HP NonStop™ S-series system enclosure. The 3860 ATM3SA supports the ATM User-Network Interface (UNI) specification over a 155-megabit/second (Mbps) OC-3 Sonet (Synchronous Optical Network) connection.

atomic. Behaving as a single, indivisible operation. For example, an atomic write operation on a file cannot write data that is interleaved with data from another, concurrent write operation on that file.

attachment. A file that contains information that augments the information in an incident report.

attribute. (1) For the Subsystem Control Facility (SCF), a characteristic of an entity. For example, two attributes of a process might be its program file and its user ID. An attribute is sometimes called a modifier. (2) In OSM and TSM client interfaces, a data item associated with a system or cluster resource. All attributes can be viewed, and some can be modified.

audit. A Distributed Systems Management/Software Configuration Manager (DSM/SCM) activity initiated by the operator at a target system that updates the target database with the fingerprints of all the files in a selected set of target subvolumes (TSVs).

authentication attributes. Security attributes of a process that do not change unless a successful reauthentication occurs or the super ID changes them. For Open System Services (OSS) processes, the authentication attributes include the login name, real user ID, real group ID, authentication system (node name), and group list.

authorization attributes. Security attributes of a process that can change through use of functions such as setuid() (or of Guardian procedures such as PROCESS_CREATE_) without reauthentication. For Open System Services (OSS) processes, the authorization attributes include the effective user ID, saved-set user ID, saved-set group ID, user audit flags, and effective user name.


Glossary authorization key

authorization key. A password required for logging on to a modem. If you plan to allow dial-outs to a service provider, you must specify the authorization key of the service provider’s modem during configuration of the OSM or TSM Notification Director.

automated cartridge subsystem (ACS). A type of tape library. Also known as automated cartridge system.

Automated Data Processing (ADP). The term used in the FIPS PUB 94 document to refer to computerized data processing equipment that is installed inside a computer room.

automatic cartridge loader (ACL). A device that stores multiple cartridge tapes and loads them automatically, one at a time, into a tape drive.

automatic configuration. The automatic assignment of magnetic disk attributes to an internal disk drive when it is inserted into a slot. Also known as plug and play.

averaging. A measurement method for determining the average value of alternating voltage and current waveforms. The averaging method involves sampling a waveform and averaging the samples over the period of one cycle.

AWAN. See asynchronous wide area network (AWAN) servers.

AXCEL. The command used to invoke the Accelerator on a TNS/R system.

back-end board (BEB). On some tape drives or disk drive modules, a circuit board that translates fiber-optic signals from a 6760 ServerNet device adapter into small computer system interface (SCSI) commands and information.

background process. In the Open System Services (OSS) environment, a process that belongs to a background process group.

background process group. In the Open System Services (OSS) environment, a process group that is both:

• Not a foreground process group• A member of a session that has a connection with a controlling terminal

backout. The Distributed Systems Management/Software Configuration Manager (DSM/SCM) action of making the last configuration applied to the target system inaccessible and replacing it with the previous configuration.

backplane. A board that has connectors, on one or both sides of the board, into which circuit board assemblies plug. Backplanes are located behind card cages or disk cages.

BACKUP. A utility for the HP NonStop™ servers that creates a backup copy of one or more disk files on magnetic tape. See also RESTORE.

backup processor. A processor running the HP NonStop™ operating system that communicates with the primary processor, allowing the processors to remain


Glossary base computing platform

independent. A component failure in one processor has no effect on any other processor.

base computing platform. The minimum software implementation that is the foundation for the X/Open common applications environment (CAE).

base enclosure. An enclosure that is placed on the floor and can have other enclosures stacked on top of it. A base enclosure is installed on a frame base. Contrast with stackable enclosure.

base profile. In an X/Open compliant system, a minimum set of software components required to create a common applications environment.

battery load. The electrical current drain imposed on a battery.

BEB. See back-end board (BEB).

BIND. A program invoked during system generation that creates TNS object (file code 100) system code files and system library files.

Binder. A programming utility that combines one or more compilation units’ TNS object code files to create an executable TNS object code file for a TNS program or library. Used only with TNS object files.

Binder region. The region of a TNS object file that contains header tables for use by the Binder program.

binding. The operation of collecting, connecting, and relocating code and data blocks from one or more separately compiled TNS object files to produce a target object file.

BIST. Built-in self-test.

bit-synchronous. A type of Open Systems Interconnection (OSI) Layer-2 protocol that uses synchronous transmission but does not require a character code to define terminal and line control sequences.

block. A grouping of one or more system enclosures that an HP NonStop™ S-series system recognizes and supports as one unit. A block can consist of either one processor enclosure, one I/O enclosure, or one processor enclosure with one or more I/O enclosures attached.

blocked signal. A programmatic signal that is currently in the pending signal mask of a process and, when generated, is not delivered to the process because of the signal mask setting. Some signals cannot be blocked.

block special file. In the Open System Services (OSS) environment, a device that is treated as a file for which all input or output must occur in blocks of data. Traditionally, such files are disk or tape devices. Block special files provide access to a device in a


Glossary bond

manner that hides the hardware characteristics of the device. Contrast with character special file.

bond. A reliable connection that ensures the required electrical conductivity between conductive parts that must be electrically connected.

bonded. The mechanical interconnection of conductive parts to maintain a common electrical potential.

bonding. The permanent joining of conductive parts to form a path that ensures electrical continuity and the capacity to safely conduct any current likely to be imposed.

bonding jumper. See main bonding jumper.

boot. A synonym for load. Load is the preferred term used in this and other publications for HP NonStop™ servers. See also millicode.

BOOTP. A protocol for providing initialization information to diskless nodes in an open network.

BOOTPC. See BOOTP client (BOOTPC).

BOOTP client (BOOTPC). A client provided as a Portable Silicon Operating System (pSOS) system product task in the essential firmware on each communications line interface processor (CLIP) in the ServerNet wide area network (SWAN) concentrator. BOOTPC tasks are also provided on the host system as the WANBoot process in the WAN subsystem.

BOOTPD. See BOOTP daemon (BOOTPD).

BOOTP daemon (BOOTPD). The BOOTP server. One BOOTPD runs as a Portable Silicon Operating System (pSOS) system product task in the essential firmware on each communications line interface processor (CLIP) in the ServerNet wide area network (SWAN) concentrator. BOOTPD tasks are also provided on the host system as the WANBoot process in the WAN subsystem.

branch circuit. The circuit conductors located between the equipment receptacles and the final overcurrent device in a power distribution panel (PDP) that protect the circuits.

branded product. A software product that is licensed by X/Open to carry the X/Open or UNIX trademark.

branding process. The activities that lead to the acceptance of a product by X/Open in accordance with its Trade Mark Licence Agreement.

break condition. An event indicator or sequence of data from a terminal or terminal emulator that requests interruption of an application program.


Glossary breakpoint

breakpoint. An object code location at which execution will be suspended so that you can interactively examine and modify the process state. With symbolic debuggers, breakpoints are usually at source line or statement boundaries.

In TNS/R native object code, breakpoints can be at any MIPS RISC instruction within a statement. In a TNS object file that has not been accelerated, breakpoints can be at any TNS instruction location. In a TNS object file that has been accelerated, breakpoints can be only at certain TNS instruction locations (see memory-exact point), not at arbitrary instructions. Some source statement boundaries are not available. However, breakpoints can be placed at any instruction in the accelerated code.

bridge rectifier. A full-wave rectifier with four elements, as in a bridge circuit. Alternating voltage is applied to one pair of opposite junctions, and direct voltage is obtained from the other pair of junctions.

BSD. Berkeley Software Distribution.

built configuration. A configuration revision for which a system image and activation package have been created.

built-in command. In the Open System Services (OSS) environment, a command that is implemented within the /bin/sh file. Some built-in commands are also available as separately executable files.

bypass mechanism. Equipment that permits switching from one power source to another. For example, a bypass mechanism on an uninterruptible power supply (UPS) would switch to an alternative power source (such as a standby power generator or commercial utility source) when maintenance must be performed on the UPS.

byte-synchronous. A type of Open Systems Interconnection (OSI) Layer-2 protocol that uses synchronous transmission techniques and requires a character code to define terminal and line control sequences. Data is always transmitted in a block.

cabinet. The rack, front and back doors, side panels (if any), and PDUs. Cabinets contain enclosures and other system components. A cabinet that can contain multiple enclosures is also called a modular cabinet.

cable channel. A cable management conduit that protects the cables that run between two HP NonStop™ S-series system enclosures in a double-high stack. Each system enclosure has two cable channels running vertically on its service side: one on the left-hand side of the enclosure, and one on the right-hand side of the enclosure.

cable guidepost. A cable management rod that routes cables exiting an HP NonStop™ S-series upper enclosure in a double-high stack to prevent the cables from hanging down in front of the customer-replaceable units (CRUs) in the base enclosure. A cable guidepost extends from the base of each cable channel.

cable support. A piece of cable management hardware that secures system cables. The cable support attaches to the service side of a system enclosure near the bottom of the


Glossary cache

enclosure. Cable ties for securing system cables are threaded through the cable support. The cable support also contains the group and module ID labels and the rear group service light-emitting diode (LED).

cache. See cache memory.

cache memory. Small, fast memory holding recently accessed data designed to speed up subsequent access to the same data. Cache memory is built from faster memory chips than main memory, and it is most often used with processor main memory as well as network data transfer to maintain a local copy of data. Contrast with main memory.

cached bindings. A copy in virtual memory of the data pages containing symbolic references that were rebound when a loadfile was loaded. The cached bindings are associated with a library import characterization that characterizes the set of loadfiles to which the symbols were bound. If the same file is subsequently loaded in an equivalent environment in the same processor, the cached bindings can be reused. See fastLoad.

CAE. See common applications environment (CAE).

canonical form. A standard way of representing TNS machine register values in assigned system registers, at certain synchronization points within accelerated code. Each live 16-bit TNS register value resides in its home system register, right-justified and sign-extended to fill the 32-bit or 64-bit register. Register values that have no future uses are considered dead; their home system registers might contain undefined values.

The TNS machine state must be in canonical form at all register-exact points where the program might switch to or from interpreted execution mode. At all other program locations, Accelerator optimizations might cause TNS register values to be carried in various noncanonical forms such as combined TNS register pairs.

canonical input mode. For an Open System Services (OSS) process, a terminal input mode in which data is not made available to the process until an entire logical line (delimited by a newline, EOF, or EOL character) is entered. This mode is sometimes called line mode or nontransparent mode. Contrast with noncanonical input mode.

CAP. See cartridge access port (CAP).

Carbon Copy. A remote operations software application that enables a workstation in one location to access, through a modem, a workstation in another location. Carbon Copy is included with all system consoles, and service providers use it to dial in to system consoles at customer sites. See also remote access.

card cage. A structure made up of slots that hold components such as disk drives and ServerNet adapters.

carrier. An electrical signal that carries data.


Glossary cartridge access port (CAP)

cartridge access port (CAP). The component on a tape library where you insert cartridges into and remove cartridges from the library.

caught signal. A programmatic signal that is delivered to a process that has a signal-handling function for it. When the signal is caught, the process is interrupted, and the signal-handling function executes.

CBB. See common base board (CBB).

CCITT. International Telegraph and Telephone Consultative Committee.

CCSA. See Common Communication ServerNet adapter (CCSA).

CE. Customer engineer. See service provider.

cell. See storage pool.

central processing unit (CPU). Historically, the main data processing unit of a computer. HP NonStop™ servers have multiple cooperating processors rather than a single CPU. See also processor.

Challenge Handshake Authentication Protocol (CHAP). An Internet-standard protocol for verifying encrypted passwords. CHAP is a security protocol that is implemented using Point-to-Point Protocol (PPP). The OSM and TSM Notification Directors use CHAP to maintain security during dial-outs.

channel. An information route for data transmission. See also ServerNet link.

CHAP. See Challenge Handshake Authentication Protocol (CHAP).

character. A sequence of one or more bytes representing a single character; used for the organization, representation, or control of data. A single-byte character consists of eight bits that represent a character. A multibyte character uses one or more bytes to represent a character. A wide character is a fixed-width character wide enough to hold any coded character supported by an implementation.

The ISO C standard defines the term multibyte character; a single-byte character is a special case of multibyte character.

character set. A finite set of characters (letters, digits, symbols, ideographs, or control functions) used for the organization, representation, or control of data. See also code set.

character special file. In the Open System Services (OSS) environment, a device that is treated as a file for which all input or output must occur in character bytes. Traditionally, such files are interactive terminals, and the ISO/IEC IS 9945-1:1990 standard defines only the access to such terminal files. See also terminal. Contrast with block special file.


Glossary chassis

chassis. A single sheet-metal structure that holds all the other components of an enclosure. See also enclosure.

checksum. A generic term, meaning to add together (although the definition of add need not be a normal arithmetic add) all of the data to produce a check word. See also cyclic redundancy check (CRC).

child process. A process created by another process. The creating process becomes the parent process of the new process. See also parent process.

CIIN. A command file in the SYSnn subvolume that is read and executed by the startup HP Tandem Advanced Command Language (TACL) process after system load if the CIIN file is specified in the CONFTEXT file and enabled in the OSM or TSM Low-Level Link.

circuit breaker. A device designed to open and close a circuit by nonautomatic means and to open the circuit automatically on a predetermined overcurrent without damage to itself.

CISC compiler. See TNS compiler.

CISC processor. An instruction processing unit (IPU) that is based on complex instruction-set computing (CISC) architecture.

class. A group of object-oriented data entities and the methods associated with that group.

Class-1 CRU. A customer-replaceable unit (CRU) that probably will not cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing Class-1 CRUs are not required to have previous experience replacing HP NonStop™ S-series CRUs. However, for some CRUs, customers must be able to use the tools needed for the replacement procedure (which are common tools) and must protect components from electrostatic discharge (ESD).

Class-2 CRU. A customer-replaceable unit (CRU) that might cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing Class-2 CRUs should have either three or more months of experience replacing HP NonStop™ S-series CRUs or equivalent training. Customers must be able to use the tools needed for the replacement procedure and must protect components from electrostatic discharge (ESD).

Class-3 CRU. A customer-replaceable unit (CRU) that probably will cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing Class-3 CRUs should have either six or more months of experience replacing HP NonStop™ S-series CRUs or equivalent training. Customers must be able to use the tools needed for the replacement procedure, must protect components from electrostatic discharge (ESD), and must understand the dependencies involved in NonStop S-series CRU-replacement procedures, such as disk-path switching. Replacement by a service provider trained by HP is recommended.


Glossary client

client. A software process, hardware device, or combination of the two that requests services from a server. Often, the client is a process residing on a programmable workstation and is the part of an application that provides the user interface. The workstation client might also perform other portions of the application logic.

client application. An application that requests a service from a server application. Execution of remote procedure calls is an example of a client application.

client (of a loadable library). A loadfile that uses functions or data from a library.

CLIP. See communications line interface processor (CLIP).

cluster. (1) A collection of servers, or nodes, that can function either independently or collectively as a processing unit. See also ServerNet cluster. (2) A term used to describe a system in a Fiber Optic Extension (FOX) ring. More specifically, a FOX cluster is a collection of processors and I/O devices functioning as a logical group. In FOX nomenclature, the term is synonymous with system or node.

cluster number. A number that uniquely identifies a node in a Fiber Optic Extension (FOX) ring. This number is in the range 1 through 14. See also node number.

cluster switch. See HP NonStop™ Cluster Switch (model 6770) and HP NonStop™ ServerNet Switch (model 6780).

cluster switch enclosure. An enclosure provided by HP for housing the subcomponents of an HP NonStop™ Cluster Switch. The subcomponents include the ServerNet II Switch, the AC transfer switch, and the uninterruptible power supply (UPS). A cluster switch enclosure resembles, but is half the height of, a standard HP NonStop S-series system enclosure.

cluster switch group. Within an external ServerNet fabric, all the cluster switches that belong to the same cluster switch zone. A cluster switch group can consist of up to four 6780 switches, each representing one cluster switch layer. All of the cluster switches that form a cluster switch group typically are installed in the same cluster switch rack.

cluster switch layer. The topological cluster switch position within a cluster switch group. Each cluster switch group can contain up to four layers, numbered 1 to 4 from bottom to top. A cluster switch layer consists of a pair of cluster switches (X and Y) and provides connections for up to eight ServerNet nodes. Layers within a group are interconnected by intragroup cables. When all four layers are present, the intragroup cables are configured as a vertical tetrahedron. See also cluster switch layer number.

cluster switch layer number. A number in the range 1 through 4 that identifies the position of a cluster switch within a cluster switch group. See also cluster switch group.

cluster switch logic board. A circuit board that provides switching logic for the HP NonStop™ ServerNet Switch (model 6780). The logic board (LB) has a front panel for operator and maintenance functions and is a Class-3 CRU.


Glossary cluster switch rack

cluster switch rack. A mechanical frame consisting of or based on a 19-inch rack that supports the hardware necessary for a cluster switch group.

cluster switch zone. A pair of X-fabric and Y-fabric cluster switch groups and the ServerNet nodes connected to them. Up to three zones are possible. The zones, if more than one, are interconnected by interzone cables, with each cluster switch layer cabled separately from the other layers.

CME. See correctable memory error (CME).

CMI. See Communications Management Interface (CMI).

code file. See object code file.

code segment. A segment that contains executable instructions of a program or library to be executed plus related information. Code segments can be executed and also accessed as read-only data but not written to by an application program. These read-only and execute-only segments are efficiently shared among simultaneous executions of that program or library. Therefore, they are read from disk but are never written back to disk. See also TNS code space.

code set. Codes that map a unique numeric value to each character in a character set, using a designated number of bits to represent each character. Single-byte code sets use 7 or 8 bits to represent each character. The ASCII and ISO 646 code sets use 7 bits to represent each character in Roman-based alphabets; these code sets are very limited and are not appropriate for international use. The single-byte ISO 8859 code sets use 8 bits to represent each character and can therefore support Roman-based alphabets and many others including Greek, Arabic, Hebrew, and Turkish. Multibyte code sets represent characters that require more than one byte, such as East Asian ideographic characters.

code space. See TNS code space.

COFF. See Common Object File Format (COFF).

cold load. A synonym for system load or load (in the case of single processor load). System load or load is the preferred term in HP NonStop™ system publications.

command. A demand for action by or information from a subsystem or the operation demanded by an operator or application. A command is typically conveyed as an interprocess message from an application to a subsystem.

command file. An EDIT file that contains a series of commands and serves as a source of command input.

common applications environment (CAE). A computer environment in which applications can be ported across all X/Open branded products because of the use of international and industry standards. A CAE is an open system application development environment, an open system execution environment, or a combination of the two.


Glossary common base board (CBB)

common base board (CBB). In ServerNet adapters that support plug-in cards (PICs) the printed wiring assembly (PWA) that PICs are installed in.

Common Communication ServerNet adapter (CCSA). A ServerNet adapter for Signaling System Number 7 (SS7) protocol communications.

Common Object File Format (COFF). A common standard for executable files and object code. On HP NonStop™ servers, COFF for TNS/R native files was replaced by the more extensible Executable and Linkable Format (ELF) beginning with the D40.00 RVU.

communications line. A two-way link consisting of processing equipment, I/O devices, protocol conventions, and cables that connect a computer to other computers.

communications line interface processor (CLIP). The major programmable device within the ServerNet wide area network (SWAN) concentrator, providing link-level protocol and a software interface to the host. The CLIP stores and implements specific communications protocols.

Communications Management Interface (CMI). A utility used in D-series and earlier release version updates (RVUs) to make online changes to the configuration of ATP6100, CP6100, and EnvoyACP/XF communications subdevices. In G-series RVUs, CMI functions are performed by the Subsystem Control Facility (SCF).

communications subsystem. The combination of data communications hardware and software processes that function together as an integrated unit to provide services and access to wide and local area networks.

Compaq TSM. Identifies a client or server software component used to manage or service HP NonStop™ S-series servers. See also Compaq TSM client software and Compaq TSM server software.

Compaq TSM client software. The component of the Compaq TSM package that runs on a system console. The TSM client software consists of the TSM Low-Level Link, the TSM Service Application, the TSM Notification Director, and the TSM Event Viewer. See also Compaq TSM server software.

Compaq TSM Event Viewer. A component of the Compaq TSM client software. The TSM Event Viewer lets you set up criteria to view Event Management Service (EMS) log files in several ways, enabling you to rapidly assess service problems.

Compaq TSM Low-Level Link. A component of the Compaq TSM client software. The TSM Low-Level Link enables you to communicate with an HP NonStop™ S-series server even when the HP NonStop operating system is not running. When the operating system is running, you usually communicate with the server using the TSM Service Application. See also Compaq TSM Service Application.

Compaq TSM package. A software product for HP NonStop™ S-series servers that provides the information needed to perform functions such as querying resources and


Glossary Compaq TSM server software

testing, provides notification of problems on the system, and allows local or remote access to the system for service and maintenance. The TSM package performs the same role as that of HP Tandem Maintenance and Diagnostic System (TMDS), Syshealth, and Remote Maintenance Interface (RMI) on earlier systems.

Compaq TSM server software. The component of the Compaq TSM package that runs on an HP NonStop™ S-series server. When the HP NonStop operating system is running, the TSM client software on a system console communicates with a server through the TSM server software. See also Compaq TSM client software.

Compaq TSM Service Application. A component of the Compaq TSM client software. The TSM Service Application enables you to communicate with an HP NonStop™ S-series server when the HP NonStop operating system is running. When the operating system is not running, communication must take place using the TSM Low-Level Link. See also Compaq TSM Low-Level Link.

compiler extended-data segment. A selectable segment, with ID 1024, created and selected automatically in many (but not all) TNS processes. Within this segment, the compiler automatically allocates global and local variables and heaps that would not fit in the TNS user data segment. A programmer must keep this segment selected whenever those items might be referenced. Any alternative selections of segments must be temporary and undone before returning.

complex instruction-set computing (CISC). A processor architecture based on a large instruction set, characterized by numerous addressing modes, multicycle machine instructions, and many special-purpose instructions. Contrast with reduced instruction-set computing (RISC).

compliance. The testing and verification process that precedes X/Open licensing.

computer-room power center (CRPC). The equipment that conditions and distributes facility power to computer-room equipment. The CRPC typically houses an electrostatically shielded isolation transformer, power distribution panels (PDPs), a main shunt-trip circuit breaker, and voltage indicators. Also referred to as a power distribution unit (PDU) or power distribution center.

concentrator manager process (ConMgr). A process provided as part of the wide area network (WAN) subsystem. The ConMgr process runs in each processor that supports WAN products and provides management functions to the WAN subsystem and WAN products, such as downloading data link control (DLC) tasks to the communications line interface processors (CLIPs) on the ServerNet wide area network (SWAN) concentrator and selecting the preferred path for the DLC tasks.

conduit. A tubular raceway, usually constructed of rigid or flexible metal, through which insulated power and ground conductors or data cables are run. Nonmetallic conduits, although available, are not recommended.

CONFAUX file. The auxiliary configuration file created by the Distributed Systems Management/Software Configuration Manager (DSM/SCM) tools. The CONFAUX file


Glossary CONFBASE file

contains a list of the code files and system files that are needed to build the new HP NonStop™ operating system. HP recommends that you avoid making any changes to your CONFAUX file.

CONFBASE file. In G-series release version updates (RVUs), the basic system configuration database file, which is stored on the $SYSTEM.SYSnn subvolume. See also configuration file.

CONFIG file. In G-series release version updates (RVUs), the current system configuration database file, which is stored on the $SYSTEM. ZSYSCONF subvolume. See also configuration file.

configuration. (1) The arrangement of enclosures, system components, and peripheral devices into a working unit. (2) The definition or alteration of characteristics of an object.

configuration file. In G-series release version updates (RVUs), one of the following files: CONFBASE, CONFIG, one or more saved configuration files named CONFxxyy, and CONFSAVE. See also system configuration database.

configuration planner. The person who manages system configuration changes and software configuration changes. This person modifies the system configuration database for system configuration changes and creates a new operating system image for software configuration changes. See also planner.

configuration revision. A planner-defined set of software products and related configuration information that the Distributed Systems Management/Software Configuration Manager (DSM/SCM) can activate on a target system. Multiple configuration revisions might exist on a target system. A configuration revision is made up of the product versions named in its software revision list, its HP NonStop™ operating system image, and the relevant profile items, such as the location of the target subvolumes on the target system. It is created by a Build request and is included in the activation package sent to the target system.

configuration tag. Each configuration tag identifies and configures the topology of a cluster switch and its unique position within the topology. The configuration tag defines which ServerNet node numbers the cluster switch supports.

configuration utility process. The $ZCNF process that is the access process for the CONFIG file and starts and maintains the $ZPM persistence manager process.

Configuration Utility Program (COUP). A utility used in D-series and earlier release version updates (RVUs) to make online changes to the configuration of devices and controllers. COUP is part of the Dynamic System Configuration (DSC) facility. In G-series RVUs, similar functions are performed by the Subsystem Control Facility (SCF).


Glossary configured object

configured object. A Subsystem Control Facility (SCF) object that exists at the time a subsystem completes its initialization process, or an SCF object that is brought into existence by a command issued through a subsystem management interface.

CONFLIST file. The output file produced during system generation, including error and warning messages.

conformance. Meeting the requirements of a specific standard.

conformance document. An implementor’s document that must accompany software claiming conformance with a POSIX standard. The document specifies the behavior or other aspect of the software when the standard describes a behavior or aspect as implementation-defined.

conformance statement questionnaire (CSQ). A document that identifies how a product implements X/Open Specifications as defined in XPG Component/Profile Definitions. A CSQ exists for each branded product.

conforming POSIX.1 application. An application that is either an ISO/IEC-conforming POSIX.1 application or a national-standards-body conforming POSIX.1 application.

conforming POSIX.1 application using extensions. An application that:

• Is a conforming POSIX.1 application

• Also uses features or facilities that are not described in ISO/IEC IS 9945-1:1990 (POSIX.1) but are consistent with the standard

• Meets the documentation requirements of a conforming POSIX.1 application and documents its use of nonstandard features or facilities

For example, an application using the tdm_fork() function could be a conforming POSIX.1 application using extensions.

CONFSAVE file. In G-series release version updates (RVUs), the automatically saved configuration database file, which is stored on the $SYSTEM.ZSYSCONF subvolume. See also configuration file.

CONFTEXT file. The configuration file used as input during system generation that contains a series of entries defining your HP NonStop™ operating system attributes. A G-series CONFTEXT file consists of one or two paragraphs: DEFINES (optional) and ALLPROCESSORS.

CONFxxyy file. In G-series release version updates (RVUs), a saved configuration database file created by the Subsystem Control Facility (SCF) and stored in the $SYSTEM.ZSYSCONF subvolume. xxyy is the number you entered as xx.yy in the SCF SAVE CONFIGURATION command. (xx indicates the base version, and yy indicates the subversion.) See also configuration file.

ConMgr. See concentrator manager process (ConMgr).


Glossary connection

connection. (1) The path between two protocol modules that provides reliable stream delivery service. (2) For OSM and TSM software, the logical link established between the client software on a workstation and the server software on an HP NonStop™ system after a logon sequence has been performed. The two types of logical connections are service connections and low-level links.

Connection view. One of several views of a server available in the view pane of the Management window of the Compaq TSM package. The Connection view is a visual representation of the connectivity among components within an enclosure. See also Physical view.

connectivity. The ability of a system to transfer information between itself and a system from another vendor. Other vendors use the term connectivity to mean hardware compatibility. See also interoperability.

connector. See port.

console message. See operator message.

contiguous ground. An insulated grounding conductor that extends from an equipment enclosure power receptacle to the final point of electrical service for the computer-room equipment, whether that final point is the main service entrance or the separately derived power source. In most instances, the final point of electrical service is an isolating transformer installed in the computer room.

control domain. Denotes the extent a given maintenance entity is directly accessible to hardware, based on the internal maintenance bus of the maintenance entity’s FRUs.

control and inquiry. The aspects of Subsystem Control Facility (SCF) object management related to the state or configuration of an object. Such aspects include actions that affect the state or configuration of an object, inquiries about the object, and commands pertaining to the session environment (for example, commands that set default values for the session).

controller. See I/O controller or ServerNet addressable controller (SAC).

controlling process. In the Open System Services (OSS) environment, the session leader that established the connection to the controlling terminal. The session leader stops being the controlling process when the corresponding terminal stops being the controlling terminal.

controlling terminal. In the Open System Services (OSS) environment, a terminal that might be associated with a session. A session can have only one controlling terminal, and a controlling terminal can control only one session at a time. When a session has a controlling terminal, all the following are true:

• Certain character sequences entered from that terminal cause signals to be sent to all processes in the process groups of that session.

• Certain characters entered from that terminal might receive special treatment.


Glossary Coordinated Universal Time (UTC)

• Members of background process groups of the session are restricted from certain kinds of access to the controlling terminal.

Coordinated Universal Time (UTC). The standard measure of time from the beginning of the current Epoch. UTC is sometimes called Universal Coordinated Time, CUT, or UCT; the standard appellation is abbreviated as UTC, an arbitrary ordering of the letters. UTC was formerly called Greenwich mean time (GMT).

core dump file. See process snapshot file or saveabend file.

core file. See process snapshot file or saveabend file.

correctable memory error (CME). An error caused by incorrect data at a particular memory location. The cause of the error is such that the error is automatically corrected by the system. Contrast with uncorrectable memory error (UCME).

COUP. See Configuration Utility Program (COUP).

CPU. See central processing unit (CPU).

cpu, pin. In the Guardian environment, a number pair that uniquely identifies a process during the lifetime of the process, consisting of the processor (CPU) number and the process identification number (PIN). See also PID.

CRC. See cyclic redundancy check (CRC).

creation version serial number (CRVSN). In the Open System Services (OSS) environment, a number assigned by a disk process when a file is created. The CRVSN is used by the disk process and the OSS name server process to verify that the correct file is accessed. The CRVSN is stored in the catalog entry for an OSS regular file and is passed to the disk process when a Data Definition Language (DDL) request that involves the file is made.

critical load. Equipment that must have an uninterruptible power input to prevent damage to the equipment or the facility or prevent injury to personnel.

CRPC. See computer-room power center (CRPC).

CRU. See customer-replaceable unit (CRU).

CRVSN. See creation version serial number (CRVSN).

CSQ. See conformance statement questionnaire (CSQ).

current. The flow of electrons in a conductor.

current configuration file. See configuration file.


Glossary current working directory

current working directory. In the Open System Services (OSS) environment, the directory used in pathname resolution of relative pathnames. A process always has a current working directory. See also working directory.

CUSTFILE. An EDIT file included on every site update tape (SUT) as $SYSTEM.Annnnnn.CUSTFILE, where nnnnnn is the system serial number of the target system. The CUSTFILE contains information on the software products on the SUT, their related files, and the destination and use of each file. HP customizes information in the CUSTFILE for each customer’s system.

customer engineer (CE). See service provider.

customer-installable system. A system that does not require specially trained service providers to install.

customer-replaceable unit (CRU). A unit that can be installed or replaced in the field either by customers or by qualified personnel trained by HP. CRUs are divided into the categories of Class 1, Class 2, and Class 3 based on the risk of causing a system outage if the documented replacement procedure is not followed correctly and how much CRU-replacement training or experience is advisable. See also Class-1 CRU, Class-2 CRU, Class-3 CRU, and field-replaceable unit (FRU).

cyclic redundancy check (CRC). The most widely used error detection code for ensuring the integrity of transmitted data. The digits of the CRC are calculated by the sender for each block of data sent and recalculated by the receiver. (It is a family of mathematical functions involving computing the quotient and remainder of a polynomial division.) A CRC is a form of checksum.

daemon. See demon.

dark site. See unattended site.

data communications equipment (DCE). Equipment that provides all the functions required to establish, maintain, and terminate a connection and provides the signal conversion and coding between the data terminal equipment (DTE) and telephone company lines or data circuits. A DCE is usually a modem.

data link control (DLC). A set of functions associated with Layer 2 of the Open Systems Interconnection (OSI) reference model. These functions are responsible for reliable communication between two physically connected nodes.

data link control (DLC) task. Tasks that support the equivalent to Layer 2 of the Open Systems Interconnection (OSI) reference model. Wide area network (WAN) DLC tasks execute in the ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP), and each WAN DLC task controls one line interface.

data segment. A virtual memory segment holding data. Every process begins with its own data segments for program global variables and runtime stacks (and for some libraries,


Glossary data terminal equipment (DTE)

instance data). Additional data segments can be dynamically created. See also flat segment and selectable segment.

data terminal equipment (DTE). Equipment that constitutes the data source or data sink and provides for the communication control function protocol. It includes any piece of equipment at which a communication path begins or ends.

data transparent. Describes software that examines all eight bits of every data byte and that uses no bit in a data byte for its own purposes. Internationalized applications must be data transparent.

dB. See decibel (dB).

dBm. Decibels as referenced to a milliwatt. A unit of measure that establishes 0 dBm equal to 1 milliwatt. A negative value represents a decrease in power, and a positive value represents an increase in power. See also decibel (dB).

DC. See direct current (DC).

DCE. See data communications equipment (DCE).

DCF. See dynamic configuration file (DCF).

DCT. See destination control table (DCT).

DC power cable. In HP NonStop™ S-series system enclosures with power shelves, a cable that delivers DC power from the power shelf to a processor multifunction (PMF) customer-replaceable unit (CRU) or I/O multifunction 2 (IOMF 2) CRU in that enclosure.

DDR. Double data rate.

Debug With Arbitrary Record Format (DWARF). A standardized debugging data format. HP debugging tools such as Native Inspect read DWARF-2 for debugging information in Executable and Linkable Format (ELF).

decibel (dB). A unit of measure used to express a relative difference in power. A negative value represents a decrease in power, and a positive value represents an increase in power.

dedicated service LAN. An Ethernet local area network (LAN) for use by only the OSM and TSM applications. This LAN connects system consoles with the Ethernet ports on the processor multifunction (PMF) customer-replaceable units (CRUs) in group 01 of an HP NonStop™ S-series server. A dedicated LAN supports NonStop S-series servers and system consoles but does not support any other types of servers or workstations. See also public LAN.

DEFINE. An HP Tandem Advanced Command Language (TACL) command you can use to specify a named set of attributes and values to pass to a process.


Glossary DEFINES paragraph

DEFINES paragraph. An optional paragraph in the CONFTEXT configuration file that contains one or more identifiers, each with its associated text string. The DEFINES paragraph, if used, precedes the ALLPROCESSORS paragraph.

delta. A method for connecting a 3-phase power source (or load) in a closed series loop with input (or output) connections made to each of the three junctions. The delta’s physical arrangement resembles the delta character from the Greek alphabet.

demon. On a UNIX system, a process that runs continuously to provide a specific service for other processes. A demon does not have a controlling terminal and is not explicitly invoked. On an HP NonStop™ system, a demon runs in the Open System Services (OSS) environment and has an OSS process ID. See also static server.

dest PID. See destination PID (dest PID).

destination control table (DCT). The HP NonStop™ operating system data structure that holds information about every device and named process in the system. The DCT consists of the named resource list (NRL) and the process-pair list (PPL). The DCT is replicated in each CPU.

destination PID (dest PID). The destination processor for a packet generated by an input/output application-specific integrated circuit (ASIC).

destination ServerNet ID (DID). A field in the ServerNet packet header indicating the intended destination for the packet.

detailed report. A complete listing of status or configuration information provided by the Subsystem Control Facility (SCF) STATUS or INFO command when you use the DETAIL option. Contrast with summary report.

device. A computer peripheral or an object that appears to an application as such. See also terminal.

DHCP. See Dynamic Host Configuration Protocol (DHCP).

dial-out point. A system console from which incident reports are sent to a service provider. Incident reports are sent only from system consoles defined as the primary and backup dial-out points (the primary and backup system consoles).

DID. See destination ServerNet ID (DID).

DIMM. See dual inline memory module (DIMM).

direct connect. Connection from the Fibre Channel ServerNet adapter (FCSA) to the Enterprise Storage System (ESS) without going through an FC switch.

direct current (DC). Electric current that flows in only one direction. Contrast with alternating current (AC).


Glossary direct jump area

direct jump area. One of sixteen 256-megabyte portions of the 4-gigabyte virtual address space. A RISC jump instruction has the ability to jump directly to any location within its own direct jump area without having to use a far jump table.

direct memory access (DMA). A technique for transferring data from main memory to a device without passing it through the CPU.

directory. A type of Open System Services (OSS) special file that contains directory entries, which associate names with files. No two directory entries in the same directory have the same name.

directory entry. In the Open System Services (OSS) file system, an object that associates a filename with a file. Several directory entries can associate names with the same file. See also link.

directory loop. In the Open System Services (OSS) file system, an error condition in which a directory is identified as its own parent directory.

directory special file. See directory.

directory stream. In the Open System Services (OSS) file system, an object with an opaque data type. A process can sequentially read directory entries from a directory stream.

directory tree. A hierarchy of directories. In the Open System Services (OSS) environment, directories are connected to each other in a branching hierarchical fashion such that only one path exists between any two directories (if no backtracking occurs).

disconnecting means. A device, group of devices, or other means by which the conductors of a circuit can be disconnected from their source of supply.

discovery. For the OSM and TSM client software, the process of identifying the resources that exist on an HP NonStop™ server. See also incremental discovery and initial discovery.

disk bootstrap. A software entity residing on disk that is used to load the HP NonStop™ operating system image (OSIMAGE) into memory during a system load. A disk that contains the disk bootstrap is referred to as a bootable disk. The disk bootstrap is placed on the disk either as part of a tape load or as a result of the SCF CONTROL DISK, REPLACEBOOT command.

disk cache. A temporary storage buffer into which data is read, retained, and perhaps updated before being written to disk, for more efficient processing.

disk drive. A device that stores and accesses data on a magnetic disk. Random access to addressable locations on a magnetic disk is provided by magnetic read/write heads. See also volume.


Glossary DISKGEN

DISKGEN. A system generation option that invokes the DISKGEN program to copy directly to disk the files necessary to generate an HP NonStop™ operating system. DISKGEN can be used instead of a system image tape (SIT).

DISK object type. The Subsystem Control Facility (SCF) object type for all disk devices attached to your system.

disk volume. See volume.

distributed system. A system that consists of a group of connected, cooperating computers.

Distributed Systems Management (DSM). A set of tools used to manage HP NonStop™ systems and Expand networks.

Distributed Systems Management/Software Configuration Manager (DSM/SCM). A graphical user interface (GUI)-based program that installs new software and creates a new HP NonStop™ operating system. DSM/SCM creates a new software revision and activates the new software on the target system.

distribution subvolume (DSV). A subvolume containing program files for a particular software product along with the release version update (RVU) document (softdoc) file for that product. The format for a DSV name is Ynnnnrrr or Rnnnnrrr, where nnnn is the software product number and rrr is the base version identifier (such as D20) or software product revision (SPR) identifier (such as AAB).

DLC. See data link control (DLC).

DLL. See dynamic-link library (DLL).

DMA. See direct memory access (DMA).

DNS. See Domain Name System (DNS).

DNS server. A server that resolves hostnames to Internet protocol (IP) address mapping queries. These queries originate from either client computers, which are known as resolvers, or other Domain Name System (DNS) servers, which accounts for the distributed nature of DNS. See also Network Information Service (NIS).

domain. (1) In the Internet, a part of the naming hierarchy. Syntactically, a domain name consists of a sequence of names (labels) separated by periods (dots). (2) In an HP NonStop™ S-series server, a pair of service processors, the associated router clouds, and the attached replaceable units. (3) A set of objects over which control or ownership is maintained. Types of domains include power domains and service processor (SP) domains.

Domain Name System (DNS). A system that defines a hierarchical, yet distributed, database of information about hosts on a network. A domain name is a meaningful and easy-to-remember handle for an Internet address. The network administrator


Glossary donor system

configures the DNS with a list of hostnames and Internet protocol (IP) addresses, allowing users of workstations that are configured to query the DNS to specify remote systems by hostnames rather than by IP addresses. DNS domains should not be confused with Windows NT networking domains. See also DNS server, Network Information Service (NIS), and ping.

donor system. The computer system you make smaller by removing enclosures, either to reduce the system or to add the removed enclosures to another target system, using a process known as system reduction.

double-high stack. A stack that includes a base, a frame, and two HP NonStop™ S-series system enclosures. Contrast with single-high stack.

double-wide plug-in card (PIC). A large-form-factor plug-in card (PIC) that occupies two adjacent PIC slots within a ServerNet adapter or an HP NonStop™ cluster switch. See also single-wide plug-in card (PIC).

download. The process of transferring software from one location to another, where the transferring entity initiates the transfer.

download line task. Any task running under the Portable Silicon Operating System (pSOS) system product, such as a data protocol.

downtime. Time during which a computer system is not capable of doing useful work because of a planned or unplanned outage. From the end user’s perspective, downtime is any time a needed application is not available.

downward compatibility. The ability of a requester to operate with a server of an earlier revision level. In this case, the requester is downward-compatible with the server, and the server is upward-compatible with the requester. Contrast with upward compatibility.

DRAM. Dynamic random-access memory.

drive. See disk drive or tape drive.

dropout. A voltage loss of very short duration (that is, milliseconds).

DSC. See Dynamic System Configuration (DSC).

DSM. See Distributed Systems Management (DSM).

DSM/SCM. See Distributed Systems Management/Software Configuration Manager (DSM/SCM).

DSV. See distribution subvolume (DSV).

DTE. See data terminal equipment (DTE).

dual inline memory module (DIMM). Small circuit boards carrying memory integrated circuits, with signal and power pins on both sides of the board. A DIMM is different


Glossary dual-ported

from a single inline memory module (SIMM) in that the connections on each side of the module connect to different chips, whereas the connections on both sides of a SIMM connect to the same memory chip. This difference gives the DIMM a wider data path, as more modules can be accessed at once.

dual-ported. The capability of a ServerNet adapter or peripheral device to receive data and commands from two sources although only one source might have access at any particular moment.

duplicate file descriptor. In the Open System Services (OSS) file system, a file descriptor that refers to the same open file description as another file descriptor.

DWARF. See Debug With Arbitrary Record Format (DWARF).

dynamic configuration file (DCF). An attachment file that is produced by the OSM and TSM client software and accompanied by an incident report. The DCF contains a snapshot of the system configuration, the state of the HP NonStop™ server, and outstanding alarms at the time that the incident report was issued. The DCF is used by the service provider to avoid having to perform online discovery of the server over dial-up telephone lines.

Dynamic Host Configuration Protocol (DHCP). An Internet protocol for automating the configuration of computers that use TCP/IP. DHCP can automatically assign IP addresses, deliver TCP/IP stack configuration parameters such as the subnet mask and default router, and provide other configuration information such as the addresses for printer, time, and news servers.

dynamic information. Information that represents the set of resources that actually exist in the current configuration of an HP NonStop™ server. Dynamic information is gathered from a server through the process of discovery. Contrast with static information.

dynamic-link library (DLL). A collection of procedures whose code and data can be loaded and executed at any virtual memory address, with run-time resolution of links to and from the main program and other independent libraries. The same DLL can be used by more than one process. Each process gets its own copy of DLL static data. Contrast with shared run-time library (SRL). See also TNS/R library.

dynamic loading. Loading and opening dynamic-link libraries under programmatic control after the program is loaded and execution has begun.

dynamic process configuration. Using Subsystem Control Facility (SCF) to configure a generic process to always start in a designated primary processor (that is, to be fault tolerant).

dynamic shared object (DSO). See dynamic-link library (DLL).

Dynamic System Configuration (DSC). A utility used in D-series and earlier release version updates (RVUs) to make online changes to the configuration of devices and


Glossary E4SA

controllers. Its interactive utility is called the Configuration Utility Program (COUP). In G-series RVUs, similar functions are performed by Subsystem Control Facility (SCF).

E4SA. See Ethernet 4 ServerNet adapter (E4SA).

earth ground. The connection of the electrical-grounding conductors to a dependable, low-resistance contact with the soil.

earth-grounding electrode. An electrically conductive rod that is driven into soil, thus providing an earth-ground connection point for the electrical ground wiring in a building. A vertical steel column of a building, with its base sunk into soil, can also serve as an earth-grounding electrode.

earth-grounding electrode system. A grounding network created by bonding together the grounding means in a building (for example, underground metal water pipes, structural steel, and ground rods into the earth) and bonding them to the switchgear at the facility’s main electrical service entrance.

ECC. See error correction code (ECC).

ECL. See emitter-coupled logic (ECL).

ECL plug-in card (PIC). See emitter-coupled logic (ECL) plug-in card (PIC).

ECL ServerNet cable. See emitter-coupled logic (ECL) ServerNet cable.

EDIT file. In the Guardian file system, an unstructured file with file code 101. An EDIT file can be processed by either the EDIT or PS Text Edit (TEDIT) editor. An EDIT file typically contains source program or script code, documentation, or program output. Open System Services (OSS) functions can open an EDIT file only for reading.

effective group ID. An attribute of an Open System Services (OSS) process that is used to determine permissions such as the file access allowed for the process. The effective group ID of a process is a group ID that contributes to the group access privileges of that process. The effective group ID of a process might be used to set the group ID of files created by that process. The effective group ID can be changed while the process runs.

effective user ID. An attribute of an Open System Services (OSS) process that is used to determine such permissions as the file access allowed for the process. The effective user ID of a process is the user ID that determines the owner access privileges of that process. The effective user ID of a process might be used to set the user ID of files created by that process. The effective user ID can be changed while the process runs.

EIA. Electronic Industries Association.

electric utility. The local utility service that, for a fee, supplies alternating-current (AC) power to businesses and residences.


Glossary electromagnetic interference (EMI)

electromagnetic interference (EMI). Forms of conducted or radiated interference that might appear in a facility as either normal or common-mode signals. The frequency of the interference can range from the kilohertz to gigahertz range. However, the most troublesome interference signals are usually found in the kilohertz to low megahertz range. At present, the terms electromagnetic interference and radio frequency interference (RFI) are usually used interchangeably.

electrostatically shielded transformer. A transformer that has a metallic shield placed between the primary and secondary windings. This shield diverts high-frequency signals to ground.

electrostatic discharge (ESD) protection kit. A kit containing an antistatic mat and a wriststrap with a cable and grounding clip. A service provider or customer wears the wriststrap while performing maintenance procedures inside an enclosure. The wriststrap and cable contain grounding wires. When the grounding clip is attached to a metal object, such as the enclosure, the person wearing the wriststrap is grounded. Any static electricity incurred during the procedure is discharged safely to the ground instead of to electrical components within the enclosure.

ELF. See Executable and Linkable Format (ELF).

emergency power off (EPO). Describes equipment used to automatically disconnect all electrical power to connected equipment if an emergency occurs. A computer room’s main EPO system shuts off all room equipment (except for lighting and fire-sensor equipment) if a fire occurs. An equipment zone EPO shuts off power to all connected computer equipment if the EPO switch is activated.

emergency power-off (EPO) connector. A two-pin connector on the service side of an HP NonStop™ S-series system enclosure that allows an external signal to disable the batteries in the enclosure during emergency conditions. A cable is attached from the connector to a relay band or push button typically located near the door of a computer room. Pushing the EPO button removes power from all computer equipment in the room and prevents the batteries from powering the server after power is removed. EPO capabilities are required in the United States when a server is installed in a computer room designed to comply with the special construction and fire protection provisions of the United States’ national electrical code (or at other sites as required by local regulations).

EMI. See electromagnetic interference (EMI).

emitter-coupled logic (ECL). A logic that expresses digital signals in differential negative voltage levels, from -8 volts to -1.8 volts. HP NonStop™ S-series servers containing ServerNet expansion boards (SEBs) use ECL ServerNet cables. An ECL plug-in card (PIC) allows the modular SEB (MSEB) and I/O multifunction (IOMF) 2 customer-replaceable unit (CRU) to use ECL ServerNet cables.

emitter-coupled logic (ECL) plug-in card (PIC). A plug-in card (PIC) for the modular ServerNet expansion board (MSEB) and I/O multifunction (IOMF) 2 customer-


Glossary emitter-coupled logic (ECL) ServerNet cable

replaceable unit (CRU) that supports the emitter-coupled logic (ECL) interface. See also emitter-coupled logic (ECL) and plug-in card (PIC).

emitter-coupled logic (ECL) ServerNet cable. A ServerNet cable that uses emitter-coupled logic (ECL). Before the modular ServerNet expansion board (MSEB) was introduced, ECL was the only ServerNet cable technology used by HP NonStop™ S-series servers. You can connect an ECL ServerNet cable directly to a ServerNet expansion board (SEB) or to an MSEB using an ECL plug-in card (PIC).

empty directory. In the Open System Services (OSS) file system, a directory that contains only an entry for itself and an entry for its parent directory.

empty string. In C and C++ programs, a character string that begins with a null character. This term is synonymous with null string.

EMS. See Event Management Service (EMS).

EMS collector. An Event Management Service (EMS) process to which subsystems report events.

emulate. To imitate the instruction set and address spaces of a different hardware system by means of software. Emulator software is compatible with and runs software built for the emulated system. For example, a TNS/R system emulates the behavior of a TNS system when executing interpreted or accelerated TNS object code.

enclosure. A single sheet-metal structure and its enclosed set of system components. See also base enclosure, stackable enclosure, system enclosure and peripheral enclosure.

enclosure interleaving. On HP NonStop™ S-series systems, configuring a mirrored disk volume to use two separate system enclosures. For internal disk drives, the two disk drives of the mirrored volume can be in separate enclosures. For external disk drives, the adapters connected to the two disk drives of the mirrored volume can be in separate enclosures.

endian. Denotes the significance of byte 0 in a multibyte structure such as a word. HP NonStop™ servers are big-endian, where the most significant bit is contained in byte 0. Intel® systems and HP AlphaServer OpenVMS and HP AlphaServer Tru64 UNIX systems are little-endian, where the least significant bit is contained in byte 0.

Enterprise Storage System (ESS). A collection of magnetic disks, their controllers, and the disk cache in a stand-alone cabinet or cabinets. These disks are configured by an attached console and presented to the attached server as logical volumes that can be a fraction of a physical volume or can span volumes.

environmental parameters. Subsystem Control Facility (SCF) session parameters set by default or by using various SCF commands. The values associated with the environmental parameters can be examined using the ENV command.


Glossary environment strings

environment strings. For an Open System Services (OSS) process, a vector of strings of the form name = value that contains information about the environment that the process runs in. Environment strings are accessible to the process and are inherited by its child processes.

EPO. See emergency power off (EPO).

Epoch. The period beginning January 1, 1970, at 0 hours, 0 minutes, and 0 seconds Coordinated Universal Time (UTC).

EPO connector. See emergency power-off (EPO) connector.

equipment grounding conductor. The conductor used to connect the non-current-carrying metal parts of equipment, raceways, and other enclosures to the grounding electrode conductor at the facility’s main service entrance or at the source of a separately derived power source.

errno. An external variable that contains the most recent error condition set by a C function.

error correction code (ECC). A coding system that incorporates extra parity bits in order to detect errors.

error number. For the Subsystem Programmatic Interface (SPI), a value that can be assigned to a return token or to the last field of an error token to identify an error that occurred. SPI defines a small set of error numbers, but most error numbers are defined by subsystems.

ESD kit. See electrostatic discharge (ESD) protection kit.

ESP. See expansion service processor (ESP).

ESS. See Enterprise Storage System (ESS).

essential firmware. Code in memory that is necessary for power-up initialization and communication with a host or device. Contrast with nonessential firmware.

Ethernet. A local area network (LAN) that uses the carrier sense multiple access with collision detection (CSMA/CD) access method on a bus topology and is the basis for the IEEE 802.3 standard.

Ethernet 4 ServerNet adapter (E4SA). A ServerNet adapter for Ethernet local area networks (LANs) that contains four Ethernet ports.

Ethernet hub. A multiport repeater typically supporting 10Base-T cabling. Most hubs are connectors for 8 or 12 cables. Also referred to as a concentrator.

Event Management Service (EMS). A Distributed Systems Management (DSM) product that provides event collection, event logging, and event distribution facilities. EMS provides different event descriptions for interactive and programmatic interfaces, lets


Glossary event message

an operator or an application select specific event-message data, and allows for flexible distribution of event messages within a system or network.

event message. Text intended for a system operator that describes a change in some condition in the system or network, whether minor or serious. The change of condition is called an event. Events can be operational errors, notifications of limits exceeded, requests for actions needed, and so on. See also operator message.

Event Viewer Server Manager. A persistent process that routes messages and data between the OSM or TSM Event Viewer on the system console and event server and summary server processes on the HP NonStop™ server. An event server process retrieves events. A summary server is a persistent process that maintains a summary of all the events in a specified log file.

exact point. See memory-exact point and register-exact point.

exception handler. A section of program code to which control is transferred when an exception occurs. The exception handler then determines what action should be taken.

executable. See object code file.

Executable and Linkable Format (ELF). A common standard for executable files and object code. On HP NonStop™ servers, ELF replaced the less extensible Common Object File Format (COFF) for native files.

execution mode. The emulated or real instruction set environment in which object code runs. A TNS system has only one execution mode: TNS mode using TNS compilers and 16-bit TNS instructions. A TNS/R system has three execution modes: TNS/R native mode using MIPS native compilers and MIPS instructions, emulated TNS execution in TNS interpreted mode, and emulated TNS execution in TNS accelerated mode.

Expand line-handler process. A process pair that handles incoming and outgoing Expand messages and packets. An Expand line-handler process handles direct links and also binds to other processes using the Network Access Method (NAM) interface to support Expand-over-X.25, Expand-over-FOX, Expand-over-ServerNet, Expand-over-TCP/IP, and Expand-over-SNA links. See also Expand-over-ServerNet line-handler process.

Expand network. The HP NonStop™ operating system network that extends the concept of fault-tolerant operation to networks of geographically distributed HP NonStop™ systems. If the network is properly designed, communication paths are constantly available even if a single line failure or component failure occurs.

Expand node. A system in an Expand network. See also node.

Expand node number. A number in the range 0 through 254, sometimes referred to as the system number, that identifies a node in an Expand network. Each Expand node number must be unique within the network. See also ServerNet node number.


Glossary Expand-over-ServerNet line

Expand-over-ServerNet line. The single line associated with an Expand-over-ServerNet line-handler process. An Expand-over-ServerNet line has the same name and logical device number as its Expand-over-ServerNet line-handler process. However, the line does not have the same states as the line-handler process.

Expand-over-ServerNet line-handler process. An Expand line-handler process that uses the NETNAM protocol to access the Network Access Method (NAM) interface provided by the ServerNet cluster monitor process, $ZZSCL. The Expand-over-ServerNet line-handler process handles incoming and outgoing Expand messages. It also handles packets leaving the server and security-related messages going between systems within a ServerNet cluster. Each node in a ServerNet cluster must be configured with an Expand-over-ServerNet line-handler process for every other node in the ServerNet cluster.

expansion service processor (ESP). A service processor (SP) that is not a master service processor (MSP). ESPs occur in pairs in groups 02 through nn (not in group 01). See also master service processor (MSP).

explicit DLL. See explicit dynamic-link library (explicit DLL).

explicit dynamic-link library (explicit DLL). A dynamic-link library (DLL) that is named in the libList of a client or is a native-compiled loadfile associated with a client.

export. To offer a symbol definition for use by other loadfiles. A loadfile exports a symbol definition for use by other loadfiles that need a data item or function having that symbolic name.

export digest. A mathematical hash of the exported symbol names and locations in a library. Two libraries with the same export digest are interchangeable in that they both export the same symbols at the same locations. They are not necessarily semantically equivalent.

extended data segment. See selectable segment.

extensible input/output (XIO). A redesign of the HP NonStop™ operating system’s I/O subsystem to enable it to extend itself in general ways to meet future requirements.

extent. A contiguous area on disk for allocating one file.

extent size. The size in bytes of a contiguous area on disk for allocating one file.

external entry-point (XEP) table. A table located in the last page of each TNS code segment that contains links for calls (unresolved external references) out of that segment.

external fabric connection. The low-level ServerNet connection between a node and one of the external ServerNet fabrics. Each node has an X and a Y connection to the external fabrics.


Glossary external routing

external routing. The routing of packets over the external ServerNet fabrics; that is, between systems (or nodes) in a ServerNet cluster. See also internal routing.

external ServerNet fabrics. The fabrics that link systems in a ServerNet cluster. See also internal ServerNet fabrics.

external ServerNet X or Y fabric. The X or Y fabric that links systems in a ServerNet cluster. See also internal ServerNet X or Y fabric.

external system area network manager process (SANMAN). (1) A Guardian process with the name $ZZSMN that provides management access to the external ServerNet X and Y fabrics. (2) A Windows NT process that configures and maintains ServerNet switches within a Windows NT cluster.

fabric. A complex set of interconnections through which there can be multiple and (to the user) unknown paths from point to point. The term fabric is used to refer to the X or Y portion of the ServerNet communications network; for example, the X fabric.

factory-installed operating system. The version of the operating system image that HP creates having a CONFTEXT configuration file, OSIMAGE file, and configuration database that matches your order. Your system is shipped with this version installed in the system subvolume $SYSTEM.SYS00.

fan. A component that circulates air into the enclosure to help maintain optimal temperature.

far gateway. A short code sequence that accomplishes the transition to privileged mode for legitimate calls to callable procedures that are located in a different direct jump area. Typically, SCr (system code, RISC) is the target area. See also direct jump area, far jump, and gateway.

far jump. A sequence of RISC instructions that permits crossing the boundaries of the 256-megabyte direct jump areas in virtual memory. Such sequences are necessary, for example, when calling into system code from user code, because the two are located in different direct jump areas. The sequence ends with a JR (Jump via Register) RISC instruction.

fastLoad. An optimization that allows the loader to avoid reading symbols and binding symbolic references when loading a program or dynamic-link library in an environment equivalent to that of a previous load. See also preset, cached bindings, and library import characterization (LIC).

Fast Ethernet ServerNet adapter (FESA). A single-ported ServerNet adapter that supports 100-megabit/second (Mbps) or 10-Mbps Ethernet data transfer rates on an HP NonStop™ S-series server.

fault domain. In a fault-tolerant system, a module that can fail without causing a system failure.


Glossary fault tolerance

fault tolerance. The ability of a computer system to continue processing despite the failure of any single software or hardware component within the system.

FCSA. See Fibre Channel ServerNet adapter (FCSA).

FC switch. See Fibre Channel switch (FC switch).

FDC. See flexible disk configuration (FDC).

feature-test macro. In C and C++ programs, a symbol that, if defined in a program’s source code, includes specific other symbols from a header within that program’s source code and makes those symbols visible.

feeder circuit. The circuit conductors installed between the facility’s main service entrance and the power distribution panels (PDPs) that supply the branch circuits.

ferrule. A cylindrical end terminal sometimes used on resistors, cartridge fuses, and other parts to permit quick insertion and removal from holders that have corresponding spring contacts.

FESA. See Fast Ethernet ServerNet adapter (FESA).

Fiber Optic Extension (FOX). Refers to two products, FOX II and ServerNet/FX, which allow you to create high-speed (up to 4 megabytes/second) networks of as many as 14 systems connected by dual fiber-optic cables.

fiber-optic plug-in card (F-PIC). A plug-in card (PIC) for the 6760 ServerNet device adapter (ServerNet/DA) that uses a fiber-optic interface to connect the adapter to external disk drives and to some tape drives that contain a back-end board (BEB) that translates fiber-optic signals from the F-PIC into SCSI commands and information for the tape drive. See also plug-in card (PIC) and SCSI plug-in card (S-PIC).

fiber optics. A medium for data transmission that conveys light or images through very fine, flexible, glass or plastic fibers. Fiber-optic cables (light guides) are a direct replacement for conventional coaxial and wire pairs.

fiber-optic ServerNet addressable controller (F-SAC). A ServerNet addressable controller (SAC) that is contained within a fiber-optic plug-in card (F-PIC).

fiber-optic ServerNet cable. A ServerNet cable that uses fiber optics to transmit data. HP NonStop™ servers support two types of fiber-optic ServerNet cables: multimode fiber-optic (MMF) ServerNet cable and single-mode fiber-optic (SMF) ServerNet cable.

Fibre Channel ServerNet adapter (FCSA). A ServerNet adapter that transmits data between an HP NonStop™ server and Fibre Channel storage devices. This ServerNet adapter is installed in an IOAM enclosure.


Glossary Fibre Channel switch (FC switch)

Fibre Channel switch (FC switch). Networking hardware that can connect an Enterprise Storage System and an HP NonStop™ server. This switch allows any-to-any connectivity.

field. In a structured programming language, an addressable entry within a data structure. The term field is sometimes used to mean member.

field-programmable gate array (FPGA). A programmable integrated circuit that can be customized to perform specific functions.

field-replaceable unit (FRU). A unit that can be replaced in the field only by qualified personnel trained by HP and cannot be replaced by customers. A unit is classified as a FRU because of safety hazards such as weight, size, sharp edges, or electrical potential; contractual agreements with suppliers; or national or international standards. See also customer-replaceable unit (CRU).

FIFO. A type of Open System Services (OSS) special file that is always read and written in a first-in, first-out manner.

FIFO special file. See FIFO.

file. An object to which data can be written or from which data can be read. A file has attributes such as access permissions and a file type. In the Open System Services (OSS) environment, file types include regular file, character special file, block special file, FIFO, and directory. In the Guardian environment, file types include disk files, processes, and subdevices.

file class. The property of an Open System Services (OSS) file indicating access permissions for a process related to the owner, group, or other identification of the process. See also file group class, file other class, and file owner class.

file description. See open file description.

file descriptor. In the Open System Services (OSS) file system, the nonnegative integer that uniquely identifies a single open of a file to a running process. Each file descriptor is associated with an open file description that contains data about the file.

file group class. The property of an Open System Services (OSS) file indicating access permissions for a process related to the group ID of the process. A process is in the file group class of a file if both:

• The process is not a member of the file owner class for the file.

• The process has an effective group ID or supplementary group ID that is the same as the group ID associated with the file.

file identifier. In the Guardian environment, the portion of a filename following the subvolume name. In the Open System Services (OSS) environment, a file identifier is a portion of the internal information used to identify a file in the OSS file system (an inode number). The two identifiers are not comparable.


Glossary file link count

file link count. The total number of directory entries for an Open System Services (OSS) file within an Expand node.

file mode. For an Open System Services (OSS) process, a field in the stat structure for a specific file that describes the type and characteristics of the file and contains the access permission bits for the file.

file mode creation mask. A mask associated with an Open System Services (OSS) process and used when the process creates a file. Bits set in this mask are cleared in the access permission bits for the file.

filename. In the Open System Services (OSS) environment, a component of a pathname containing any valid characters other than slash (/) or null. See also file name.

file name. A string of characters that uniquely identifies a file.

In the PC environment, file names for disk files normally have at least two parts (the disk name and the file name); for example, B:MYFILE.

In the Guardian environment, disk file names include an Expand node name, volume name, subvolume name, and file identifier; for example, \NODE.$DISK.SUBVOL.MYFILE.

In the Open System Services (OSS) environment, a file is identified by a pathname; for example, /usr/john/workfile. See also filename.

file other class. The property of an Open System Services (OSS) file indicating access permissions for a process related to the user ID and group ID of the process. A process is in the file other class of a file if both:

• The process is not a member of the file owner class for the file.• The process is not a member of the file group class for the file.

file owner class. The property of an Open System Services (OSS) file indicating access permissions for a process related to the user ID of the process. A process is in the file owner class of a file if the process has an effective user ID that is the same as the user ID (owner) associated with the file.

file permission bits. Information about an Open System Services (OSS) file that is used, along with other information, to determine whether a process or user has read, write, or execute/search permission to that file. The bits are divided into three parts: owner, group, and other. Each part is used with the corresponding file class of processes.

file serial number. A number that uniquely identifies a file within its file system.

fileset. In the Open System Services (OSS) environment, a set of files with a common mount point within the file hierarchy. A fileset can be part or all of a single virtual file system.

On an HP NonStop™ system, the Guardian file system for an Expand node has a mount point and is a subset of the OSS virtual file system. The entire Guardian file


Glossary file system

system therefore could be viewed as a single fileset. However, each volume and each process of subtype 30 within the Guardian file system is actually a separate fileset.

The term file system is often used interchangeably with fileset in UNIX publications.

file system. In the Open System Services (OSS) environment, a collection of files and file attributes. A file system provides the namespace for the file serial numbers that uniquely identify its files. Open System Services provides a file system (see also ISO/IEC IS 9945-1:1990 [ANSI/IEEE Std. 1003.1-1990], Clause 2.2.2.38); the Guardian application program interface (API) provides a file system; and OSS Network File System (NFS) provides a file system. (OSS NFS filenames and pathnames are governed by slightly different rules than OSS filenames and pathnames.) Within the OSS and OSS NFS file systems, filesets exist as manageable objects.

On an HP NonStop™ system, the Guardian file system for an Expand node is a subset of the OSS virtual file system. Traditionally, the API for file access in the Guardian environment is referred to as the Guardian file system.

In some UNIX and NFS implementations, the term file system means the same thing as fileset. That is, a file system is a logical grouping of files that, except for the root of the file system, can be contained only by directories within the file system. See also fileset.

File Transfer, Access, and Management (FTAM). The Open Systems Interconnection (OSI) standard developed by the International Organization for Standardization (ISO) for network file exchange and management services.

file transfer protocol (FTP). (1) The Internet-standard, high-level protocol for transferring files from one machine to another. The server side requires the client to supply a logon identifier and password before it honors requests. FTP makes no assumptions about the file-naming structure of the source and destination systems, and it allows the file names of each system to be represented in the vernacular. (2) The application used to send complete files over Transmission Control Protocol/Internet Protocol (TCP/IP) services.

filler panel. A blank faceplate that is installed in place of a computer component to ensure proper ventilation.

fingerprint. A unique identifier calculated for a file and displayed in hexadecimal format.

FIPS. A Federal Information Processing Standard of the United States government.

FIPS 151-1. The Federal Information Processing Standard that specifies the requirements for conformance to an older draft of POSIX.1 (IEEE Std. 1003.1-1988) than the version adopted as ISO/IEC IS 9945-1:1990 and imposes some additional requirements.

FIPS 151-2. The Federal Information Processing Standard that specifies the requirements for conformance to POSIX.1 as ISO/IEC IS 9945-1:1990 and imposes some additional requirements.


Glossary FIR

FIR. See FRU information record (FIR).

FIRINIT. A diagnostic task used to update the communications line interface processor (CLIP) FRU information record (FIR) that is kept in the ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP) flash memory.

FIRMUP. A diagnostic task used to update the copy of the Portable Silicon Operating System (pSOS) system product embedded kernel that is kept in the ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP) flash memory.

firmware. Code in memory that is necessary for the power-up initialization and communication with a host or device. The software for components of the ServerNet architecture (for example, an adapter) is called firmware. Some firmware for ServerNet components is downloaded when the system or component is loaded.

fixed process configuration. Using Subsystem Control Facility (SCF) to configure a generic process to always start in the first available processor (that is, to be fault tolerant).

flag. In a UNIX or Open System Services (OSS) command, a character sequence that begins with a hyphen and is processed as a unit.

flash memory. A type of memory that contains essential firmware and nonessential firmware.

flash PROM. A type of programmable read-only memory (PROM) that is electrically reprogrammable.

flat segment. A type of logical segment. Each flat segment has its own distinct address range within the process address space that never overlaps the range of any other allocated segments. Thus all allocated flat segments for a process are always available for use concurrently. See also logical segment and selectable segment.

flexible disk configuration (FDC). For HP NonStop™ S-series servers, a configuration of an internal mirrored disk volume such that no single processor enclosure or I/O enclosure can result in loss of online access to the volume.

foreground process. An Open System Services (OSS) process that belongs to a foreground process group.

foreground process group. In the Open System Services (OSS) environment, a process group whose members have privileges for access to their controlling terminal that are denied to processes in background process groups of that terminal. Each session with a controlling terminal has only one foreground process group for that terminal. Contrast with background process group.

foreground process group ID. In the Open System Services (OSS) environment, the process group ID of a foreground process group.


Glossary four-lane link

four-lane link. The four single-mode fiber-optic (SMF) ServerNet cables that connect the two HP NonStop™ Cluster Switches on the same external fabric (for example, X1 and X2) in a split-star topology.

FOX. See Fiber Optic Extension (FOX).

FOXMON. See FOX monitor process.

FOX monitor process. The Fiber Optic Extension (FOX) monitor process for the ServerNet/FX adapter subsystem. The process name is $ZZFOX.

FOX ring. The fiber-optic cabling that connects the nodes in a Fiber Optic Extension (FOX) cluster. This term is also used to refer to the topology of a FOX network.

FPGA. See field-programmable gate array (FPGA).

F-PIC. See fiber-optic plug-in card (F-PIC).

frame. (1) An assembly of sheet-metal parts that is an integral part of an HP NonStop™ S-series system enclosure and might contain peripherals or a chassis, depending on the type of enclosure. The frame enables the enclosures to be stacked and has provisions for routing and securing cables. The frame of an enclosure has dimensions that conform to an industry-standard 19-inch rack. (2) A unit of transmission in some data communications protocols, usually containing header, data, and checksum fields. (3) In NonStop S-series processors, a 4096-byte unit of physical memory; also called a physical page.

frame base. An assembly consisting of casters, leveling pads, and frame sheet metal that is an integral part of an HP NonStop™ S-series base enclosure.

free list. In the Open System Services (OSS) file system, the list of available inodes that can be allocated to files.

frequency. The number of complete cycles/second of sinusoidal variation. For alternating-current (AC) power lines, the most common frequencies are 60 hertz and 50 hertz.

FRU. See field-replaceable unit (FRU).

FRU information record (FIR). A collection of information that every field-replaceable unit (FRU) carries with it, such as part number, revision, track ID, and media access control (MAC) address.

F-SAC. See fiber-optic ServerNet addressable controller (F-SAC).

FTAM. See File Transfer, Access, and Management (FTAM).

FTP. See file transfer protocol (FTP).

GART. See graphics address remapping table (GART).


Glossary gateway

gateway. (1) A device used to convert the message protocol of one network to that of another. (2) A short code sequence that accomplishes the transition to privileged mode for legitimate calls to callable procedures. See also far gateway.

GB. See gigabyte (GB).

GCSC. See Global Customer Support Center (GCSC).

general-purpose register (GPR). One of a small number of undedicated high-speed memory locations in a processor.

generic process. A process created and managed by the Kernel subsystem; also known as a system-managed process. A common characteristic of a generic process is persistence.

GESA. See Gigabit Ethernet ServerNet adapter (GESA).

G4SA. See Gigabit Ethernet 4-port ServerNet adapter (G4SA).

Gigabit Ethernet ServerNet adapter (GESA). A single-port ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop™ systems and Ethernet LANs. A GESA can be directly installed in slots 51 through 54 of an I/O enclosure and slots 53 and 54 of a processor enclosure.

Two versions of the GESA are available:

• 3865 GESA-C (T523572): a single-port copper version compliant with the 1000 Base-T standard (802.3ab)

• 3865 GESA-F (T523572): a single-port fiber version compliant with the 1000 Base-SX standard (802.z)

Gigabit Ethernet 4-port ServerNet adapter (G4SA). A multiport ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop™ systems and Ethernet LANs. The G4SA is installed in slots 1, 2, 3, 4, and 5 of an I/O adapter module (IOAM). There are two IOAMs in an I/O adapter module (IOAM) enclosure, so a total of 10 G4SAs can be installed in an enclosure. The G4SA is the only LAN adapter supported for the IOAM enclosure. Although the G4SA implements the Ethernet 4 ServerNet adapter (E4SA), Fast Ethernet ServerNet adapter (FESA), and the Gigabit Ethernet ServerNet adapter (GESA) functions, it cannot be installed in an HP NonStop™ S-series enclosure.

gigabyte (GB). A unit of measurement equal to 1,073,741,824 bytes (1024 megabytes). See also kilobyte (KB), megabyte (MB), and terabyte (TB).

Global Customer Support Center (GCSC). A support organization that provides telephone and remote diagnostic support for HP customers. GCSCs are located all over the world. See also Online Support Center (OSC).


Glossary global offset table (GOT)

global offset table (GOT). A table of indirect addresses of data, including function descriptors, that might reside in a different loadfile.The GOT is an artifact of the native compiler.

globalized. The import-control characteristic of a loadfile that allows it to import symbols from any loadfile in the loadList of the program with which it is loaded. When those loadfiles offer multiple definitions of the same symbol, those loadfiles are searched in loadList sequence, and the first definition found takes precedence. See also searchList.

globally unique ID (GUID). A unique, read-only number stored in nonvolatile memory (SEEPROM) on a ServerNet II Switch at the time of manufacture. The GUID also appears on the bar code label. This number can be used programmatically to identify the switch.

GMS. Group, module, slot CRU or FRU identification scheme.

GOT. See global offset table (GOT).

GPR. See general-purpose register (GPR).

graphical user interface (GUI). A user interface that offers point-and-click access to program functions.

graphics address remapping table (GART). The scatter-gather table used for graphics address remapping functions.

ground. A conducting connection, whether intentional or accidental, between an electrical circuit and either the earth or some conducting body that serves in place of the earth, such as an underground metal water pipe, structural steel, or a ground rod driven into the earth. See also earth ground.

grounded. Connected to earth or to some conducting body that serves in place of the earth.

grounded conductor. A system or circuit conductor that is intentionally grounded.

ground fault. Any undesired current path from a point of differing potential to ground.

ground fault interrupter. A device that interrupts the electric current to the load when a fault current to ground exceeds a predetermined value that is less than that required to operate the overcurrent protection device of the supply circuit.

grounding conductor. A conductor used to connect equipment of the grounded circuit of a wiring system to one or more earth-grounding electrodes. See also earth-grounding electrode.

group. (1) Part of the group, module, slot naming convention for uniquely identifying the logical location of a component within a system. A group is a subset of a system and contains one or more modules. A group does not necessarily correspond to a single


Glossary group database

physical object, such as an enclosure. For example, an HP NonStop™ S-series processor enclosure typically includes only one group number, but a modular cabinet can contain several enclosures that each might belong to different groups. See also module. (2) In the Open System Services (OSS) environment, a set of user IDs with the same group ID.

group database. A database on an Expand node that contains the group name, group ID, and user names for each group using that node.

group ID. The nonnegative integer used to identify a group of users of an Expand node. Each user of a node is a member of at least one group. When the identity of a group is associated with an Open System Services (OSS) process, a group ID value is referred to as one of:

• Real group ID• Effective group ID• Supplementary group ID• Saved-set group ID

group list. An Open System Services (OSS) process attribute that is used with the effective group ID of the process to determine the file access permissions for the process.

GRT. See Guided Replacement Toolkit (GRT).

Guardian. An environment available for interactive or programmatic use with the HP NonStop™ operating system. Processes that run in the Guardian environment usually use the Guardian system procedure calls as their application program interface. Interactive users of the Guardian environment usually use the HP Tandem Advanced Command Language (TACL) or another HP product’s command interpreter. Contrast with Open System Services (OSS).

Guardian environment. The Guardian application program interface (API), tools, and utilities.

Guardian services. An application program interface (API) to the HP NonStop™ operating system, plus the tools and utilities associated with that API. This term is synonymous with Guardian environment. See also Guardian.

Guardian user ID. See HP NonStop™ operating system user ID.

GUI. See graphical user interface (GUI).

GUID. See globally unique ID (GUID).

guided procedure. A software tool that assists you in performing complex configuration or replacement tasks on an HP NonStop™ server. OSM guided procedures are launched through actions in the OSM Service Connection. TSM guided procedures are accessible from the Start menu on your system console. Guided procedures include Replace PMF, IOMF, SNDA, SEB, or MSEB. Some names vary between OSM and


Glossary Guided Replacement Toolkit (GRT)

TSM. For example, Add Node to ServerNet Cluster is the OSM equivalent of Configure ServerNet Node in TSM.

Guided Replacement Toolkit (GRT). A software product that guides you through online replacement of these customer-replaceable units (CRUs) on HP NonStop™ S-series systems: I/O multifunction (IOMF) CRUs, power supplies, processor multifunction (PMF) CRUs, and 6760 ServerNet device adapters. GRT is used only with older versions of TSM server software. If you are replacing a CRU in a system running TSM server version T7945AAX (shipped with G06.13) or later, use the appropriate guided procedure.

hard link. In the Open System Services (OSS) file system, the relationship between two directory entries for the same file. A hard link acts as an additional pointer to a file. A hard link cannot be used to point to a file in another fileset. Contrast with symbolic link.

hard reset. An action performed on an HP NonStop™ Cluster Switch (model 6770) and HP NonStop™ ServerNet Switch (model 6780) that reinitializes the router-2 ASIC within the switch, disrupting the routing of ServerNet messages through the switch for several minutes. When the hard reset is finished, the paths are restored automatically.

harmonic. The sinusoidal component of an alternating-current (AC) voltage that is a multiple of the waveform frequency.

harmonic distortion. Harmonics that change an alternating-current (AC) waveform from sinusoidal to complex.

header. An object that, when specified for inclusion in a program’s source code, causes the program to behave as if the statement including the header were actually a specific set of other programming statements. A header contains coded information that provides details (such as data item length) about the data that the header precedes.

In an Open System Services (OSS) program, a header is the name of a file known to the run-time library used by a process. In a Guardian environment C language program, a header is the file identifier for a file known to the run-time library used by a process.

heat sink. A metal conductor specifically designed to absorb and dissipate excess heat.

HEF. Hardware error freeze.

hertz (Hz). A unit of frequency. One hertz equals one cycle/second.

high frequency. A Federal Communications Commission (FCC) designation for a frequency in the range 30 through 300 megahertz, corresponding to a decametric wave in the range 10 through 100 meters.

high PIN. A process identification number (PIN) that is greater than 255. Contrast with low PIN.


Glossary hop count

hop count. The number of routers that form a route between a ServerNet source and ServerNet destination. Hop count is used to determine the best route. If two alternate routes have the same time factor, the path with the lower hop count is the better route.

host database. An SQL database maintained for the host system and containing information about requests, software inputs, snapshots, targets, and profiles.

host system. (1) A computer system that supports very large databases and does batch processing, usually for an entire network of smaller systems. (2) The central site on which the Distributed Systems Management/Software Configuration Manager (DSM/SCM) is managed, the Archive is maintained, and configuration revisions are built. The host system is also a target system.

HP NonStop™ Cluster Switch (model 6770). An assembly that routes ServerNet messages across an external fabric of a ServerNet cluster. The cluster switch consists of a ServerNet II Switch, an uninterruptible power supply (UPS), and AC transfer switch, and it can be packaged in a switch enclosure or in a 19-inch rack. The cluster switch is used with star, split-star, and tri-star topologies. See also HP NonStop™ ServerNet Switch (model 6780).

HP NonStop™ Open System Services (OSS). The product name for the OSS environment. See also Open System Services (OSS).

HP NonStop™ Kernel operating system. The former name of the operating system for HP NonStop systems. See HP NonStop™ operating system user ID.

HP NonStop™ operating system user ID. A user ID within an HP NonStop system. The Guardian environment normally uses the structured view of this user ID, which consists of either the group-number, user-number pair of values or the group-name.user-name pair of values. For example, the structured view of the super ID is (255, 255). The Open System Services (OSS) environment normally uses the scalar view of this user ID, also known as the UID, which is the value (group-number * 256) + user-number. For example, the scalar view of the super ID is (255 * 256) + 255 = 65535.

HP NonStop™ K-series servers. The set of NonStop servers having product numbers beginning with the letter K. These servers run the HP NonStop Kernel operating system, but they do not implement the ServerNet architecture.

HP NonStop™ Open System Management (OSM) Interface. Identifies software used to manage or service HP NonStop servers.

HP NonStop™ operating system. The operating system for HP NonStop systems.

HP NonStop™ S700 server. A special configuration of HP NonStop S-series server that is limited to one processor enclosure and a maximum of two I/O enclosures. A matched pair of any model of PMF CRU can be used in a NonStop S700 server.


Glossary HP NonStop™ S7000 server

HP NonStop™ S7000 server. The first mid-range server in a product line of HP NonStop S-series servers that implements the ServerNet architecture and runs the HP NonStop operating system.

HP NonStop™ S7400 server. A mid-range HP NonStop S-series server that provides an upgrade option for migrating from an HP NonStop K-series server or a NonStop S7000 server. The NonStop S7400 server is based on the NonStop S72000 technology and supports all NonStop S-series hardware products that are compatible with the NonStop S72000 servers.

HP NonStop™ S7600 server. A mid-range HP NonStop S-series server that is based on the NonStop S74000 technology and supports all NonStop S-series hardware products that are compatible with the NonStop S74000 servers.

HP NonStop™ S7800 server. A mid-range HP NonStop S-series server that is based on the NonStop S76000 technology and supports all NonStop S-series hardware products that are compatible with the NonStop S76000 servers.

HP NonStop™ S70000 server. The first high-performance server in a product line of HP NonStop S-series servers that implements the ServerNet architecture and runs the HP NonStop operating system.

HP NonStop™ S72000 server. The high-performance successor of the NonStop S70000 line of HP NonStop S-series servers.




HP NonStop™ S86000 server. The first premium high-performance server in a product line of HP NonStop S-series servers that implements the ServerNet architecture and runs the HP NonStop operating system.

HP NonStop™ S88000 server. The premium high-performance successor of the NonStop S86000 line of HP NonStop S-series servers.

HP NonStop™ Sxx000 server. Any server in a family of high-performance or premium high-performance HP NonStop S-series servers. This family includes the NonStop S70000, S72000, S74000, S76000, S78000, S86000, and S88000 servers.

HP NonStop™ ServerNet Cluster (ServerNet Cluster). The product name for the collection of hardware and software components that constitute a ServerNet cluster.


Glossary HP NonStop™ ServerNet Switch (model 6780)

HP NonStop™ ServerNet Switch (model 6780). The cluster switch used in the layered topology. The 6780 switch consists of a switch logic board, a midplane, plug-in cards, power supplies, and fans. See also HP NonStop™ Cluster Switch (model 6770).

HP NonStop™ S-series servers. The HP NonStop servers having product numbers beginning with the letter S. These servers implement the ServerNet architecture and run the HP NonStop operating system.

HP NonStop™ servers. The entire line of HP NonStop servers, including NonStop S-series servers.

HP NonStop™ Storage Management Foundation (SMF). A subsystem used by the storage subsystem that facilitates automation of storage management tasks by providing location-independent naming, storage pools, and virtual disks on HP NonStop™ systems.

HP NonStop™ System RISC Model D processor (NSR-D processor). The model designation for the TNS/R processor used in the HP NonStop S7400 server.

HP NonStop™ System RISC Model E processor (NSR-E processor). The model designation for the TNS/R processor used in the HP NonStop S7600 server.

HP NonStop™ System RISC Model G processor (NSR-G processor). The model designation for the TNS/R processor used in the HP NonStop S70000 server.

HP NonStop™ System RISC Model H processor (NSR-H processor). The model designation for the TNS/R processor used in the HP NonStop S78000 server.

HP NonStop™ System RISC Model J processor (NSR-J processor). The model designation for the TNS/R processor used in the HP NonStop S7800 server.

HP NonStop™ System RISC Model T processor (NSR-T processor). The model designation for the TNS/R processor used in the HP NonStop S72000 server.

HP NonStop™ System RISC Model V processor (NSR-V processor). The model designation for the TNS/R processor used in the HP NonStop S74000 server.

HP NonStop™ System RISC Model W processor (NSR-W processor). The model designation for the TNS/R processor used in the HP NonStop S7000 server.

HP NonStop™ System RISC Model X processor (NSR-X processor). The model designation for the TNS/R processor used in the HP NonStop S76000 server.

HP NonStop™ System RISC Model Y processor (NSR-Y processor). The model designation for the TNS/R processor used in the HP NonStop S86000 server.

HP NonStop™ System RISC Model Z processor (NSR-Z processor). The model designation for the TNS/R processor used in the HP NonStop S88000 server.


Glossary HP NonStop™ TCP/IP

HP NonStop™ TCP/IP. The HP implementation of Transmission Control Protocol/Internet Protocol (TCP/IP) for the HP NonStop servers. See also Parallel Library TCP/IP.

HP NonStop™ TCP/IP process. An HP product that supports the Transmission Control Protocol/Internet Protocol (TCP/IP) layers. TCP/IP processes are used together with the communications line interface processor (CLIP) pNA+ to provide the transport layer between wide area network (WAN) I/O processes and data link control (DLC) tasks, between ConMgr and the Simple Network Management Protocol (SNMP) task, between the WANBoot process and BOOTP tasks, and between an OSM or TSM process and a DIAG task.

HP NonStop™ TCP/IP subsystem. A subsystem that allows the use of HP NonStop TCP/IP to access an HP NonStop server host from Macintosh computers, personal computers, and UNIX workstations. Applications running on a NonStop system or in an Expand network can transparently exchange data with NonStop TCP/IP devices.

HP NonStop™ TCP/IPv6. An HP product that adds IP version 6 (IPv6) functionality to the parallel library TCP/IP product. IPv6 is a TCP/IP protocol that extends the IP version 4 (IPv4) of 32 bits to 128 bits. NonStop TCP/IPv6 can be run in three modes: INET (only IPv4 and is a direct replacement for parallel library TCP/IP), INET 6 (only IPv6), and Dual (both IPv4 and IPv6 communications).

HP NonStop™ Technical Library (NTL). The application for accessing, searching, and viewing technical publications and support information for the HP NonStop server. NTL replaces Total Information Manager (TIM).

HP NonStop™ Transaction Management Facility (TMF). HP software that provides transaction protection and database consistency in demanding online transaction processing (OLTP) and decision-support environments. It gives full protection to transactions that access distributed SQL and Enscribe databases, as well as recovery capabilities for transactions, online disk volumes, and entire databases.

HP Tandem Advanced Command Language (TACL). The user interface to the HP NonStop™ operating system. The TACL product is both a command interpreter and a command language. Users can write TACL programs that perform complex tasks or provide a consistent user interface across independently programmed applications.

HP Tandem Failure Data System (TFDS). A diagnostic tool that is a component of the HP NonStop™ operating system. The TFDS tool isolates software problems and provides automatic processor-failure data collection, diagnosis, and recovery services.

HP Transaction Application Language (TAL). A systems programming language with many features specific to stack-oriented TNS systems.

hybrid shared run-time library (hybrid SRL). A shared run-time library (SRL) that has been augmented by the addition of a dynamic section that exports the SRL’s symbols in a form that can be used by position independent code (PIC) clients. A hybrid SRL looks like a dynamic-link library (DLL) to PIC clients (except it cannot be loaded at


Glossary Hz

other addresses and cannot itself link to DLLs). The code and data in the SRL are no different in a hybrid SRL, and its semantics for non-PIC clients are unchanged.

Hz. See hertz (Hz).

I18N. See internationalization.

IBC. See in-band control (IBC).

ICMP. See Internet control message protocol (ICMP).

identifier. A unique name; for example, TANDEM^FILES^TO^COPY; in the CONFTEXT file that refers to a text string (one or more file names as given in the CONFAUX file). When Distributed Systems Management/Software Configuration Manager (DSM/SCM) encounters an identifier, it substitutes the text string for the identifier.

ideogram. See ideograph.

ideograph. A character or symbol representing a word or idea. Some writing systems, such as Japanese and Chinese, use thousands of ideographs. An ideograph is sometimes called an ideogram.

IEC. International Electrotechnical Committee. IEC is a professional organization that creates or adopts standards for computer hardware, environments, and physical interconnections.

IEEE. Institute of Electrical and Electronics Engineers. IEEE is a professional organization whose committees develop and propose computer standards that define the physical and data link protocols of entities such as communication networks.

IEEE 802.3 protocol. Institute of Electrical and Electronics Engineers (IEEE) standard defining the hardware layer and transport layer of (a variant of) Ethernet. The maximum segment length is 500 meters, and the maximum total length is 2.5 kilometers. The maximum number of hosts is 1024. The maximum packet size is 1518 bytes.

IID. See interrupt ID (IID).

impedance. The total opposition (that is, resistance and reactance) a circuit provides to the flow of alternating current at a given frequency.

implementation-defined. Not specified by a standard. A correct value or behavior that is implementation-defined can vary from system to system and therefore might represent a feature or facility that cannot be ported.

implicit library. A library supplied by HP that is available in the read-only and execute-only globally mapped address space shared by all processes without being specified to the linker or loader. See also TNS system library and public library.


Glossary implicit library import library (imp-imp)

implicit library import library (imp-imp). See import library.

implied user library. A method of binding TNS object files that have more than 16 code segments. Segments 16 through 31 are located in the user code (UC) space but are executed as if they were segments 0 through 15 of the user library (UL) code space. This method precludes the use of a user library. Binder now supports 32 segments of UC space concurrently with 32 segments of UL code space, so the implied user library method is not needed in new or changed TNS applications.

import. To refer to a symbol definition from another loadfile. A loadfile imports a symbol definition when it needs a data item or function having that symbolic name.

import control. The characteristic of a loadfile that determines from which other loadfiles it can import symbol definitions. The programmer sets a loadfile’s import control at link time. That import control can be localized, globalized, or semiglobalized. A loadfile’s import control governs the way the linker and loader construct that loadfile’s searchList and affects the search only for symbols required by that loadfile.

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 TSM or OSM 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™ 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 field-replaceable unit (FRU) or 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.


Glossary initial discovery

initial discovery. Discovery of an HP NonStop™ 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.

inode number. A unique identifier within the Open System Services (OSS) file system of an instance of an OSS file. The inode number identifies the instance within the file system catalogs.

input/output process (IOP). A running program (part of the HP NonStop™ operating system) that manages the I/O functions for one or more ServerNet addressable controllers (SACs) of the same type.

input source. The resource from which Subsystem Control Facility (SCF) accepts command input. SCF can accept input from a terminal or a disk file. The initial input source is determined by the form of the RUN command used to initiate SCF. At any time during an SCF session, the input source can be temporarily changed to execute a series of commands from a command file.

inrush current. The initial surge current demand of a load.

Inspect region. The region of a TNS object file that contains symbol tables for all blocks compiled with the SYMBOLS directive. The Inspect region is sometimes called the symbols region.

INSPSNAP. The program that provides a process snapshot file for the Inspect subsystem.

installation subvolume (ISV). A subvolume containing files that perform a specific function during the installation process, such as organizing documentation in a specific location, providing the components of the HP NonStop™ operating system image (OSIMAGE), and containing files that are used after the installation process.

installer. The person who installs the system equipment for a new system. This person also installs new equipment when additions are made to the system. This person can install software and perform system verification procedures as directed by the system planner, configuration planner, or support planner.


Glossary instruction processing unit (IPU)

instruction processing unit (IPU). A processing unit that executes programs by fetching instructions from memory and executing them.

insulated ground. A grounding conductor with a dielectric (low-conductance) insulator around it to prevent inadvertent contact with metal conduits.

intelligent SCSI processor (ISP). The ServerNet addressable controller (SAC) that controls the small computer system interface (SCSI) bus.

interactive mode. A mode of operation that is characterized by having the same input and output device (a terminal or a process) for the session. If a terminal is used, a person enters a command and presses Return. If a process is used, the system interface waits for the process to send a request and treats the process in the same manner as a terminal. Contrast with noninteractive mode.

internal routing. The routing of packets within an HP NonStop™ server. See also external routing.

internal ServerNet fabrics. The fabrics that link ServerNet devices within an HP NonStop™ server. See also external ServerNet fabrics.

internal ServerNet X or Y fabric. The X or Y fabric that links ServerNet devices within an HP NonStop™ server. See also fabric.

internationalization. The process of designing and coding software so that it can be adapted to meet the needs of different languages, cultures, and character sets, with the ability to handle various linguistic and cultural conventions. Internationalization methods enable the processing of character-based data independently of the underlying character encoding, allowing choice among character sets. Sometimes referred to as I18N, derived from the 18 letters between the initial I and the final N of the word internationalization. See also character set.

Internet address. The 32-bit address assigned to hosts that want to participate in the Internet using Transmission Control Protocol/Internet Protocol (TCP/IP). Internet addresses are an abstraction of physical hardware addresses, just as the Internet is an abstraction of physical networks. As assigned to the interconnection of a host to a physical network, an Internet address consists of a network portion and a host portion. See also IP address.

Internet control message protocol (ICMP). A maintenance protocol in the Transmission Control Protocol/Internet Protocol (TCP/IP) suite that is required in every TCP/IP implementation. The ICMP allows two nodes on an IP network to share IP status and error information. The ICMP is used by the ping utility to determine the readability of a remote system. See also IP address and ping.

Internet protocol (IP). A data communications protocol that handles the routing of data through a network, which typically consists of many different subnetworks. IP is connectionless. It routes data from a source address to a destination address. See also IP address.


Glossary interoperability

interoperability. (1) Within an Expand node, the ability to use the features or facilities of one environment from another. For example, the gtacl command in the Open System Services (OSS) environment allows an interactive user to start and use a Guardian tool in the Guardian environment. (2) Among systems from multiple vendors or with multiple versions of operating systems from the same vendor, the ability to exchange status, files, and other information. Product externals and end-user publications for NonStop servers often use the term connectivity in this context. See also connectivity.

interpreted mode. See TNS interpreted mode.

interprocessor communications (IPC). The exchange of messages between processors.

interrupt ID (IID). The identification of an external interrupt.

intrinsic library. See Shared Millicode Library.

instance. A particular case of a class of items or objects. For example, a process is defined as one instance of the execution of a program. Multiple processes might be executing the same program simultaneously. Also, instance data refers to global data of a program or library. Each process has its own instance of the data.

instance data. For each process using a dynamic-link library, a data segment area containing the global variables used by the library.

I/O adapter module (IOAM). A collection of modular components that provides I/O connectivity and can include ServerNet switch boards, Fibre Channel ServerNet adapters (FCSAs), fans, and power supplies. In the IOAM, each module is a logical entity that represents a single service domain.

I/O adapter module (IOAM) enclosure. The sheet-metal carrier that is installed in a 19-inch rack and contains the IOAM components.

IOAM. See I/O adapter module (IOAM).

IOAM enclosure. See I/O adapter module (IOAM) enclosure.

I/O cabinet. See I/O enclosure.

I/O controller. The hardware logic that controls computer I/O operations for a particular set of devices, such as disks, tapes, terminals, or communications lines. See also ServerNet addressable controller (SAC).

I/O enclosure. An HP NonStop™ S-series system enclosure containing one module, which includes ServerNet adapters, disk drives, components related to the ServerNet fabrics, and components related to electrical power and cooling for the enclosure. An I/O enclosure is identical to a processor enclosure except that it contains I/O multifunction (IOMF) customer-replaceable units (CRUs) instead of processor multifunction (PMF) CRUs.


Glossary IOMF CRU

IOMF CRU. See I/O multifunction (IOMF) CRU.

IOMF 2 CRU. See I/O multifunction (IOMF) 2 CRU.

I/O multifunction (IOMF) CRU. (1) An HP NonStop™ S-series customer-replaceable unit (CRU) that connects an I/O enclosure to a processor enclosure through a ServerNet cable and supplies power to the components within the IOMF CRU as well as redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that enclosure. The IOMF CRU contains a power supply, a service processor (SP), a ServerNet router, an Ethernet controller, an external ServerNet port, and three SCSI ServerNet addressable controllers (S-SACs) in a single unit. (2) A collective term for both IOMF CRUs and IOMF 2 CRUs when a distinction between the two types of CRUs is not required.

I/O multifunction (IOMF) 2 CRU. An HP NonStop™ S-series customer-replaceable unit (CRU) that connects an I/O enclosure to a processor enclosure through a ServerNet cable and supplies power to the components within the IOMF 2 CRU as well as redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that enclosure. The IOMF 2 CRU contains a power supply, a service processor (SP), a ServerNet router 2, an Ethernet controller, three configurable ServerNet ports, and three SCSI ServerNet addressable controllers (S-SACs) in a single unit.

IOP. See input/output process (IOP).

IP. See Internet protocol (IP).

IP address. An address that uniquely identifies a specific host system within a network to the Internet protocol (IP). An IP address consists of two parts: a network address, which identifies the network, and a local address, which identifies the host within the network. IP routes data between source and destination IP addresses.

IPC. See interprocessor communications (IPC).

IPU. See instruction processing unit (IPU).

ISO. International Organization for Standardization. ISO is an international body that drafts, discusses, proposes, and specifies standards for network protocols. ISO is best known for its seven-layer reference model that describes the conceptual organization of protocols.

ISO is sometimes called the International Standards Organization. Although ISO is the official abbreviation, it does not correspond to the organization’s name in any language.

ISO 646. An ISO standard for representing characters in languages based on the Roman alphabet. Like ASCII, ISO 646 uses only 7 bits of each 8-bit byte to represent data. Contrast with ISO 8859.


Glossary ISO 8859

ISO 8859. A series of ISO standard 8-bit code sets used to represent languages based on many alphabets, including Roman, Greek, Cyrillic, Hebrew, Turkish, and Arabic. The ISO 8859 code sets are used in international applications that must be data transparent. ASCII is a subset of each of the ISO 8859 code sets.

ISO 10646. A universal coded character set that represents all characters and symbols from all commonly used scripts and languages.

ISO/IEC-conforming POSIX.1 application. An application that both:

• Uses only the facilities described in ISO/IEC IS 9945-1:1990 and approved conforming language bindings for any ISO or IEC standard

• Is documented as using only those facilities and approved conforming language bindings

isolated ground. A grounding conductor that directly connects the equipment ground through an isolated ground-type receptacle with the power system grounding point without any intermediate grounding points.

isolation transformer. A transformer containing electrostatic shields between the primary and secondary windings, with no direct electrical path between the primary and secondary windings.

ISP. See intelligent SCSI processor (ISP).

ISV. See installation subvolume (ISV).

JDS box. See ServerNet extender module (SEM).

job control. The Open System Services (OSS) features that allow processes to be stopped, continued, and moved from or to the background.

KB. See kilobyte (KB).

Kernel subsystem. In G-series release version updates (RVUs), the subsystem for configuration and management of the Subsystem Control Facility (SCF) subsystem managers that are generic processes, some system attributes, and the ServerNet X and Y fabrics.

Kernel subsystem manager process. The generic process that starts and manages other generic processes, some system attributes, and the ServerNet X and Y fabrics in G-series release version updates (RVUs). The $ZZKRN Kernel subsystem manager process is started and managed by the $ZPM persistence manager process.

keyword. A character sequence recognized by a command process.

kilobyte (KB). A unit of measurement equal to 1024 bytes. See also gigabyte (GB), megabyte (MB), and terabyte (TB).


Glossary K-series servers

K-series servers. See HP NonStop™ K-series servers.

L10N. See localization.

labeled dump. A token-by-token display-text representation of the Subsystem Programmatic Interface (SPI) command buffer or response buffer, as produced by the Subsystem Control Facility (SCF) commands DETAIL CMDBUFFER and DETAIL RSPBUFFER. The display text includes a labeled value for each token.

LAN. See local area network (LAN).

LANMAN. See LAN manager (LANMAN) process.

LAN manager (LANMAN) process. The process provided as part of the ServerNet local area network (LAN) Systems Access (SLSA) subsystem that starts and manages the SLSA subsystem objects and the LAN monitor (LANMON) process and assigns ownership of Ethernet adapters to the LANMON processes in the system. Subsystem Control Facility (SCF) commands are directed to the LANMON processes for configuring and managing the SLSA subsystem and the Ethernet adapters.

LANMON. See LAN monitor (LANMON) process.

LAN monitor (LANMON) process. The process provided as part of the ServerNet local area network (LAN) Systems Access (SLSA) subsystem that has ownership of the Ethernet adapters controlled by the SLSA subsystem.

late binding. At load time, binding a symbolic reference in a dynamic-link library (DLL) to a definition in a loadfile that appears on the program’s loadList rather than the one found on the DLL’s linker searchList. Late binding occurs in either of these cases:

• The loader resolves a symbol that is unresolved by any loadfile on the linker searchList.

• The loader binds a symbol in a DLL to the first definition it finds on the program’s loadList, and this is not the first definition that was encountered on the linker searchList.

For localized loadfiles, the linker and loader searchLists are the same, so late binding does not occur.

layer number. See cluster switch layer number.

layered topology. The network topology for ServerNet clusters using the HP NonStop™ ServerNet Switch (model 6780). The layered topology can scale by adding cluster switch layers or zones. The layered topology supports up to four layers and three zones. See also star topology, split-star topology, and tri-star topology.

LB. See logical network partitioning.


Glossary LC-LC cable

LC-LC cable. A multimode fiber cable that connects a Fibre Channel ServerNet adapter (FCSA) to a Fibre Channel storage device or a Fibre Channel switch (FC switch).

LC-SC cable. A multimode fiber cable that connects a modular ServerNet expansion board (MSEB) to an I/O adapter module (IOAM) or a Fibre Channel switch (FC switch).

ldev. See logical device number (ldev).

LDEV. Logical device. The HP term for a disk in the Enterprise Storage System (ESS).

ld utility. A utility that collects, links, and modifies code and data blocks from one or more position-independent code (PIC) object files to produce a target TNS/R native object file. See also nld utility.

LED. See light-emitting diode (LED).

legacy system. An operating system that is not open but from which applications must be ported or users transferred.

libList. The list of libraries to be loaded along with a loadfile. When linking the loadfile, the linker constructs the libList from the names of libraries specified in the linker’s command stream. It stores the libList within the loadfile.

library. A generic term for a collection of routines useful in many programs. An object code library can take the form of a linkfile to be physically included into client programs, it can be an OSS archive file containing several linkable modules, it can be a loadfile, or it can be a system-managed collection of preloaded routines. Source-code libraries fall outside the scope of this glossary. See also dynamic-link library (DLL) and shared run-time library (SRL).

library client. A program or another library that uses routines or variables from that library.

library file. See library.

library import characterization (LIC). A list of the export digests and relocation offsets of all the libraries used to resolve symbols in a loadfile. It allows the loader and operating system to determine when a file is being loaded in an environment equivalent to that found by the linker or to a previous load. (See fastLoad.) A LIC is generated and stored in the loadfile by the linker when a file is preset; it can be used in a subsequent load step to determine whether the loadfile’s existing bindings can be reused. The operating system can also retain the bindings as modified when a loadfile is loaded and associate a LIC with those cached bindings, so that they can be reused when the same file is again loaded in an equivalent environment. (See cached bindings.)

LIC. See library import characterization (LIC).

LIF. See logical interface (LIF).


Glossary light-emitting diode (LED)

light-emitting diode (LED). A semiconductor device that emits light from its surface. Indicator lights are composed of LEDs. See also indicator lights.

line. The specific hardware path over which data is transmitted or received. A line can also have a process name associated with it that identifies an input/output process (IOP) or logical device associated with that specific hardware path.

linear load. Electrical loads for which the impedance is constant regardless of the voltage, so that if the voltage is sinusoidal, the current drawn is also sinusoidal.

line-handler process. See Expand line-handler process or Expand-over-ServerNet line-handler process.

line interface unit (LIU). A dual-ported unit consisting of two parts: a communications line interface processor (CLIP) and a line interface module (LIM). An LIU can communicate with either the primary or the backup processor, providing fault tolerance. When it is a component of the communications subsystem, an LIU communicates with either processor through either of a pair of communications interface units (CIUs).

link. In the Open System Services (OSS) file system, a directory entry for a file.

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 ld or nld utility. (2) A file containing object code that is not yet ready to load and execute. Linkfiles are combined by means of a linker 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).


Glossary LMU

LMU. See logical memory unit (LMU).

load. (1) To transfer the HP NonStop™ 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.

loadfile. An executable object code file that is ready for loading into memory and executing on the computer. Loadfiles are further classified as executable programs (containing a main routine at which to begin execution of that program) or executable libraries (supplying routines or variables to multiple programs or separately loaded libraries). A TNS code file might be both a loadfile and a linkfile. Native code files are never both. Contrast with linkfile.

loadList. A list of all the libraries that must be loaded for a given loadfile to execute. A loadfile’s loadList includes all the libraries in the given loadfile’s libList plus all the libraries in those loadfiles’ libLists, and so forth. It does not include the implicit libraries. The loadList order is the sequence in which these loadfiles are to be loaded when they are not already loaded by a previous operation. The loadList of the program includes all the loadfiles present in the process, in the order they were loaded.

local area network (LAN). A network that is located in a small geographical area and whose communications technology provides a high-bandwidth, low-cost medium to which low-cost nodes can be connected. One or more LANs can be connected to the system such that the LAN users can access the system as if their workstations were connected directly to it. Contrast with wide area network (WAN).

locale. In localization, the definition of the subset of a user’s environment that depends on language and cultural conventions.

localization. The process of adapting computer interfaces, data, and documentation to the culturally accepted way of presenting information in the culture. Sometimes referred to as L10N, derived from the 10 letters between the initial L and the final N of the word localization.

localized. The import-control characteristic of a loadfile that allows it to import symbols only from the loadfile itself followed by the libraries in its libList, libraries that those libraries


Glossary local mount

reexport, and from these, any successions of reexported libraries. See also libList and searchList.

local mount. In the Network File System (NFS), a mount that attaches the fileset associated with a server to the specified mount point within the local directory hierarchy. The local mount is visible within the NFS subsystem and makes the files associated with the server available through the path associated with the local mount point.

local node. See local system.

local operator. The person who performs routine system operations, such as starting and stopping the system, loading and unloading tapes, and changing the air filter. The local operator is normally the operator of the asynchronous system console for the node. See also operator.

local processor. A processor in the same node as the ServerNet cluster monitor process (SNETMON) that is reporting status about the processor.

local system. (1) An on-site system or a system that is geographically near the user or operator. (2) From the perspective of a particular SNETMON, the system or node on which that SNETMON is running. (3) From the perspective of a system console operator, the system to which the operator is logged on. Contrast with remote system.

logic board (LB). (1) See cluster switch logic board. (2) A printed wiring assembly (PWA) on which computer circuits (chips and wiring) are mounted. One type of logic board is a processor and memory board (PMB). Another type is a multifunction I/O board (MFIOB).

logical device name. The name assigned to an I/O process during its configuration. Other processes use the logical device name when issuing Guardian procedure calls to the I/O process.

logical device number (ldev). For a device or named process, the index into the destination control table (DCT); or more precisely, into the named resource list (NRL). Each device or named process in the system has an ldev.

logical disk volume. A hardware device or device pair that provides persistent, highly accessible storage for data on a medium that is either magnetic or optical.

logical interface (LIF). A process that allows an application or another process to communicate with data communications hardware.

logical memory unit (LMU). A group of four memory units on an HP NonStop™ S-series processor and memory board. Memory on a processor and memory board (PMB) is divided into two LMUs. One LMU contains memory units in slots MS1 through MS4. The other LMU contains memory units in slots MS5 through MS8. An LMU must have memory units installed either in all of its slots or in none of its slots. See also memory unit.


Glossary logical segment

logical segment. A single data area consisting of one or more consecutive 128-kilobyte unitary segments that is dynamically allocated by a process. The two types of logical segments are selectable segments and flat segments. See also selectable segment and flat segment.

logical network partitioning. An HP NonStop™ TCP/IPv6 feature that allows you to divide the system into separately addressed IP subnetworks whereby applications have access only to a defined set of network interfaces (IP addresses).

logical unit number (LUN). (1) A unique number used on a SCSI bus to differentiate between devices on the bus. (2) The logical unit in the Enterprise Storage System (ESS) that maps the LDEV onto a port. Specification of the port and LUN specifies an LDEV.

login. The activity by which a user establishes a locally authenticated identity on a server. Each login has one login name.

login name. A user name associated with a session.

logon sequence. The process through which the HP NonStop™ server to be managed is determined, the security constraints to interact with that server are met, and a connection with that server is established.

low-level link. A connection between the OSM or TSM client software running on a system console and the master service processors (MSPs) on an HP NonStop™ S-series server. When the HP NonStop operating system is not running, communication must take place over a low-level link. You can also communicate with a NonStop S-series server over a low-level link when the operating system is running. See also service connection.

low PIN. A process identification number (PIN) that is in the range 0 through 254. Contrast with high PIN.

LUN. See logical unit number (LUN).

MAC address. See media access control (MAC) address.

MAF. See missed address file (MAF).

main bonding jumper. The connection between the grounded circuit conductor and the equipment grounding conductor at the service.

main memory. Data storage, specifically the chips that store the programs and data currently in use by a processor.

main service entrance. The enclosure containing connection panels and switchgear, located at the point where the utility power lines enter the building.


Glossary maintenance entity

maintenance entity. A processing entity in a single HP NonStop™ system that collects state information, environmental information, and failure data about the system resource or resources for which the maintenance entity is responsible. A maintenance entity can include both physical and software components, and a system can contain multiple maintenance entities. For example, each I/O adapter module (IOAM) has its own maintenance entity.

Maintenance Interface. See Archive and Database Maintenance Interface.

maintenance switch. The Ethernet switch that links the maintenance entities in various modular components to the HP NonStop™ Open System Management (OSM) Interface.

management process. A process through which an application issues commands to a subsystem. A management process can be part of a subsystem, or it can be associated with more than one subsystem. In the latter case, the management process is logically part of each subsystem. Subsystem Control Point (SCP) is the management process for all subsystems controlled by Subsystem Control Facility (SCF).

manager. (1) For an HP NonStop™ system, the person responsible for day-to-day monitoring and maintenance tasks associated with a software subsystem on an Expand node. (2) For a UNIX system, any person in Management and Information Services management for the site.

man page. A term sometimes used in UNIX documentation for the online or hard-copy version of a file that provides reference information. See reference page.

master. The processor providing the results to a computation, which are externalized by a processor board.

master service processor (MSP). A service processor (SP) in HP NonStop™ S-series servers that provides the basic service processor functions as well as centralized system functions such as a console port, a modem port for remote support functions, and system-load control. The enclosure containing processors 0 and 1 (group 01) also contains a pair of MSPs. See also expansion service processor (ESP).

MB. See megabyte (MB).

MCA. Maintenance console entity.

ME. See maintenance entity.

Measure. A tool used for monitoring the performance of HP NonStop™ servers. Measure can be used to check the performance of a ServerNet cluster.

media access control (MAC) address. A value in the Medium Access Control sublayer of the IEEE/ISO/ANSI local area network (LAN) architecture that uniquely identifies an individual station implementing a single point of physical attachment to a LAN.


Glossary Media Interface Connector (MIC)

Media Interface Connector (MIC). A type of head on a fiber-optic cable that has locking wings on the sides.

megabyte (MB). A unit of measurement equal to 1,048,576 bytes (1024 kilobytes). See also gigabyte (GB), kilobyte (KB), and terabyte (TB).

member. In a structured programming language, an addressable entry within a data structure. A member can be a simple field or a data structure.

memory-exact point. A potential breakpoint location within an accelerated object file at which the values in memory (but not necessarily the values in registers) are the same as they would be if the object file were running in TNS interpreted mode or on a TNS system. Most source statement boundaries are memory-exact points. Complex statements might contain several such points: at each function call, privileged instruction, and embedded assignment. Contrast with register-exact point and nonexact point.

memory manager. An HP NonStop™ operating system process that implements the paging scheme for virtual memory. This process services requests generated by different interrupt handlers as well as by other system processes.

memory page. A unit of virtual storage. In TNS systems, a memory page contains 2048 bytes. In TNS/R systems, the page size is determined by the memory manager and can vary, depending on the processor type.

memory slot. A physical, labeled space for a memory unit or a dual inline memory module (DIMM). Memory slots are located on the processor board of an HP NonStop™ S-series processor multifunction (PMF) customer-replaceable unit (CRU).

memory unit. A unit consisting of a dual inline memory module (DIMM) or a single inline memory module (SIMM) that is installed in groups of four on the processor and memory board (PMB) of the processor multifunction (PMF) customer-replaceable unit (CRU) in an HP NonStop™ S-series server. Memory units constitute the processor memory. The memory units in certain models of PMF CRU are not replaceable by customers or in the field.

message monitor process (MSGMON). A helper process for the ServerNet cluster monitor process (SNETMON) that runs in each processor on every node of a ServerNet cluster. MSGMON is started by the persistence manager process, $ZPM. It performs duties for SNETMON in those instances where SNETMON needs an agent in each system processor. In addition, MSGMON monitors the connections within the processor and reports changes back to SNETMON when required.

method. An object-oriented term for a function, procedure, or routine.

MFIOB. See multifunction I/O board (MFIOB).

MIC. See Media Interface Connector (MIC).


Glossary microcode

microcode. Any machine code or data that can run in a microprocessor. HP produces two types of microcode for HP NonStop™ systems: volatile and nonvolatile. Volatile microcode is loaded into the volatile random-access memory (RAM) of some types of printed wiring assemblies (PWAs) and is not retained in a host PWA when power to the PWA is interrupted. For nonvolatile microcode, see firmware. See also millicode.

midplane. A board that has connectors, on one or both sides of the board, into which circuit board assemblies plug. Midplanes are located inside enclosures.

millicode. The system’s lowest-level machine-dependent code, often coded in assembler language. TNS/R millicode is functionally similar to the microcode on TNS systems. The system has several types of millicode, including machine interrupt handlers, operating system primitives, routines implicitly called from native-compiled code, emulators for TNS floating-point arithmetic, and emulators for privileged-only or long-running TNS machine operations.

MIPS Computer Systems, Incorporated. RISC processor manufacturer.

MIPS region of a TNS object file. The region of a TNS object file that contains MIPS instructions and the tables necessary to execute the instructions in accelerator mode on a TNS/R system. Accelerator creates this region and writes it into the TNS object file.

MIPS RISC instructions. Register-oriented 32-bit machine instructions in the MIPS-1 RISC instruction set that are native to and directly executed on TNS/R systems. MIPS RISC instructions do not execute on TNS systems. Contrast with TNS instructions.

Accelerator-generated MIPS RISC instructions are produced by accelerating TNS object code. Native-compiled MIPS RISC instructions are produced by compiling source code with a TNS/R native compiler.

MIPS RISC word. An instruction-set-defined unit of memory. A MIPS RISC word is 4 bytes (32 bits) wide, beginning on any 4-byte boundary in memory. Contrast with TNS word and word.

mirrored disk or volume. A pair of identical disk drives that are used together as a single logical volume. One drive is considered primary, and the other is called the mirror. Each byte of data written to the primary drive is also written to the mirror drive. If the primary drive fails, the mirror drive can continue operations. See also volume.

missed address file (MAF). A file used by the HP NonStop™ operating system during memory caching operations.

MMF PIC. See multimode fiber-optic (MMF) plug-in card (PIC).

MMF ServerNet cable. See multimode fiber-optic (MMF) ServerNet cable.

MO. Maintenance orchestrator.


Glossary mode

mode. The set of attributes that specify the type and access permissions for a file. See also file mode.

modular cabinet. A cabinet with an integrated 19-inch rack equipped with a power distribution unit (PDU), doors, slides, brackets, castors, leveling pads, and optional side panels. See also cabinet.

modular I/O. An I/O system that uses I/O adapter modules and provides direct I/O connectivity for all processors in the core tetrahedron. See also I/O adapter module (IOAM).

modular ServerNet expansion board (MSEB). A ServerNet expansion board (SEB) that uses plug-in cards (PICs) to provide a choice of connection media for routing ServerNet packets.

modular system. A complete server system in which processors, storage, input/output components, and interconnect components are separate, self-contained, replaceable modules. A modular system occupies one or more racks and allows independent evolution and optimization of each kind of module.

module. (1) Part of the group, module, slot naming convention for uniquely identifying the logical location of a component within a system. A module is a subset of a group, and it is usually contained in an enclosure. A module contains one or more slots. A module can consist of components sharing common interconnect, such as a backplane, or it can be a logical grouping of components performing a particular function. See also group. (2) A set of I/O devices or services that share a common protocol and can be controlled by a single module driver in the extensible I/O (XIO) subsystem.

MON object type. The Subsystem Control Facility (SCF) object type for the storage pool master process.

mount. To make a fileset accessible to the users of an Expand node.

mount point. In the Open System Services (OSS) file system, a directory that contains a mounted fileset. The mounted fileset can be in a different file system.

MRouter. A field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC) that is part of the serial maintenance bus (SMB) architecture for HP NonStop™ S-series enclosures. The MRouter distributes the SMB throughout a group.

MSEB. See modular ServerNet expansion board (MSEB).

MSEB CBB. See MSEB common base board (CBB).

MSEB common base board (CBB). In modular ServerNet expansion boards (MSEBs), the printed wiring assembly (PWA) that plug-in cards (PICs) are installed on.


Glossary MSEB port

MSEB port. A connector on modular ServerNet expansion boards (MSEBs) used for ServerNet links. An MSEB has four fixed serial-copper ports and six plug-in card (PIC) slots that accept a variety of connection media. See also SEB port.

MSGMON. See message monitor process (MSGMON).

MSIO. Modular storage I/O.

MSP. See master service processor (MSP).

multifunction I/O board (MFIOB). A ServerNet adapter that contains ServerNet addressable controllers (SACs) for SCSI and Ethernet; a service processor; ServerNet links to the processor, to the two ServerNet adapter slots, and to one of the ServerNet expansion board (SEB) slots; and connections to the serial maintenance bus (SMB), which connects components within an enclosure to the service processor.

multilane link. A communication link between HP NonStop™ Cluster Switches that can consist of multiple ServerNet cables. Two-lane links and four-lane links are examples of multilane links.

multimode fiber-optic (MMF) plug-in card (PIC). A plug-in card (PIC) that supports the multimode fiber-optic (MMF) interface.

multimode fiber-optic (MMF) ServerNet cable. A fiber-optic cable that either allows more than one mode to propagate or supports propagation of more than one mode of a given wavelength. MMF ServerNet cable typically supports shorter transmission distances than single-mode fiber-optic (SMF) ServerNet cable.

multiplexed. The action of separating data traffic from one line onto several distinct lines or of combining data traffic from several distinct lines onto one line.

mutex. See mutual exclusion (mutex).

mutual exclusion (mutex). An operating mode with interrupts disabled.

NAM. See Network Access Method (NAM).

named resource list (NRL). A table that contains one entry for each device and named process in the system. A logical device number (ldev) is an NRL index.

national-standards-body conforming POSIX.1 application. An application that both:

• Uses only the facilities described in ISO/IEC IS 9945-1:1990 and approved standards of a specific member of the ISO or IEC (the national standards body)

• Documents use of only those facilities and approved standards and documents all options and dependencies on limits

native. An adjective that can modify object code, object file, process, procedure, and mode of process execution. Native object files contain native object code, which directly uses


Glossary native-compiled MIPS RISC instructions

MIPS instructions and the corresponding conventions for register handling and procedure calls. Native processes are those created by executing native object files. Native procedures are units of native object code. Native mode execution is the state of the process when it is executing native procedures.

native-compiled MIPS RISC instructions. See MIPS RISC instructions.

native-compiled RISC instructions. See MIPS RISC instructions.

native link editor. See ld utility or nld utility.

native mode. See TNS/R native mode.

native-mode code. Object code that has been compiled with TNS/R native compilers to run on TNS/R systems.

native-mode library. A native-compiled loadfile associated with one or more other native-compiled loadfiles. A native mode process can have any number of associated native-mode libraries. See also TNS library and TNS/R library.

native-mode source code. High-level language routines that can be compiled with TNS/R native compilers.

native object code. See TNS/R native object code.

native object file. See TNS/R native object file.

native object file tool. See noft utility.

native process. See TNS/R native process.

native signal. See TNS/R native signal.

native system library. Synonym for implicit library.

$NCP. The process name of the network control process.

NEC. National Electrical Code.

net list. The definition of integrated-circuit signal (other than a power or clock signal) interconnections.

network. Two or more computer systems (nodes) connected so that they can exchange information and share resources. See also Expand network, wide area network (WAN), and local area network (LAN).

Network Access Method (NAM). The interface through which an Expand-over-ServerNet line-handler process communicates with the ServerNet cluster monitor process (SNETMON).


Glossary network control process

network control process. A process pair, named $NCP, that runs in each system of an Expand network. $NCP establishes and terminates system-to-system connections, maintains network-related system tables (including the network routing table, NRT), calculates the most efficient way to transmit data to other systems in the network, monitors and logs changes in the status of the network and its systems, informs $NCPs at neighbor systems of changes in line or Expand line-handler process status, and aborts pending requests when all paths go down. See also network routing table (NRT).

Network Information Service (NIS). A distributed name service (formerly known as Yellow Pages) developed by Sun Microsystems. See also Domain Name System (DNS).

network routing table (NRT). A table that resides in each processor in each system in a network. The NRT associates each destination system with the logical device (LDEV) number of the best-path route Expand line-handler process to use to send messages to that system. See also network control process.

network topology. The physical layout of components that define a system, a local area network (LAN), or a wide area network (WAN).

neutral. (1) The conductor used as the primary return for current during normal operation of electrical equipment. (2) The junction of the legs in a wye circuit. See also wye. (3) Generally at ground potential.

NIS. See Network Information Service (NIS).

nld utility. A utility that collects, links, and modifies code and data blocks from one or more object files to produce a target TNS/R native object file. See also ld utility.

NNA. See node-numbering agent (NNA).

NNA PIC. See node-numbering agent (NNA) plug-in card (PIC).

node. (1) A uniquely identified computer system connected to one or more other computer systems in a network. See also Expand node and ServerNet node. (2) An endpoint in a ServerNet fabric, such as a processor or ServerNet addressable controller (SAC).

node number. A number used to identify a member system in a network. The node number is usually unique for each system in the network. See also node and ServerNet node number.

node-numbering agent (NNA). A field-programmable gate array (FPGA) in a single-mode fiber-optic (SMF) plug-in card (PIC) that translates the node number of each ServerNet packet entering or exiting the external ServerNet fabrics.

node-numbering agent (NNA) plug-in card (PIC). A plug-in card (PIC) for the modular ServerNet expansion board (MSEB) that supports the node-numbering agent (NNA) interface.


Glossary node routing ID

node routing ID. See ServerNet node routing ID.

noft utility. A utility that reads and displays information from TNS/R native object files.

noncanonical input mode. For an Open System Services (OSS) process, a terminal input mode in which data is made available to the process when a timer expires or when a certain number of characters have been entered. Noncanonical data is not grouped into logical lines of input. This mode is sometimes called block mode or transparent mode. Contrast with canonical input mode.

nonclustered. Lacking the quality of belonging to a cluster.

nonconfigured object. An object that comes into existence after Subsystem Control Facility (SCF) is running and that was created in response to activity outside the SCF environment. An SCF STATUS command can display the name of a nonconfigured object, but its state is UNKNOWN.

nondedicated (public) LAN. A local area network (LAN) connected to the Ethernet ports on an Ethernet 4 ServerNet adapter (E4SA), Fast Ethernet ServerNet adapter (FESA), or Gigabit Ethernet ServerNet adapter (GESA). Unlike a dedicated service LAN, a public LAN supports the connection of many types of servers and workstations. System consoles can be connected to a public LAN, but such system consoles cannot use all the OSM or TSM client applications. See also dedicated service LAN.

nonessential firmware. Code that is used for support routines such as self-test diagnostics and that can be overwritten during flash programming without affecting the next power-up operation. Contrast with essential firmware.

nonexact point. A code location within an accelerated object file that is between memory-exact points. The mapping between the TNS program counter and corresponding RISC instructions is only approximate at nonexact points, and interim changes to memory might have been completed out of order. Breakpoints cannot be applied at nonexact points. Contrast with memory-exact point and register-exact point.

noninteractive mode. A mode of operation that usually involves a command file (an EDIT file that contains a series of commands). Contrast with interactive mode.

nonlinear load. Electrical load for which the instantaneous current is not proportional to the instantaneous voltage. Consequently, the local impedance varies with the voltage.

nonsensitive command. A command that can be issued by any user or program that is allowed access to a subsystem—that is, a command on which the subsystem imposes no further security restrictions. For Subsystem Control Facility (SCF), nonsensitive commands are those that cannot change the state or configuration of objects; most of them are information commands. Contrast with sensitive command.

NonStop™ Cluster Switch. See HP NonStop™ Cluster Switch (model 6770).

NonStop™ Kernel operating system. See HP NonStop™ operating system.


Glossary NonStop™ Series TNS

NonStop™ Series TNS. See TNS.

NonStop™ Series TNS/R. See TNS/R.

NonStop™ ServerNet Cluster. See HP NonStop™ ServerNet Cluster (ServerNet Cluster).

NonStop™ ServerNet Switch. See HP NonStop™ ServerNet Switch (model 6780).

NonStop™ TCP/IP. See HP NonStop™ TCP/IP.

NonStop™ TCP/IP process. See HP NonStop™ TCP/IP process.

NonStop™ TCP/IP subsystem. See HP NonStop™ TCP/IP subsystem.

NonStop™ TCP/IPv6. See HP NonStop™ TCP/IPv6.

NonStop Technical Library. See HP NonStop™ Technical Library (NTL).

normal mode. Electromagnetic interference that occurs between current-carrying conductors (for example, line to neutral).

notification. Another name for an incident report created by the OSM and TSM Notification Director. When incident reports are dialed out to service providers, this process is also referred to as remote notification.

NRL. See named resource list (NRL).

NRT. See network routing table (NRT).

NSR-D processor. See HP NonStop™ System RISC Model D processor (NSR-D processor).

NSR-E processor. See HP NonStop™ System RISC Model E processor (NSR-E processor).

NSR-G processor. See HP NonStop™ System RISC Model G processor (NSR-G processor).

NSR-H processor. See HP NonStop™ System RISC Model H processor (NSR-H processor).

NSR-J processor. See HP NonStop™ System RISC Model J processor (NSR-J processor).

NSR-T processor. See HP NonStop™ System RISC Model T processor (NSR-T processor).

NSR-V processor. See HP NonStop™ System RISC Model V processor (NSR-V processor).


Glossary NSR-W processor

NSR-W processor. See HP NonStop™ System RISC Model W processor (NSR-W processor).

NSR-X processor. See HP NonStop™ System RISC Model X processor (NSR-X processor).

NSR-Y processor. See HP NonStop™ System RISC Model Y processor (NSR-Y processor).

NSR-Z processor. See HP NonStop™ System RISC Model Z processor (NSR-Z processor).

null object type. A placeholder object type for the Subsystem Control Facility (SCF) NAMES and VERSION commands, which do not require explicit specification of a particular object type.

null string. In C and C++ programs, a character string that begins with a null character. This term is synonymous with empty string.

OBEY file. See command file.

object. One or more of the devices, lines, processes, and files in a subsystem; any entity subject to independent reference or control by one or more subsystems. In the Subsystem Control Facility (SCF), each object has an object type and an object name.

object code library. Synonym for library.

object code file. A file containing compiled machine instructions for one or more routines. This file can be an executable loadfile for a program or library or a not-yet-executable linkfile for some program module. On other systems, an object code file is also known as a binary or as an executable.

object name. A unique name for a Subsystem Control Facility (SCF) object within a subsystem.

object-name template. A name that stands for more than one Subsystem Control Facility (SCF) object. Such a name includes one or more wild-card characters, such as * (asterisk) and ? (question mark). See also wild-card character.

object type. The category of Subsystem Control Facility (SCF) objects to which a specific SCF object belongs. For example, a specific disk has the object type DISK, and a specific terminal can have the object type SU. Each subsystem has a set of object types for the objects it manages.

obsolescent. An indication that a feature or facility exists for compatibility with older versions or drafts of a standard. Obsolescent features or facilities should not be used because they might be removed from future versions of a standard and therefore might not be portable.


Glossary offline

offline. (1) Used to describe tasks that are performed outside of the control of an application or computer system. (2) Used to describe tasks that require system resources to be shut down. Contrast with online.

offline change. Any change that requires system resources to be shut down. Offline changes are usually performed during a planned outage. Contrast with online change.

offline configuration. Configuration performed offline by Distributed Systems Management/Software Configuration Manager (DSM/SCM). If necessary, you edit the CONFTEXT configuration file to create a new configuration and then run DSM/SCM to generate a system image for the new configuration.

ohm. The standard unit for measuring resistance. A one-ohm resistor will conduct one ampere when one volt is applied.

online. Used to describe tasks that can be performed while the HP NonStop™ operating system and system utilities are operational. Contrast with offline.

online change. Any change that can be performed while an application or its system resources are operational. In some situations, online changes might temporarily affect subsystem and application availability. For example, altering the characteristics of a communications line might temporarily affect applications that use the communications line. Contrast with offline change.

Online Support Center (OSC). The group of support specialists within the HP Global Customer Support Center (GCSC) who respond to telephone calls regarding system problems and diagnose malfunctioning systems using remote diagnostic links.

open file. In the Open System Services (OSS) file system, a file with a file descriptor.

open file description. In the Open System Services (OSS) file system, a data structure within an HP NonStop™ Expand node that contains information about the access of a process or of a group of processes to a file. An open file description records such attributes as the file offset, file status, and file access modes. An open file description is associated with only one open file but can be associated with one or more file descriptors.

open migration. In the Open System Services (OSS) file system, the set of events and outcomes that occur when an open file description is inherited by a child process in a different processor than its parent process. Contrast with open propagation.

open propagation. In the Open System Services (OSS) file system, the set of events and outcomes that occur when an open file description is inherited by a child process in the same processor as its parent process. Contrast with open migration.

Open SCSI. A subsystem that provides the hardware and software for a SCSI-2 open interface that runs on HP NonStop™ S-series servers and to which developers can attach small computer system interface (SCSI) devices.


Glossary open system

open system. A system with interfaces that conform to international computing standards and therefore appear the same regardless of the system’s manufacturer. For example, the Open System Services (OSS) environment on HP NonStop™ systems conforms to international standards such as ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990, also known as POSIX.1), national standards such as FIPS 151-2, and portions of industry specifications such as the X/Open Portability Guide Version 4 (XPG4).

Open System Services (OSS). An open system environment available for interactive or programmatic use with the HP NonStop™ operating system. Processes that run in the OSS environment usually use the OSS application program interface. Interactive users of the OSS environment usually use the OSS shell for their command interpreter. Synonymous with Open System Services (OSS) environment. Contrast with Guardian.

Open System Services (OSS) environment. The HP NonStop™ Open System Services (OSS) application program interface (API), tools, and utilities.

Open System Services (OSS) Monitor. A Guardian utility that accepts commands affecting OSS objects through an interactive Guardian interface named the Subsystem Control Facility (SCF).

Open System Services (OSS) signal. A signal model defined in the POSIX.1 specification and available to processes in the OSS environment. OSS signals can be sent between processes.

Open Systems Interconnection (OSI). A seven-layer network architecture model defined by the International Organization for Standardization (ISO). The two lowest layers deal with the physical connections and their protocols. The five upper layers deal with network services, such as network file transfers and access to remote databases.

Open Systems Interconnection Layer 2. The data-link control level of the Open Systems Interconnection (OSI) model, composed of asynchronous or minimal line control protocols, byte-oriented or character-oriented protocols, and bit-synchronous or bit-oriented protocols. Data link protocols can be defined in terms of method of access of data, link relationship of stations, error detection scheme, error recovery, message formatting, logical half-duplex or full-duplex operation, code, and machine transparency.

operating system. See HP NonStop™ operating system.

operating system image. See OSIMAGE.

operational environment. The conditions under which your system performs. These conditions include the devices and communications lines that are made active and the system and application processes that are started at system startup.

operator. (1) A symbol, such as an arithmetic or conditional operator, that performs a specific operation on operands. (2) In Network Control Language (NCL), a lexical element used for working on terms in expressions. The five types of operators are parenthetical, arithmetic, Boolean, relational, and string. (3) For an HP NonStop™


Glossary operator message

server, the person or program responsible for day-to-day monitoring and maintenance tasks associated with the HP NonStop operating system and the hardware of a NonStop node. The operator issues commands to subsystems; retrieves, examines, and responds to event messages; or does any combination of those things. See also local operator. Contrast with administrator. (4) For a UNIX system, any interactive user of that system.

operator message. A message, intended for an operator, that describes a significant event on an HP NonStop™ server. An operator message is the displayed-text form of an Event Management Service (EMS) event message.

option. In a UNIX or Open System Services (OSS) command, a flag and its parameters or a flag without parameters.

orphaned process group. In the Open System Services (OSS) environment, a process group in which the parent of every member is also either a member of the process group or a member of a different session.

orphan file. In the Open System Services (OSS) environment, a file with no corresponding inode in the PXINODE file.

orphan inode. In the Open System Services (OSS) environment, an inode that appears in the PXINODE file but has no links in the PXLINK file.

OS. See HP NonStop™ operating system.

OSC. See Online Support Center (OSC).

OSCONFIG file. In G-series release version updates (RVUs), a configuration file built during system generation that contains only Software Problem Isolation and Fix Facility (SPIFF) and Software Identification (SWID) tool records. In D-series and earlier RVUs, the Configuration Utility Program (COUP) uses the $SYSTEM.SYSnn.OSCONFIG file to store its configuration information.

OSI. See Open Systems Interconnection (OSI).

OSIMAGE. A file built during system generation that contains the complete image of the HP NonStop™ operating system that runs in each processor in the system.

OSM. See HP NonStop™ Open System Management (OSM) Interface.

OSM Event Viewer. OSM replacement for the TSM Event Viewer.

OSM Low-Level Link. OSM replacement for the TSM Low-Level Link.

OSM Notification Director. OSM replacement for the TSM Notification Director.

OSM Service Connection. OSM replacement for the TSM Service Application.

OSS. See Open System Services (OSS).


Glossary OSS environment

OSS environment. See Open System Services (OSS) environment.

OSS Monitor. See Open System Services (OSS) Monitor.

OSS process ID. In the Open System Services (OSS) environment, the unique identifier that identifies a process during the lifetime of the process and during the lifetime of the process group of that process. See also PID.

OSS signal. See Open System Services (OSS) signal.

OSS user ID. See HP NonStop™ operating system user ID.

outage. Condition during which a computer system is not capable of doing useful work. Outages can be planned or unplanned. From the end user’s perspective, an outage is any time an application being used is not available. See also planned outage and unplanned outage.

outage minutes. A metric for measuring outages that translates percentages into minutes/year of downtime.

output destination. The resource to which Subsystem Control Facility (SCF) sends its responses to commands. SCF can direct output to a disk file, an application process, a terminal, or a printer. The initial output destination is determined by the form of the RUN command used to initiate SCF. The output destination can be changed dynamically during an SCF session.

owner. (1) In the case of a disk file, the user or program that created the file, or a user or program to whom the creator has given the file with the File Utility Program (FUP) GIVE command. (2) In the case of a process, the user or program that created the process or, if the PROGID option was specified in the FUP SECURE command for the code file, the user or program that owns the code file. (3) In the case of a token or other definition, the subsystem that provided the definition. (4) In the case of a subsystem, the company or organization that provides the subsystem, or the 8-character string identifying that company.

packet. A block of information that contains fields for addressing, sequencing information, possible priority indicators, and a portion of a message or an entire message. See also ServerNet packet.

page. See memory page.

Parallel Library TCP/IP. An HP product that provides increased performance and scalability over conventional Transmission Control Protocol/Internet Protocol (TCP/IP). Parallel Library TCP/IP coexists with conventional TCP/IP on HP NonStop™ systems. See also HP NonStop™ TCP/IP.

PARAM. An HP Tandem Advanced Command Language (TACL) command and a Subsystem Control Facility (SCF) command you can use to create a parameter and


Glossary parent directory

give it a value. The TACL process stores the values of parameters assigned by the PARAM command and sends the values to applications that request parameter values.

parent directory. A particular directory in the hierarchy of directories within a file system. The parent directory for a directory contains an entry for that specific directory and is identified in that directory as the directory immediately above it in the hierarchy. The parent directory for a file contains an entry for that file.

parent process. The process that created a given process or (if the creating process has stopped) a process that has inherited a given process. See also child process.

parent process ID. In the Open System Services (OSS) environment, an attribute of a child process determined by the parent process. The parent process ID is the OSS process ID of the current parent process.

parity. The use of an extra bit on memory chips that serves as a checksum so the operating system can detect if single-bit memory errors are occurring.

passthrough terminator. See SCSI passthrough terminator.

path. The route between a processor and a subsystem. If a subsystem is configured for fault tolerance, it has a primary path (from the primary processor) and a backup path (from the backup processor).

pathname. In the Open System Services (OSS) file system and Network File System (NFS), the string of characters that uniquely identifies a file within its file system. A pathname can be either relative or absolute. See also ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990 or POSIX.1), Clause 2.2.2.57.

pathname component. See filename.

pathname resolution. In the Open System Services (OSS) environment, the process of associating a single file with a specified pathname.

pathname-variable limits. Limits that can vary within the Open System Services (OSS) file hierarchy; that is, the limits on a pathname variable that can vary according to the directory in which pathname resolution begins.

path prefix. In the Open System Services (OSS) environment, a pathname with an optional final slash (/) character that refers to a directory.

PDP. See power distribution panel (PDP).

PDU. See power distribution unit (PDU).

peak load current. The maximum instantaneous load over a designated interval of time.

PEEK. A utility program that reports statistics on resource use in a processor. PEEK is used to ensure proper allocation of memory and processes in a system after system load.


Glossary peer fabric

peer fabric. The fabric on which an operation is not taking place. The X and Y fabrics are peers. If an action is being performed on one fabric, the other fabric is the peer fabric.

peer service processors. A pair of service processors (X and Y) in a service processor (SP) domain. See also service processor (SP).

pending incident report. An incident report that has never been delivered to your service provider, either because delivery to both the primary and backup dial-out points was unsuccessful or because the incident report was generated at an unattended site.

pending signal. A signal that has been generated for a process but has not been delivered. Pending signals are usually blocked signals.

periodic incident report. A type of incident report that is generated periodically to test the connection to the service provider and report the current system configuration. The default frequency is 20 days.

peripheral enclosure. An enclosure that contains components related to one or more peripherals. The 519x tape subsystem is an example of a peripheral enclosure. Peripheral enclosures are not part of the set of system enclosures. Contrast with system enclosure.

Peripheral Utility Program (PUP). A utility used in D-series and earlier release version updates (RVUs) to manage disks and other peripheral devices. In G-series RVUs, similar functions are performed by the Subsystem Control Facility (SCF).

persistence. For the Subsystem Control Facility (SCF), the capability of a generic process to restart automatically if it was stopped abnormally. You configure this capability by specifying a nonzero AUTORESTART value in an ADD command.

persistence count. The number of times the $ZPM persistence manager process will restart a generic process that has been terminated abnormally. A generic process with an AUTORESTART value of 10 (the maximum) is said to have a persistence count of 10. See also persistence.

persistence manager process. The $ZPM process that is started and managed by the $ZCNF configuration utility process and that starts generic processes in G-series release version updates (RVUs) and manages their persistence.

persistent configuration. A configuration that remains the same from one system load to another.

persistent process. A process that must always be either waiting, ready, or executing. Persistent processes are usually controlled by a monitor process that checks on the status of persistent processes and restarts them if necessary.

physical interface (PIF). The hardware components that connect a system node to a network.


Glossary physical link interfaces

physical link interfaces. Communications standards defined by standards organizations. These physical link interfaces are supported for the ServerNet wide area network (SWAN) concentrator: RS-232, RS-442, RS-449, V.35, and X.21.

Physical view. One of several views of a server available in the view pane of the Management window of the OSM Service Connection, TSM Service Application, and OSM and TSM Low-Level Link. A Physical view of a server is a view of all the enclosures and is intended to represent the actual floor plan at the site. A Physical view of an enclosure is a visual representation of the physical placement of supported resources inside the enclosure. See also Connection view.

PIB. See power interface board (PIB).

PIC. (1) See plug-in card (PIC). (2) See position-independent code (PIC).

PID. In the Open System Services (OSS) environment, a synonym for process ID. OSS process ID is the preferred term in HP NonStop™ system publications.

In the Guardian environment, PID is sometimes used to mean either:

• A Guardian process identifier such as the process ID

• The cpu, pin value that is unique to a process within an Expand node (See process identification number (PIN).)

PIF. See physical interface (PIF).

PIN. See process identification number (PIN).

ping. A utility used to verify connections to one or more remote hosts. The ping utility uses the Internet control message protocol (ICMP) echo request and echo reply packets to determine whether a particular IP system on a network is functional. The ping utility is useful for diagnosing IP network or router failures.

pipe. In the Open System Services (OSS) environment, an unnamed FIFO, created programmatically by invoking the pipe() function or interactively with the shell pipe syntax character (|). A shell pipe redirects the standard output of one process to become the standard input of another process. A programmatic pipe is an interprocess communication mechanism.

planned outage. Time during which a computer system is not capable of doing useful work because of a planned interruption. A planned outage can be time when the system or user application is shut down to allow for servicing, upgrades, backup, or general maintenance.

planner. (1) The Distributed Systems Management/Software Configuration Manager (DSM/SCM) user who is responsible for planning and managing new software revisions. The planner uses the DSM/SCM Planner Interface to carry out these functions. (2) A person who participates in planning a new HP NonStop™ system.


Glossary Planner Interface

Planner Interface. A graphical user interface (GUI) to the Distributed Systems Management/Software Configuration Manager (DSM/SCM) that runs on the host system. It provides an interface to all the host DSM/SCM planner functions.

PLD. Programmable logic device.

plug-in card (PIC). A replaceable component that provides a unique function when installed in a customer-replaceable unit (CRU) or field-replaceable unit (FRU). For example, PICs for modular ServerNet expansion boards (MSEBs) and I/O multifunction (IOMF) 2 CRUs provide a choice of connection media for attaching ServerNet cables.

PM. See product module (PM).

PMB. See processor and memory board (PMB).

PMCU. See power monitor and control unit (PMCU).

PMF CRU. See processor multifunction (PMF) CRU.

PMF 2 CRU. See processor multifunction (PMF) 2 CRU.

pNA+. The support for the Transmission Control Protocol/Internet Protocol (TCP/IP) layers and the Ethernet interface provided by Integrated Systems Inc. as part of the Portable Silicon Operating System (pSOS) system product. pNA+ is provided as part of the wide area network (WAN) architecture in each ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP).

Point-to-Point Protocol (PPP). A data communications protocol that provides a standard method of encapsulating Transmission Control Protocol/Internet Protocol (TCP/IP) information over point-to-point links. OSM and TSM use PPP to provide TCP/IP communication over a dial-up connection.

PON. Power on.

POOL object type. The Subsystem Control Facility (SCF) object type for storage pools.

port. (1) A data channel that connects to other devices or computers. (2) A connector to which a cable can be attached. The system transmits and receives data or requests through ports on ServerNet adapters and processor multifunction (PMF) customer- replaceable units (CRUs). (3) The entrance or physical access point (such as a connector) to a computer, multiplexer, device, or network where signals are supplied, extracted, or observed.

portable application. An application that can execute on a wide range of hardware systems from multiple manufacturers. A portable application is a program that can be moved with little or no change in its source code from another manufacturer’s system to an HP NonStop™ system.


Glossary portable filename character set

portable filename character set. The set of characters that includes the Roman uppercase and lowercase letters, the Arabic numerals, the period, the underscore, and the hyphen. The hyphen cannot be the first character of a portable filename.

portable pathname character set. The set of characters that includes the Roman uppercase and lowercase letters, the Arabic numerals, the period, the underscore, the slash (/), and the hyphen. The hyphen cannot be the first character of a portable pathname.

Portable Silicon Operating System (pSOS) system product. A product of Integrated Systems Inc. that provides support for industry-standard communications protocols based on the UNIX operating system. It is used as a compact multitasking kernel operating system for PowerPCs and similar systems.

position ID. A character that indicates the position an HP NonStop™ Cluster Switch occupies in a network topology. The position ID is a component of the two-character cluster switch name. The cluster switch name includes an external fabric ID (X or Y) as the first character and a position ID as the second character. For example, the cluster switch name X3 indicates that the cluster switch serves the external ServerNet X fabric and occupies position 3 in the topology. Supported values for position IDs are 1 through 9 or A through Z. Currently supported topologies (star, split-star, and tri-star) use position IDs 1, 2, and 3.

position-independent code (PIC). Executable program or library code that is designed to be loaded and executed at any virtual memory address, without any modification. Addresses that can be modified by the loader do not appear in PIC code, only in data that can be modified by the loader. See also dynamic-link library (DLL).

POSIX. The Portable Operating System Interface, as defined by the Institute of Electrical and Electronics Engineers (IEEE) and the American National Standards Institute (ANSI). Each POSIX interface is separately defined in a numbered ANSI/IEEE standard or draft standard. The application program interface (API), known as POSIX.1, has become ISO/IEC IS 9945-1:1990.

power distribution panel (PDP). A group of panel assemblies that composes a single panel that includes buses and overcurrent protection devices (with or without switches). A PDP is used for the control of power circuits.

power distribution unit (PDU). An assembly of outlets and fuses that is installed on both sides of a modular cabinet. This assembly provides power and over-current protection for the components installed in the modular cabinet.

power domain. A set of customer-replaceable units (CRUs) and field-replaceable units (FRUs) that share a set of power rails. For telco Central Office (CO) systems, the power domain is the entire system.

power factor. The ratio of real power to apparent power (that is, kilowatts/kilovoltamperes). The power factor for a sinusoidal load is determined by the position of the applied voltage waveform with respect to the current drawn by the load. When voltage and


Glossary power factor correction

current are in phase with each other, the power factor is unity, and the power for the load is equal to the product of the applied voltage and load current (P=EI). When the current waveform lags the voltage waveform, the load is inductive. Conversely, when the current waveform leads the voltage waveform, the load is capacitive. In either case, the power for the load is equal to the product of the applied voltage, load current, and the angular displacement between the voltage and current waveforms (P=EIcosf). Nonlinear (nonsinusoidal) loads also have a power factor. However, the power factor for a nonsinusoidal load reflects harmonic content and not angular displacement.

power factor correction. The addition of a reactive component to offset the angular displacement of a sinusoidal load. Traditionally, the normal power factor for a facility is inductive, so the normal correction involves the addition of capacitors to offset the lagging power factor. The capacitors offset part or all of the inductive reactance, making the total circuit more nearly in phase with the applied voltage. The power factor for nonlinear (nonsinusoidal) loads cannot be corrected through the addition of simple reactive components. Harmonic filters are required to correct the power factor of nonlinear loads.

power interface board (PIB). In HP NonStop™ S-series system enclosures with power shelves, a board mounted on the bulkhead located behind the power supplies in the power shelf. The PIB provides electrical connection between the power supplies and DC power cables.

power monitor and control unit (PMCU). A field-replaceable unit (FRU) that connects the batteries to the DC power distribution bus in an HP NonStop™ S-series enclosure and provides a means of disconnecting the batteries for powering off the system. The PMCU also provides a means for the service processor (SP) to diagnose the condition of the batteries, fans, and power supplies; to regulate the voltage supplied to the fans; and to provide the interface to the group ID switches and service light-emitting diodes (LEDs). A group contains two PMCUs, one for each of the two DC power distribution buses.

power shelf. In HP NonStop™ S7400, S7600, and Sxx000 processor enclosures and I/O enclosures containing I/O multifunction (IOMF) 2 customer-replaceable units (CRUs), an assembly residing below the chassis consisting of power supplies and supporting circuitry that provides DC power to the enclosure.

power supply. (1) In HP NonStop™ S-series system enclosures without power shelves, the component on the processor multifunction (PMF) customer-replaceable unit (CRU) or the I/O multifunction (IOMF) CRU that converts standard AC line voltage into the DC voltages needed by the group components in the enclosure. (2) In HP NonStop™ S-series system enclosures with power shelves, the component located in the power shelf that converts standard AC line voltage into DC voltage and delivers it to the PMF CRUs or IOMF 2 CRUs in that enclosure, which in turn supply the DC voltages needed by the group components in the enclosure.

PPL. See process-pair list (PPL).


Glossary PPP

PPP. See Point-to-Point Protocol (PPP).

preemption. A form of late binding in which a symbolic reference to a symbol defined in the same dynamic-link library is instead bound to a definition in another loadfile.

preferences file. A file that contains configuration information for the graphical user interface (GUI) portion of the OSM and TSM client software. The preferences file is used by the OSM and TSM client software at system startup.

preferred path. See primary path.

preprocessing commands. Commands specifying unique run-time parameters that can override your default system parameters. These commands can assign process file names, select backup media formats, and define utility options during system configuration.

preset. A linker operation that sets the correct values (addresses) of imported symbols according to the environment seen by the linker. If the loader encounters the same environment at load time, it avoids adjusting these values, which reduces loading overhead. (See fastLoad.) If not, the loader resets these values to match the load-time environment.

primary path. A path enabled as the preferred path. When a primary path is disabled, an alternate path becomes the primary path.

primary processor. The processor that is designated as owning the ServerNet addressable controller (SAC) connected to separate processors running the HP NonStop™ operating system. The primary processor is the processor that has direct control over the SAC. Contrast with backup processor.

problem incident report. A type of incident report that reports a problem in the server. A problem incident report is generated when changes occur on the server that could directly affect the availability of system resources.

procedure entry-point (PEP) table. A table in a TNS object file that contains the entry-point addresses for each procedure and is located in the first page of each code segment.

process. (1) A program that has been submitted to the operating system for execution, or a program that is currently running in the computer. (2) An address space, a single thread of control that executes within that address space, and the system resources required by that thread of control.

process group. In the Open System Services (OSS) environment, a set of processes that can signal associated processes. Each process in an Expand node is a member of a process group. The process group has a process group ID. A new process becomes a member of the process group of its creator.


Glossary process group ID

process group ID. In the Open System Services (OSS) environment, the unique identifier representing a process group during its lifetime.

process group leader. In the Open System Services (OSS) environment, the process that has the process group ID of its process group as its OSS process ID.

process group lifetime. In the Open System Services (OSS) environment, the period that begins when a process group is created and ends when the lifetime of the last remaining process of the group ends.

process ID. In the Guardian environment, the content of a 4-integer array that uniquely identifies a process during the lifetime of the process. See also PID.

process identification number (PIN). A number that uniquely identifies a process running in a processor. The same number can exist in other processors in the same system. See also process ID.

process image file. On a UNIX system, an executable object file. In some Guardian product externals and end-user publications, an executable object file is referred to as a program file. See also object code file.

process lifetime. The period that begins when an Open System Services (OSS) process is created and ends when its OSS process ID is returned to the system for reuse.

PROCESS object type. In a subsystem, the object type for the subsystem manager process itself or any generic process.

process-pair list (PPL). A table that contains one entry for each process or process pair associated with a named resource. For some devices, a single PPL entry is associated with multiple named resource list (NRL) entries. For process pairs, a single PPL entry describes both members of the pair.

process snapshot. The contents of a saveabend file or process snapshot file.

process snapshot file. (1) A file containing dump information needed by the system debugging tool. In UNIX systems, such files are usually called core files or core dump files. (2) A file containing the state of a running process at a specific moment, regardless of whether the process terminated abnormally. See also saveabend file.

processor. (1) A functional unit of a computer that reads program instructions, moves data between processor memory and the input/output controllers, and performs arithmetic operations. Because a processor is composed of several hardware components that reside in different enclosures, it is sometimes called a logical processor. A processor is sometimes referred to as a central processing unit (CPU), but HP NonStop™ servers have multiple cooperating processors rather than a single CPU. (2) One or more computer chips, typically mounted on a logic board, that are designed to perform data processing or to manage a particular aspect of computer operations.


Glossary processor and memory board (PMB)

processor and memory board (PMB). A logic board that has lockstepped microprocessors, the main memory system, and the ServerNet memory interface (SMI) application-specific integrated circuits (ASICs) to act as an interface between the microprocessors and memory and the ServerNet fabrics. This board is part of the processor multifunction (PMF) customer-replaceable unit (CRU).

processor cache. Small, fast memory holding recently accessed data in order to speed up subsequent access to the same data. Cache memory is built from faster memory chips than main memory. It is most often used with process or main memory but is also used in network data transfer (to maintain a local copy of data) and so forth.

processor dump. A copy of the memory of a processor. A dump can be to disk or to tape. See also ServerNet dump and tape dump.

processor enclosure. An HP NonStop™ S-series system enclosure containing one group, which includes processors, ServerNet adapters, disk drives, components related to the ServerNet fabrics, and components related to electrical power and cooling for the enclosure.

processor multifunction (PMF) CRU. (1) An HP NonStop™ S-series customer-replaceable unit (CRU) that contains a power supply, service processor (SP), ServerNet router 1, Ethernet controller, three ServerNet addressable controllers (SACs), and a processor and memory system in a single unit. The PMF CRU consists of three subassemblies: the processor and memory board (PMB), the multifunction I/O board (MFIOB), and the power supply subassembly. (2) A collective term for both PMF CRUs and PMF 2 CRUs when a distinction between the two types of CRUs is not required.

processor multifunction (PMF) 2 CRU. An HP NonStop™ S-series customer-replaceable unit (CRU) that contains a power supply, service processor (SP), ServerNet router 2, Ethernet controller, three ServerNet addressable controllers (SACs), and a processor and memory system in a single unit. The PMF 2 CRU consists of three subassemblies: the processor and memory board (PMB), the multifunction I/O board (MFIOB), and the power supply subassembly.

product module (PM). The part of the Subsystem Control Facility (SCF) subsystem that is responsible for subsystem-specific command processing.

profile. Default values used by the Distributed Systems Management/Software Configuration Manager (DSM/SCM) when processing requests. The three types of profiles are the Configuration Manager profile, the system profile, and the target profile.

PROFILE object type. The Subsystem Control Facility (SCF) object type for the storage subsystem configuration profile.

program. See program file.

program file. An executable object code file containing a program’s main routine plus related routines statically linked together and combined into the same object file. Other


Glossary pSOS system product

routines shared with other programs might be located in separately loaded libraries. A program file can be named on a RUN command; other code files cannot. See also object code file.

pSOS system product. See Portable Silicon Operating System (pSOS) system product.

pTAL. Portable Transaction Application Language. A machine-independent system programming language based on Transaction Application Language (TAL). The pTAL language excludes architecture-specific TAL constructs and includes new constructs that replace the architecture-specific constructs. Contrast with HP Transaction Application Language (TAL).

pTAL compiler. An optimizing native-mode compiler for the pTAL language.

public dynamic-link library (public DLL). Optional native-mode executable code modules available to all native user processes.

public LAN. See nondedicated (public) LAN.

public library. A dynamic-link library (DLL) or shared run-time library (SRL) that is known to the operating system, available for execution by any process or user, and is not an implicit library.

public shared run-time library (public SRL). A TNS/R library supplied by HP.

PUP. See Peripheral Utility Program (PUP).

quad-integrated communications controller (QUICC). The Motorola MC68360 chip. For HP NonStop™ S-series servers, the QUICC is used as the service processor (SP) and is the main part of the ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP).

quality power. The attributes and configuration of the power-distribution systems installed within a facility that best serve the power needs of that facility’s electrical equipment (for example, computer systems, air conditioning, and so on), providing the minimum possible disruption to equipment operation.

QUICC. See quad-integrated communications controller (QUICC).

R1. See ServerNet router 1.

R2. See ServerNet router 2.

raceway. An enclosed channel used to hold wires, cables, or busbars. Most raceways have removable tops to facilitate the installation or removal of their contents.

rack. A metal structure that has four columns, to which slides or rails that hold computer equipment can be fastened. See also frame.


Glossary radio frequency interference (RFI)

radio frequency interference (RFI). Forms of conducted or radiated interference that might appear in a facility as either normal or common-mode signals. The frequency of the interference can range from the kilohertz to gigahertz range. However, the most troublesome interference signals are usually found in the kilohertz to low megahertz range. At present, the terms radio frequency interference and electromagnetic interference (EMI) are usually used interchangeably.

RDMA. Remote direct memory access.

read-only file system. A file system with implementation-defined characteristics that restrict changes to the files within that file system.

read/write head. An electromagnet that can pick up (read) electronic pulses and record (write) electronic pulses on a magnetic disk or tape. The electronic pulses are interpreted by the processor as binary data. See also disk drive and tape drive.

real group ID. An attribute of an Open System Services (OSS) process. When an OSS process is created, the real group ID identifies the group of the user or parent process that created the process. The real group ID can be changed after process creation.

real user ID. An attribute of an Open System Services (OSS) process. When an OSS process is created, the real user ID identifies the user or parent process that created the process. The real user ID can be changed after process creation.

$RECEIVE. The name of a file through which a process receives and optionally replies to messages from other processes.

reconfiguration. The act of changing the hardware or software configuration of a running system. Examples include installing a new software release version update (RVU), adding hardware peripherals, and restructuring a database. Reconfiguring a system might or might not require a planned outage.

reduced instruction-set computing (RISC). A processor architecture based on a relatively small and simple instruction set, a large number of general-purpose registers, and an optimized instruction pipeline that supports high-performance instruction execution. Contrast with complex instruction-set computing (CISC).

reexported library. A library whose symbols are made available by another dynamic-link library (DLL) to any localized client of that DLL. Reexport is an attribute of the DLL’s libList entry for that library. This attribute is specified by the DLL’s programmer and recorded by the linker as a DLL is built. It affects only localized clients of the DLL. This feature allows a symbol to be moved from one DLL to another without relinking clients of the original DLL.

Reexporting is transitive; that is, if A reexports B and B reexports C, then A reexports C. Reexported libraries can reexport other libraries to form a succession of reexported libraries of arbitrary length.


Glossary reference page

reference page. In Open System Services (OSS) and Distributed Computing Environment (DCE), the online or hard-copy version of a file that provides reference information for a software facility. Some UNIX product externals and end-user publications use the term man page instead, referring either to the online delivery mechanism used to display the file (usually the shell man command) or to the nature of the file as part of a publication.

register-exact point. A synchronization location within an accelerated object file at which both of these statements are true:

• All live TNS registers plus all values in memory are the same as they would be if the object file were running in TNS mode or TNS interpreted mode or on a TNS system.

• All accelerator code optimizations are ended.

Register-exact points are a small subset of all memory-exact points. Procedure entry and exit locations and call-return sites are usually register-exact points. All places where the program might switch into or from TNS mode or TNS interpreted mode are register-exact points. Contrast with memory-exact point and nonexact point.

register pointer (RP). The register pointer in TNS computers.

requester missed address file (RMAF). A file used by the HP NonStop™ operating system during memory-caching operations.

regular file. In the Open System Services (OSS) file system, a file that is a randomly accessible sequence of bytes. A regular file contains binary or text data and has no structure imposed by the system. Contrast with special file.

relative pathname. In the Open System Services (OSS) file system and Network File System (NFS), a pathname that does not begin with a slash (/) character. A relative pathname is resolved beginning with the current working directory. Contrast with absolute pathname.

release version update (RVU). A collection of compatible revisions of HP NonStop operating system software products, identified by an RVU ID, and shipped and supported as a unit. An RVU consists of the object modules, supporting files, and documentation for the product revisions. An RVU also includes a set of documentation for the overall RVU.

RELOAD. An HP Tandem Advanced Command Language (TACL) command to load the HP NonStop™ operating system image from disk over the ServerNet fabrics into the memory of the processor.

remote access. A form of remote support, configured in the OSM and TSM Notification Director. Remote access, or dial-in, allows a service provider to dial in to your system console and access your HP NonStop™ server to diagnose hardware and software problems. See also remote notification.


Glossary remote interprocessor communication (RIPC)

remote interprocessor communication (RIPC). The exchange of messages between processors in different systems or nodes.

remote mount. A mount used by a Network File System (NFS) client to attach part of the local NFS file hierarchy to a point within the client’s remote file hierarchy. The remote mount is visible only to the NFS client performing the mount. In effect, the local hierarchy from the mount point down is exported to the client performing the remote mount.

remote node. See remote system.

remote notification. A form of remote support. Remote notification, or dial-out, allows the OSM or TSM Notification Director to notify a service provider, such as the Global Customer Support Center (GCSC), of pending hardware and software problems. See also remote access.

remote operator. The person who performs routine system operations from a geographical distance, usually when no local operator is present.

remote procedure. A procedure or function packaged to be called within a server process indirectly by a client process.

remote procedure call. A remote procedure or the action of calling a remote procedure.

Remote Procedure Call (RPC). A protocol that extends a procedure-call form of process-to-process communication to a network environment. RPC is a way for programs running on client computers to invoke the services of a program running on a server computer. RPC allows a program to call a procedure that does not exist on the client computer.

remote procedure call system. A set of facilities that includes a programming library, network resource mapping, and binding services to provide a mechanism for a client process to execute a procedure on a remote server. A remote procedure call system is a subset of the Distributed Computing Environment (DCE) and of other products.

remote processor. A processor in a node other than the node running the ServerNet cluster monitor process (SNETMON) that is reporting status about the processor.

remote switch. An HP NonStop Cluster Switch (model 6770) or HP NonStop ServerNet Switch (model 6780) in a ServerNet cluster that is not directly connected to the server that you are logged on to. The OSM Service Connection and the TSM Service Application cannot perform any actions on a remote switch. To perform actions or get additional information on a remote switch, use the OSM Service Connection (for either the 6770 or 6780 switch) or TSM Service Application (for the 6770 switch only) to log on to a server that is directly connected to the switch.

remote system. An active ServerNet node to which the local system has active external ServerNet paths. Contrast with local system.


Glossary request packet

request packet. A ServerNet packet sent from one ServerNet device to another, requesting either a read action or a write action on the part of the receiving device. In the case of a write request, the packet contains the data to be written. The receiving device is expected to take the appropriate action and return a response packet to the device that sent the request packet. See also response packet, ServerNet packet, and ServerNet transaction.

requester missed address file (RMAF). A file used by the HP NonStop™ operating system during memory-caching operations.

reserved symbol. An identifier that is reserved for use by system or compiler language implementors.

resistance. The measure of noninductive or capacitive opposition (impedance) to current that limits the amount of current that can be produced by an applied voltage. Conductors have very little resistance; insulators have a large amount of resistance. Resistance is measured in ohms.

resource. A component of a computer system that works with other components to process transactions. Terminals, workstations, processors, memory, disk drives, processes, files, and applications are examples of resources.

response. The information or confirmation supplied by a subsystem in reaction to a command. A response is typically conveyed as one or more interprocess messages from a subsystem to an application.

response packet. A ServerNet packet returned from one ServerNet device to another, responding to an earlier received read request or write request. In the case of responding to a read request, the response packet contains the data that the requesting device wanted to have read. See also request packet, ServerNet packet, and ServerNet transaction.

RESTORE. A utility for HP NonStop™ servers that copies files from a backup tape to disk. See also BACKUP.

RFC. Request for Comments. Documents compiled by number by the Internet Engineering Task Force (IETF) that define standards for intercommunication.

RFI. See radio frequency interference (RFI).

RIPC. See remote interprocessor communication (RIPC).

RISC. See reduced instruction-set computing (RISC).

RISC instructions. See MIPS RISC instructions.

RISC processor. An instruction processing unit (IPU) that is based on reduced instruction-set computing (RISC) architecture. TNS/R processors contain RISC processors.


Glossary rld library

rld library. A library that loads position-independent code (PIC) programs and their associated dynamic-link libraries (DLLs). The rld library also provides the dlopen(), dlclose(), dlresultcode(), dlsys(), and dlerror() functions.

RMAF. See requester missed address file (RMAF).

rms. See root mean square (rms).

robot. A media-changer device that transfers a tape cartridge to a tape drive for use and then returns the cartridge to the storage cell.

root. See root fileset and root directory. See also super ID.

root directory. In the Open System Services (OSS) file system and Network File System (NFS), a directory associated with a process that the system uses for pathname resolution when a pathname begins with a slash (/) character.

root fileset. For the Open System Services (OSS) file system, the fileset with the device identifier of 0, normally containing the root directory. HP recommends that this fileset be named root.

root mean square (rms). A measurement method used to determine the direct current (DC) equivalent value for alternating voltage and current waveforms. The rms method refers to the process of sampling a waveform, squaring the samples, averaging the samples (mean value) over the period from one cycle, and then calculating the square root of the samples. In general, rms-sensing devices are more accurate than averaging meters. Measurements from averaging meters can be as low as 30 percent of the actual current for loads with high crest factors.

root user. See super ID.

router. See ServerNet router.

router 1. See ServerNet router 1.

router 2. See ServerNet router 2.

RP. See register pointer (RP).

RPC. See Remote Procedure Call (RPC).

RS-232. An industry standard for serial data transmission. It describes pin assignments, signal functions, and electrical characteristics. The current standard specifies a 25-pin connector.

RS-449. An industry standard for serial data transmission. It specifies pin assignments, signal functions, electrical characteristics, and a 37-pin connector with an optional 9-pin connector for a secondary channel.


Glossary run-time data unit (RTDU)

run-time data unit (RTDU). The region of a TNS object file used to store SQL/MP source and object code. It contains embedded SQL information for clients of SQL/MP. Source RTDUs are created when a program file using embedded SQL/MP is initially compiled and linked. Object RTDUs are added to the program when the file is SQL-compiled.

run-time linker. See linker.

run-time loader. See loader.

RVU. See release version update (RVU).

S700 server. See HP NonStop™ S700 server.












Sxx000 server. See HP NonStop™ Sxx000 server.

S-series servers. See HP NonStop™ S-series servers.

SAC. See ServerNet addressable controller (SAC).

sag. A reduction in voltage, usually lasting from one cycle to a few seconds. Sags are typically caused by fault clearing or by heavy load startups.

SAIL. See ServerNet Advanced Interface Logic (SAIL).

SAN. System area network. The preferred term is fabrics.

SANMAN. See external system area network manager process (SANMAN).


Glossary save file

save file. A file created by the Inspect subsystem in response to a command from a debugger. A save file contains enough information about a running process at a given time to restart the process at the same point in its execution. A save file contains an image of the process, data for the process, and the status of the process at the time the save file was created.

A save file can be created through an Inspect SAVE command at any time. A save file called a saveabend file can be created when a process’s SAVEABEND attribute is set and the process terminates abnormally. Other debuggers can create a save file but refer to the result as a process snapshot file. See also process snapshot file.

saveabend file. A file containing dump information needed by the system debugging tool. (In UNIX systems, such files are usually called core files or core dump files.) A saveabend file is a special case of a save file. See also save file and process snapshot file.

saved-set group ID. An Open System Services (OSS) process attribute that stores a group ID so that the group ID can later be used as the effective group ID of the process.

saved-set user ID. An Open System Services (OSS) process attribute that stores a user ID so that the user ID can later be used as the effective user ID of the process.

save file. A file created by the Inspect subsystem in response to a command from a debugger. A save file contains enough information about a running process at a given time to restart the process at the same point in its execution. A save file contains an image of the process, data for the process, and the status of the process at the time the save file was created.

A save file can be created through an Inspect SAVE command at any time. A save file called a saveabend file can be created when a process’s SAVEABEND attribute is set and the process terminates abnormally. Other debuggers can create a save file but refer to the result as a process snapshot file. See also process snapshot file.

SBB. See ServerNet buffer board (SBB).

SBI. See ServerNet bus interface (SBI).

SC. See Subscriber Channel (SC).

scalar view of the user ID. A view of the HP NonStop™ operating system user ID, normally used in the Open System Services (OSS) environment, that is the value (group-number * 256) + user-number. Also called the UID.

SCC. See serial communications controller (SCC).

SCF. See Subsystem Control Facility (SCF).

SCL. The mnemonic subsystem name for the ServerNet cluster subsystem.

SCP. See Subsystem Control Point (SCP).


Glossary SCSI

SCSI. See small computer system interface (SCSI).

SCSI object type. The Subsystem Control Facility (SCF) object type for an Open SCSI device.

SCSI passthrough terminator. A bus-terminating plug connected between a cable and the external connector of a customer-replaceable unit (CRU). The SCSI passthrough terminator contains the necessary termination resistors required by the SCSI bus. See also terminator.

SCSI plug-in card (S-PIC). A plug-in card (PIC) for the 6760 ServerNet device adapter (ServerNet/DA) that uses a small computer system interface (SCSI) interface to connect devices to an HP NonStop™ S-series system. See also plug-in card (PIC) and fiber-optic plug-in card (F-PIC).

SCSI ServerNet addressable controller (S-SAC). A ServerNet addressable controller (SAC) that is contained within a small computer system interface (SCSI) plug-in card (S-PIC).

SCSI terminator. See terminator.

SDK. See Software Developers Kit (SDK).

SE. System engineer. See service provider.

searchList. For each loadfile, a list that is constructed and used by the linker and loader to tell them which libraries to examine, and in which order, to locate symbol definitions needed by that loadfile. The linker and loader construct the loadfile’s searchList in accordance with that loadfile’s import control, which is set at link time by the loadfile’s programmer. A loadfile’s searchList is unaffected by the import control of any other loadfile.

SEB. See ServerNet expansion board (SEB).

SEB port. A connector on ServerNet expansion boards (SEBs) used for ServerNet links. An SEB has six emitter-coupled logic (ECL)-based ServerNet ports. See also MSEB port.

Security Manager Process (SMP). A component of the Safeguard subsystem that manages all changes to the subject and object databases and authenticates user logon attempts.

segment. In general, a contiguous sequence of logically related pages of virtual memory. The pages of the segment are individually swapped in and out of physical memory as needed. Within a loadable object file, one of the portions of the file that is mapped as one unit into virtual memory as the file is loaded. See also code segment and data segment.

selectable segment. A type of logical segment formerly known as an extended data segment. The data area for a selectable segment always begins with relative segment


Glossary SEM

4, and this area can be dynamically switched among several selectable segments by calls to the Guardian SEGMENT_USE_ procedure. The effect is similar to a rapid overlaying of one large data area. See also logical segment and flat segment.

SEM. See ServerNet extender module (SEM).

semaphore. A mechanism used to provide multiple processes with access to a shared data object.

semi-globalized. An import control characteristic of a loadfile that allows the loadfile first to obtain symbols from its own definitions and then to obtain others as for a globalized loadfile. See also searchList.

sensitive command. A Subsystem Control Facility (SCF) command that can be issued only by a user with super-group access, by the owner of the subsystem, or by a member of the group of the owner of the subsystem. The owner of a subsystem is the user who started that subsystem (or any user whose application ID is the same as the server ID—the result of a PROGID option that requires super-group access). Contrast with nonsensitive command.

SEP table. See system entry-point (SEP) table.

separately derived power source. A facility wiring system where power is derived from a generator, transformer, or converter windings and there is no direct electrical connection, including a solidly connected grounded circuit conductor (neutral), to supply conductors originating in other facility wiring systems. Types of separately derived power sources include standby power generator, uninterruptible power supply (UPS), isolation transformer, and computer-room power center (CRPC).

serial communications controller (SCC). A type of communications controller. Each quad-integrated communications controller (QUICC) has four SCCs to handle the two Ethernet ports and the two wide area network (WAN) ports.

serial copper. A standard for physical connectivity in ServerNet I and ServerNet II networks that is available both in HP NonStop™ S-series servers and in Windows NT clusters. Serial copper uses serial encoding and supports 50 and 125 megabyte/second (MB/s) speeds. The maximum link distance at 125 MB/s is 25 meters.

serial copper PIC. See serial copper plug-in card (PIC).

serial copper plug-in card (PIC). A plug-in card (PIC) for the modular ServerNet expansion board (MSEB) and I/O multifunction (IOMF) 2 customer-replaceable unit (CRU) that supports the serial copper interface. See also serial copper and plug-in card (PIC).

serial maintenance bus (SMB). A bus that connects service processors (SPs) within an enclosure to each other and to the customer-replaceable units (CRUs) in the group.


Glossary serial maintenance bus (SMB) domain

serial maintenance bus (SMB) domain. The set of enclosures, modules, field-replaceable units (FRUs), and customer-replaceable units (CRUs) connected by a common serial maintenance bus (SMB).

server. (1) An implementation of a system used as a stand-alone system or as a node in an Expand network. (2) A combination of hardware and software designed to provide services in response to requests received from clients across a network. For example, HP NonStop™ servers provide transaction processing, database access, and other services. (3) A process or program that provides services to a client or a requester. Servers are designed to receive request messages from clients or requesters; perform the desired operations, such as database inquiries or updates, security verifications, numerical calculations, or data routing to other computer systems; and return reply messages to the clients or requesters. A server process is a running instance of a server program.

server application. An application that provides a service to a client application. An application that provides local execution of remote procedure calls is an example of a server application.

ServerNet. A communications protocol developed by HP that is used in HP NonStop™ S-series servers. See also ServerNet I and ServerNet II.

ServerNet I. The first-generation ServerNet network. ServerNet I architecture is used in HP NonStop™ S-series servers and other products. It features 50 megabytes/second speed, 6-port ServerNet routers, 8b/9b encoding, and a 64-byte maximum packet size. See also ServerNet II.

ServerNet II. The second-generation ServerNet network. ServerNet II architecture is backward-compatible with ServerNet I architecture, and it features 125 (or 50) megabytes/second speed, 12-port ServerNet routers, 8b/9b and 8b/10b (serializer ready) encoding, and a 512-byte maximum packet size. See also ServerNet I.

ServerNet adapter. A component that connects peripheral devices to the rest of the system through a ServerNet bus interface (SBI).

ServerNet address. A virtual memory address that, when translated to a physical address, indicates where the memory access needed by a ServerNet transaction begins. In some cases, the translation can point to some entity other than memory, such as a register. The ServerNet address is included in all ServerNet read request and write request packets.

ServerNet addressable controller (SAC). An I/O controller that is uniquely addressable by a ServerNet ID in the ServerNet fabrics. A SAC is typically implemented on some portion of a processor multifunction (PMF) customer-replaceable unit (CRU), an I/O multifunction (IOMF) CRU, or a ServerNet adapter.

ServerNet Advanced Interface Logic (SAIL). An application-specific integrated circuit (ASIC) that supports the ServerNet communications protocol.


Glossary ServerNet buffer board (SBB)

ServerNet buffer board (SBB). The board that provides the ServerNet connection to and from the I/O multifunction (IOMF) customer-replaceable unit (CRU). This board replaces the processor and memory board (PMB) in the IOMF CRU.

ServerNet bus interface (SBI). The I/O control and expansion packetizer application-specific integrated circuit (ASIC).

ServerNet cable. A cable that conducts ServerNet signals.

ServerNet cluster. A network of servers (nodes) connected together using the ServerNet protocol for interprocessor communication across a cluster and within its nodes. A ServerNet cluster offers linear system expansion beyond the 8-processor or 16-processor limits of a single server, achieving comparable speeds for internal and external ServerNet communication. See also cluster and HP NonStop™ ServerNet Cluster (ServerNet Cluster).

ServerNet Cluster. See HP NonStop™ ServerNet Cluster (ServerNet Cluster).

ServerNet cluster monitor process (SNETMON). A process pair with the process name $ZZSCL that manages the state of the ServerNet cluster subsystem. Each node (system) in a ServerNet cluster must have one SNETMON process pair running.

ServerNet cluster services. The functions necessary to allow a node to join, participate in, or leave an HP NonStop™ ServerNet Cluster. These functions include monitoring and control of the physical connections to the cluster, discovery of other nodes in the cluster, and automatic recovery of failed connections.

ServerNet cluster subsystem. The subsystem managed by the ServerNet cluster monitor process (SNETMON). The subsystem name is SCL. The subsystem number is 218. The subsystem identifier is ZSCL.

ServerNet/DA. See ServerNet device adapter (ServerNet/DA).

ServerNet device. Interface logic that is associated with a specific hardware unit, such as a processor or I/O adapter, and that provides the interface to the ServerNet communications network. The responsibilities of the ServerNet device are to transform message data into ServerNet packets, to transmit those packets, to receive ServerNet packets, and to unpack the data on behalf of the associated hardware unit. See also ServerNet subdevice.

ServerNet device adapter (ServerNet/DA). A ServerNet adapter that controls external devices. The 6760 ServerNet/DA contains up to four ServerNet addressable controllers (SACs), each of which can control either disk drives or tape drives.

ServerNet device ID. See ServerNet ID.

ServerNet diagram. A graphical layout of the logical connections between objects in the system. These objects can include processors, ServerNet routers, ServerNet adapters, disks on the SCSI bus, and so on.


Glossary ServerNet dump

ServerNet dump. To copy the memory of a processor to disk by using the ServerNet fabrics.

ServerNet end device. See ServerNet device.

ServerNet expansion board (SEB). (1) A connector board that plugs in to the backplane to allow one or more ServerNet cables to exit the rear of the enclosure. The SEBs and ServerNet cables allow processors in one group to communicate with processors in another group. Each SEB provides either the ServerNet X fabric or the ServerNet Y fabric for a group. (2) A collective term for both SEBs and modular SEBs (MSEBs) when a distinction between the two types of SEBs is not required.

ServerNet extender module (SEM). Equipment that increases the distance that ServerNet signals can be transmitted over fiber-optic cables to 40 kilometers. If multimode fiber-optic (MMF) and single-mode fiber-optic (SMF) ServerNet cables are used in the same system, the SEM converts MMF signals so that they can be transmitted by SMF ServerNet cables and converts SMF signals so that they can be transmitted by MMF ServerNet cables.

ServerNet/FX adapter. A ServerNet adapter that logically extends the ServerNet X and Y fabrics to other clusters in a Fiber Optic Extension (FOX) ring by using fiber-optic lines. Two 6740 ServerNet/FX adapters are used, one for the X ring and one for the Y ring.

ServerNet/FX 2 adapter. A ServerNet adapter that logically extends the ServerNet X and Y fabrics to other clusters in a Fiber Optic Extension (FOX) ring by using fiber-optic lines. Two 6742 ServerNet/FX 2 adapters are used, one for the X ring and one for the Y ring.

ServerNet ID. A unique identifier for an addressable unit on a ServerNet communications network. A unit can have multiple ServerNet node IDs. This ID is used for routing. Each packet has a source ServerNet node ID and a destination ServerNet node ID. A pair of processors operating in duplex mode share one ServerNet node ID.

ServerNet LAN Systems Access (SLSA) subsystem. A subsystem of the HP NonStop™ operating system for configuration and management of ServerNet local area network (LAN) objects in G-series release version updates (RVUs).

ServerNet link. Two unidirectional point-to-point communication paths, one in each direction, connecting a router to a ServerNet node or another router. Each ServerNet link contains a transmit channel and a receive channel.

ServerNet memory interface (SMI). An application-specific integrated circuit (ASIC) that provides the interface between the microprocessor and the two ServerNet fabrics and main memory.

ServerNet node. A system in a ServerNet cluster. See also node.

ServerNet node number. A number that identifies a member system in a ServerNet cluster. The ServerNet node number is a simplified expression of the ServerNet node routing ID. The ServerNet node number is assigned based on the port to which the node is


Glossary ServerNet node routing ID

connected on the cluster switch. The ServerNet node number, which can be viewed using the Subsystem Control Facility (SCF) or the OSM Service Connection, is unique for each node in a ServerNet cluster.

ServerNet node routing ID. A bit field used to route ServerNet packets across the external ServerNet X and Y fabrics. The ServerNet node routing ID occupies a portion of the ServerNet ID, and it is unique for each member, or node, in a ServerNet cluster. This term is the fully qualified form of node routing ID. The node routing ID determines the node to which a ServerNet packet is routed.

SERVERNET object type. In the Kernel subsystem, the object type for either the $ZSNET ServerNet subsystem manager process or the ServerNet X fabric or Y fabric.

ServerNet packet. The unit of transmission in a ServerNet communications network. A ServerNet packet consists of a header, a variable-size data field, and a 32-bit cyclic redundancy check (CRC) checksum covering the entire packet. The header contains fields for control, virtual memory address, and destination and source fields to identify the processor or I/O controller transmitting and receiving the packet. See also request packet and response packet.

ServerNet port. A connector used for ServerNet links.

ServerNet router. An application-specific integrated circuit (ASIC) responsible for routing ServerNet packets along ServerNet links in the ServerNet fabrics, using routing information that is present within the packets. A ServerNet router acts as a fully duplex crossbar switch, able to switch any of its input ports to any of its output ports.

ServerNet router 1. A ServerNet router that has a total of six input and six output ports. See also ServerNet router 2.

ServerNet router 2. A ServerNet router that has a total of twelve input and twelve output ports. See also ServerNet router 1.

ServerNet subdevice. An I/O device that sends and receives its information through a controlling device that acts as the ServerNet device for routing purposes.

ServerNet subdevice ID. The low-order (least significant) bits of a ServerNet ID, used by a ServerNet device to distribute incoming and outgoing information between itself and its associated subdevices.

ServerNet switch. A point-to-point networking device that connects ServerNet nodes to a single fabric (X or Y) of the ServerNet communications network. The ServerNet switch routes ServerNet packets among these nodes.

ServerNet II Switch. A 12-port network switch that provides the physical junction point to enable an HP NonStop™ server to connect to a ServerNet cluster. The ServerNet II Switch is a component of the HP NonStop™ Cluster Switch (model 6770).


Glossary ServerNet switch board

ServerNet switch board. Component in an IOAM. The ServerNet switch board provides ServerNet connections to the I/O adapters in the IOAM. It also provides maintenance functions for the modules in which they are installed.

ServerNet transaction. The bidirectional, successful transmission of a pair of ServerNet packets between two ServerNet devices. The device that originates the transaction sends a request packet, and the device that receives the request returns a response packet. See also request packet and response packet.

ServerNet wide area network (SWAN) concentrator. (1) An HP data communications peripheral that provides connectivity to an HP NonStop™ server. The SWAN concentrator supports both synchronous and asynchronous data over RS-232, RS-449, X.21, and V.35 electrical and physical interfaces. (2) A collective term for both SWAN concentrators and SWAN 2 concentrators when a distinction between the two is not required.

ServerNet wide area network (SWAN) 2 concentrator. An HP data communications peripheral that provides connectivity to an HP NonStop™ server. The SWAN 2 concentrator supports both synchronous and asynchronous data over RS-232, RS-449, X.21, and V.35 electrical and physical interfaces. The SWAN 2 concentrator is the next-generation SWAN concentrator and has 12 WAN ports.

service connection. A connection between the Compaq TSM client software running on a system console and the TSM server software running on an HP NonStop™ S-series server. A service connection can be used to communicate with the server only when the HP NonStop™ operating system is running. A service connection provides a comprehensive service and maintenance picture of the server and is used to perform most service management tasks. See also low-level link.

service equipment. The necessary equipment, usually consisting of circuit breakers and their accessories, that is located near the entrance point of supply conductors. This equipment constitutes the main control and cutoff means of the supply.

service processor (SP). A physical component of the processor multifunction (PMF) customer-replaceable unit (CRU) or I/O multifunction (IOMF) CRU that controls environmental and maintenance functions (including system load functions) in the enclosure. SPs operate in pairs to provide fault tolerance. The two SPs in group 01 of an HP NonStop™ S-series server are designated the master service processors (MSPs). Other pairs of SPs within a system are called expansion service processors (ESPs). See also expansion service processor (ESP) and master service processor (MSP).

service provider. (1) A person trained and qualified to service field-replaceable units (FRUs). (2) An organization, such as the Global Customer Support Center (GCSC), that helps you resolve problems with your HP NonStop™ server. OSM and TSM allow you to use the help of a service provider by configuring client software to support remote notification and remote access.


Glossary service side

service side. The rear side of a HP NonStop™ S-series system enclosure. It contains processor multifunction (PMF) customer-replaceable units (CRUs) or I/O multifunction (IOMF) CRUs, ServerNet expansion boards (SEBs) or modular SEBs (MSEBs), and ServerNet adapters. The service side is opposite the appearance side. All cables are accessed from the service side. Most service actions are performed from the service side. Service side doors are supplied with later NonStop S-series servers but are optional on earlier servers. Service-side doors are cosmetic and are not required for system cooling.

session. In the Open System Services (OSS) environment, a set of process groups associated for job control purposes. A session can have a controlling terminal.

session leader. In the Open System Services (OSS) environment, the process that created a session.

session lifetime. In the Open System Services (OSS) environment, the period that begins when a session is created and ends when the lifetime of the last remaining process group of the session ends.

setup configuration. A simple stand-alone network used to configure the OSM or TSM environment. The setup configuration for an HP NonStop™ S-series server consists of the server, the primary system console, an Ethernet hub, and two local area network (LAN) cables. One cable connects the primary system console to the hub, and another cable connects the hub to a processor multifunction (PMF) customer-replaceable unit (CRU) in group 01 of the server. When OSM or TSM configuration is complete, the setup configuration can serve as the working network configuration. Variations of the setup configuration can be constructed using additional cables and hubs to increase fault tolerance.

set-user-ID program. In the Open System Services (OSS) environment, a program file that has the S_ISUID bit set in its file mode.

shadow. The processor used to check the results of the master processor on a processor board.

shared memory. An interprocess communication mechanism that allows two or more processes to share a given region of memory.

Shared Millicode Library. An intrinsic library containing privileged or TNS-derived millicode routines used by many native-compiled programs and by emulated TNS programs. This library includes efficient string-move operations, TNS floating-point emulation, and various privileged-only operations. These routines are mode independent. They comply with native calling conventions but can be directly invoked from any mode without changing execution modes.

shared run-time library (SRL). A collection of procedures whose code and data can be loaded and executed only at a specific assigned virtual memory address (the same address in all processes). SRLs use direct addressing and do not have run-time resolution of links to and from the main program and other independent libraries.


Glossary shell

Contrast with dynamic-link library (DLL). See also TNS shared run-time library (TNS SRL) and TNS/R native shared run-time library (TNS/R native SRL).

shell. (1) In the Open System Services (OSS) environment, a program that interprets sequences of text input as commands. A shell can operate on an input stream, or it can interactively prompt and read commands from a terminal. (2) An envelope of code that provides a convenient way to call a procedure in another execution environment. See also TNS to native-mode access shell.

shell generator. A software tool that, given a procedure interface definition coded in pTAL for a native-mode library procedure, produces a custom shell routine to provide access from TNS object code to that native-mode procedure. See also TNS to native-mode access shell.

shell map. An address table created by the HP NonStop™ operating system that contains the entry point addresses of all available TNS to native-mode access shells. See also TNS to native-mode access shell.

shielded twisted pair (STP). A transmission medium consisting of two twisted conductors with a foil or braid shield. Contrast with unshielded twisted pair (UTP).

shutdown file. A file invoked by the local operator or by another shutdown file that contains commands to shut down system devices, communications lines, and system and application software. Contrast with startup file.

SID. See system image disk (SID) or source ServerNet ID (SID).

signal. The method by which an environment notifies a process of an event. Signals are used to notify a process when an error that is not related to input or output has occurred. See also Open System Services (OSS) signal and TNS/R native signal.

signal delivery. The time when Open System Services (OSS) takes the action appropriate for a specific process and a specific signal.

signal generation. The time when an event occurs that causes a signal for a process.

signal handler. A function or procedure that is executed when a specific signal is delivered to a specific process.

Signaling System Number 7 (SS7). The protocol used in public networks to establish connections between switches.

signal mask. The set of signals that are currently blocked from delivery to a specific process.

signal reference grid. A series of conductors, constructed of pure or composite metals (for example, copper) with good surface conductivity. A superior signal reference grid is installed on the subfloor of a computer room and connected to the raised-floor


Glossary Simple Network Management Protocol (SNMP)

structure to establish constant and equal potential for all equipment in the computer room that is connected to it.

Simple Network Management Protocol (SNMP). An asynchronous request-response protocol used for network management. SNMP originated as a means for managing Transmission Control Protocol/Internet Protocol (TCP/IP) and Ethernet networks. OSM and TSM can include an SNMP-compliant interface for communication between the system console and HP NonStop™ S-series server.

single-high stack. A stack that includes a base, a frame, an HP NonStop™ S-series system enclosure, and power shelf. Contrast with double-high stack.

single-mode fiber-optic (SMF) plug-in card (PIC). A plug-in card (PIC) that supports the single-mode fiber-optic (SMF) interface.

single-mode fiber-optic (SMF) ServerNet cable. A fiber-optic cable that allows only one mode to propagate. An SMF ServerNet cable has a small-diameter core for optimized long-distance transmission. See also multimode fiber-optic (MMF) ServerNet cable.

single-wide plug-in card (PIC). A small-form-factor plug-in card (PIC) that occupies one PIC slot within a ServerNet adapter or an HP NonStop™ cluster switch. See also double-wide plug-in card (PIC).

sinusoidal. A waveform that can be mathematically expressed by the sine function.

SIT. See system image tape (SIT).

site update tape (SUT). One or more tapes that contain each target system’s site-specific subvolume and various products. Each product contains a softdoc and a complete set of files. A SUT is delivered with every new HP NonStop™ system and can be ordered whenever a new release version update (RVU) of the system software is available. A full SUT contains the current RVU of the HP NonStop operating system and all product software that has been ordered with it. A partial SUT contains a subset of products for the current RVU.

SIV. See system interrupt vector (SIV).

skin effect. The tendency of higher frequency signals to flow on the outside surface, or skin, of a conductor instead of through the entire cross-section of the conductor. The result is less total conductor area available for carrying current and an increase in the resistance of the conductor at that high signal frequency.

slot. (1) A physical, labeled space for a customer-replaceable unit (CRU) or field-replaceable unit (FRU) that is part of an enclosure or another CRU or FRU. (2) Part of the group, module, slot naming convention for uniquely identifying the logical location of a component within a system. A slot is a subset of a module.


Glossary slot location

slot location. A three-number identifier for a particular slot on a system that consists of the group number, module number, and slot number; for example, 02,01,08 (group 02, module 01, slot 08).

SLSA subsystem. See ServerNet LAN Systems Access (SLSA) subsystem.

small computer system interface (SCSI). An ANSI-standard protocol used by a controller to access a device.

SMB. See serial maintenance bus (SMB).

SMB domain. See serial maintenance bus (SMB) domain.

SMF. See HP NonStop™ Storage Management Foundation (SMF).

SMF PIC. See single-mode fiber-optic (SMF) plug-in card (PIC).

SMF ServerNet cable. See single-mode fiber-optic (SMF) ServerNet cable.

SMI. See ServerNet memory interface (SMI).

SMN. The mnemonic name for the external system area network manager process (SANMAN).

SMP. See Security Manager Process (SMP).

SMT. See SWAN manager task (SMT).

snapshot. (1) A file that can be created by OSM and TSM client software to record information about the status of an HP NonStop™ server, including the attributes values of all system resources, at the time it was created. The file can be forwarded to your service provider to help with troubleshooting problems. (2) For Distributed Systems Management/Software Configuration Manager (DSM/SCM), a list of the target system tape and disk locations, file fingerprints for files managed by DSM/SCM, and DSM/SCM target information. The snapshot is compiled on the target system from the target database and sent to the host system to store in the host database. An instruction to create a snapshot is part of every activation package sent from the host and can also be requested independently through the Target Interface. (3) In Visual Inspect, a disk file created by the Save Snapshot command or by DMON if the SAVEABEND attribute for a process is ON and the process abends. A snapshot is an image of the process, its data, and its status at the moment it was saved. Visual Inspect and Inspect can be used to debug snapshots, but the Inspect product refers to a snapshot as a save file.

SNDA. See ServerNet device adapter (ServerNet/DA).

SNETMON. See ServerNet cluster monitor process (SNETMON).

SNMP. See Simple Network Management Protocol (SNMP).


Glossary SNMP task

SNMP task. A task that runs in each ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP) as part of the WAN architecture. This task accepts and replies to Simple Network Management Protocol (SNMP) request messages.

socket. An end-point for stream-oriented communication. A socket has a file descriptor.

soft reset. An action performed on an HP NonStop™ Cluster Switch that restarts the firmware on the cluster switch but does not interfere with ServerNet passthrough data traffic.

software configuration incident report. A type of incident report that reports changes in the software configuration of the server. A software configuration incident report includes the server’s software configuration file.

Software Developers Kit (SDK). A set of tools for use by customer developers of applications. These tools can include an editor, a compiler, libraries, and so on.

software product revision (SPR). The method of releasing incremental software updates on HP NonStop™ S-series systems. An SPR can include one or more corrections to code, or it can contain code that adds new function to a software product.

source ServerNet ID (SID). A field in the ServerNet packet header indicating the source of the packet.

SP. See service processor (SP).

special character. A character entered from a terminal that has an effect other than being part of the input stream from that terminal.

special file. A file in the Open System Services (OSS) file system that is not a regular file. Special files include directories, FIFOs, and character special files such as terminal device files. Contrast with regular file.

SP event message. See service processor (SP).

SPI. See Subsystem Programmatic Interface (SPI).

S-PIC. See SCSI plug-in card (S-PIC).

split-star topology. A network topology that uses up to two HP NonStop™ Cluster Switches for each external fabric. External routing is implemented between the two starred halves of a ServerNet cluster. (A starred half consists of up to eight nodes attached to one set of cluster switches.) The starred segments are joined by four-lane links. Introduced with the G06.12 release version update (RVU), the split-star topology supports up to 16 nodes. See also star topology, tri-star topology, and layered topology.


Glossary spooler

spooler. The collection of files and processes that manages the printers and print jobs on the system.

SPR. See software product revision (SPR).

SP Tool Application. A PC-based software application that you can use to request information from the master service processors (MSPs) in an HP NonStop™ S-series server. This application is intended for use only by trained service providers.

SRL. See shared run-time library (SRL).

SRM. See system resource model (SRM).

SS7. See Signaling System Number 7 (SS7).

SS7TE PIC. See SS7TE plug-in card (PIC).

SS7TE2 PIC. See SS7TE2 plug-in card (PIC).

SS7TE plug-in card (PIC). A plug-in card (PIC) used in the 6763 Common Communication ServerNet adapter (CCSA) that supports the EIA-232, EIA-449, V.35, and X.21 interfaces.

SS7TE2 plug-in card (PIC). A plug-in card (PIC) used in the 6763 Common Communication ServerNet adapter (CCSA) that supports the E1, J1, and T1 interfaces.

S-SAC. See SCSI ServerNet addressable controller (S-SAC).

SSI log. See System Service Information (SSI) log.

stackable enclosure. An enclosure that can rest on top of another enclosure. A stackable enclosure is not installed on a frame base. Contrast with base enclosure.

standby power generator. A turbine-driven or engine-driven generator that provides a backup source of power to designated loads. Often used to supplement an uninterruptible power supply (UPS) in the event of extended utility outages.

star group. One set of X and Y HP NonStop™ Cluster Switches and the ServerNet nodes (up to eight) that are connected to them. A star group can be thought of as a segment of a split-star or tri-star topology. A split-star topology can contain up to two star groups. A tri-star topology can contain up to three star groups.

start mode. An attribute of Subsystem Control Facility (SCF) PROCESS objects that controls when and if an application process starts in G-series release version updates (RVUs).

star topology. A network topology in which all nodes are connected to a central hub (HP NonStop™ Cluster Switch). Each node has its own connection to the network, so a break in the connection does not affect other nodes in the network. In a ServerNet cluster, a star topology requires one cluster switch for each external fabric and can


Glossary startup file

support up to eight nodes. See also split-star topology, tri-star topology, and layered topology.

startup file. A file invoked by the local operator or by another startup file that contains commands to start up system devices, communications lines, and system and application software. Contrast with shutdown file.

state. In Subsystem Control Facility (SCF), one of the generally defined possible conditions of an object with respect to the management of that object. Examples of states are DEFINED, STARTED, and STOPPED.

static information. Information that represents the set of customer-replaceable units (CRUs) on an HP NonStop™ S-series system. Contrast with dynamic information.

static server. In the Guardian environment, a process that runs continuously and provides a specific service to other processes. A static server differs from a traditional UNIX demon in that a demon actively looks for tasks to perform. A static server performs only tasks brought to its attention by a client (requestor) process. See also demon.

static translation. A TNS translation step explicitly invoked from the command line before a TNS object file is executed. The Accelerator is a static translator.

STFs. See super time factors (STFs).

storage pool. A set of physical disk volumes administered as a set of logical disk volumes. A logical disk volume can span multiple physical disk volumes. When a logical disk volume becomes full, more physical disk volumes can be added.

storage-pool file. A file containing a list of disk volumes to be used by an Open System Services (OSS) fileset. As these volumes are filled, more volumes can be added to the storage-pool file.

storage subsystem. A subsystem of the HP NonStop™ operating system that handles configuration and management of disk and tape devices in G-series release version updates (RVUs).

storage subsystem manager process. The generic process that starts and manages disk and tape drives. The $ZZSTO storage subsystem manager process is started and managed by the $ZZKRN Kernel subsystem manager process through the $ZPM persistence manager process.

store and forward routing. A form of message routing whereby a router must receive an entire packet or message before it can start to forward the packet or message to the next router. Contrast with wormhole routing.

STP. See shielded twisted pair (STP).

strictly conforming POSIX.1 application. An application that requires only the facilities described in ISO/IEC IS 9945-1:1990 and the applicable computer language


Glossary structured view of the user ID

standards. Such an application must accept any behavior or value described in ISO/IEC IS 9945-1:1990 as unspecified or implementation-defined and, for symbolic constants, accept any value permitted by ISO/IEC IS 9945-1:1990.

structured view of the user ID. A view of the HP NonStop™ operating system user ID, normally used in the Guardian environment, that consists of either the group-number, user-number pair of values or the group-name.user-name pair of values.

subnet. See subnetwork.

subnetwork. A physical network within an Internet protocol (IP) network. Each IP network can be divided into a number of subnetworks. Within a given network, each subnetwork is treated as a separate network. Outside the network, the subnetworks appear as part of a single network. The terms subnetwork and subnet are used interchangeably.

subnetwork address. An extension of the Internet protocol (IP) addressing scheme that allows a site to use a single IP address for multiple physical networks. A subnetwork address is created by dividing the local part of an IP address into a subnetwork number (identifying a particular subnetwork) and a host number (uniquely identifying the host system within the subnetwork). The terms subnetwork address and subnet address are used interchangeably.

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.


Glossary Subsystem Control Facility (SCF)

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™ 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), COBOL, and HP Tandem Advanced Command Language (TACL) for inclusion in programs, macros, and routines using the interface procedures; and definition files in Data Definition Language (DDL) for programmers writing their own subsystems.

subvolume. A group of related files stored on a disk. All the files have the same volume and subvolume name, but each file has a unique file identifier.

summary report. A brief informational listing of status or configuration information provided by the Subsystem Control Facility (SCF) STATUS or INFO command. Contrast with detailed report.

superblock. The part of the Open System Services (OSS) environment that contains all the information about the current state of the OSS file system. The superblock contains such items as the free list and the size of inodes.

super group. The group of user IDs that have 255 as the group number. This group has special privileges; many HP utilities have commands or functions that can be executed only by a member of the super group.

super-group user. A user who can read, write, execute, and purge most files on the system. Super-group users have user IDs that have 255 as the group number.

super ID. On HP NonStop™ systems, a privileged user who can read, write, execute, and purge all files on the system. The super ID is usually a member of a system-supervisor group.


Glossary super time factors (STFs)

The super ID has the set of special permissions called appropriate privileges. In the Guardian environment, the structured view of the super ID, which is (255, 255), is most commonly used. In the Open System Services (OSS) environment, the scalar view of the super ID, which is 65535, is most commonly used.

super time factors (STFs). An enhancement to the Expand product that allows the extension of automatically calculated time factors to line speeds greater than 224 kilobits/second. These time factors are logarithmic based and allow specification of a much broader range of line performance.

superuser. See super ID.

supplementary group ID. An Open System Services (OSS) process attribute that is used to determine the file-access permissions for the process.

support planner. The person who creates the operational environment for the system and is responsible for the support of the system. This person creates the startup and shutdown files, performs replacement operations, and prepares the system for upgrades and additions.

surge. An increase in the amplitude of source voltage of short duration.

SUT. See site update tape (SUT).

SVID. The System V Interface Definition for UNIX, published by AT&T.

SVR4. System V Release 4, a specific implementation of UNIX. See also System V.

SWAN concentrator. See ServerNet wide area network (SWAN) concentrator.

SWAN 2 concentrator. See ServerNet wide area network (SWAN) 2 concentrator.

SWAN manager task (SMT). A manager task that is provided as part of the wide area network (WAN) subsystem. The SMT runs in each communications line interface processor (CLIP) and provides a variety of management functions such as coordinating data link control (DLC) and diagnostic task downloads.

SWID. The software identification tool invoked by the system generation program that audits file identification information about your software.

switch. See HP NonStop™ Cluster Switch (model 6770) and HP NonStop™ ServerNet Switch (model 6780).

switch enclosure. See cluster switch enclosure.

switch group. See cluster switch group.

switch layer. See cluster switch layer.

switch layer number. See cluster switch layer number.


Glossary switch logic board

switch logic board. See cluster switch logic board.

switch mode power supply. A computer power supply that uses a pulse-width modulation switching inverter and nonlinear current draw characteristics. Switch-mode power supplies are widely used because of their small size and efficiency.

switch rack. See cluster switch rack.

switch zone. See cluster switch zone.

switched connect. Connection to the Enterprise Storage System (ESS) through a Fibre Channel switch (FC switch).

symbol. (1) The symbolic name of a value, typically a function entry point or a data location. In the context of loadable libraries, symbols are defined in loadfiles and referenced in the same or other loadfiles. (2) Within the ServerNet architecture, the nine or more bits that encode 8-bit data and protocol commands.

symbolic link. In the Open System Services (OSS) file system and Network File System (NFS), a type of special file that acts as a name pointer to another file. A symbolic link contains a pathname and can be used to point to a file in another fileset. Symbolic links are not included in ISO/IEC IS 9945-1:1990. Contrast with hard link.

symbolic reference. An occurrence in code or data of the value of a symbol. The symbolic reference is bound (resolved and made usable) by assigning to it the value of a definition of that symbol. The symbol value is normally the address of a function or variable named by the symbol. In position-independent code (PIC) loadfiles, symbolic references occur only in data.

symbols region. See Inspect region.

SYSGENR. The system generation program that generates a customized version of the HP NonStop™ operating system for G-series release version updates (RVUs).

SYSnn subvolume. A subvolume on the $SYSTEM volume where the new version of the HP NonStop™ operating system image is located. Also located on the SYSnn subvolume is system-dependent and release version update (RVU)-dependent software. nn is an octal number in the range %00 through %77.

SYSPOOL. The system data space that remains in memory after all system data structures are built by the HP NonStop™ operating system at the time of a processor load.

system. All the processors, controllers, firmware, peripheral devices, software, and related components that are directly connected together to form an entity that is managed by one HP NonStop™ operating system image and operated as one computer. See also node.

system area network management process. See external system area network manager process (SANMAN).


Glossary System Code (SC)

System Code (SC). See TNS code space.

system code. A logically distinct part of the HP NonStop™ operating system that consists of operating system procedures shared by all processors.

system configuration database. The database file on the $SYSTEM.ZSYSCONF subvolume that contains configuration information for all system objects that can be configured by the Subsystem Control Facility (SCF). Configuration information for all system objects that can be configured during system generation is contained on the $SYSTEM.SYSnn subvolume. See also configuration file and SYSnn subvolume.

system console. An HP-approved personal computer used to run maintenance and diagnostic software for HP NonStop™ servers. New system consoles are preconfigured with the required HP and third-party software. When upgrading to the latest RVU, software upgrades can be installed from the HP NonStop System Console Installer CD. System consoles communicate with NonStop servers over a dedicated local area network (LAN) or a nondedicated (public) LAN. System consoles configured as the primary and backup dial-out points are referred to as the primary and backup system consoles, respectively.

system enclosure. An enclosure for system components. Processor enclosures and I/O enclosures are both system enclosures. Contrast with peripheral enclosure.

system engineer (SE). See service provider.

system entry-point (SEP) table. A table used on TNS systems that stores the XEP entry value for each TNS operating system procedure entry point.

system expansion. The process of making a target system larger by adding enclosures to it. The enclosures being added can be either new enclosures or enclosures from a donor system. Contrast with system reduction.

system generation. The process of creating an operating system to support a particular system configuration and release version update (RVU).

system image disk (SID). A disk copy of the HP NonStop™ operating system produced during system configuration. The DISKGEN utility copies operating system files to the SID.

system image tape (SIT). A tape that can be used to perform a system load on a system if the system subvolume has become corrupted on both $SYSTEM disks. The tape contains a minimum set of software necessary to bring up and run the system. Use the SIT only for disaster recovery. It is not needed for normal system load. Contact the Global Customer Support Center (GCSC) before loading the system from a SIT; many additional steps are required to restore your system to working order. See also tape load.


Glossary system interrupt vector (SIV)

system interrupt vector (SIV). An HP NonStop™ operating system data structure that contains the addresses of interrupt handlers, parameters passed to interrupt handlers by special interrupt microcode, and other interrupt processing information.

System Library (SL). See TNS code space.

system library. A logically distinct part of the HP NonStop™ operating system that consists of user-callable library procedures and kernel procedures.

system load. (1) To start the system; to load the HP NonStop™ operating system image into the memory of a processor. See RELOAD. (2) The process of loading the operating system. A system load changes a system from an inactive to an active (or operational) state by loading software that establishes communication between the operating system and configured system peripherals.

system-managed process. Another name for a generic process.

system manager. See manager.

system number. See Expand node number.

system operator. See local operator and remote operator.

system planner. The person who plans for the hardware and software installation of a new system or for changes to a system already installed. This person arranges for site preparation, schedules the installation, and completes the Installation Document Packet.

system process. (1) A privileged process that comes into existence at system-load time and exists continuously for a given configuration for as long as the processor remains operable. (2) An HP NonStop™ operating system process, such as the memory manager, the monitor, and the input/output (I/O) control processes. The files containing system processes are invoked by ALLPROCESSORS paragraph entries. (3) A part of a single copy of the HP NonStop operating system with Open System Services (OSS) interfaces. A system process does not have an OSS process ID.

system reduction. The process of making a donor system smaller by removing enclosures from it. The enclosures removed from a donor system might be added to a target system. Contrast with system expansion.

system resizing. See system expansion or system reduction.


Glossary system resource model (SRM)

system resource model (SRM). A collection of C++ objects that model the diagnostic and serviceability state behavior of the system resources discovered and managed by the Compaq TSM package. The SRM has these attributes:

system serial number. A unique identifier, typically five or six alphanumeric characters, assigned to an HP NonStop™ server when it is built.

System Service Information (SSI) log. An Event Management Service (EMS) log that includes information about customer-replaceable unit (CRU) removal, CRU insertion, firmware loading, security authentication, incident report dial-out authorization, incident report dial-out failure, and incident report confirmation. The SSI log can be viewed using the OSM or TSM Event Viewer.

system terminal. See system console.

System V. A version of UNIX developed and marketed originally by AT&T.

TACL. See HP Tandem Advanced Command Language (TACL).

TAL. See HP Transaction Application Language (TAL).

tape bootstrap. The program on a system image tape (SIT) that reads the rest of the SIT during tape load and writes it to the system disk.

tape drive. A device that moves magnetic tape past magnetic read/write heads, which read data from or write data to the tape.

tape dump. To copy the memory of a processor to tape.

tape library. A storage device consisting of magnetic tape drives, multiple storage locations for magnetic tape cartridges, an automatic mechanism for loading the cartridges into and unloading them from the drives, and a means for an operator to load cartridges into or remove cartridges from the tape library.

tape load. A system load. A tape load is the process of reading a system image tape (SIT) and writing it to the system disk. Performing a tape load from a SIT to restore the system image files to the $SYSTEM disk is generally not recommended. Perform a tape load only with the advice of the Global Customer Support Center (GCSC) or your service provider. Loading from a tape reinitializes the disk directory.

TAPE object type. The Subsystem Control Facility (SCF) object type for all tape drives attached to your system.

target system. The computer system you make larger by adding enclosures, using a process known as system expansion. See also donor system.

Generic process name $ZZKRN.#TSM-SRM

Process name $ZTSM

Program file name $SYSTEM.SYSnn.SRM


Glossary TB

TB. See terabyte (TB).

TCP. See Transmission Control Protocol (TCP).

TCP/IP. See Transmission Control Protocol/Internet Protocol (TCP/IP).

TEMPLI. The Event Management Service (EMS) template installation program that merges template object files from specified subsystems and produces resident and nonresident template files.

terabyte (TB). A unit of measurement equal to 1,099,511,627,776 bytes (1024 gigabytes). See also gigabyte (GB), kilobyte (KB), and megabyte (MB).

terminal. A type of Open System Services (OSS) character special file that conforms to the interface description in Clause 7 of ISO/IEC IS 9945-1:1990.

terminator. A resistor connected to a signal wire in a bus or network for the purpose of impedance matching to prevent reflections. SCSI chains, Ethernet cables, and some LocalTalk wiring configurations require terminators.

Tetra 8 topology. A tetrahedral topology of HP NonStop™ S-series servers that allows a maximum of four processor enclosures (eight processors) and eight I/O enclosures. Contrast with Tetra 16 topology.

Tetra 16 topology. A tetrahedral topology of HP NonStop™ S-series servers that allows a maximum of eight processor enclosures (16 processors). The maximum number of I/O enclosures allowed by the Tetra 16 topology varies depending on the release version update (RVU) and the server model. Contrast with Tetra 8 topology.

tetrahedral topology. A topology of HP NonStop™ S-series servers in which the ServerNet connections between the processor enclosures form a tetrahedron. See also tetrahedron and topology.

tetrahedron. A geometric solid with four vertices. The edges of the tetrahedron represent connections between the vertices in which each vertex connects to all other vertices. For ServerNet, a tetrahedron is four processors interconnected by ServerNet links so as to form a conceptual tetrahedron. Each processor therefore has a direct connection to the other three processors. See tetrahedral topology.

text string. A variable-length sequence of ASCII characters, defined in the CONFTEXT file, that an identifier represents. When Distributed Systems Management/Software Configuration Manager (DSM/SCM) encounters an identifier, it substitutes the associated text string for the identifier.

TF. See time factor (TF).

TFDS. See HP Tandem Failure Data System (TFDS).

TFTP. See Trivial File Transfer Protocol (TFTP).


Glossary THD

THD. See total harmonic distortion (THD).

three point fall of potential measurement method. The measurement of a grounding electrode (such as a ground rod) where ground resistance is measured with respect to two other points. The ratio of the measurements determines the resistance of the grounding electrode.

TIM. See HP NonStop™ Technical Library (NTL).

time factor (TF). A number assigned to a line, path, or route to indicate its efficiency in transporting data. The lower the time factor, the more efficient the line, path, or route. See also surge.

TLB. See translation lookaside buffer (TLB).

TMF. See HP NonStop™ Transaction Management Facility (TMF).

TNS. Refers to fault-tolerant HP computers that support the HP NonStop™ operating system and are based on microcoded complex instruction-set computing (CISC) technology. TNS systems run the TNS instruction set. Contrast with TNS/R.

TNS accelerated mode. A TNS emulation environment on a TNS/R system in which accelerated TNS object files are run. TNS instructions have been previously translated into optimized sequences of MIPS instructions. TNS accelerated mode runs much faster than TNS interpreted mode. Accelerated or interpreted TNS object code cannot be mixed with or called by native mode object code.Contrast with TNS/R native mode.

TNS C compiler. The C compiler that generates TNS object files. Contrast with TNS/R native C compiler.

TNS code segment. One of up to 32 128-kilobyte areas of TNS object code within a TNS code space. Each segment contains the TNS instructions for up to 510 complete routines. Each TNS code segment contains its own procedure entry-point (PEP) table and external entry-point (XEP) table. It can also contain read-only data.

TNS code segment identifier. A seven-bit value in which the most significant two bits encode a code space (user code, user library, system code, or system library) and the five remaining bits encode a code segment index in the range 0 through 31.

TNS code segment index. A value in the range 0 through 31 that indexes a code segment within the current user code, user library, system code, or system library space. This value can be encoded in five bits.

TNS code space. One of four addressable collections of TNS object code in a TNS process. They are User Code (UC), User Library (UL), System Code (SC), and System Library (SL). UC and UL exist on a per-process basis. SC and SL exist on a per-node basis.


Glossary TNS compiler

TNS compiler. A compiler in the TNS development environment that generates 16-bit TNS object code following the TNS conventions for memory, stacks, 16-bit registers, and call linkage. The TNS C compiler is an example of such a compiler. Contrast with TNS/R native compiler.

TNS emulation software. The set of tools, libraries, and system services for running TNS object code on TNS/R systems. On a TNS/R system, the TNS emulation software includes the TNS Object Code Interpreter (OCI), the Accelerator, and various millicode libraries.

TNS fixup. A task performed at process startup time when executing a TNS object file. This task involves building the procedure entry point (PEP) table and external entry point (XEP) table and patching PCAL and XCAL instructions in a TNS object file before loading the file into memory. See also TNS mode, procedure entry-point (PEP) table, and external entry-point (XEP) table.

TNS instructions. Stack-oriented, 16-bit machine instructions that are directly executed on TNS systems by hardware and microcode. TNS instructions can be emulated on TNS/R systems by using millicode, an interpreter, and either translation or acceleration. Contrast with MIPS RISC instructions.

TNS interpreted mode. A TNS emulation environment on a TNS/R system in which individual TNS instructions in a TNS object file are directly executed by interpretation rather than permanently translated into MIPS instructions. TNS interpreted mode runs slower than TNS accelerated mode. Each TNS instruction is decoded each time it is executed, and no optimizations between TNS instructions are possible. TNS interpreted mode is used when a TNS object file has not been accelerated for that hardware system, and it is also sometimes used for brief periods within accelerated object files. Accelerated or interpreted TNS object code cannot be mixed with or called by native mode object code. Contrast with TNS accelerated mode and TNS/R native mode.

TNS library. A single, optional, TNS-compiled loadfile associated with one or more application loadfiles. If a user library has its own global or static variables, it is called a TNS shared run-time library (TNS SRL). Otherwise it is called a User Library (UL).

TNS loading. A task performed at process startup time when executing a TNS object file. This task involves mapping the TNS instructions, procedure entry-point (PEP) table, and external entry-point (XEP) table from a TNS object file into memory.

TNS mode. The operational environment in which TNS instructions execute by inline interpretation. See also accelerated mode and TNS/R native mode.

TNS object code. The TNS instructions that result from processing program source code with a TNS compiler. TNS object code executes on TNS and TNS/R systems.

TNS object file. An object file created by a TNS compiler or the Binder. A TNS object file contains TNS instructions. TNS object files can be processed by the Accelerator to


Glossary TNS procedure label

produce to produce accelerated object files. A TNS object file can be run on TNS and TNS/R systems.

TNS procedure label. A 16-bit identifier for an internal or external procedure used by the TNS object code of a TNS process. The most-significant 7 bits are a TNS code segment identifier: 2 bits for the TNS code space and 5 bits for the TNS code segment index. The least-significant 9 bits are an index into the target segment's procedure entry-point (PEP) table. When the TNS code space bits of a TNS procedure label are %B10, the remaining 14 bits are an index into the system's shell map table, not a segment index and PEP index.

TNS process. A process whose main program object file is a TNS object file, compiled using a TNS compiler. A TNS process executes in interpreted or accelerated mode while within itself, when calling a user library, or when calling into TNS system libraries. A TNS process temporarily executes in native mode when calling into native-compiled parts of the system library. Object files within a TNS process might be accelerated or not, with automatic switching between accelerated and interpreted modes on calls and returns between those parts. Contrast with TNS/R native process.

TNS shared run-time library (TNS SRL). A shared run-time library (SRL) available to TNS processes in the Open System Services (OSS) environment. A TNS process can have only one TNS SRL. A TNS SRL is implemented as a special user library that allows shared global data.

TNS signal. A signal model available to TNS processes in the Guardian environment.

TNS stack segment. See TNS user data segment.

TNS system library. A collection of HP-supplied TNS-compiled routines available to all TNS processes. There is no per-program or per-process customization of this library. All routines are immediately available to a new process. No dynamic loading of code or creation of instance data segments is involved. See also native system library.

TNS to native-mode access shell. A shell object file, generated by the shell generator, that supports procedure calls from TNS object files to a particular TNS/R native-mode library routine. The shell suspends TNS code emulation, copies and reformats parameters from the TNS execution stack to the native execution stack, calls the desired routine in native mode, copies back the function result, and resumes TNS code emulation. A custom shell exists for each native-mode library routine that can be called from TNS object files. See also shell generator and shell map.

TNS user data segment. In a TNS process, the segment at virtual address zero. Its length is limited to 128 kilobytes. A TNS program's global variables, stack, and 16-bit heap must fit within the first 64 kilobytes. See also compiler extended-data segment.

TNS user library. A user library available to TNS processes in the Guardian environment.

TNS word. An instruction-set-defined unit of memory. A TNS word is 2 bytes (16 bits) wide, beginning on any 2-byte boundary in memory. See also MIPS RISC word and word.


Glossary TNS/R

TNS/R. Refers to fault-tolerant HP computers that support the HP NonStop™ operating system and are based on 32-bit reduced instruction-set computing (RISC) technology. TNS/R systems run the MIPS-1 RISC instruction set and can run TNS object files by interpretation or after acceleration. TNS/R systems include all HP systems that use NSR-x processors. Contrast with TNS.

TNS/R library. A TNS/R native-mode library. For a PIC-compiled application, TNS/R libraries can be dynamic-link libraries (DLLs) or hybridized native shared runtime libraries (SRLs). For an application that is not PIC compiled, TNS/R libraries can only be native SRLs.

TNS/R native C compiler. The C compiler that generates TNS/R object files. Contrast with TNS C compiler.

TNS/R native compiler. A compiler in the TNS/R development environment that generates TNS/R native object code, following the TNS/R native-mode conventions for memory, stack, 32-bit registers, and call linkage. The TNS/R native C compiler is an example of such a compiler. Contrast with TNS compiler.

TNS/R native mode. The primary execution environment on a TNS/R system, in which native-compiled MIPS object code executes, following TNS/R native-mode compiler conventions for data locations, addressing, stack frames, registers, and call linkage. Contrast with TNS interpreted mode and TNS accelerated mode.

TNS/R native object code. The MIPS RISC instructions that result from processing program source code with a TNS/R native compiler. TNS/R native object code executes only on TNS/R systems, not on TNS systems.

TNS/R native object file. An object file created by a TNS/R native compiler that contains MIPS RISC instructions and other information needed to construct the code spaces and the initial data for a TNS/R native process.

TNS/R native process. A process initiated by executing a TNS/R native object file. Contrast with TNS process.

TNS/R native shared run-time library (TNS/R native SRL). A shared run-time library (SRL) available to TNS/R native processes in both the Guardian and Open System Services (OSS) environments. TNS/R native SRLs can be either public or private. A TNS/R native process can have multiple public SRLs but only one private SRL.

TNS/R native signal. A signal model available to TNS/R native processes in both the Guardian and Open System Services (OSS) environments. TNS/R native signals are used for error exception handling.

TNS/R native user library. A user library available to TNS/R native processes in both the Guardian and Open System Services (OSS) environments. A TNS/R native user library is implemented as a special private TNS/R native shared run-time library (TNS/R native SRL).


Glossary token

token. A character sequence processed as a unit by a command process.

Token-Ring ServerNet adapter (TRSA). A ServerNet adapter that provides a single line from an HP NonStop™ server to a token-ring network, allowing the server to act as a station on the ring. The 3862 TRSA can be configured to support network speeds of 4 megabits/second (Mbps) or 16 Mbps, and the media can be either shielded twisted pair (STP) or unshielded twisted pair (UTP).

topology. The physical layout of components that define a local area network (LAN), wide area network (WAN), or ServerNet fabric. See also star topology and tetrahedral topology.

topology branch. A processor enclosure and the I/O enclosures attached to it.

total harmonic distortion (THD). The ratio, expressed in percent, of the root mean square (rms) value for all harmonics present in the output of a power source to the total rms voltage at the output, for a pure sine-wave output. The lower the THD, the better the power source.

Total Information Manager (TIM). See HP NonStop™ Technical Library (NTL).

transformer. Equipment used to step up or step down alternating-current (AC) voltage to meet the specific requirements of the load. A transformer also provides isolation and noise-attenuation properties.

transient. A short-duration, high-amplitude impulse that is imposed on the normal voltage or current.

translation lookaside buffer (TLB). A special-purpose cache, part of the RISC processor chip, that is used in quickly translating virtual addresses to physical addresses. This rapid translation is accomplished by remembering and reusing the translations of recently referenced pages.

Transmission Control Protocol (TCP). A connection-oriented protocol that provides for the reliable exchange of data between a sending and a receiving system. TCP implements functions corresponding to the Open Systems Interconnection (OSI) reference model Layer 4, the transport layer.

Transmission Control Protocol/Internet Protocol (TCP/IP). A set of layered communication protocols for connecting workstations and larger systems in both local area networks (LANs) and wide area networks (WANs). See also HP NonStop™ TCP/IP and Parallel Library TCP/IP.

tri-star topology. A network topology that uses up to three HP NonStop™ Cluster Switches for each external fabric. External routing is implemented between the three star groups of a ServerNet cluster. (A star group consists of the eight nodes attached to one set of cluster switches.) The star groups are joined by two-lane links. Introduced with the G06.14 release version update (RVU), the tri-star topology supports up to 24 nodes. See also split-star topology, star topology, and layered topology.


Glossary Trivial File Transfer Protocol (TFTP)

Trivial File Transfer Protocol (TFTP). A protocol defined by Request for Comments (RFC) 1350. TFTP is used as a data link control (DLC) and diagnostic task.

TRSA. See Token-Ring ServerNet adapter (TRSA).

TSM. See Compaq TSM.

TSM client software. See Compaq TSM client software.

TSM Event Viewer. See Compaq TSM Event Viewer.

TSM Low-Level Link. See Compaq TSM Low-Level Link.

TSM Notification Director. A component of the Compaq TSM client software. The TSM Notification Director receives incident reports from an HP NonStop™ S-series server, displays them, and allows you to take action or forward the incident reports to your service provider for resolution. The TSM Notification Director can be configured to run on a system console at all times, even when other TSM applications are not being used.

TSM package. See Compaq TSM package.

TSM server software. See Compaq TSM server software.

TSM Service Application. See Compaq TSM Service Application.

two-lane link. The two single-mode fiber-optic (SMF) ServerNet cables that connect the HP NonStop™ Cluster Switches on the same external fabric (for example, X1, X2, and X3) in a tri-star topology.

u. Unit of height for a rack; 1.75 inches.

UCME. See uncorrectable memory error (UCME).

UID. A nonnegative integer that uniquely identifies a user within a node.

In the Open System Services (OSS) environment, the UID is the scalar view of the HP NonStop™ operating system user ID. The UID is used in the OSS environment for functions normally associated with a UNIX user ID.

unattended site. A computer environment where no operator resides on site and the only access is from a central monitoring station.

uncorrectable memory error (UCME). An error caused by incorrect data at a particular memory location. The cause of the error is such that the error is not automatically corrected by the system, and memory replacement is required. Contrast with correctable memory error (CME).


Glossary undefined

undefined. Pertaining to the use of an incorrect value for data or the incorrect behavior of a program for which the ISO/IEC IS 9945-1:1990 standard imposes no portability requirements.

undervoltage. A negative change in the amplitude of the voltage.

unicode. A 2-octet (2-byte) character code designed to represent more alphabetic and graphic characters than allowed by the ASCII character set. When the first octet of a unicode character is zero, the second octet maps to the ISO 8859-1 (ASCII) character set. Unicode is the standard character set for encoding characters in implementations of the Java language and is the default character code set used by several Microsoft Windows operating systems.

uninterruptible power supply (UPS). The equipment used to provide an uninterruptible source of power to connected equipment if a main power outage occurs. The basic components of any UPS system are a rectifier/charger that converts alternating-current (AC) power to direct-current (DC) power, batteries that store the DC power, and an inverter that converts the DC power back into AC power for distribution to the load.

unitary segment. See segment.

unmount. To make a fileset inaccessible to the users of a node.

unplanned outage. Time during which a computer system is not capable of doing useful work because of an unplanned interruption. Unplanned interruptions can include failures caused by faulty hardware, operator error, or disaster.

unshielded twisted pair (UTP). A transmission medium consisting of two twisted conductors with no cable shielding. Contrast with shielded twisted pair (STP).

unspecified. Pertaining to the use of a correct value for data or the correct behavior of a program for which the ISO/IEC IS 9945-1:1990 standard imposes no portability requirements.

UPS. See uninterruptible power supply (UPS).

upward compatibility. The ability of a requester to operate with a server of a later revision level. In this case, the requester is upward-compatible with the server, and the server is downward-compatible with the requester. Contrast with downward compatibility.

User Code (UC). See TNS code space.

user code. A logically distinct part of the HP NonStop™ operating system that consists of the code for user processes.

user database. A database within an HP NonStop™ node that contains the user name, user ID, group ID, initial working directory, and initial user program for each user of the node.


Glossary user ID

user ID. The unique identification of a user within a node.

In the Guardian environment, the term user ID usually means the structured view of the HP NonStop™ operating system user ID. In the Open System Services (OSS) environment, the term user ID usually means the scalar view of the HP NonStop™ operating system user ID—a number called the UID.

User Library (UL). See TNS code space.

user library. (1) An object code file that the operating system links to a program file at run time. A program can have only one user library. See also TNS user library and TNS/R native user library. (2) A library loadfile associated with a program so that it emulates the user library feature of the operating system on TNS systems. For position-independent code programs on TNS/R systems, the user library is a dynamic-link library. It is treated as if it were the first library in the program's libList; thus it is searched first for symbols required by the program. However, a user library does not appear in the program's libList; instead, its name is recorded internally in the program's loadfile. A program can be associated with at most one user library; the association can be specified using the linker at link time or in a later change command, or at run time using the process creation interfaces. (The /LIB …/ option to the RUN command in TACL uses these interfaces.)

user name. A string that uniquely identifies a user within the user database for a node.

UTC. See Coordinated Universal Time (UTC).

UTP. See unshielded twisted pair (UTP).

V. See volt (V).

V.35. The International Telecommunications Union, Telecommunication Standardization Sector (ITU-T) standard for data transmission at 48 kilobits/second over 60 - 108 kilohertz group band circuits. It contains the 34-pin V.34 connector specifications normally implemented on a modular RJ-45 connector. V.35 is the equivalent of Electronics Industry Association (EIA) RS-422/RS-449.

V AC. Volts of alternating current.

vertical tetrahedron. A topology of HP NonStop™ S-series servers in which the ServerNet connections between the layers of a cluster switch group form a tetrahedron. See also tetrahedron, tetrahedral topology, and cluster switch layer.

virtual file system. In UNIX and Open System Services (OSS), a file system that allows files of a fileset to be distributed across several physical devices.

volt (V). The standard unit of measure of the potential difference that is required to move an electric charge.


Glossary volume

volume. A logical disk, which can be one or two magnetic disk drives. In HP NonStop™ S-series systems, volumes have names that begin with a dollar sign ($), such as $DATA. See also mirrored disk or volume.

WAN. See wide area network (WAN).

WANBoot process. A process provided as part of the wide area network (WAN) subsystem that implements the BOOTP protocol and provides management functions to the WAN subsystem and the WAN products.

WAN concentrator. See ServerNet wide area network (SWAN) concentrator and ServerNet wide area network (SWAN) 2 concentrator.

WAN shared driver. A driver, provided as part of the wide area network (WAN) subsystem, that provides a simplified interface to HP NonStop™ TCP/IP for use by I/O processes. The shared driver interface is similar to that provided by DOIOPLEASE on earlier systems.

WAN subsystem. See wide area network (WAN) subsystem.

WAN subsystem manager process. A process named $ZZWAN provided as part of the wide area network (WAN) subsystem that starts and manages the WAN subsystem objects, the WAN product process, and device objects. Subsystem Control Facility (SCF) commands are directed to the WAN subsystem manager process for configuring and managing the WAN subsystem and the ServerNet wide area network (SWAN) concentrator.

WAN Wizard Pro. A graphical user interface (GUI) that guides you step-by-step through the configuration of wide area network (WAN) and local area network (LAN) software and hardware.

wide area network (WAN). A network that operates over a larger geographical area than a local area network (LAN); typically, an area with a radius greater than one kilometer. The elements of a WAN can be separated by distances great enough to require telephone communications.

wide area network (WAN) subsystem. The Subsystem Control Facility (SCF) subsystem for configuration and management of WAN objects in G-series release version updates (RVUs).

wild-card character. A character that stands for any possible character or characters in a search string or in a name applying to multiple objects. In Subsystem Control Facility (SCF) object-name templates, two wild-card characters can appear: ? (question mark) for a single character and * (asterisk) for zero or more consecutive characters. See also object-name template.

Windows Internet Name Service (WINS). A name resolution service that resolves Windows NT networking computer names to Internet protocol (IP) addresses in a


Glossary WINS

routed environment. A WINS server handles name registration, queries, and release version updates (RVUs). See also IP address.

WINS. See Windows Internet Name Service (WINS).

word. An instruction-set-defined unit of memory that corresponds to the width of registers and to the most common and efficient size of memory operations. A TNS word is 2 bytes (16 bits) wide, beginning on any 2-byte boundary in memory. A MIPS RISC word is 4 bytes (32 bits) wide, beginning on any 4-byte boundary in memory.

work files. Temporary files created during system generation that serve as storage areas. Work files are useful for debugging purposes after system generation. You can choose to make specified work files permanent.

working directory. In the Open System Services (OSS) environment, a directory, associated with a process, that is used in pathname resolution for relative pathnames.

worldwide name (WWN). A unique, 64-bit number assigned to hardware ports.

WORM. See write once, read many (WORM).

wormhole routing. A technique for reducing network latency in a router. Packet bytes are immediately switched to the appropriate output port as soon as they arrive rather than accumulated in a buffer until an entire packet is received. Contrast with store and forward routing.

write once, read many (WORM). A media storage class in which data, once written, cannot be erased or overwritten.

WWN. See worldwide name (WWN).

WWN zones. Similar to Ethernet virtual LANs (VLANs), WWN zones organize the cabling and interactions between components in a storage and server system.

wye. A polyphase electrical supply where the conductors of the source transformer are connected to the terminals in a physical arrangement that resembles the letter Y. Each point of the Y represents the connection for a conductor at high potential. The angle of phase displacement between each point on the Y is 120 degrees. The center point of the Y is the common return point for the neutral conductor.

wye-delta. The interconnections between a wye source and a delta load.

X.21. A digital signaling interface recommended by the International Telecommunications Union, Telecommunication Standardization Sector (ITU-T) that includes specifications for data terminal equipment/data communications equipment (DTE/DCE) physical interface elements, alignment of call control characters and error checking, elements of the call control phase for circuit switched services, data transfer at or below 9600 bits/second, and test loops.


Glossary X fabric

X fabric. The X side of the internal or external ServerNet fabrics. See also fabric, external ServerNet X or Y fabric, and internal ServerNet X or Y fabric.

XEP table. See external entry-point (XEP) table.

XIO. See extensible input/output (XIO).

XLLink. An Accelerator-related tool invoked by SYSGENR only for TNS/R systems. XLLink binds together separately accelerated modules of TNS library code to make system libraries. XLLink preserves and fixes up the existing Accelerator-generated MIPS RISC code, avoiding the additional time needed for a complete acceleration from TNS instructions. XLLink is not supported for program files, user libraries, or shared run-time libraries.

XO bond. The bond connection on an isolation transformer, installed between the transformer’s neutral XO terminal and ground. This bond is required at North American and British sites to provide an effective return path for any equipment conductor fault current back to the neutral of the isolation transformer.

Y fabric. The Y side of the internal or external ServerNet fabrics. See also fabric, external ServerNet X or Y fabric, and internal ServerNet X or Y fabric.

$YMIOP. The name of the maintenance I/O process that is built during system generation and is available at system startup.

$ZCNF. The name of the configuration utility process.

zero-signal reference. A connecting point, bus, or conductor used as one side of a signal circuit. Such a reference object might or might not necessarily be designated as a ground. Sometimes referred to as a common circuit.

$ZEXP. The name of the Expand manager process.

$ZMnn. The name of the QIO monitor process in processor nn.

$ZNET. The name of the Subsystem Control Point (SCP) management process.

zombie process. In the Open System Services (OSS) environment, a process that has terminated but is still recorded in system tables.

zone. See cluster switch zone and WWN zones.

$ZPM. The name of the persistence manager process.

ZSCL. The subsystem identifier for the ServerNet cluster subsystem.

ZSERVER. The object file name of the $ZSVR server process for the labeled-tape subsystem.


Glossary ZSMN

ZSMN. The subsystem identifier for the external system area network manager process (SANMAN).

$ZSVR. The name of the server process for the labeled-tape subsystem. See also ZSERVER.

ZSYSCONF subvolume. The subvolume on the $SYSTEM disk that contains the system configuration database.

$ZTC0. The default transport-provider process that provides Transmission Control Protocol/Internet Protocol (TCP/IP) services to Open System Services (OSS) AF_INET sockets programs.

$ZZATM. The name of the Asynchronous Transfer Mode (ATM) monitor process.

$ZZFOX. The name of the Fiber Optic Extension (FOX) monitor process in the ServerNet/FX adapter subsystem.

$ZZKRN. The name of the Kernel subsystem manager process.

$ZZLAN. The name of the ServerNet LAN Systems Access (SLSA) subsystem manager process that is started by the $ZZKRN Kernel subsystem manager process and maintained by the $ZPM persistence manager process. See also LAN manager (LANMAN) process.

$ZZPAM. The name of the Port Access Method (PAM) manager process.

$ZZSCL. The name of the ServerNet cluster monitor process (SNETMON).

$ZZSMN. The name of the external system area network manager process (SANMAN).

$ZZSTO. The name of the storage subsystem manager process.

$ZZWAN. The name of the wide area network (WAN) subsystem manager process.


Glossary $ZZWAN


What’s New in This Guide xix

What’s New in This Guide xixManual Information xixNew and Changed Information xx

About This Guide xxiWho Should Use This Guide xxiWhat’s in This Guide xxiWhere to Get More Information xxiiiNotation Conventions xxv

1. IntroductionInstallation Overview 1-3Standard Operating Practices 1-5

Using ESD Protection 1-6Tools 1-7Installation Checklist 1-8Shipping Packages 1-9

About Shipping Packages 1-9Shipping Package Specifications 1-10

Enclosure Types 1-12Enclosure Contents 1-12Enclosure Combinations 1-12Enclosure Positions 1-13Modified I/O Enclosures 1-13IOAM Enclosures 1-13Enclosure Illustrations 1-16

Groundstraps 1-23What Groundstraps Do 1-23Number of Groundstraps 1-23Where to Install Groundstraps 1-23More About Groundstraps and Power Requirements 1-23

Power-On Cables 1-24Emergency Power-Off Cables 1-25

About EPO Cables 1-25EPO Cable Requirements 1-25

System Organization 1-26Group, Module, and Slot Hierarchy for System Enclosures 1-26Group, Module, and Slot Hierarchy for IOAM Enclosures 1-28Server Numbering and Labeling 1-31

ServerNet Cabling 1-36

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-0011

2. Installing Enclosures

System Size 1-36Topologies 1-37Fabrics and Slots 1-37IOAM Enclosure Cabling 1-38ServerNet Cables 1-38

The System Console 1-45System Consoles 1-45The OSM Product 1-45The TSM Package 1-46Primary and Backup System Consoles 1-47Modems 1-48Preloaded Hardware and Software 1-49Software Connections 1-53

System Startup 1-54Startup and Shutdown Files 1-54System Load Paths 1-54PMF CRU and IOMF CRU Power-On Self-Tests 1-56

2. Installing EnclosuresPrepare to Install New Equipment 2-2

1. Review the Documentation 2-22. Prepare the Work Space 2-33. Organize the Equipment 2-4

Unpack the Enclosures 2-6Tools 2-6Unpack the Enclosures 2-6

Connect the Groundstraps 2-13Inventory the Enclosures 2-16

Slot Assignments for NonStop S-Series Enclosures 2-16Inspect the Components 2-23

3. Cabling Enclosures1. Connect Power-On Cables 3-12. Connect EPO Cables 3-33. Connect ServerNet Cables 3-4

4. Installing Service-Side Doors

5. Installing, Starting, and Testing a System ConsoleUnpacking and Assembling a System Console 5-2


6. Connecting a System Console

Installation Quick Reference 5-2Finding Documentation 5-2Finding the Quick Setup Reference Card 5-2Unpacking the System Console 5-2Assembling the System Console 5-6

Starting and Testing a System Console 5-8Powering On a System Console 5-8Verifying Readiness 5-9Final Setup Steps 5-9Operational Considerations for OSM and TSM 5-10Connecting Multiple System Consoles 5-11System Console Function Keys 5-12

6. Connecting a System ConsoleThe Dedicated LAN 6-2

Server Connection to a LAN 6-2System Console Connection to a Dedicated Service LAN 6-3System Console Connection to a Secure Operations LAN 6-3Ethernet Cables 6-4Ethernet Switch Ports 6-4

Installing Ferrite Cores 6-4Installing the Ethernet Switch or Hub 6-5

Connect the Ethernet Switch or Hub to the Server 6-5Connect the System Console to the Ethernet Switch or Hub 6-6

7. Installing External System DevicesInstalling Tape Drives 7-1

Installing a 5175 Open-Reel Tape Subsystem 7-2Installing a 519x Cartridge Tape Subsystem 7-9Installing Other Tape Devices 7-12Attaching a Tape Drive to the NonStop S-Series Server 7-14

Installing a SWAN or SWAN 2 Concentrator 7-15Installing an AWAN Server 7-15Installing Printers and Terminals 7-16

8. Powering On and Starting the SystemStarting a System for the First Time 8-2

Startup Checklist 8-2Powering On External System Devices 8-3

Powering On the Primary System Console and Modem 8-3


9. Performing Post-Startup Tasks

Powering On the Tape Subsystem 8-3Powering On the System 8-6

Fault Tolerance and Access to Power Cutoffs 8-6Power-On Procedure Using AC Power Cords 8-6Status LEDs During a Power-On Procedure 8-10Troubleshooting Abnormal LED States 8-12

Verifying Topology and System Components 8-14Starting the System 8-17

Loading the System 8-17Completing the System Load 8-20Verifying the System Is Started 8-20

9. Performing Post-Startup TasksTesting the System 9-1

Check Power Supplies 9-2Check System Enclosure Components 9-2Check Critical System Processes 9-6Check Disk Subsystem Status 9-7Test the Disk Drives 9-8Test the Communications Lines 9-10Check Tape Subsystem Status 9-10Test the Tape Subsystems 9-11

Completing Final Installation Steps 9-12System Configuration Changes and Verifications 9-13Restarting the Inspect Monitor Process 9-14

Preparing for Daily Operations 9-15Reference Manuals 9-15

Configuring the OSM or TSM Environment 9-16Configuring the OSM Environment 9-16Configuring the TSM Environment 9-16

10. Configuring the SystemSetup Configuration 10-2

Procedure to Create the Setup Configuration 10-2Operating Configuration 10-3

Create the Operating Configuration 10-4Add a System Console to the Operating Configuration 10-7Add a Server to the Operating Configuration 10-9Create a Cascading Ethernet Switch Configuration 10-11Add a System Console to the Cascading Ethernet Switches 10-13


11. Offline Configuration Tasks

Add a Server to the Cascading Ethernet Switches 10-13Unattended Site Configuration 10-14

Create the Unattended Site Configuration 10-15Add a Server to an Unattended Site Configuration 10-15

Nondedicated (Public) LAN Configuration 10-16Construct a Nondedicated (Public) LAN Configuration 10-16

11. Offline Configuration TasksChanges That Must Be Made Offline 11-1Application Reconfiguration 11-2Installing a New RVU 11-2Installing a Product Revision 11-2Changing System Name, System Number, or Time Attributes 11-3Changing the System Topology 11-3Changing the CONFTEXT File 11-3

12. Online Configuration TasksSCF 12-2

Initial CONFIG file 12-2Subsystems in G-Series RVUs 12-3Generic Processes 12-4Making Important Processes Persistent 12-5Types of System Configuration Files 12-6

KMSF 12-8Initial Configuration of KMSF Swap Files 12-8Changing the Configuration of KMSF Swap Files 12-8KMSF and the Operations Environment 12-8

The OSM and TSM Packages 12-9Creating an Alternate System Disk 12-10

1. Choose the Target Disk and Plan Its Space and Files 12-112. Verify That the Target Disk Is Present 12-123. Stop Access to the Target Disk and Display Its Status 12-124. Change the Label of the Target Disk 12-135. Create a New System Volume and a System Image Tape (SIT) 12-146. Install the Boot Millicode on the Target Disk 12-147. Verify the Installation of Boot Millicode on the Target Disk 12-158. Copy Subvolumes to the Target Disk 12-16

Create a Command File 12-17

13. Creating Startup and Shutdown Files


13. Creating Startup and Shutdown Files

Automating System Startup and Shutdown 13-2Startup 13-2Shutdown 13-2For More Information 13-2

Processes That Represent the System Console 13-3$YMIOP.#CLCI 13-3$YMIOP.#CNSL 13-3$ZHOME 13-3$ZHOME Alternative 13-4

Example Command Files 13-5CIIN File 13-6

Establishing a CIIN File 13-6Modifying a CIIN File 13-7If a CIIN File Is Not Specified or Enabled in OSM or TSM 13-7Example CIIN Files 13-8

Tips for Startup Files 13-9How Process Persistence Affects Configuration and Startup 13-9Startup File Examples 13-10

System Startup File 13-10Spooler Warm-Start File 13-12TMF Warm-Start File 13-12TCP/IP Stack Configuration and Startup File 13-12CP6100 Lines Startup File 13-15ATP6100 Lines Startup File 13-15X.25 Lines Startup File 13-15Printer Line Startup File 13-16Expand-Over-IP Line Startup File 13-16Expand Direct-Connect Line Startup File 13-16

Tips for Shutdown Files 13-17Shutdown File Examples 13-17

System Shutdown File 13-18CP6100 Lines Shutdown File 13-19ATP6100 Lines Shutdown File 13-19X.25 Lines Shutdown File 13-19Printer Line Shutdown File 13-20Expand-Over-IP Line Shutdown File 13-20Direct-Connect Line Shutdown File 13-20Spooler Shutdown File 13-21TMF Shutdown File 13-21


14. Case Study: Installing and Configuring aSystem


14. Case Study: Installing and Configuring a SystemAbout These Examples 14-2Background for Developers Inc. 14-3Hardware Configuration 14-4Installation Documents 14-4

Case Study: Installation Document Checklist 14-5Case Study: System Equipment Inventory Form 14-6Case Study: Enclosure Arrangement Diagram 14-7Case Study: Floor Plan 14-8Case Study: Preinstalled I/O Device Cable Checklist 14-9Case Study: Group 01 System Enclosure Checklist 14-10Case Study: Group 01 Slot 50 PMF CRU Configuration Form 14-11Case Study: Group 01 Slot 55 PMF CRU Configuration Form 14-12Case Study: Group 01 Slot 53 E4SA Configuration Form 14-13Case Study: Group 01 Slot 54 E4SA Configuration Form 14-14Case Study: Group 02 System Enclosure Checklist 14-15Case Study: Group 02 Slot 50 PMF CRU Configuration Form 14-16Case Study: Group 02 Slot 55 PMF CRU Configuration Form 14-17Case Study: Group 02 Slot 53 E4SA Configuration Form 14-18Case Study: Group 02 Slot 54 E4SA Configuration Form 14-19

System Configuration: CONFTEXT File 14-20LAN Environment at Developers Inc. 14-20

Registry of IP Addresses 14-20Installing the System 14-22Customizing the Configuration 14-22

Adding Ethernet 4 ServerNet Adapters (E4SAs) 14-23Adding ConMgr Process 14-24Configuring NonStop TCP/IP Stacks on E4SA Ports 14-25Adding Persistent CLCI TACL, Expand Manager, and SCP Processes 14-27Starting the $ZEXP Expand Manager Process 14-27Adding a SWAN Concentrator 14-28Adding a SWAN 2 Concentrator 14-28Adding CP6100 Lines 14-29Adding an ATP6100 Line 14-30Adding a 5516 Printer 14-31Adding an X.25 Line 14-32Configuring and Starting the $NCP Network Control Process 14-33


A. Part Numbers

Adding an Expand-Over-IP Line 14-33Adding a Direct-Connect Line 14-34

A. Part Numbers

B. ServerNet Cabling What ServerNet Cabling Diagrams Mean B-2Maximum ServerNet Configurations B-4Maximum ServerNet Cabling Tables B-7

Shaded Areas in These Tables B-7Tetra 8 Cabling Tables B-8Tetra 16 Cabling Tables B-10

Small Tetra 8 Systems B-14About This Information B-14Tetra 8 Systems With One Processor Enclosure B-15Tetra 8 Systems With Two Processor Enclosures B-16Tetra 8 Systems With Three Processor Enclosures B-17Tetra 8 Systems With Four Processor Enclosures B-21

Small Tetra 16 Systems B-25About This Information B-25Tetra 16 Systems With Four Processor Enclosures B-26Tetra 16 Systems With Six Processor Enclosures B-28

C. Power-On Cabling

D. TroubleshootingReference D-2

Power States D-2Status LEDs D-4

Powering On the System D-5System Does Not Appear to Be Powered On D-6Power Is Applied to Enclosure But Fans Are Not Turning D-6Any Green LED Is Not Lit D-8Any Amber LED Remains Lit After POST D-9Yellow ServerNet Port LEDs on SEBs or MSEBs Are Not Lit D-9Group Service LED on System Enclosure Is Flashing D-9Correcting Topology Attribute D-9

Starting the System D-10Startup Event Stream and Startup TACL Windows Do Not Appear D-10System Load Fails D-11


E. FastPath Tasks: Required

CIIN File Is Not Invoked During System Startup D-12Reload Fails D-13CPU Memory Test Fails D-14System Load Path Test Fails D-14Multifunction I/O Board (MFIOB) Test Fails D-15

Dumping Processor Memory D-16Dumping Processor Memory to Disk Online D-16Dumping Processor Memory to Tape Offline D-20

Expand-Over-IP Connections D-22Recovery Actions for the CONNECTING State D-24Recovery Actions for the WAIT State D-24

Backing Out a Software Revision D-26Prerequisites D-261. Start DSM/SCM D-262. Start and Log On to Target Interface D-273. Initiate Backout Activity D-274. Monitor Backout Process D-285. Stop All Applications D-286. Rename Software Files Using ZPHIRNM D-297. Stop System D-298. Load System From Saved Configuration D-309. Start Applications D-30

System Consoles D-31Software Configuration Problems D-36Software Corruption and Hard-Disk Problems D-37Restoring Software on the Hard Disk D-38 Configuring a ProCurve 24-Port Ethernet Switch D-48

E. FastPath Tasks: Required1. Install Hardware E-3

1. Inventory Shipment E-42. Collect Tools E-63. Unpack and Unload Server E-64. Connect Groundstraps E-105. Inventory and Inspect All Components E-116. Connect the Power-On Cables E-117. Connect Emergency Power-Off (EPO) Cables E-138. Connect ServerNet Cables E-149. Install Service-Side Enclosure Doors If Necessary E-15


F. FastPath Tasks: Optional

10. Install Primary System Console E-1611. Create Emergency Repair Disk or Automated System Recovery Disk E-1812. Install Ethernet Switch E-1813. Connect Ethernet Switch to Group 01 E-1814. Connect Primary System Console to Ethernet Switch E-1915. Install Tape Drive E-19

2. Start the System E-221. Prepare for System Startup E-222. Power On External System Devices E-233. Connect AC Power Cords E-244. Apply Power to Server E-265. Verify Topology E-276. Verify System Components E-287. Start System E-28

3. Verify the System E-301. Verify Components E-302. Verify Critical System Processes E-313. Verify Disk Drives E-314. Verify Tape Drive E-325. Verify Firmware E-326. Verify State of the Internal ServerNet Fabric E-32

4. Configure the System E-331. Configure Passwords E-342. Configure Kernel-Managed Swap Files E-353. Configure OSM or TSM Environment E-364. Configure System Attributes E-375. Configure DSM/SCM E-41


F. FastPath Tasks: Optional1. Prerequisites F-2

1a. Verify Required Configuration Changes F-21b. Review Initial System Configuration F-21c. Start Required Processes F-21d. Save Current System Configuration F-31e. If Your Server Will Be Part of a ServerNet Cluster F-3

2. Customize the System Configuration F-42a. Change SCF F-42b. Rename SCF Objects in the CONFIG File F-5



2c. Add SCF Objects to the CONFIG File F-63. Automate System Startup F-7

Modify Provided Startup Files F-7Create Startup Files F-7

4. Automate System Shutdown F-8Tips for Shutdown Files F-8

5. Configure a SWAN or SWAN 2 Concentrator F-9Access the WAN Wizard Pro F-9

6. Configure an Expand-Over-IP Line F-10Prerequisites F-111. On the NonStop S-Series Server F-122. On the NonStop K-Series Server F-163. On the NonStop S-Series Server F-184. On the NonStop K-Series Server F-195. On Either NonStop Server F-21

7. Install Software F-22Configuring Software With DSM/SCM F-23Installing a Software Product Revision (SPR) F-25


Glossary

Index


Index


IndexNumbers3883/4/5 AWAN server

See AWAN3886-8/16/32 AWAN server

See AWAN517x tape subsystem

see Tape subsystem, 517x519x tape subsystem

see Tape subsystem, 519x

AAC power cord

compatibility 2-3, 8-2connecting 7-7, 8-7, 8-8, E-24/E-25illustration 8-6, 8-7, E-5open first box 2-5power-on 8-6/8-10quantity 2-5, E-5tape subsystem 8-4, 8-5, E-20, E-23tools 1-7, E-6troubleshooting D-6

Accessories box 5-3, 5-4, E-16Alternate system disk

boot millicode 12-14changing target disk label 12-13copying subvolumes 12-16creating 12-10/12-16planning 12-11stopping access 12-12system image tape 12-14system volume 12-14target disk 12-11verifying 12-12

Application fails when started D-37Applications, reconfiguring 11-2ASSIGN F-6

Asynchronous wide area network (AWAN)See AWAN

ATM subsystem 12-4ATP6100 7-16, 13-19, 14-30Automating

system shutdown 13-2, F-8system startup 13-2, F-7

AWAN 7-15/7-17

BBACKUP and RESTORE 9-11Backup system console

installing E-45/E-46IP address E-19settings E-36

BAD attribute, SCF INFO DISK 9-10Binder E-17Bus dumps

See Processor dumps

CCable

AC powersee AC power cord

channels 1-43compatibilities 1-38/1-39connections, MSEB 1-39ECL

see ECL cableEPO

see EPO cablesfiber-optic

see SMF cable, MMF cableguideposts 1-43labels 1-42management 1-44, 3-5routing 1-43

HP NonStop S-Series Hardware Installation and FastPath Guide—529876-001Index-1

Index C

SCSIsee SCSI cable

securing 1-43, 3-5ServerNet

see ServerNet cablesupports 1-43, 3-5tie anchors 1-44, 3-5ties 2-5, 3-5, E-5

CablingTetra 16 B-5/B-6, B-10/B-13, B-25/B-29Tetra 8 B-4, B-8/B-9, B-21/B-23

Carbon Copy softwaredial-ins 1-49installing D-46preloaded 1-50

Cartridge tapeSee Tape subsystem

Cascade port 6-4, 6-6, 10-5, 10-6Cascading Ethernet switch configuration 10-11/10-13Case study

ATP6100 lines 14-30direct-connect line 14-34Expand-over-IP 14-33hardware 14-4installation documents 14-4/14-19TCP/IP stacks 14-26X.25 lines 14-32$NCP network control 14-33$ZEXP Expand manager 14-27

Certificate of Authenticity 5-3CIIN file 8-18

automatic 1-55contents 13-6disabled 8-18establishing 13-6file name 13-6initial location of 13-2modifying 13-7ownership 13-6

CIIN file (continued) 8-18processor load 1-55, 8-17RELOAD 13-7security 13-6, 13-8specifying 13-6system behavior when absent 13-7

CLCI sessions 8-19CNSL 8-19, 9-14Command files

creating 12-17examples 13-5/13-21, 14-23/14-34preparation 12-17

CommandsCONTROL DISK, SPARE 9-10COPYDUMP D-19example file 12-5INFO D-18, D-22, D-24INFO DISK 12-17INFO, LABEL 12-15LISTDEV 9-6LOG 12-17PRIMARY DISK 9-9, 9-10RCVDUMP D-18RECEIVEDUMP D-17, D-18RELOAD 8-20, 13-7, D-12, D-13, D-19RUN ZPHIRNM D-29SAVE 12-2START 12-2STATS D-22, D-24STATUS 12-12, D-24STATUS DISK 9-7, 9-8, 9-9STATUS LINE D-22STATUS TAPE 9-10, 9-11STOP 12-12SWITCH 9-8, 9-10

Communications lines, testing 9-10Compressed dump file message D-19CONF0000 file 12-2, 12-6CONFBASE file 12-6


Index D

CONFIG file 8-18, 9-14customizing F-4function 12-3initial 12-2types of 12-6$ZPM E-44

Configurationcascading 10-11/10-13database 12-2, 12-3, 12-6Ethernet switch 10-11/10-13files

ATP6100 14-30CONF0000 12-6CONFBASE 12-6CONFIG

See CONFIG fileCONFSAVE 12-2, 12-6CONFTEXT 2-4

See CONFTEXT fileCONFxxyy 12-6ConMgr 14-24CP6100 14-29direct-connect 14-34E4SA 14-23Expand-over-IP 14-33INITIAL_COMMAND_FILE 13-6SCF 2-4, 7-14SWAN concentrator 14-28TCP/IP stacks 13-13, 14-25types 12-6WANBoot 14-24X.25 14-32$NCP network control 14-33

nondedicated (public) LAN 10-16/10-19operating 10-3/10-13setup 10-2

toolsKMSF 12-8OSM 12-9SCF 12-2/12-7TSM 12-9

unattended site 10-14/10-15utility process ($ZCNF) 12-3

Configuring disk paths 12-17CONFSAVE file 12-2, 12-6CONFTEXT file

changing 11-3example 14-20INITIAL_COMINT_INFILE 13-6INITIAL_COMMAND_FILE 13-6location of 14-20printout 2-4

ConMgr process 14-24Connectivity problems D-32/D-35Console

See System consoleCONTROL DISK 9-10Cores, ferrite 6-4Corruption, software D-37CP6100 lines configuration file 14-29CPU dump message D-18CPU memory test 1-56, D-14CSSI Web -xxiii

DDatabase, configuration 12-2, 12-3, 12-6DC power cords E-25Dedicated LAN 6-2, 10-1Dial-ins 1-49Dial-outs 1-48Direct-connect line

configuration file 14-34shutdown file 13-20startup file 13-16, 14-34


Index E

Disk drivesLEDs D-4replacing 9-10testing 9-8/9-10

Display monitorSee Monitor

Distributed Systems Management/Software Configuration Manager (DSM/SCM)

See DSM/SCMDocumentation -xxiiiDSM/SCM 1-50, D-45

EE4SA

See also ServerNet adapterscase study 14-4configuration file 14-23configuration form 14-13, 14-14, 14-18, 14-19configurations using 10-1/10-19LAN connection 10-16LEDs 8-11

ECL cable 1-20, 1-38, 1-40, 1-41Electrostatic discharge (ESD) 1-5/1-6Emergency power-off (EPO) cables

See EPO cablesEmergency repair disk (ERD)

See ERDEMS event message D-11, D-13, F-29emulate Glossary-31Enclosure

See also I/O enclosureSee also Processor enclosureSee also IOAM enclosureappearance side 1-26base 1-13, 1-16, 1-23, 1-43, 2-10, 2-12, 2-13, E-8, E-9block 1-12cables shipped 2-5casters 2-10

contents 1-12described 1-12electrical connections 2-3EPO 2-3ESD safety 1-5groundstraps

see Groundstrapsgroup ID switches 1-33group numbers 1-31height 2-4illustration 2-14, 2-15

appearance side 2-17base 1-16group ID switches 1-33group, module, slot for system enclosure 1-27labels 1-34service side 2-18/2-20stackable 1-16

inventory 2-16/2-22IOAM 1-13LEDs D-6modified I/O 1-13moving 2-10, E-8opening 2-22pedestal 2-10postitions 1-13processor numbers 1-31service side 1-26slot assignments 2-16, 2-17stack 1-13, 2-10tools 1-7, 2-6types 1-12/1-13unlocking 2-22unpacking 2-6/2-12weight 1-10

Enterprise Storage System (ESS)See ESS


Index F

EPO cablesconnecting 1-25illustrated E-5installing 2-4part number 1-25quantity 2-5

ERD 5-10, D-47/D-48ESD 1-5/1-6ESS 1-13Ethernet 4 ServerNet adapter (E4SA)

See E4SAEthernet cables

accessory box 5-3, E-16quantity 5-3switch to server 6-5/6-6

Ethernet ports 6-2/6-4, 10-17Ethernet switch

See also MDI switchcascading configuration 10-11/10-13dedicated LAN 6-2installing 5-8ports 6-4powering on 5-8server 6-5shipping box 5-3switch 2 10-5system console 6-6unpacking 5-5

Event messageSee EMS event message D-13

Expand manager ($ZEXP) 12-4, 14-27Expand-over-IP

configuration file 14-33probe message D-23startup file 13-16, 14-33TCP/IP F-13

External device 8-2, 8-3, 8-5

FFan (IOAM) LEDs D-4Fast Ethernet Servernet Adapter (FESA)

See FESAFCSA

description 1-13LEDs D-4

Ferrite cores 6-4FESA 10-1/10-19Fiber-optic cable

see also SMF cable, MMF cableabout 1-41compatibilities 1-38compatibility 1-39distance 1-41illustrated 1-41illustration 1-41IOMF 2 CRU 1-20, 1-39LC-SC connectors 1-41MMF 1-41MSEB 1-39port numbers 1-39recommended 1-41SMF 1-41

Fibre channel ServerNet Adapter (FCSA)See FCSA

Firmwareintelligent SCSI processor D-14ISP D-14requirements 7-2, 7-9RVUs, backing out D-26RVUs, new 11-2SP 9-13tape subsystem 7-2, 7-9updating 9-13, 12-9

Function keys, system console 5-12


Index G

GG4SA

description 1-14LEDs D-4

Gateway, default IP address for 1-52Generic processes 12-4GESA 10-16Getting Started document 2-5Gigabit Ethernet 4-port ServerNet Adapter (G4SA)

See G4SAGroundstraps

about 1-23connecting 1-8, 2-13/2-15, B-14, B-25, E-10illustration 2-13, 2-14open first box 2-5, E-4, E-5quantity 2-5tools 1-7, E-6

Group ID 1-33, 1-34Groups 1-34

IOAM enclosure 1-28numbering and labeling 1-31system enclosures 1-26

Guided replacement procedures xxivGuided Replacement Toolkit xxiiiG-series, systems running 12-3

HHalt code message D-11, D-13Hexagonal wrench E-11Home terminal, using $ZHOME 13-3Hometerm

See VHSHP Tandem Advanced Command Language (TACL)

See TACL

IIdentification labels 1-34INFO D-18INITIAL_COMINT_INFILE 13-6INITIAL_COMMAND_FILE 13-6Inspect Monitor Process ($IMON)

see $IMONInstallation

checklist 1-8, 1-42, 2-2overview 1-3/1-4preparing for 2-2/2-6, E-5tools E-6

Internet Explorer 1-50, D-46IOAM enclosure

components 1-13contents 1-12description 1-12, 1-13group, module, slot 1-28LCD 1-35LEDs D-4maintenance switch 1-14numbering 1-31ServerNet switch board 1-13

IOMF CRUEthernet ports 6-2LEDs 8-10, D-4power-on self-test (POST) 1-56/D-15reseating 2-24troubleshooting 8-13

IP addressassigning 10-8, 10-10changing 1-52, 9-16, 10-4, 10-9configuring 10-18default 1-51, 9-16, 10-4, 10-7, 10-9examples 14-20, 14-21MSP 1-52, 10-9NonStop operating system 1-52operating configuration 10-4, 10-9setup configuration 10-2


Index K

IP address (continued)system console 10-4viewing 10-9

I/O Adapter Module (IOAM) enclosureSee IOAM enclosure

I/O enclosureSee also Enclosurescontents 1-12description 1-12group numbers 1-31illustration 2-17, 2-20maximum quantity 1-36modified 1-13slot assignments 2-16, 2-17

I/O multifunction (IOMF) CRUSee IOMF CRU

KKernel subsystem 12-4Kernel-Managed Swap Facility (KMSF)

See KMSFKeyboard 5-3, 5-4, D-32KMSF 9-13, 12-8

LLabels, identification 1-34LAN 6-1, 7-16, 10-1LCD, IOAM enclosure 1-35LC-SC connectors, for fiber-optic cables 1-41LEDs

activity 8-11amber 8-10, 8-12, 8-13, D-15disk drive 8-11, D-4enclosure 8-11fan (IOAM) D-4fault 8-11FCSA D-4functions 8-10

LEDs (continued)green 1-56, 8-9, 8-10, D-14group service 8-11, 8-12, D-9IOMF CRU 8-10, 8-13, D-4, D-15monitor screen 5-10MSEB 8-11, 8-13, D-5PMF CRU 1-56, 8-10, 8-12, D-5, D-14, D-15power supply (IOAM) D-4power-on 1-56, 8-9, 8-10, D-14SEB 8-11, 8-13, D-5ServerNet adapter 8-11, 8-14ServerNet port 8-13ServerNet port service 8-10ServerNet switch board (IOAM) D-4service 8-10, 8-12, 8-13, D-15status 8-9, 8-10, D-4system enclosure 8-12tape subsystem 9-11troubleshooting 8-12/8-13, D-6/D-9, E-26, E-27yellow 5-10, 8-13

Leveling pads 2-10, 2-12, E-9Light-emitting diodes (LEDs)

See LEDsLoad path, operating system 1-54Loading the system 8-17Local area network (LAN)

See LANLog file message D-29, F-29

MMaintenance switch, IOAM enclosure 1-14Maintenance, remote 12-9Manuals

See DocumentationMaster service processors (MSPs)

See MSPsMDI switch 10-6, 10-12


Index N

Medium-dependent interface (MDI) switchSee MDI switch

Memory 1-56, 12-8, D-14Messages

ASSIGN F-6compressed dump file D-19CPU dump D-18EMS event D-11, D-13, F-29Expand-over-IP probe D-23generic process configuration F-6halt code D-11, D-13log file D-29, F-29PARAM F-6processor reload E-29RCVDUMP D-16, D-17, D-18system configuration F-25system load E-29TCP/IP E-46

MFIOB test 1-56, D-15MMF cable 1-41

See also Fiber-optic cableModem 5-3/5-8Modular cabinet 1-13Modular ServerNet expansion board (MSEB)

See MSEBModule, IOAM enclosure 1-28Monitor 5-3, 5-4, 5-8, D-34, D-36Monitoring system load E-29Mouse 5-4Moving enclosures E-8MSEB

cable adapter 1-40cables 1-40/1-41fiber-optic connection 1-41illustration 1-39LEDs 8-11, 8-13, D-5reseating 2-25slot numbers 2-16/2-17troubleshooting 8-13

MSPsconnection to system console 1-53default IP addresses 1-52, 10-9LAN connection 10-2quantity supported 1-53SP Tool Application 8-17TSM tests 9-16

Multifunction I/O board test 1-56, D-15Multimode fiber (MMF) cable

See MMF cableMultiple-row systems 2-14

NName and number, system E-38Network control process ($NCP)

See $NCPNetwork interface card (NIC)

See NICNIC 6-3, 6-6, 10-6, 10-8, 10-18NNA PICs 1-41NonStop Virtual Hometerm Subsystem (VHS) 13-4

OOffline configuration changes 11-1/11-3Online configuration changes 12-1/12-18OPEN FIRST box 2-4, E-4Open System Services (OSS) E-38Open-reel tape

See Tape subsystemOperating configuration

See Recommended operating configuration

Operating practices 1-5OSIMAGE file on D-series RVUs 12-6


Index P

OSMabout 1-47, 9-16, 12-9CIIN file 13-7configuring 9-16connections D-47firmware 12-9guided replacement procedures xxiiihelp 9-11IP addresses 10-18Low-Level Link 1-53, 8-15, 10-9, D-47Notification Director 9-16security 13-8Service Connection 9-2, 9-11, 10-16, D-47

OSS E-38Outages 5-7, 11-1, 11-2OutsideView terminal emulator software

function keys 1-50installing D-46preloaded 1-50startup windows on 8-19

PPacking materials 5-2Pallet, shipping 1-9PAM subsystem 12-4Parallel Library TCP/IP F-13PARAM F-6Part numbers A-1PC accessory shipping box 5-3, 5-4Persistence manager process ($ZPM) 12-3PMF CRU

configuration form 14-11, 14-12, 14-16, 14-17Ethernet ports 6-2LEDs 8-10, D-5reseating 2-24troubleshooting 8-12

Port Access Method (PAM) 12-4

Ports, EthernetSee Ethernet ports

POSTsSee Power-on self-tests (POSTs)

Power cordsSee AC power cords

Power scrub action, redundant 9-2Power supply

LED D-4verification 9-2

Powering on5175 tape subsystem 8-4519x tape subsystem 8-5external system devices 8-3modem 5-8sequence 8-8system 8-10/8-11, E-22/E-29

Power-on self-tests (POSTs)about 1-56, D-15LEDs 8-10system power-on 8-9

Power-on cableabout 1-24connecting 3-1/3-2illustration 1-24, 2-5, E-5

Primary system console E-16about 1-3, 1-47, 10-4configuring E-36installing E-16, E-19IP addresses 1-51LAN connections 6-2operating configuration 10-9powering on 5-8system startup 8-2

Printers, installing 7-16Private LAN

See Dedicated LANProcessor dumps D-16


Index Q

Processor enclosurecombined with I/O enclosures 1-36contents 1-12description 1-12group numbers 1-31illustration 2-17, 2-18, 2-19processor numbers 1-31S700 1-36, 2-16S7000 1-36, 2-17, 2-18S7x00, Sxx000 1-36, 2-17, 2-19slot assignments 2-16, 2-17

Processor multifunction (PMF) CRUSee PMF CRU

Processors 8-20, 13-7, E-29Public LAN 10-16

QQIO subsystem 12-4Quick setup reference card 5-2, 6-3, 6-6

RRack 1-13Ramp, for unloading enclosure 1-9RCVDUMP D-16, D-17, D-18RECEIVEDUMP D-18Recommended operating configuration

adding server 10-9adding workstation 10-7creating 10-3/10-6

Redundant power scrub action 9-2Reel tape

See Tape subsystemRELOAD 8-20Remote access 12-9Remote monitoring 12-9, D-47Reseating components 2-23/2-26RJ-45 connectors 6-3Routers 6-2

RVUcreate software revision F-23installing 11-2SYSINFO F-26Visual Inspect E-44$ZPM E-44

SSafety glasses 2-6SCF

about 12-2command file 12-17configuration components 12-3configuration file 2-4, 7-13configuration tools 12-2/12-7CONTROL DISK 9-10G-series 12-3INFO DISK 9-10modifying system attributes 11-3PRIMARY DISK 9-10SCF0000 command file D-12STATUS 9-9STATUS DISK 9-10SWITCH 9-8, 9-10testing the tape subsystem 9-11

SCF0000 command file 12-6Screen

See MonitorSCSI cables 7-7, 7-10SEBs

cables 1-40, E-14cabling 1-18fabrics 1-37LEDs 8-11, 8-13, D-5reseating 2-25slot numbers 2-16/2-17startup 8-10troubleshooting 8-13

Security 1-49, 9-16


Index S

Serial-connected printers 7-16Serial-copper cable 1-38/1-41ServeNet switch board

IOAM component 1-13ServerNet adapters

command file 12-17LEDs 8-11, 8-13power-on self-test (POST) 8-11reseating 2-26slot numbers 1-38, 2-16, 2-17/2-21startup 8-11subsystem 12-4troubleshooting 8-13

ServerNet cablecompatibilities 1-38defined 1-38diagrams B-14/B-23ECL

See ECL cablefiber-optic

See Fiber-optic cableillustrated 1-40/1-41labels 1-42quantity 2-5routing 1-43securing 3-5serial-copper

see Serial-copper cableServerNet Cluster Switch, NNA 1-41ServerNet device adapter (ServerNet/DA)

See ServerNet adaptersServerNet expansion board (SEB)

See SEBsServerNet LAN Systems Access (SLSA) subsystem 7-15, 12-4ServerNet switch board (IOAM)

description 1-13LCD 1-35LEDs D-4

ServerNet Wide Area Network 2 (SWAN 2) concentrator

See SWAN concentratorServerNet wide area network (SWAN) concentrator

See SWAN concentratorServerNet/DA

See ServerNet adaptersServerNet/FX adapter

See ServerNet adaptersService connection 1-53Setup configuration

adding fault tolerance to 5-11connecting 6-1/6-6tasks 10-2

Shipping-carton contents 2-4, 5-3Shutdown files

about 13-17/13-21ATP6100 lines 13-19automating 1-54, 13-2CP6100 lines 13-19Expand-over-IP lines 13-20security 13-17sequence 13-2, 13-17spooler 13-21system shutdown file 13-18TMF 13-21X.25 lines 13-19

Single-mode fiber (SMF) cableSee SMF cablesee SMF cable

SIT 2-4, 2-5, 12-14Site update tape (SUT) 2-4, 2-5

see SUTSlot

assignments 2-17/2-19definition for system enclosure 1-26IOAM enclosure 1-28labels 1-34

SLSA subsystem 7-16, 12-4


Index S

SMF cable 1-41Software

approved 1-49backing out D-26/D-30configuration D-36connections 1-53installing 1-45K-series F-11managing E-42OSM

see OSMpreloaded 1-49restoring D-38troubleshooting D-36TSM

see TSMSoftware product revisions (SPRs)

description 11-2installing 11-2, F-23, F-25/F-29

SPARE attribute 9-10Spooler 13-12, 13-21Spooler FASTPxxx 7-16Stackable enclosures 1-13Standard configurations 1-38Standard operating practices 1-5STARTCOM file F-7STARTSCF file F-7Startup files

about 13-6/13-16ATP6100 lines 13-15, 14-29automating 1-54, 13-2, F-7CIIN 13-2configuration database 13-10CP6100 13-15, 14-29direct-connect 13-16direct-connect lines 14-34Expand-over-IP 13-16, 14-33invoking 13-2security 13-9, F-7sequence 13-9, F-7

Startup files (continued)spooler warm start 13-12system startup file 13-10TCP/IP stacks 13-9TMF warm start 13-12X.25 lines 13-15$NCP network control process 14-33$ZEXP Expand manager 14-27

Status LEDSSee LEDs

Storage subsystem 12-4Subnet, default IP address for 1-52Subsystem Control Facility (SCF)

See SCFSubsystem managers 12-4Surge suppression 5-7SUT 1-50, 2-4, 2-5, D-45SWAN concentrator 13-12, 14-28, F-9Swap files 12-8Switch

See Ethernet SwitchSWITCH command, SCF 9-9, 9-10System configuration message F-25System console

assembling 5-6/5-7backup 10-4binder E-17connecting a modem 5-7connecting components 5-6connecting to Ethernet switch 6-6connecting to system 6-1defined 1-47documentation 5-2, 5-6, 6-6function keys 5-12installer CD D-38, D-46IP address for 1-51modem requirement 1-48PC accessory box E-16power source 5-6powering on 5-8, 8-3


Index T

preloaded hardware and software 1-49primary E-16primary and backup 1-47, 1-51shipping box 5-3software connections 1-53TACL window 13-6testing 5-9unpacking 5-4use 5-10

System disk recovery D-11System disk, alternate

See Alternate system diskSystem enclosure

See EnclosureSystem Enclosure Arrangement Form 1-42System Equipment Inventory Form 14-6System Image Tape(SIT)

see SITSystem load 1-54, 1-56, 8-17, D-14, E-29System name 11-3, E-38System number 11-3, E-38System organization 1-26System starting 8-2/8-20System time 11-3, E-38

TTACL 8-20, 13-6, E-28Tape cable 7-6, 7-14Tape dump D-20Tape subsystem

517x 7-1/7-8, 8-4, 9-11519x 7-9/7-11, 8-2, 8-5, 9-11open-reel 7-2/7-8supported 7-12

Target disk 12-11/12-16

TCP/IPconfiguration file 13-13, 14-25Expand-over-IP F-13message E-46parallel library 13-12startup file 13-12

TCP/IPv6 F-13, F-14TELSERV 7-16Terminal emulator software 1-50Tetra 16 topology

cabling B-5/B-6, B-10/B-13, B-25/B-29changing 11-3

Tetra 8 topologycabling B-4, B-8/B-9, B-14/B-24changing 11-3

Time attribute 11-3TMF 13-12, 13-21Tools, installation 1-7, 5-6Troubleshooting

disks D-37LEDs 8-12/8-13software D-36, D-37workstations D-32/D-35

TSMabout 1-45, 1-46CIIN file 13-7client software 1-46configuring 9-16connections D-47firmware 12-9help 9-11IP addresses 10-18Low-Level Link

configuring 9-16functions 1-53IP addresses 10-9Management window 8-15preinstalled 1-50SP firmware 9-13starting D-47


Index U

TSM (continued)topology 8-14

Notification Director 9-16security 13-8server software 1-46Service Application

checking components with 9-2firmware 9-13illustration 9-4preinstalled 1-50public LAN 10-16redundant power scrub 9-2starting D-47

tape subsystem 9-11Twist-lock handles 2-8, E-7

UUnattended sites 10-14, 10-15, 12-9Uninterruptible power source (UPS) 1-15, 2-3User IDs, adding 13-21

VVirtual Hometerm Subsystem (VHS) 13-4Virtual memory, managing 12-8

WWAN subsystem

documentation 7-16ethernet 7-16installation summary 1-3installing printers 7-16installing SWAN 7-15planning 1-3process 12-4

WANBoot configuration file 14-24WANPRINT printer software 7-16Weight of enclosures 1-10

Wide area network (WAN) subsystemSee WAN subsystem

Windows CD E-16

XX.25 lines 13-19, 14-32

ZZSYSCONF configuration subvolume 12-6

Special Characters$AUDIT disk F-5$DSMSCM 14-20, F-5$IMON 9-14, E-44$NCP 14-33$SYSTEM disk F-5$SYSTEM.ZSYSCONF.CONFIG 12-3$SYSTEM.ZSYSCONF.SCF0000 2-4, 7-13$YMIOP.#CLCI 13-3, 13-6$YMIOP.#CNSL 13-3$ZCNF 12-3$ZEXP 14-27$ZHOME 13-3$ZPM 12-3$ZTCP default IP addresses 1-51
